On 12/23/06, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
Yep. If you haven't seen it, Wikipedia has excellent coverage of unicode, including utf-8: http://en.wikipedia.org/wiki/Utf-8
Yeah, that's actually where I wound up reading about it. Specifically, its property of not allowing the bytes encoding one character to appear in the bytes for another character with a longer byte string.
Which basically means that the character encoding used in octet encoding for http URIs is undefined. ...In the real world, I've only ever seen characters encoded as utf-8 octets.
Well I tried it in Safari, Camino (and thus Firefox?), and IE 7. That's pretty much good enough for my purposes. Of course, it would be better if the web framework would take the initiative and do the Right Thing without me having to worry about it...
There's been a general consensus that unicodifying Django is a worthy goal, and I know some work's been done on it, though I don't see a branch for it.
Yeah, that's what I gathered and I really hope that happens. For now, I guess I'll have to go with this solution. Thanks for your help. Aaron --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
