On Tue, 4 Feb 2003, Jeff Garland wrote:
> > Great! I'll keep the issues list on the Wiki updated; the main issue is
> > still matching up namespace-level functions to their headers. Until that's
> > solved, we're not going to get any of those functions into BoostBook :(.
>
> Seems to me we can use the compounddef for the namespace to extract this. Under
> this element there is a <sectiondef kind="func"> that has a list of all the
> functions defined in the namespace including the header file. Was there some
> reason you didn't use this?
Maybe I missed it? I don't have access to the Doxygen XML output at the
moment, but I'll try this out later. If this works out, we might not even
need to ask for changes to Doxygen. 1.2.18 might "just work".
> One of the other ones you had on the Wiki:
>
> >Tags that should be empty (e.g., an empty briefdescription or detaileddescription)
> >are not actually empty in the XML output. Instead, they are output with extra
>(significant!)
> >whitespace as:
> > <briefdescription>
> > </briefdescription>
>
> What exactly is the issue here? The whitespace gets carried into the final html?
>
> Jeff
I'd really prefer that empty description elements not even appear in the
output. If they do appear, they should probably be
<briefdescription/>
I've actually worked around the problem (and learned a little more XSLT
in the process), so perhaps it's a non-issue at this point.
Doug
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Boost-docs mailing list
[EMAIL PROTECTED]
Unsubscribe and other administrative requests:
https://lists.sourceforge.net/lists/listinfo/boost-docs
