Bjorn, if you read my first messages and specially my patch #3370, you find that I made a suggestion that if the guys want to move to unicode they better drop all native encodings support and so does my patch. Then people started to answer me that this is wrong. And at the moment noone is able to explain the whole thing and answer my quesions: 1. how do they want to support templates and python code (views/ scripts) in native encodings if django itself would be all in unicode. The only way i see is to encode/decode everything at programmer's end and this means for me no native encodings support at all. 2. how do they want to support legacy databases if db connection speaks unicode
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
