OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

docbook message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: DOCBOOK: Re: attaching text to cmdsynopsis


/ davidw@dedasys.com (David N. Welton) was heard to say:
| First of all, I hope this list is the right place to be asking this, a
| question about use of docbook, rather than the discussion of DTD
| itself!  If not, my apologies.

Perfect place to ask.

| I am documenting some commands:
|
|     <cmdsynopsis>
|       <command>Rivet_Script</command>
|       <arg>ChildExitScript</arg>
|       <arg><replaceable>script</replaceable></arg>
|     </cmdsynopsis>
|     <para>
|       Script to be evaluated when each Apache child process exits.
|     </para>
|
|     <cmdsynopsis>
|       <command>Rivet_Script</command>
|       <arg>BeforeScript</arg>
|       <arg><replaceable>script</replaceable></arg>
|     </cmdsynopsis>
|     <para>
|       Script to be evaluated before each server parsed (.rvt) page.
|     </para>
|
| I'd like to "attach" the text in the para tags to the cmdsynopsis, to
| make a unit out of it, in order to be able to process it better with
| XSL, and so on.

It might be easier to answer your question if you could provide a
little bit more context. Depending on how the rest of your document is
organized, I can imagine that a separate section for each command
might be appropriate.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com>      | I'm NOT in denial!
http://www.oasis-open.org/docbook/ | 
Chair, DocBook Technical Committee |


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC