translated strings for Firefox accounts website

Перейти к файлу

vladikoff 2b2d3d91bf fix(l10n): convert sr to sr_Latn automatically Fixes #82		2015-11-11 10:56:08 -05:00
grunttasks	fix(build): Use grunt-l10n-lint to check for valid HTML, attributes and values.	2015-09-22 10:33:25 +01:00
locale	fix(l10n): convert sr to sr_Latn automatically	2015-11-11 10:56:08 -05:00
scripts	fix(l10n): convert sr to sr_Latn automatically	2015-11-11 10:56:08 -05:00
.gitignore	fix(build): Use grunt-l10n-lint to check for valid HTML, attributes and values.	2015-09-22 10:33:25 +01:00
.travis.yml	fix(build): Use grunt-l10n-lint to check for valid HTML, attributes and values.	2015-09-22 10:33:25 +01:00
Gruntfile.js	feat(build): scan emails for invalid style attributes	2015-09-22 10:28:09 +01:00
README.md	fix(l10n): convert sr to sr_Latn automatically	2015-11-11 10:56:08 -05:00
package.json	fix(build): Use grunt-l10n-lint to check for valid HTML, attributes and values.	2015-09-22 10:33:25 +01:00

README.md

fxa-content-server-l10n

This repo (abbreviated as "L10N" in this README) contains all translated/translatable strings for the fxa-content-server repo (abbreviated as "SOURCE"). It contains an exact copy of the locales/ directory from SOURCE, and nothing else (except for this README).

The moz-verbatim translation team works with this L10N repo, pushing changes into it any time they like.

On a regular basis, somebody on the SOURCE committers team copies everything from L10N into SOURCE/locale/, reviews the changes, then commits and pushes SOURCE. This makes the new translated strings available to SOURCE users, provides a clean (single-commit) revision history, and prevents non-locale/ changes from leaking from one repo to the other. The SOURCE repo contains a script (scripts/import_locale) to perform this update.

On a (different) regular basis, a SOURCE committer will update in the other direction. This starts with running the SOURCE repo's grunt "l10n-extract" task, which updates the *.pot files in SOURCE. The committer then copies the *.pot files from SOURCE into a checkout of L10N. Then they run ./scripts/merge_po.sh in L10N, which updates the *.po files in L10N. Then they should commit and push to L10N. That will update the set of translatable strings for the l10n team to work on.

Dependencies

Install gettext.

OS X:

brew install gettext
brew link gettext --force # brew does not link the tools into /usr/local. Force the link.

Ubuntu: sudo apt-get install gettext

String extraction

Source strings are extracted from the fxa-content-server and fxa-auth-mailer repos.

The process to extract strings:

Make sure you installed dependencies and msgfilter (from gettext) command is available in your shell.
Have the fxa-auth-mailer and fxa-content-server repos at the directory level as fxa-content-server-l10n.
Have all the dependencies be up to date in the fxa-auth-mailer and fxa-content-server repos using npm install.
cd into this project directory and run:

./scripts/extract_strings.sh --mailer-repo ../fxa-auth-mailer --content-repo ../fxa-content-server --l10n-repo . TRAIN_NUMBER

where TRAIN_NUMBER is the train you are cutting strings for.

Submitting Translations

Please find your locale on Pontoon - Firefox Accounts or Verbatim - Firefox Accounts. Follow the instructions on those sites to submit your translations.