ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Thomas A.Schmitz <thomas.schmitz@uni-bonn.de>
Subject: Re: processaction in keyval lists[SOLVED]
Date: Sat, 22 Jan 2005 17:37:45 +0100	[thread overview]
Message-ID: <F1720F00-6C93-11D9-92C7-000A95B9ADE2@uni-bonn.de> (raw)
In-Reply-To: <6DAABEA8-6C86-11D9-92C7-000A95B9ADE2@uni-bonn.de>

Answering my own question, and apologizing for the noise: after having  
a look at some instances of \processaction in the source, I just took  
out \expandafter before and after \processaction; now it works. I'm  
just getting a mysterious pair of brackets in my pdf, but I'll try and  
hunt that down, too.

Best

Thomas
On Jan 22, 2005, at 4:01 PM, Thomas A.Schmitz wrote:

> All,
>
> I couldn't resist spending some time today working on the Greek  
> problem. I'm trying to write a proper module that would allow me to  
> set up definitions for fonts and scaling. But I'm running into a  
> problem  that is beyond my meagre TeX abilities. I want to define the  
> setup-command like so (using code that Taco send to the list a couple  
> of months ago and that can be found on the wiki):
>
> \unprotect
>
> \def\setupgreek{\dodoubleempty\dosetupgreek}
>
> \def\dosetupgreek#1[#2]{%
>   \getparameters[GG][Scale=,Font=,#2]%Font,Scale
> \edef\MyScale{\GGScale}%
> \expandafter\processaction\expandafter[\GGFont]
>    [SomeFont1     =>\def\MyFont{somefont },
>     SomeFont2     =>\def\MyFont{someotherfont }]
> }
>
> \protect
>
> \definebodyfont[4pt,5pt,6pt,7pt,8pt,9pt,10pt,10.5pt,11pt,12pt,14pt,14.4 
> pt,16pt,18pt,20pt,22pt][rm][Gf=\MyFont sa \MyScale]
>
> So I want this setup
> \setupgreek[Scale=1.5,Font=SomeFont1]
> to be expanded to somefont scaled at 1.5.
>
> However, when I process a file, I always get this error:
>
> ! Undefined control sequence.
> <argument> \MyFont
>                    sa \MyScale
> \parsefontspec #1->\xdef \somefontspec {#1
>                                           \space }\@EA  
> \doparsefontspec \som...
>
> \xxdododefinefont ...tsize {#2}\parsefontspec {#4}
>                                                   \newfontidentifier  
> \let \l...
>
> \fontstrategy ...ame #1\csname #2#3#4#5\endcsname
>                                                   \tryingfontfalse \fi
> <inserted text> ...yle \fontalternative \fontsize
>                                                   \fi \iftryingfont  
> \fontstr...
>
> \synchronizefont ...strategy \the \fontstrategies
>                                                   \relax \fi  
> \ifskipfontchar...
> ...
>
> When I add this line
>
> \def\MyFont{somefont }
>
> to the module, files compile without problems. So I conclude: the  
> mistake is not in the definiton of MyFont itself, but my values are  
> not getting processed the proper way; something in the \processaction  
> part must be wrong. But I'm "stymied" here. Any suggestions would be  
> most welcome!
>
> Best
>
> Thomas
>
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>

  reply	other threads:[~2005-01-22 16:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-22 15:01 processaction in keyval lists Thomas A.Schmitz
2005-01-22 16:37 ` Thomas A.Schmitz [this message]
2005-01-23 21:04   ` processaction in keyval lists[SOLVED] 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=F1720F00-6C93-11D9-92C7-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).