This is the mail archive of the
docbook@lists.oasis-open.org
mailing list for the DocBook project.
Re: attaching text to cmdsynopsis
- From: Norman Walsh <ndw at nwalsh dot com>
- To: davidw at dedasys dot com (David N. Welton)
- Cc: docbook at lists dot oasis-open dot org
- Date: Tue, 16 Jul 2002 05:35:09 -0400
- Subject: DOCBOOK: Re: attaching text to cmdsynopsis
- References: <877kjwvcxk.fsf@dedasys.com>
/ 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 |