Bug 104090

Summary:	write UTF8 instead of ISO8859-1 ID3 tags
Product:	[Frameworks and Libraries] AudioCD-KIO	Reporter:	Noam Raphael <noamraph>
Component:	General	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	ASSIGNED ---
Severity:	normal	CC:	icefox, rapkasta, yurchor
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:

Description Noam Raphael 2005-04-17 21:34:34 UTC

Version:           unknown (using KDE 3.3.2,  (3.1))
Compiler:          gcc version 3.3.5 (Debian 1:3.3.5-8)
OS:                Linux (i686) release 2.6.7-1-386

Hello,

CDDB (or at least freedb) now supports UTF-8 information. However, mp3 files created by kio/audiocd are using ID3 version 1 tags, which do not support UTF8, so the created tags consist of question marks, instead of (in my case) Hebrew characters.

The problem is probably not in CDDB information retrieval (kscd works fine with these albums), and not with reading ID3 version 2 tags (konqueror, kaffeine and noatun do that fine, with other mp3 files).

(I marked this as a bug, although from the programmer point of view this is a feature request. However, from the user's point of view this is definitely not a feature request. I hope my marking was ok.)

Thank you,
Noam Raphael

Comment 1 Thiago Macieira 2005-04-17 21:45:21 UTC

Your wish can probably be summarised as "write ID3v2 when non-Latin1 characters are present". Is that it?

Comment 2 Noam Raphael 2005-04-17 23:40:09 UTC

Yes, it is.
You can probably add the word utf8 somewhere in that definition, since I've 
encountered an ID3v2 writer that only accepted Latin1, but, of course, even 
without mentioning it, it's quite clear why you should want ID3v2 when 
non-Latin1 characters are present...

On 17 Apr 2005 19:45:24 -0000, Thiago Macieira <thiago@kde.org> wrote:
[bugs.kde.org quoted mail]
Yes, it is.<br>
You can probably add the word utf8 somewhere in that definition, since
I've encountered an ID3v2 writer that only accepted Latin1, but, of
course, even without mentioning it, it's quite clear why you should
want ID3v2 when non-Latin1 characters are present...<br><br><div><span class="gmail_quote">On 17 Apr 2005 19:45:24 -0000, <b class="gmail_sendername">Thiago Macieira</b> &lt;<a href="mailto:thiago@kde.org">thiago@kde.org
</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">------- You are receiving this mail because: -------<br>You reported the bug, or are watching the reporter.
<br><br><a href="http://bugs.kde.org/show_bug.cgi?id=104090">http://bugs.kde.org/show_bug.cgi?id=104090</a><br><br>------- Additional Comments From thiago kde org&nbsp;&nbsp;2005-04-17 21:45 -------<br>Your wish can probably be summarised as &quot;write ID3v2 when non-Latin1 characters are present&quot;. Is that it?
<br></blockquote></div><br>

Comment 3 Noam Raphael 2005-04-17 23:43:32 UTC

Oh, sorry for all that 'quote' garbage! Next time I'll delete it from my message.

Comment 4 icefox 2005-12-17 22:47:13 UTC

audiocd uses lame to encode the mp3's, would adding the --add-id3v2 command do the job?

Comment 5 shattered 2007-07-29 15:09:47 UTC

No, lame's id3v2 support is broken (at least in 3.97).  It doesn't set 'encoding byte'.

Comment 6 shattered 2007-07-29 15:38:28 UTC

...but there's an experimental patch at http://sourceforge.net/tracker/index.php?func=detail&aid=1192706&group_id=290&atid=300290 which fixes that.  It's not included in 3.97.

Comment 7 shattered 2008-12-06 17:00:33 UTC

Quoting aforementioned sf.net tracker entry:

"In LAME 3.98 stable there is some experimental code you may use. In case
your system has libiconv installed, define the preprocessor symbol
HAVE_ICONV when building LAME frontend executable. Now you can use
'--uTitle abc' '--uAlbum def', '--uArtist ghi', '--uGenre jkl' and
'--uComment mno' to store ID3v2 tags in UCS2 encoding."

Comment 8 Maarten De Meyer 2012-11-16 15:17:11 UTC

*** Bug 212616 has been marked as a duplicate of this bug. ***