[EMAIL PROTECTED] wrote: > I think the next step in the unicodeification of django is to decide where > the conversions happen. Or has this already been decided? > > I like the picture of "unicode circle of trust": everything inside the circle > is trusted as unicode strings. Everything outside has to be encoded/decoded. > It's pretty clear the database is outside, the http gets/posts are outside > too. But what about templates? What about settings/views/models? > I guess if that is decided, we can have a "unicode roadmap". I guess there > are a few people who have spare time and knowledge to help django become > unicode.
Yes this was discussed and resolved pretty much like you described: everything is in unicode except the Web and the database. The roadmap is here: http://code.djangoproject.com/wiki/UnicodeInDjango --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
