From: Bruce Horrocks <01.0032@granby.demon.co.uk>
Subject: Managing errata in documents
Date: Fri, 11 Jan 2002 13:03:12 +0000 [thread overview]
Message-ID: <FjFUluAQKuP8EwSs@granby.demon.co.uk> (raw)
Dear All,
What is the best way to manage errata for a printed document produced
using ConTeXt?
Suppose that I wish to produce a book that will be published. Obviously,
it is not going to be possible to re-print each time an error is found,
so I would like to be able to collect these together and produce an
errata sheet which can be distributed to those who have the book.
Is there a (simple) way of being able to make and tag the changes in the
original ConTeXt source files but process to produce an errata sheet
rather than a whole new book?
At the moment, the only thing that I can think of to do is to keep two
documents: the original book updated as errors are found, and a separate
errata sheet document which is also updated as each is found.
Does anyone have any experience of either approach that they are able to
share with us?
Regards,
--
Bruce Horrocks
Hampshire
England
bh@granby.demon.co.uk
next reply other threads:[~2002-01-11 13:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-11 13:03 Bruce Horrocks [this message]
2002-01-11 14:42 ` Berend de Boer
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=FjFUluAQKuP8EwSs@granby.demon.co.uk \
--to=01.0032@granby.demon.co.uk \
/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 NNTP newsgroup(s).