[ZCM] [ZC] 737/ 3 Resolve "For people that live in a Non-latin1 Non-unicode world, Zope 2.6 has some rough edges."

Collector: Zope Bugs, Features, and Patches ... zope-coders-admin@zope.org
Tue, 28 Jan 2003 09:58:26 -0500


Issue #737 Update (Resolve) "For people that live in a Non-latin1 Non-unicode world, Zope 2.6 has some rough edges."
 Status Resolved, Zope/bug medium
To followup, visit:
  http://collector.zope.org/Zope/737

==============================================================
= Resolve - Entry #3 by htrd on Jan 28, 2003 9:58 am

 Status: Accepted => Resolved

merged with 2.6.1
________________________________________
= Comment - Entry #2 by htrd on Jan 27, 2003 10:33 am

There is an updated patch at http://www.atransia.co.jp/home/ZenKai/Members/kafka/patch/Zope261b.patch 

I have had several confirmations that this patch is good. I will add it (plus some documentation) to toby-charset-branch, with a goal of getting this in 2.6.1 or 2.6.2

________________________________________
= Request - Entry #1 by htrd on Dec 20, 2002 6:09 am

 Status: Pending => Accepted

 Supporters added: htrd


Uploaded:  "nuzmi.tgz"
 - http://collector.zope.org/Zope/737/nuzmi.tgz/view
A number of old bugs relate to this issue in different ways:
http://collector.zope.org/Zope/598
http://collector.zope.org/Zope/623
possibly others

There was a big debate on zope-dev:
http://lists.zope.org/pipermail/zope-dev/2002-December/018261.html

I attach 4 patches for the proposal in that zope-dev article:

01-bugday-multiple.diff
  a change from the last bug day, needed to make
  other patches merge cleanly. This is already in 2.6.1

02_publisher_encodings.diff
  duplicated from http://collector.zope.org/Zope/736
  I would like to get this in 2.6.1

03-properties.diff
  a patch to implement a variant of step 3
  in the proposal. The properties page does not
  use utf8 if another site-global ZMI encoding has
  been specified

04-manage-header.diff
  a patch to restore the documented behavior
  of management_page_charset (step 2 in the proposal
  linked above)

I do not intend rushing these last two patches into 2.6.1
==============================================================