[gstreamer-bugs] [Bug 321383] Unreadable text in MP3 tags

GStreamer (bugzilla.gnome.org) bugzilla-daemon at bugzilla.gnome.org
Sun Nov 13 10:57:25 PST 2005


Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=321383
 GStreamer | gst-plugins-ugly | Ver: 0.9.x





------- Additional Comments From Tim-Philipp Müller  2005-11-13 18:57 -------
What kind of ID3 tags?

For (reading) ID3v1 tags this is supported, you just have to set the right
environment variable, e.g. set GST_ID3_TAG_ENCODING=cp1251 and it should work.

For ID3v2 tags this is not supported (nor required), because there is a very
clear spec for ID3v2 and you can store strings either in unicode or as
ISO-8859-1, so russian tags would need to be stored as unicode and be marked as
a unicode string.  That will already be read fine. Anything else is totally
broken and wrong and not according to spec (there is bug #320188 for this issue).

As for writing, I don't think GStreamer should be writing ID3v1 tags with random
encodings (this issue is basically unsolvable for ID3v1, so anything that isn't
plain ASCII should really not be stored in ID3v1 tags; the only reason this is
supported for reading is because there are simply so many broken files out
there). As for ID3v2 tags, GStreamer should only output ID3v2 tags that conform
to the specification. This includes storing russian text as unicode in ID3v2
tags (which should already work), but I doubt it will ever include labelling
strings that are really CP1251 encoded as Latin1 strings or unicode strings, if
that's what you meant.

Could you provide some more details about what specific issues you're running into?



------- You are receiving this mail because: -------
You are the assignee for the bug.
You are the QA contact for the bug.




More information about the Gstreamer-bugs mailing list