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 645486 - hard-coded StringType.Latin1 causing content not correctly parsed
hard-coded StringType.Latin1 causing content not correctly parsed
Status: RESOLVED DUPLICATE of bug 642993
Product: taglib-sharp
Classification: Other
Component: General
unspecified
Other All
: Normal major
: ---
Assigned To: taglib-sharp-maint
taglib-sharp-maint
Depends on:
Blocks:
 
 
Reported: 2011-03-22 01:29 UTC by unruledboy
Modified: 2011-03-23 18:53 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description unruledboy 2011-03-22 01:29:56 UTC 
Hi,

   I got a lot of mp3 files, most of them are using GB2312 encoding for the tagging content, because in TagLib.Id3v1.StringHandler is using StringType.Latin1, thus the parsed tag contents are not correct.

   Can we allow the user to pass proper encoding to File.Create to address this issue?

   This kind of problem might apply to any format that hard-code Latin1 as the encoding.
Comment 1 unruledboy 2011-03-22 01:31:37 UTC 
FYI, after I change the encoding while debugging, it's working correctly.
Comment 2 Alexander Kojevnikov 2011-03-22 01:40:14 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 642993 ***
Comment 3 unruledboy 2011-03-22 01:58:52 UTC 
Hi, (In reply to comment #2)
> 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 642993 ***


I think Encoding.Default is NOT a good idea, for example I am using a windows with en-gb as the default encoding, but actually I am parsing files that are with gb2312 encoding, so either latin1 or en-gb(default) will be WRONG.

I still want to stick to have the ability for the user to specify the encoding.
Comment 4 Gabriel Burt 2011-03-23 18:53:21 UTC 
Please comment on the other bug