From: "Wolfgang Schuster" <schuster.wolfgang@googlemail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: itemize start=2
Date: Thu, 30 Aug 2007 07:43:06 +0200 [thread overview]
Message-ID: <115224fb0708292243l4e0f5af1q79374c47e04c8b6a@mail.gmail.com> (raw)
In-Reply-To: <46D5CACC.18009.363AEE@wwl.musensturm.de>
2007/8/29, Wolfgang Werners-Lucchini <wwl@musensturm.de>:
> > > how can I start an itemization with 2
> > >
> > > I have tried snippets like
> > >
> > > \setupitemgroup[[itemize][start=2]
> > > \startitemize[n]
> > > \item zwei
> > > \item drei
> > > \stopitemize
> > >
> > > but could'nt found a solution.
> > >
> > > Btw.: Is there a differenz between
> > >
> > > \setupitemize[]
> > >
> > > and
> > >
> > > \setupitemgroup[[itemize][]
> > >
> > > Wolfgang
> >
> > Hi Wolfgang,
> >
> > \setupitemize is only macro for \setupitemgroup[itemize] and is
> > generated with \defineitemgroup like many other setup commands.
> >
> > To start your enumeration with 2 you have to define your own
> > number conversion.
> >
> > \def\nextnumber#1{\the\numexpr#1+1\relax}
> >
> > \defineconversion[nn][\nextnumber]
> >
> > \starttext
> > \startitemize[nn]
> > \item zwei
> > \item drei
> > \stopitemize
> > \stoptext
> >
> > Wolfgang
>
> Hi Wolfgang!
>
> This works!
>
> But two questions remain:
>
> 1) I am wondering, how you find such answers. What is your strategie
> searching the sources?
You can the answer in the big manual (cont-enp), it explains the symbols
are defined with \definesymbol and the counters values (n, r, r ... keys)
with \defineconversion.
> 2) What is that existing option 'start' for? Take this as an example
> for question 1).
If I understand the source correct it should begin the itemize with the
level you give with the start value, with the value 2 in your example the
outer itemize group should start with itemlevel 2 and we should get
the dash symbol as item marker but either this did not work I am wrong.
I tried this with the following example but the output off both items
are the same.
\starttext
\startitemize
\item Text
\stopitemize
\setupitemize[start=2]
\startitemize
\item Text
\stopitemize
\stoptext
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
___________________________________________________________________________________
next prev parent reply other threads:[~2007-08-30 5:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1188381610.30510.ntg-context@ntg.nl>
2007-08-29 17:36 ` Wolfgang Werners-Lucchini
2007-08-30 5:43 ` Wolfgang Schuster [this message]
2007-08-30 8:12 ` Mojca Miklavec
[not found] <mailman.1.1188468002.4085.ntg-context@ntg.nl>
2007-09-06 18:46 ` Wolfgang Werners-Lucchini
2007-09-08 10:29 ` Mojca Miklavec
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=115224fb0708292243l4e0f5af1q79374c47e04c8b6a@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).