ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
* \xmldocument vs #1 in \xmlsetsetup
@ 2022-11-14 13:00 Denis Maier via ntg-context
  2022-11-14 18:28 ` Pablo Rodriguez via ntg-context
  0 siblings, 1 reply; 3+ messages in thread
From: Denis Maier via ntg-context @ 2022-11-14 13:00 UTC (permalink / raw)
  To: ntg-context; +Cc: denis.maier


[-- Attachment #1.1: Type: text/plain, Size: 366 bytes --]

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 ?

When should you prefer one over the other?

Best,
Denis


[-- Attachment #1.2: Type: text/html, Size: 2488 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
___________________________________________________________________________________

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: \xmldocument vs #1 in \xmlsetsetup
  2022-11-14 13:00 \xmldocument vs #1 in \xmlsetsetup 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
  0 siblings, 1 reply; 3+ messages in thread
From: Pablo Rodriguez via ntg-context @ 2022-11-14 18:28 UTC (permalink / raw)
  To: Denis Maier via ntg-context; +Cc: Pablo Rodriguez

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.

Pablo
___________________________________________________________________________________
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
___________________________________________________________________________________

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: \xmldocument vs #1 in \xmlsetsetup
  2022-11-14 18:28 ` Pablo Rodriguez via ntg-context
@ 2022-11-14 21:32   ` Hans Hagen via ntg-context
  0 siblings, 0 replies; 3+ messages in thread
From: Hans Hagen via ntg-context @ 2022-11-14 21:32 UTC (permalink / raw)
  To: Pablo Rodriguez via ntg-context; +Cc: Hans Hagen

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
___________________________________________________________________________________

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2022-11-14 21:32 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-11-14 13:00 \xmldocument vs #1 in \xmlsetsetup 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 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).