Hi Bob,
now that you have explained it, I now understand my own question ! Thanks.
I will be writing both documentation (English French) in a single
document (or xinclude), which is not the scenario which publican was
designed for. I'll use profiling.
Thanks.
On Mon, Mar 14, 2011 at 10:01
I recently hit a problem with nested indexterms. While nesting an indexterm
within an indexterm is invalid it seems there is a loop hole.
If you put the systemitem tag within the primary tag then it allows an
additional indexterm which is valid in a systemitem tag.
I have not tried other tags.
Hello,
I do have a problem when assembling new documents with xincludes, turning
external olinks to internal links by using entity-references, as it is
described here:
http://www.sagehill.net/docbookxsl/modular-olinks.html
I put a reference to an external entity-declaration in a master
In the default titlepage template for glossary, the title is formed from:
title t.named-template=component.title [...]
That seems wrong! In the manual that I'm hacking, that used the book's title at
the top of the glossary.
Changing it to use division.title made the expected glossary/title
Hi,
So it seems that the entities are being resolved before the include takes
place?
Yes, that is the case. Entities are resolved by the XML parser, and XML
parsing must take place before an XInclude can proceed. It is mentioned at the
end of the last bullet in this section:
