Tres Seaver schrieb:
[..]
Aren't RFC822-compliant e-mails 7-bit only in the headers?
Yes, but only in as much as. e.g.
Subject: =?iso-8859-1?q?p=F6stal?=
is 7-bit ASCII.
http://docs.python.org/lib/module-email.header.html
has more.
Raphael
Tres.
- --
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13 Oct 2006, at 10:10, yuppie wrote:
Wichert Akkerman wrote:
Previously yuppie wrote:
Some people still use email clients that don't support utf-8. So
you might have a policy to send iso-8859-1 emails even if your
content is utf-8 encoded.
Dear all,
I noticed recently that Formulator does not work with CMF v2 because
FSForm.py imports from CMFCore.CMFPermissions so I thought I'd fix
this and thought it might be useful. Easier said than done as there
does not seem to be a standard way to find out which version of CMF
is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charlie Clark wrote:
Dear all,
I noticed recently that Formulator does not work with CMF v2 because
FSForm.py imports from CMFCore.CMFPermissions so I thought I'd fix this
and thought it might be useful. Easier said than done as there does not
Jens Vagelpohl wrote at 2006-10-11 12:03 -0400:
...
I'm not sure this can be called a bug. It is true (and perfectly
normal) that rendering a filesystem page template will always call
the CPM. You're rendering both here. Since output_page_2 is rendered
last as it's calles from output_page_1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
Jens Vagelpohl wrote at 2006-10-11 12:03 -0400:
...
I'm not sure this can be called a bug. It is true (and perfectly
normal) that rendering a filesystem page template will always call
the CPM. You're rendering both
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13 Oct 2006, at 14:06, [EMAIL PROTECTED] wrote:
Thus, this *is* the bug. It should distinguish between primary and
nested
rendering.
Unfortunately, the bug is probably deep -- affecting the complete
cache integration. Even more importantly,
