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.

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

1. software authors (coders)
2. UI localizers
3. content localizers
4. 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.

Characteristics

The L20n:Characteristics 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 all grammatical and stylistic features of languages
• not bound to a particular implementation language
• support specify fallback language for non-localized strings
• workflow that encourages cooperation from localizers and makes localization maintenance easy

Toolbox

One of the best ways to learn what L20n has to offer is to review the Toolbox. It leads you through the capabilities of L20n introducing them one by one and letting you discover the power of its semantics.

Roadmap

• L20n 1.0
• L20n.Next

Features

[[L20n:Features|List of features] that are debated for inclusion into L20n.

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.

Design

Read more about the essential parts for the L20n:Design.

Examples

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

For L20n-DOM bindings look at those tests.

Grammar

Find out more about the file format on the annotated grammar. The annotations are sketchy still, but there.

Workflow

The L20n:Workflow article explains workflow scenarios that L20n is designed to fit into.

Feedback

Feedback on this proposal is best directed to the localization-20 group. 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.

Some first thoughts on L20n:Requirements

Weekly Meetings

Each Monday, the l20n team meets to discuss the progress of the project.