On 8/11/09 10:43 , Martijn Pieters wrote:
Archetypes is very much wrong doing this; encoding and decoding should happen at the I/O boundaries. The number of times I have to special-case Archetypes because it returns UTF-8 is ridiculous.
It returns site encoding, which might not be UTF-8.
The reason Archetypes does this is purely historical, technically there is no reason anymore (other than backwards compatibility) to not return unicode.
Aside from expectations by a probably surprisingly large amount of code. Everything that tries to pass data to external processes such as portal transforms and various newsletter products are build around a lot of assumptions that might no longer hold if we change this.
Having said that I would love to see this change in a major Plone release. Wichert. _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
