[Mono-bugs] [Bug 52604][Wis] New - XSP output encoding bug
Mon, 5 Jan 2004 08:34:36 -0500 (EST)
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
Changed by email@example.com.
--- shadow/52604 2004-01-05 08:34:36.000000000 -0500
+++ shadow/52604.tmp.2184 2004-01-05 08:34:36.000000000 -0500
@@ -0,0 +1,46 @@
+Summary: XSP output encoding bug
+Description of Problem:
+XSP has problems with displaying properly encoded national characters.
+When .aspx contains utf-8 strings, either in HTML part or generated by
+Response.Write (file is recognized as proper UTF-8), output is messy,
+looks like UTF-16 or sth similar.
+I've tried to enforce utf-8 by setting Response.Charset, http headers
+and globalization options in web.config, nothing worked.
+.NET displays the file properly only if Unicode signature (BOM) is defined
+at the beginning of the file, but XSP seems to ignore even that. Also
+BOM is *not* mandatory, so in my opinion XSP should recognize BOM, but
+should not require it.
+I wrote more about BOM issue here:
+Attaching simple test case:
+* encoding.aspx - proper utf-8, displayed incorrectly (only last line,
+parsed XML, looks fine; but this is because national characters are
+transformed to non-ASCII &#[number]; form)
+* encoding-bom.aspx - same as above, with utf-8 BOM (three bytes at the
+beginning of the file: EF BB BF); IIS sends proper chars to the browser,
+* encoding.xml, encoding.xsl
+I did not check, but I suppose same thing happens when someone would like
+to have ISO-8859-2 output encoding or any other.