Monday, November 16, 2009

Re: Encoding ISO-8859-1

Thank's Karen for your reply.
With php+smarty I do the same I make a base template on which I have
some
stuff that is the same for all. In the template I place a meta tag
with charset=ISO-8859-1
and everything is fine. With Django it doesn't make any difference
what I place in meta or
xml tags. The template is processed and it is UTF-8 whether I like it
or not.
This not a matter of database or views or models it is a base
template.
I have read the manual regarding charset and I can't make any sence
from it. What I need
is an example that shows how to...
Ulferik

On 16 Nov, 14:11, Karen Tracey <kmtra...@gmail.com> wrote:
> On Mon, Nov 16, 2009 at 3:59 AM, ulferik <ulf.nordlan...@gmail.com> wrote:
> > My problem is that when I put one of these characters (´ Å Ä Ö) in the
> > template I get an error like this "UnicodeDecodeError: 'utf8' codec
> > can't decode bytes in position 578-579: invalid data"
> > Normally I specify the encoding in meta like this "charset=ISO-8859-1"
> > or "xml version="1.0" encoding="ISO-8859-1" ". There must be a way of
> > changing the encoding in Django. If anyone know how to do that please
> > post it here:
>
> http://docs.djangoproject.com/en/dev/ref/settings/#file-charset
>
> Karen

--

You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=.

0 Comments:

Post a Comment

Subscribe to Post Comments [Atom]

<< Home


Real Estate