deep-translator VS django-parler

deep-translator to translate your CLI input

The API is based on the deep-translator python package (https://github.com/nidhaloff/deep-translator).

It is one tool that supports multiple translators and therefore, very easy and convenient to use.

If you want to check the code, here is the link to the repo: https://github.com/nidhaloff/deep-translator-api

For years now, I have been developing and maintaining the deep-translator package.

Feel free to check the GitHub repo here

To keep short, I contribute regularly to open source and about a year ago I started working on deep-translator (https://github.com/nidhaloff/deep-translator). Honestly, I didn't expect so much success but it amazed me that the package is being downloaded ~55k per day (statistics from PyPI https://pepy.tech/project/deep-translator).

- deep-translator: https://github.com/nidhaloff/deep-translator which has ~ 3 million downloads and being used by many people recently.

Last year I built deep-translator https://github.com/nidhaloff/deep-translator

I wanted a tool where multiple translators are integrated and where I can get translations from different sources but only using one tool. I then tried to build a cross platform mobile app using python (which is not the best language for this, I know) https://github.com/nidhaloff/Translator-pp

Probably the best project I built/started last year is the machine learning package igel: https://github.com/nidhaloff/igel

I18n only handles static content and urls. If you need to have translatable Django models you should take a look at django-parler.

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)