RE: node lists

Subject: RE: node lists
From: Avi Kivity <Avi@xxxxxxxxxxxxx>
Date: Tue, 2 Mar 1999 13:22:15 +0200
On Tuesday, March 02, 1999 12:30, Joerg F. Wittenberger
[SMTP:Joerg.Wittenberger@xxxxxxxxx] wrote:
> Hello folks,
> 

<...>

> 
> <hld>
> <intro>
> <para>bla bla</para>
> <extinterface>
> <dataobjects>
> <para>blub</para>
> 
> Should be processed like this docbook equivalent:

> <book>
> <chapter><title>hld</title>
> <section id="hld.intro"><title>Introduction</title>
> <para>bla bla.</para>
> </section>
> <section id="hld.extinterfaces>><title>External Interfaces</title>
> <section id="hld.extinterfaces.dataobjects>
>  <title>Dataobjects</title>
> <para>blub</para>
> </section>
> </section>
> </chapter>
> </book>
> 

Your statement of the problem contains the (rather, a) solution.

If you write a variant of the sgml identity transform which expands the new
elements into standard docbook elements, omitting elements as required,
expanding subdocs, and generally wreaking havoc on the source, you can use
docbook in a second pass to achieve the correct formatting, with possibly no
changes at all to the stylesheet. 

Once the transformation language is implemented, it may be possible to feed
the result of a transform directly to the style engine, eliminating the need
for two passes (sort of like unix filters: cat ... | grep ... | sed ... |
sort ... | uniq > /dev/null)



---
"The only words which have meaning are the last ones spoken"


 DSSSList info and archive:  http://www.mulberrytech.com/dsssl/dssslist


Current Thread