ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm <hraban@fiee.net>
Subject: Re: ConTeXt project structure?
Date: Tue, 22 Jul 2003 15:35:04 +0200	[thread overview]
Message-ID: <4D4EAA1E-BC49-11D7-B3A7-0030659899AA@fiee.net> (raw)
In-Reply-To: <002201c35049$8d3c7490$0100a8c0@vademecum>

>> .../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
>>
> You can do this. It might be worthwhile to think about making the 
> chapter a
> product, then you keep the possibility to add components if the size 
> of the
> chapters is too large.

I won't do that...

>> 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
>
> No, use modes in the environment file.

Or use products if the content is very different.

>> Is there a good example somewhere?
> Whether is is a good example you will have to decide...

Perhaps have a look at my ConTeXt tutorial (german), it uses the 
structure.
Link below or directly 
http://www.ramm.ch/fiee/texnique/material/fiee_source.zip

Grüßlis vom Hraban!
-- 
http://www.fiee.net/texnique/?lang=en

  reply	other threads:[~2003-07-22 13:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-22  9:14 Gerben Wierda
2003-07-22 12:05 ` Willi Egger
2003-07-22 13:35   ` Henning Hraban Ramm [this message]
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=4D4EAA1E-BC49-11D7-B3A7-0030659899AA@fiee.net \
    --to=hraban@fiee.net \
    --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).