[ID3 Dev] BOMS for multiple string fields ?

Mathias Kunter mathiaskunter at yahoo.de
Sat Apr 24 04:36:01 PDT 2010

Well, the specification says: "UTF-16 [UTF-16] encoded Unicode [UNICODE] with BOM. All strings in the same frame SHALL have the same byteorder."

1) Strings in the same frame MAY have different byteorder.
2) To encode different byteorder strings, each string MUST have a BOM.
3) In order to be consistent with 2), also encode same byteorder strings with a BOM for each string.

Using a BOM for each string also is the solution which should be most compatible with other ID3 implementations, since no UTF-16 compliant ID3 implementation should ignore the BOM of any string.

Mathias K.

Von: Paul Taylor <paul_t100 at fastmail.fm>
An: id3v2 at id3.org
Gesendet: Montag, den 19. April 2010, 13:33:41 Uhr
Betreff: [ID3 Dev] BOMS for multiple string fields ?

If have a text frame with multiple strings, stored as a null separated list, where null is represented by the termination code for the character encoding how do you encode type 01   (UTF-16 [UTF-16] encoded Unicode [UNICODE] with BOM)  Do you write BOM for each string or just at the start of the total string


Say just have the single char string twice (0xDE 0x03)

Should BOM be written for both strings

0xFF 0xFE 0xDE 0x03 0x00 0x00  0xFF 0xFE 0xDE 0x03

or just at the start of the total string

0xFF 0xFE 0xDE 0x03 0x00 0x00  0xDE 0x03

(null separator should be written for all fields except  last one)


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/20100424/01523485/attachment.html>

More information about the ID3v2 mailing list