#8391: slugify template filter poorly encodes non-English strings
--------------------------------------+-------------------------------------
          Reporter:  bjornkri         |         Owner:  nobody
            Status:  reopened         |     Milestone:        
         Component:  Template system  |       Version:  SVN   
        Resolution:                   |      Keywords:        
             Stage:  Unreviewed       |     Has_patch:  0     
        Needs_docs:  0                |   Needs_tests:  0     
Needs_better_patch:  0                |  
--------------------------------------+-------------------------------------
Changes (by Daniel Pope <[EMAIL PROTECTED]>):

  * status:  closed => reopened
  * resolution:  wontfix =>
  * summary:  Admin slugify function's results differ from those of slugify
              template filter => slugify template filter
              poorly encodes non-English strings
  * component:  Uncategorized => Template system
  * milestone:  1.0 maybe =>

Comment:

 Sorry Malcolm, I may have subverted this ticket a little by talking about
 generalised handling of slugs, and thrown you off the scent.

 The original ticket was about a broken Python slugify filter, not a broken
 Javascript function. It was simply an observation on bjornkri's part that
 the admin javascript works better. The Python filter is not "just an aid".
 It should produce acceptably good results, which it has not done for the
 string u'bøøøø'.

 Reopening.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/8391#comment:17>
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to