Closed
Bug 253623
Opened 21 years ago
Closed 9 years ago
Improve support for non-ASCII file:// URLs
Categories
(Core :: Networking, defect)
Core
Networking
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: darin.moz, Unassigned)
References
()
Details
(Keywords: helpwanted, intl)
Attachments
(1 file)
53.57 KB,
image/jpeg
|
Details |
Improve support for non-ASCII file:// URLs.
Today, file:// URLs in Mozilla should be encoded using the filesystem charset
and then any non-ASCII character should be %-escaped. However, it is often the
case that UTF-8 characters are passed to Necko via NewURI or GetFileFromURLSpec.
The current implementation of GetFileFromURLSpec does not handle UTF-8 input
characters properly unless the native filesystem charset is UTF-8!
It might help if nsFileProtocolHandler::NewURI passed the native filesystem
charset as the origin charset parameter to nsStandardURL::Init.
Reporter | ||
Updated•21 years ago
|
Keywords: helpwanted
Target Milestone: --- → Future
Comment 2•21 years ago
|
||
what's that screenshot supposed to demonstrate?
This report in order for there to be a picture which is attached, thought that
it means that the folder name of non-ascii illegal character.
Comment 4•20 years ago
|
||
Searching for 'non-ascii' turns up a lot of related bugs with different
approaches to resolve this and related issues. To ease the tracking, I'm listing
a couple of related bugs (we need 'related bugs' feature in bugzilla) : bug
263750, bug 278161.
Keywords: intl
Reporter | ||
Updated•19 years ago
|
Assignee: darin → nobody
QA Contact: benc → networking
Target Milestone: Future → ---
Comment 5•9 years ago
|
||
a lot has improved here... and the bug isn't specifically actionable so I'm closing
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•