Chrome manifest files are ASCII. I think this should be WONTFIXed unless there's a compelling reason we need to allow UTF8 BOMs.
Non-ASCII filenames? Not all filesystems use the same encoding, which makes manually encoding the characters a chancy proposition. For example, if an author is naming files in their native language and use the 'Latin Capital Letter O With Stroke' on a filesystem that is Unicode-friendly, it might get encoded as C3 98. Later, the app/extension gets moved over to a Windows box, which always uses the 1252 encoding and that O-with-slash gets translated into D8. Not understanding Unicode, the manifest now refers to a file which doesn't exist. So supporting Unicode character encodings (at least those that are easily recognizable by their BOM) does have some benefit. Couldn't say whether it's worth the effort to implement, though. If this gets WONTFIXed, there should probably be a note mentioning the "ASCII-only" restriction on http://developer.mozilla.org/en/docs/Chrome_Registration,.
The .manifest files do not contain "filenames", they contain URIs (typically relative URIs)... you can and should %escape any non-ascii characters.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → WONTFIX
(In reply to comment #3) > The .manifest files do not contain "filenames", they contain URIs (typically > relative URIs)... you can and should %escape any non-ascii characters. > I just lost 2 hours searching for the bug. In my xulrunner application chrome.manifest is the only file encoded in ASCII.
Component: XRE Startup → Startup and Profile System
QA Contact: xre.startup → startup
You need to log in before you can comment on or make changes to this bug.