From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: IMHO there is a bug in itemgrops
Date: Sun, 16 Nov 2014 20:24:04 +0100 [thread overview]
Message-ID: <5468F9D4.9030502@wxs.nl> (raw)
In-Reply-To: <486271415886078@web29o.yandex.ru>
On 11/13/2014 2:41 PM, Vasiliy Chirkov wrote:
> Minimal example:
>
> \starttext
> \defineitemgroup[Enum][levels=3]
> \setupitemgroup[Enum][each][fit][symbol=n]
> \setupitemgroup[Enum][1][stopper={}]
> \setupitemgroup[Enum][2][stopper={***}]
> \setupitemgroup[Enum][3][stopper={******}]
>
> \startEnum
> \item item 1
> \startEnum
> \item item 1.1
> \startEnum
> \item item 1.1.1
> \item item 1.1.2
> \stopEnum
> \item item 1.2
> \stopEnum
> \item item 2
> \stopEnum
> \stoptext
>
> When option 'fit' is used with nested lists, calculated max item widths are saved in reverse order. Maxitemwidths are saved at first pass in \stopitemgrup in reverse order, while are read at second pass in \startitem grpoup in sequental order.
>
> Am i right?
yes, i'll fix it (i didn't assume nested fixed usage)
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2014-11-16 19:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 13:41 Vasiliy Chirkov
2014-11-16 19:24 ` Hans Hagen [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=5468F9D4.9030502@wxs.nl \
--to=pragma@wxs.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).