Hi Bob,
Yes, there seem to be one of those custom page sequence thingies:
|
|
|
|
This is from code I just copied (from this list) to remove all the page
breaks everywhere.
Any idea what I need to do to get the first page treated separately?
/Tomas
On 2016-11-13 23:33, Bob
Hi Bob,
This does not seem to work. I already modify the space-* values in that
attribute set, so I just added your middle six lines. I also tried to
remove the choose/when bit, but in both cases the BNF were in normal
font size, not xx-small.
/Tomas
On 2016-11-13 23:51, Bob Stayton
Hi,
I've updated in github to support saxon9HE, but it's not in a tagged
release yet. to use it:
xslcoverage report run saxon9he [saxon options and args]
Note that I've noticed some regressions in tracing since release 6.5.5.
The side effect is that some covered instructions appear as not
Hi Tomas,
Since the font-size change is being made on the same element that uses
an attribute-set, you can customize the attribute-set instead to make
the font-size conditional on the element. An attribute-set is evaluated
each time it is applied.
For example:
xx-small
Hi Tomas,
I'm not able to duplicate this problem. When I copied your
header.content template into an otherwise empty customization layer and
processed an article, the header on the first page is blank.
The header.content template is called each time a page sequence is being
set up, in the
I would be willing to help with this effort, but not lead it. If
someone were willing to evaluate better alternatives and integrate the
code into DocBook's webhelp, I could write the XSL templates that
generate the index files.
Bob Stayton
Sagehill Enterprises
b...@sagehill.net
On
