Django templates stripping spaces?


I'm having trouble with Django templates and CharField models.

So I have a model with a CharField that creates a slug that replaces spaces with underscores. If I create an object, Somename Somesurname, this creates slug Somename_Somesurname and gets displayed as expected on the template.

However, if I create an object, Somename Somesurname (notice the second space), slug Somename__Somesurname is created, and although on the Django console I see this as <Object: Somename Somesurname>, on the template it is displayed as Somename Somesurname.

So do Django templates somehow strip spaces? Is there a filter I can use to get the name with its spaces?

10/1/2014 3:06:48 AM

Accepted Answer

Let me preface this by saying @DNS's answer is correct as to why the spaces are not showing.

With that in mind, this template filter will replace any spaces in the string with &nbsp;


{{ "hey there  world"|spacify }}

Output would be hey&nbsp;there&nbsp;&nbsp;world

Here is the code:

from django.template import Library
from django.template.defaultfilters import stringfilter
from django.utils.html import conditional_escape
from django.utils.safestring import mark_safe
import re

register = Library()

def spacify(value, autoescape=None):
    if autoescape:
    esc = conditional_escape
    esc = lambda x: x
    return mark_safe(re.sub('\s', '&'+'nbsp;', esc(value)))
spacify.needs_autoescape = True

For notes on how template filters work and how to install them, check out the docs.

4/13/2009 7:52:30 PM

Django sees the object internally as having two spaces (judging by the two underscores and two spaces in the repr output). The fact that it only shows up with one space in the template is just how HTML works. Notice how, in the question you just asked, most of the places where you entered two spaces, only one is showing up?

From the HTML4 Spec:

In particular, user agents should collapse input white space sequences when producing output inter-word space.

As S.Lott suggested, you can verify that my guess is correct by adding debug logging, or using the Firebug plugin for Firefox or something similar, to see exactly what's getting sent to the browser. Then you'll know for sure on which end the problem lies.

If multiple spaces are really important to you, you'll need to use the &nbsp; entity, though I don't know offhand how you'd get Django to encode the output of that specific object using them.

Licensed under: CC-BY-SA with attribution
Not affiliated with: Stack Overflow