From: Taco Hoekwater via ntg-context <ntg-context@ntg.nl>
To: Hans Hagen <j.hagen@xs4all.nl>
Cc: Taco Hoekwater <taco@bittext.nl>,
mailing list for ConTeXt users <ntg-context@ntg.nl>,
Pablo Rodriguez <oinos@gmx.es>
Subject: Re: issue with lpath
Date: Thu, 4 Aug 2022 17:32:03 +0200 [thread overview]
Message-ID: <96080631-8497-4005-98C8-0DDC2A5E3CDB@bittext.nl> (raw)
In-Reply-To: <7d6c00fb-55dc-c341-b29d-473d330c062a@xs4all.nl>
> On 4 Aug 2022, at 16:07, Hans Hagen <j.hagen@xs4all.nl> wrote:
>
> On 8/4/2022 12:22 PM, Taco Hoekwater via ntg-context wrote:
>>> On 3 Aug 2022, at 15:54, Pablo Rodriguez via ntg-context <ntg-context@ntg.nl> wrote:
>>>
>>> BTW, is there any way to rephrase "{h3 + blockquote}" in proper Lua?
>> I was wondering about that as well, and I really had no clue how to do that. Some
>> reading and studying later, I realised that there is a preceding-sibling:: axis.
>> That is not documented in xml-mkiv.pdf I think, but it inherited from xpath, and that means this works:
>> \xmlsetsetup{#1}{blockquote/preceding-sibling::h3[-1]/} {xml:section}
>> “Take all blockquotes, then tests their immediate preceding siblings (index [-1]) that are h3."
>> But the CSS version is nicer. Still, both solutions fail on generic input.
>> Sorry, out of clues
> \startbuffer[demo]
> ...
That puts the whole <div> content inside the \section, and I don’t think that was the intent. I understood that Pablo only wants the “h3” node.
In the original request, the CSS “{h3 + blockquote}” matches a “blockquote” anyplace where it is immediately preceded by a “h3” (and nowhere else).
After that, some trickery was needed to try and get back to the actual “h3”.
My trick above with preceding-sibling above also gets the “h3” that is immediately followed by a “blockquote”, but it got easily
confused if there were multiple “h3” or “blockquote” objects in the input.
Best wishes,
Taco
PS This sort of confusing filtering is why I do most of my xml processing from the lua end, where it is much clearer to me what is what.
—
Taco Hoekwater E: taco@bittext.nl
genderfluid (all pronouns)
___________________________________________________________________________________
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-08-04 15:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 19:14 Pablo Rodriguez via ntg-context
2022-08-03 7:09 ` Taco Hoekwater via ntg-context
2022-08-03 13:54 ` Pablo Rodriguez via ntg-context
2022-08-04 10:22 ` Taco Hoekwater via ntg-context
2022-08-04 14:07 ` Hans Hagen via ntg-context
2022-08-04 15:32 ` Taco Hoekwater via ntg-context [this message]
2022-08-04 16:39 ` Pablo Rodriguez via ntg-context
2022-08-05 15:28 ` Taco Hoekwater via ntg-context
2022-08-04 15:15 ` Pablo Rodriguez 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=96080631-8497-4005-98C8-0DDC2A5E3CDB@bittext.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@xs4all.nl \
--cc=oinos@gmx.es \
--cc=taco@bittext.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).