From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Expansion problem in natural table
Date: Sun, 09 Feb 2003 21:26:27 +0100 [thread overview]
Message-ID: <5.1.0.14.1.20030209212337.0321af18@remote-1> (raw)
In-Reply-To: <20030208205254.GA1686@scaprea>
At 09:52 PM 2/8/2003 +0100, Simon Pepping wrote:
>This is my hack, but it is awful because it relies on an exact number
>of expansions:
>
>\expandafter\expandafter\expandafter\def
>\expandafter\expandafter\expandafter\!!stringa
>\expandafter\expandafter\expandafter{\csname XML:dat:#1\endcsname}
>\@EA\bTD\@EA\XMLDBcontinuepartrue\@EA\ignorespaces\!!stringa\eTD}
ah, the umlauts ...
even if it would work out ok, it looks to ugly, so how about:
\def\somethingsimon{blabla}
\bTABLE
\bTR\safeexpanded{\bTD\Aumlaut}\eTD\eTR
\bTR\safeexpanded{\bTD\noexpand\somethingsimon\Aumlaut}\eTD\eTR
\eTABLE
with in enco-ini:
\appendtoks
\keepencodedtokens
\to \everysafeexpanded
and in syst-gen:
\newtoks\everysafeexpanded
\long\def\safeexpanded#1%
{\begingroup
\the\everysafeexpanded\long\xdef\@@expanded{\noexpand#1}%
\endgroup
\@@expanded}
A more contexy alternative -)
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
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
next prev parent reply other threads:[~2003-02-09 20:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-08 20:52 Simon Pepping
2003-02-09 18:39 ` Simon Pepping
2003-02-09 20:43 ` Hans Hagen
2003-02-09 20:26 ` Hans Hagen [this message]
2003-02-18 20:11 ` Simon Pepping
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.20030209212337.0321af18@remote-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).