Confirm, emeritus
2,976
edits
Changes
L20n
,forking up my writings on l10n ideas.
{{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. 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.
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.
== 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.
{{Category::L20n}}
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.
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.
== 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.
{{Category::L20n}}
