[Zope-Checkins] CVS: Zope3/lib/python/Zope/PageTemplate - PageTemplate.py:1.3
Stephan Richter
srichter@cbu.edu
Fri, 14 Jun 2002 08:11:26 -0400
On Friday 14 June 2002 08:01, Guido van Rossum wrote:
> > > When I type a non-ASCII character in a box in my browser, is it
> > > encoded as UTF-8?
> >
> > That depends on your browser settings. Also, if you send
> >
> > <meta http-equiv=3D"content-type" content=3D"text/html; charset=3DUTF-8=
">
> >
> > you can set a particular character set (encoding).
>
> Does this affect the encoding of stuff sent back from the form?
Yes, it should theoretically encode it to UTF-8 now...but it does not work =
all=20
the time. Geez.
> > We agreed to standardize on UTF-8. However, we really need to find a
> > way later to make this variable.
>
> Why? Because of the first issue?
Well, I actually just changed the code. I noticed that even the meta direct=
ive=20
does not work all the time. Therefore we check for UTF-8 first, and if this=
=20
fails I try all the character sets in HTTP_ACCEPT_CHARSETS. If no encoding=
=20
works, then we do nothing...maybe we should raise an error, but I want some=
=20
feedback about this first.
> > I still don't understand why the browser is not sending its encoding
> > mechanism in the HTTP header.
>
> Because the authors of HTTP were clueless about i18n?
:-) Most likely.
Regards,
Stephan
=2D-=20
Stephan Richter
CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student)
Web2k - Web Software Design, Development and Training