From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: hierarchical modes
Date: Thu, 15 May 2008 23:56:59 +0200 [thread overview]
Message-ID: <482CB1AB.7020706@wxs.nl> (raw)
In-Reply-To: <B1534C6B-A762-4A24-A291-DE654F77C3A5@zscout.de>
Janko Hauser wrote:
> Hello, I need to prepare a document for different audiences. The
> question here is, how to encapsulate the different parts of the
> document. There are paragraphs which are "public", some more which are
> "internal" and some which are "private". People who are in the private
> group should see everything, the group internal only the public parts
> and the internal ones. As far as I see, modes are not additive.
> What would be the best way to structure such a document and to style
> the different paragraphs, so that the different audiences see, who can
> read what?
\defineblock cum suis ...
quite old stuff btw (reminds me to provide a mkiv variant)
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2008-05-15 21:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 21:51 Janko Hauser
2008-05-15 21:56 ` Hans Hagen [this message]
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=482CB1AB.7020706@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).