Gabor Farkas wrote: > but what i don't understand, is: why is this an issue? can't we assume > that the developer knows the encoding of his own files? and if he knows > them, he should be able to easily recode them to utf-8, for example.
This is in many cases an emotional issue. Developers get used to their environment and they need a reason to change it, not a reason to leave it intact. We already allow them to have a database and web output in any encoding. Requiring template files to be in utf-8 only may look weird. > i'm personally for the one-encoding-to-rule-them-all solution btw :) Yeah, this is very appealing indeed. I think this is due to be ruled by one of our BDFL's :-). Do we actively push utf-8 adoption or support the legacy? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
