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 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
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
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 ...
dtml-var u''
This ensures that the dtml which computes this page
content returns a unicode object.
This line, intended to
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
