[ZCM] [ZC] 2148/ 2 Comment "management_page_charset confusion and uglyness"

[Collector: Zope Bugs, Features, and Patches ...]

Issue #2148 Update (Comment) "management_page_charset confusion and uglyness"
 Status Accepted, Zope/bug medium
To followup, visit:
  http://www.zope.org/Collectors/Zope/2148

==============================================================
= Comment - Entry #2 by Mark Barratt on Jul 29, 2006 8:17 pm

+1 from me. there may be occasions where you want to have the ZMI in a different character-set from your published output, but this is largely only true where your PC's operating system is character-set-crippled. Windows Unicode support is mature and pervasive, Macs are OK. Don't know about Linux desktops
________________________________________
= Request - Entry #1 by tino on Jul 13, 2006 9:09 am

 Status: Pending => Accepted

 Supporters added: tino

Symptom:

with the unicode patchery, there was a management_page_charset property invented which, when set, defines the charset put into
meta-tag for (some) ZMI pages to override what is set by the ZPUblisher. While this isnt even evaluated for every ZMI page,
the default is iso-8859-1. 

Now this property is only used by ZMI pages but not by the
publishing process by default. So if you input in some charset
and then hit "test" - you see your results in a totally different
charset - this time the zope.conf directive 
default-zpublisher-encoding is used.

So you input in one encoding and view in another, which its
totally silly imho and leads to a lot of confusing errors
like if you add true unicode strings to the scenario.

Solution:

remove all default meta-tag code including the management_page_charset - hack and just use
the zope.conf default-zpublisher-encoding.

This would solve all problems at once
(including unicode properties, form values
etc)

(NB: default-zpublisher-encoding could probably
default to the encoding specified on locale
in zope.conf)

==============================================================