ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: xml in lua: how to say "ancestor"?
Date: Fri, 3 Mar 2017 17:47:44 +0100	[thread overview]
Message-ID: <12991568-a5aa-3603-9fe9-55eb5af4b9fe@uni-bonn.de> (raw)
In-Reply-To: <e27e78e5-345c-8d94-eaca-3a27114416a9@wxs.nl>

On 25.02.2017 21:49, Hans Hagen wrote:
> xml.attribute(e,"..[tag()='section' or tag()='chapter']","title")
>
> with an optional default
>
> (there is also p = xml.parent(e) and then you can access p.at.title ..
> so there are several ways(
>
> Hans

I am sorry it took me so long to play with this... But it still doesn't 
do what I need. My problem is still: from a given element, I need to 
grab the content of an attribute that may be two or three or four levels 
up in the xml tree. The code below (adapted from Hans) still only works 
for a parent, but I need access to an "ancestor."

Thomas

\starttext

\startbuffer[test]
<document>
   <chapter title="OneC">
     <section title="OneS">
       <subsection title="OneSS">
       Subsection Text
       </subsection>
     </section>
   </chapter>
   <chapter title="TwoC">
     <subsection title="OneSS">
       Subsection Text
     </subsection>
   </chapter>
</document>
\stopbuffer

\startluacode

function xml.functions.xml_subsection(e)
     chaptertitle = xml.attribute(e, "..[tag()='chapter']", "title")
     context("Title of chapter is: ")
     context(chaptertitle)
     context.par()
     lxml.flush(e)
     context.blank( { "2*line" })
end

\stopluacode

\startxmlsetups xml:test:setups
     \xmlsetsetup{\xmldocument}{*}{xml:*}
\stopxmlsetups

\xmlregistersetup{xml:test:setups}

\startxmlsetups xml:document
     \xmlflush{#1}
\stopxmlsetups

\startxmlsetups xml:chapter
     \xmlflush{#1}
\stopxmlsetups

\startxmlsetups xml:section
     \xmlflush{#1}
\stopxmlsetups

\startxmlsetups xml:subsection
     \xmlfunction{#1}{xml_subsection}
\stopxmlsetups

\xmlprocessbuffer{main}{test}{}

\stoptext
___________________________________________________________________________________
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
___________________________________________________________________________________

  parent reply	other threads:[~2017-03-03 16:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-25 16:18 Thomas A. Schmitz
2017-02-25 18:30 ` Hans Hagen
2017-02-25 19:24   ` Thomas A. Schmitz
2017-02-25 20:10     ` Hans Hagen
2017-02-25 20:35       ` Thomas A. Schmitz
2017-02-25 20:49         ` Hans Hagen
2017-02-25 21:15           ` Thomas A. Schmitz
2017-03-03 16:47           ` Thomas A. Schmitz [this message]
2017-03-04  9:37             ` Hans Hagen

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=12991568-a5aa-3603-9fe9-55eb5af4b9fe@uni-bonn.de \
    --to=thomas.schmitz@uni-bonn.de \
    --cc=ntg-context@ntg.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).