Re: [Django] #13427: verbose_name and verbose_name_plural is untranslated on autogenerated m2m models

[Django]

#13427: verbose_name and verbose_name_plural is untranslated on autogenerated m2m
models
-------------------------------------+-------------------------------------
Reporter: russellm | Owner: ramiro
Type: Bug | Status: new
Component: Database layer | Version: SVN
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: verbose_name | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by ramiro):

* owner: nobody => ramiro
* keywords: => verbose_name
* ui_ux: => 0
* easy: => 0

--
Ticket URL: <https://code.djangoproject.com/ticket/13427#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#13427: verbose_name and verbose_name_plural is untranslated on autogenerated m2m
models
-------------------------------------+-------------------------------------
Reporter: russellm | Owner: ramiro
Type: Bug | Status: new
Component: Database layer | Version: SVN
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: verbose_name | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------

Comment (by quinode):

This does also happens for m2m with intermediate through models, when
they're used as inlines in the admin [[BR]]

The fields labels are also completely untranslated in tabular inlines, and
partially (?) in stacked inlines, where I can see that verbose_name
gettext translations for text input and textarea widgets are displayed,
but not for select widgets...


This bug does not happens at all with Generic Inlines, their app and
fields verbose_name translated labels are correctly displayed in the
admin.

--
Ticket URL: <https://code.djangoproject.com/ticket/13427#comment:5>

[Django]

#13427: verbose_name and verbose_name_plural is untranslated on autogenerated m2m
models
-------------------------------------+-------------------------------------
Reporter: russellm | Owner: ramiro
Type: Bug | Status: new

Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: verbose_name | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by claudep):

* has_patch: 0 => 1

Comment:

I've re-added the translatable strings, and encountered no failures
locally. Let's see...

[Django]

#13427: verbose_name and verbose_name_plural is untranslated on autogenerated m2m
models
-------------------------------------+-------------------------------------
Reporter: russellm | Owner: ramiro

Type: Bug | Status: closed

Component: Database layer | Version: master
(models, ORM) |

Severity: Normal | Resolution: fixed

Keywords: verbose_name | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Changes (by Claude Paroz <claude@…>):

* status: new => closed
* resolution: => fixed

Comment:

In [changeset:"68554d16761d1e3bb618686b6d66437c59940b47" 68554d16]:
{{{
#!CommitTicketReference repository=""
revision="68554d16761d1e3bb618686b6d66437c59940b47"
Fixed #13427 -- Made auto-m2m verbose names translatable
}}}

--
Ticket URL: <https://code.djangoproject.com/ticket/13427#comment:6>