#26497: No Capitalization of verbose_name of model fields when Rendered by
BoundField
-----------------------------+--------------------------------------
Reporter: srkunze | Owner: nobody
Type: New feature | Status: closed
Component: Forms | Version: 1.8
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+--------------------------------------
Comment (by srkunze):
I did a quick review of the patch and opened PyCharm with a fresh Django
1.9.5 installation.
Maybe I am wrong, but it seems to me that he missed some usages of
capfirst with regards to field names. Not sure if that is intended.
AFAICS, the patch does not distinguish between auto-generated
verbose_name and user-defined verbose_name. So, the patch does not help in
this regard. However, given the patch is applied, we would need to add all
capitalized forms as explicit verbose_names. Not sure if I would like
that; especially when it works so conveniently for the German language but
it would solve the problem at hand.
--
Ticket URL: <https://code.djangoproject.com/ticket/26497#comment:8>
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/065.41dc19818dd56af633554d5d424d23aa%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
