From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-0.7 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED,
	HTML_MESSAGE,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE,URIBL_SBL_A
	autolearn=ham autolearn_force=no version=3.4.4
Received: (qmail 19517 invoked from network); 21 Apr 2023 12:34:48 -0000
Received: from zapf.ntg.nl (5.39.185.232)
  by inbox.vuxu.org with ESMTPUTF8; 21 Apr 2023 12:34:48 -0000
Received: from localhost (localhost [127.0.0.1])
	by zapf.ntg.nl (Postfix) with ESMTP id 1A1313CBE;
	Fri, 21 Apr 2023 14:34:32 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at zapf.ntg.nl
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 4iGWTUmk46rq; Fri, 21 Apr 2023 14:34:31 +0200 (CEST)
Received: from zapf.ntg.nl (localhost [127.0.0.1])
	by zapf.ntg.nl (Postfix) with ESMTP id C00D7144D;
	Fri, 21 Apr 2023 14:34:30 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
 by zapf.ntg.nl (Postfix) with ESMTP id 8E66A144D
 for <ntg-context@ntg.nl>; Fri, 21 Apr 2023 14:34:28 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at zapf.ntg.nl
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 PAVVrM3Odk_n for <ntg-context@ntg.nl>;
 Fri, 21 Apr 2023 14:34:27 +0200 (CEST)
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=212.54.42.168;
 helo=smtpq5.tb.mail.iss.as9143.net; envelope-from=havdmeer@ziggo.nl;
 receiver=<UNKNOWN> 
Received: from smtpq5.tb.mail.iss.as9143.net (smtpq5.tb.mail.iss.as9143.net
 [212.54.42.168])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by zapf.ntg.nl (Postfix) with ESMTPS id 701FF4EC
 for <ntg-context@ntg.nl>; Fri, 21 Apr 2023 14:34:27 +0200 (CEST)
Received: from [212.54.42.105] (helo=smtp1.tb.mail.iss.as9143.net)
 by smtpq5.tb.mail.iss.as9143.net with esmtps
 (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1)
 (envelope-from <havdmeer@ziggo.nl>) id 1pppy7-0004y7-3r
 for ntg-context@ntg.nl; Fri, 21 Apr 2023 14:34:27 +0200
Received: from smtpclient.apple ([84.104.102.59])
 by smtp1.tb.mail.iss.as9143.net with ESMTPA
 id ppy6ptYFGqL60ppy7pCBpy; Fri, 21 Apr 2023 14:34:27 +0200
X-Env-Mailfrom: havdmeer@ziggo.nl
X-Env-Rcptto: ntg-context@ntg.nl
X-SourceIP: 84.104.102.59
X-CNFS-Analysis: v=2.4 cv=CfPOppnl c=1 sm=1 tr=0 ts=644282d3 cx=a_exe
 a=r8aFSP8g8qyxuwAfcqn69g==:117 a=r8aFSP8g8qyxuwAfcqn69g==:17
 a=br8bnoXJpEcD8D3scbIA:9 a=CjuIK1q_8ugA:10 a=ff4rTfRrBIoLFfH-7RYA:9
 a=hhpQoq6KDqpqIYpr:21 a=_W_S_7VecoQA:10
X-Authenticated-Sender: havdmeer@ziggo.nl
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ziggo.nl;
 s=202002corplgsmtpnl; t=1682080467;
 bh=TprkVT+KxttjdN8RJwrXxNLr2Y+ArErh9A1vI7RcWdI=;
 h=From:Subject:Date:To;
 b=brMN8rEGqRECo4GSwDY6Yoo15yXT5CayL0R1rmjEkhJ6aHUg0ui8BFvrxZqtNZh3m
 Slo88NKdl7bGQob8Yun/PTkuFLqZOApwcNKS0uFsB6k580u3twKkwrWkoozIh7+ZP9
 UY5orxRty/eNvJoHF3U9aLIOsGiTK/DUzunt1pto2tOoCj1mffetN561VD66VRgG0n
 aejXColgGQe09jFjIEcOQdmJ4349p3IRvVGvFUDFQf+zAcdQcIpk1imEgfWiOFASBm
 ibRWr+NZ4n5n2GxoiEV2gv2xifmsf6TWM8VYBCFvS+iyJtYdUvB/j0kEgcOXXIFGHC
 v5ezQUD8OWBYg==
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.500.231\))
Message-Id: <C4709A1C-FAEA-428E-8AF0-FAFA29BBA878@ziggo.nl>
Date: Fri, 21 Apr 2023 14:34:16 +0200
To: NTG ConTeXt <ntg-context@ntg.nl>
X-Mailer: Apple Mail (2.3731.500.231)
X-CMAE-Envelope: MS4xfJ6BEZu9X8fZUir1uzOJdEBVBbqLz5DI21gaXByKQZUdcLnNWmUR8GXRqPW7i+1nZ4ctylr5lywcg/Jp+w4Fc22PtjVHHIQCrWL3bMPAQ8CVako0KG7t
 4KLlV+yNLOjBnzxnr7A4O3zN3pxUTq9TOvSjiLjcuyzKThUZz+eIK0v+6eJYmHgWprS0quVISNajZw==
Subject: [NTG-context] missing xml call
X-BeenThere: ntg-context@ntg.nl
X-Mailman-Version: 2.1.38
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>
From: Hans van der Meer via ntg-context <ntg-context@ntg.nl>
Reply-To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans van der Meer <havdmeer@ziggo.nl>
Content-Type: multipart/mixed; boundary="===============6822133156248465858=="
Errors-To: ntg-context-bounces@ntg.nl
Sender: "ntg-context" <ntg-context-bounces@ntg.nl>


--===============6822133156248465858==
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_E44B2EA8-0961-432C-80D0-7B18F1E615E4"


--Apple-Mail=_E44B2EA8-0961-432C-80D0-7B18F1E615E4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

\xmlatt{}{} has a counterpart \xmlattribute{}{LPATH}{} where one can =
start the search for the attribute at LPATH.
for \xmlchainatt{}{} I am missing such a counterpart =
\xmlchainattribute{}{LPATH}{} where one can do the same.

The problem now is that \xmlchainatt{#1}{att} always finds attribute att =
when it is defined on the node itself.
But consider the case where att=3D"true" exists with the intention to =
trigger a search higher up in the call chain for that same attribute =
att.
Of course \xmlattribute{#1}{..}{att} is not exactly the same as =
\xmlchainattribute{#1}{..}{att} would be .

yours sincerely
dr. Hans van der Meer




--Apple-Mail=_E44B2EA8-0961-432C-80D0-7B18F1E615E4
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv="content-type" content="text/html; charset=us-ascii"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">\xmlatt{}{} has a counterpart \xmlattribute{}{LPATH}{} where one can start the search for the attribute at LPATH.<div>for \xmlchainatt{}{} I am missing such a counterpart \xmlchainattribute{}{LPATH}{} where one can do the same.</div><div><br></div><div>The problem now is that \xmlchainatt{#1}{att} always finds attribute att when it is defined on the node itself.</div><div>But consider the case where att="true" exists with the intention to trigger a search higher up in the call chain for that same attribute att.</div><div>Of course \xmlattribute{#1}{..}{att} is not exactly the same as \xmlchainattribute{#1}{..}{att} would be .</div><div><br><div>
<div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>yours sincerely</div><div>dr. Hans van der Meer</div><div><br></div></div><br class="Apple-interchange-newline">

</div>


<br></div></body></html>
--Apple-Mail=_E44B2EA8-0961-432C-80D0-7B18F1E615E4--

--===============6822133156248465858==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

--===============6822133156248465858==--