Re: [Refdb-devel] new-document and doc-processing menu behavior

[Michael S. <sm...@xm...>]

Bruce D'Arcus <bd...@fa...> writes:

> 
> On Dec 9, 2003, at 7:16 PM, Markus Hoenicka wrote:
> 
> >Bruce D'Arcus writes:
> >>>Use XInclude's and have RefDB call xsltproc to process those?
> >>
> >>Can RefDB already handle this Markus?  I want to avoid using entities
> >>altogether.
> >
> >I didn't follow this discussion. At which stage of the document
> >processing would this come into play?
> 
> In other words, I want to process citations and bibs for my entire book 
> project, which is assembled via xincludes in a document called 
> book.xml.  They serve the same function as the current entities that 
> specify the chapter files.

It seems like nothing much actually needs to be changed in the RefDB
tool chain to support processing a doc that uses XIncludes.

I think the only toolchain fix needed is to change a couple lines in
refdbxml so that it always calls xsltproc with the "--xinclude" option. 

Then, the docs could just be updated to mention using Xincludes; e.g.,
the tutorial doc would say:

   ... At a location where such a [div or bibliography] element is
   valid, either include the external entity itself or an Xinclude
   element that references the entity, like in the following chunk:

     ..
       </chapter>
       &bibliography;
       </book>

     or 

     ..
       </chapter>
       <xi:include href="&bibliography;" xmlns:xi="http://www.w3.org/2001/XInclude"/>
       </book>

And if you really wanted to do away with the bibliography entity
entirely in an XML doc, you could instead just reference the file name
of the bibliography directly, like this:

  <xi:include href="refdbtest.bib.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>

If you did that, and you're editing in nXML mode, you could also just drop
the document prologue entirely; otherwise, you could, if you wanted to, at
least get rid of the entity declaration in the internal subset.

  --Mike