-
Notifications
You must be signed in to change notification settings - Fork 2
Home
tomer edited this page Oct 2, 2014
·
6 revisions
This repository is a mirror of the Hebrew locale Mercurial repository available on hg.mozilla.org. This repository has created to ease the translation process and allow contributions from people who doesn't have commit access on Mozilla Mercurial server.
- First, make sure the repository is in-sync with hg.mozilla.org. This can be approved by asking someone who is an active contributor to the repository or checking if the latest commits on hg.mozilla.org are the same as the recent commits here.
- Know the dashboard. The dashboard contain important information about missing strings and those that are obsolete. This repository is the Aurora repository, so ideally we should have zero missing strings on fx_aurora, as well as other _aurora repositories. We may sync the repository into the beta repository (_beta) as well, in order to speed up development. *_central are nightly builds so it is unimportant to watch them as they are considered unstable (but may be synced as well!)
- Never work directly on the main repository. Instead, create a fork and work on your very own repository, so we could use the pull requests as a translation review mechanism.
- Start a clean branch on your cloned repository for every file or group of files you are planning to work on, so every Pull Request will be focused on specific task.
- Find on the dashboard the files you are planning to work on and has missing strings or missing files.
- Locate the en-US source file (see Source mapping), copy the missing strings (and the comment above it, if any) to the translation file, and translate these strings.
- When you complete, commit it to your cloned repository and create a pull request.
- Do not remove obsolete strings right away. Doing so could be harmful if we sync the repository with other repositories (i.e., these strings removed in aurora but still in use on beta).
- When merging new strings into the translation file, keep it on the same location as in the source file. You may want to use a file comparison tool (diff) with two files open side-by-side such as Meld.
- Don't keep translated and uncommitted tasks as well as committed and not PR'ed tasks open for long time, as someone else may start working on the same files, which could be causing some translation conflicts.
- Create pull request with the translated commits.
- If you get no replies in a few days, feel free to nag us in other channels. 😀
- The person that approves your files should sync the changes with the official repository.
- Changes would be reflected on the dashboard only after sync is complete, and few minutes after re-build is complete.
- Someone with sign-off permissions should sign-off the most recent good commit (on every affected product on the dashboard) in order to push files into Aurora builds.