From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: Denis Maier via ntg-context <ntg-context@ntg.nl>
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: Re: What exactly is lpath?
Date: Wed, 3 Aug 2022 19:08:54 +0200 [thread overview]
Message-ID: <9f5964c6-e562-d5f4-b751-c933e5a3de02@gmx.es> (raw)
In-Reply-To: <847c871b2d264774b9457901ac3cac1f@unibe.ch>
On 8/3/22 16:39, Denis Maier via ntg-context wrote:
> [...]
> Just like Pablo, I'm from time to time reading through the xml-mkiv
> manual, and I was just wondering if there other places where I can
> other examples or explanations. (If it were a more general Lua thing
> for example...)
Hi Dennis,
my impression is that (at least in my case) the hardest part is to
figure out how XPath actually works.
For that, I wonder whether
https://github.com/sarahalang/Harvard_BeyondTEI_Workshop_SLang2022 may
be helpful.
This is from the LaTeX-Ninja (Sarah A. Lang). But nothing prevents using
it as an exercise for ConTeXt users. I haven’t done it myself.
Just in case it might help,
Pablo
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2022-08-03 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 7:46 Denis Maier via ntg-context
2022-08-03 8:34 ` Hans Hagen via ntg-context
2022-08-03 14:39 ` Denis Maier via ntg-context
2022-08-03 15:05 ` Hans Hagen via ntg-context
2022-08-03 17:08 ` Pablo Rodriguez via ntg-context [this message]
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=9f5964c6-e562-d5f4-b751-c933e5a3de02@gmx.es \
--to=ntg-context@ntg.nl \
--cc=oinos@gmx.es \
/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).