From: "Martin Kolarík" <martin@mii.cz>
Subject: RE: some XML stuff (and bugs?)
Date: Mon, 11 Aug 2003 17:27:13 +0200 [thread overview]
Message-ID: <00af01c3601d$09fd0200$2197fac3@mii.cz> (raw)
In-Reply-To: <5.2.0.9.1.20030811165000.01f7e318@server-1>
> -----Original Message-----
> From: ntg-context-admin@ntg.nl [mailto:ntg-context-admin@ntg.nl]On
> Behalf Of Hans Hagen
> Sent: Monday, August 11, 2003 4:53 PM
> To: ntg-context@ntg.nl
> Subject: RE: [NTG-context] some XML stuff (and bugs?)
>
>
> At 15:41 11/08/2003 +0200, you wrote:
> >yes, this works:
> >
> > > \starttext
> > >
> > > \defineXMLsave [buffer]
> > >
> > > \defineXMLsingular [buffer] {\XMLflush{buffer}}
> > >
> > > \startXMLdata
> > > test <buffer>here</buffer> test <buffer/>
> think of it: what should expand and what not and when?
exactly said, in this case I need unwrap <buffer/> and process it in
\XMLremapdata[mml]... I tried it but I did not suceed as \XMLflush executes
content and, of course, there nothing is left for \XMLremapdata to remap.
So, I fairly know what and how to expand, but I did not achieve this in
ConTeXt. It worths for thinking :-).
Currently, I have this solved -- I process my buffers first using XSLT (as
I cannot decompose <... etc. in verbatim buffers into <... and then
process the buffer using processXMLbuffer) to generate
\startbuffer..\stopbuffer containing <>, and I assure that all buffers will
contain <math> and </math> to avoid problems with expanding for
\XMLremapdata.
Thank you and please dismiss the topic if you want,
Martin
next prev parent reply other threads:[~2003-08-11 15:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-11 8:12 Martin Kolařík
2003-08-11 12:37 ` Hans Hagen
2003-08-11 13:40 ` Martin Kolarík
2003-08-11 12:41 ` Hans Hagen
2003-08-11 13:41 ` Martin Kolarík
2003-08-11 14:52 ` Hans Hagen
2003-08-11 15:27 ` Martin Kolarík [this message]
2003-08-11 16:15 ` Hans Hagen
2003-08-12 6:45 ` Martin Kolarík
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='00af01c3601d$09fd0200$2197fac3@mii.cz' \
--to=martin@mii.cz \
--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).