From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: \xmldocument vs #1 in \xmlsetsetup
Date: Mon, 14 Nov 2022 22:32:57 +0100 [thread overview]
Message-ID: <dd7aac72-5690-1984-ee95-2e40609dc083@xs4all.nl> (raw)
In-Reply-To: <d78999dd-01ad-8aa8-99d6-c96189766c7a@gmx.es>
On 11/14/2022 7:28 PM, Pablo Rodriguez via ntg-context wrote:
> On 11/14/22 14:00, Denis Maier via ntg-context wrote:
>> Hi,
>>
>> most examples in the mkiv-xml manual use #1 with \xmlsetsetup, e.g.
>>
>> \startxmlsetups xml:demo:base
>> \xmlsetsetup{#1}{document|section|p}{xml:demo:*}
>> \stopxmlsetups
>>
>> However, in quite a few occasions I’ve noticed the usage of \xmldocument
>> instead of #1.
>>
>> What exactly is the difference ?
>
> Hi Denis,
>
> I have just found the following explanation
> (https://www.pragma-ade.com/general/manuals/xml-mkiv.pdf#search=xmlself):
>
> The macro \xmldocument expands to the current document id. There is
> also \xmlself which expands to the current node number (#1 in setups).
>
> Now I think that I have abused \xmldocument too much, since I should
> have used #1. But I’m afraid I haven’t got much different results.
>
> I must also confess that a proper explanation would be helpful (to me in
> order) to understsand when \xmldocument should not be used.
if you load a main xmkl file that is then xml document; there can be
many xml files loaded at the same time (which you can then access bu
{whatever} you used and once in the tree nodes are #1)
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2022-11-14 21:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 13:00 Denis Maier via ntg-context
2022-11-14 18:28 ` Pablo Rodriguez via ntg-context
2022-11-14 21:32 ` Hans Hagen via ntg-context [this message]
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=dd7aac72-5690-1984-ee95-2e40609dc083@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@xs4all.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).