From: Hans Hagen <pragma@wxs.nl>
Cc: NTG ConTeXt <ntg-context@ntg.nl>
Subject: Re: XML Processing Instructions
Date: Sat, 23 Mar 2002 11:08:50 +0100 [thread overview]
Message-ID: <5.1.0.14.1.20020323110822.02ca0eb0@server-1> (raw)
In-Reply-To: <20020323132855.GA2032@miwie.in-berlin.de>
At 02:28 PM 3/23/2002 +0100, Michael Wiedmann wrote:
>* Simon Pepping <spepping@scaprea.hobby.nl> [020321 20:36]:
>...
> > \defineXMLprocessor[some-pi] \dosomepi
> > \def\dosomepi#1{(Some PI: #1)}
>...
> > That is because context expects a form like <?pi-name pi-data?>. The
> > data are inserted as a single token after the defined XML processor,
> > and thus can be picked up by it as an argument. If no processor is
> > defined, the data is ignored.
>
>Thanks Simon, it works like you pointed out, *but*:
>
>in contrary e.g. to the handling of PIs in DocBook DSSSL styleheets
>*and* against my understanding of the definition for PIs, ConTeXt forces
>to use a 'data' field in PIs (like <?line-break true?>) though
><?line-break?> alone should be sufficient. ConText stops processing the
>current element content in the last case.
>
>Or do I still miss something.
ok, i'll see if i can fix that
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
fall-back web server:
www.pragma-ade.nl
-------------------------------------------------------------------------
next prev parent reply other threads:[~2002-03-23 10:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-18 20:11 Michael Wiedmann
2002-03-21 19:36 ` Simon Pepping
2002-03-23 13:28 ` Michael Wiedmann
2002-03-23 10:08 ` Hans Hagen [this message]
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=5.1.0.14.1.20020323110822.02ca0eb0@server-1 \
--to=pragma@wxs.nl \
--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).