Re: [docbook-apps] Multi-part document, multiple stylesheets

["Bob Stayton" <bobs at sagehill dot net>]

The process for customizing the chunking stylesheet is different from the
standard stylesheet.  It requires more setup because of the rules of import
precedence.  This page describes how to do it:

http://www.sagehill.net/docbookxsl/ChunkingCustomization.html

Your customized set template can go in the file described in step 1.

Bob Stayton
Sagehill Enterprises
DocBook Consulting
bobs@sagehill.net


----- Original Message ----- 
From: "Larry Garfield" <larry@garfieldtech.com>
To: <docbook-apps@lists.oasis-open.org>
Sent: Thursday, March 31, 2005 3:01 AM
Subject: Re: [docbook-apps] Multi-part document, multiple stylesheets


> Hi, Bob.
>
> I tried the first suggestion, customizing the match="set" template.
> However, as soon as I copy the template to my customization file the
> portion of the document that it matches gets printed to standard out
> rather than to a file.  It doesn't matter if I'm extending docbook.xsl,
> chunk.xsl, or onechunk.xsl, those only change how much gets printed to
> standard out instead of to files.  The set's TOC always ends up on
> standard out.
>
> Any idea what the problem is?  My initial thought is that the set
> template is getting processed "outside" of an output redirector
> statement now, but given the way I understand how the XSL file is
> compiled (which I do not guarantee to be accurate), that doesn't make
> sense.
>
> Bob Stayton wrote:
> > I have two suggestions.
> >
> > 1.  Create a small customization file that copies the match="set"
template
> > from html/division.xsl, and remove the last <xsl:apply-templates/> in
it.
> > That should generate the index.html file, but will skip generating the
rest
> > of the chunks.  It still has to load all the content, but at least it
> > doesn't have to write it all.
> >
> > 2.  Ask the Oxygen XML editor folks for a copy of their patched Xerces
> > parser that supports the 2001 namespace name in XIncludes.  They include
> > that with their product, so they might just let you download it.  It
would
> > be a great public service since the Apache folks are so slow in getting
out
> > a fixed version of Xerces.
> >
> > Bob Stayton
> > Sagehill Enterprises
> > DocBook Consulting
> > bobs@sagehill.net
> >
> >
> > ----- Original Message ----- 
> > From: "Larry Garfield" <larry@garfieldtech.com>
> > To: <docbook-apps@lists.oasis-open.org>
> > Sent: Sunday, March 27, 2005 3:25 AM
> > Subject: [docbook-apps] Multi-part document, multiple stylesheets
> >
> >
> >
> >>First off, thank yo to Bob and Michael.  I've since switched over to
> >>Saxon, XIncluder, and Ant and most of the technological issues seem to
> >>have finally been taken care of.  (And yes, I am using Debian.  Good
> >>eye.  I take it you are too. <g>)
> >>
> >>However, I'm now running into a design problem that I'd also appreciate
> >>some help on.
> >>
> >>I have/will be building a <set> of books, probably around 5 although at
> >>the moment I just have one marked up for testing.  The source is in a
> >>series of XML files across a few directories, brought together via
> >>XIncludes.  (set.xml is mostly xi:include directives to various books,
> >>each of which is mostly xi:include directives to various
> >
> > chapters/articles.)
> >
> >>Although all are similar, the outputs for each (HTML and PDF, just
> >>dealing with HTML for now) will be just different enough that I need to
> >>use separate customization XSL files for them.  (Different CSS links,
> >>for instance.)  OK, fine, run each one separately via Ant.  Except that
> >>I also want to generate an index/cover page for the whole set.  That
> >>requires running the scripts against the top set.xml file.  Of course,
> >>that also then generates files for the rest of the tree, which will not
> >>have the right customizations set.
> >>
> >>In addition, I'm using XIncluder as a preprocessor to generate a single,
> >>complete document before passing that to the rest of the targets.  I
> >>originally was using Xerces directly in the Saxon command, but the
> >>version of Xerces I have still has the bug in its XInclude URI string
> >>(2001 vs. 2003).  Being a nitpicky purist I didn't want to go through
> >>and put "wrong" namespaces in all of my documents, but I'm not sure how
> >>to link XIncluder in directly.  That means that in order to run each
> >>book separately, I'd have to run XIncluder on a portion of the source
> >>tree first for each one.  Since neither XIncluder nor Saxon is
> >>particularly speedy, that results in a very slow, very ugly build
> >>process.  I don't even want to contemplate how messy it would get once I
> >>added FO/PDF output as well.
> >>
> >>So the best I can come up with right now for the build process is
> >>something like:
> >>
> >>- XIncluder to resolve whole set.
> >>- Saxon on whole set to generate set's index.html.
> >>- XIncluder to resolve book A.
> >>- XIncluder to resolve book B.
> >>- XIncluder to resolve book C.
> >>- Saxon on book A temp file, overwrite what set generated.
> >>- Saxon on book B temp file, overwrite what set generated.
> >>- Saxon on book C temp file, overwrite what set generated.
> >>
> >>My mind is screaming at me that there has got to be a better, cleaner,
> >>less ugly way than that.  Can anyone point me in the direction of what
> >>that would be?  Many thanks.
> >>
> >>-- 
> >>Larry Garfield AIM: LOLG42
> >>larry@garfieldtech.com ICQ: 6817012
> >>
> >>"If nature has made any one thing less susceptible than all others of
> >>exclusive property, it is the action of the thinking power called an
> >>idea, which an individual may exclusively possess as long as he keeps it
> >>to himself; but the moment it is divulged, it forces itself into the
> >>possession of every one, and the receiver cannot dispossess himself of
> >>it."  -- Thomas Jefferson
> >>
> >>
> >
> >
> >
>
> -- 
> Larry Garfield AIM: LOLG42
> larry@garfieldtech.com ICQ: 6817012
>
> "If nature has made any one thing less susceptible than all others of
> exclusive property, it is the action of the thinking power called an
> idea, which an individual may exclusively possess as long as he keeps it
> to himself; but the moment it is divulged, it forces itself into the
> possession of every one, and the receiver cannot dispossess himself of
> it."  -- Thomas Jefferson
>
>