Closed Bug 1111281 Opened 10 years ago Closed 3 years ago

nsIStringBundleService cannot load .properties files with non ASCII name

Categories

(Core :: General, defect)

34 Branch
x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED INACTIVE

People

(Reporter: ct.gll, Unassigned)

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:34.0) Gecko/20100101 Firefox/34.0
Build ID: 20141201171754

Steps to reproduce:

The nsIStringBundleService cannot open a .properties file which contains non-ASCII characters in its path. Opening the file directly from the address bar is ok.

See the minimal example I joined. When the "bundléstring" is replaced by "bundlestring" in the chrome.manifest and example.js, the example.properties file is loaded as expected.


Actual results:

It triggers a NS_ERROR_FILE_NOT_FOUND: Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIStringBundle.GetStringFromName] error.


Expected results:

nsIStringBundleService should be able to load files with UTF-8 path.

We're not going to work on StringBundle anymore.

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: