> > > > """ > It is better to encode your Web pages in UTF-8, and serve them as such. In > HTTP, the HTTP header has priority, then the meta name contained in HTML. > Some Web pages have specific encoding. It happens often on the Web that the > Web page encoding is different from the one specified in the file and/or > the one specified in HTTP headers. It creates issues for users who receive > unreadable characters on their screens. So the browsers have to fix the > encoding on the fly. We had bug reports about Web sites sending BOM > different from the HTTP header. We decided to make the BOM authoritative > like webkit and IE, because there are more chances for it to be exact than > the HTTP headers. > """ > > http://my.opera.com/ODIN/blog/**2012/03/26/whats-new-in-opera-** > development-snapshots-march-**26-2012<http://my.opera.com/ODIN/blog/2012/03/26/whats-new-in-opera-development-snapshots-march-26-2012> > > In our case if a meta content type tag exists in a template, the HTTP header charset parameter will always be set to the same value. Always. There is no chance of a conflict. zope.pagetemplate should therefore not opaquely strip out the meta tag.
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )