-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proper way to add locale #134
Comments
I also tried l20n (which seems to be where it's going anyways). EDIT: Correction. l20n's i e |
I've already tried inserting a few prefs but none of them seem to work.
|
Hmm, how does it fail? Does it report an error, fail silently, or do something else?
Hmm, as I understand it, this should work, if your chrome.manifest file is in the top-level directory of your app, and it contains an instruction like Nevertheless, you're right that l20n is the future of localization for Firefox, so it's probably a better solution for your use case as well. |
It looks like intl.accept_languages is a "complex value" pref whose value isn't the literal string to which it's set but rather comes from a file that is referenced by the pref: http://searchfox.org/mozilla-central/source/modules/libpref/init/all.js#2312 After a bit of searching the codebase, I found some code that does something like this:
Adding that to the end of examples/hello-world-html/main.js causes this line to be output on the console:
|
It blocks the UI and displays the following error message
And thanks. The other code works. Now to figure out how to actually make use of that. |
I'm desperately trying to add locales to my code, using
.properties
files.What is the proper way to do this?
So far I've been trying to manually load a
chrome.manifest
file in the root directory, however that fails.Here's the code I put inside
main.js
for a PoC.The text was updated successfully, but these errors were encountered: