[Doxygen-users] DocBook/XML

[Anton G S. <ag...@ml...>]

Hi all,

IMHO there is very good DTD for computer texts including API description. 
This is DocBook. The full information can be found on these web-sites:

http://www.oasis-open.org/docbook
http://www.docbook.org
http://nwalsh.com/docbook
http://web.oreilly.com/news/docbooklic_0901.html
http://docbook.sourceforge.net

With best regards,
        Anton Sergeev.

========================================================================
Message: 2
Date: Wed, 24 Oct 2001 15:58:12 -0700
From: Hunter Marshall <hma...@vi...>
To: dox...@li...
Subject: Re: [Doxygen-users] xml

On Thu, Oct 18, 2001 at 09:51:04PM +0200, Dimitri van Heesch wrote:
> On Thu, Oct 18, 2001 at 10:26:00AM -0700, Hunter Marshall wrote:
> > I will begin working with a smaller case. Is the doxygen.dtd file in
> > doxygen-1.2.11.1/addon/xmlparse the associated DTD? 
> 
> No, it is just something that could be used as a starting point ;-)
> Any help on writing a proper DTD is highly welcomed.

After playing with xsl/fop, I think that maybe the DTD structure might
be an area for experimentation. For example, I am finding that the
numbering control in XSLT (<xsl:number>) does not go outside a
sequence of sibling nodes. I suppose some cool XSL hacker could do
it. It's not like LaTeX where you can tap your own custom counter when
you want the next number value in a sequence.

What I mean is that the numbering works well for something like

chap
 sec
  subsec
  subsec
 sec
  subsec
chap
 sec
  subsec

Whereas the doxygen DTD (at a highlevel) looks like

compounddef
 compoundname
 sectiondef
  memberdef (the dtd and the output differ on this)
  memberdef
  memberdef
 sectiondef
  memberdef
 detaileddescriptio

I don't have any suggestions yet. I am just now realizing the impact
of DTD design on the ease of processing. 

                 hunter

PS Should this go to doxygen-develop? Or to a smaller group than
doxygen-users?