[ID3 Dev] 0-termination in text frames

Florian Heidenreich support at mp3tag.de
Sat Mar 17 13:06:04 PDT 2007

Paul Taylor wrote:
> Florian Heidenreich wrote:
>> I'm still not sure about the issue. The ID3v2.4 spec from 
>> http://id3.org/id3v2.4.0-structure presents a list of possible 
>> encodings at '4. ID3v2 frame overview' where the terminating 0 is 
>> explicitly included in every text string:
>> <snip>
>> Frames that allow different types of text encoding contains a text
>>     encoding description byte. Possible encodings:
>>       $00   ISO-8859-1 [ISO-8859-1]. Terminated with $00.
>>       $01   UTF-16 [UTF-16] encoded Unicode [UNICODE] with BOM. All
>>             strings in the same frame SHALL have the same byteorder.
>>             Terminated with $00 00.
>>       $02   UTF-16BE [UTF-16] encoded Unicode [UNICODE] without BOM.
>>             Terminated with $00 00.
>>       $03   UTF-8 [UTF-8] encoded Unicode [UNICODE]. Terminated with $00.
>> </snap>
>> According to that list it seems to me, that every string includes a 
>> terminating $00 (or $00 00 when using UTF-16).
>> What do you think about it?
>> Thank you!
>> Kind regards,
>> Florian
> I think it is just saying that if you use a null terminated string then 
> you should terminate correctly for the encoding you use.
> <text string according to encoding> does not include a null terminator, 
> where a null terminator is required it is explicity stated in the spec
> as these extracts show.

Thanks for the clarification!

It seems that I'll have to change Mp3tag's ID3 writer :)

Kind regards,

To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org

More information about the ID3v2 mailing list