RE: [xsl] Path for a DTD : proposition

Subject: RE: [xsl] Path for a DTD : proposition
From: "Kaganovich, Yevgeniy (Eugene)" <ykaganovich@xxxxxxxxxxx>
Date: Tue, 27 Feb 2001 13:00:34 -0800
You can write an EntityResolver to set DTD to anything you please during
parsing. It would probably be a useful functionality of XSLT processor
command-line options to be able to specify a local DTD file and create an
EntityResolver that uses that file instead of the remote version. It's
definitely not part of XSLT spec.

- Eugene

: -----Original Message-----
: From: Paul Terray [mailto:terray@xxxxxxxxxxxx]
: Sent: Tuesday, February 27, 2001 9:46 AM
: To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
: Subject: Re: [xsl] Path for a DTD : proposition
: 
: 
: At 10:25 27/02/01 +0000, you wrote:
: 
: > > How about catalog support in 1.1?
: >
: >Catalog support is irrelevant to XSLT, surely.
: >It's a good thing (on the whole) but it's a feature of the XML parser
: >used not of the XSL system. If your XML parser supports catalogues
: >then you can use them with XSLT 1.0.
: >
: >David
: 
: That's right, however, xslt processors are usually the kind 
: of process you 
: launch from command-line. That's why it is the kind of 
: process where you 
: need the most a catalog.
: 
: I still think, however, that a catalog is a solution that is 
: too heavy for 
: most problems. Perhaps an alternative would be good ? That's 
: how Omnimark 
: work, for example.
: 
: 
: --
: Paul TERRAY - Documents Management Systems Engineer
: 4Dconcept
: Centre d'affaires - 22, rue Etienne de Jouy
: 78353 Jouy en Josas CEDEX
: FRANCE
: Tel. +33 (0)1 34 58 70 70 - Fax. +33 (0)1 39 46 06 90
: email : terray@xxxxxxxxxxxx 
: 
: 
: 
:  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