Is there any need to support tool settings with other encodings than
utf-8 (and ascii as a subset of utf-8)?
AFAICS there's not even a need for utf-8: Most settings are not visible
for users and those that are (like title and description of Actions and
type infos) can contain an ascii i18n message id.
But supporting utf-8 would not cost us much extra and might help people
who don't use translations.
See also http://www.zope.org/Collectors/CMF/292
For CMFSetup/GenericSetup this would mean:
All 'encoding' parameters, attributes and methods could be removed. The
XML files are anyway utf-8 encoded, so there would not be any need to
convert strings from one encoding to an other.
(At the moment a hardcoded ascii encoding is passed around everywhere.)
Zope-CMF maillist - Zope-CMF@lists.zope.org
See http://collector.zope.org/CMF for bug reports and feature requests