10 May
2006
10 May
'06
1:52 p.m.
Steve Howe wrote:
I can buy that a framework might automagically encode Unicode strings as UTF-8 byte strings, but forcing the use of Unicode sounds like a really lousy idea to me.
I still don't understand the "forcing" thing here. Does anyone want to get rid of the .tostring() call ? Or just provide an alternative .tounicode() call for those who want unicode returned ?
It helps if you read the posts you quote: Martijn's example was a web frame- work used Unicode strings for HTTP responses, and encoded it as UTF-8 on the way out. Such a framework won't be able to handle output from the current ET serializer, but it won't work with images, external templating systems, resources read from disk, preformatted resources, etc, either. </F>