I finally nailed it !
For some strange reason my editor did not save the index.html template
in utf8.
I've reloaded both template in another editor, force to save in utf-8
and all went well.
Thanks to all for the support.
Jorge Gajon wrote:
> On 9/18/06, Phil <[EMAIL PROTECTED]> wrote:
> > I
On 9/18/06, Phil <[EMAIL PROTECTED]> wrote:
> I tried what you suggested (replace my meta http-equiv by your version)
> and it does no good )c:
Sorry to hear that Phil, I don't know what else to suggest :( It is
really weird that it works when you duplicate the content-type line
though.
Hi Jorge,
I tried what you suggested (replace my meta http-equiv by your version)
and it does no good )c:
I also checked my settings.py and there is no DEFAULT_CHARSET nor
DEFAULT_CONTENT_TYPE, so they are defaulted to uft-8 and text/html.
Thanks for the suggestion, though.
Jorge Gajon wrote:
Malcolm Tredinnick wrote:
> On Mon, 2006-09-18 at 00:22 +, coulix wrote:
> > puting DEFAULT_CHARSET to utf-8 didnt solve the Ao? != Aôut
> > Not that only Aôut orm date generation is liek this all other
> > accesnts in the template are fine.
>
> I haven't been following this thread in all
On Mon, 2006-09-18 at 00:22 +, coulix wrote:
> puting DEFAULT_CHARSET to utf-8 didnt solve the Ao? != Aôut
> Not that only Aôut orm date generation is liek this all other
> accesnts in the template are fine.
I haven't been following this thread in all its gory details, but seeing
this
puting DEFAULT_CHARSET to utf-8 didnt solve the Ao? != Aôut
Not that only Aôut orm date generation is liek this all other
accesnts in the template are fine.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django
Jorge Gajon wrote:
> On 9/16/06, Phil <[EMAIL PROTECTED]> wrote:
> > In the base.html template I added in the section a {% block
> > extrahead %}{% endblock %}.
> > And in the index.html template I added {% block extrahead %} > http-equiv="content-type" content="application/xhtml+xml;
> >
On 9/16/06, Phil <[EMAIL PROTECTED]> wrote:
> In the base.html template I added in the section a {% block
> extrahead %}{% endblock %}.
> And in the index.html template I added {% block extrahead %} http-equiv="content-type" content="application/xhtml+xml;
> charset=UTF-8" /> {% endblock %}
It
Now that I think of it, I use the same editor for all of my templates,
so I doubt that this is the root cause.
Jorge Gajon wrote:
> Hi,
>
> On 9/12/06, Phil <[EMAIL PROTECTED]> wrote:
> > When I render index.html, the special character from base.html are
> > rendered normaly but the ones from
Hi Jorge,
thanks for the tip. I'll check that.
In the meantime, I've solved this with a bit of a uncool hack.
In the base.html template I added in the section a {% block
extrahead %}{% endblock %}.
And in the index.html template I added {% block extrahead %} {% endblock %}
This seems to
Hi,
On 9/12/06, Phil <[EMAIL PROTECTED]> wrote:
> When I render index.html, the special character from base.html are
> rendered normaly but the ones from index.html are shown as '?'.
Make sure that the editor you are using is writing your files to disk
with the correct encoding.
Hi all,
Warning: I'm a new user in town, new to django (albeit already totaly
converted this great framework), so be totally warned about my
potentially uber-noob question.
I have some troubles in the way special character (accentuated
character �, �, � and the like) are presented in the
12 matches
Mail list logo
