Introduction
Translation manager and helper for Plone CMS / LinguaPlone sites.
Features
Force admin language: Useful e.g. for when admin needs to work with languages they are not familiar with. Very useful for strange languages (from western point of view) like China, Japanese or Russian. You can set this language in the control panel.
Translations Manager: A menu item for the admins in the user menu. This allows you to batch enter translated content and quickly get overview what contents still needs to be translated.
Notes
Admin language behavior
By default the forced admin language is handled by overriding language when doing look-ups for plone and collective.* gettext translation domains. The logic here is that these language strings are used by the management interface.
The actual language is not switched in any point: changing the language itself would cause site behavior differense in folder contents, search and other content listing views making administrative tasks impossible.
Translation manager
The Translation Manager is effective in the current folder and all its childred: if you have a site with a lot of content you might want to invoke Translation Manager one folder by at the time and not in the site root due to speed issues of locating translated content.
1.2 (2014-08-12)
Add buildout and missing dependencies [laulaz]
1.1 (2013-09-20)
Add missing MANIFEST [fulv]
1.0 (2013-09-20)
Italian translation [giacomos]
Added missing dependency to Products.LinguaPlone [giacomos]
French translation [laulaz]
Fixes (grok CodeView is now View, protect settings and other minor things) [laulaz]
Basque and spanish translations [erral]
i18nize the product [erral]
Log errors instead of throwing RuntimeError [erral]
Changes to work in a given context instead of site root [erral]
Initial implementation [miohtama]
Metadata
Release files for silvuple 1.2
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 |
|---|---|---|---|---|
| silvuple-1.2.zip | 27.6 kB | Without provenance | Details for silvuple-1.2.zip |
Release files / silvuple-1.2.zip
| Download URL | silvuple-1.2.zip |
|---|---|
| Size | 27.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7df9cbd712c8281d058516f6f052662c3a711f2cc5f84a971c8376a0687ac69f
|
|
BLAKE2b-256 checksum How to use checksums |
a1ddecc29818f3b7c657910a1043e1b32b62d1c4cff1111eead5179c6223c37b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for silvuple 1.2
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.