Hey. Yeah I just noticed that I was in the wrong forum also. Sorry
about that.
If it's possible, perhaps an administrator could move it?

On Feb 25, 1:14 pm, "patrick k." <[EMAIL PROTECTED]> wrote:
> we?re also using UTF-8 (with umlauts and special characters) and we
> don?t have any problems.
> do you use the right content-type?
> <meta http-equiv="Content-type" content="text/html; charset=utf-8" />
>
> btw, that question should go to "django-users".
>
> patrick
>
> Am 25.02.2007 um 11:59 schrieb Emil Ahlb?ck:
>
>
>
> > Hello everyone.
>
> > Recently me and a friend revived an old project, in hope that Django
> > will offer us a non-clusterf***y way to work, and it did. It's great,
> > I love it. :)
>
> > I have run into a problem though, after using google a bit for finding
> > information in the documentation I decided to turn here.
>
> > OK, so what I am doing now is to let the user register and give us his
> > real name there. Names like Friedrich or so are fine, but when there
> > are non-ANSI (correct term?) characters we're running into problems.
> > My name for example is Emil Ahlb?ck, and what it does when I enter it
> > is to cut the name at "Ahlb" and just enter that part. Both my
> > database and all my tables are set to have utf8_unicode_ci collation,
> > which should be enough I hope? Displaying UTF-8 characters are no
> > problems, I already tried manipulating the record manually.
>
> > So, how should I accomplish this? I also tried using the u'' stuff, as
> > in user_object.last_name = self.clean_data[u'last_name'], but this
> > didn't change anything.
>
> > Thanks in advance, Emil.


--~--~---------~--~----~------------~-------~--~----~
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