ppl-i18n
django-parler
| ppl-i18n | django-parler | |
|---|---|---|
| 1 | 2 | |
| 24 | 670 | |
| - | 0.4% | |
| 8.8 | 0.0 | |
| 2 days ago | about 1 month ago | |
| Python | Python | |
| MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ppl-i18n
-
What they don’t tell you when you translate your app
> Translation and localization costs money
If you have a fan base, you can leverage it to get some amount of translation done. A lot of users are happy to help the product they like get better. Granted, the quality will not be as good as the quality you get with professional translators.
The article also did not talk about the actual the translation process, which in the case of a product that is released but keeps getting updates, is not trivial.
There are tools that exists, but I personally decided to build a workflow around git, with a python scripts that generates a status of all the translations: https://github.com/jyaif/ppl-i18n#status
The downside is that contributors need to figure out how to use github to contribute. The upside is that it's free, you get auditability, versioning, and the barrier of entry may actually increase the quality of translations.
django-parler
-
What is the best way to make my website available in multiple languages?
I18n only handles static content and urls. If you need to have translatable Django models you should take a look at django-parler.
-
Translate models with parler, modeltranslate or something else?
django-parler uses a different table for the translated objects and creates a new row for every language version of an object and connects them via foreign key and a join which should scale better imho. But it has the downside that it doesn't do a fallback on a per-field basis. So if a model has two translatable fields and only one has some content in the specific language, an object in this language gets created and the other field is empty and does not gets populated with the content from the fallback language (see this issue)
What are some alternatives?
nicotine-plus - Graphical client for the Soulseek peer-to-peer network
deep-translator - A flexible free and unlimited python tool to translate between different languages in a simple way using multiple translators.
cldr - The home of the Unicode Common Locale Data Repository
Weblate - Web based localization tool with tight version control integration.
Fluent - Rust implementation of Project Fluent
django-lifecycle - Declarative model lifecycle hooks, an alternative to Signals.
Font-Downloader - Download fonts from the web!
avantpy - Python with training wheels: executable pseudocode in any language
ModelTracker - Track a model object over time and blame users
Babel - The official repository for Babel, the Python Internationalization Library
Korean - :warning: NOT MAINTAINED! Use https://github.com/what-studio/tossi instead. | A library for Korean morphology