Hi,
Thanks to a previous post reply from Bob Stayton
(https://lists.oasis-open.org/archives/docbook-apps/200804/msg00086.html),
I have been able to build an article PDF doc with an index with multiple
columns. However, this results in an FOP error:
Property ID x (found on fo:block)
You can create additional xsl:when clauses and use the 'pageclass' param
passed to the footer.content template. Something like
test=contains($pageclass, 'index') will be true when the page-sequence
is for the index.
The possible values of pageclass are described in this doc:
Oystein:
Just a thought, I have seen this error before, and generally (in my case) this
has to do with the content.
Particularly when combining smaller modular docs into a larger book or set.
We use an ID=attribute attribute for every section, sect1, sect2, etc.
When combining sections if
Frank Arensmeier [mailto:farensme...@gmail.com] wrote:
I'd like to chime in here for a second or two. I think it is also important
to ask
in which direction Docbook (and other XML standards too for that matter)
need to evolve in the near future. If you look at marketshare for desktop
Not quite. The current xhtml5 stylesheet converts a DocBook videodata
element to an HTML5 video element, but does not handle multiple
source children. The DocBook TC today approved allowing multiple
videodata children of videoobject, so now the stylesheet can be changed
to support a single
On Fri, 2013-12-06 at 11:48 -0800, Bob Stayton wrote:
Hi Peter,
The quality of the indenting depends on the XSLT processor. All that
DocBook XSL is doing is passing along the setting to the processor. The
stylesheet does not perform any indenting. What XSLT processor are you
using?
