Viktor wrote: > The story about non ASCII characters in slug started in #1602: urlify.js > blocks out non-English chars. > > We tested utf-8 urls against ie, opera and konqueror and they work > great. Firefox by default shows the urls urlencoded, but you can change: > network.standard-url.escape-utf8 to false > and it will show the url in original encoding. > > > So I changed the validator for the SlugField so it can accept utf-8 strings. >
could you please describe some use-cases for this feature? because for me it seems a little...strange.. the whole point of the Slug is to only contain alphanumeric (as in ascii-alphanumeric) characters + underscore + hyphen. with the utf-8 change it can contain underscore+hyphen + all unicode symbols that are considered as alphanumeric... but if you allow so many symbols, why to use a SlugField at all? why don't allow all the unicode characters? i'm pretty sure i'm missing something there... :-( gabor --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
