Hi Tom, and Tom :)
I have tried the Hindle version of the test.
Summary: the sample depends on .NET bug; 2 .NET bugs, 1 mono bug.
This exactly shows that .NET Normalization is buggy. Here is the
result from ICU normalization results:
http://demo.icu-project.org/icu-bin/nbrowser?t=\u00e1bcs=uv=0
Actually I was wrong at fixing the first bug you reported. It was
actually .NET which is buggy, though unlike older Mono it doesn't result
in an unhandled exception.
http://demo.icu-project.org/icu-bin/nbrowser?t=\u03B1\u0313\u0345s=uv=0
To examine C# implementation, try below:
foreach
Atsushi,
Thanks for the fixes. From a cursory test, it appears this fixes our issues
as well. I assumed that Mono was using MbUnit. I'll send you a test case w/o
MbUnit that's more in line with the current Mono test framework when I get
the chance.
Tom Philpot
On 6/19/09 3:04 AM, Atsushi Eno
Hey Atsushi,
What version of .NET did you test against?
I get the expected result using both .NET 3.5 SP1 (.NET 2.0 SP2) and .NET
4.0 beta 1.
Gert
-Original Message-
From: mono-devel-list-boun...@lists.ximian.com
[mailto:mono-devel-list-boun...@lists.ximian.com] On Behalf Of Atsushi Eno
Atsushi,
Thats great - our unit tests that involve Normalization stuff now pass
with mono r136521.
Regression squashed from our perspective!
Thanks very much!
Tom
On Fri, 2009-06-19 at 19:04 +0900, Atsushi Eno wrote:
Actually I was wrong at fixing the first bug you reported. It was
actually
