[datatype-dev] MP3 HTTP Streaming and Unicode ID3 tags

[datatype-dev] MP3 HTTP Streaming and Unicode ID3 tags

Eric Hyche ehyche at real.com
Fri Nov 3 09:35:54 PST 2006


Tony,

I probably won't be able to get to this for
a while, but I don't want it to fall through
the cracks. If you would like to fix this
and submit the CR, that would be great. I'll
review the CR and check it in (or we can
get you set up with CVS commit rights).

If you don't want to fix it yourself, then
please file a bug in the datatype project,
provide all the info you've provided in the
email thread (you could just copy the email
thread into the bug description if you want),
and then that will make sure I don't forget about it.

Eric

=============================================
Eric Hyche (ehyche at real.com)
Technical Lead
RealNetworks, Inc.  

> -----Original Message-----
> From: Tony Espy [mailto:espy at pepper.com] 
> Sent: Friday, November 03, 2006 12:23 PM
> To: ehyche at real.com
> Cc: datatype-dev at helixcommunity.org
> Subject: Re: [datatype-dev] MP3 HTTP Streaming and Unicode ID3 tags
> 
> Eric Hyche wrote:
> > What indication is there that an ID3 tag is Unicode
> > as opposed to ASCII? Is there some flag set somewhere,
> > or do we have to deduce it from the byte string (i.e. - 
> > lots of 0 bytes in between non-zero bytes, etc.)?
> 
> It depends, as most, but not all ID3v2 frames that include 
> text strings 
> support Unicode values.
> 
> The tags that CMp3Misc cares about are all "Text" frames,  which do 
> support encoded strings.  For text frames, the 1st byte of 
> the data is 
> an encoding byte:
> 
> 0x00 == ISO 8859-1 / Latin-1
> 0x01 == Unicode
> 
> This is the same for ID3v2.2 and ID3v2.3.
> 
> If the encoding byte specifies Unicode, then the string must 
> start with 
> the Unicode BOM ( 0xFFFE or 0xFEFF ).  Unicode strings are terminated 
> with 0x0000, whereas 8859-1 strings are terminated with a single 0x00.
> 
> Also, there's no logic to detect ID3v2.4 tags.  They're not 
> really used 
> at all in practice, but it might not be a bad idea to add a log 
> statement and skip the processing for now.
> 
> Here's a direct link to the ID3v2.3 spec's "Frame Overview" section.
> 
> http://www.id3.org/id3v2.3.0.html#sec3.3
> 
> And also for reference, here's a link to the ID3v2.2 spec:
> 
> http://www.id3.org/id3v2-00.txt
> 
> Thanks,
> /tony
> 
> 




More information about the Datatype-dev mailing list
 

Site Map   |   Terms of Use   |   Privacy Policy   |   Contact Us

Copyright © 1995-2007 RealNetworks, Inc. All rights reserved. RealNetworks and Helix are trademarks of RealNetworks.
All other trademarks or registered trademarks are the property of their respective holders.