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 PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=79458 --- shadow/79458 2006-09-21 07:50:47.000000000 -0400 +++ shadow/79458.tmp.23201 2006-09-21 08:32:19.000000000 -0400 @@ -1,14 +1,14 @@ Bug#: 79458 Product: Mono: Runtime Version: unspecified OS: All OS Details: -Status: NEW -Resolution: -Severity: +Status: RESOLVED +Resolution: NOTABUG +Severity: Unknown Priority: Normal Component: interop AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] TargetMilestone: --- @@ -25,6 +25,15 @@ Encoding.Default however is a code page based on environment variables or other system settings. I think the code page used for Encoding.Default would be more proper for interop ANSI strings as well because that is based on the system settings and is probably in use on system that may differ from UTF-8. + +------- Additional Comments From [EMAIL PROTECTED] 2006-09-21 08:32 ------- +This by-design issue should be ignored. Kornel pretty much understands +the argument that (1) it is Microsoft/ECMA to blame for not having +alternative to specify UTF8 in System.Runtime.InteropServices.CharSet, +(2) how the concept of "ANSI" encoding is broken, (3) such a change +will break Gtk# on Windows and there is no other way to solve the +issue, *and* still tries to flood. It is like complaining against +final and conclusive judgment, ignoring res adjudicata. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
