From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
To: plink@veribox.net, "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: debian: itemize start=0
Date: Wed, 10 Oct 2007 22:51:16 +0200 [thread overview]
Message-ID: <6faad9f00710101351w6f06d7edv80f24f00bdf8fd2f@mail.gmail.com> (raw)
In-Reply-To: <470CB362.8080602@veribox.net>
On 10/10/07, plink wrote:
> Hi,
>
> on debian testing this small file
>
> \starttext
>
> \startitemize[n]
> \item one
> \item two
> \stopitemize
>
> blahblah
>
> \startitemize[n,continue]
> \item three
> \stopitemize
>
> \stoptext
>
> gives an itemization that starts at zero, plus the continue does not
> work either (context version: 2007.09.28 16:52
> (/usr/share/texmf/tex/context/base/context.tex)).
>
> Any hints or preliminary solutions greatly appreciated.
Don't ask me how that was possible. I tried that example and it works
fine. Last time (Thread "nesting \startitemize", 3 days ago) I had
those problems as well, but nobody else has complained about it, so I
have never mentioned it.
Weird.
I have no time to test at the moment, but there seem to have been
problems with this for some time already. See also:
http://article.gmane.org/gmane.comp.tex.context/36285
Also, in past, people reported many problem with "itemization starts
with 0 when in dvi mode".
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
___________________________________________________________________________________
prev parent reply other threads:[~2007-10-10 20:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 11:11 plink
2007-10-10 17:44 ` George N. White III
2007-10-10 20:51 ` Mojca Miklavec [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=6faad9f00710101351w6f06d7edv80f24f00bdf8fd2f@mail.gmail.com \
--to=mojca.miklavec.lists@gmail.com \
--cc=ntg-context@ntg.nl \
--cc=plink@veribox.net \
/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).