[Zope-dev] [ZOPE 2.6 B1] Unicode/locale problems withOFS/dtml/properties.dtml

Arnar Lundesgaard arnar.lundesgaard@creuna.no
Thu, 26 Sep 2002 23:01:15 +0200


> I can second this. With CVS-Zope (did the last cvs up this moment)
> I'm getting a very curios thing:
> Displaying .../index_html is ok.
> But=20
> return context.index_html(context,request)
> creates broken characters instead is isolatin1 Umlaute.
> In my case (Konqueror on Linux) it seems that the
> text/html;charset=3DUTF-8 breaks the page because the byte values are
> correct for the "Umlaute". This is further confirmed by the fact that
> forcing Konq to display iso8859-1 fixes the display.

Hmm, you may check out http://collector.zope.org/Zope/517 but it could =
be the same difficulties as we experienced earlier.

The problem here was that Zope thought it was returning UTF-8, while it =
was really returning ISO-8859-1. This was due to the <dtml-var "u''"> =
statement not having the desired effect. <dtml-var "u' '"> (notice the =
space) seemed to work brilliantly.

> So how are these Unicode changes supposed to work? Are non-ascii
> characters forbidden now? And how do I get UTF-8 text into Zope?

There are converters inside ZOPE. UTF-8 is simply a transport format, =
although it may be used for storage to save space. There is lots of =
software that supports UTF-8 today. This is the future.

> While I'm quite sure that this will help Zope in the Asiatic region, =
it
> seems quite inconvienent for isolatin1 world :(

This will be a win in Europe as well, especially for multilingual sites. =
IIRC  there are 15 variants of ISO-8859-1.

I18N is *very* important, and Unicode is an essential ingredient.

=20
  Arnar Lundesgaard