Forums | Admin

Discussion Forums: open-discussion

Start New Thread Start New Thread

 

By: Dirk Dittert
RE: ID3V2 tags and i18n [ reply ]  
2009-03-04 20:19
That is correct. ID3v2 is encoded in UTF-16. Beginning with v.2.4 it may also be encoded with UTF-8.

I have submitted a patch to Guillaume that will properly decode some of the fields but haven't heard anything back from him yet.

By: Jochen Hayek
RE: ID3V2 tags and i18n [ reply ]  
2008-02-06 21:49
Thanks for your advise!!!

Finally this little conversion did the job:

node.text.unpack('U*').pack('c*')

I could not believe it myself.

J.

By: Georg Fritzsche
RE: ID3V2 tags and i18n [ reply ]  
2008-02-05 19:03
take a look at id3.org...
for example the informal standard says per default ISO-8859-1 is used; anything else only if defined:
http://id3.org/id3v2.3.0#head-1a37d4a15deafc294208ccfde950f77e47000bca

if you look here:
http://id3.org/id3v2.3.0#head-05145d86196104464db40d63035e402ee3c504e7
you see the text information frames include a text encoding definition.

now whats left, apart from the standard, is of course the question what other applications can handle and expect... you have to look for that yourself.

hth,
Georg

By: Jochen Hayek
ID3V2 tags and i18n [ reply ]  
2008-02-05 10:54
I experienced problems, when I tried to create tags containing strings with german special characters.
I did a little research, and I became quite sure, that software dealing with ID3V2 should consider the values to be UTF-16 encoded and I think, that this software does that especially, but I got the impression, that the Windows Explorer, KDE amarok, iTunes, ... don't.
Any ideas?
I feel a little lost ;-)