A natural-language localization framework
L20n reinvents software localization. Users should be able to benefit from the entire expressive power of a natural language. L20n keeps simple things simple, and at the same time makes complex things possible.
A straight-forward example in English:
And the same thing in Polish:
Visit L20n by Example to learn more about L20n's syntax.
You can take advantage of HTML bindings to localize your HTML documents with L20n. See docs/html for documentation and examples.
L20n encloses localization into so-called contexts. A context is an independent object with its own set of localization resources and available languages. You can have more than one context at the same time.
var ctx = L20ngetContext;ctxlinkResource'./locales/strings.l20n';ctxrequestLocales;
When you freeze the context by calling
requestLocales, the resource files
will be retrieved, parsed and compiled. You can listen to the
(emitted by the
Context instance when all the resources have been compiled)
ctx.getEntitySync to get translations
Alternatively, you can register callbacks to execute when the context is ready
(or when globals change and translations need to be updated) with
ctxlocalize'hello' 'new'var node = documentquerySelector'[data-l10n-id=hello]';nodetextContent = l10nentitieshellovalue;nodeclassListremove'hidden';;
You can find the complete documentation for localizers, developers and contributors at the Mozilla Developer Network. The original design documents can be found at the Mozilla Wiki. We also use the wiki for release planning.
We'd love to hear your thoughts on L20n! Whether you're a localizer looking for a better way to express yourself in your language, or a developer trying to make your app localizable and multilingual, or a hacker looking for a project to contribute to, please do get in touch on the mailing list and the IRC channel.
L20n is open-source, licensed under the Apache License, Version 2.0. We encourage everyone to take a look at our code and we'll listen to your feedback.
We <3 GitHub, but we prefer
text/plain patches over pull requests. Refer to
the Contributor's documentation for more information.