Creating iTunes compatible COMM frames

[Dudy Kohen]

This is the standard when the language is not defined or invalid.
It's not correct to set a default language in a library, so you should set
the language before writing.

On Tue, Jan 26, 2010 at 11:42 PM, patrick machielse <patrick at hieper.nl>wrote:

> Op 22 dec 2009, om 23:03 heeft patrick machielse het volgende geschreven:
>
> > It turns out that new comment frames by default do not have a language
> set, and TagLib writes out 'XXX' in place of the 3-character language code:
> >
> > //  commentsframe.cpp
> > ByteVector CommentsFrame::renderFields() const
> > {
> >    //...
> >    v.append(d->language.size() == 3 ? d->language : "XXX");
> >
> >
> > The ID3V2.4 spec says it should be an ISO 639-2 code. "XXX" isn't valid.
>
> Is this a bug in TagLib? I can't find a response to my original message in
> the list archives.
>
> Thanks,
> patrick
> --
> Patrick Machielse
> Hieper Software
>
> http://www.hieper.nl
> info at hieper.nl
>
> _______________________________________________
> taglib-devel mailing list
> taglib-devel at kde.org
> https://mail.kde.org/mailman/listinfo/taglib-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/taglib-devel/attachments/20100127/4afc108f/attachment.htm