On Sun, 2006-08-20 at 07:15 +0200, Julian 'Julik' Tarkhanov wrote: > > On 17-aug-2006, at 1:08, Bill de hÓra wrote: > > > like wanting to serve utf8 rss feeds, but have latin1 come > > in and out of mysql. > > Might seem very extreme, but I would love to chime in. Maybe it would > be wise to go even further, whereby: > > 1. Hardcode Django to output and input UTF-8 as the most useful for > interop
Huge -1. This stuff (output encoding) has to be configurable, it's the way the Internet works. Sure, there are a bunch of cases where the specs will be inconclusive or ignored, and then we will need to make inspired choices, just like every other data-consuming, network-based application. But the whole planet has not standardised on UTF-8 and with valid reasons. It's also not that hard to get right, albeit fairly fiddly. You identify the interfaces between external data and Django and do the conversion to unicode as soon as you can. That's the process Gabor is going through at the moment. Metaphorically cutting off both our arms so that we appear more aerodynamic is probably not a gain worth making. > 1a. Any case where the developer might expect different input (for > instance almost all OPML files are still exported as ISO due to > idyosyncrastic way Radio worked back in the day) has to be known to > him and handled explicittly > 1b. Honor the charset headers sent in the request for transcoding > 1c. Allow everyone who wants to output other charsets to cry and perish. > 2. Stick the utf-8 output charset anywhere where it's possible > (headers, page head...). Since non-UTF-8 encodings are the norm in a lot of East-Asian locales (both for cultural and technical reasons), this isn't going to work. > 5. Internally, work with unicode strings exclusively (after > transcoding the request and the template). Response should be python > unicode as well up until the moment it gets sent out. That's the idea. [...] > I know, it seems so nice to be liberal and allow people to choose > their encoding but just too many situations prove that to be the > Wrong Choice. Th combined citizenry of China, Japan and South Korea thank your for your input, but respectfully point out that you are mistaken. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
