This is the mail archive of the xsl-list@mulberrytech.com mailing list .

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: OT: ICFP 2001 (xsl solution?)

To: xsl-list at lists dot mulberrytech dot com
Subject: Re: [xsl] OT: ICFP 2001 (xsl solution?)
From: Mark Nahabedian <naha at ai dot mit dot edu>
Date: Fri, 27 Jul 2001 11:36:56 -0400 (Eastern Daylight Time)
References: <9891913C5BFE87429D71E37F08210CB9081D26@zeus.sfhq.friskit.com><15201.30374.762000.619586@gargle.gargle.HOWL><200107271449.PAA07744@penguin.nag.co.uk>
Reply-To: xsl-list at lists dot mulberrytech dot com

David Carlisle writes:
 > 
 > > The input language isn't valid XML, there are tags whose names start
 > > with digits.
 > 
 > sed -e "s/</<x/g" $1 > tmp.xml ; saxon tmp.xml icfp.xsl

Well, you'll need to deal more appropriatly with the close tags, but
I get your point.

My point, trivial as it was, was that an XSLT processor was not
sufficient unless its XML parser was permissive.

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

Follow-Ups:
- Re: OT: ICFP 2001 (xsl solution?)
  - From: Francis Norton

References:
- OT: ICFP 2001 (xsl solution?)
  - From: Piers Haken
- OT: ICFP 2001 (xsl solution?)
  - From: Mark Nahabedian
- Re: OT: ICFP 2001 (xsl solution?)
  - From: David Carlisle

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]