From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: [NTG-context] Re: ConTeXt source from XML
Date: Thu, 6 Jun 2024 17:42:45 +0200 [thread overview]
Message-ID: <03f0a877-6b3b-4754-87f6-ae5951395fd0@freedom.nl> (raw)
In-Reply-To: <e7948327-afc4-4e31-b9ac-24586bcbff88@gmx.es>
On 6/6/2024 5:33 PM, Pablo Rodriguez via ntg-context wrote:
> On 6/5/24 20:23, Christoph Edenhauser wrote:
>> Dear Pablo,
>>
>> Thank you very much for your very clear, detailed and elaborate
>> explanations. - Over the next few days I will meditate on the ConTeXt
>> way to handle XML and on my workflow and take a look at lpath (never
>> heard of it). And somehow I have the impression that the next few days
>> will last a few weeks.
>
> Dear Christoph,
>
> just in case it might help to your meditation.
>
> First of all, lpaths are XPath implemented with Lua in ConTeXt.
>
> XPath seems to have as it primary purpose to address the nodes of XML trees.
>
> About your sources, the real issue here is to define whether you want
> TEI or TeX to be the format containing them.
>
> I mean, if you add explaining footnotes to your TeX file(s), XML won’t
> be source anymore.
>
> If you don’t want this to happen, you have to encode them in the TEI XML
> sources.
>
> One last suggestion about proofreading. This is something I learnt from
> personal experience.
>
> The first reading is much better to catch errors in the text than the
> subsequent ones.
>
> Having the text properly formatted and printed on paper helps a lot to
> spot errors.
>
> Reading source code is cheaper (no doubt), but the results will be
> poorer too.
>
> Just in case it might help,
fwiw, context supports 'synctex' to xml files / nodes so that might help
a bit
Hans
-----------------------------------------------------------------
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://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2024-06-06 15:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 11:51 [NTG-context] " Christoph Edenhauser
2024-06-04 15:21 ` [NTG-context] " Pablo Rodriguez via ntg-context
2024-06-04 19:21 ` Christoph Edenhauser
2024-06-04 20:09 ` Hans Hagen
2024-06-05 10:00 ` Christoph Edenhauser
2024-06-05 12:16 ` Henning Hraban Ramm
2024-06-05 14:13 ` Christoph Edenhauser
2024-06-05 15:08 ` Hans Hagen
2024-06-05 14:34 ` Pablo Rodriguez via ntg-context
2024-06-05 18:23 ` Christoph Edenhauser
2024-06-06 15:33 ` Pablo Rodriguez via ntg-context
2024-06-06 15:42 ` Hans Hagen via ntg-context [this message]
2024-06-06 20:53 ` [NTG-context] " Christoph Edenhauser
2024-06-07 19:41 ` [NTG-context] " Pablo Rodriguez via ntg-context
2024-06-07 20:34 ` Henning Hraban Ramm
2024-06-08 7:14 ` Denis Maier via ntg-context
2024-06-08 7:49 ` Wolfgang Schuster
2024-06-08 8:49 ` vm via ntg-context
2024-06-08 8:59 ` Thomas A. Schmitz
2024-06-08 8:59 ` Pablo Rodriguez via ntg-context
2024-06-08 9:04 ` Pablo Rodriguez via ntg-context
2024-06-05 16:30 ` 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=03f0a877-6b3b-4754-87f6-ae5951395fd0@freedom.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@freedom.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).