From: Hans Hagen <pragma@wxs.nl>
Cc: NTG-CONTEXT <ntg-context@ntg.nl>
Subject: Re: sample styles
Date: Wed, 08 Sep 1999 23:48:26 +0200 [thread overview]
Message-ID: <37D6D9AA.8E96C335@wxs.nl> (raw)
In-Reply-To: <vho7lm1ff70.fsf@jane.coe.uga.edu>
"Ed L. Cashin" wrote:
> It's hard to keep up with you! I am trying out "tabulate" (for the
> impatient). :)
Come on, we're only talking about some styles. Most is already there, so
once you're synchronized ...
> > I don't want to use our company styles. What do you want, how should
> > it look, what should it do? Do you want latex counterparts, in which
> > case I need some samples. Or don't you want styles at all ...
>
> I'm not sure if I'm understanding the question. If you mean:
>
> \setupstyle[letter]
> % ...
In context there is: \usemodule.
There are m- modules that contain things that do not belong to the core
of context, currently the chemics module, soon the math module, there is
a units module (10 \square \milli \meter \per \second), a flow chart
module, etc. The s- modules are styles, currently there are 6
presentation ones (14 on my machine), one for the maps, one for tugboat,
etc Last there are p- modules, some internal pragma ones, like the page
selection styles used in the a la carte project.
> ... then I don't really have an opinion. But if you mean that you are
> drawing up a set of example documents illustrating how to achieve a
> familiar style using ConTeXt commands, then that sounds great.
That's what I mean.
> I find myself wondering, e.g., how exactly I would go about setting up
> headers with running headers showing chapter (for one-sided documents)
> and chapter/section (for two-sided documents). I know that it will be
> \setupheadertexts and \setupfootertexts, but I'm unsure of what I'll
> put in the square brackets.
\setupheadertexts [chapter] [section]
\setupheadertexts [whatever]
or
\setupheadertexts [{\getmarking[chapter][first]}] [...]
or
\setupheadertexts [{\getmarking[subsection][all]}]
or ...
1 arg is centered, 2 are left and right (single and double sided
swapped) and 4 args are for different doublesides ones.
> My point is that I would find it helpful to see documents formatted in
> familiar styles.
>
> If you are looking for a sample of a LaTeX article, I have one that's
> about emacs and programming in Linux that I'd be happy to share. I
> have some plain-TeX letters, a plain-TeX resume ... let me know.
Ok. Some latex article and report styles. How important is A4/letter
size?
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~1999-09-08 21:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-08 15:57 Hans Hagen
1999-09-08 18:09 ` Ed L. Cashin
1999-09-08 21:48 ` Hans Hagen [this message]
1999-09-08 18:32 ` David Arnold
1999-09-08 21:55 ` Hans Hagen
1999-09-09 9:39 ` Hans Hagen
1999-09-09 10:34 ` Taco Hoekwater
1999-09-09 12:36 ` Hans Hagen
1999-09-09 13:32 ` Taco Hoekwater
1999-09-09 8:54 ` Matthew Baker
1999-09-09 9:32 ` Hans Hagen
1999-09-09 14:06 ` Hans Hagen
1999-09-09 15:04 ` Taco Hoekwater
1999-09-09 15:58 ` Hans Hagen
1999-09-09 15:58 ` Wybo Dekker
1999-09-10 10:13 ` Hans Hagen
1999-09-09 17:49 ` Berend de Boer
2001-08-20 7:45 Sample styles Victor Sanchez
2001-08-20 14:52 ` Hans Hagen
2001-08-20 15:15 ` Henning Hraban Ramm
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=37D6D9AA.8E96C335@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).