Cart
[Home] [By Thread] [By Date] [Recent Entries]
Probably so, Adam, but as I recall, the XML parser isn't required to per se, so as a general solution, it may not be reliable. Also, the self-documenting solutions I've liked also included the HTML namespace in the documentation element so one gets a nicer layout defined right up front. Six of one, half dozen of the other. All considered, for non-documentation element systems, Ken's solution is the best, IMHO. len -----Original Message----- From: Adam Turoff [mailto:ziggy@p...] Sent: Monday, October 28, 2002 3:08 PM To: AndrewWatt2000@a... Cc: xml-dev@l... Subject: Re: Documenting XSLT (Was: Note from the Troll) On Mon, Oct 28, 2002 at 04:00:58PM -0500, AndrewWatt2000@a... wrote: > In a message dated 28/10/2002 20:53:24 GMT Standard Time, ziggy@p... > writes: > > <xsl:template match="xsl:template/comment()"> > > <!-- Here's a template to "automatically generate documentation..." --> > > ... > > </xsl:template> > > > > And what happens if the parser happens not to pass on information about > comments? Every XSLT processor I've met passes on comments, and makes them available through the comment() function. The solution you see above is an XSLT based one. Z. ----------------------------------------------------------------- The xml-dev list is sponsored by XML.org <http://www.xml.org>, an initiative of OASIS <http://www.oasis-open.org> The list archives are at http://lists.xml.org/archives/xml-dev/ To subscribe or unsubscribe from this list use the subscription manager: <http://lists.xml.org/ob/adm.pl>
|
