From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>, Pablo Rodriguez <oinos@gmx.es>,
Taco Hoekwater <taco@bittext.nl>
Subject: Re: issue with lpath
Date: Thu, 4 Aug 2022 16:07:51 +0200 [thread overview]
Message-ID: <7d6c00fb-55dc-c341-b29d-473d330c062a@xs4all.nl> (raw)
In-Reply-To: <6E3914FB-D5A6-47B8-B781-5E849BB4F61C@bittext.nl>
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]
<xml>
<div class="section level3">
<h3>One</h3>
<p>Standard paragraph</p>
<blockquote>
<p>Quoted text</p>
</blockquote>
</div>
<div class="section level3">
<h3>Two</h3>
<blockquote>
<p>Direct quote</p>
</blockquote>
</div>
</xml>
\stopbuffer
\startxmlsetups xml:initialize
\xmlsetsetup{#1}
{xml|p|blockquote|div}
{xml:*}
\xmlsetsetup{#1}
{/xml/div[contains(@class,'level3')]}
{xml:section:level3}
\stopxmlsetups
\xmlregistersetup{xml:initialize}
\startxmlsetups xml:xml
\xmlall{#1}{/div}
\stopxmlsetups
\startxmlsetups xml:p
\startpar\xmlflush{#1}\stoppar
\stopxmlsetups
\startxmlsetups xml:blockquote
\startblockquote\xmlflush{#1}\stopblockquote
\stopxmlsetups
\startxmlsetups xml:section:level3
\xmldoif{#1}{/blockquote} {
\xmldoifnot{#1}{/p} {
\section{\xmlflush{#1}}
}
}
\stopxmlsetups
\starttext
\xmlprocessbuffer{main}{demo}{}
\stoptext
-----------------------------------------------------------------
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:[~2022-08-04 14:07 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 [this message]
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=7d6c00fb-55dc-c341-b29d-473d330c062a@xs4all.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).