[prev in list] [next in list] [prev in thread] [next in thread] 

List:       taglib-devel
Subject:    Re: Taglib + ogg/flac/speex +images.
From:       Anton Sergunov <setosha () gmail ! com>
Date:       2011-09-20 0:14:54
Message-ID: CAPdia6ubNZejpwcHbDY3BASO_g7NGrwXK9nfuC91ogeekUyj5A () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


It's not just binary data. It's base64 encoded binary data. So it's still
string.
20.09.2011 1:54 =D0=CF=CC=D8=DA=CF=D7=C1=D4=C5=CC=D8 "Scott Wheeler" <wheel=
er@kde.org> =CE=C1=D0=C9=D3=C1=CC:
> On Sep 19, 2011, at 3:40 PM, Michael Helmling wrote:
>
>> Shouldn't Xiph comments also support cover art, according to
>> http://wiki.xiph.org/index.php/VorbisComment#Cover_art?
>
> Ah, interesting. They've apparently updated the recommendation on that --
it used to be that they specifically said that binary data *should not* be
included in Xiph comments (and even specifically mentioned cover art).
Looking at that spec, it's actually quite a u-turn since
>
> In that case the answer is that there's no easy way to set those fields
without doing all of the [en/de]coding of the cover art fields yourself, bu=
t
it'd probably make sense to add a convenience method to the XiphComment
class to handle such.
>
> -Scott
> _______________________________________________
> taglib-devel mailing list
> taglib-devel@kde.org
> https://mail.kde.org/mailman/listinfo/taglib-devel

[Attachment #5 (text/html)]

<p>It&lsquo;s not just binary data. It&lsquo;s base64 encoded binary data. So \
it&lsquo;s still string. </p> <div class="gmail_quote">20.09.2011 1:54 пользователь \
&quot;Scott Wheeler&quot; &lt;<a \
href="mailto:wheeler@kde.org">wheeler@kde.org</a>&gt; написал:<br \
type="attribution">&gt; On Sep 19, 2011, at 3:40 PM, Michael Helmling wrote:<br> &gt; \
<br>&gt;&gt; Shouldn&#39;t Xiph comments also support cover art, according \
to<br>&gt;&gt; <a href="http://wiki.xiph.org/index.php/VorbisComment#Cover_art">http://wiki.xiph.org/index.php/VorbisComment#Cover_art</a>?<br>
 &gt; <br>&gt; Ah, interesting.  They&#39;ve apparently updated the recommendation on \
that -- it used to be that they specifically said that binary data *should not* be \
included in Xiph comments (and even specifically mentioned cover art).  Looking at \
that spec, it&#39;s actually quite a u-turn since <br> &gt; <br>&gt; In that case the \
answer is that there&#39;s no easy way to set those fields without doing all of the \
[en/de]coding of the cover art fields yourself, but it&#39;d probably make sense to \
add a convenience method to the XiphComment class to handle such.<br> &gt; <br>&gt; \
-Scott<br>&gt; _______________________________________________<br>&gt; taglib-devel \
mailing list<br>&gt; <a \
href="mailto:taglib-devel@kde.org">taglib-devel@kde.org</a><br>&gt; <a \
href="https://mail.kde.org/mailman/listinfo/taglib-devel">https://mail.kde.org/mailman/listinfo/taglib-devel</a><br>
 </div>



_______________________________________________
taglib-devel mailing list
taglib-devel@kde.org
https://mail.kde.org/mailman/listinfo/taglib-devel


[prev in list] [next in list] [prev in thread] [next in thread]