After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 321383 - Russian text in MP3 tags unreadable
Russian text in MP3 tags unreadable
Status: RESOLVED DUPLICATE of bug 149274
Product: GStreamer
Classification: Platform
Component: gst-plugins-ugly
0.9.x
Other All
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-11-13 18:34 UTC by Sergey Bezdenezhnyh
Modified: 2005-11-15 18:59 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description Sergey Bezdenezhnyh 2005-11-13 18:34:17 UTC
In Russia the most of the MP3 tags are in the cp1251 code page.
Is it possible to add support of automatic MP3 tags convertion from cp1251 code
page to utf8 while reading file. And automatic conversion support from utf8 to
cp1251 when saving MP3 tags.
Comment 1 Tim-Philipp Müller 2005-11-13 18:57:24 UTC
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?

Comment 2 Tim-Philipp Müller 2005-11-15 18:58:54 UTC
Setting the environment variable resolved the issue (according to private mail).
This is a duplicate of #149274 then.
Comment 3 Tim-Philipp Müller 2005-11-15 18:59:37 UTC

*** This bug has been marked as a duplicate of 149274 ***