This is the mail archive of the
docbook@lists.oasis-open.org
mailing list for the DocBook project.
Re: generating a reference manual from source code
- To: docbook at lists dot oasis-open dot org
- Subject: Re: DOCBOOK: generating a reference manual from source code
- From: Norman Walsh <ndw at nwalsh dot com>
- Date: Tue, 29 May 2001 15:16:00 +0200
- References: <3B0E94B7.39FD32DA@sympatico.ca>
/ Stefan Seefeld <seefeld@sympatico.ca> was heard to say:
| However, in case of docbook I'm missing a couple of entities (or is it just
| the documentation that lacks...?): typedefs, modules, enums for example
| are missing.
DocBook is intended for software documentation, not necessarily a
complete representation of all the abstract syntax elements of a
particular language.
I'm not sure exactly what you're generating, but I suggest that a good
working solution is to use a role attribute to distinguish between the
cases on some more general element.
|
| Is there any document that I could consult to get more information about
| the kind of problem I'm trying to solve ?
The documentation for the new OO elements needs to be updated.
ASAP.
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | The common excuse of those who
http://www.oasis-open.org/docbook/ | bring misfortune on others is that
Chair, DocBook Technical Committee | they desire their
| good.--Vauvenargues
------------------------------------------------------------------
To unsubscribe from this elist send a message with the single word
"unsubscribe" in the body to: docbook-request@lists.oasis-open.org