From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: [NTG-context] Re: Map XML attributes to variables, dynamically
Date: Thu, 10 Aug 2023 10:50:23 +0200 [thread overview]
Message-ID: <4c0076c7-f9df-be56-afaf-518f9ef91796@freedom.nl> (raw)
In-Reply-To: <08d2c2e9-7be4-e14e-e16a-b162b9771362@xs4all.nl>
On 8/10/2023 10:37 AM, Hans Hagen wrote:
> On 8/10/2023 10:14 AM, Thangalin wrote:
>> Here's an MWE:
>>
>> % SOT
>> \startbuffer[demo]
>> <html>
>> <body>
>> <div class="concurrent" data-title="Berth 5" data-location="San Diego">
>> Text Goes Here
>> </div>
>> <div class="concurrent" data-title="Road" data-location="Beale AFB">
>> Different Text Goes Here
>> </div>
>> </body>
>> </html>
>> \stopbuffer
>>
>> \startxmlsetups xml:xhtml
>> \xmlsetsetup{\xmldocument}{*}{-}
>> \xmlsetsetup{\xmldocument}{html|body}{xml:*}
>> \xmlsetsetup{\xmldocument}{div}{xml:*}
>> \stopxmlsetups
>>
>> \xmlregistersetup{xml:xhtml}
>>
>> \startxmlsetups xml:html
>> \xmlflush{#1}
>> \stopxmlsetups
>>
>> \startxmlsetups xml:body
>> \xmlflush{#1}
>> \stopxmlsetups
>>
>> \startxmlsetups xml:div
>> \setvariable{div}{\xmlatt{#1}{class}}{#1}
>> \start[\xmlatt{#1}{class}]\xmlflush{#1}\stop
>> \stopxmlsetups
>>
>> \definestartstop[concurrent][
>> before={TITLE: \xmlatt{\getvariable {div} {concurrent} {title}}},
>> ]
>>
>> \starttext
>> \xmlprocessbuffer{main}{demo}{}
>> \stoptext
>> % EOT
>>
>> It doesn't look like the variables are taking, regardless of whether
>> {title} or {data-title} are used.
>
> \startxmlsetups xml:div
> \setvariable{div}{\xmlatt{#1}{class}}{#1}
> \start[\xmlatt{#1}{class}]\xmlflush{#1}\stop
> \stopxmlsetups
>
> \definestartstop
> [concurrent]
> [before={TITLE: \xmlatt{\getvariable{div}{concurrent}}{data-title}}]
>
> -- watch the braces
> -- use data-title and not title
>
> Hans
You can actually do this:
\startxmlsetups xml:div
\setupstartstop
[\xmlatt{#1}{class}]
[before={TITLE: \xmlatt{#1}{data-title}}]%
\start[\xmlatt{#1}{class}]%
\xmlflush{#1}
\stop
\stopxmlsetups
\definestartstop
[concurrent]
and you then can also do
\namedstartstopparameter{concurrent}{before}
when needed, which save you the intermediate variable because it's
already in before, so from that it's a natural step to
\startxmlsetups xml:div
\setupstartstop
[\xmlatt{#1}{class}]
[title=\xmlatt{#1}{data-title},
before={TITLE: \namedstartstopparameter{concurrent}{title}}]%
\start[\xmlatt{#1}{class}]%
\xmlflush{#1}
\stop
\stopxmlsetups
\definestartstop
[concurrent]
and then with:
\namedstartstopparameter{concurrent}{title}
(i'll add this example to the test suite as demo)
-----------------------------------------------------------------
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 8:52 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 ` [NTG-context] " Hans Hagen
2023-08-10 8:14 ` Thangalin
2023-08-10 8:37 ` Hans Hagen
2023-08-10 8:50 ` Hans Hagen via ntg-context [this message]
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=4c0076c7-f9df-be56-afaf-518f9ef91796@freedom.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@freedom.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).