1,035
edits
L10n:Starting a localization: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
This document outlines what you should expect in order to start building a new language (in a language pack). | This document outlines what you should expect in order to start building a new language (in the form of a language pack). | ||
= Team building = | = Team building = | ||
Initially, you want to join an existing team or start a new one if there isn't one already working on your language | Initially, you want to join an existing team or start a new one if there isn't one already working on your language. | ||
* Check out the [[L10n:Teams]] list to determine whether your language is already started or not. | * Check out the [[L10n:Teams]] list to determine whether your language is already started or not. | ||
* Add yourself to a [[L10n:Teams]] wiki page that identifies you and what you're working on so people can find you. | * Add yourself to a [[L10n:Teams]] wiki page that identifies you and what you're working on so people can find you. | ||
* If you haven't already you should also get onto the IRC Channel, [http://irc.mozilla.org/ #l10n]. You will be able to get real-time help from other localizers and members of the L10n-driver team. You can also post questions or suggestions to [http://www.mozilla.org/community/developer-forums.html#dev-l10n m.d.l10n], available as newsgroup or on Google groups. In addition, you would want to have a bugzilla account as the majority of our work is started and tracked to completion in this way. | * If you haven't already you should also get onto the IRC Channel, [http://irc.mozilla.org/ #l10n]. You will be able to get real-time help from other localizers and members of the L10n-driver team. You can also post questions or suggestions to [http://www.mozilla.org/community/developer-forums.html#dev-l10n m.d.l10n], available as newsgroup or on Google groups. In addition, you would want to have a bugzilla account as the majority of our work is started and tracked to completion in this way. | ||
* Set up a communication channel for your language. You can use mailing lists or newsgroups, which many open source hosting partners [is there a link we can insert here] offer, or simply open a Google or Yahoo group. You should leave a link to this forum on the wiki page for your language, so that new volunteers and members of the Mozilla community can find it. | * Set up a communication channel for your language. You can use mailing lists or newsgroups, which many open source hosting partners [is there a link we can insert here] offer, or simply open a Google or Yahoo group. You should leave a link to this forum on the wiki page for your language, so that new volunteers and members of the Mozilla community can find it. That's important because building your localization team and a community around it, is something that will stay on your "to-do" list forever. It's the essential part of being an open source project. | ||
= Localization work = | = Localization work = | ||
Now you and your community are set up to do the actual localization work. Depending on your working habits and the size of your team, you may want to look into open source hosting offers like [http://mozdev.org mozdev.org] or [http://sf.net/ SourceForge] | Now you and your community are set up to do the actual localization work. | ||
You will want to get some central repository for your work (code, mailing lists, newsgroups, website). Depending on your working habits and the size of your team, you may want to look into open source hosting offers like [http://mozdev.org mozdev.org] or [http://sf.net/ SourceForge]. You can also just use plain files and regular backups, or set up your own P2P VCS. | |||
You should localize the Mozilla sources instead of the built files, and make your work publicly available. This is a good way to start out because it indicates you are open to new collaborators and enabling a smooth path going forward. | |||
To make your work available for users to download and test, you create a language pack, which can be hosted on AMO[insert link]. AMO offers many advantages for both you and your testers and users, starting from download capacity, and ending in automatic updates of your Add-on. | To make your work available for users to download and test, you create a language pack, which can be hosted on AMO[insert link]. AMO offers many advantages for both you and your testers and users, starting from download capacity, and ending in automatic updates of your Add-on. | ||