Victor Ng wrote: > Hi all, > > The unicode problem seems to creep up in this list a lot, so here's > what I've done to solve my problems. > > My particular problem is that I need to be able to deal with Unicode > data in the URLs as well as the regular request GET/POST data. > > This is a piece of middleware that I'm using to force all incoming > data to be UTF-8. If you also add in a meta tag in your head section > of your template to declare utf-8, I think IE will actually do the > right thing and not do it's weird charset guessing. >
hi, well, from my experiences, the most important thing is the content-type http header. if you explicitly tell there the charset, then the browser will use that, and completely ignore the charset-specification in the html file. also, may i ask, why such a paranoid way of working with GET/POST? because (also, only my experience, no big testing), the browsers submit their form-data in the charset in which the page containing the form was. so if you send to the browser an utf-8 page, it's submitted data is going to be utf-8. gabor --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
