-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12 Oct 2006, at 13:56, yuppie wrote:

Jens Vagelpohl wrote:
I'd like to add an 'email_charset' property to the site (making it possible to use e.g. iso-8859-1 for emails and utf-8 for site content) and to fix the header encoding.
Are there specific problems using the same encoding for email that is used for the site (apart from any other bugs that you mention)?

None I'm aware of. But you can't change the default_charset easily because it describes the encoding of persistent data. The email encoding is just an output format that can be changed at any time.

The setting can be used for other emails as well, so I don't think it's overkill to have an extra property for that.

Well, I'm not going to protest, but I still don't see a good reason for another setting. Why would you even want to change email encoding at random times?

jens


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFFL5D9RAx5nvEhZLIRAs/5AJ4xg7g/fo0btHpNynYma3GsszELYACgpVCy
Xwqbq07kxdkePNjL9qK++HM=
=7rNo
-----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

Reply via email to