From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Strange bug with reversed itemize
Date: Sun, 16 Sep 2012 12:52:47 +0200 [thread overview]
Message-ID: <5055AF7F.2060308@wxs.nl> (raw)
In-Reply-To: <alpine.DEB.2.02.1209151406020.8170@nqv-guvaxcnq>
On 15-9-2012 20:06, Aditya Mahajan wrote:
> On Sat, 15 Sep 2012, Wolfgang Schuster wrote:
>
>>
>> Am 15.09.2012 um 00:06 schrieb Aditya Mahajan <adityam@umich.edu>:
>>
>>> Thanks for the diagnosis. What will be a good way to fix this? I
>>> think that
>>>
>>> \expanded{\setupcounter[#1][\c!start=\ifx\p_start\empty0\else\number\p_start\fi.,...]}
>>>
>>>
>>> should work (but I haven't tested it yet).
>>
>>
>> I would do the expansion here but with \normalexpanded.
>>
>> \def\strc_counter_setup_using_parameter#1#2% name \someparameter
>> {\edef\p_start{#2\c!start}%
>> %\setupcounter
>> \normalexpanded{\setupcounter
>> [#1]
>> [ \c!start=\ifx\p_start\empty0\else\number\p_start\fi,
>> \c!state=#2\c!state, % beware, "" == start
>> \c!way=#2\c!way,
>> %
>> \c!prefix=#2\c!prefix,
>> \c!prefixseparatorset=#2\c!prefixseparatorset,
>> \c!prefixconversion=#2\c!prefixconversion,
>> \c!prefixconversionset=#2\c!prefixconversionset,
>> \c!prefixstarter=#2\c!prefixstarter,
>> \c!prefixstopper=#2\c!prefixstopper,
>> \c!prefixset=#2\c!prefixset,
>> \c!prefixsegments=#2\c!prefixsegments,
>> \c!prefixset=#2\c!prefixset,
>> \c!prefixconnector=#2\c!prefixconnector,
>> %
>> \c!numberseparatorset=#2\c!numberseparatorset,
>> \c!numberconversion=#2\c!numberconversion,
>> \c!numberconversionset=#2\c!numberconversionset,
>> \c!numberstarter=#2\c!numberstarter,
>> \c!numberstopper=#2\c!numberstopper,
>> % \c!numbersegments=#2\c!numbersegments]}
>> \c!numbersegments=#2\c!numbersegments]}}
>
> Thanks.
>
> Hans, can you add this to strc-num.mkiv?
Sure, as I assume that Wolfgang investigated possible side effects.
Hans
-----------------------------------------------------------------
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:[~2012-09-16 10:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 0:34 Aditya Mahajan
2012-09-13 3:30 ` burwoad
2012-09-13 3:36 ` Aditya Mahajan
2012-09-13 7:59 ` Otared Kavian
2012-09-13 16:18 ` Aditya Mahajan
2012-09-13 22:36 ` Aditya Mahajan
2012-09-13 22:49 ` Aditya Mahajan
2012-09-13 23:11 ` Wolfgang Schuster
2012-09-14 22:06 ` Aditya Mahajan
2012-09-15 8:03 ` Wolfgang Schuster
2012-09-15 18:06 ` Aditya Mahajan
2012-09-16 10:52 ` 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=5055AF7F.2060308@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).