djinn_i18n
Djinn i18n module providing overrides of djinn translations. Other than for instance Rosetta, this tool writes it’s overrides to a separate .po file that resides outside of your or other people’s sources, so you won’t get into trouble when updating source code.
The one single .po file is written to settings.PO_OVERRIDES, or if that doesn’t exist, to: settings.PROJECT_ROOT/var/locale.
Make sure to add the path to your settings.LOCALE_PATHS, like so:
LOCALE_PATHS = [PO_OVERRIDES] + LOCALE_PATHS
or:
LOCALE_PATHS = [PROJECT_ROOT + “/var/locale”] + LOCALE_PATHS
1.0.8
now supporting unicode in msgid’s as well
1.0.7
newline support in po-file msgid’s
1.0.5
added reload button on i18n index page for reloading po files in running server
1.0.4
made urls more flexible with respect to locale-name
1.0.3
Move to Django 1.6.x
1.0.1
Skip monkey patch for translations in front end for now
1.0.0
Initial version
Release files for djinn_i18n 1.0.8
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 |
|---|---|---|---|---|
| djinn_i18n-1.0.8.tar.gz | 18.9 kB | Without provenance | Details for djinn_i18n-1.0.8.tar.gz |
Release files / djinn_i18n-1.0.8.tar.gz
| Download URL | djinn_i18n-1.0.8.tar.gz |
|---|---|
| Size | 18.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
db46d2909ab6c5d80eaa785c47a28eaf82e9f99dc52a285260f377165da5f9cd
|
|
BLAKE2b-256 checksum How to use checksums |
928eb79c3ec86f68a30fc9396b7cbcfd6a9c86bbd24c7fd4dee452046bd745b3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for djinn_i18n 1.0.8
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.
