[ID3 Dev] Why does Itunes write null terminated strings (v2.2/v2.3) ?

[Ben Bennett]

On Thu, Apr 05, 2007 at 09:56:40PM +0000, Mathias Kunter wrote:
> ...why should iTunes NOT write null terminated strings??
> 
> >From the 2.2 / 2.3 text frame specs:
> 
> "If the textstring is followed by a termination ($00 (00)) all the following
> information should be ignored and not be displayed."
> 
> So I would say it even is good practice to write a terminating 00 (or
> 00 00 in Unicode) to a text frame. Or did I misunderstand you?

Consensus from previous discussions was that this was not great
practice in 2.4.  A dumb implementation might consider the 0-length
string between the terminator and the end of the frame data as a
second value.  I think the smart implementation would be to omit the
trailing terminator (so only use it to separate lists) when writing.
When reading they should ensure that a trailing terminator is not
treated as a 0-length item.

In 2.3, it is less of a concern.  I omit it in my writer if the frame
is changed.

		      -ben

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