From: Taco Hoekwater via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Taco Hoekwater <taco@bittext.nl>, Pablo Rodriguez <oinos@gmx.es>
Subject: Re: issue with lpath
Date: Wed, 3 Aug 2022 09:09:08 +0200 [thread overview]
Message-ID: <5BB3E275-8316-4465-9A81-81A7F9789C70@bittext.nl> (raw)
In-Reply-To: <7d65388d-636f-1a52-784a-7a9ecc426ee4@gmx.es>
> On 2 Aug 2022, at 21:14, Pablo Rodriguez via ntg-context <ntg-context@ntg.nl> wrote:
>
> Dear list,
>
>
> I need an lpath to select the h3 node above, but only the one with "h3 +
> blockquote" as a CSS selector (which could be added the lpath "../h3"
> after).
Lpath supports CSS selectors between curly braces as parts, so simply:
\xmlsetsetup{#1}{{h3 + blockquote}/../h3} {xml:section}
should do. The xml-mkiv.pdf manual has lots of other lpath examples as well.
Best wishes,
Taco
—
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-03 7:09 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 [this message]
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
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=5BB3E275-8316-4465-9A81-81A7F9789C70@bittext.nl \
--to=ntg-context@ntg.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).