This is not a Zope related issue. In my experience most browser seem to ignore the charset as specified with the meta-equiv tag. The recommended way is to send a content-type: text/html; charset=XXX HTTP header..this is the way to do..you can use REPONSE.setHeader() for doing this as well from the app level.

-aj

--On 12. Mai 2006 14:18:30 -0500 mbr <[EMAIL PROTECTED]> wrote:

Hi list

I use Zope 2.9.1 and have a problem with encoding.
I use Firefox 1.5.0.3

The document have &lt;meta http-equiv="content-type"
content="text/html; charset=ISO-8859-1"&gt; but Firefox say what the
document it ISO-8859-15

I found in zope.conf default-zpublisher-encoding and change to iso-8859-1
it this the only way to resolv my problem?
why the meta tag is ignored?

pd. Sorry for my english

--
Lo bueno de vivir un dia mas
es saber que nos queda un dia menos de vida
_______________________________________________
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists -  http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope-dev )



--
ZOPYX Ltd. & Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany
Web: www.zopyx.com - Email: [EMAIL PROTECTED] - Phone +49 - 7071 - 793376
E-Publishing, Python, Zope & Plone development, Consulting

Attachment: pgpPnThhdiVwj.pgp
Description: PGP signature

_______________________________________________
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope-dev )

Reply via email to