Bug 84897 - gftp 2.0 can't enter directory with Chinese names
gftp 2.0 can't enter directory with Chinese names
Product: Red Hat Linux
Classification: Retired
Component: gftp (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jonathan Blandford
Mike McLean
: i18n
Depends On:
  Show dependency treegraph
Reported: 2003-02-23 01:49 EST by Need Real Name
Modified: 2013-04-02 00:17 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-06-10 01:43:06 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2003-02-23 01:49:26 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; zh-CN; rv:1.2.1) Gecko/20030206

Description of problem:
When I use gftp 2.0 (the xft version) to log into a ftp server, I find that gftp
can only enter directory with English names (e.g. pub, incoming, etc.). For
directory with Chinese names (e.g. ��ת�ļ�ר��Ŀ¼), gftp complains that "550
/incoming/��ת�ļ�ר��Ŀ¼: No such file or directory."

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Use gftp 2.0 to log into ftp.lib.pku.edu.cn (or any other ftp servers
containing directories with Chinese names)
2.Try to dive into the directories with Chinese names.


Actual Results:  gftp can't enter those directories. 

Expected Results:  gftp should be able to enter those directories freely, just
like gftp 1.0 does.

Additional info:

My locale is zh_CN.GB18030 (Simplified Chinese).
Comment 1 Warren Togami 2004-04-15 00:54:52 EDT
Is this still an issue with FC1 or FC2 development?
Comment 2 Leon Ho 2004-06-10 01:42:27 EDT
Created attachment 101020 [details]

Thanks for your report. I am using FC2 and it works for me. Please confirm
again if that's not the same case. Attached is the screenshot.

Note You need to log in before you can comment on or make changes to this bug.