[ID3 Dev] iTunes COM Frame question

[Dale Preston]

In the latest versions of iTunes, I have run across another questionable COM frame issue in my code.  My code takes the frame bytes after the language descriptor and parses the null terminated strings.  This has worked for some time so, even though I cannot say I remember absolutely, I have to assume this is a change in how iTunes creates the COM frame.  

Now, instead of returning an array of two strings (description and comment), my parser is returning three strings (description, comment, and an empty string) because the frame bytes end in two null bytes instead of one.

The questionable frame is using ISO-8859 encoding (0 encoding byte).

I am trying to decide if my code is flawed and needs to be fixed somewhere to handle this scenario as a valid frame or if this frame is flawed (I think this is the case) and I need to handle it as a flaw - basically throw away the third string in the array and keep on moving.

Thanks for any feedback on this,


Dale
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.id3.org/pipermail/id3v2/attachments/20070902/f5a29681/attachment.html>