ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Duncan Hothersall via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Duncan Hothersall <dh@capdm.com>,
	"Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
Subject: Re: Xml filtering in Lua
Date: Wed, 16 Nov 2022 16:18:20 +0000	[thread overview]
Message-ID: <CAN8fp9UmyUDf798zNXKeagsPmUe+hPAPnaCz-mb7bJwMYTWw5Q@mail.gmail.com> (raw)
In-Reply-To: <FE5E7CBC-B883-4E30-9138-AB87F08E3017@uni-bonn.de>


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

Hi Thomas.

I'm not sure about the code, sorry, but I do know that an XML document
can't have two IDs of the same value. Typically you would use a linkend
attribute on the element which is referencing an id (in this case the
topics, I think).

Probably doesn't help with your problem, but it's likely a prerequisite for
it to work.

Bests,

Duncan

On Wed, 16 Nov 2022 at 16:11, Thomas A. Schmitz via ntg-context <
ntg-context@ntg.nl> wrote:

> Hi all,
>
> I thought this was easy, but I overestimated my competence… I want to
> filter xml elements via their attributes and retrieve and typeset parts
> belonging together. Here is a small test file that explains what I’m trying:
>
> \startbuffer[test]
> <document>
>    <topics>
>       <topic id="test1">
>         <title>This is the first test</title>
>         <date>22/11/16</date>
>       </topic>
>       <topic id="test2">
>         <title>This is the second test</title>
>         <date>22/11/17</date>
>       </topic>
>    </topics>
>    <chapters>
>       <chapter id="test1">
>         <content>
>           This will be the content of the <emph>first</emph> chapter.
>         </content>
>       </chapter>
>       <chapter id="test2">
>          <content>
>           This will be the content of the <emph>second</emph> chapter.
>          </content>
>       </chapter>
>    </chapters>
> </document>
> \stopbuffer
>
> \startxmlsetups xml:testsetups
>         \xmlsetsetup{#1}{*}{-}
>         \xmlsetsetup{#1}{document|chapters|chapter|content|emph}{xml:*}
> \stopxmlsetups
>
> \xmlregistersetup{xml:testsetups}
>
> \startxmlsetups xml:document
>         \xmlflush{#1}
> \stopxmlsetups
>
> \startxmlsetups xml:chapters
>         \xmlflush{#1}
> \stopxmlsetups
>
> \startxmlsetups xml:chapter
>         \xmlfunction {#1} {chapter}
>          \xmlflush {#1}
> \stopxmlsetups
>
> \startxmlsetups xml:chapter:content
>         \xmltext {#1} {content}
> \stopxmlsetups
>
> \startxmlsetups xml:emph
>    {\em \xmlflush {#1}}
> \stopxmlsetups
>
> \startluacode
> function xml.functions.chapter (t)
>          local ch_id = t.at.id
>                 local metadata = xml.filter (root,
> '../../topics/topic[@id=="%s"]', ch_id)
>                 print (inspect(metadata))
>                 lxml.command(t, ".", "xml:chapter:content")
>                 context.par ()
>                 context (ch_id)
>                 context.par ()
> end
> \stopluacode
>
> \starttext
>         \xmlprocessbuffer{main}{test}{}
> \stoptext
>
> The line with xml.filter does not work as I expected. How can I walk the
> tree, find the “topic” element with the same “id” attribute as the chapter
> I’m currently in, and then typeset the different children of the topic
> element?
>
> Thanks a lot and all best
>
> Thomas
>
>
> ___________________________________________________________________________________
> 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
>
> ___________________________________________________________________________________
>

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

[-- Attachment #2: Type: text/plain, Size: 496 bytes --]

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

  reply	other threads:[~2022-11-16 16:18 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 [this message]
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
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=CAN8fp9UmyUDf798zNXKeagsPmUe+hPAPnaCz-mb7bJwMYTWw5Q@mail.gmail.com \
    --to=ntg-context@ntg.nl \
    --cc=dh@capdm.com \
    --cc=thomas.schmitz@uni-bonn.de \
    /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).