From: "Wolfgang Werners-Lucchini" <wwl@musensturm.de>
To: ntg-context@ntg.nl
Subject: Re: itemize start=2
Date: Thu, 06 Sep 2007 20:46:58 +0200 [thread overview]
Message-ID: <46E06742.32214.25C5447@wwl.musensturm.de> (raw)
In-Reply-To: <mailman.1.1188468002.4085.ntg-context@ntg.nl>
Hallo!
> > > > I have tried snippets like
> > > >
> > > > \setupitemgroup[[itemize][start=2]
> > > > \startitemize[n]
> > > > \item zwei
> > > > \item drei
> > > > \stopitemize
> > > >
> > > > but could'nt found a solution.
>
> It looks like a misfeature (ie. bug) to me.
>
> > But two questions remain:
> >
> > 1) I am wondering, how you find such answers. What is your
> strategie
> > searching the sources?
> > 2) What is that existing option 'start' for? Take this as an
> example
> > for question 1).
>
> As far as I can see, 'start' currently serves no purpose since it
> gets
> overridden in line 447 in
> \expanded{\setitemparameter{\itemlevel}{\c!start}{1}}%
> in core-itm.tex anyway. Try to comment out that line.
>
> The next problem lies a few lines below:
>
> \doifelsenothing{\getitemparameter\itemlevel\c!start}
> {\def\currentitemoffset{1}}
>
> {\def\currentitemoffset{\getitemparameter\itemlevel\c!start}%
> \letitemparameter\itemlevel\c!start\empty}%
>
> You need to say \edef instead of \def, otherwise the empty value
> will
> be used for calculating \currentitemoffset.
>
> How to search? It's difficult to tell, but in this particular
> case,
> you take a look into core-itm.tex (assuming you know where
> itemizations are. If you don't, you can execute "grep \setupitem *"
> in
> tex/context/base/.) Then, you search for \c!start and try to
> figure
> out where it is used. You find \setitemlevel. OK, great. What does
> it
> do there? It's supposed to change \currentitemoffset. If you want
> to check \currentitemoffset, you simply place
> (my debug: \currentitemoffset)
> at the end of \setitemlevel. Now, you either need to copy that
> definition on the top of your document (which will override the
> global
> one), or remake the formats with "texexec --make en" before
> running
> texexec on your document again. You will get some extra info on top
> of your itemization. It doesn't belong there, but you will remove it
> afterwards. (Did I forget to say that it might be wise to make a
> bacup
> of the original file?) Now when you remade the formats (or placed
> the
> definition on top of your file or to cont-new.tex) and compiled
> the
> document again, take a look at the result.
>
> Oh, well, you only get (my debug: ). \currentitemoffset seems to
> be empty.
If I change the above /def to /edef I get (my debug: 1), but as a
sideeffect the counter is incremented and therefor is starting with 2
then.
> Then try to put
> (I wanted to have: \getitemparameter\itemlevel\c!start)
> somewhere at the beginning of \setitemlevel, somewhere inbetween
> (after \expandex{...}) and somewhere at the end. It works at the
> beginning, then it gets reset to 1, and then it gets deleted.
> And they you try to figure out why.
\letitemparameter\itemlevel\c!start\empty}
commenting this line has too the above sideeffect that counting is
started with 2.
But I don't understand the whole thing.
If I understand you right, the c!start is for increasing the
itemizelevel NOT the numbering. So I wonder why the later is
affected.
Wolfgang
> Btw: the two modifications mentioned above don't solve the problem
> yet, since you now have a problem with offset +1 (I remember a bug
> report from not so long ago, when itemizations started with 0, so
> that
> might be related). But I would better leave that for Hans.
> Itemizations are so complex that I don't dare to touch anything
> there.
>
> Mojca
___________________________________________________________________________________
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 parent reply other threads:[~2007-09-06 18:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1188468002.4085.ntg-context@ntg.nl>
2007-09-06 18:46 ` Wolfgang Werners-Lucchini [this message]
2007-09-08 10:29 ` Mojca Miklavec
[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
2007-08-30 8:12 ` 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=46E06742.32214.25C5447@wwl.musensturm.de \
--to=wwl@musensturm.de \
--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).