ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans van der Meer <hansm@science.uva.nl>
Subject: document structure
Date: Fri, 21 Jul 2006 12:20:58 +0200	[thread overview]
Message-ID: <74B0153C-8A9C-45BD-94DB-6B52CD54CDFA@science.uva.nl> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1062 bytes --]

I have a question about document structure, because I want to  
structure a series of products correctly and I do not know if I  
understand everything in the manual about it well enough.

Must I understand that "\startlocalenvironment[abc]" within an  
environment file means that this codeblock is used only for  
typesetting product/component abc and excluded automatically when  
another product/component is typeset?
Or is it just a declaration analogous to "\startenvironment file  
setups \stopenvironment"?
But then I don't understand why the manual does not tells me
"\startlocalenvironment[abc] file setups \stoplocalenvironment" as it  
does for \startenvironment

The macro "\localenvironment name" gives me some headaches. I might  
guess usage in a master setup file as:
\localenvironment abc % load environment file abc.tex if typesetting  
product/component abc
\localenvironment xyz % load environment file xyz.tex if typesetting  
product/component xyz
How does this relate to the above question about setup-file structure?

Hans van der Meer


[-- Attachment #1.2: Type: text/html, Size: 1961 bytes --]

[-- Attachment #2: Type: text/plain, Size: 139 bytes --]

_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

             reply	other threads:[~2006-07-21 10:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-21 10:20 Hans van der Meer [this message]
2006-07-21 12:58 ` Taco Hoekwater
2006-07-21 18:02   ` Hans van der Meer
2006-07-22  8:19     ` Taco Hoekwater
2006-07-22 11:38       ` Hans van der Meer
2006-07-22 12:19         ` document structure (small bug) Taco Hoekwater
2006-07-22 12:40           ` Hans van der Meer

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=74B0153C-8A9C-45BD-94DB-6B52CD54CDFA@science.uva.nl \
    --to=hansm@science.uva.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).