Hello public-webarch-comments, The reason for that is because of the required text/* fallback to text/plain;charset="us-ascii" So, since XML requires UTF-8 and UTF-16 support the latter in particular is a problem - for systems that don't understand XML. However, if one happens to have a UTF-16 XML document and one wants to serve the source as source, then serving it as text/plain;charset="utf-16" is perfectly fine because it is not a falback behavior but a deliberate action, and is unambiguous wrt character encoding -- Chris Lilley mailto:chris@w3.org Chair, W3C SVG Working Group Member, W3C Technical Architecture GroupReceived on Monday, 18 October 2004 19:32:36 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 6 April 2009 12:37:33 GMT