On 28 Jun 2006, at 14:43, Andrey Golovizin wrote: > Unicode awareness may seem not a big issue for English-speakers > (for whom > plain ASCII is perfectly enough :)), but for others (like me) it's > of crucial > importance.
I don't think that's true. On today's Web there's no guarantee at all that you won't get comments (for example) posted by someone with a non-ascii character in their name. If you want to consume data from other services (RSS feeds are a particularly good example here) character encoding stuff is also bound to turn up. I seem to remember that last time people looked at unicode with Django one of the sticking points was database stuff - some of the adapters are unicode-string aware, others choke and burn. That shouldn't be an insurmountable problem though, it would just require a bit more logic in the database adapters. If we're going to add unicode support it really should happen before 1.0. One point that's worth considering is how much of a marketing coup out-of-the-box unicode would be, especially in comparison to Ruby and Rails, neither of which are very good at this stuff. As far as engineering goes, developing a water-tight test suite seems like a critical component for confidently adding unicode support. Cheers, Simon --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
