[ID3 Dev] Encoding UTF-16 (i.e UTF-16 with BOM which is the most compatible choice Little Endian or Big Endian ?)

[Pierre-Yves Thoulon]

Shouldn't matter. The BOM indicates which convention was used, and so any
decent decoder should be able to handle both UTF-16 types...

Best regards,
Pyt.


On Wed, Apr 27, 2011 at 12:16, Paul Taylor <paul_t100 at fastmail.fm> wrote:

> When encoding string as UTF-16 (i.e UTF with BOM) which is the most
> compatible choice Little Endian or Big Endian, should you chnage default
> based on what latform you are on ?
>
> i.e Encoding Beck as BOM Big Endian would be
> FE FF 00 62 00 65 00 63 00 6B
>
> and BOM little Endian would be
> FF FE 62 00 65 00 63 00 6B 00
>
> Seems Big Endian might be better because wouldn't cause a load of
> unsynchronization if unsynchronizations was enabled.
>
> But I know Macs and Pcs tend to default to the opposite for this sort of
> stuff
>
> Paul
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
> For additional commands, e-mail: id3v2-help at id3.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.id3.org/pipermail/id3v2/attachments/20110427/cfed3c26/attachment.html>