Hi!
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
The following supporters have open issues assigned to them in this collector
(http://www.zope.org/Collectors/CMF).
Assigned and Open
efge
- CMFSetup: provide non-ascii im- and exports,
[Accepted] http://www.zope.org/Collectors/CMF/292
- CMFSetup doesn't correctly detect
Hi Yuppie,
Is there any need to support tool settings with other encodings than
utf-8 (and ascii as a subset of utf-8)?
I think there is. Take for instance the portal property title. It could
very well be a non-ascii string, and contain accents. It could be (a) an str
encoded in some
Hi Florent!
Florent Guillaume wrote:
Is there any need to support tool settings with other encodings than
utf-8 (and ascii as a subset of utf-8)?
I think there is. Take for instance the portal property title. It
could very well be a non-ascii string, and contain accents. It could be
(a)
On 15 Sep 2005, at 17:16, yuppie wrote:
Is there any need to support tool settings with other encodings
than utf-8 (and ascii as a subset of utf-8)?
I think there is. Take for instance the portal property title.
It could very well be a non-ascii string, and contain accents. It
could be
