From: Norman Walsh <ndw@nwalsh.com>
To: Peter Toft <pto@sslug.dk>
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: <87ya307muv.fsf@nwalsh.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0007151938470.855-100000@laptop.linus.dk>
/ Peter Toft <pto@sslug.dk> was heard to say:
| 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.
|
| Any clues on how to proceed in splitting books in
| practice could help.
The DSSSL stylesheets support OLink which can help you do this.
See http://nwalsh.com/docbook/dsssl/doc/olinksemantics.html
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | A man is not necessarily intelligent
http://nwalsh.com/ | because he has plenty of ideas, any
| more than he is a good general because
| he has plenty of soldiers.--Chamfort
next 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 [this message]
2000-12-27 6:36 ` Peter Toft
2000-12-27 6:36 ` Eric Lee Green
2000-12-27 6:36 ` Peter Toft
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=87ya307muv.fsf@nwalsh.com \
--to=ndw@nwalsh.com \
--cc=docbook-tools-discuss@sourceware.cygnus.com \
--cc=pto@sslug.dk \
/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).