From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: combining itemize and starttabulate
Date: Thu, 7 Apr 2016 10:49:25 +0200 [thread overview]
Message-ID: <57061F15.4030900@wxs.nl> (raw)
In-Reply-To: <81171766-4282-4CBD-B8C6-50351BBC9E9E@icloud.com>
On 4/6/2016 1:04 PM, Jan Willem Flamma wrote:
> Dear members,
> The following combination of itemize and starttabulate is numbered from
> 'd. to f.' instead of from 'a. to c.'
> \starttext
> \startitemize[a]
> \starttabulate[|l|p|]
> \item \NC column1 \NC column2 \NC \NR
> \item \NC column1 \NC column2 \NC \NR
> \item \NC column1 \NC column2 \NC \NR
> \stoptabulate
> \stopitemize
> \stoptext
> I'm unable to figure out why this occurs and also how to get the
> following desired result:
> a. tekst tekst
> b. tekst tekst
> c. tekst tekst
I'm surprised it works at all. We should have a place on the garden
where we put such 'unexpected combinations of mechanisms' (Alan?).
you can put this in cont-new.mkiv:
\unprotect
\unexpanded\def\itemtag % not yet in interface definitions
{\dosingleempty\strc_itemgroups_item_tag}
\unexpanded\def\strc_itemgroups_item_tag[#1]% we can reuse more
{\def\currentitemreference{#1}%
\iftrialtypesetting
\strc_counters_save\v_strc_itemgroups_counter
\strc_itemgroups_increment_item_counter
\strc_itemgroups_insert_item_tag_indeed
\strc_counters_restore\v_strc_itemgroups_counter
\else
\strc_itemgroups_increment_item_counter
\strc_itemgroups_insert_item_tag_indeed
\fi}
\def\strc_itemgroups_insert_item_tag_indeed
{\letitemgroupparameter\c!distance\zeropoint
%letitemgroupparameter\c!width\zeropoint
\strc_itemgroups_make_symbol_box
\strc_itemgroups_make_destination_box
\let\m_strc_itemgroups_destination\empty
\ht\b_strc_itemgroups\strutheight
\dp\b_strc_itemgroups\strutdepth
\box\b_strc_itemgroups
\ignorespaces}
\protect
and then do:
\starttext
\startitemize[a,intext]
\starttabulate[|l|l|p|]
\NC \itemtag \NC column1 \NC column2 \NC \NR
\NC \itemtag \NC column1 \NC column2 \NC \NR
\NC \itemtag \NC column1 \NC column2 \NC \NR
\stoptabulate
\starttabulate[|l|l|l|]
\NC \itemtag \NC c1 \NC c2 \NC \NR
\NC \itemtag \NC c1 \NC c2 \NC \NR
\NC \itemtag \NC c1 \NC c2 \NC \NR
\stoptabulate
\stopitemize
\stoptext
and then explain it on the wiki
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | 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
___________________________________________________________________________________
next prev parent reply other threads:[~2016-04-07 8:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 11:04 Jan Willem Flamma
2016-04-07 8:49 ` Hans Hagen [this message]
2016-04-07 11:22 ` Procházka Lukáš Ing.
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=57061F15.4030900@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).