ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jano Kula <jano.kula@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: content of xml node (element) in lua
Date: Fri, 16 Oct 2020 20:57:24 +0200	[thread overview]
Message-ID: <CAPefzZ2Y3zpoJExRuuWmEW8i2XHgzngpDRNpr0vuSdcTj6VHNg@mail.gmail.com> (raw)


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

Hello!

Processing XML I want to manipulate content of XML elements inside Lua.

I can define the Lua function xml.functions.name(t), where processing
happens, and use the command \xmlfunction{#1}{name} to pass the current
node #1 from ctx to lua as described in the xml-mkiv.pdf manual. To access
the element content xml.text(t,"/element") Lua function is used.

However, using the same function xml.text("#1",/element) directly inside
Lua doesn't work for me. Node #1 is available, but not the content of
/element.

\startluacode
    local node = "#1"
    local content = xml.text("#1","/color")
    context.par() context("node: ") context(node)
    context.par() context("lua: ")  context(content)
\stopluacode

MWE (mkiv, beta) attached.

I haven't found an example, so is it even possible? If so, which way is
more efficient?

Thanks,
Jano

[-- Attachment #1.2: Type: text/html, Size: 1586 bytes --]

[-- Attachment #2: xmlluanode.tex --]
[-- Type: application/octet-stream, Size: 1145 bytes --]

\startbuffer[doc]
<?xml version "1.0"?>
<document>
    <section title="First">
        <color>red</color>
        text1
    </section>
    <section title="Second">
        <color>blue</color>
        text2
    </section>
</document>
\stopbuffer

\startluacode
function xml.functions.name(t)
    local content = xml.text(t,"/color")
    context.par() context("function: ") context(content)
end

\stopluacode

\startxmlsetups xml:name
    \xmlsetsetup{\xmldocument}{*}{-}
    \xmlsetsetup{\xmldocument}{document|section}{xml:name:*}
\stopxmlsetups

\xmlregistersetup{xml:name}

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

\startxmlsetups xml:name:section
    \startsection[title=\xmlatt{#1}{title}]
    % ctx function
    \xmlfunction{#1}{name}
    % lua only
    \startluacode
        local node = "#1"
        local content = xml.text("#1","/color")
        context.par() context("node: ") context(node)
        context.par() context("lua: ")  context(content)
    \stopluacode
    \stopsection
\stopxmlsetups

\starttext

\xmlprocessbuffer{xml:name}{doc}{}

\stoptext

[-- Attachment #3: Type: text/plain, Size: 493 bytes --]

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

             reply	other threads:[~2020-10-16 18:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-16 18:57 Jano Kula [this message]
2020-10-16 22:16 ` mf
2020-10-17 10:02   ` Hans Hagen
2020-10-17 10:45     ` Jano Kula

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=CAPefzZ2Y3zpoJExRuuWmEW8i2XHgzngpDRNpr0vuSdcTj6VHNg@mail.gmail.com \
    --to=jano.kula@gmail.com \
    --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).