From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: defineXMLpush and grouping
Date: Sun, 10 Feb 2002 21:36:43 +0100 [thread overview]
Message-ID: <5.1.0.14.1.20020210213413.02edb700@server-1> (raw)
In-Reply-To: <20020208215856.A384@scaprea>
At 09:58 PM 2/8/2002 +0100, Simon Pepping wrote:
>\defineXMLpush actually makes its definition when the pushed element
>occurs. When a parent element defines a group, then the pushed element
>is not visible outside that group. In \TeX\ this problem is usually
>solved by doing a \gdef. Perhaps this problem can be solved in the
>same manner, by providing a \gdefineXMLpush.
Btw, push is now save (more correct name, but push will be available for
backward comp)
In xtag-ini search for \redoXMLsave and add:
\long\gdef\dododefineXMLgsave#1%
{\letvalue{\@@XMLdata:#1}\longempty
\long\setvalue{\@@XMLelement:#1/}{\long\setgvalue{\@@XMLdata:#1}{}}%
\long\setvalue{\@@XMLelement:#1}{\redoXMLgsave{#1}}}
\gdef\redoXMLgsave#1%
{\long\@EA\def\@EA\next\@EA##\@EA1\@EA<\@EA/\currentXMLelement>%
{\long\@EA\gdef\csname\@@XMLdata:#1\endcsname{##1}}%
\next}
regenerate the format and off you go. [this macro looks awful, which is due
to dynamic namespace mapping]
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-pod.nl
-------------------------------------------------------------------------
prev parent reply other threads:[~2002-02-10 20:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-08 20:58 Simon Pepping
2002-02-10 20:36 ` Hans Hagen [this message]
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.20020210213413.02edb700@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).