On Wed, Jul 7, 2010 at 8:27 AM, Russell Keith-Magee
wrote:
> On Wed, Jul 7, 2010 at 4:00 AM, C. Alan Zoppa wrote:
>> I occasionally enter special characters as HTML entities (e.g. “,
>> ®, etc.) in an object's title. I feel that slugify() would be more
>> useful if these were removed entirely fro
And sometimes I want articles inserted in my slug, but it's an unusual case.
For example, a title like 'This is the way this works' gets reduced to
'way-works', which is not very useful. But I can easily tweak the slug by
hand. I think the occasional desire to blog about HTML entities is a similar
On Wed, 2010-07-07 at 21:27 +0800, Russell Keith-Magee wrote:
> On Wed, Jul 7, 2010 at 4:00 AM, C. Alan Zoppa wrote:
> > I occasionally enter special characters as HTML entities (e.g. “,
> > ®, etc.) in an object's title. I feel that slugify() would be more
> > useful if these were removed entirel
On Wed, Jul 7, 2010 at 4:00 AM, C. Alan Zoppa wrote:
> I occasionally enter special characters as HTML entities (e.g. “,
> ®, etc.) in an object's title. I feel that slugify() would be more
> useful if these were removed entirely from the returned slug. For example:
> At the moment, a title of “Ob
I wasn't even aware there was a slugify; mine looks something like this[1]."
However, if you are passing the actual string
"“stuffhere”" to slugify(), you are escaping it too early.
It should go something like slugify(txt), escape(txt), response(txt).
This is more of a django-users matter at this
I occasionally enter special characters as HTML entities (e.g. “,
®, etc.) in an object's title. I feel that slugify() would be more
useful if these were removed entirely from the returned slug. For example:
At the moment, a title of “Object Title ” returns the slug "
ldquoobject-titlerdquo." It i
