Langchecker is used to analyze all projects using .lang files as data sources. It also stores all configuration information needed to manage these repositories: which projects are supported, which files are in each project, which locales are supported for each project or file, metadata like critical status or deadlines.
Langchecker’s scripts are used to propagate changes to all .lang files, or add news ones, in l10n repositories. It also provides an API to retrieve translations, and information about coverage, i.e how many locales translated a specific string or a page, and what percentage of the l10n population that represents.
See the Useful Links at the end of the document for links to the relevant GitHub code repositories. Follow the instructions provided in each README for system requirements and instructions.
Note that the instances on the l10n community server of all products use a GitHub’s webhook to update code automatically every time the repository is updated.
For detailed information check the specific pages for each project:
These are detailed instructions for the most common tasks:
- Add locales to an existing file.
- Update an existing file.
- Add a new file to an existing project.
- Bootstrap a new locale.
- Remove obsolete files.
For documentation specific to mozilla.org, see this page.
Always work on forks of the main repository and open pull requests if you’re going to update code. Automated tests are run with Travis on each pull request to check for syntax and functional errors.
- Code repository (codename bedrock): https://github.com/mozilla/bedrock
- Trunk localization: https://github.com/mozilla-l10n/www.mozilla.org
- Production localization: https://github.com/mozilla-l10n/bedrock-l10n