On Sun, Sep 6, 2009 at 8:32 PM, Bob Staytonb...@sagehill.net wrote:
Hi Karen,
Yes, the example you provided is correct.
It's really just the one in your book, rephrased so that I'm
absolutely sure what I'm doing. Which helped!
I'm afraid there is some ambiguity in the use of document,
I think you are calling the id attribute of the root element of each file
the document id, but that isn't an official XML term. It just means the
id of the document's root element.
Ok -- I'm not as clear on this as I thought.
In the following, can the xml:id function as the document id
This is half a DocBook question and half a process question for
anyone on this list working in a distributed DocBook production
environment where for a particular assembled document you are
generating at least one common glossary. (In this case, the assembled
document is planned as a set with two
It works for my partner too, so obviously I have something in my
environment that needs tweaking.
Thanks for your help.
Bob Stayton wrote:
Hmm, that's odd. It worked for me. Can you provide more details?
Bob Stayton
Sagehill Enterprises
b...@sagehill.net mailto:b...@sagehill.net
Karen,
For a simple distributed DocBook production environment, I'd
suggest a Subversion repository that all authors use for their
individual parts, as well as shared parts (like the glossary).
I'd use a glossary database (Chapter 17 of Bob's book) that is
writable by any author. Authors can
Yes, setting xml:id=filenames in the chapter element is fine. I'm not
sure what you mean by without any additional declaration, though. All
elements in DocBook 5 allow an xml:id attribute, so putting one on the
chapter element does not require any further declaration. You can put an
xml:id
Great - Thanks Bob.
This all came about when I needed to render a table in PDF that had no borders,
but had one cell on the bottom of the table that needed a bottom line, but I
could not render it because the rowsep does not work on the bottom cell
because the outer table line would overwrite
