RE: [xsl] coping with missing external document

Subject: RE: [xsl] coping with missing external document
From: Wendell Piez <wapiez@xxxxxxxxxxxxxxxx>
Date: Thu, 31 Jul 2008 09:58:48 -0400

At 05:33 AM 7/31/2008, you wrote:
I'm using Saxon for all XSLT work in the project apart from the pathway into
and out of FrameMaker. Frame has some features which technical authors like
very much, so I need to support it. Unfortunately there appears to be no way
to change the XSL processor which Frame uses, we're stuck with Xalan.

No, but one can use a 1.0 identity transform with Xalan under Frame and run the XSLT engine of your choice outside it to generate whatever XML Frame wants.

Or a near-identity transform, if you can encapsulate things you always have to worry about (such as output encoding or whatever) and handle them there.

A potential downside to this would depend on who has to run the transforms and what they have to install to do it. That might not be a difference that makes a difference.


====================================================================== Wendell Piez mailto:wapiez@xxxxxxxxxxxxxxxx Mulberry Technologies, Inc. 17 West Jefferson Street Direct Phone: 301/315-9635 Suite 207 Phone: 301/315-9631 Rockville, MD 20850 Fax: 301/315-8285 ---------------------------------------------------------------------- Mulberry Technologies: A Consultancy Specializing in SGML and XML ======================================================================

Current Thread