From: Petr Ferdus <pferdus@vertigo.fme.vutbr.cz>
Cc: ntg-context@ntg.nl
Subject: Re: typeseting XML
Date: Fri, 1 Jun 2001 10:03:44 +0200 (CEST) [thread overview]
Message-ID: <Pine.BSF.3.96.1010601083337.29526A-100000@vertigo.fme.vutbr.cz> (raw)
In-Reply-To: <3.0.6.32.20010531111252.01ac13a0@server-1>
On Thu, 31 May 2001, Hans Hagen wrote:
> >(1)also if there is an entity at the beginning of element passed
> >by argument (example in XML data).
>
> dontknow/dontsee, anyway i'll send you the latest xtag files [there is also
> a new \defineXMLenv..push one you may want to use]
Right placement of \appendtoks ... sequence with expansion of
list makes them nicely expand. Thank you very much.
Unafected remains only case (1) than means, if one line of XML data in
gtest example would look like:
<h2>&Title H2 with any entity an the very beginning of it</h2>
which is processed by some macro e.g.:
\long\def\MySection#1{\section{#1}}% which could do more, would it had
% chance
and declared as:
\defineXMLargument [h2] {\MySection}
it produces "! Incomplete \ifnum; error. ..."
(data from elements, which have no macros hooked to their processing, do
process correctly)
Thanks
Peter
next prev parent reply other threads:[~2001-06-01 8:03 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3.0.6.32.20010525212835.0127d390@server-1>
[not found] ` <Pine.BSF.3.96.1010529101027.14223A-100000@vertigo.fme.vutb r.cz>
2001-05-29 9:45 ` Hans Hagen
2001-05-29 14:05 ` Petr Ferdus
2001-05-30 15:01 ` Petr Ferdus
[not found] ` <Pine.BSF.3.96.1010529153914.15436A-101000@vertigo.fme.vutb r.cz>
2001-05-30 15:09 ` Hans Hagen
2001-05-30 20:12 ` Petr Ferdus
2001-06-14 23:07 ` Petr Ferdus
[not found] ` <Pine.BSF.3.96.1010615004606.12697C-100000@vertigo.fme.vutb r.cz>
2001-06-15 8:09 ` Hans Hagen
2001-06-27 7:46 ` typeseting XML - mixed buffers Petr Ferdus
[not found] ` <Pine.BSF.3.96.1010627092248.18364B-100000@vertigo.fme.vutb r.cz>
2001-06-27 8:28 ` Hans Hagen
2001-06-27 9:25 ` Petr Ferdus
[not found] ` <Pine.BSF.3.96.1010627110044.18364C-100000@vertigo.fme.vutb r.cz>
2001-06-27 10:26 ` Hans Hagen
2001-06-27 10:43 ` Petr Ferdus
[not found] ` <Pine.BSF.3.96.1010627122029.18364D-100000@vertigo.fme.vutb r.cz>
2001-06-27 21:16 ` Hans Hagen
2001-06-28 7:41 ` Petr Ferdus
[not found] ` <Pine.BSF.3.96.1010628091736.23569C-100000@vertigo.fme.vutb r.cz>
2001-06-28 9:31 ` Hans Hagen
[not found] ` <Pine.BSF.3.96.1010530154343.20742A-101000@vertigo.fme.vutb r.cz>
2001-05-31 9:12 ` typeseting XML Hans Hagen
2001-06-01 8:03 ` Petr Ferdus [this message]
[not found] ` <Pine.BSF.3.96.1010601083337.29526A-100000@vertigo.fme.vutb r.cz>
2001-06-04 9:55 ` Hans Hagen
2001-06-06 4:47 ` Petr Ferdus
2001-06-06 8:01 ` very beta font switching/mapping Petr Ferdus
2001-11-25 11:26 ` pdf font resource support Petr Ferdus
[not found] ` <Pine.BSF.3.96.1011125122544.11290A-100000@vertigo.fme.vutb r.cz>
2001-11-26 11:27 ` Hans Hagen
[not found] <Pine.BSF.3.96.1010515225104.2197B-100000@vertigo.fme.vutbr .cz>
2001-05-18 14:10 ` typeseting XML Hans Hagen
2001-05-18 16:15 ` Petr Ferdus
[not found] ` <Pine.BSF.3.96.1010518180453.16005F-100000@vertigo.fme.vutb r.cz>
2001-05-18 16:53 ` Hans Hagen
2001-05-16 23:54 Petr Ferdus
2002-02-03 19:51 ` Johannes Hüsing
2002-02-05 8:26 ` Hans Hagen
2002-02-05 13:20 ` Taco Hoekwater
2002-02-05 13:57 ` Hans Hagen
2002-02-05 21:40 ` Johannes Hüsing
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=Pine.BSF.3.96.1010601083337.29526A-100000@vertigo.fme.vutbr.cz \
--to=pferdus@vertigo.fme.vutbr.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).