[Mono-bugs] [Bug 76758][Maj] Changed - String with nonstandard characters is not handled correctly.

[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 atsushi at ximian.com.

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

--- shadow/76758	2005-12-06 23:36:57.000000000 -0500
+++ shadow/76758.tmp.13878	2005-12-07 00:51:47.000000000 -0500
@@ -1,12 +1,12 @@
 Bug#: 76758
 Product: Mono: Class Libraries
 Version: 1.1
 OS: unknown
 OS Details: Tested under Windows XP SP2 and CentOS 3.4
-Status: NEW   
+Status: NEEDINFO   
 Resolution: 
 Severity: Unknown
 Priority: Major
 Component: CORLIB
 AssignedTo: mono-bugs at ximian.com                            
 ReportedBy: admin at svwebhosting.com               
@@ -135,6 +135,27 @@
 43 65 80 56 65 47 119 68 47 65 80 56 45 103 101 116 115 116 97 116 117 115
 
 -------------------------------------------------
 Using System.Text.Encoding.UTF8.GetBytes:
 195 191 195 191 195 191 195 191 103 101 116 115 116 97 116 117 115
 
+
+------- Additional Comments From atsushi at ximian.com  2005-12-07 00:51 -------
+Encoding.Default is VERY different between Windows and non-Windows.
+You seem to have utf-8 as the default encoding, which makes sense if
+you are running GNOME.
+
+> I have tested with all encodings on CentOS and they all give the
+wrong results
+
+Incorrect. All seem to give the *correct* results (what is the
+criteria of "wrong" here??).
+
+No one can't exactly know which encoding is used for the source file
+with the information provided in this bug, but when I read the source
+file in UTF-8 mode, it is regarded as containing invalid characters.
+
+They show replacement characters for "invalid" UTF-8 input characters.
+For example, "63" in ASCII is '?'.
+
+This bug will be closed as NOTABUG, but it depends on the actual input
+encoding.