From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Several environments in a project?
Date: Tue, 19 Jun 2007 02:45:02 -0400 (EDT) [thread overview]
Message-ID: <alpine.WNT.0.99.0706190214510.1080@nqvgln> (raw)
In-Reply-To: <C28E3051-907F-44FD-85F5-F08760E36FCB@gmx.net>
On Mon, 18 Jun 2007, fiëé visuëlle wrote:
> Am 2007-06-18 um 12:50 schrieb nicola:
>
>> I have a project with a few products sharing the same layout, which is
>> specified in a global environment file. Each product is in a separate
>> subdirectory together with its components. Then, I want to put some
>> setups and figure definitions in product-specific environments and
>> I do
>> it like this:
>>
>> \startproduct OneProduct
>> \project MyProject
>> \environment OneProductDir/LocalEnvironment
>> ...
>>
>> The problem is that the local environment is not read when I typeset a
>> particular component, but only when I typeset the whole product.
>> How can
>> I fix that?
>
> Put your product specific settings in the product file.
AFAIU, they will not be executed. There is really no clean way of
doing this without adding extra markup. Suppose I have a product file
which says
\startproduct product \environemnt env1 \environemnt env2
Title Text
\component one
\component two
\stopproduct
and a component
\startcomponent one
\product product
text
\stopcomponent
How can TeX parse the product file without typesetting title text? It
would have been simple if title text was surronded by some markup, but
it is not. This is one of the reasons projects are not supposed to
have any matertial that will be typeset.
So, the short answer is just add \environment commands in your
components. Another way is to use localenvironments in your
environment file, but I have never used them myself.
Aditya
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2007-06-19 6:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 10:50 nicola
2007-06-18 21:24 ` fiëé visuëlle
2007-06-19 6:45 ` Aditya Mahajan [this message]
2007-06-19 8:53 ` Henning Hraban Ramm
2007-06-19 8:54 ` nicola
2007-06-20 8:50 ` Wolfgang Schuster
2007-06-20 9:13 ` nicola
2007-07-21 16:46 ` Sanjoy Mahajan
2007-07-21 16:55 ` Aditya Mahajan
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=alpine.WNT.0.99.0706190214510.1080@nqvgln \
--to=adityam@umich.edu \
--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).