On Jan 28, 2007, at 7:02 AM, ak wrote:
> 1. how do they want to support templates and python code (views/ > scripts) in native encodings if django itself would be all in unicode. `Why do you need to support it, that's the first question that comes to mind. If you have input requirements, decode on read. If you have output requirements, encode on out. > 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. AFAIK, templates explicitly should be assumed to be in UTF-8 (supported by most text editors) and decoded as such. Templates being in national encodings should raise nasty and irrecoverable errors all over the place with a proper explanation thereof. > 2. how do they want to support legacy databases if db connection > speaks unicode The database client should support dynamic encoding/decoding (all modern clients do). Not all database backends (AFAIK) properly return unicode strings, so these will have to be scrutinized. People running old clients sack themselves and do the long overdue upgrades. -- Julian 'Julik' Tarkhanov please send all personal mail to me at julik.nl --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
