I'm adding support for the id fixup mechanism [1, 2] in the
clouddocs-maven-plugin [3]. To my mind, the most common use case (aside
from no fixup at all) will be to specify a prefix with global linkscope:
xi:include
href=foo.xml
db:idfixup=prefix
db:idprefix=second-
On 17.6.2014 17:07, David Cramer wrote:
xi:include
href=foo.xml
db:idprefix=second-/
Likewise, it should be an error to set db:idfixup to none, strip, or
auto and also to set a db:idprefix. Does that make sense?
That sounds reasonable. I should update spec and sample
Hi everybody,
I'm facing a problem with a customization... I want to inhibit the
presence of some object (such as rows, para, ...) in the generation of a
PDF document, and I was expecting that I could use the /_status=draft
_/attribute, but it doesn't work.
I've discovered that from DocBook
Using DB5 and the 1.78.1 stylesheets, my 'procedure' element is rendered in
HTML, but the anchors it produces in each 'step' element cause IE display
issues.
The procedure element and its 'step' children render as an ordered list in
HTML. For each step (list item in html), the anchor goes before
One simple solution is to set the stylesheet param
generate.id.attributes=1. That causes the stylesheet to replace named
anchor elements with id attributes. See if that fixes the problem.
Bob Stayton
Sagehill Enterprises
b...@sagehill.net
On 6/17/2014 10:51 AM, Tim Arnold wrote:
Using DB5
hi Bob,
Thanks for that fast response! Because the doc lives with a bunch of other
content that depend on named anchors I don't have a choice (rules from
webmasters);
I would much rather use id attributes if I could.
However, I did check and you are right--it prevents the problem and will be
a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 6/17/14, 10:12 AM, Jirka Kosek wrote:
...
That sounds reasonable. I should update spec and sample code to
use XInclude 1.1. I was waiting for XInclude 1.1 implementations
before doing this. I will not be able to attend tomorrow telcon,
but
