From: Peter Toft <pto@sslug.dk>
To: Eric Lee Green <elgreen@iname.com>
Cc: docbook-tools-discuss@sourceware.cygnus.com
Subject: Re: Book split to several books
Date: Wed, 27 Dec 2000 06:36:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.21.0007152041120.855-100000@laptop.linus.dk> (raw)
In-Reply-To: <00071511261800.24882@ehome.inhouse>
On Sat, 15 Jul 2000, Eric Lee Green wrote:
> On Sat, 15 Jul 2000, Peter Toft wrote:
> > Now I have to split the book into 4-5 parts, but I like
> > feedback on how to do this in an optimal way. My
> > problem is that I have many cross-references which will
> > suffer from the split.
> >
> > I have looked into using <part> which presumably
> > enables me to keep correct cross-references, but I
> > really would like to compile the sub-books
> > individually now - currently it takes too much time to
> > make PS, PDF, and HTML.
>
> Unfortunately your two goals (seperate compilation, extensive cross-references)
> are incompatible. Splitting your document into parts or multiple files on disk
> is easy enough -- "Docbook -- The Definitive Guide" tells you how to do that
Agree - no problem - I have 13 files at the moment.
> within the first few pages. But if you want cross-references, or a common
> index, well, the document processing system is going to have to chew through
> each of the documents to find all of those references.
Hrrm - my idea could be that book-A makes a summary
file, book-B the same .... and book-N can use check
cross-references to the other books by reading these
summary files (with the relevant labels) - which then
have to be available.
It could be cool, that book-N automatically could have
Take a look into <xref linkend="hardcoreLinux">
being expanded to
Take a look into the book "Peter Toft; Linux for the
cool dudez - section 3.1"
if the label hardcoreLinux is found in book-A
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 <---
prev parent reply other threads:[~2000-12-27 6:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-27 6:36 Peter Toft
2000-12-27 6:36 ` Norman Walsh
2000-12-27 6:36 ` Peter Toft
2000-12-27 6:36 ` Eric Lee Green
2000-12-27 6:36 ` Peter Toft [this message]
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.0007152041120.855-100000@laptop.linus.dk \
--to=pto@sslug.dk \
--cc=docbook-tools-discuss@sourceware.cygnus.com \
--cc=elgreen@iname.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).