Re: newforms.CharField now returns unicode, but how to specify encoding?

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

Re: newforms.CharField now returns unicode, but how to specify encoding?

Just as you said, all my html files are using utf-8. So it is OK at this time. But some part of our program needs to handle the data from other web site. That is, those forms are in some HTML pages (or programs) that we cannot control. They will use GB2312 encoding definitely. So we still need

Re: newforms.CharField now returns unicode, but how to specify encoding?

On Fri, 27 Jul 2007 05:42:12 -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

newforms.CharField now returns unicode, but how to specify encoding?

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