RE: how to influence dtd processing?

Subject: RE: how to influence dtd processing?
From: "Mark D. Anderson" <mda@xxxxxxxxxxxxxx>
Date: Thu, 03 Feb 2000 16:36:34 -0800
yikes. ok, no easy answer, and certainly none that is processor-independent,
which is part of what i'm trying to resolve to begin with.
so i guess i'll go with the Makefile approach:

xt:
       cp xt_entities.dtd xslt_entities.dtd
       $(XT) ...

xalan:
       cp xalan_entities.dtd xslt_entities.dtd
       $(XALAN) ...

latest:
       cp latest_entities.dtd app_entities.dtd

stable:
       cp stable_entities.dtd app_entities.dtd

my actual makefile is of course a lot more complicated, but you get the idea.
and i could have just done sed on a single file, but that interferes
with source control tool write protection.

-mda

--On Monday, January 31, 2000 9:32 AM +0000 Kay Michael <Michael.Kay@xxxxxxx> wrote:

nsgmls has a command line -i option whereby "-iname" is the same as:
<!ENTITY % name "INCLUDE">

i'd like to do the same thing with xt (or any xslt processor). but
i don't think they support it. i don't even see mention of how
this can be done via their various servlet apis

If you use the Java API to Saxon, it allows you to nominate a SAX parser of your choice. You could nominate a parser which is a simple subclass of John Cowan's ParserFilter (www.ccil.org/~cowan), which delegates all the work to a real parser but nominates its own EntityResolver. The EntityResolver could then select which DTD to use, or construct a DTD dynamically, based on some environment parameter.

Mike Kay


XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list



XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list



Current Thread