--On 25. August 2007 15:48:04 +0200 Sascha Welter <[EMAIL PROTECTED]>
wrote:
(Fri, Aug 24, 2007 at 10:26:42AM +0200) Patrick Ulmer
wrote/schrieb/egrapse:
Now I only must find the right place for setdefaultencoding() so
it only affect my zope-instance.
Install a separate python that is use
(Fri, Aug 24, 2007 at 10:26:42AM +0200) Patrick Ulmer wrote/schrieb/egrapse:
> Now I only must find the right place for setdefaultencoding() so
> it only affect my zope-instance.
Install a separate python that is used only by your zope instance. Use
setdefaultencoding only there.
Regards,
Sascha
Doyon, Jean-Francois wrote at 2007-8-24 09:36 -0400:
> ...
>setdefaultencoding() is apparently frowned upon ... Not sure why though.
Occasionally, a package writer expects that "str" converts to ASCII,
such that
try: ascii = str(unicodeStr)
except UnicodeError:
# non ascii
can b
Patrick Ulmer wrote at 2007-8-24 10:26 +0200:
>I think I solved the problem.
>
>
>
>works. I read some further and found out that I should use something like
>
>import sys
>sys.setdefaultencoding('utf-8')
>
>I set it global in sitecustomize.py under /usr/lib/python2.4/site-packages and
>then
>
>
rting to any "trickery".
setdefaultencoding() is apparently frowned upon ... Not sure why though.
Good luck!
J.F.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Patrick Ulmer
Sent: August 24, 2007 04:27
To: zope@zope.org
Subject: Re: [Zope] u
Hi,
I think I solved the problem.
works. I read some further and found out that I should use something like
import sys
sys.setdefaultencoding('utf-8')
I set it global in sitecustomize.py under /usr/lib/python2.4/site-packages and
then
works. Now I only must find the right place for setd
>> I have checked it but it is the same problem. Browser is encoding in
>> utf-8 correct, but the result (html sourcecode from zope) is not utf-8
>> anymore after inserting and I
>> don't know why it changed. How can a dtml-var-tag changed the encoding
>> for the document?
>>
>
> What about
>
>
--On 24. August 2007 09:36:30 +0200 Jaroslav Lukesh <[EMAIL PROTECTED]>
wrote:
- Original Message - From: "Patrick Ulmer" <[EMAIL PROTECTED]>
The http-equiv tag means not much to browser. Try setting the
content-type
including the charset within the HTTP response
(REQUEST.RESPONSE.
- Original Message -
From: "Patrick Ulmer" <[EMAIL PROTECTED]>
The http-equiv tag means not much to browser. Try setting the
content-type
including the charset within the HTTP response
(REQUEST.RESPONSE.setHeader(...)).
I have checked it but it is the same problem. Browser is encoding
Hi,
>> 4. I insert html-code and some russian chars for testing
>>
>>
>>
>>
>>
>>
>>...russian chars...
>>
>>
>>
>> After Saving all looks great in ZMI and also in my webbrowser.
>>
>> 5. Now I add one line to use a MessageCatalog:
>>
>>
>>
>> After that, all of my utf-8-chars are br
--On 24. August 2007 08:32:17 +0200 Patrick Ulmer <[EMAIL PROTECTED]>
wrote:
Hi,
because nobody in der Localizer-Mailings list react and I thinks it could
be a common problem with utf-8 in zope, I ask my question here also.
I use Localizer 1.2.1 and I try out some things and all looks
great
11 matches
Mail list logo