From: Michael Wiedmann <mw@miwie.in-berlin.de>
Subject: XML Processing Instructions
Date: Mon, 18 Mar 2002 21:11:36 +0100 [thread overview]
Message-ID: <20020318201136.GA7141@miwie.in-berlin.de> (raw)
How do I best handle - non ConTeXt related - XML Processing
Instructions?
Given:
<phrase>foo foo foo <?some-pi?> bla bla bla</phrase>
and a mapping of
\defineXMLenvironment[phrase] \em
the rendering stops right after the last "foo".
I just want ConTeXt to ignore the PI.
Michael
--
mw@miwie.in-berlin.de http://www.miwie.org
mw@miwie.org
next reply other threads:[~2002-03-18 20:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-18 20:11 Michael Wiedmann [this message]
2002-03-21 19:36 ` Simon Pepping
2002-03-23 13:28 ` Michael Wiedmann
2002-03-23 10:08 ` Hans Hagen
2002-03-24 21:23 ` Simon Pepping
2002-03-24 22:50 ` Michael Wiedmann
2022-05-02 7:19 XML processing instructions Duncan Hothersall via ntg-context
2022-05-02 7:33 ` Duncan Hothersall via ntg-context
2022-05-02 7:44 ` Denis Maier via ntg-context
2022-05-02 7:48 ` Denis Maier via ntg-context
2022-05-02 8:24 ` Duncan Hothersall via ntg-context
2022-05-03 7:30 ` Duncan Hothersall 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=20020318201136.GA7141@miwie.in-berlin.de \
--to=mw@miwie.in-berlin.de \
/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).