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 48181 - bad: cannot display file name which is in multibyte
bad: cannot display file name which is in multibyte
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: Internationalization (i18n)
1.0.x
Other Linux
: Normal normal
: old
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2001-04-27 05:34 UTC by granziliao
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description granziliao 2001-09-10 01:18:32 UTC
The nautilus file manager can not display file names that are in 
multibyte (like chinese and japanese) The nautilsu peference offers 
4 choice for displaying file names ,but all the choices are coded in 
ISO-8859-1 it cannot support chinese-Big5,chinese-GB ,Japanese,Korea
.......etc

* REPRODUCIBLE: Always

* STEPS TO REPRODUCE:

just open nautilus in the directaries which have some
file named in multibyte charset( like chinese)

* ACTUAL RESULTS: 

 can not display file name (in multibyte)correctly

* EXPECTED RESULTS: 

  nothing



------- Additional Comments From dan@eazel.com 2001-04-27 02:54:01 ----

CC'ing Ramiro.

Ramiro - Could you look into this?



------- Additional Comments From eli@eazel.com 2001-04-27 10:43:11 ----

Are you using Red Hat 7.0 or 7.1?

Could you be seeing bug #48042?



------- Additional Comments From don@eazel.com 2001-05-01 12:38:07 ----

Not a 1.0.3 blocker.  Moving to "later" as P3.




------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-09-09 21:18 -------

The original reporter (granziliao@sinamail.com) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.

Comment 1 John Fleck 2002-01-05 04:15:03 UTC
Changing to "old" target milestone for all bugs laying around with no milestone set.
Comment 2 Kjartan Maraas 2002-08-03 10:57:22 UTC
Still not fixed in 2.0.x?
Comment 3 Dave Bordoley [Not Reading Bug Mail] 2002-10-31 14:49:24 UTC
this should be fixed by pango.