#24167: Backend-agnostic template internationalization
-------------------------------------+-------------------------------------
Reporter: aaugustin | Owner:
Type: New feature | Status: new
Component: | Version: master
Internationalization |
Severity: Normal | Resolution:
Keywords: multiple-template- | Triage Stage:
engines | Someday/Maybe
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by prestontimmons):
I wonder how many people using Jinja2 with Django use Babel? The django-
jinja library, at least, takes the approach of overriding the makemessages
command instead.
Personally, I've found Babel much less constrained than makemessages when
the translation workflow requires anything custom, e.g. multiple domain
files, files that shouldn't automatically remove obsolete strings,
combining po files from multiple apps from a single repository into one,
only extracting pot files, etc. These are situational, but with Babel
there's minimal retooling necessary if you want to do it. The same can't
be said for makemessages.
--
Ticket URL: <https://code.djangoproject.com/ticket/24167#comment:6>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.b19b40dbd5774ee46d66d43fcba5405d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
