- From: MURATA Makoto <murata@apsdc.ksp.fujixerox.co.jp>
- Date: Fri, 30 Apr 1999 11:32:14 +0900
- To: xsl-editors@w3.org
- Cc: murata@apsdc.ksp.fujixerox.co.jp
1) CES of the result tree in files When the result tree is created as a sequence of bytes, how does XSLT implementation chooses the character encoding scheme (CES)? In the spirit of XML, I think that any charset should be allowed although most implementations support UTF-8 or UTF-16 only. One implementation of XSL in Japan already supports Shift JIS. Though I am not a fan of Shift JIS and encourage people to switch to Unicode, I do not think we are not quite ready to throw away legacy encodings. 2) Generating encoding declarations We also need a mechanism for easily creating encoding declarations or META tags containing the charset info. It might be a good idea to automatically generate XML declarations or META tags. 3) CES of the result tree in the main memory In the case that the result tree is created in the main memory and then directly used for imaging, the program should just know the CES of the result tree. This should be made explicit. (Does this policy conflict with (2) as above?) Note: IE 5.0 fails here. If an XSL stylesheet does not create META tags, IE 5.0 displays a corrupted document. Cheers, Makoto Fuji Xerox Information Systems Tel: +81-44-812-7230 Fax: +81-44-812-7231 E-mail: murata@apsdc.ksp.fujixerox.co.jp
Received on Thursday, 29 April 1999 22:32:31 UTC