Hey sorry guys, i couldn't find this post anymore!
Thanks for the answers but i've found the resolution to my problem in
the documentation, i just forgot in the beginning where it says about
{% autoescape off %}
This is the tag to use to prevent the template system from converting
"
in
"
Exa
Oops, it would actually be
title={% filter force_escape %}"{{ villa.name }}"{% endfilter %}
Sorry.
--
Alex Robbins
5Q Communications, Inc.
http://www.5Qcommunications.com/
alex.robb...@5qcommunications.com
800-747-4214 ext 913 (p)
http://www.ask5q.com/twitter/
On Thu, Feb 25, 2010 at 8:33 AM, A
I think you can do that with title={% filter force_escape
%}"{{ villa.name }}"{% endfilter %}. Haven't tried it though.
Alex
On Feb 24, 8:36 am, Federico Capoano wrote:
> Hello to all,
>
> simple question:
>
> I have the following HTML in a template:
>
>
> But it gets rendered this way:
>
>
>
On Feb 24, 2:36 pm, Federico Capoano wrote:
> Hello to all,
>
> simple question:
>
> I have the following HTML in a template:
>
>
> But it gets rendered this way:
>
>
> That is, the " entity is converted to the respective character,
> ". Very nice, but i'd need "
>
> Is there a filter or somethi
Hello to all,
simple question:
I have the following HTML in a template:
But it gets rendered this way:
That is, the " entity is converted to the respective character,
". Very nice, but i'd need "
Is there a filter or something i can use to tell the Django Template
System to render " ?
Thank
Ya see? I *knew* it was obvious ... as I already had the "Backwards-
incompatible changes" page open.
The problem was is that I was convinced it was a unicode-merge issue
so I've been up and down
http://code.djangoproject.com/wiki/UnicodeBranch#PortingApplicationsTheQuickChecklist
and
http://www.
On 12/4/07, JHeasly <[EMAIL PROTECTED]> wrote:
> it works as expected. So it seems something in the templating response
> food chain is converting the greater than's/less than's(?).
>
> What is the obvious thing I'm missing?
You're going against the strong recommendation of the Django project,
wh
Hello,
I'm missing something somewhere. Somebody please point me in the right
direction. I'm using Rev. 6865.
My view.py:
def foo(request) :
return render_to_response('classifieds/blank.html',
{
'content': "",
},
mimetype =
Am Donnerstag, 5. Oktober 2006 23:11 schrieb Ivan Sagalaev:
> Dirk Eschler wrote:
> > In theory i can just use utf-8, but what if one participant in the line
> > (os, db, browser, whatever) can't handle it?
>
> Talking about client side, only very old browsers can't handle utf-8
> (NN4 and IE4 can
Am Freitag, 6. Oktober 2006 09:48 schrieb Holger Schurig:
> > >
>
> Oh, I just noticed this with Konqueror from KDE 3.5.4: you can
> have this meta line in your base.html template as long as you
> want. When you use "./manage.py runserver", it won't be honored,
> the value from DEFAULT_CHARSET
> >
Oh, I just noticed this with Konqueror from KDE 3.5.4: you can
have this meta line in your base.html template as long as you
want. When you use "./manage.py runserver", it won't be honored,
the value from DEFAULT_CHARSET from settings.py takes
precedence.
--~--~-~--~~-
On Thu, 2006-10-05 at 18:24 +0200, Dirk Eschler wrote:
> Am Donnerstag, 5. Oktober 2006 14:22 schrieb Malcolm Tredinnick:
> > Python has an htmlentitydefs module and you can use that to convert
> > unicode characters into the appropriate HTML entities.
> >
> > Djang
Dirk Eschler wrote:
> In theory i can just use utf-8, but what if one participant in the line (os,
> db, browser, whatever) can't handle it?
Talking about client side, only very old browsers can't handle utf-8
(NN4 and IE4 can). Same goes for email clients. And even such simple and
'legacy'
Am Donnerstag, 5. Oktober 2006 16:04 schrieb Holger Schurig:
> > ä -> ä
> > Ö -> Ö
> > ß -> ß
>
> Do you really need them? Theoretically, you can simply set
>
>
>
> And then you may use those characters literally.
>
> However, I'm not a browser expert and don't know if all modern
> browsers un
Am Donnerstag, 5. Oktober 2006 14:22 schrieb Malcolm Tredinnick:
> Python has an htmlentitydefs module and you can use that to convert
> unicode characters into the appropriate HTML entities.
>
> Django does not do anything like this by default, because it assumes
> that you are
> ä -> ä
> Ö -> Ö
> ß -> ß
Do you really need them? Theoretically, you can simply set
And then you may use those characters literally.
However, I'm not a browser expert and don't know if all modern
browsers under the sun understand this.
--~--~-~--~~~---~--~-
> ß -> ß
> etc.
>
> How can i achieve this when defining a model in Django? Or is it a bad
> pratice
> and there's a better way? Sorry if this is obvious, but i can't seem to find
> a good answer.
Python has an htmlentitydefs module and you can use that to conver
Hi,
in PHP *shrug* i used to pipe user input through htmlentities() before i
stored it in a database. Basically to avoid encoding issues with German
special chars.
ä -> ä
Ö -> Ö
ß -> ß
etc.
How can i achieve this when defining a model in Django? Or is it a bad pratice
and there's a better wa
18 matches
Mail list logo
