From: <denis.maier@unibe.ch>
To: <j.hagen@xs4all.nl>, <ntg-context@ntg.nl>
Subject: [NTG-context] Re: xmldoif: checking for contents of attribute
Date: Fri, 25 Aug 2023 11:45:28 +0000 [thread overview]
Message-ID: <ZRAP278MB049538A9D25956C209893EC183E3A@ZRAP278MB0495.CHEP278.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <0e5968e6-ad6f-4838-5d90-d559484f6892@xs4all.nl>
> -----Ursprüngliche Nachricht-----
> Von: Hans Hagen <j.hagen@xs4all.nl>
> Gesendet: Freitag, 25. August 2023 09:06
> An: Maier, Denis Christian (UB) <denis.maier@unibe.ch>; mailing list for
> ConTeXt users <ntg-context@ntg.nl>
> Betreff: Re: [NTG-context] Re: xmldoif: checking for contents of attribute
>
> On 8/25/2023 8:22 AM, denis.maier@unibe.ch wrote:
>
> > Thanks for your help. I can use that, but why is this sort of double-checking
> necessary here?
>
> because containsa in a function that has checking while find is just the lua find
> .. so i've added a check in that one too now but no upload
>
So, that would mean that the double checking is only necessary for find, not for contains. And indeed the example below works.
Is that correct or are there any unwanted side-effects?
\startxmlsetups xml:test
\xmlsetsetup{#1}{*}{-}
\xmlsetsetup{#1}{doc|element}{xml:*}
\stopxmlsetups
\xmlregisterdocumentsetup{test}{xml:test}
\startxmlsetups xml:doc
\xmlflush{#1}
\stopxmlsetups
\startxmlsetups xml:element
1 \xmldoifelse{#1}{.[contains(@class,'abc')]}{Yes}{No} \par
2 \xmldoifelse{#1}{.[@class and find(@class,'abc')]}{Yes}{No} \par % runs, but no match
\stopxmlsetups
\startxmlsetups xml:whatever
Yes
\stopxmlsetups
\startbuffer[test]
<?xml version="1.0" encoding="UTF-8"?>
<doc>
<element class="abcdefg">Yes</element>
<element>No</element>
</doc>
\stopbuffer
\starttext
\xmlprocessbuffer{test}{test}{}
\stoptext
___________________________________________________________________________________
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-25 11:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 14:11 [NTG-context] " denis.maier
2023-08-24 14:34 ` [NTG-context] " Thomas A. Schmitz
2023-08-25 6:25 ` denis.maier
2023-08-24 14:54 ` Hans Hagen
2023-08-25 6:22 ` denis.maier
2023-08-25 7:05 ` Hans Hagen
2023-08-25 11:45 ` denis.maier [this message]
2023-08-25 12:48 ` Hans Hagen
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=ZRAP278MB049538A9D25956C209893EC183E3A@ZRAP278MB0495.CHEP278.PROD.OUTLOOK.COM \
--to=denis.maier@unibe.ch \
--cc=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).