Good evening everybody. :) I would like to reference this ticket: https://code.djangoproject.com/ticket/26497#comment:11
It appears we stumbled over this issue as well while designing a new model form. Quoting my comment from the ticket: Would it make sense to separate concepts here? 1) *user-defined* verbose_name: Django should not touch it 2) *auto-generated* verbose_name: Django generates the verbose_name from the field's name In both cases, once the label of a form field is set, Django should only touch it (except on the designers behalf). *Deprecation phase*: a) make global capitalization optional via settings (or form variable) with True as default for status quo. b) auto-generated verbose_names are generated using a format string which can also be specified by a settings variable (or form variable). Default should result in current output (with the capitalization) c) disable global capitalization by default Does this makes sense? -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/94da855b-c159-4c17-a24f-16f843096ae7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
