From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/109099
Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail
From: Rik Kabel <ConTeXt@rik.users.panix.com>
Newsgroups: gmane.comp.tex.context
Subject: MkIV and LMTX difference in comma list expansion
Date: Mon, 26 Oct 2020 12:34:28 -0400
Message-ID: <44c73441-764f-5d6b-3d82-9b921e34a108@rik.users.panix.com>
Reply-To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1268882775562178018=="
Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214";
	logging-data="22138"; mail-complaints-to="usenet@ciao.gmane.io"
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Firefox/68.0 Thunderbird/68.12.1
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Original-X-From: ntg-context-bounces@ntg.nl Mon Oct 26 17:34:56 2020
Return-path: <ntg-context-bounces@ntg.nl>
Envelope-to: gctc-ntg-context-518@m.gmane-mx.org
Original-Received: from zapf.boekplan.nl ([5.39.185.232] helo=zapf.ntg.nl)
	by ciao.gmane.io with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <ntg-context-bounces@ntg.nl>)
	id 1kX5SR-0005eg-Vz
	for gctc-ntg-context-518@m.gmane-mx.org; Mon, 26 Oct 2020 17:34:56 +0100
Original-Received: from localhost (localhost [127.0.0.1])
	by zapf.ntg.nl (Postfix) with ESMTP id 43DBE1A9980;
	Mon, 26 Oct 2020 17:34:35 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl
Original-Received: from zapf.ntg.nl ([127.0.0.1])
	by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id o-ZvKq5Jxnte; Mon, 26 Oct 2020 17:34:34 +0100 (CET)
Original-Received: from zapf.ntg.nl (localhost [127.0.0.1])
	by zapf.ntg.nl (Postfix) with ESMTP id 65C6A1A9976;
	Mon, 26 Oct 2020 17:34:34 +0100 (CET)
Original-Received: from localhost (localhost [127.0.0.1])
 by zapf.ntg.nl (Postfix) with ESMTP id 71BFE1A9973
 for <ntg-context@ntg.nl>; Mon, 26 Oct 2020 17:34:33 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl
Original-Received: from zapf.ntg.nl ([127.0.0.1])
 by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id rvIjVGBOLSBH for <ntg-context@ntg.nl>;
 Mon, 26 Oct 2020 17:34:32 +0100 (CET)
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=166.84.1.89;
 helo=mailbackend.panix.com; envelope-from=context@rik.users.panix.com;
 receiver=<UNKNOWN> 
Original-Received: from mailbackend.panix.com (mailbackend.panix.com [166.84.1.89])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
 (No client certificate requested)
 by zapf.ntg.nl (Postfix) with ESMTPS id B846B1A9961
 for <ntg-context@ntg.nl>; Mon, 26 Oct 2020 17:34:32 +0100 (CET)
Original-Received: from [192.168.0.6] (cpe-24-194-26-93.nycap.res.rr.com [24.194.26.93])
 by mailbackend.panix.com (Postfix) with ESMTPSA id 4CKgQt48yKzFvL
 for <ntg-context@ntg.nl>; Mon, 26 Oct 2020 12:34:30 -0400 (EDT)
Content-Language: en-US
X-BeenThere: ntg-context@ntg.nl
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: mailing list for ConTeXt users <ntg-context.ntg.nl>
List-Unsubscribe: <https://mailman.ntg.nl/mailman/options/ntg-context>,
 <mailto:ntg-context-request@ntg.nl?subject=unsubscribe>
List-Archive: <http://mailman.ntg.nl/pipermail/ntg-context/>
List-Post: <mailto:ntg-context@ntg.nl>
List-Help: <mailto:ntg-context-request@ntg.nl?subject=help>
List-Subscribe: <https://mailman.ntg.nl/mailman/listinfo/ntg-context>,
 <mailto:ntg-context-request@ntg.nl?subject=subscribe>
Errors-To: ntg-context-bounces@ntg.nl
Original-Sender: "ntg-context" <ntg-context-bounces@ntg.nl>
Xref: news.gmane.io gmane.comp.tex.context:109099
Archived-At: <http://permalink.gmane.org/gmane.comp.tex.context/109099>

This is a multi-part message in MIME format.
--===============1268882775562178018==
Content-Type: multipart/alternative;
 boundary="------------C9FF961BA3CF46F1C39253B7"
Content-Language: en-US

This is a multi-part message in MIME format.
--------------C9FF961BA3CF46F1C39253B7
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Hello list,

Another difference, perhaps the result of my lack of knowledge, but a 
difference.

The following example produces different results for the fourth 
sequence, with the index being passed one item under MkIV and two items 
under LMTX.

