Application names i18n in the admin app broken

[Ramiro Morales]

Having

{% blocktrans with app.name as name %}{{ name }}{% endblocktrans %}

as we currently do in some admin templates shows a decision has been made to allow developers the ability translate application names.

Problem is this feature was DOA (r3270, django/contrib/admin/templates/admin/index.html, similar template code was copied since then to another file: r8474, app_index.html)

See relevant ​django-users and ​django-i18n threads for the details.

The attached patch implements as a fix the awkward manual steps needed to workaround this bug outlined by the user patrikk in the first thread, plus the following enhancements:

• index, app_index: Moved the markup-as-translatable of app names from the template to the view code so the translators aren't forced to translate a second title()'d version of every app name.
• Consistent use of the capfirst filter on the app names in the breadcrumbs of the different views.
• Don't touch base_site.html in order to provide for translatability of the app name in the <title> HTML tag for the application-specific model list view. Instead, implement the needed change in the relevant view (app_index) (replacing a "%s administration" msgid with a more translator-friendly "%(app_label)s administration" one in the process). This will spare translators the need to translate both a "<appname>" and a "<appname> administration" literals.
• Extend above fixes to other templates that also need them (delete_confirm.html, object_history.html)

Notes to reviewers:

Note 1: This patch has nothing to do with the decision of how we will allow the app name metadata to be specified and marked as translatable in the app itself, that seems to be a new feature I'm sure is being dealt with in other tickets. This ticket is much less ambitious: it's about fixing an old internationalization bug in the presentation of that information (irrespective of its origin in the backend) in the admin contrib app.

Note 2: The change_form.html template ran the app label through the escape filter. This has been dropped because it seems inconsistent with what is done in rest of the templates, the app name isn't end user-provided content so the risk of being abused for XSS seems low.

Note 3: There seems to be some inconsistency on how the app name is a) .title()'d for the name that appear in the caption of model tables (index and app_index views) and b) |capfirst'd for use in HTML title and breadcrumbs. This has been left untouched to avoid introducing a backward incompatible change.

Note 4: A further enhancement would be to move presentation-related munging (like calling .title() and/or capfirst() in view code) from views to templates if/when #5972 gets committed but meanwhile this fix can solve this bug now with the tools we have at hand now.

Several of the problems exposed above had already been reported in #9273.

[Ramiro Morales]

(made description more clear)

[Ramiro Morales]

Patch updated to trunk post-bulk-edit and post-r10234

[Ramiro Morales]

Updated patch also extends fixes to two recently added templates: delete_selected_confirmation.html (added in r10121) and change_password.html (added in r10234)

[Ramiro Morales]

Patch with some fixes to the patch iself

[Ramiro Morales]

Patch updated to trunk as of r11581

[Ramiro Morales]

Updated ticket description.

[Ramiro Morales]

Patch updated to r12157

[James Bennett]

I know Adrian put that bit into the template, but other than that we've never officially supported translation of app names, and that's really a much larger problem which should be dealt with all in one go rather than piecemeal in tickets like this one. So I'm going to punt it to 1.3.

[Ramiro Morales]

Patch updated to r12676 simplify fixes taing in account fixed made in r12472.

[Julien Phalip]

I agree with ubernostrum that this is part of a much larger problem. This needs at least a lot more discussion and therefore has now no chance to make it to 1.3.

[Jannis Leidel]

I'm inclined to call this at least related to #3591, worked on in the app-loading GSoC branch.

[patchhammer]

10436-app-name-translation-in-admin-r12676.diff fails to apply cleanly on to trunk

[Jacob]

Milestone 1.4 deleted

[Ramiro Morales]

Patch updated to trunk as of now

[Ramiro Morales]

I've attached an update patch for review. I intend to commit it in a couple of days.

[Ramiro Morales]

In [17378]:

Fixed translatability of application names in admin app.

Also, made usage of the filter template tag consistent in some
breadcrumbs elements across the different admin templates.

Fixes #10436.

[Jannis Leidel]

I'm not sure if that's the correct approach, there is no easy way to actually mark an app name for translation, so this would only be a work around at best, an anti-pattern at worst. In other words, I would have vetoed this approach, to be honest, in favor of the app class approach of #3591.

[Ramiro Morales]

In [17389]:

Reverted [17378] until a public API is available for application labels.

This will allow to solve the i18n of such labels in a more holistic way
without the need to introduce temporary, undocumented mechanisms to
translate them.

Refs #3591, #10436

[anonymous]

see #15810, similiar aproach using .title which can be translated

[paramburu]

I've started a discussion about this topic on the Django Developers google group. I would appreciate your opinions on how to keep this moving forward because I believe it has to be implemented some way as soon as possible but I don't want to make the wrong decisions.

​https://groups.google.com/forum/?fromgroups=#!topic/django-developers/7f0gKen2ces

Thank you in advance.

[Aymeric Augustin]

1.7 contains a proper solution to this issue, based on the app-loading refactor (#3951).

See also b80a8357d683b9a04a14ff46b1a132ad480e8a61.

[Aymeric Augustin <aymeric.augustin@…>]

In 6e3ca6507cd0a431d63924a708c39f6faa21341b:

Used app_config.verbose_name instead of app_label|capfirst.

An admin view performed the capitalization in the template, unlike all others.

Refs #10436.