On Thursday 26 Sep 2002 9:06 pm, Arnar Lundesgaard wrote:
> Jepp, that seems to work. I'm at home though, so I haven't been able to try
> with the original browser configuration. 'wget' gives me UTF-8 though, so
> it should work nicely. :-)
Thanks. This is now in the cvs trunk and the 2.6 branch
On Friday 27 Sep 2002 10:38 am, Joachim Werner wrote:
> After copying the relevant lines from the new
> manage_page_header in Zope 2.6 everything works fine,
hurrah!
> except for one
> remaining issue:
b
> One can create properties with Umlauts or other non-ASCII characters (which
>
Hi!
I have tracked down the problem with Collector issue 517 (Unicode problems)
now:
My Product used a modified manage_page_header that did not set the meta
header for the encoding. After copying the relevant lines from the new
manage_page_header in Zope 2.6 everything works fine, except for one
ginal Message -
From: "Toby Dickenson" <[EMAIL PROTECTED]>
To: "Arnar Lundesgaard" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Thursday, September 26, 2002 6:04 PM
Subject: Re: [Zope-dev] [ZOPE 2.6 B1] Unicode/locale problems with
OFS/dtml/properties.dt
> Thanks for taking the time to help debug this.
Thanks for fixing it so quickly!
> This line, intended to force the dtml to be rendered as a unicode
> object, is not doing its job. If the dtml is not a unicode object
> then ZPublisher's encoding mechanism is not engaged. Has there been
> some r
On Thursday 26 Sep 2002 5:47 pm, Arnar Lundesgaard wrote:
Thanks for taking the time to help debug this.
> > > lib/python/OFS/dtml/properties.dtml contains ...
> > >
> > This ensures that the dtml which computes this page
> > content returns a unicode object.
This line, intended to force t
> what do you mean by "inserted into the form"?
Put there by the dtml-method in a dtml-var statement.
> That the response contains a single byte where you properties
> contain character whose unicode value is greater than 127 ?
Yes
> how have you checked this? if so, thats a bug.
In a Hex e
On Thursday 26 Sep 2002 4:38 pm, Arnar Lundesgaard wrote:
> We can successfully store Norwegian characters
> ('æ','ø', and 'å') in property fields, but when we reload the page, we
> get results that display wrong.
Thats bad. I will definetely resolve this asap.
> When studying the generated sou
