L20n/Toolbox: Difference between revisions

Making some edits to the intros, preparing for page rename
(Making some edits to the intros, preparing for page rename)
Line 1: Line 1:
{{DRAFT}}
== Introduction ==
== Introduction ==


Currently available localization architectures are usually little more sophisticated than static key:value pair lists and rarely allow localizers to provide high quality localizations that would look natural to the user.
L20n is a localization format and an API that is aiming at remodeling the way developers internationalize their code and how localization is being done. This document runs down the items of the toolbox that l20n offers to localizers and programmers. Simple examples that build on each other make up the first part, and the second part will show how those tools are put to use to implement some patterns that are hard in current l10n infrastructures.


L20n is a localization format and an API that is aiming at remodeling the way developers internationalize their code and how localization is being done.
The examples will be composed by the localized files, and an example API pseudo code that shows how much of the l20n logic the programmer sees.


== Goals ==
You can see the [http://people.mozilla.org/~axel/l20n/grammar.html annotated grammar] of the localized files for reference (warning, WIP).


== Proposed API ==
== Toolbox ==


* [http://people.mozilla.org/~axel/l20n/grammar.html Annotated grammar]
Starting off with the simplest "just strings" example, let's build our toolbox one by one.


=== Simple example ===
=== Simple example ===
Line 237: Line 239:




== Advanced usage cases ==
== Use cases ==
 
Now that our toolbox is complete, let's use them to attack some real life examples. This section goes by linguistic use cases rather than the concrete technical tools used to attack them.


=== Plurals and Genders ===
=== Plurals and Genders ===
Confirmed users, Bureaucrats and Sysops emeriti
2,976

edits