On 04/02/10 14:46, bruno desthuilliers wrote:
On Feb 4, 9:18 am, Nohinder<[email protected]> wrote:
Hello,
i ran into this problem too, the solution was to specify the page coding
from the very begining:
" # -*- coding: latin-1 -*-"
This is for .py files, not templates.
well, just to note, a similar declaration can help to remove any doubt
in templates too. I try to make sure templates have a
{# -*- coding: utf-8 -*- #}
(to match the FILE_CHARSET default)
where emacs (where the -*- coding: -*- thing comes from...) and other
editors which expect it can pick it up (i.e. the first line, which
appears to be okay with {%extend%} too, I guess since {#...#} is
template syntax, not a tag like {%comment%} )
After all, a lot of template files won't have a relevant html/xml
encoding declaration in them, as they'll be extend or include fragments.
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
