One issue i have with new forms is that there is no detail/description
space for the forms, it would be really useful, since at the moment,
rather than being able to use the automatic generation methods, i have
to write custom templates for each form with the labels in (or use an
ugly hack to pull the information in).

Adrian Holovaty wrote:
On 12/5/06, Ivan Sagalaev <[EMAIL PROTECTED]> wrote:
> Adrian Holovaty wrote:
> > This is an interesting problem. That template fix would be OK by me,
> > but it's sort of a hack. I think we're going to run into similar
> > issues with Form.__str__() returning a Unicode object. Maybe, as you
> > suggest, Form.__str__() should return a bytestring according to
> > DEFAULT_CHARSET, and we could add a Form.__unicode__() that would
> > return it as Unicode.
>
> +1
>
> This will work until unicodification when we could get rid of __str__
> version because the whole template will be processed as unicode anyway.

OK, I've made the change in newforms [4163]. I also applied Gabor's
patch to make the template system handle objects whose str() returns a
Unicode object with non-ASCII characters [4161]. This is coming along
nicely!

Adrian

--
Adrian Holovaty
holovaty.com | djangoproject.com


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django 
developers" group.
To post to this group, send email to django-developers@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-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to