#8391: Admin slugify function's results differ from those of slugify template
filter
------------------------------------+---------------------------------------
Reporter: bjornkri | Owner: nobody
Status: new | Milestone: 1.0 maybe
Component: Uncategorized | Version: SVN
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Comment (by Daniel Pope <[EMAIL PROTECTED]>):
I think the template filter should accept an argument, so
{{{slugify:"de"}}} might add in the German-specific rules, and so on; a
settings.py option would just choose whether that was done by default. But
it would be difficult to ensure those tables are comprehensive enough. I
note that libiconv has rudimentary support for transliteration, so perhaps
we could use their data.
Slugs and URLs are the same thing, imho.
If we can adequately provide IRIs, on the other hand, the slugify
operation can be well-defined, eg.
{{{
>>> slugify(u'Føø Bär Baß')
u'føø-bär-baß'
}}}
@bjornkri: You're still using UTF-8 encoded bytestrings. You must use
unicode strings.
--
Ticket URL: <http://code.djangoproject.com/ticket/8391#comment:12>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
