From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/111714
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: Re: LMTX problem with doifmode in \setuplayout
Date: Tue, 8 Jun 2021 17:01:22 -0400
Message-ID: <bffe962b-db6d-6283-2f1d-c810f4f59dd0@rik.users.panix.com>
References: <b7262c96-4ecf-9e95-01c8-68b293127a15@rik.users.panix.com>
 <15b30ada-da1b-5d3b-13bd-86948a380054@gmail.com>
Reply-To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============5110219684115351461=="
Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214";
	logging-data="36057"; mail-complaints-to="usenet@ciao.gmane.io"
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Firefox/78.0 Thunderbird/78.11.0
To: ntg-context@ntg.nl
Original-X-From: ntg-context-bounces@ntg.nl Tue Jun 08 23:01:57 2021
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 1lqirE-0009DT-NN
	for gctc-ntg-context-518@m.gmane-mx.org; Tue, 08 Jun 2021 23:01:56 +0200
Original-Received: from localhost (localhost [127.0.0.1])
	by zapf.ntg.nl (Postfix) with ESMTP id 23F712843CF;
	Tue,  8 Jun 2021 23:01:33 +0200 (CEST)
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 MyFtfZNq0Bqk; Tue,  8 Jun 2021 23:01:28 +0200 (CEST)
Original-Received: from zapf.ntg.nl (localhost [127.0.0.1])
	by zapf.ntg.nl (Postfix) with ESMTP id 4FB992843B7;
	Tue,  8 Jun 2021 23:01:28 +0200 (CEST)
Original-Received: from localhost (localhost [127.0.0.1])
 by zapf.ntg.nl (Postfix) with ESMTP id AC28A2843AB
 for <ntg-context@ntg.nl>; Tue,  8 Jun 2021 23:01:26 +0200 (CEST)
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 JrL83sHUevwV for <ntg-context@ntg.nl>;
 Tue,  8 Jun 2021 23:01:25 +0200 (CEST)
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 CA51E2843A7
 for <ntg-context@ntg.nl>; Tue,  8 Jun 2021 23:01:24 +0200 (CEST)
Original-Received: from [192.168.1.106] (cpe-69-204-137-117.nycap.res.rr.com
 [69.204.137.117])
 by mailbackend.panix.com (Postfix) with ESMTPSA id 4G02hy74SZz3qQj
 for <ntg-context@ntg.nl>; Tue,  8 Jun 2021 17:01:22 -0400 (EDT)
In-Reply-To: <15b30ada-da1b-5d3b-13bd-86948a380054@gmail.com>
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:111714
Archived-At: <http://permalink.gmane.org/gmane.comp.tex.context/111714>

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

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


On 6/8/2021 16:11, Wolfgang Schuster wrote:
> Rik Kabel schrieb am 08.06.2021 um 18:14:
>>
>> Hello all,
>>
>> Odd issue with LMTX (works fine with --luatex). \doifelsemode causes 
>> a failure if it is used to set a simple value such as on, off, yes, 
>> no, ..., but works with a dimension. Perhaps better illustrated by an 
>> example:
>>
>>     \definemode        [aaa]
>>                        [keep]
>>     \setuplayout       [
>>                         marking=\doifmodeelse{aaa}{off}{on},
>>     %                   marking=on,
>>                         grid=\doifmodeelse{aaa}{yes}{no},
>>     %                   grid=yes,
>>                         bottom=\doifmodeelse{aaa}{10mm}{20mm},
>>                        ]
>>     \starttext
>>        This is only a test.
>>     \stoptext
>>
>> The problem occurs whether or not the mode is enabled. In the 
>> example, it fails with the mode test in the either the marking= or 
>> grid= keys, but has no problem with it in the bottom= key.
>>
>> The error message says:
>>
>>     The control sequence marked <to be read again> should not appear
>>     between \csname and \endcsname.
>>
>> pointing to the enabled \doifmodeelse line.
>>
>> The same issue occurs with the following, using \doifmode:
>>
>>     \definemode        [aaa]
>>                        [keep]
>>     \setuplayout       [
>>                         marking=on,
>>                         marking=\doifmode{aaa}{off},
>>                        ]
>>     \starttext
>>        This is only a test.
>>     \stoptext
>>
>> This did work without complaint a few months ago.
>>
>
> You can never be sure if these combinations (\doifXXX within 
> \setupXXX) work without problems. The only reliable method in this 
> case is:
>
> % default setup
>
> \setuplayout
>     [marking=on]
>
> % mode dependent setup
>
> \startmode[aaa]
>
>     \setuplayout
>         [marking=off]
>
> \stopmode
>
>
> Wolfgang
>
Yes, that works. Of course, to say that you can never be sure if such 
combinations will work is not a welcome statement about the state of 
ConTeXt.

