>i understand the general unicode-related problems with python, i just >wanted to understand what's django specific.
Since Django is written in Python, those _are_ django specific. For example several of the template filters make use of uppercase/lowercase conversions (only interesting if you can make use of those, of course - there are languages without the concept of upper/lowercase, so users of those languages won't see any problems there). Other places are when you try to check the length of strings, to see wether they fit into some place. Or situations where you try to cut strings because of their length being too large - you could just accidentely break the utf-8 encoding by "cutting" directly into a multibyte character ... So, no, "just playing nice" doesn't allways work, there _are_ places where your code might break or misbehave due to the utf-8 encoding, even if your own code works. Because you can't allways just turn strings into unicode and feed to the Django code, as that code might do some str() call or something like it and so break on your unicode string. In most cases, though, Django will work fine - as can be seen by all those projects running already with Django, even with non-english languages ;-) bye, Georg
