Add translations for helps.

[bckohan]

Should make a good faith effort to provide translations for all the languages Django provides translations for.

[bckohan]

One wrinkle here is that typer adds some of the help text for (i.e. --help) - that may eventually be wrapped in gettext and if it is - how do the native python translation and django translation systems work together?

[bckohan]

Does django have translations for the common options?

[bckohan]

We will not translate error messages presented on the terminal per Django's practice. I do think translating the default CLI helps is important because the CLI interface may be used by non-devs. Consider using google translate: https://github.com/ankitpopli1891/django-autotranslate

[oliverandrich]

What is the rationale behind including it? Will it be an optional dependency? And shouldn't it be up to the project, including django-typer to supply the translation? I would use django-translate either for all of my project or not at all. But it would surprise me, if one third-party library handles it on its own.

[bckohan]

It would only be a development dependency, it wouldn't register on pypi at all. Translations would be produced at package time.

Django's stance toward translation so far as I can tell is that if it's language that only developers are exposed to the strings are not translated and if it's language downstream users are exposed to it is translated. Django does not offer translations out of the box for the helps for default command parameters. Probably because this language is thought of as in the first category. I'm not sure I agree with this. I think the CLI interface of a Django site probably falls somewhere between the developer only audience and the user audience. As such I think it makes sense to provide translations out of the box for the common parameters.