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 615211 - [id3demux] detect charset of broken tags
[id3demux] detect charset of broken tags
Status: RESOLVED DUPLICATE of bug 451565
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
unspecified
Other All
: Normal enhancement
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
: 621589 627680 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-04-08 19:23 UTC by Taras
Modified: 2011-05-18 20:21 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Taras 2010-04-08 19:23:04 UTC
is realized only in "DeaDBeeF"
Comment 1 Taras 2010-04-08 19:25:46 UTC
< (of audio players for Linux)
Comment 2 Jonathan Matthew 2010-04-08 21:11:16 UTC
I have no idea what this bug report is about.  Please explain the problem you're having.
Comment 3 Taras 2010-04-09 09:17:12 UTC
auto-detect encoding in the id3 tags (for example cp1251, iso8859-1 and unicode)
Comment 4 Jonathan Matthew 2010-04-09 09:42:26 UTC
This would be implemented in GStreamer if it was going to happen at all.
Comment 5 Tim-Philipp Müller 2010-04-09 09:49:54 UTC
Well, we've WONTFIXed this a few times in the past, but I've got a plan and some stuff locally, so it may just happen one day.

Moving to id3demux for now, but would probably also involve libgsttag in -base.
Comment 6 Jonathan Matthew 2010-06-28 07:08:28 UTC
*** Bug 621589 has been marked as a duplicate of this bug. ***
Comment 7 Jonathan Matthew 2010-08-22 23:41:28 UTC
*** Bug 627680 has been marked as a duplicate of this bug. ***
Comment 8 Sebastian Dröge (slomo) 2011-05-18 20:21:05 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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