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=77315 --- shadow/77315 2006-01-21 11:21:18.000000000 -0500 +++ shadow/77315.tmp.18956 2006-01-23 04:23:13.000000000 -0500 @@ -10,12 +10,13 @@ Component: interop AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] TargetMilestone: --- URL: +Cc: [EMAIL PROTECTED],[EMAIL PROTECTED] Summary: Invalid Unicode surrogate handling Description of Problem: The internal string representation (UTF-16) allows for certain invalid strings to appear in the program, when the surrogate characters (U+D800-U+DFFF) don't pair correctly. I've identified three problems @@ -108,6 +109,22 @@ A proposed fix for the 3 issues (hunks related to individual issues can be easily extracted) ------- Additional Comments From [EMAIL PROTECTED] 2006-01-21 11:21 ------- eno, could you look at this stuff ? + +------- Additional Comments From [EMAIL PROTECTED] 2006-01-23 04:23 ------- +Sebastien: which do you think is better: to keep UTF8Encoding as is +(i.e. ignore RFC and make UTF8Encoding behavior match MS.NET) only +under 1.x, or treat them as invalid as well. There are a bunch of +tests that turned to fail after applying this patch. They all look like: + +#if NET_2_0 + [ExpectedException (typeof (DecoderFallbackException))] + [Category ("NotWorking")] +#endif +// MS Fx 1.1 accept this +// [ExpectedException (typeof (DecoderException))] + public void T5_IllegalCodePosition_1_UTF16Surrogates_511 () + { + _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
