From: Peter Toft <pto@sslug.dk>
To: docbook-tools-discuss@sourceware.cygnus.com
Subject: 6 Linux books in DocBook, and so what ...
Date: Mon, 02 Oct 2000 13:24:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.21.0010022215030.12910-100000@pto.sslug> (raw)
Message-ID: <20001002132400.SdztuyLdOBgijRyNgKsis6tYONqAeRI_CqeFrL54WB8@z> (raw)
I have had many good hints from this list, hence I try
again.
I have 6 Linux books written in DocBook, and each of
them have their seperate index. However it could be
cool if I could make a mega-book containing the 6 books
+ one joint mega-index :)
Actually I made one book - it kept growing, hence we
did split that one, but some people would like to have
the benefit of one index (especially) in the HTML
version.
It seems that I can use the <set> tag to make the
mega-book and then I had to consider the index. I can
make an additional new <book> within the <set> which
contains the index, but it seems clumsy that I have to
add that book (named index - with one item in it -
named index). Can I make a smarter trick here???
BR
--
Peter Toft, Ph.D. [pto@sslug.dk] http://www.sslug.dk/~pto
"You don't win a battle by asking, `Will we win?'
You win it by doing your best to win"
- Richard M Stallman
----> Visit http://petition.eurolinux.org <---
next reply other threads:[~2000-10-02 13:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-27 6:36 Peter Toft [this message]
2000-10-02 13:24 ` Peter Toft
2000-12-27 6:36 ` Norman Walsh
2000-10-02 13:31 ` Norman Walsh
2000-12-27 6:36 ` Peter Toft
2000-10-02 13:34 ` Peter Toft
2000-12-27 6:36 ` Norman Walsh
2000-10-02 13:56 ` Norman Walsh
2000-12-27 6:36 ` Bill Campbell
2000-10-02 15:34 ` Bill Campbell
2000-12-27 6:36 ` Eric Bischoff
2000-10-10 1:39 ` Eric Bischoff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.21.0010022215030.12910-100000@pto.sslug \
--to=pto@sslug.dk \
--cc=docbook-tools-discuss@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).