0b69680daa
This updates compare-locales to 8.0. The major version bump is due to the changes to the json output. This also updates fluent.syntax to 0.17. Vendor in fluent.migrate 0.9. This is the first formal vendoring, the version we had in-tree wasn't released on pypi before. Differential Revision: https://phabricator.services.mozilla.com/D75127 |
||
|---|---|---|
| .. | ||
| fluent | ||
| PKG-INFO | ||
| README.md | ||
| setup.cfg | ||
| setup.py | ||
README.md
Fluent Migration Tools
Programmatically create Fluent files from existing content in both legacy and Fluent formats. Use recipes written in Python to migrate content for each of your localizations.
migrate-l10n is a CLI script which uses the fluent.migrate module under
the hood to run migrations on existing translations.
validate-l10n-recipe is a CLI script to test a migration recipe for common
errors, without trying to apply it.
Installation
Install from PyPI:
pip install fluent.migrate[hg]
If you only want to use the MigrationContext API, you can drop the
requirement on python-hglib:
pip install fluent.migrate
Usage
Migrations consist of recipes, which are applied to a localization repository, based on template files.
You can find recipes for Firefox in mozilla-central/python/l10n/fluent_migrations/,
the reference repository is gecko-strings or quarantine.
You apply those migrations to l10n repositories in l10n-central, or to gecko-strings for testing.
The migrations are run as python modules, so you need to have their file location in PYTHONPATH.
An example would look like
$ migrate-l10n --lang it --reference-dir gecko-strings --localization-dir l10n-central/it bug_1451992_preferences_sitedata bug_1451992_preferences_translation
Contact
- mailing list: https://lists.mozilla.org/listinfo/tools-l10n
- bugzilla: Open Bugs - New Bug