More recent LMTX releases also now break older documents that worked 
(with LMTX and MkIV) before. If there is an error in what was previously 
written that is only noticed because of tighter enforcement, that is one 
thing, but an undocumented change to supported behaviour is less to be 
desired. And that it works with dimensions but not on/off/yes/no is very 
strange and suggests some other problem may be lurking.

-- 
Rik


--------------3BE68720416DB94158CDA7E8
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><br>
    </p>
    <div class="moz-cite-prefix">On 6/8/2021 16:11, Wolfgang Schuster
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:15b30ada-da1b-5d3b-13bd-86948a380054@gmail.com">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <span>Rik Kabel schrieb am 08.06.2021 um 18:14:</span><br>
      <blockquote type="cite"
        cite="mid:b7262c96-4ecf-9e95-01c8-68b293127a15@rik.users.panix.com">
        <meta http-equiv="content-type" content="text/html;
          charset=UTF-8">
        <p>Hello all,</p>
        <p>Odd issue with LMTX (works fine with --luatex). \doifelsemode
          causes a failure if it is used to set a simple value such as
          on, off, yes, no, ..., but works with a dimension. Perhaps
          better illustrated by an example:</p>
        <blockquote>
          <p><font face="monospace">\definemode        [aaa]<br>
                                 [keep]<br>
              \setuplayout       [<br>
                                  marking=\doifmodeelse{aaa}{off}{on},<br>
              %                   marking=on,<br>
                                  grid=\doifmodeelse{aaa}{yes}{no},<br>
              %                   grid=yes,<br>
                                  bottom=\doifmodeelse{aaa}{10mm}{20mm},<br>
                                 ]<br>
              \starttext<br>
                 This is only a test.<br>
              \stoptext</font><br>
          </p>
        </blockquote>
        <p>The problem occurs whether or not the mode is enabled. In the
          example, it fails with the mode test in the either the
          marking= or grid= keys, but has no problem with it in the
          bottom= key.</p>
        <p>The error message says:</p>
        <blockquote>
          <p><font face="monospace">The control sequence marked &lt;to
              be read again&gt; should not appear between \csname and
              \endcsname.</font><br>
          </p>
        </blockquote>
        <p>pointing to the enabled \doifmodeelse line.</p>
        <p>The same issue occurs with the following, using \doifmode:</p>
        <blockquote>
          <p><font face="monospace">\definemode        [aaa]<br>
                                 [keep]<br>
              \setuplayout       [<br>
                                  marking=on,<br>
                                  marking=\doifmode{aaa}{off},<br>
                                 ]<br>
              \starttext<br>
                 This is only a test.<br>
              \stoptext</font><br>
          </p>
        </blockquote>
        <p>This did work without complaint a few months ago.<br>
        </p>
      </blockquote>
      <br>
      You can never be sure if these combinations (\doifXXX within
      \setupXXX) work without problems. The only reliable method in this
      case is:<br>
      <br>
      % default setup<br>
      <br>
      \setuplayout<br>
          [marking=on]<br>
      <br>
      % mode dependent setup<br>
      <br>
      \startmode[aaa]<br>
      <br>
          \setuplayout<br>
              [marking=off]<br>
      <br>
      \stopmode<br>
      <br>
      <br>
      Wolfgang<br>
      <br>
    </blockquote>
    <p>Yes, that works. Of course, to say that you can never be sure if
      such combinations will work is not a welcome statement about the
      state of ConTeXt.</p>
    <p>More recent LMTX releases also now break older documents that
      worked (with LMTX and MkIV) before. If there is an error in what
      was previously written that is only noticed because of tighter
      enforcement, that is one thing, but an undocumented change to
      supported behaviour is less to be desired. And that it works with
      dimensions but not on/off/yes/no is very strange and suggests some
      other problem may be lurking.</p>
    <p>-- <br>
      Rik<br>
    </p>
  </body>
</html>

--------------3BE68720416DB94158CDA7E8--

--===============5110219684115351461==
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==

--===============5110219684115351461==--