What browsers are you guys using to put the data in? If you're using IE6 in the admin site I was having problems with non ascii characters, and even though I'd set DEFAULT_CHARSET to be utf8 in the settings file, I still had to overwrite the base.html in admin and put a charset and content type ino the header.
That solved the problem. It seemed to me like IE6 was not picking that charset up from the settings file for form encoding. On 09/09/2007, Anderson Santos <[EMAIL PROTECTED]> wrote: > > > I had to work on my old website again to fix it, since even doing > iconv on my files and database didn't converted well. It was a pain, > and sometimes I get unicode error on my django app. I wish it could be > more easy (or less painy) to migrate apps. =) > > > > On 8 set, 06:25, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote: > > hi, > > > > this is not a bug report, because unicode upgrade is not backwardly > > compatible. When i did the upgrade, the finnish data in the site had > > problems rendering. Fortunately only one or alphabets were affected. > > For example: > > > > Jarske-Sjöstedt > > became > > Jarske-Sjöstedt > > > > retypeing the correct spelling and saving solved the problem. People > > have reported the same problem in Polish too. > > > > -- > > > > regards > > kghttp://lawgon.livejournal.comhttp://nrcfosshelpline.in/web/ > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
