L20n

	THIS PAGE IS A WORKING DRAFT
	The page may be difficult to navigate, and some information on its subject might be incomplete and/or evolving rapidly. If you have any questions or ideas, please add them as a new topic on the discussion page.

L20n is the codename for a localization architecture taking existing approaches one step further. The name stands for l10n 2. The architecture is laid out with Mozilla applications in mind, but should be applicable to other areas as well. As for Mozilla, Mozilla 2 will give us a chance to implement significant changes in our l10n architecture, and this is one attempt to do that.

Check out the L20n:FAQ.

There are several localization-related communities out there, and thus there are different target audiences for docs on l10n (and l20n). In the order of appearance in the lifecycle of some code, that would be

software authors (coders)
localizers
localization tool authors

Expect to see the level of complexity involved grow for each level of audience. Software authors should need only very limited knowledge about any particular language, localizers should need to know only the language they translate into well, localization tool authors should understand the variation of complexity coming with different languages.

Features

The L20n:Features page details on some of the features of the proposal, such as

developed in the open
clear separation between application logic and localization framework
supports both plural and grammatical forms
not bound to a particular implementation language
support specify fallback language for non-localized strings

Background

The L20n:Background article shows some common pitfalls that are common in todays software engineering practice. It's setting a base for what you should keep in mind when evaluating this proposal against others.

Control flow

The L20n:Control flow article explains how the flow of control differs in this proposal, compared to existing systems.

Examples

If you like to look at L20n:Examples, that's good.

Feedback

Feedback on this proposal is best directed to the mozilla.dev.i18n newsgroup, which is also available on Google groups or as a mailing list. Or you can use the Discussion pages here on the wiki, though those comments may get lost every now and then.

There is also a list of L20n:Issues pointing out issues we need to resolve.