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

[Brian Mearns]

Well, if you look at the specification, it says that ALL text frames 
support multiple strings, in the form of a null separated list. This 
could be the reason they're doing it, though I'd say it's still pretty 
superfluous. But that's my best guess.

Paul Taylor wrote:
> Most people on this list knows that Itunes writes null terminated 
> strings, but does anyone know why - did they just make a mistake or is 
> there a reason for it ?
> I ask because I would like to know what you would expect a tag editor to 
> do with these values.
> 
> It could display these null terminators but this doesnt make much sense 
> to user using the tag editor
> It could silently hide these null terminators from view, but they they 
> would remain in the file possibly causing problems for other applications
> It could provide an option to explicity remove these null terminators 
> when the records are loaded, and remove them when they are saved, but 
> would this cause any kind of problem for Itunes
> 
> thanks Paul
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
> For additional commands, e-mail: id3v2-help at id3.org
> 

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