From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: mf via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: Xml filtering in Lua
Date: Thu, 17 Nov 2022 11:04:40 +0100 [thread overview]
Message-ID: <d70eb400-e843-3ddc-86ec-c4b4c6665200@xs4all.nl> (raw)
In-Reply-To: <4902918e-d6e1-47a7-6d22-0067262a5714@fastwebnet.it>
On 11/16/2022 8:56 PM, mf via ntg-context wrote:
> This works:
>
> local metadata = xml.filter (t, '../../topics/topic[@t:id=="' .. ch_id
> .. '"]')
>
> also this:
>
> local lpath = string.format('../../topics/topic[@t:id=="%s"]', ch_id)
>
> local metadata = xml.filter (t, lpath)
>
>
> It looks like xml.filter supports only 2 arguments (see lxml-tex.lua),
> and so it doesn't let you use string formatting patterns like the
> "context" command does.
>
> You can write:
>
> context('the value of @t:id is "%s"', ch_id)
>
> but you can't write:
>
> xml.filter (t, '../../topics/topic[@t:id=="%s"]', ch_id)
In Thomas example this is also an approach:
\startxmlsetups xml:document
\xmlfunction{#1} {document}
\xmlflush{#1}
\stopxmlsetups
with
\startluacode
local topics = { }
local chapters = { }
function xml.functions.document(t)
for c in xml.collected(t,"/topics/topic") do
topics[c.at.t_id] = c
end
-- for c in xml.collected(t,"/chapters/chapter") do
-- chapters[c.at.ch_id] = c
-- -- or flush here
-- end
end
function xml.functions.chapter (t)
local ch_id = t.at.ch_id
local metadata = topics[ch_id]
lxml.command(t, ".", "xml:chapter:content")
context.par ()
context (ch_id)
context.par ()
end
\stopluacode
so, basically you collect data and use it later ... for huge datasets
that saves some time
if you have only chapters to process you can even decide to flush in
that function
Hans
-----------------------------------------------------------------
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
___________________________________________________________________________________
next prev parent reply other threads:[~2022-11-17 10:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 16:10 Thomas A. Schmitz via ntg-context
2022-11-16 16:18 ` Duncan Hothersall via ntg-context
2022-11-16 17:33 ` Thomas A. Schmitz via ntg-context
2022-11-16 18:56 ` mf via ntg-context
2022-11-16 19:55 ` Thomas A. Schmitz via ntg-context
2022-11-16 20:51 ` Denis Maier via ntg-context
2022-11-16 21:09 ` Thomas A. Schmitz via ntg-context
2022-11-16 22:19 ` Hans Hagen via ntg-context
2022-11-16 19:56 ` mf via ntg-context
2022-11-17 10:04 ` Hans Hagen via ntg-context [this message]
2022-11-17 10:56 ` Thomas A. Schmitz via ntg-context
2022-11-20 18:19 ` Thomas A. Schmitz via ntg-context
2022-11-21 8:23 ` Thomas A. Schmitz via ntg-context
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=d70eb400-e843-3ddc-86ec-c4b4c6665200@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@xs4all.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).