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 85948 - funny sorting order for Korean characters
funny sorting order for Korean characters
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: Views: All
unspecified
Other other
: Normal major
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 78830 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2002-06-19 16:02 UTC by kz
Modified: 2005-02-26 15:24 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description kz 2002-06-19 16:12:21 UTC 
Package: nautilus
Severity: normal
Version: 2.0.0
Synopsis: funny sorting order for Korean characters
Bugzilla-Product: nautilus
Bugzilla-Component: View as (Icons or List)

Description:
what the rule for ordering sort of icons?
For Korean characters of filename, nautilus does absolutely funny
sorting order.
the visible result does not fit to UCS4 order. then what?
so I even cannot imagine what the basement of sorting order.

If any data for sorting Korean characters required,
I'll gladly attach them.
ATM I hardly wonder what is necessary.

waiting for reply.




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-06-19 12:12 -------

Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.
Comment 1 kz 2002-06-19 16:25:37 UTC 
Even if I do insert a space as word breaker, the sort order changed.
Comment 2 Luis Villa 2002-07-02 09:41:15 UTC 
The sort order is a bit screwy all around; not sure if this is Korean
specific.
Comment 3 kz 2003-01-03 13:31:12 UTC 
I think it's ok now; in rawhide gnome 2.1, Korean locale with
G_BROKEN_FILENAMES=1.
Comment 4 Murray Cumming 2003-07-28 14:43:02 UTC 
*** Bug 78830 has been marked as a duplicate of this bug. ***
Comment 5 Murray Cumming 2003-07-29 07:31:59 UTC 
Is this still a problem?
Comment 6 Kjartan Maraas 2003-09-01 23:15:42 UTC 
Should this be closed? And should we close the tracker bug #83080 ?
Comment 7 Martin Wehner 2005-02-26 15:24:21 UTC 
Given the lack of activity on this bug, I guess it has been fixed. Feel free to
reopen if you can still reproduce it.