From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
Subject: Re: separating layout from content: section blocks?
Date: Wed, 3 May 2006 19:34:49 +0200 [thread overview]
Message-ID: <6faad9f00605031034i1537b650mc2b9d564c56a095e@mail.gmail.com> (raw)
In-Reply-To: <A4E8A7CD-97AB-4F02-B0B3-D06D3F1F88C1@u.washington.edu>
On 5/1/06, Andrew D. Crouse wrote:
> To whom it may concern,
>
> I have a large document with several distinct pieces. Each piece has
> different layout requirements. I can setup the layout before each
> piece, but I would prefer to separate the layout from content.
> Currently what is the best way to do this?
I guess that you can use
\startsetups[somename]
... whatever setups you need ...
\stopsetups
and then recall them by
\setups[somename]
I first saw the example of usage here, but didn't try them out by myself yet:
http://source.contextgarden.net/tex/context/base/s-mag-01.tex
http://www.pragma-ade.com/general/magazines/mag-0000.pdf
Mojca
prev parent reply other threads:[~2006-05-03 17:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-01 16:30 Andrew D. Crouse
2006-05-03 16:14 ` Willi Egger
2006-05-03 17:34 ` Mojca Miklavec [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=6faad9f00605031034i1537b650mc2b9d564c56a095e@mail.gmail.com \
--to=mojca.miklavec.lists@gmail.com \
--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).