ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
Subject: again: new module mechanism
Date: Mon, 10 Apr 2006 11:13:26 +0200	[thread overview]
Message-ID: <E8FE8FA1-7A41-49A8-BC4C-7554F50762F4@uni-bonn.de> (raw)

All, and esp. Hans, Taco,

I'm still experimenting with the new moduleparameter mechanism. One  
thing I can't get to work is using it in a \definefont. Here's my  
minimal example:

\startmodule[mymod]

\unprotect

\setupmodule[font=Times]

\definefontsynonym[Times][ec-TimesNewRoman] % valid name

\definefont[myfont][\currentmoduleparameter{font}]

\message{The myfont is \currentmoduleparameter{font}}

\protect
\stopmodule
\endinput

\usemodule[mymod][font=Times]

\starttext

Hello world!

\myfont and hello again

\purefontname\font

\stoptext

In the log file, I get:

(./t-mymod.tex The myfont is Times)

So the definefont should work (if I define \definefont[myfont] 
[Times], I get the expected output), but the file fails to compile,  
with this error:

! Missing \endcsname inserted.
<to be read again>
                    \@@md:unknown:font
\truefontname #1->\ifcsname \??ff \fontclass #1
                                                \endcsname \@EA  
\truefontname...

\donoparsefontspec ...\truefontname \somefontname
                                                   }\ifx \fontfile \s! 
unknown...

\dododefinefont ...e \fontbody \parsefontspec {#2}
                                                   \rawfontidentifier  
\let \l...

\redodefinefont #1#2#3->\dododefinefont {#1}{#2}
                                                 \doifsetupselse {#3}  
{\setup...
l.7 \myfont
             and hello again
?
Process aborted

What am I missing?

Best

Thomas

             reply	other threads:[~2006-04-10  9:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-10  9:13 Thomas A. Schmitz [this message]
2006-04-10  9:45 ` Taco Hoekwater
2006-04-10 10:39   ` Thomas A. Schmitz

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=E8FE8FA1-7A41-49A8-BC4C-7554F50762F4@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).