From: Hans Hagen <j.hagen@xs4all.nl>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: Map XML attributes to variables, dynamically
Date: Thu, 10 Aug 2023 09:43:28 +0200 [thread overview]
Message-ID: <89aff31c-5233-fba1-593a-27d8d56a3249@xs4all.nl> (raw)
In-Reply-To: <CAANrE7qGC=urT4az6jSthrk1X2hbPJL-7xycPQYyYEv=mS=j-Q@mail.gmail.com>
On 8/10/2023 9:10 AM, Thangalin wrote:
> Environments for the DIV element gets translated using:
>
> \startxmlsetups xml:div
\setvariable {div} {\xmlatt{#1}{class}} {#1}
> \start[\xmlatt{#1}{class}]\xmlflush{#1}\stop
> \stopxmlsetups
> \setMPtext{1}{\usermap[concurrent.title]}
> \setMPtext{2}{\usermap[concurrent.location]}
\setMPtext{1}{%
\xmlatt {\getvariable {div} {concurrent} {title}%
}
> I can verify the attribute values exist by exporting them to the document:
something like that .. untested as no mwe
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:[~2023-08-10 7:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 7:10 [NTG-context] " Thangalin
2023-08-10 7:43 ` Hans Hagen [this message]
2023-08-10 8:14 ` [NTG-context] " Thangalin
2023-08-10 8:37 ` Hans Hagen
2023-08-10 8:50 ` Hans Hagen via ntg-context
2023-08-10 8:55 ` Hans Hagen 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=89aff31c-5233-fba1-593a-27d8d56a3249@xs4all.nl \
--to=j.hagen@xs4all.nl \
--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).