(The code is stripped out of a much more complex bit to show the issue.)

    % macros=mkvi
    \starttexdefinition unexpanded startBlockQuotation
         \dosingleempty\dostartBlockQuotation
    \stoptexdefinition
    \starttexdefinition dostartBlockQuotation [#SETUPS]
         \getrawparameters[BlockQuotation]
           [index=,#SETUPS]
         \expandafter\processcommalist
           \expandafter[\BlockQuotationindex]\doIndexIt{}
    \stoptexdefinition
    \starttexdefinition stopBlockQuotation
    \stoptexdefinition

    \starttexdefinition doIndexIt #INDEXTERM
       indexer sees #INDEXTERM\
       \index{#INDEXTERM}
    \stoptexdefinition

    \starttext

    \startBlockQuotation[index=aaa]
      \startparagraph
       1 \quad when indexing aaa.
      \stopparagraph
    \stopBlockQuotation
    \startBlockQuotation[index={aab}]
      \startparagraph
       2 \quad when indexing \{aab\}.
      \stopparagraph
    \stopBlockQuotation
    \startBlockQuotation[index={aac, aad}]
      \startparagraph
       3 \quad when indexing \{aac, aad\}.
      \stopparagraph
    \stopBlockQuotation
    \startBlockQuotation[index={{aae, aaf}}]
      \startparagraph
       4 \quad when indexing \{\{aae, aaf\}\}.
      \stopparagraph
    \stopBlockQuotation
    \startBlockQuotation[index={{{aag, aah}}}]
      \startparagraph
       5 \quad when indexing \{\{\{aag, aah\}\}\}.
      \stopparagraph
    \stopBlockQuotation
    \startBlockQuotation[index={{aai, aaj},{aak, aal}}]
      \startparagraph
       6 \quad when indexing \{\{aai, aaj\},\{aak, aal\}\}.
      \stopparagraph
    \stopBlockQuotation
    \startBlockQuotation[index={{{aam, aan}},{{aao, aap}}}]
      \startparagraph
       7 \quad when indexing \{\{\{aam, aan\}\},\{\{aao, aap\}\}\}.
      \stopparagraph
    \stopBlockQuotation
    \placeindex
    \stoptext

Did I misuse the comma list processing, or is this a bug?

-- 
Rik


--------------C9FF961BA3CF46F1C39253B7
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Hello list,</p>
    <p>Another difference, perhaps the result of my lack of knowledge,
      but a difference.</p>
    <p>The following example produces different results for the fourth
      sequence, with the index being passed one item under MkIV and two
      items under LMTX.</p>
    <p>(The code is stripped out of a much more complex bit to show the
      issue.)</p>
    <blockquote><tt>% macros=mkvi<br>
        \starttexdefinition unexpanded startBlockQuotation<br>
            \dosingleempty\dostartBlockQuotation<br>
        \stoptexdefinition<br>
        \starttexdefinition dostartBlockQuotation [#SETUPS]<br>
            \getrawparameters[BlockQuotation]<br>
              [index=,#SETUPS]<br>
            \expandafter\processcommalist<br>
              \expandafter[\BlockQuotationindex]\doIndexIt{}<br>
        \stoptexdefinition<br>
        \starttexdefinition stopBlockQuotation<br>
        \stoptexdefinition<br>
        <br>
        \starttexdefinition doIndexIt #INDEXTERM<br>
          indexer sees #INDEXTERM\ <br>
          \index{#INDEXTERM}<br>
        \stoptexdefinition<br>
        <br>
        \starttext<br>
        <br>
        \startBlockQuotation[index=aaa]<br>
         \startparagraph<br>
          1 \quad when indexing aaa.<br>
         \stopparagraph<br>
        \stopBlockQuotation<br>
        \startBlockQuotation[index={aab}]<br>
         \startparagraph<br>
          2 \quad when indexing \{aab\}.<br>
         \stopparagraph<br>
        \stopBlockQuotation<br>
        \startBlockQuotation[index={aac, aad}]<br>
         \startparagraph<br>
          3 \quad when indexing \{aac, aad\}.<br>
         \stopparagraph<br>
        \stopBlockQuotation<br>
        \startBlockQuotation[index={{aae, aaf}}]<br>
         \startparagraph<br>
          4 \quad when indexing \{\{aae, aaf\}\}.<br>
         \stopparagraph<br>
        \stopBlockQuotation<br>
        \startBlockQuotation[index={{{aag, aah}}}]<br>
         \startparagraph<br>
          5 \quad when indexing \{\{\{aag, aah\}\}\}.<br>
         \stopparagraph<br>
        \stopBlockQuotation<br>
        \startBlockQuotation[index={{aai, aaj},{aak, aal}}]<br>
         \startparagraph<br>
          6 \quad when indexing \{\{aai, aaj\},\{aak, aal\}\}.<br>
         \stopparagraph<br>
        \stopBlockQuotation<br>
        \startBlockQuotation[index={{{aam, aan}},{{aao, aap}}}]<br>
         \startparagraph<br>
          7 \quad when indexing \{\{\{aam, aan\}\},\{\{aao, aap\}\}\}.<br>
         \stopparagraph<br>
        \stopBlockQuotation<br>
        \placeindex<br>
        \stoptext<br>
      </tt><br>
    </blockquote>
    <p>Did I misuse the comma list processing, or is this a bug?<br>
    </p>
    <p>-- <br>
      Rik<br>
    </p>
  </body>
</html>

--------------C9FF961BA3CF46F1C39253B7--

--===============1268882775562178018==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX18KSWYgeW91ciBxdWVzdGlvbiBpcyBvZiBpbnRlcmVz
dCB0byBvdGhlcnMgYXMgd2VsbCwgcGxlYXNlIGFkZCBhbiBlbnRyeSB0byB0aGUgV2lraSEKCm1h
aWxsaXN0IDogbnRnLWNvbnRleHRAbnRnLm5sIC8gaHR0cDovL3d3dy5udGcubmwvbWFpbG1hbi9s
aXN0aW5mby9udGctY29udGV4dAp3ZWJwYWdlICA6IGh0dHA6Ly93d3cucHJhZ21hLWFkZS5ubCAv
IGh0dHA6Ly9jb250ZXh0LmFhbmhldC5uZXQKYXJjaGl2ZSAgOiBodHRwczovL2JpdGJ1Y2tldC5v
cmcvcGhnL2NvbnRleHQtbWlycm9yL2NvbW1pdHMvCndpa2kgICAgIDogaHR0cDovL2NvbnRleHRn
YXJkZW4ubmV0Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCg==

--===============1268882775562178018==--