> On 30 Aug 2018, at 00:53, Hans Hagen <j.ha...@xs4all.nl> wrote:
>
> On 8/29/2018 5:54 PM, Hans van der Meer wrote:
>> Doing: \xmlremovesetup{SETUP}
>> does not seems to have an effect.
>> Is it possible to deactivate a xml setup and reinstate at at a later point
>> in time?
> normally one uses modes for that (inside the setup)
>
> ir you can decide for explicit filtering (\xmlfilter)
>
I cannot imagine how to accomplish it that way, given my intentions.
Solved it with a global if (not so happy with global code, but could not think
of a neater, local solution).
All other solutions I tried typeset multiple copies of <subsubnode>
<topnode>
<subnode>
<subsubnode>
</subsubnode>
</subnode>
</topnode>
\startxmlsetups process:topnode (structures the output, collects all
<subsubnode>s here)
\global\topleveltrue
\xmlall{#1}{subsubnode}
\global\toplevelfalse
\stopxmlsetups
\startxmlsetups process:subsubnode
\iftoplevel
…
\fi
\stopxmlsetups
dr. Hans van der Meer
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
