L10n:Localization Process: Difference between revisions

Jump to navigation Jump to search

L10n:Localization Process (view source)

Revision as of 18:05, 1 May 2007

2,980 bytes removed ,  1 May 2007
→‎START
Line 24: Line 24:




==START==
Our common (Mozilla and Localizers) objective is to get a community formed and launch a new language/locale.


We all start here:
(A) message from localizer to volunteer and/or a request to localize Firefox into a specific language.
The decision process (set of questions we go through) that factually happens in this stage is this:
1 - Assess the merits of the language, in particular, in terms of population and linguistic. Are there new users to be reached by adding this language that we can't reach with existing languages, or will there likely be an active user community forming around this language? (Axel/Pascal handle this), if the language is considered contentious by for example, linguistic scholars, then we say "no" to the localizer and we should suggest they work to create a language pack^^ or ship a variant of an existing build.^
*^ closest examples of this are en-CA and en-ZA
*^^ we can offer hosting the language pack in CVS/AMO (not shipped.locales), however this is l10n-drivers team contentious and is a conversation that still needs to be addressed, the issue for all language packs is that they break minor updates; we need help from Smedberg (see bug 334136)
2 - if yes, check if there is a team that exists that you can join
3 - if no, evaluate the kind of skills you want to use (see more on this below),  and what you need to continue (Axel does this in direct contact with localizer go to B for new suggestions)
Implications for Mozilla
* Decision to what extent we can give Localizers support
Implications for Localizer
* determining if you will operate as either an individual or team (often times teams are funded by local government initiatives)
(B) Mozilla then needs to get informed (or enhance our understanding) about the existing community and communicate the full set of skills required to be successful to localizers
Implications for Mozilla
* (Mic TO DO): Provide a documented description of full set of skills required:
**1-translation of web and client application content (this is considered a P1 to be a successful locale)
**2-people with engineering skills and people testing skills (P1)
**3-community development skills (P2)
**4-marketing and PR skills (P2)
**5-support (P3)
Implications for the Localizer
* Communicate the kind of work you'd like to do i.e.,your self-evaluation of your skill set, and where you are for a particular language in terms of all that's needed to support a new language
(Mic) TO DO cont'd:
provide a set of documentation and graphical image to support this:
*- small pages
*- heavily interlinked
*- the graphical image should depict
*- with starting point being diagram or something similar depicting skill sets and how they can leverage other sources for support (other locales, communities)
* Need better job of describing community network that's needed
**- best practices for building out skills in each area
**- figure out likely places for recruiting e.g., University, other?


==MIDDLE==
==MIDDLE==
Mic
1,035

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/55762"

Navigation menu