Closed
Bug 716189
Opened 13 years ago
Closed 13 years ago
UTF-8 Encoded Chinese Filename in a FTP Site Fail to Show Correctly
Categories
(Firefox :: General, defect)
Firefox
General
Tracking
()
People
(Reporter: damage3025, Unassigned)
Details
Attachments
(2 files)
The URL of the FTP site is here
ftp://www.shlug.org/Slide/2011/11/
This FTP site use UTF-8 Encoding. And there is a file called `如何成为一名黑客.pdf`. The filename is in Chinese.
I've tested with following environments, both OS use English locales. However, I'm quite sure they have well Chinese support. Since I'm a native Chinese and use Chinese web sites every day.
Windows 7 + Firefox 4.0.1/9.0.1
OS X 10.7 + Firefox 9.0.1
The result is, Firefox cannot display correct characters even UTF-8 Encoding is manually set. A screenshot is given in the attachment.
To further prove it is likely to be Firefox's fault. I've tested with Google Chrome, Safari and IE8. All of them can display correct character when UTF-8 Encoding is set.
I also captured FTP packets in Windows using Wireshark. I found no difference in the FTP data received by Firefox and IE8. But the display result is different.
The issue is actually more than a display issue. Since I even cannot download the file in Firefox, but those browsers that display the filename correctly can.
Reporter | ||
Comment 1•13 years ago
|
||
cat /etc/*-release
CentOS release 5.5 (Final)
In the above OS with Firefox 9.0.1, same problem also occur.
Updated•13 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 3•13 years ago
|
||
I read through RFC 2640, the stuff Bug 26767 concerned, except the Annex A, B.
However, I don't think it is relevant to my problem.
If the user select the correct encoding, why should the browser display some garbage?
Here is the UTF-8 representation of `如何成为一名黑客`
e5 a6 82 e4 bd 95 e6 88 90 e4 b8 ba e4 b8 80 e5 90 8d e9 bb 91 e5 ae a2
It is copied from Wireshark result and verified by online tools.
Reporter | ||
Comment 4•13 years ago
|
||
You need to log in
before you can comment on or make changes to this bug.
Description
•