<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:arial,helvetica,sans-serif;font-size:10pt"><div>> If you have an APIC frame its very likely to have bytes that fall foul
of the unsynchronization schema ,<br>>and if you don't do Unsychronization
then that image WILL NOT display correctly in iTunes. So this is<br>>one
example where unsysnchronization is needed for newer software not for
the music to play okay, but<br>>for the metadata to display okay.<br><br>Yes, it's a pain...<br><br>>Ok I'll take another look at BE ( I thought it caused problems for
WIndows but perhaps my diagnosis was<br>>wrong) , but I don't think you can
just drop the BOM thats breaking the ID3 standard<br><br>Ah yes, ID3 specifies that a BOM must be present (the ISO specification of UTF-16 doesn't - I remembered incorrectly). Well, Windows Media Player stores strings within ID3 tags as little endian strings (as most unicode strings on the Windows platform are stored), but I'm not aware of problems caused by big endian strings. I however also didn't test this with all common versions of Windows Media Player.<br><br>Mathias<br><br></div><div style="font-family: arial,helvetica,sans-serif; font-size: 10pt;"><br><div style="font-family: arial,helvetica,sans-serif; font-size: 10pt;"><font face="Tahoma" size="2"><hr size="1"><b><span style="font-weight: bold;">Von:</span></b> Paul Taylor <paul_t100@fastmail.fm><br><b><span style="font-weight: bold;">An:</span></b> id3v2@id3.org<br><b><span style="font-weight: bold;">Gesendet:</span></b> Samstag, den 10. April 2010, 23:16:03 Uhr<br><b><span
style="font-weight: bold;">Betreff:</span></b> Re: [ID3 Dev] Which byte order should be used when using UTF16 BOM with ID3v23<br></font><br>Hi Mathias<br>Mathias Kunter wrote:<br>> Yes, unsynchronized tags aren't supported very well. However, de facto all software and hardware mp3 players support ID3 version 2 tags today, at least for skipping them if they're present within an mp3 file. It therefore shouldn't often be nescessary to unsynchronize an ID3 tag at all.<br>> <br>If you have an APIC frame its very likely to have bytes that fall foul of the unsynchronization schema , and if you don't do Unsychronization then that image WILL NOT display correctly in iTunes. So this is one example where unsysnchronization is needed for newer software not for the music to play okay, but for the metadata to display okay.<br>> If you need to ensure compatibility with (old) software or hardware mp3 implementations which don't support ID3 version 2 tags and
therefore actually scan the tag for a mp3 synchronization pattern, I would avoid using the 0xFF 0xFE byte order mark. You then may don't use any byte order mark at all and encode the string as big endian (as specified by the unicode standard), or explicitely use the big endian 0xFE 0xFF byte order mark - most applications which support UTF-16 should also be able to actually decode a big endian string!<br>Ok I'll take another look at BE ( I thought it caused problems for WIndows but perhaps my diagnosis was wrong) , but I don't think you can just drop the BOM thats breaking the ID3 standard<br><br>> <br>> Mathias K.<br>Paul<br><br>---------------------------------------------------------------------<br>To unsubscribe, e-mail: <a ymailto="mailto:id3v2-unsubscribe@id3.org" href="mailto:id3v2-unsubscribe@id3.org">id3v2-unsubscribe@id3.org</a><br>For additional commands, e-mail: <a ymailto="mailto:id3v2-help@id3.org"
href="mailto:id3v2-help@id3.org">id3v2-help@id3.org</a><br><br></div></div>
</div><br>__________________________________________________<br>Do You Yahoo!?<br>Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. <br>http://mail.yahoo.com </body></html>