wagtail-localize-git
This plugin enables translating Wagtail content using a PO files in a git repository.
It works by committing source content into the repository then polling it for updates. When the PO files are translated, this will automatically create translated pages in Wagtail.
This is useful for when you are using external translation tools for translating your Wagtail content. Currently, this plugin supports Mozilla's Pontoon, but PRs are welcome for other translation tools!
Installation
This plugin requires Wagtail 2.11 with internationalisation enabled and Wagtail Localize.
Install both wagtail-localize and wagtail-localize-git, then add the following to your INSTALLED_APPS:
INSTALLED_APPS = [
...
'wagtail_localize',
'wagtail_localize.locales', # Replaces 'wagtail.locales'
'wagtail_localize_git',
...
]
Then set the following settings:
WAGTAILLOCALIZE_GIT_URL - This is a URL to an empty git repository that wagtail-localize-git will push source strings to and fetch translations from.
WAGTAILLOCALIZE_GIT_CLONE_DIR - The local directory where the git repository will be checked out.
Synchronisation
Once this is configured, you can use the sync_git management command to push/pull changes. This management command should be set up in your server's crontab to run often (preferably, every 10 minutes).
How it works
This plugin uses wagtail-localize to convert pages into segments and build new pages from translated segments. wagtail-localize provides a web interface for translating these segments in Wagtail itself and this plugin plays nicely with that (translations can be made from the Wagtail side too).
Pages/snippets are submitted to the git repo when they are submitted for translation from the default locale. Pages authored in other locales are not supported yet.
Metadata
Release files for wagtail-localize-git 0.11.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| wagtail-localize-git-0.11.0.tar.gz | 23.0 kB | Without provenance | Details for wagtail-localize-git-0.11.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| wagtail_localize_git-0.11.0-py3-none-any.whl | Python 3 | none | any | Details for wagtail_localize_git-0.11.0-py3-none-any.whl |
Total release size: 51.5 kB
Release files / wagtail-localize-git-0.11.0.tar.gz
| Download URL | wagtail-localize-git-0.11.0.tar.gz |
|---|---|
| Size | 23.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
63c7c18abb3f214d63c8939e07296f682ccf78dcbbf97ebe42b90be586beb85f
|
|
BLAKE2b-256 checksum How to use checksums |
8ad441a8bbd2a6e5329579aff90dbce862f0eeefd725ae0e3515462c872fc76d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.5.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.57.0 CPython/3.9.9
|
Release files / wagtail_localize_git-0.11.0-py3-none-any.whl
| Download URL | wagtail_localize_git-0.11.0-py3-none-any.whl |
|---|---|
| Size | 28.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e3ff60c023468c64ac9760e077e01028c4a2627fe2b2d80064a1d1fbc399220a
|
|
BLAKE2b-256 checksum How to use checksums |
df960a41e5f8b89a17aba8033fa4b113e1cf14544340e294695389532c39270b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.5.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.57.0 CPython/3.9.9
|
Security for wagtail-localize-git 0.11.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.