Hi Nic,
I think your assessment is correct that the find.chunks template that generates the
chunk.hierarchy is processing the original namespaced nodes when it calls the chunk
template. So preceding-sibling::section would not be matched in that round of
processing. This looks like a bug in
Hi Dave,
This isn't a case of import precedence, but of different attributes. In general, the
qualified attributes (like space-before.optimum) take precedence over the
non-qualified attributes (like space-before). I wish the DocBook XSL stylesheets had
not been written using the qualified
If you want to use the original page master names, then the answer is yes, you must
customize that big template. If you want to use your own master names, then you can
use the user.pagemasters and select.user.pagemaster templates to write your own
original page masters.
Bob Stayton
Sagehill
On 08/07/2011 05:50 PM, Bob Stayton wrote:
Hi Dave,
This isn't a case of import precedence, but of different attributes.
In general, the qualified attributes (like space-before.optimum) take
precedence over the non-qualified attributes (like space-before). I
wish the DocBook XSL
On 08/07/2011 05:53 PM, Bob Stayton wrote:
If you want to use the original page master names, then the answer is
yes, you must customize that big template. If you want to use your
own master names, then you can use the user.pagemasters and
select.user.pagemaster templates to write your own
