Thank you for replies, Malcolm!
Since the beginning every  .py in my project begins with
# -*- utf-8 -*- .  Also, I tried to putting < u > in front of
strings,
but it didn't help.
Anywhere, I will review all my code, according to your advices.
I am agree with you, the cause of problem is not in Django. Django
rules!-)
Thanks again!

On Nov 25, 4:16 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> On Mon, 2008-11-24 at 12:19 -0800, oleg wrote:
> > Thank you, Malcolm!
> > Really, I'm using GAE, but it is patched to django 1.0.2. So, the
> > truth is outhere ^_^
>
> No, the problem could still very well be with App Engine. A lot of the
> support required to handle Unicode transparently is part of the backend
> storage system (since it needs to be able to convert between unicode and
> UTF-8 and back without interference). I don't know what App Engine's
> specifications are with respect to UTF-8 strings, for example (and your
> code fragments are passing UTF-8 strings around -- or possible some
> other encoding, since you don't show the "# coding: ..." comment in any
> of the examples you're posted and non of your strings look like u"...".
>
> If you rewrote your example for Django proper (using a relational
> database as the storage mechanism), it would work. So the App Engine
> portion is significant. If I were you, I'd start by using unicode
> strings throughout (after checking the App Engine supports Unicode). If
> somebody here doesn't spot what's going on, asking on the App Engine
> forums will probably be a good next step. I can't see any
> Django-specific problem in the code you've posted.
>
> Regards,
> Malcolm
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to