https://bugzilla.novell.com/show_bug.cgi?id=814814
https://bugzilla.novell.com/show_bug.cgi?id=814814#c53
Dave Plater changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |aj@suse.com
See Also| |https://bugzilla.novell.com
| |/show_bug.cgi?id=780256
--- Comment #53 from Dave Plater 2013-04-25 06:55:35 UTC ---
I once made a hardware coin operated mp3 juke box (most probably one of the
first in the world) and am familiar with Id3v1 tags as I parsed them for both
the juke box display, a simple lcd and to print out a playlist for the front
panel. Id3v1 fields are a simple string of 8 bit wide characters so Utf-8
characters should be able to occupy those fields. A quick glance (I have to get
to work) at :
http://www.joelonsoftware.com/articles/Unicode.html a link which I found at
http://www.utf-8.com leads me to believe that Utf-8 displays Asian characters
let alone Cyrillic. I see these characters on my "en_US.UTF-8" system.
I haven't read up on any Id3 standards yet, I simply viewed the headers of mp3s
and worked it out for myself so I'm not an expert but I would like to know how
this mess started. Reading a little more of the Utf-8 website, I can understand
where the problem is. This is most probably why clementine likes Id3v2 tags.
Not sure where an Id3v2 tag sits when there is also an Id3v1 tag but I hope
it's always after and not before.
I think the solution for Russian community is a converter to create a unicode
Id3v2 tag from the Id3v1 tag. The older players will parse the Id3v1 tags so
they need to be preserved.
Hopefully the next time some upgrade breaks the rusxmms patch, it will be in
Factory and the problem won't find it's way into a release.
Does anyone in this bug test Factory?
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.