ansaurus

Question

Answer 1

A:

You shouldn't have to think about escaping in 1.0 . If you have a template

<html>
 <body>
  & == &amp; in HTML
 </body>
</html>

It should encode the & to & before printing.

If you have a variable

<html>
 <body>
  {{ msg }}
 </body>
</html>

and

def view(request) :
  msg = "& == &amp; in HTML"

if should be printed the same way.

The only time you want to do the encoding yourself is if you need to paste in raw html. Like:

def view(request) :
  msg = '<img src="http://example.com/pretty.jpg" />This picture is very pretty'

and in your template

<html>
 <body>
  {{ msg|safe }}
 </body>
</html>

Paul Tarjan 2009-07-21 07:37:57

philipk 2009-07-21 08:00:38

Well, I tried doing something like that, and it came out just fine. That being said though, my problem with my actual code is unrelated. I'm going to poke around a bit.

philipk 2009-07-21 08:06:49

Answer 2

+1 A:

Oh hardy har har,

Silly me, Google is so smart that they already escaped those chars in the XML I was parsing. Wouldn't you know it, an hour of fiddling only to realize Google outsmarted me again!

P.S. In case anyone else ever comes across a similar problem, I'm specifically referring to the XML returned when doing this sort of query: http://books.google.com/books/feeds/volumes?q=1984 , the data is already escaped for you! That being said, it does put me on edge a little bit because putting |safe in my templates will mean that if I ever get data from another source that I don't trust so much... Anyway, thanks for reading!

philipk 2009-07-21 08:12:03

ansaurus

tags:

views:

answers:

Django Double Escaping Quotes etc.

related questions