Closed
Bug 978056
Opened 12 years ago
Closed 4 years ago
[OS.File] Use native encoding for file paths
Categories
(Toolkit Graveyard :: OS.File, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: Yoric, Unassigned)
Details
At the moment, whenever opening a file, OS.File uses an arbitrary file encoding:
- UTF-8 under Unix;
- platform encoding under Windows.
While this is correct under Windows, MacOS X, Android, B2G, this is not always correct under Linux. On Linux, we need to use http://dxr.mozilla.org/mozilla-central/source/xpcom/io/nsNativeCharsetUtils.h to use the correct encoding.
| Reporter | ||
Updated•12 years ago
|
OS: All → Linux
Comment 1•11 years ago
|
||
(In reply to David Rajchenbach-Teller [:Yoric] (use "needinfo") from comment #0)
> - platform encoding under Windows.
Why not UTF-16 on Windows?
| Reporter | ||
Comment 2•11 years ago
|
||
Because not all users have UTF-16 file systems. We let the OS handle the encoding, which should be right right choice.
Comment 3•4 years ago
|
||
Mass closure: OSFIle is being replaced with IOUtils and PathUtils. If you think this bug was closed in error, please re-open.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
Updated•3 years ago
|
Product: Toolkit → Toolkit Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•