On Fri, 2007-07-27 at 05:42 -0700, Gilbert Fine wrote: > I used django rev. 5559 for some time. After svn up today, I found > CharField's cleaned_data is unicode. I think it is a good idea. > Actually, I made this conversion in my source program. > > The only question is how to specify encoding of the string sent from > client browser? My users almost certainly using gb2312, not utf-8.
This is documented in unicode.txt in the source. Online, it is at http://www.djangoproject.com/documentation/unicode/ although that may not be linked from the front documentation page yet (adding the doc file name after documentation/ is the pattern we use, though, so it's easy to guess -- an advantage of predictable URLs). If form submission is not in the default character set, it is up to you to set the encoding in your view function each time. However, we've given you the ability to do that for just the reason you mention. We don't do anything automatically (even with "accept-charset", since it's unreliably implemented and the browser doesn't always send the right information). Regards, Malcolm > > > Thanks. > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
