You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In version 3.9.3 WXXX (URL) ID3v2.3 tags are being parsed incorrectly as UCS-2 rather than ISO-8859-1. From the spec:
All numeric strings and URLs are always encoded as ISO-8859-1.
Example bytes of a WXXX tag where user_description should be 'あ' (UCS-2 encoded) and data should be https://www.example.com: 57 58 58 58 00 00 00 1E 00 00 01 FF FE 42 30 00 00 68 74 74 70 73 3A 2F 2F 77 77 77 2E 65 78 61 6D 70 6C 65 2E 63 6F 6D
I think the issue was introduced with this change: #120
We want the description to be encoded as UTF-16, but the link is encoded with ISO-8859-1 (as the spec says). jsmediatags 3.9.3 in the function getUserDefinedFields assumes that userDesc and userDefinedData should use the same charset.
In version 3.9.3
WXXX
(URL) ID3v2.3 tags are being parsed incorrectly as UCS-2 rather than ISO-8859-1. From the spec:Example bytes of a
WXXX
tag whereuser_description
should be 'あ' (UCS-2 encoded) anddata
should behttps://www.example.com
:57 58 58 58 00 00 00 1E 00 00 01 FF FE 42 30 00 00 68 74 74 70 73 3A 2F 2F 77 77 77 2E 65 78 61 6D 70 6C 65 2E 63 6F 6D
I think the issue was introduced with this change: #120
Repro: https://codepen.io/Quppa/pen/yLNbPpX
Example MP3 (contains just
TIT2
andWXXX
):jsmediatags.zip
The text was updated successfully, but these errors were encountered: