local file list, better to use system default charset instead of browser default charset

VERIFIED FIXED in mozilla1.3alpha

Status

()

Core
Internationalization
VERIFIED FIXED
15 years ago
15 years ago

People

(Reporter: Yuying Long, Assigned: nhottanscp)

Tracking

({intl})

Trunk
mozilla1.3alpha
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

15 years ago
Build: 11-08 trunk build on all platforms

After bug 102812 checked in, the file is in html mode, but for local file list,
better to use system default charset instead of browser default charset.  Please
see comment 101 and 102 in bug 102812.

Here is an example:
When I am running on a Japanese windows system, after I launch the browser, then
open the local file list, those Japanese folder/file names are displayed
garbled, I have to change the browser default charset to shift-jis in order to
view those names.

If I set browser default charset as UTF-8, those Japanese names will disappear.
(Reporter)

Comment 1

15 years ago
reassign to nhotta.
Assignee: smontagu → nhotta
Keywords: intl
(Assignee)

Updated

15 years ago
Target Milestone: --- → mozilla1.3alpha
(Assignee)

Comment 2

15 years ago
Created attachment 105909 [details] [diff] [review]
Reset parser's charset to file system's default for file url.
(Assignee)

Updated

15 years ago
Attachment #105909 - Flags: review?(yokoyama)

Comment 3

15 years ago
Comment on attachment 105909 [details] [diff] [review]
Reset parser's charset to file system's default for file url.

/r=yokoyama
(Assignee)

Updated

15 years ago
Attachment #105909 - Flags: superreview?(bzbarsky)
Attachment #105909 - Flags: superreview?(bzbarsky) → superreview+

Comment 4

15 years ago
Comment on attachment 105909 [details] [diff] [review]
Reset parser's charset to file system's default for file url.

/r=yokoyama
Attachment #105909 - Flags: review?(yokoyama) → review+
(Assignee)

Comment 5

15 years ago
checked in to the trunk
Status: NEW → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → FIXED
(Reporter)

Comment 6

15 years ago
Verified fixed in 11-19 trunk build on WinME.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.