From: Thomas A.Schmitz <thomas.schmitz@uni-bonn.de>
Subject: Re: finishing a module
Date: Sun, 23 Jan 2005 15:42:30 +0100 [thread overview]
Message-ID: <02549B04-6D4D-11D9-B338-000A95B9ADE2@uni-bonn.de> (raw)
In-Reply-To: <41F3AF5D.2090202@elvenkind.com>
Taco, I feel bad taking your time, but still no go. For clarity's sake,
I leave aside the scaling for the time being. I thought that after
unprotect
\def\setupgreek#1[#2]{%
\getparameters[GG][Scale=,Font=,#2]%Font,Scale
\xdef\MyScale{\GGScale}%
\processaction[\GGFont]
[ SomeFont=>\xdef\MyFont{somefont }]%
}
\protect
the macro \MyFont would always expand to "somefont ". But it doesn't
seem to do so in
\definefont[Gf][\MyFont]
I still get the error message. When I assign it "manually"
\definefont[Gf][somefont ]
it works. I tried every combination of \expanded, \xdef or \edef, but
it doesn't seem to work (while it does work in \definebodyfont). So it
must be something within ConTeXt that doesn't let it expand, and I
don't see how I could escape this problem. The \definebodyfont is a
workaround for now, but it has the problem that I have to give precise
font dimensions, which might fail in certain circumstances.
Thanks again
Thomas
On Jan 23, 2005, at 3:06 PM, Taco Hoekwater wrote:
> Thomas A.Schmitz wrote:
>>> This, however, will not work:
>>> \definefont[Gf][\MyFont sa \MyScale]
>
>> It looks like \MyFont doesn't get expanded when the \definefont
>> command is read, but this is an area of TeX that I find especially
>> opaque...
>
> I see. You need
>
> \expanded{\definefont[Gf][\MyFont sa \MyScale]}
>
> Or you could \xdef the MyScale (instead of \edef), making it global.
>
> Greetings, Taco
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>
next prev parent reply other threads:[~2005-01-23 14:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-22 20:41 Thomas A.Schmitz
2005-01-23 9:33 ` Taco Hoekwater
2005-01-23 13:33 ` Thomas A.Schmitz
2005-01-23 14:06 ` Taco Hoekwater
2005-01-23 14:42 ` Thomas A.Schmitz [this message]
2005-01-23 15:22 ` Taco Hoekwater
2005-01-23 21:24 ` h h extern
2005-01-24 14:06 ` Thomas A.Schmitz
2005-01-24 17:50 ` Hans Hagen
2005-01-24 17:50 ` Hans Hagen
2005-01-24 18:20 ` Thomas A.Schmitz
2005-01-24 18:03 ` Hans Hagen
2005-01-24 18:47 ` Thomas A.Schmitz
2005-01-25 14:56 ` h h extern
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=02549B04-6D4D-11D9-B338-000A95B9ADE2@uni-bonn.de \
--to=thomas.schmitz@uni-bonn.de \
--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).