[Mono-devel-list] Re: Fixes to XSLT

Andrew Skiba andrews at mainsoft.com
Tue Feb 8 05:28:32 EST 2005

Atsushi Eno wrote:
> Okay, it also throws that exception in my box, but it is not reported
> in your Class1.cs test ... ?
Class1.cs catches all the exceptions and prints the text of them into
the results file, if I understand correct your question.

> So maybe there is no reference (original) "catalog.xml", right?
Sorry, I again do not understand what you just said. If you mean that
there is no original catalog.xml, it's a part of OASIS test suite. My
catalog-out.xml is produced from the original catalog by a simple XSL,
so it ended up in the same dir.

> Well, apparently Xalan test collection is less than MS tests, so
> it is great that now we can easily test MS test collections with
> your testcode ;-) I'll modify Class1.cs as runnable under 
> "standalone_tests" (and file name as well ;-) and check into svn.
Cool! Than probably it's better to use my XSL on the up-to date OASIS
catalog.xml to make updated catalog-out.xml, see the attached file.

> BTW am on reviewing your patch and committed some of them. Now
> the error (well, different result) cases are 438, from 557.
> It is very nice :-) I'll continue my review and mail you later.
Yes, I hope that changes in this patch are very simple, so there will be
no problems with them. There is another patch, which I named
"notsogood.patch", there we will probably have problems.

> Thanks,
> Atsushi Eno
Thank you, too.
I'm still working on the enum issue, BTW, so you will hear from me today.
Andrew Skiba.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: simplify.xsl
Type: text/xml
Size: 826 bytes
Desc: not available
Url : http://lists.ximian.com/pipermail/mono-devel-list/attachments/20050208/6deec67e/attachment.xsl 

More information about the Mono-devel-list mailing list