<div dir="ltr"><div>How to read the specified tag like album , or original artist,original lyricst etc..<br><br></div>i need to how to set and get for the above tags.<br><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Dec 9, 2015 at 5:30 PM, <span dir="ltr"><<a href="mailto:taglib-devel-request@kde.org" target="_blank">taglib-devel-request@kde.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send taglib-devel mailing list submissions to<br>
<a href="mailto:taglib-devel@kde.org">taglib-devel@kde.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://mail.kde.org/mailman/listinfo/taglib-devel" rel="noreferrer" target="_blank">https://mail.kde.org/mailman/listinfo/taglib-devel</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:taglib-devel-request@kde.org">taglib-devel-request@kde.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:taglib-devel-owner@kde.org">taglib-devel-owner@kde.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of taglib-devel digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Problems after Update on taglib-1.10-1 (Urs Fleisch)<br>
2. Re: Problems after Update on taglib-1.10-1 (Tsuda Kageyu)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 8 Dec 2015 22:07:08 +0100<br>
From: Urs Fleisch <<a href="mailto:urs.fleisch@gmail.com">urs.fleisch@gmail.com</a>><br>
To: <a href="mailto:taglib-devel@kde.org">taglib-devel@kde.org</a><br>
Subject: Re: Problems after Update on taglib-1.10-1<br>
Message-ID:<br>
<CAAekg=WU=<a href="mailto:CGpmiYqrpiG1h-y8dXes6dzBctscLVRHAt5ynoU8g@mail.gmail.com">CGpmiYqrpiG1h-y8dXes6dzBctscLVRHAt5ynoU8g@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
I can confirm these problems on Arch Linux. I have tested it with kid3. If<br>
I use kid3 3.3.0-3, which was built against TagLib 1.9.1, and currently<br>
dynamically links to TagLib 1.10 on Arch Linux, I have the same situation:<br>
Saved tags are stored with wrong characters. If I build kid3 against TagLib<br>
1.10, the problems disappear. As Walter Schineis reported, the problems are<br>
solved when downgrading to TagLib 1.9.1. This looks like a binary<br>
incompatibility between the two versions.<br>
<br>
I have used abi-compliance-checker and found the following:<br>
<br>
In TagLib 1.9.1, we had the following<br>
<br>
String(const wstring &s, Type t = WCharByteOrder);<br>
String(const wchar_t *s, Type t = WCharByteOrder);<br>
<br>
where WCharByteOrder is a private static const String::Type, which will be<br>
initialized to UTF16LE on little endian systems (as most of our PCs are).<br>
<br>
In TagLib 1.10 we have<br>
<br>
String(const wstring &s, Type t = UTF16BE);<br>
String(const wchar_t *s, Type t = UTF16BE);<br>
<br>
with a default of UTF16BE. The default encoding seems to have changed from<br>
UTF16LE to UTF16BE. If a program is built against TagLib 1.9.1 and uses one<br>
of these String constructors with a default parameter for the type, the<br>
compiler will assign the value of WCharByteOrder (which still exists in<br>
TagLib 1.10 and is still UTF16LE) to the type parameter. The code in the<br>
constructor in TagLib 1.10 now tries to do something for compatibility with<br>
TagLib 1.8 (had same signatures for these constructors as TagLib 1.10), but<br>
this will fail if the application was linked against TagLib 1.9.1.<br>
<br>
So it seems that TagLib 1.10 is compatible with TagLib 1.8, but not with<br>
TagLib 1.9. The ChangeLog contains<br>
<br>
Fixed backwards-incompatible change in TagLib::String when constructing<br>
UTF16 strings.<br>
<br>
It seems that applications linked against TagLib 1.9 have to be recompiled.<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://mail.kde.org/pipermail/taglib-devel/attachments/20151208/19a62000/attachment-0001.html" rel="noreferrer" target="_blank">http://mail.kde.org/pipermail/taglib-devel/attachments/20151208/19a62000/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Wed, 9 Dec 2015 09:33:39 +0900<br>
From: Tsuda Kageyu <<a href="mailto:tsuda.kageyu@gmail.com">tsuda.kageyu@gmail.com</a>><br>
To: "<a href="mailto:taglib-devel@kde.org">taglib-devel@kde.org</a>" <<a href="mailto:taglib-devel@kde.org">taglib-devel@kde.org</a>><br>
Subject: Re: Problems after Update on taglib-1.10-1<br>
Message-ID:<br>
<<a href="mailto:CAG4hMGd8TuRPpnNYATe7S63m0yTWwW-%2BPHyN512rOg7Fdx0UPg@mail.gmail.com">CAG4hMGd8TuRPpnNYATe7S63m0yTWwW-+PHyN512rOg7Fdx0UPg@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi Urs,<br>
<br>
The parameter UTF16BE and UTF16LE are somewhat confusing. Unlike their<br>
name, UTF16BE means "the system byte order" and UTF16LE means "contrary to<br>
the system byte order" in TagLib 1.8 and 1.10. I introduced WCharByteOrder<br>
in v1.9 to straighten it out, but it caused some binary incomatibility<br>
between v1.8 and v1.9, so we reverted it in v1.10.<br>
<br>
Privately, I think that either way (keep the compatibility with v1.8 or<br>
v1.9) is logical accordingly. v1.9 is not compatible with older versions,<br>
but has been used for a long time...<br>
<br>
Regards,<br>
Kageyu<br>
<br>
2015-12-09 6:07 GMT+09:00 Urs Fleisch <<a href="mailto:urs.fleisch@gmail.com">urs.fleisch@gmail.com</a>>:<br>
<br>
> I can confirm these problems on Arch Linux. I have tested it with kid3. If<br>
> I use kid3 3.3.0-3, which was built against TagLib 1.9.1, and currently<br>
> dynamically links to TagLib 1.10 on Arch Linux, I have the same situation:<br>
> Saved tags are stored with wrong characters. If I build kid3 against TagLib<br>
> 1.10, the problems disappear. As Walter Schineis reported, the problems are<br>
> solved when downgrading to TagLib 1.9.1. This looks like a binary<br>
> incompatibility between the two versions.<br>
><br>
> I have used abi-compliance-checker and found the following:<br>
><br>
> In TagLib 1.9.1, we had the following<br>
><br>
> String(const wstring &s, Type t = WCharByteOrder);<br>
> String(const wchar_t *s, Type t = WCharByteOrder);<br>
><br>
> where WCharByteOrder is a private static const String::Type, which will be<br>
> initialized to UTF16LE on little endian systems (as most of our PCs are).<br>
><br>
> In TagLib 1.10 we have<br>
><br>
> String(const wstring &s, Type t = UTF16BE);<br>
> String(const wchar_t *s, Type t = UTF16BE);<br>
><br>
> with a default of UTF16BE. The default encoding seems to have changed from<br>
> UTF16LE to UTF16BE. If a program is built against TagLib 1.9.1 and uses one<br>
> of these String constructors with a default parameter for the type, the<br>
> compiler will assign the value of WCharByteOrder (which still exists in<br>
> TagLib 1.10 and is still UTF16LE) to the type parameter. The code in the<br>
> constructor in TagLib 1.10 now tries to do something for compatibility with<br>
> TagLib 1.8 (had same signatures for these constructors as TagLib 1.10), but<br>
> this will fail if the application was linked against TagLib 1.9.1.<br>
><br>
> So it seems that TagLib 1.10 is compatible with TagLib 1.8, but not with<br>
> TagLib 1.9. The ChangeLog contains<br>
><br>
> Fixed backwards-incompatible change in TagLib::String when<br>
> constructing UTF16 strings.<br>
><br>
> It seems that applications linked against TagLib 1.9 have to be recompiled.<br>
><br>
> _______________________________________________<br>
> taglib-devel mailing list<br>
> <a href="mailto:taglib-devel@kde.org">taglib-devel@kde.org</a><br>
> <a href="https://mail.kde.org/mailman/listinfo/taglib-devel" rel="noreferrer" target="_blank">https://mail.kde.org/mailman/listinfo/taglib-devel</a><br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://mail.kde.org/pipermail/taglib-devel/attachments/20151209/eed47fe2/attachment-0001.html" rel="noreferrer" target="_blank">http://mail.kde.org/pipermail/taglib-devel/attachments/20151209/eed47fe2/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
taglib-devel mailing list<br>
<a href="mailto:taglib-devel@kde.org">taglib-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/taglib-devel" rel="noreferrer" target="_blank">https://mail.kde.org/mailman/listinfo/taglib-devel</a><br>
<br>
<br>
------------------------------<br>
<br>
End of taglib-devel Digest, Vol 134, Issue 2<br>
********************************************<br>
</blockquote></div><br></div>