ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Wolfgang Schuster" <schuster.wolfgang@googlemail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Feature request: \newitemize or something like this
Date: Mon, 1 Sep 2008 10:23:42 +0200	[thread overview]
Message-ID: <115224fb0809010123l39c29639me51a4239891bffe6@mail.gmail.com> (raw)
In-Reply-To: <115224fb0808270112o101dc9eaicc063af842b8bd3c@mail.gmail.com>

On Wed, Aug 27, 2008 at 10:12 AM, Wolfgang Schuster
<schuster.wolfgang@googlemail.com> wrote:
> On Wed, Aug 27, 2008 at 10:03 AM, Marcin Borkowski
> <mbork@atos.wmid.amu.edu.pl> wrote:
>> Hi there!
>>
>> I have a feature request (or a question "how to do it";)) concerning
>> itemizations.  Currently, they are much like LaTeX (say, with the
>> enumitem package).  I think this is not the best idea.  I can hardly
>> imagine using more than two levels of itemize in my documents; on the
>> other hand, I like to introduce different "kinds" of itemize on the
>> _first_ level.  Imagine I'm typesetting a paper on mathematics (which
>> I'm doing all the time;)).  I want another kind of itemize for lists of:
>> * equivalent conditions (as in: "the following are equivalent: ...");
>> * statements connected by an "or" clause (as in: "at least one of these
>>  holds: ...";
>> * statements connected by an "and" clause (as in: "assume that these
>>  conditions are satisfied: ...").
>>
>> What I usually do (in LaTeX) is to define a few environments, like
>> "equivenumerate", "orenumerate", "andenumerate" etc., and make them use
>> (a), (b), ..., (i), (ii), ..., or (1), (2), ... respectively.  This way
>> I have a clear visual clue in my papers on what's going where, and on
>> the other hand, I separate content and presentation.
>>
>> Would it be possible in ConTeXt?  If yes, how to do this?  Maybe it's
>> worth mentioning in the new manual?
>>
>> (As usual, I'll try to post the answer on the wiki when I have some
>> spare time!)
>
>
> Take a look at page 20.
>
> http://wolfgang.schuster.googlepages.com/erlangen.pdf

The source is also available: http://wolfgang.schuster.googlepages.com/baytex

Wolfgang
___________________________________________________________________________________
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
___________________________________________________________________________________


      parent reply	other threads:[~2008-09-01  8:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-27  8:03 Marcin Borkowski
2008-08-27  8:12 ` Wolfgang Schuster
2008-08-27  8:23   ` Thomas A. Schmitz
2008-08-27  8:30     ` Wolfgang Schuster
2008-08-27  8:37   ` Marcin Borkowski
2008-08-30 20:45   ` Henning Hraban Ramm
2008-09-01  8:23   ` Wolfgang Schuster [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=115224fb0809010123l39c29639me51a4239891bffe6@mail.gmail.com \
    --to=schuster.wolfgang@googlemail.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).