On Mon, 19 Mar 2007 12:47:23 -0400, Michel Thadeu Sabchuk <[EMAIL PROTECTED]> wrote:
> > Hi guys, > > If I have a form defined on newforms as: > > class MyForm(forms.Form): > field1 = forms.CharField(max_length=100) > field2 = forms.Charfield(max_length=100, label='custom field') > > When I render the field, the label for field1 get his first character > uppercased and becomes "Field1", the label for field2 was set by the > label keyword and this value doesn't get passed through pretty_name > function and keeps "custom field" (without the first letter > uppercase). > > I couldn't figure out if this is a bug or a design decision. > I it is a bug I can fix and send a patch. > Is it a bug? > That is by design. A custom label is just that. If you wnat your label in all lowercase, then that is possable. Whatever you type in your code is exactly how it will appear. That is complete customization. Pretty-name is just a shortcut for lazy programmers (we all are) when the default behavior is good enough. -- Waylan Limberg [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
