-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Florent Guillaume wrote: > If I understand, the goal is to specify the file encoding for the > export. Do we really need this? Isn't UTF-8 good enough in all cases?
It's good enough for XML, where documents without specified encodings are mandated to be UTF-8; For HTML, it gets tougher, as the mechanisms for spelling the encodings are harder. Python scripts are much harder, as Python's parser wants an explicit comment for non-ASCII-encoded source. One place that the breakdown shows up is in the 'SnapshotExportContext', where unicode can sneak into content (via import, for instance), which breaks the OFS.File handling in 2.8 (that code is the only client of 'getEncoding' at the moment). Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDOsgM+gerLs4ltQ4RArwFAJ9Dl3BMQP9RmADsLY7GxAK58hC0aQCeK1Gt uKDJiT7IL0W9jC4j55skdWg= =Z3Mj -----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