L20n: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
__NOTOC__
__NOTOC__
{{draft}}
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.
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.


Line 16: Line 13:
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.
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 color-coded tracks below divide up the topics surrounding L20n, pointing to wiki pages, blog articles, and newsgroups where you can learn more about L20n and even get involved in the discussion.
The [[L20n:Characteristics]] page details on some of the features of the proposal, such as


* developed in the open
<div style="display:block;-moz-border-radius:10px;background-color:#A2BFF4;padding:20px;margin-top:20px;">
* clear separation between application logic and localization framework
<h1>L20n design</h1> {{anchor|Reps}}
* supports all grammatical and stylistic features of languages
<div style="display:block;background-color:#d1dffa;-moz-column-gap:20px;padding:20px;margin-top:20px;-moz-border-radius:10px;">
* not bound to a particular implementation language
  <div style="-moz-column-count:3;-moz-column-gap:20px;">
* support specify fallback language for non-localized strings
===Wiki pages===
* workflow that encourages cooperation from localizers and makes localization maintenance easy
* [[L20n:Characteristics]]
 
* [[L20n/Roadmap/1.0|L20n 1.0]]
== Toolbox ==
* [[L20n/Features|List of features]]
 
* [[L20n:Design]]
One of the best ways to learn what L20n has to offer is to review the [[L20n/Toolbox|Toolbox]]. It leads you through the capabilities of L20n introducing them one by one and letting you discover the power of its semantics.
* [[L20n:FAQ]]
===Blog===
* [http://diary.braniecki.net/2012/02/27/l20n-feedback-round/ L20n feedback round]
* [http://diary.braniecki.net/2012/02/27/l20n-what-to-add-before-1-0/ L20n: What to add before 1.0]
<br />
<br />
<br />
===Other===
* [http://groups.google.com/group/mozilla.dev.l10n Discussion on L20n design]
<br />
<br />
<br />
<br />
  </div>
</div>
</div>


== Roadmap ==
<div style="display:block;-moz-border-radius:10px;background-color:#E67451;padding:20px;margin-top:20px;">
<h1>Easy L10n to L20n transition</h1> {{anchor|Reps}}
<div style="display:block;background-color:#F9966B;-moz-column-gap:20px;padding:20px;margin-top:20px;-moz-border-radius:10px;">
  <div style="-moz-column-count:3;-moz-column-gap:20px;">
===Wiki pages===
* [[L20n/Toolbox|Toolbox]]
* [[L20n:Background]]
* [[L20n:Control flow]]
* [[L20n:Examples]]
* [[L20n/Workflow]]
===Blog===
* [http://informationisart.com/3/ An intro to L20n]
* [http://diary.braniecki.net/2011/03/24/l20n-gets-tangible/ L20n becomes tangible]
* [http://blog.mozilla.org/l10n/2012/03/15/l20n_next_stage/ Next stage of L10n]
* [http://blog.mozilla.org/l10n/2012/03/29/l20n-examples-for-localizers/ L20n examples for localizers]
<br />
===Other===
* [http://l20nenv.labs.braniecki.net/static/index.html?id=example1 L20n environment lab]
* [http://groups.google.com/group/mozilla.dev.l10n Discussion on L10n to L20n transition]
<br />
<br />
<br />
  </div>
</div>
</div>


* [[L20n/Roadmap/1.0|L20n 1.0]]
<div style="display:block;-moz-border-radius:10px;background-color:#F88017;padding:20px;margin-top:20px;">
<h1>Future of L20n</h1> {{anchor|Reps}}
<div style="display:block;background-color:#FFA500;-moz-column-gap:20px;padding:20px;margin-top:20px;-moz-border-radius:10px;">
  <div style="-moz-column-count:3;-moz-column-gap:20px;">
===Wiki pages===
* [[L20n/Roadmap/Next|L20n.Next]]
* [[L20n/Roadmap/Next|L20n.Next]]
 
* [[L20n:Issues]]
== Features ==
* [[L20n:Requirements]]
 
===Blog===
[[L20n/Features|List of features]] that are debated for inclusion into L20n.
<br />
 
<br />
== Background ==
<br />
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.
===Other===
 
* [http://groups.google.com/group/mozilla.tools.l10n Discussion on future of L20n]
== Control flow ==
<br />
The [[L20n:Control flow]] article explains how the flow of control differs in this proposal, compared to existing systems.
<br />
 
  </div>
== Design ==
</div>
Read more about the essential parts for the [[L20n:Design]].
</div><br />
 
== Examples ==
If you like to look at [[L20n:Examples]], that's good.
 
For L20n-DOM bindings look at [http://zbraniecki.github.com/l20n/ those tests].
 
== Grammar ==
Find out more about the file format on the [http://people.mozilla.com/~axel/l20n/grammar.html 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 [http://groups.google.com/group/localization-20 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 ==
==  Weekly Meetings ==


[https://wiki.mozilla.org/L20n:Weekly_Meetings Each Monday, the l20n team meets] to discuss the progress of the project.
[https://wiki.mozilla.org/L20n:Weekly_Meetings Each Monday, the l20n team meets] to discuss the progress of the project.


[[category:L20n]][[Category:L10n]]
[[category:L20n]][[Category:L10n]]

Revision as of 21:28, 7 May 2012

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.

The color-coded tracks below divide up the topics surrounding L20n, pointing to wiki pages, blog articles, and newsgroups where you can learn more about L20n and even get involved in the discussion.

L20n design

Easy L10n to L20n transition

Future of L20n


Weekly Meetings

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

Retrieved from "https://wiki.mozilla.org/index.php?title=L20n&oldid=428187"