Generic API useless with Unicode for ID3v2?
Andreas Klöckner
lists at informa.tiker.net
Thu Oct 18 15:46:56 CEST 2007
On Donnerstag 18 Oktober 2007, Scott Wheeler wrote:
> Andreas Klöckner wrote:
> > If we enter the case (*), no encoding is set. Am I mis-reading this?
>
> I oversimplified in my explanation. The encoding is set right after the
> frame parsed (in ID3v2FrameFactory). If a default encoding has been set
> it is applied to each text frame directly after it is instantiated.
> This naturally has no effect on the tags in the files until the tag is
> saved again.
>
> In this specific example it is not set again because it was already set
> (if applicable) by the FrameFactory.
Well, then something is broken.
I do this:
TagLib::ID3v2::FrameFactory::instance()->setDefaultTextEncoding(TagLib::String::UTF8);
and then dump the textEncoding of each TextIdentificationFrame of an MP3 and I
get:
TALB
Latin1
TIT2
Latin1
TPE1
Latin1
I'm confused.
Andreas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/taglib-devel/attachments/20071018/8fe2869f/attachment.pgp
More information about the taglib-devel
mailing list