-----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. At a later point you might want to
change that policy.
Do those people expect to be able to read non-ascii mails? I suspect
not, in which case utf-8 will not change their situation.
I can't provide an overview which clients don't support utf-8 and
what they support instead.
But AFAIK Eudora supports only iso-8859-1. So at least if people
use Eudora (without the converter plugin) iso-8859-1 will change
their situation. And I guess iso-8859-1 support is quite common in
older clients.
From my point of view please go ahead.
In general, in the future all of the emailing out stuff should make
as much use of the Python email module as possible. That way we don't
need to worry about email details.
jens
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
iD8DBQFFL6H7RAx5nvEhZLIRAktNAJ9HLkxLHMiExAIhppNF4TFYd7uj8QCgtVmt
VKiWUnXMgrv33le+O0p6pxw=
=3DB6
-----END PGP SIGNATURE-----
_______________________________________________
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
