Malcolm Tredinnick wrote:
>
> Although I have not used non-ISO-8859-1 storage much at all, I know that
> there are some people around who have been using it for a while now
> quite successfully, so almost all of the problems are easily solvable
> with current Django code. One day I hope to find time to play some more
> with this so that I'll know all the tricks, but at the moment I'm not
> the expert on the "how" side of things.
>
the simplest way (currently) is to go the all-utf8 route. have
everything in utf-8 (page templates, database etc.)
but the problem with simpleTAL seems to be that it expects the strings
to be unicode-strings.
so you will have to do some conversion.
if you build your Context "manually", then it's quite easy.
simply convert every string into unicode.
with something like " context[u'username'] = user.username.decode('utf-8')"
(i've never used simpleTAL, so take this example as pseudocode)
on the other hand, if you are using django models in the context, then
it's going to be harder.
one thing you might try to do is to create a wrapper object.
create a class that wraps around the model instance, and does the
unicode-conversion for you. something like:
==========================
class UnicodeProxy(object):
def __init__(self,model):
self._model = model
def __getattr__(self,name):
return getattr(_model,name).decode('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 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
-~----------~----~----~----~------~----~------~--~---
