Am 18.01.2009 um 23:00 schrieb yuppie:
Hi Charlie!
Hiya Yuppie,
Charlie Clark wrote:
Am 29.12.2008 um 15:01 schrieb Charlie Clark:
CMFDefault.utils
def getBrowserCharset(request):
Get charset preferred by the browser.
envadapter = IUserPreferredCharsets(request)
Charlie Clark wrote:
Am 18.01.2009 um 23:00 schrieb yuppie:
I agree that there shouldn't be implemented in a different way than
for Zope 3. And if we can solve the problems by fixing form encoding
I'm happy. Although I'd like to see UTF-8 always the first charset
returned if * the
Summary of messages to the cmf-tests list.
Period Sun Jan 18 12:00:00 2009 UTC to Mon Jan 19 12:00:00 2009 UTC.
There were 6 messages: 6 from CMF Tests.
Tests passed OK
---
Subject: OK : CMF-2.1 Zope-2.10 Python-2.4.5 : Linux
From: CMF Tests
Date: Sun Jan 18 21:15:18 EST 2009
URL:
Am 19.01.2009 um 11:32 schrieb yuppie:
zope.publisher.http.HTTPCharsets explicitly prefers utf-8. Are you
sure
getPreferredCharsets()[0] is iso-8859-1 with your browser? Or do you
override somewhere the Content-Type header set by setPageEncoding()?
AFAICS CMFDefault works exactly the way
yuppie wrote at 2009-1-19 11:32 +0100:
Charlie Clark wrote:
Am 18.01.2009 um 23:00 schrieb yuppie:
I agree that there shouldn't be implemented in a different way than
for Zope 3. And if we can solve the problems by fixing form encoding
I'm happy. Although I'd like to see UTF-8 always the
Charlie Clark wrote at 2009-1-18 22:30 +0100:
Am 18.01.2009 um 20:36 schrieb Dieter Maurer:
...
From the current HTML specification:
accept-charset = charset list [CI]
This attribute specifies the list of character encodings for input
data that is accepted by the server processing this form.
Dieter Maurer wrote:
yuppie wrote at 2009-1-19 11:32 +0100:
Charlie Clark wrote:
Am 18.01.2009 um 23:00 schrieb yuppie:
I agree that there shouldn't be implemented in a different way than
for Zope 3. And if we can solve the problems by fixing form encoding
I'm happy. Although I'd like to
