From: Duncan Hothersall <dh@capdm.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: arbitrary context commands in xml file
Date: Mon, 8 Mar 2021 11:48:53 +0000 [thread overview]
Message-ID: <CAN8fp9XqQ2CWOSW63dKw7BUFWQDD60g7Gju7ASeWeiSgn1C72g@mail.gmail.com> (raw)
In-Reply-To: <a183b3abc05940329e1d57dbbd7b566f@ub.unibe.ch>
[-- Attachment #1.1: Type: text/plain, Size: 1168 bytes --]
On Mon, 8 Mar 2021 at 10:21, <denis.maier@ub.unibe.ch> wrote:
> > -----Ursprüngliche Nachricht-----
> > Von: Hans Hagen <j.hagen@xs4all.nl>
> > Gesendet: Freitag, 5. März 2021 23:17
> > An: mailing list for ConTeXt users <ntg-context@ntg.nl>; Maier, Denis
> > Christian (UB) <denis.maier@ub.unibe.ch>;
> > wolfgang.schuster.lists@gmail.com
> > Betreff: Re: [NTG-context] arbitrary context commands in xml file
>
>
> [...]
>
> > >
> > > Here, I was thinking if something like this could be easier:
> > >
> > > <?context-directive raw-tex-injector \testpage[4]?>
> > you can also do this:
> >
> > <testpage n="4"/>
> >
> > \startxmlsetups xml:testpage
> > \testpage[\xmlatt{#1}{n}]
> > \stopxmlsetup
> >
> > and register that one (as in previous examples)
>
> Thanks,. That's a good idea, but it will also make the XML invalid.
>
> Denis
>
I'd like to second Denis' request for support for XML processing
instructions to execute ConTeXt code, rather than elements which can cause
big problems if one is working to a fixed schema. It would be a boon to be
able to drop in <?context \whatever{fdfd}?> in an XML source.
Duncan
[-- Attachment #1.2: Type: text/html, Size: 2175 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2021-03-08 11:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 14:39 denis.maier
2021-03-05 14:53 ` denis.maier
2021-03-05 15:01 ` Wolfgang Schuster
2021-03-05 15:26 ` denis.maier
2021-03-05 21:27 ` denis.maier
2021-03-05 22:17 ` Hans Hagen
2021-03-08 10:20 ` denis.maier
2021-03-08 11:48 ` Duncan Hothersall [this message]
2021-03-08 12:46 ` Hans Hagen
2021-03-08 13:05 ` Duncan Hothersall
2021-03-08 13:39 ` denis.maier
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=CAN8fp9XqQ2CWOSW63dKw7BUFWQDD60g7Gju7ASeWeiSgn1C72g@mail.gmail.com \
--to=dh@capdm.com \
--cc=ntg-context@ntg.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).