Register | Log in

Mozilla.com

  1. MDC
  2. Main Page
  3. What every Mozilla translator should know
Table of contents
  1. 1. Mailing lists and other resources
  2. 2. When you have a problem
  3. 3. Useful Tools
  4. 4. CVS
    1. 4.1. Mozilla Cross-Reference
    2. 4.2. Bonsai
  5. 5. Bugzilla, the bug-tracking system
  6. 6. Tinderbox
  7. 7. QA (Quality Assurance)

What every Mozilla translator should know

l10n stands for localization = l + another 10 letters + n

Mailing lists and other resources

There are several mailing lists to keep the track of what's going on, which are available as newsgroups, as well, both on news.mozilla.org and Google groups:

The main l10n list 
Also available as mozilla.dev.l10n, .l10n in short. Discussion about localization take part here just as well as l10n-focused announcements.
Planning list 
Also available as mozilla.dev.planning, .planning in short. The Mozilla project discusses general planning and schedule questions here. Discussions of interest to the general Mozilla developer community are at least notified here.
Translate the Mozilla web 
or mozilla.dev.l10n.web, we moved announcements and discussions about the translation of the Mozilla web pages to this group.

All these groups are pretty low traffic.

To keep the track of what's going on, it's also a good idea to read the Planet Mozilla L10N

When you have a problem

  • Use the above mailing lists
  • The person in charge of the Mozilla l10n is Axel Hecht (l10n at mozilla.com), Pike on IRC
  • Another interesting way of getting help is the IRC channel #l10n at irc.mozilla.org

CVS

The CVS is organized in several branches. We have the main branch called Trunk where the day to day developing work is done. When a development is started for an specific version, a new Branch is created. All the content of the trunk is copied to the branch so the developing work will be done in two parallel places: the generic trunk and the version oriented branch. When the work in the Branch is finished because the version is out, it becomes a Release.

Some branch/release names identified:

  • MOZILLA_1_8_BRANCH -> Firefox/Thunderbird 2.0 Branch
  • MOZILLA_1_8_0_BRANCH -> Firefox/Thunderbird 1.5.0.x Branch

Mozilla Cross-Reference

Mozilla Cross-Reference is a web site mirroring the content of the CVS server. Here we can easily have a look into other languages translations.

Bonsai

We can also use Bonsai to search the whole CVS server

Bugzilla, the bug-tracking system

You do need an account in Bugzilla

You should configure the account to Watch the following addresses:

This way you will receive mail for bugs affecting many or even all locales.

When you create a bug, if you want the person in charge of the l10n to follow up your bug you should CC: l10n@mozilla.com

Sometime before a release, the Branch is closed and the only way to change something is to create a bug asking for approval:

  • Do the changes in your local disk
  • Create a diff file with the changes 
cvs diff -uN > filename.diff

Product: 	Mozilla Localization
Component:	your language
...
CC:		l10n@mozilla.com
Assigned to: you
explain what you need!
Specify the branch (1.8.1 for Firefox 2, 1.8.1.1 for Firefox 2.0.1, ...)
  • attach the diff file to the bug: 
Content Type: patch
Mark the approval1.8.xxx with ? asking for approval (use the appropriate branch)
  • If you get the approval you will see who_is_ap:approval1.8.xxx+ Now, you can upload the changes approved to the CVS server. When you commit the changes you must write in the comment the Bug number, what you have changed and who has approved. For example: 
bug 12345, fix typos and resize prefwindow, a=l10n
  • As soon as you have committed, put the bug in FIXED state and write fixed1.8.xxx in the keyword field
  • You have to verify in the next build that the changes have been successful. If so, change the state of the bug to VERIFIED and write verified1.8.xxx in the keyword field

Tinderbox

In Tinderbox you can see the result of the build process. Once you have made some changes in the CVS, as soon as the next build is done you can check the Tinderbox and see if something was wrong.

When the color is green, it means that the build process has finished with no errors. In this case the resultant installable file will be available in the Mozilla FTP servers:

QA (Quality Assurance)

In order to assure the quality of a build we should make some tests using http://litmus.mozilla.org/

Languages

Page last modified 22:09, 21 May 2007 by Igartua

Tags:

Files (0)