From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/114215
Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail
From: Rik Kabel via ntg-context <ntg-context@ntg.nl>
Newsgroups: gmane.comp.tex.context
Subject: Re: Convertnumber with \ref[number] fails in MkIV,
 works in LMTX
Date: Wed, 19 Jan 2022 12:39:14 -0500
Message-ID: <3888c9bc-8edc-7643-04ff-59eea8453dd6@panix.com>
References: <b9624f04-c124-ae60-9867-4951573df674@rik.users.panix.com>
 <dd956570-10ac-431b-1862-7b6422ed6552@rik.users.panix.com>
Reply-To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============5243771947925301729=="
Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214";
	logging-data="17749"; mail-complaints-to="usenet@ciao.gmane.io"
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
 Firefox/91.0 Thunderbird/91.5.0
Cc: Rik Kabel <rik@panix.com>
To: ntg-context@ntg.nl
Original-X-From: ntg-context-bounces@ntg.nl Wed Jan 19 18:57:46 2022
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 1nAFDN-0004SD-GK
	for gctc-ntg-context-518@m.gmane-mx.org; Wed, 19 Jan 2022 18:57:45 +0100
Original-Received: from localhost (localhost [127.0.0.1])
	by zapf.ntg.nl (Postfix) with ESMTP id EF588284AD8;
	Wed, 19 Jan 2022 18:57:24 +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 dXHz-XwXDWEV; Wed, 19 Jan 2022 18:57:22 +0100 (CET)
Original-Received: from zapf.ntg.nl (localhost [127.0.0.1])
	by zapf.ntg.nl (Postfix) with ESMTP id 8A8AE283A5E;
	Wed, 19 Jan 2022 18:57:22 +0100 (CET)
Original-Received: from localhost (localhost [127.0.0.1])
 by zapf.ntg.nl (Postfix) with ESMTP id 862A5283A5E
 for <ntg-context@ntg.nl>; Wed, 19 Jan 2022 18:57:21 +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 qxkk6f4WQShx for <ntg-context@ntg.nl>;
 Wed, 19 Jan 2022 18:57:20 +0100 (CET)
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=166.84.1.75;
 helo=l2mail1.panix.com; envelope-from=rik@panix.com; receiver=<UNKNOWN> 
X-Greylist: delayed 1082 seconds by postgrey-1.36 at zapf.ntg.nl;
 Wed, 19 Jan 2022 18:57:20 CET
Original-Received: from l2mail1.panix.com (l2mail1.panix.com [166.84.1.75])
 (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 0AF14280F96
 for <ntg-context@ntg.nl>; Wed, 19 Jan 2022 18:57:19 +0100 (CET)
Original-Received: from mailbackend.panix.com (mailbackend.panix.com [166.84.1.89])
 by l2mail1.panix.com (Postfix) with ESMTPS id 4JfCYy2RbvzDYj
 for <ntg-context@ntg.nl>; Wed, 19 Jan 2022 12:39:18 -0500 (EST)
Original-Received: from [192.168.1.106] (cpe-69-204-136-231.nycap.res.rr.com
 [69.204.136.231])
 by mailbackend.panix.com (Postfix) with ESMTPSA id 4JfCYw4HvYz3l26
 for <ntg-context@ntg.nl>; Wed, 19 Jan 2022 12:39:16 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=panix.com; s=panix;
 t=1642613956; bh=6NYtYKA76AMM7QS9eG4MxGWQ3g82bXA+ElYN84g+Sd4=;
 h=Date:Subject:To:References:From:In-Reply-To;
 b=r17BkglVNOpFxCvLePPZyYfN+lPU+D812eJvZO2Uy48swarPJbq8VRbpemR+YVkfL
 381huNNat2FkXuSsfV+51JOXaSceE10ak1eEH/MjjSklwKVeWHq8e3JJ8pfjxubuSj
 GBBLXuyD7KTm3fqt2hq5eBGLOnA7qQp6Mc7xAQHE=
Content-Language: en-US
In-Reply-To: <dd956570-10ac-431b-1862-7b6422ed6552@rik.users.panix.com>
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:114215
Archived-At: <http://permalink.gmane.org/gmane.comp.tex.context/114215>

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

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

This is still a problem with the current standalone.

    \definelabel[X][text=]
    \startTEXpage[offset=1cm]
       \X\X[a]\X[b]\X\par
       \convertnumber{R}{\ref[number][a]}
       \convertnumber{G}{\ref[number][b]}
    \stopTEXpage

    %% The above example fails to compile when there is no tuc file,
    %%    complaining of a missing number in line 4. When lines 4
    %%    and 5 are removed and the file is compiled, producing
    %%    a .tuc file, and then they are restored, the example
    %%    compiles without error. The effect of having or not having
    %%    an associated .tuc file does seem a bit odd.

Surely there is a way to get the number from a label reference that can 
then be converted to a numeral of choice.

-- 
Rik

--------------A2AKPu0YLQ5Zz4nXqitzUXlF
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>This is still a problem with the current standalone.</p>
    <blockquote>
      <p><font face="monospace">\definelabel[X][text=]<br>
          \startTEXpage[offset=1cm]<br>
            \X\X[a]\X[b]\X\par<br>
            \convertnumber{R}{\ref[number][a]}<br>
            \convertnumber{G}{\ref[number][b]}<br>
          \stopTEXpage<br>
          <br>
          %% The above example fails to compile when there is no tuc
          file,<br>
          %%    complaining of a missing number in line 4. When lines 4<br>
          %%    and 5 are removed and the file is compiled, producing<br>
          %%    a .tuc file, and then they are restored, the example<br>
          %%    compiles without error. The effect of having or not
          having<br>
          %%    an associated .tuc file does seem a bit odd.</font><br>
      </p>
    </blockquote>
    <p>Surely there is a way to get the number from a label reference
      that can then be converted to a numeral of choice.</p>
    <p>-- <br>
      Rik<br>
    </p>
    <pre class="moz-quote-pre" wrap="">
</pre>
  </body>
</html>

--------------A2AKPu0YLQ5Zz4nXqitzUXlF--

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

--===============5243771947925301729==--