The short answer is no, xmllint does not successfully validate DocBook 5
documents that are in fact valid.
I normally use Jing to validate DocBook 5. I've not seen it hang like you
have.
Bob Stayton
Sagehill Enterprises
b...@sagehill.net
--
Fr
Hi Erik,
Setting a completely empty 'generate.toc' param is a little too much it
seems. Instead of:
use one that specifies only the title for a book toc:
book title
That will generate the title for the relocated toc, with one glitch. If you
are using the default 'header.content' templat
When choosing to place the TOC of a book after the book's preface, it
appears that one loses[*] the TOC's generated title as a side-effect.
That is, when following the recipe in this URL:
https://lists.oasis-open.org/archives/docbook-apps/200705/msg00023.html
What's the best approach to make
Hi,
I looked into this some more. Seeing strange characters in DocBook XHTML
output usually means the browser thinks the file has iso-8859-1 encoding
instead of the UTF-8 encoding that is the DocBook XHTML default. It is the
case that browsers should read either the encoding attribute of the
Hi Bob, List,
I don't know if this a new thread or a continuation of what has been discussed
below. I set up some olinks on a set of very simple documents for testing
purposes (only transformed to pdf at this stage) and they were working fine.
However, I have now incorporated olinks into som
Hi Robert,
On Fr, 2013-10-25 at 22:23 -0500, Robert Nagle wrote:
> As you know, MS Word automatically changes quotes to smart quotes and so my
> docbook source in Oxygen editor includes smart quotes and not normal
> quotes.
I think the best way to generate quotes in DocBook is using the
element
I'm trying to validate some documents generated by the db4-upgrade.xsl from
existing (validating) db4 documents. Validating the resulting db5 results in
mysterious errors that don't seem to correspond to actual problems. Eventually I
figured out that if I inlined content that had originally be
