hugo wrote:
i understand that django's architecture should use unicode because it's
the better way, but from the "outside"... what functionality is not
working fine with non-english characters?
currently you are up to your own to turn the
unicode strings returned from those into utf-8 bytestrings, because
otherwise the Django core will become upset. With switching to full
unicode internally, we will work much better with the standard lib,
because the standard lib already does prefer a full-unicode
environment.
thanks for the info.
i understand the general unicode-related problems with python, i just
wanted to understand what's django specific.
so if i understand correctly, if i play nice, and convert to/from
utf8-encoded-bytestring everytime i interact with django, things should
work. is this correct?
gabor
