Hi!
I've an Zope application, basically postgres + zpt.
The postgres db has been upgraded to 8.5, the data inside is utf-8
(dumped and checkd it), the pg adapeter is the latest, and the *Z
Psycopg 2 Database Connection is configured to use utf-8.* Zope is
2.12.20 + latest security fix.
Hi Yuri,
does this error occur with all browsers? I once had a similar issue
that was caused only by some browsers because they do not send a
HTTP_ACCEPT_CHARSET header.
Maybe the following bug reports helps you in solving the issue:
https://bugs.launchpad.net/zope2/+bug/160968
I'm using a
I've upgraded my installation from Zope2.8.4 to Zope 2.10.4
(by copying data.fs, Products/ etc.). I have publisher encoding
and management_page_charset set to utf-8. Also system
default encoding is utf-8.
Zope 2.10 is said to have better Unicode support with
UnicodeEncodeConflictResolver. It is
--On 17. Juli 2007 10:33:39 +0200 Maciej Wisniowski
[EMAIL PROTECTED] wrote:
I've upgraded my installation from Zope2.8.4 to Zope 2.10.4
(by copying data.fs, Products/ etc.). I have publisher encoding
and management_page_charset set to utf-8. Also system
default encoding is utf-8
Did you
--On 17. Juli 2007 10:52:05 +0200 Andreas Jung [EMAIL PROTECTED] wrote:
--On 17. Juli 2007 10:33:39 +0200 Maciej Wisniowski
[EMAIL PROTECTED] wrote:
I've upgraded my installation from Zope2.8.4 to Zope 2.10.4
(by copying data.fs, Products/ etc.). I have publisher encoding
and
Did you read
http://www.zope.org/Products/Zope/2.10.4/Zope-2.10.4-released
Yes.
The migration code should auto-detect ISO-8859-15 and UTF-8
encoded page templates. For other encodings you must set
the environment variable ZPT_PREFERRED_ENCODING.
The migration code applies to
If the documented hints don't work, please submit a bugreport
with a reproducable testcase in form of a unittest.
Bug submitted with tests attached at:
http://www.zope.org/Collectors/Zope/2339
--
Maciej Wisniowski
___
Zope maillist - Zope@zope.org
Both
em tal:content=python: 'żółć'template id/em.
and
em tal:content=structure python: 'żółć'template id/em
is like playing with fire. Don't do it.
What you've got there is unicode characters written down without any
encoding information.
It will work if you set the internal ZPT encoding to
Both
em tal:content=python: 'żółć'template id/em.
and
em tal:content=structure python: 'żółć'template id/em
is like playing with fire. Don't do it.
What you've got there is unicode characters written down without any
encoding information.
This is legacy code from zope 2.8.4 that I have to
Hello,
With Zope 2.8.7 and Python 2.3.5 (Plone 2.1.3 installer), when I search inside the ZMI for the spanish
ñ character (inside a Plone site object), I get an UnicodeDecodeError:
Site Error
An error was encountered while publishing this resource.
UnicodeDecodeErrorSorry, a site error
Remy Pinsonnault wrote at 2006-9-5 11:18 -0400:
With Zope 2.8.7 and Python 2.3.5 (Plone 2.1.3 installer), when I search
inside the ZMI for the spanish ñ character (inside a Plone site object), I
get an UnicodeDecodeError:
Site Error
An error was encountered while publishing this resource.
Hi all,Due to project demands I had to convert the html entities in all TEXT fields in my database to the real international characters like á, ç and so on. The problem is that all my dynamic generated XML started to fail with UnicodeDecodeError. The XML encoding is set to utf-8 and the file
Luiz Fernando Bernardes Ribeiro wrote at 2006-8-14 11:03 -0300:
Due to project demands I had to convert the html entities in all TEXT fields
in my database to the real international characters like á, ç and so on.
Good!
The problem is that all my dynamic generated XML started to fail with
Dieter Maurer wrote:
Only the default is latin-1 (as specified by the HTML
specification).
Indeed, but that should be configurable...
Chris
--
Simplistix - Content Management, Zope Python Consulting
- http://www.simplistix.co.uk
Joern Wallstabe wrote:
Seem Zopes ZPT system is trying to do the encoding, depending on on
setHeader() method.
So if this header is set you can simply return unicode strings.
It's actually lower down in the stack... ZPublisher encodes the
response, and has a stoopid hard coded default of
Chris Withers wrote at 2005-5-25 20:54 +0100:
Joern Wallstabe wrote:
Seem Zopes ZPT system is trying to do the encoding, depending on on
setHeader() method.
So if this header is set you can simply return unicode strings.
It's actually lower down in the stack... ZPublisher encodes the
Hello,
i would like to feed a zpt form with data from a python dictionary via a
python script
zpt snippet:
textarea name=title:record:ulines rows=3 cols=65
tal:span content=python:context.printDict(here.dict)/
/textarea
python script prinDict:
keys_ = dict.keys()
keys_.sort()
lines=[]
--On Montag, 23. Mai 2005 10:35 Uhr +0200 Joern Wallstabe
[EMAIL PROTECTED] wrote:
I'm always getting a UnicodeDecodeError.
To every error message belongs a traceback where you can see
*where* the error occurs...another try?
-aj
pgpo0qQ4ukTs7.pgp
Description: PGP signature
Andreas Jung wrote:
--On Montag, 23. Mai 2005 10:35 Uhr +0200 Joern Wallstabe
[EMAIL PROTECTED] wrote:
I'm always getting a UnicodeDecodeError.
To every error message belongs a traceback where you can see
*where* the error occurs...another try?
-aj
the script decodes unicode
--On Montag, 23. Mai 2005 11:18 Uhr +0200 Joern Wallstabe
[EMAIL PROTECTED] wrote:
the script decodes unicode 'Spécification' - utf8 'Sp\xc3\xa9cification'
the error is raised during zpt processing.
by the way python default default encoding is set to ascii.
hm...I can't reproduce
Am Montag, den 23.05.2005, 10:35 +0200 schrieb Joern Wallstabe:
Hello,
i would like to feed a zpt form with data from a python dictionary via a
python script
zpt snippet:
textarea name=title:record:ulines rows=3 cols=65
tal:span content=python:context.printDict(here.dict)/
This is
Thank you all for replying - now it works I got utf-8 string in my form.
Seem Zopes ZPT system is trying to do the encoding, depending on on
setHeader() method.
So if this header is set you can simply return unicode strings.
Strange setting cmf default charset to utf-8 doesn't work :-(
Am
Joern Wallstabe wrote at 2005-5-23 11:18 +0200:
...
the error is raised during zpt processing.
by the way python default default encoding is set to ascii.
FSControllerPageTemplate at /cmf/edit_form used for /cmf/Members/wal/myid
Module StringIO, line 203, in getvalue
UnicodeDecodeError:
23 matches
Mail list logo
