Labs/Jetpack/Localization: Difference between revisions
Jump to navigation
Jump to search
(Created page with 'We've had some prelimenary thoughts on Jetpacks and l10n. Our basic thoughts are: *Disassociate translation files from the Jetpack itself. It's important that an author doesn't …') |
No edit summary |
||
| Line 4: | Line 4: | ||
*Use gettext for JS code. | *Use gettext for JS code. | ||
*We need to find a nice way of doing localization in HTML. This probably involves finding a nice pre-existing solution for doing client-side webpage localization. Anyone know about this? | *We need to find a nice way of doing localization in HTML. This probably involves finding a nice pre-existing solution for doing client-side webpage localization. Anyone know about this? | ||
== L20n == | |||
Alternative approach may be to go with [[L20n]], which is a new format with JS API that fits jetpack and provides much better localization experience. | |||
[[User:Gandalf]] is working on JEP for that and initial implementation, check at [http://hg.mozilla.org/users/zbraniecki_mozilla.com/l20n] | |||
Revision as of 23:42, 9 December 2009
We've had some prelimenary thoughts on Jetpacks and l10n. Our basic thoughts are:
- Disassociate translation files from the Jetpack itself. It's important that an author doesn't need to think hard about localization, and that others can then (from the Gallery) localize a Jetpack without the need to coordinate with the original author. (Of course, an original author can specify that they don't want others to localize, but that's not the default.
- Use gettext for JS code.
- We need to find a nice way of doing localization in HTML. This probably involves finding a nice pre-existing solution for doing client-side webpage localization. Anyone know about this?
L20n
Alternative approach may be to go with L20n, which is a new format with JS API that fits jetpack and provides much better localization experience.
User:Gandalf is working on JEP for that and initial implementation, check at [1]