[Mono-bugs] [Bug 75252][Nor] Changed - ASP.NET failing to compile code with identifiers containing non-English characters in UTF-8

[bugzilla-daemon at bugzilla.ximian.com]

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 kornelpal at hotmail.com.

http://bugzilla.ximian.com/show_bug.cgi?id=75252

--- shadow/75252	2005-06-14 08:42:31.000000000 -0400
+++ shadow/75252.tmp.3020	2005-06-14 10:17:51.000000000 -0400
@@ -242,6 +242,30 @@
 being honored, but replaced with Encoding.Default.
 
 ------- Additional Comments From informatique.internet at fiducial.fr  2005-06-14 08:42 -------
 I've no more problem with compilation with your fixes. But I cannot
 display Utf-8 characters in apsx pages... they don't appear at all...
 changes to <globalization> in web.config changes nothing...
+
+------- Additional Comments From kornelpal at hotmail.com  2005-06-14 10:17 -------
+Gonzalo, there are bigger problems with the handling of 
+globalization element.
+
+I used Windows XP, Mono and XSP from SVN HEAD.
+
+1. If I set bot requestEncoding and responseEncoding to "utf-8" and 
+fileEncoding to the appropriate code page (I used windows-1250) or 
+use byte order marks (I used UTF-8) the file is read but is double 
+encoded using UTF-8. I think at source code level because the "é" in 
+identifier still does not compiles and the output has charset=utf-8 
+but I have to decode it using UTF-8 twice to get the original text.
+
+2. If I set fileEncoding to "" to override machine.config with 
+Encoding.Default it results in charset=windows-1250 
+(Encoding.Default) altough responseEncoding is "utf-8" and does not 
+show the text as expected. I examined the raw HTTP response and it 
+contains "???©?­??" instead of "áéíõ" so there are a lot of charset 
+misinterpretations.
+
+3. The value of fileEncoding and responseEncoding should be 
+independent from each other none of the should be used as the 
+default value or instead of the other one.