DRAFT — DRAFT — DRAFT — DRAFT
Registering a Mozilla L10n project
Mark Tyndall, MLP-Staff
newsgroup discussion /
mailing list
Mozilla Localization Project Staff
If you want to register as an official Mozilla L10n team, follow these steps:
Prerequisites
-
What you need to get started:
- Check to see if there's already a team registered to localize
your intended product (Firefox,
Thunderbird or the
Application Suite).
- Find the code you need to use. You may need only a
language
code; alternatively, you may need
language
+ country
+ dialect
codes. Please use the shortest codes possible.
We are currently generalising and simplifying the codes in use:
- Simplifying: For languages that are not region-specific
(ie, they do not vary according to where they are used), use only
the
language
code.
Examples:
- German:
de
- French:
fr
- Italian:
it
- Current practice: For languages that vary in different
regions, use
language-country
code.
Examples:
- English:
en-GB, en-US
- Spanish:
es-ES, es-AR
- Generalising: For languages and dialects which cannot
be uniquely identified using defined
language-country
codes, we will be allowing a third
part to the code to describe the dialect, as proposed in RFC
3066; where possible, use a SIL identifier. Otherwise, simply
describe the dialect in 3-8 characters (matching the
RegExp
/[A-Za-z]{3,8}/
).
However, note that rather than using x-SIL-XXX
as
the full tag, we will be using the first two parts as much as
possible (using the generic codes in ISO 639).
Examples:
- Venetian:
roa-IT-VEC
- Bavarian:
de-DE-Bavarian
- Geordie:
en-GB-Geordie
The following references should be used in constructing your code:
- Have a valid email address ready.
What to do
- These are the steps you need to take:
- Subscribe to the mailing-list mozilla-l10n@mozilla.org,
or to its newsgroup mirror netscape.public.mozilla.l10n. Note that
posts made to the newsgroup are copied to the mailing list, and vice versa.
Any important announcements will be posted here.
- File a bug
in Bugzilla - product "Mozilla Localizations", component "Registration & Management". State in the bug report:
- the product you want to localize
- the language + country code
- your contact details (name + email, web-page if available).
- For official Firefox localizations, the owner-to-be will also need to:
Questions
- Why should I register?
- Registered teams have their work hosted at mozilla.org. Registration also helps to publicise your efforts to the widest
possible audience, and prevents the duplication of effort. Official Firefox localizations are included in the CVS tree
and builds for Windows, Linux and Mac OS X are generated automatically.
- Why must I file a bug to register my team?
- Using bugzilla to track these requests means everyone can see how far along
the process is, and whether any further information is required from the new team.
- I filed a bug, and nothing's happened. Is anyone there?
- Yes, but the localizers are all volunteers, devoting what spare time we can to this. Before
you get too annoyed, make sure it's not a major holiday, or it's not just
before a big mozilla.org product release.
If there's been a very long period of inaction, then ask mlp-staff@mozilla.org,
or in n.p.m.l10n
DRAFT — DRAFT — DRAFT — DRAFT