From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: local environment?
Date: Wed, 5 Aug 2015 13:41:57 +0200 [thread overview]
Message-ID: <55C1F685.9080402@wxs.nl> (raw)
In-Reply-To: <70029FD2-DF67-4015-B952-9CA26D82BA7F@fastmail.fm>
On 8/5/2015 3:05 AM, talazem@fastmail.fm wrote:
> Dear all,
>
> What is the replacement for `localenvironment` in project structures?
>
> The first part of my book has one layout; the second has another. I have designed one environment for the first part, and another environment for the second. I do not want the first environment to be used for the second half of the book.
>
> In cont-eni.pdf, I read about using `localenvironment` for such scenarios, but it seems this has been removed.
>
> This is probably a very basic question, but how do I should change the following such that *one pdf* is produced, where the first part—ComponentA—uses EnvironmentA’s layout, while the second part—ComponentB—uses EnvironmentB's. If any startsetups need to be defined, I’d be grateful for any example, showing also where to place them.
>
> # Product
> \startproduct MyProduct
> \component ComponentA
> \component ComponentB
> \stopproduct
>
> # EnvironmentA
> \startenvironment envA
> % the definitions
> \stopenvironment
>
> # EnvironmentB
> \startenvironment envB
> % the definitions
> \stopenvironment
>
> # ComponentA
> \environment envA
> \product MyProduct
> \startcomponent ComponentA
> \starttext
> …
> \stoptext
>
> # ComponentB
> \environment envB
> \product MyProduct
> \startcomponent ComponentA
> \starttext
> …
> \stoptext
(1) set up a common style and then load specific ones for each part
or
(2) use grouping \start \component #1 \stop although this assumes that
settings are not global
--
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2015-08-05 11:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 1:05 talazem
2015-08-05 11:41 ` Hans Hagen [this message]
2015-08-05 12:43 ` talazem
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=55C1F685.9080402@wxs.nl \
--to=pragma@wxs.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).