On Wednesday 25 Sep 2002 6:24 pm, Andreas Jung wrote:

How do your patches compare to the unicode extensions made by Toby Dickenson for Zope 2.6?

They are built on top of my changes.

...

I did not test this very throughly, but it seems not broken any thing yet.

I dont have time to explain your bugs right now, but this patch is horribly broken. I suggest kent sin re-reads the updated docs on Unicode/dtml integration. I think Chris M was integrating them with the main documentation, but the original documatation about the changes is still at: http://www.zope.org/Members/htrd/howto/unicode http://www.zope.org/Members/htrd/howto/unicode-zdg-changes Hint: you should use Unicode string objects inside your published method. Dont work in plain strings and rely on a meta header to tell browsers about the character encoding. Also, think about what character encoding the browser will use for form submissions, and how zope is supposed to know about it.

Hi Kent, I'd like to compare your patches with the ones I currently implemented on my private branch. I tried to use the default settings in site.py. Unfortunately this requires changes in the local installation of python. (Dont know why the hell this does not make use of locales) Regards Tino --On Mittwoch, 25. September 2002 13:26 -0400 "Matthew T. Kromer" <matt@zope.com> wrote:

kent sin wrote:

...

I have a quick hack of Zope to use utf-8 as default encoding.

This will allow all languages co-exist, making a heaven for different language users. Also, this help to easy Zope 2.6 for non latin users.

I did not test this very throughly, but it seems not broken any thing yet.

Please consider seriously make this into zope 2.6.

I know this is very late, but the current 2.6 is very bad to non-latin users.

Rgs,

Kent Sin

Please take a look at the proposals on dev.zope.org, and file this idea as a proposal. In this way we can evaluate the solution with regards to the problem and the implementation.