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 593592 - Banshee does not properly group by Track Number for a Chinese Artist I have
Banshee does not properly group by Track Number for a Chinese Artist I have
Status: RESOLVED DUPLICATE of bug 499650
Product: banshee
Classification: Other
Component: Metadata
1.4.3
Other Linux
: Normal normal
: 1.x
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-08-30 22:31 UTC by solzenith
Modified: 2009-08-31 11:12 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Picture of two albums that to not group properly by Track Number (57.83 KB, image/png)
2009-08-30 22:31 UTC, solzenith
Details

Description solzenith 2009-08-30 22:31:45 UTC
Created attachment 142089 [details]
Picture of two albums that to not group properly by Track Number

So I have some albums by a Chinese artist, Faye Wong, and 4 or so out of the 8
of her albums that I have are not properly grouped when reading the library.
All the ID3 tags are there. The song names are generally in Chinese. The track
number ID3 tags are all there, but they will not group properly. For one of the
albums it groups them like 2,4,5,6,7,8,9,10,1,3 and for another the tracks are
grouped 1,3,5,4,2,6,7,8,9,10,11. The Album name is identical to itself, in
Chinese, for each of those albums. I have not noticed if this is happening with
other artists since I just got Banshee. I did go on #ubuntu on FreeNode to ask
about this, and someone mentioned to me that they get this problem often with
their playlists (they didn't specify though whether it was with Chinese artists
or anything like that, I don't know if this is a language issue with the ID3
tags, even though the numbers for the track lists are just numbers). 

Thank you, I hope this can be fixed!
Comment 1 Bertrand Lorentz 2009-08-31 11:12:56 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but
we are happy to tell you that the problem has already been fixed. It should be
solved in version 1.5.0.

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