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 08:32:19.000000000 -0400 +++ shadow/79458.tmp.23802 2006-09-21 08:52:05.000000000 -0400 @@ -34,6 +34,18 @@ 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. + +------- Additional Comments From [EMAIL PROTECTED] 2006-09-21 08:52 ------- +I like your metaphor and agree with most of your comments. But there +are other ways to marshal strings as UTF-8. + +The easiest would be to add a runtime level setting (an environment +variable for example) that specifies whether ANSI charset is UTF-8 +or Encoding.Default. + +Another solution that would be very proper and even supported on +MS.NET is to use custom marshalers that marshal managed strings to +unmanaged UTF-8 string. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
