ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "W. Egger" <w.egger@boede.nl>
Cc: "ntg-context" <ntg-context@ntg.nl>
Subject: Re: Questions on enumeration and itemize
Date: Wed, 24 Apr 2002 19:25:48 +0200	[thread overview]
Message-ID: <000701c1ebb5$1b914e00$0100a8c0@digitpaint.nl> (raw)
In-Reply-To: <1642723161.1019666468@[192.168.7.37]>

Hi Christophe

I was dealing with this issue some time ago. There are a lot of partially
new possibilities within the itemization environment. You might have a look
into core-itm.tex

Here tow examples as I used them:

\setupitemize[2][atmargin][headstyle=\it,marstyle=\it,symstyle=\it,indentnex
t=no]

\setupitemize[3][4*broad][distance= 2cm, width=2cm,before={\blank[small]}]

The first [ ] indicate the level on which the settings are used.

I hop this will help you setup your environment.

Willi

----- Original Message -----
From: Christophe Pythoud <pythoud@moria.ch>
To: <ntg-context@ntg.nl>
Sent: Wednesday, April 24, 2002 4:41 PM
Subject: Questions on enumeration and itemize

> Hi,
>
> 1)
>
> I have some legal documents to typeset of the form :
>
> 1    This is an article
> 1.1  this is a subarticle detailing some point
> 1.2  this is a second subarticle
>
> 2    This is an other article
> 2.1  this is a subarticle
> 2.2  etc.
>
> I do:
>
> \defineenumeration
>   [artst]
>   [location=left,
>    text={},
>    width=3em,
>    headstyle=normal]
> \setupenumerations[artst][headstyle=bold,style=bold]
> \setupenumerations[subartst][headstyle=normal,style=normal]
>
> and I get the main items (1 and 2) typeset in bold (which is what I want).
> But the minor items (1.1, 1.2, 2.1, etc.) are not typeset the way I was
> expecting them to be: the text is in normal style (what I want) but the
> number is in bold (I want them as normal text).  I don't understand why
> this happen.  I was under the impression that the second
\setupenumerations
> should not even be necessary.  What am I missing?
>
>
> 2)
>
> Later in the same document, I want to have at some point:
>
> 2    bla bla
> 2.1  bla bla
> 2.2  bla bla :
>      a)  bla bla
>      b)  bla bla
>      c)  etc.
>
> What I do for now is:
>
> \startitemize[a][width=3em,stopper=)]
> \item some text ;
> \item some more text.
> \stopitemize
>
> which gives me:
>
> 2.2  bla bla
> a)   bla bla
> b)   bla bla
> c)   etc.
>
> Quite nice but not exactly what I want.  How do I place the whole
> enumeration 3em away from the margin?  BTW, is there a way to do that for
> any paragraph (I mean a random paragraph in some text, not as a global
> setting).  I have been trying every possible combination of commands I
> looked up in the manuals but to no avail.  Any help would be greatly
> appreciated.
>
> I'm using ConTeXt beta from March 27, 2002.
>
> A nice day to all,
>
> Christophe
>
> ------
>  Christophe Pythoud (pythoud@moria.ch)


      reply	other threads:[~2002-04-24 17:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-24 14:41 Christophe Pythoud
2002-04-24 17:25 ` W. Egger [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='000701c1ebb5$1b914e00$0100a8c0@digitpaint.nl' \
    --to=w.egger@boede.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).