#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
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* owner: aaugustin =>
* status: assigned => new
* stage: Accepted => Someday/Maybe
Comment:
For the record, I didn't use that approach, I recommended using Jinja2
instead.
It's increasingly unclear to me that this is a problem that needs solving.
I'll leave the ticket open because 1.8 has been released only recently.
However I don't plan to work on it and I won't be surprised if it ends up
as wontfix.
--
Ticket URL: <https://code.djangoproject.com/ticket/24167#comment:3>
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.3acefe385575215dd9a67d2cae346cc2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
