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 78830 - Files with Korean names are not sorted properly
Files with Korean names are not sorted properly
Status: RESOLVED DUPLICATE of bug 85948
Product: nautilus
Classification: Core
Component: Views: All
unspecified
Other other
: Normal normal
: 1.1.x
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks: 83080
 
 
Reported: 2002-04-16 05:06 UTC by Xavier Cho
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Xavier Cho 2002-04-16 05:06:06 UTC 
Files and folders with Korean names are not sorted properly.

I have set G_BROKEN_FILENAMES=1, but both euc-kr and utf-8 
encoded names have the same problem. 

=================================================
Korean GNOME Community - http://gnome.or.kr
Comment 1 kz 2002-04-16 07:15:40 UTC 
I suspect it's UTF-8 issue, which nautilus sorted by.
I think it's best to have another hidden column to be sorted:
    the strings are all UCS-4 not UTF-8 or native.
Comment 2 Luis Villa 2002-04-25 16:11:04 UTC 
I'm marking as 1.1.x because I think this should get looked at, but...
it seems like the answer is probably 'use UTF-8', right?
Comment 3 Xavier Cho 2002-04-30 07:45:23 UTC 
Sorry but I don't understand what do you mean about 'use UTF-8'. As I
have mentioned above, this problem happens for both UTF-8 and EUC-KR
file names, not just EUC-KR.
Comment 4 Kjartan Maraas 2002-10-27 14:19:17 UTC 
Upping the severity on this. It's not a minor problem that files are
sorted wrong for a locale I think.
Comment 5 Andrew Sobala 2003-03-24 18:18:02 UTC 
Does this still happen in GNOME 2.2?
Comment 6 Kjartan Maraas 2003-05-03 16:01:07 UTC 
Is anyone working on this currently?
Comment 7 Murray Cumming 2003-07-28 14:43:04 UTC 

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