Submitted by : SimonMichael at: 2004-06-15T12:02:50+00:00 (13 years ago)
Name :
Category : Severity : Status :
Optional subject :  
Optional comment :

RESPONSE.setHeader(...utf8...) was added in wikipage_macros and in I18NSupport.py to get translations working. For 0.32 it has been added to all dtml pages/templates as well. This causes problems for people who want to stay with latin-1 encoding.

It's about all I can do to get utf-8 working right now, I won't spend time on latin-1 but will welcome fixes to make it work better. At minimum we should probably be sensitive to portal_properties/site_properties/default_charset when in CMF/Plone.

Encoding as optional property on wiki-folder? --Sun, 08 May 2005 05:37:52 -0700 reply

I have some wikis in English (charset doesn't matter) and some wikis in Norwegian (charset is iso-8859-1). Upgrading from Zope 2.6.2/Zwiki 0.25 to Zope 2.7.5/ZWiki 0.39 was naturally bad news for the Norwegian ones. I wound up changing wikipage_macros, replacing "utf-8" in lines 5 and 7 with "iso-8859-1". Now, why can't this be just another property on the wiki-folder? If the property is set, use it, if not, use utf-8. Furthermore, since line 5 exist (sets charset in response), why is line 7 (explicitly sets charset in html) necessary at all? Some browsers don't like the charset being reset this way, and it tends to slow the rendering of the page.

... --betabug, Wed, 21 Feb 2007 08:31:47 +0000 reply

Name: '#855 ara' => '#855 0.31 hard-codes utf-8, ignores cmf/plone's default_charset' Category: user-fittests => general-i18n