Thanks Bob, that worked perfectly. I just had to remove all of the "d:"
prefixes to the legalnotice references, but after that it worked just fine.
Eric
-Original Message-
From: Bob Stayton [mailto:b...@sagehill.net]
Sent: Friday, April 26, 2013 12:44 PM
To: Eric Nordlund; docbook-apps@
Hi Richard,
What you want isn't possible with just the existing attribute-sets. If you
want to pursue a customization, I can give some guidance.
There are two levels of formatting in the FO table of contents: mode="toc" and
toc.line. The document hierarchy is processed in mode="toc", and ther
Dear Richard,
briefly, your proposal needs advanced customizations.
But to be honest, I still prefer a default behavior.
I‘ve already had to defend my opinion several times. Our graphics designers
wished the same thing, but none of them was aware of several typographic
issues:
1. I
I think so. You can try this (untested):
1. Copy the template with match="d:legalnotice" mode="titlepage.mode" from
html/titlepage.xsl to your customization layer.
2. Change the match attribute to
match="d:legalnotice[not(preceding-sibling::d:legalnotice)]"
so that only the first legalno
Hello. The source files for my company's books all have 4 legalnotice tags on
them. This is fine in the PDF output, but in the HTML output I get 4 legal
notice links on the front page.
Is there a way to funnel all of the legalnotice content into one legalnotice
page and corresponding link in th
I'm working on a docbook document which I am currently trying to process to PDF
via FO.
The document is an .
I'm generally copying the formatting of an existing set of Word documents.
In particular at the moment I'm looking at the appearance of the ToC pages.
In the standard stylesheets,
Hi Edwin,
I, for one, would like to encourage the kinds of innovations that you are
suggesting. From my perspective, these would not necessarily be included in
the stock distribution, but could be a customization layer made available to
anyone who wants them.
As a start, I'd like to distinguis
