On Sunday 08 December 2002 09:05 am, Douglas Gregor wrote:
> On Sunday 08 December 2002 03:43 am, Peter Simons wrote:
> > P. S.: I see that "boost.xml" uses the XInclude module to refer to
> > sub-parts of the document via <xi:include .../>. Can I convince you to
> > use the "XML way" instead? This would be that you define a parameter
> > entity refering to the document:
>
> [snip good reasons]
>
> Sure. We'll use entities instead of XIncludes. The fact that Saxon doesn't
> handle XIncludes should have been a warning flag...
>
> Doug
On second thought, it's not so clear-cut. The benefit of using XIncludes is
that the included documents can themselves be valid XML documents, from which
we can generate fragments of the Boost documentation. Fragments take less
time to generate (e.g., when we're writing documentation and want to see the
output without waiting for _all_ of the Boost documentation to be
regenerated) and may be useful if a user wanted to, say, generate a
self-contained document for a subset of Boost libraries.
Also, can entities be recursive? When you declare an entity, it can't have its
own !DOCTYPE, so can it have its own !ENTITYs? We can't expect all of the
documentation for each library to be in a single big XML file.
Doug
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Boost-docs mailing list
[EMAIL PROTECTED]
Unsubscribe and other administrative requests:
https://lists.sourceforge.net/lists/listinfo/boost-docs
