276691 - mldonkey->scan temp (web UI) : Correct UTF-16 to UTF-8 with the Safari, but not with the Firefox.

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[JongAm Park]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

There are some files whose names are written in Korean.
Mac standard encoding method for the file system is UTF-16.
When you try to see the local file listing with mldonkey's WEB UI,
(Transfer->Scan Temp ), it shows discomposed Korean characters, while the Safari
displays them correctly.
The used encoding method for the Safari and the Firefox is the UTF-8.


Reproducible: Always

Steps to Reproduce:
1. put some files with Korean file name into the mldonkey's temp directory.
2. launch the mldonkey
3. http://127.0.0.1:4080 for opening mldonkey's WEB UI.
4. click "Transfer" and click "Scan Temp".
5. See if the Korean file names are displayed correctly.
6. Compare the result with other browsers like the Safari.


Actual Results:  
Please take a look the screenshot I will attach.

Expected Results:  
Correct conversion to the UTF-8.

I don't think this problem is caused by the mldonkey, because if you open local
directory with file:///blah.. then you also can confirm that Korean file names
are displayed as discomposed.

Comment 1

[JongAm Park]

Attachment: How it looks with the Safari - Correct

Comment 2

[JongAm Park]

Attachment: How it looks with the Firefox - Incorrect

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.