From: Gerben Wierda <Sherlock@rna.nl>
Subject: ConTeXt project structure?
Date: Tue, 22 Jul 2003 11:14:35 +0200 [thread overview]
Message-ID: <E994315C-BC24-11D7-913B-000A95901A7E@rna.nl> (raw)
It is probably my lack of brain cells, but I do not understand chapter
2 of the ConTeXt manual at all.
Suppose I have a manual-like document and I want to produce different
PDF-files out of it:
1. The book
2. The book in another layout
3. The book in screen format with navigation
4. A simple presentation with bullet points, one or more pages per
chapter
As I understand it I will need 4 environments:
.../foo/bookenv.tex
.../foo/book2env.tex
.../foo/bookscreenenv.tex
.../foo/presentation.tex
and I can put each chapter in a component file, i.e. chapter1.tex,
chapter2.tex etc.
.../foo/chapter1.tex
.../foo/chapter2.tex
But here my understanding stops.
- Should I create a project file for each of the 4 modes above? And put
these in different subdirectories as in:
.../foo/book/book.tex
.../foo/book2/book2.tex
etc.? Or do I use multiple environments in one project and I can get 4
PDF's as a result? Or are these multiple products (I would guess this,
but how then to set it up)? Should my chapter files contain
\startcomponent \stopcomponent and does that mean they are
independently compilable?
I have been reading and re-reading this, but the relation between
project, environment, component and product keeps escaping me.
Is there a good example somewhere?
next reply other threads:[~2003-07-22 9:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-22 9:14 Gerben Wierda [this message]
2003-07-22 12:05 ` Willi Egger
2003-07-22 13:35 ` Henning Hraban Ramm
2003-07-29 14:44 ` Gerben Wierda
2003-07-30 1:56 ` Matthias Weber
2003-09-03 15:55 ` Patrick Gundlach
2003-09-04 19:31 ` Hans Hagen
2003-09-04 21:19 ` Patrick Gundlach
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=E994315C-BC24-11D7-913B-000A95901A7E@rna.nl \
--to=sherlock@rna.nl \
--cc=ntg-context@ntg.nl \
/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).