Malcolm Tredinnick wrote: >So either we're going to end up carrying around a fairly large mapping >table in the Javascript or we need a better solution. > > Looking at what Wordpress does at the link in the beginning of this thread (http://trac.wordpress.org/file/trunk/wp-includes/functions-formatting.php) it's not that large really. Especially in javascript and python that know what unicode is and you don't need to write things like "chr(195).chr(128)" for utf-8. You can also strip half of that table with capital letters since slugs don't use them anyway.
>To put the problem into context: it's only a small generalisation to >attempt to do the same thing for mapping Japanese characters to >ASCII-based URLs. > This is a whole another issue since there is no "correct" translation from non-latin based scripts that wouldn't look plain ugly. So let's keep this issue to just "stripping accents and umlauts" without claiming an ability to produce slugs for any language. Django will become a little bit better for latin-based scripts with no changes for the rest. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
