#34567: slugify template filter with allow_unicode
---------------------------------+--------------------------------------
Reporter: benjaoming | Owner: tuxo
Type: New feature | Status: closed
Component: Template system | Version: dev
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
---------------------------------+--------------------------------------
Comment (by benjaoming):
> Duplicate of #8391.
Thanks Mariusz, I did look at that issue, and I should have noted it in
the description - but ''I think'' #8391 is from before
django.utils.text.slugify existed and provided allow_unicode. The previous
issue was mostly about the complex area of mapping one character to
another - allow_unicode=True doesn't want to map anything AFAIK.
> Also, the current thread is to keep Django a core framework, not
providing every utility which might be useful.
That's fair. The functionality is already implemented in django.utils.text
- so this is only a proposal to expose the keyword `allow_unicode`. But
yeah, exposing it will of course lead to more usage.
I was particularly intrigued by the fact that I had introduced bugs in my
codebase because I used `|slugify` without considering its affect on
translated versions.
> You can start a discussion about #8391 on DevelopersMailingList if you
don't agree.
That's a nice page <3 I have been "WONTFIX'ed" :) I don't feel like having
a discussion on this topic. I tried to write a topic for the forum, but it
became disproportionate -- adding the keyword to the template filter is
both very easy to implement in Django defaultfilters, it's also very easy
to port my own boilerplate around between projects. If it cannot be a
quick yes/no, then I think leaving it aside is better.
--
Ticket URL: <https://code.djangoproject.com/ticket/34567#comment:3>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018823ced49f-d9e9ed30-894e-42f8-a425-307a148d0524-000000%40eu-central-1.amazonses.com.
