From: Thangalin via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Thangalin <thangalin@gmail.com>
Subject: Re: String substitution using regular expressions and backreferences
Date: Mon, 1 Aug 2022 13:56:09 -0700 [thread overview]
Message-ID: <CAANrE7q4eOYkZ6oPfvzXvoFaggvBemYOOVCU-CCnmzBshha1qQ@mail.gmail.com> (raw)
In-Reply-To: <20329b8b-6347-2bf8-7d63-9f5ac3d01e8e@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 325 bytes --]
Good point, Wolfgang.
The Markdown is translated to XHTML then typeset as XML using the setups
listed here:
https://github.com/DaveJarvis/keenwrite-themes/tree/main/xhtml
Having an XML string replacement solution would be great. I suppose that
would help prevent substitutions within pre and code blocks, too, wouldn't
it?
[-- Attachment #1.2: Type: text/html, Size: 818 bytes --]
[-- Attachment #2: Type: text/plain, Size: 496 bytes --]
___________________________________________________________________________________
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-01 20:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 19:58 Thangalin via ntg-context
2022-08-01 20:13 ` Wolfgang Schuster via ntg-context
2022-08-01 20:56 ` Thangalin via ntg-context [this message]
2022-08-25 19:44 ` Thangalin via ntg-context
2022-08-26 7:34 ` Hans Hagen 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=CAANrE7q4eOYkZ6oPfvzXvoFaggvBemYOOVCU-CCnmzBshha1qQ@mail.gmail.com \
--to=ntg-context@ntg.nl \
--cc=thangalin@gmail.com \
/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).