OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: One TOC and one glossary for multiple docbook XML files

> From : Bob Stayton [mailto:bobs@sco.com] 
> Since you are using olinks, you could use the olink targets
> database to create a master table of contents.  One could
> write an XSL stylesheet that generates a DocBook <toc>
> with <tocentry> elements from the database, following the DocBook DTD
> for <toc>.

Yes. The only problem is that the master target database does not have
any information related to order of documents. It only describes the
directories structure.
Thus, without this knowledge of how documents must be chained (I mean:
which XML should be the preface, which one the first chapter, etc...),
the main TOC would have a structure that follows the directory
structures, and not the chapters order...
I miss something: a document that contains both information (which XML
to proceed, their identifier, where to create the HTML, and how HTML
should be ordered in the main TOC).

I also thought about a main document which would include the other ones.
A book, for example, with a structure like this one:

<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
<book id="onlyone" xmlns:xi="http://www.w3.org/2001/XInclude">
  <title>The main doc</title>
  <xi:include href="xmldocs/doc1.xml" />
  <xi:include href="xmldocs/doc2.xml" />
  <xi:include href="xmldocs/doc3.xml" />

But in such a case, I have two problems:
- my original XML docs have sections with identifiers, and I do not know
if this identifier is unique once merged into my main document. In fact,
as many of my XML documents share the same internal structure, they do
use the same sections identifiers.
- the olinks would not work anymore.

Hum again...

I do not have any idea about the master glossary document. Should I
write glossary entries directly inside it, with olinks ? Or should I
collect local glossaries among my XML docs in order to build the master
glossary ??


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]