On Thursday 12 December 2002 06:18 pm, David Abrahams wrote:
> Peter Simons <[EMAIL PROTECTED]> writes:
> > Douglas Gregor writes:
> > >> (4) It must be possible to link reliably from one library
> > >> documentation into another one.
> > >
> > > I don't like that as a requirement, but only because I don't know
> > > how to do it.
> >
> > Good point. Let's keep that as a "nice to have" and decide whether we
> > can do it when we know more about the processing engine. DocBook's
> > <olink> basically only says: "You can define it ... But how to _do_ it
> > is your problem."
> >
> > Clearly, if we're trying to do something like this, we're going beyond
> > the capabilities of XSLT.
>
> I understand the predicament, but we'd better figure it out. I need
> to write "this is an MPL metafunction..." in my docs and get a link to
> the MPL definition of metafunction.
You will, but it will require MPL's documentation to be generated along with
your documentation. Basically, the documentation for all Boost libraries will
be stuffed into one big document (via XIncludes) and that document will be
compiled/translated/transformed/whatever together so that all links can be
resolved at once.
What we're saying is that you can't build HTML for just MPL, then build HTML
for just Python, and expect links between the two to work. DocBook just isn't
set up for that AFAICT.
Doug
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
Boost-docs mailing list
[EMAIL PROTECTED]
Unsubscribe and other administrative requests:
https://lists.sourceforge.net/lists/listinfo/boost-docs
