From: Giuseppe Bilotta <gip.bilotta@iol.it>
Subject: Re: parameter mechanism
Date: Wed, 27 Aug 2003 16:56:40 +0200 [thread overview]
Message-ID: <7521020275.20030827165640@iol.it> (raw)
In-Reply-To: <3F4CB2F0.2020705@arcor.de>
Wednesday, August 27, 2003 Peter Rolf wrote:
PR> Hello all,
PR> I have problems to understand the command (parameter) mechanism of context.
PR> My experiments with \getparameters didn't work, so I used
PR> \xdescgetparameters
PR> from Giuseppe Bilotta (t-xdesc.tex).
PR> In my eyes they look the same, but \xdescgetparameters works with my sample
PR> code, \getparameters don't. Mhhh....
PR> % t-xdesc.tex
PR> \def\xdescsetvalue#1#2{\expandafter\def\csname#1#2\endcsname}
PR> \def\xdescgetparameters{\dogetparameters\xdescsetvalue}
PR> % syst-gen.tex
PR> \def\dosetvalue#1#2% #3
PR> {\@EA\def\csname#1#2\endcsname} % {#3}}
PR> \def\getparameters {\dogetparameters\dosetvalue}
PR> This leads me to my two questions:
PR> What must I change, to make my test example run with \getparameters?
The trick is in mult-ini.tex, which redefines dosetvalue & co
to support the multilingual interface; this is a problem when
you want to get raw (unconverted) keyword/value sets, which is
why it fails. ConTeXt used to have "raw" version of the
do..value commands, but they disappeared at one point. Yes,
they should be re-introduced.
--
Giuseppe "Oblomov" Bilotta
next prev parent reply other threads:[~2003-08-27 14:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-27 13:32 Peter Rolf
2003-08-27 14:56 ` Giuseppe Bilotta [this message]
2003-08-27 16:53 ` Hans Hagen
2003-08-27 17:03 ` Re[2]: " Giuseppe Bilotta
2003-08-27 17:22 ` Re[3]: " Giuseppe Bilotta
2003-08-28 8:38 ` Hans Hagen
2003-08-28 10:49 ` Peter Rolf
2003-08-27 16:54 ` Hans Hagen
2003-08-27 16:55 ` Patrick Gundlach
2003-08-27 19:18 ` Simon Pepping
2003-08-27 20:33 ` Patrick Gundlach
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=7521020275.20030827165640@iol.it \
--to=gip.bilotta@iol.it \
--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).