L20n: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(→‎Feedback: Hook up issues)
 
(41 intermediate revisions by 6 users not shown)
Line 1: Line 1:
__NOTOC__
__NOTOC__
L20n (L10n x 2) is the code name for a localization architecture taking existing approaches to L10n one step further. No matter who you are (e.g., localizer, tool author, developer, or release manager), you'll be able to find information suited to your L20n-related needs here.


{{draft}}
We've broken up the content into three distinct tracks that discuss the current design for L20n, how teams and localizers can easily transition into using L20n, and its future development. These color-coded tracks point to wiki pages, blog articles, and newsgroups where you can learn more about L20n and even get involved in the discussion.


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.
For more information, [[L20n/Weekly_Update|the l20n team meets each Monday]] to discuss the progress of the project.


Check out the [[L20n:FAQ]].
<div style="display:block;-moz-border-radius:10px;background-color:#A2BFF4;padding:20px;margin-top:20px;">
<h1>L20n design</h1> {{anchor|Reps}}
<div style="display:block;background-color:#d1dffa;-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/1.0|1.0 specs]]
* [[L20n/Design|Design]]
* [[L20n/Characteristics|Characteristics]]
* [[L20n/Features|Features]]
* [[L20n/Toolchain|Toolchain]]


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
===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]
* [http://informationisart.com/4/ Syntax changes to data types]
* [http://informationisart.com/5/ Media queries with globals]
* [http://informationisart.com/6/ Default values and local entities]


# software authors (coders)
===Other===
# localizers
* [http://groups.google.com/group/mozilla.tools.l10n Discussion on L20n design]
# localization tool authors
* [[L20n/Documentation|Documentation plan]]
<br />
<br />
<br />
  </div>
</div>
</div>


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.
<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;">


== Features ==
===Wiki pages===
The [[L20n:Features]] page details on some of the features of the proposal, such as
* [[L20n/Background|Background]]
* [[L20n/Control flow|Control flow]]
* [[L20n/Workflow|Workflow]]
* [[L20n/Toolbox|Toolbox]]
* [[L20n/Examples|Examples]]
* [[L20n/HTML|L20n for web apps]]


* developed in the open
===Blog===
* clear separation between application logic and localization framework
* [http://informationisart.com/3/ An intro to L20n]
* supports both plural and grammatical forms
* [http://diary.braniecki.net/2011/03/24/l20n-gets-tangible/ L20n becomes tangible]
* not bound to a particular implementation language
* [http://blog.mozilla.org/l10n/2012/03/15/l20n_next_stage/ Next stage of L10n]
* support specify fallback language for non-localized strings
* [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>


== Background ==
<div style="display:block;-moz-border-radius:10px;background-color:#F88017;padding:20px;margin-top:20px;">
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.
<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/Tracking|Bug tracking]]
* [[L20n/Requirements|Requirements]]
* [[L20n/Issues|Issues]]
* [[L20n/Roadmap/Next|Next release]]


== Control flow ==
===Blog===
The [[L20n:Control flow]] article explains how the flow of control differs in this proposal, compared to existing systems.
<br />
<br />
<br />
===Other===
* [http://groups.google.com/group/mozilla.tools.l10n Discussion on future of L20n]
<br />
<br />
  </div>
</div>
</div><br />


== Feedback ==
Feedback on this proposal is best directed to the [news://news.mozilla.org/mozilla.dev.i18n mozilla.dev.i18n] newsgroup, which is also available on [http://groups.google.com/group/mozilla.dev.i18n Google groups] or as a [https://lists.mozilla.org/listinfo/dev-i18n 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.
[[category:L20n]][[Category:L10n]]
 
[[category:L20n]]

Latest revision as of 10:58, 27 April 2013

L20n (L10n x 2) is the code name for a localization architecture taking existing approaches to L10n one step further. No matter who you are (e.g., localizer, tool author, developer, or release manager), you'll be able to find information suited to your L20n-related needs here.

We've broken up the content into three distinct tracks that discuss the current design for L20n, how teams and localizers can easily transition into using L20n, and its future development. These color-coded tracks point to wiki pages, blog articles, and newsgroups where you can learn more about L20n and even get involved in the discussion.

For more information, the l20n team meets each Monday to discuss the progress of the project.

L20n design

Easy L10n to L20n transition

Future of L20n


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