From: Hans van der Meer via ntg-context <ntg-context@ntg.nl>
To: NTG ConTeXt <ntg-context@ntg.nl>
Cc: Hans van der Meer <havdmeer@ziggo.nl>
Subject: [NTG-context] missing xml call
Date: Fri, 21 Apr 2023 14:34:16 +0200 [thread overview]
Message-ID: <C4709A1C-FAEA-428E-8AF0-FAFA29BBA878@ziggo.nl> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 640 bytes --]
\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="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
[-- Attachment #1.2: Type: text/html, Size: 1270 bytes --]
[-- Attachment #2: Type: text/plain, Size: 496 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
reply other threads:[~2023-04-21 12:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=C4709A1C-FAEA-428E-8AF0-FAFA29BBA878@ziggo.nl \
--to=ntg-context@ntg.nl \
--cc=havdmeer@ziggo.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).