W3C home > Mailing lists > Public > www-xsl-fo@w3.org > April 2005

RE: [XSL-FO] which xslt processor for .net?

From: Altsoft Xml2PDF <xml2pdf@alt-soft.com>
Date: Tue, 19 Apr 2005 02:38:10 +1200 (NZST)
Message-ID: <4057.194.158.217.187.1113835090.squirrel@194.158.217.187>
To: www-xsl-fo@w3.org

There is a number of limitations in the built-in Microsoft .NET Framework
XslTransform (System.Xml.Xsl.XslTransform) class which makes Microsoft
.NET XSLT compiler incompatible with DocBook stylesheets.

There is the patch for the latest docbook-xsl version (1.68.1) that fixes
these problems in FO stylesheets.  Please find additional information
here:
http://alt-soft.com/support_kb_docbook_and_net_xsltransform.jsp


Best Regards,
Altsoft Xml2PDF Team
http://alt-soft.com/products_xml2pdf.jsp



> -----Original Message-----
> From: XSL-FO@yahoogroups.com [mailto:XSL-FO@yahoogroups.com]
> On Behalf Of scasquiov squerniovsqui
> Sent: Friday, April 15, 2005 1:45 AM
> To: XSL-FO@yahoogroups.com
> Subject: [XSL-FO] which xslt processor for .net?
>
>
> I tried several XSLT processors but couldn't find one that
> worked with the Docbook to XSL-FO stylesheets from the
> docbook open repository and that could be embeded into my application.
>
> both .NET's classes for XSL Transformations and Saxon.NET
> don't seem to handle the stylesheets the way they should
> (several errors come up; from the info I could gather is
> seems there are some limitations in both these implementations).
> I found a lot of other XSLT processor but none of them seems
> to have .NET bindings so that it can be embedded into the application.
>  Invoking java's version of Saxon would work for example but
> I'm trying to avoid having external dependencies. Making sure
> java is installed would be another step in the installation
> process and I'd rather not have it.
>
>  Has anyone else needed to use docbook_to_FO stylesheets in .NET?
> which xslt processor have you used?
>
>
> thanks in advance!
Received on Monday, 18 April 2005 13:39:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 3 October 2007 16:06:13 GMT