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=\u00e1bc&s=&uv=
Attached small self contained my test case.
I think the output should be 5 trues.
I getting 2 Trues and 3 Fails. on mono version r136435
Incidentally .NET returns 5 trues for this test case.
Is there a Bugzilla entry for this issue?
Also normalization-tables.h is now has windows line endings
Here is a revision of the test case I sent earlier to the list that doesn't
rely on any specific encoding (only uses '\u' characters).
Hopefully this will be helpful.
Tom
On 6/18/09 1:49 PM, "Tom Hindle" wrote:
> Hi Guys,
>
> With regard to recent Normalization changes I have just run ou
Hi Guys,
With regard to recent Normalization changes I have just run our test
suite with recent mono r136422 - and are getting a number of
regressions.
For example:
{
string styleName = "\u00e1bc";
StStyle style = new StStyle();
Cache.LangProject.StylesOC.Add(style);
style.Name = styleName;
Fw
