* reading attribute from ancestor element in XML
@ 2015-10-06 10:06 massifr
2015-10-06 10:46 ` Hans Hagen
0 siblings, 1 reply; 2+ messages in thread
From: massifr @ 2015-10-06 10:06 UTC (permalink / raw)
To: ntg-context
Hello list,
I have an XML fragment like this:
<div id="myid">
<p><sup>12</sup> blah blah...</p>
</div>
In the typeset text I want to substitute the text of the sup element ("12")
with the id ("myid") in its div grandfather.
The xmlsetup associated to the sup element looks like this:
\startxmlsetups xml:sup
\xmlatt{\xmlfirst{#1}{../..}}{id}
\stopxmlsetups
This gives an error (TeX capacity exceeded).
I'm using ConTeXt version 2015.06.15.
I've tried \xmlfilter and \xmlall too, with different lpaths.
Sometimes ConTeXt ends without errors,
but I've never managed to get the text of that attribute.
What's the right way to backtrack to parent and ancestor nodes?
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: reading attribute from ancestor element in XML
2015-10-06 10:06 reading attribute from ancestor element in XML massifr
@ 2015-10-06 10:46 ` Hans Hagen
0 siblings, 0 replies; 2+ messages in thread
From: Hans Hagen @ 2015-10-06 10:46 UTC (permalink / raw)
To: ntg-context
On 10/6/2015 12:06 PM, massifr@fastwebnet.it wrote:
> Hello list,
> I have an XML fragment like this:
>
> <div id="myid">
> <p><sup>12</sup> blah blah...</p>
> </div>
>
> In the typeset text I want to substitute the text of the sup element ("12")
> with the id ("myid") in its div grandfather.
>
> The xmlsetup associated to the sup element looks like this:
>
> \startxmlsetups xml:sup
> \xmlatt{\xmlfirst{#1}{../..}}{id}
> \stopxmlsetups
\xmlattribute{#1}{../..}{id}
> This gives an error (TeX capacity exceeded).
> I'm using ConTeXt version 2015.06.15.
> I've tried \xmlfilter and \xmlall too, with different lpaths.
> Sometimes ConTeXt ends without errors,
> but I've never managed to get the text of that attribute.
>
> What's the right way to backtrack to parent and ancestor nodes?
> ___________________________________________________________________________________
> 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://tex.aanhet.net
> archive : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
>
--
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| 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 / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2015-10-06 10:46 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-10-06 10:06 reading attribute from ancestor element in XML massifr
2015-10-06 10:46 ` Hans Hagen
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).