On 4/14/06, James Bennett <[EMAIL PROTECTED]> wrote: > Which is a problem, because really the whole idea behind a URL slug is > to provide some useful information about the page which lives at that > URL. But a long string of URL-encoded characters doesn't convey any > more useful information than the sorts of > "index.php?ar=Q76&pqb=r33857326&bdz=efweofgh" gibberish that was and > still is so common on the Web. Given that, what is the advantage of > UTF-8 URL slugs?
I would sooner blame your setup or software for not properly supporting such links. http://ja.wikipedia.org/wiki/京都 is a perfectly valid URL nowadays and for anyone a bit versed in Japanese they would immediately recognise Kyouto. And that's why UTF-8 URLs are useful, you can keep your slugs in the language you want. For me, I use multiple languages on my weblog and would love these to be reflected in UTF-8 for every slug I use. With all due respect, the world is much larger than English. Who are we to dictate their slugs are to be encoded in ASCII only? (Heck, even my textbased browser w3m and links can open such URLs. :)) -- Jeroen Ruigrok van der Werven --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
