[ZCM] [ZC] 1124/ 2 Resolve "ZReST Product charset default encodings"
Collector: Zope Bugs, Features,
and Patches ...
zope-coders-admin at zope.org
Thu May 13 10:55:23 EDT 2004
Issue #1124 Update (Resolve) "ZReST Product charset default encodings"
Status Resolved, Zope/bug low
To followup, visit:
http://zope.org/Collectors/Zope/1124
==============================================================
= Resolve - Entry #2 by ajung on May 13, 2004 10:55 am
Status: Pending => Resolved
Fixed on the SVN HEAD and 2.7 branch.
________________________________________
= Request - Entry #1 by barryp on Nov 16, 2003 10:56 pm
I noticed that by default, a ReStructuredText Document from the ZRest Product has the defaul input_encoding and output_encoding properties fixed to 'iso-8859-15'. It doesn't seem to be affected by the 'rest-input-encoding' or 'rest-output-encoding' properties in zope.conf (mentioned as a new feature in 2.7.0b1)
The rest of Zope seems to be thinking 'utf-8'; on my box I'm seeing inconsistent charsets in a test document between the HTTP header and the document source:
HTTP HEADER:
Content-Type: text/html; charset=iso-8859-15
DOCUMENT SOURCE:
<?xml version="1.0" encoding="utf-8" ?>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
---------
I'd think that somehow lib/python/Products/ZReST/ZReST.py should have its default encodings the same as found in lib/python/reStructuredText/__init__.py
==============================================================
More information about the Zope-Collector-Monitor
mailing list