#16596: Tags within {% blocktrans %} blocks should work.
-------------------------------------+-------------------------------------
Reporter: | Owner: nobody
llugosch@… | Status: closed
Type: | Component: Translations
Cleanup/optimization | Severity: Normal
Milestone: | Keywords: translation
Version: 1.3 | Has patch: 0
Resolution: wontfix | Needs tests: 0
Triage Stage: | Easy pickings: 0
Unreviewed |
Needs documentation: 0 |
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Changes (by bpeschier):
* status: new => closed
* needs_docs: => 0
* resolution: => wontfix
* needs_tests: => 0
* needs_better_patch: => 0
Comment:
This seems unfeasible to do since the blocktrans has to be translated to a
gettext call with variable substitution, which means the template tag
calls should be translated in some form of variable name which wouldn't be
pretty for starters.
There is a perfectly simple
[https://docs.djangoproject.com/en/dev/topics/i18n/internationalization
/#blocktrans-template-tag mechanism] to include variables in a blocktrans
environment. The only catch is that templatetags should be able to put
their output in context to do so. A ticket for (partial) extension of this
mechanism can be found at #12104.
If you want to advocate the change in approach for blocktrans I would
recommend taking it up on the django-developers mailinglist.
--
Ticket URL: <https://code.djangoproject.com/ticket/16596#comment:1>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
