Subject: RE: [xsl] xslt 2.0, use case wanted. From: "Willink, Ed" <Ed.Willink@xxxxxxxxxxxxxxx> Date: Tue, 6 Apr 2004 09:38:40 +0100 |
> Template > names and mode names are not things that a stylesheet > normally manipulates > at run-time Except that they are very useful for diagnostics. An output file should be able to log its creation mechanism. I regularly code a catch-all template match for unexpected elements. It is tedious having to retype the template mode, and not uncommon to have to debug a wrong diagnostic resulting from a lazy cut and paste. Regards Ed Willink ------------------------------------------------------------------------ E.D.Willink, Email: mailto:EdWillink@xxxxxxx Thales Research and Technology (UK) Ltd, Tel: +44 118 923 8278 (direct) Worton Drive, or +44 118 986 8601 (ext 8278) Worton Grange Business Park, Fax: +44 118 923 8399 Reading, RG2 0SB ENGLAND http://www.computing.surrey.ac.uk/personal/pg/E.Willink ------------------------------------------------------------------------
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] xslt 2.0, use case wanted, David . Pawson | Thread | RE: [xsl] xslt 2.0, use case wanted, Willink, Ed |
RE: [xsl] Using a custom URIResolve, David . Pawson | Date | RE: [xsl] xerces2 Element type "xsl, Andrew Welch |
Month |