[NTG-context] Defining new font switches (solved?)

Adam Lindsay atl at comp.lancs.ac.uk
Sat Apr 9 01:09:17 CEST 2005


Idris Samawi Hamid said this at Fri, 8 Apr 2005 15:43:49 -0600:

>  \definetypeface [mytest] [rm] [serif] [mystyle]
>  %[mystyle] [encoding=default]

>Consider the  \definetypeface line. If we leave the comment in place,
>then the 
>\tf switch will work (and give us small caps) while the \mv switch will give 
>an undefined control sequence. If we uncomment the last two options in  
>\definetypeface, then \mv will also work.

this is absolutely consistent!
The second mystyle argument, the one that you commented out, is the
argument for the "size" typescripts. As you only define the mv
alternative in [serif] [mystyle] [size], that makes perfect sense. 

For further details, look at the definition in type-ini, which reduces
down to:
\def\definetypeface[#1][#2][#3][#4][#5][#6]
 {\usetypescript[#3,map][#4][name,default,\typefaceencoding,special]
  \usetypescript[#3][#5][size]}

In the commented out version, there's no #5, so it defaults to the
[serif] [default] [size] typescript. There's no \mv definition there, so
ConTeXt complains. When you correctly tell ConTeXt where to look, all is
right with the world.
-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Adam T. Lindsay, Computing Dept.     atl at comp.lancs.ac.uk
 Lancaster University, InfoLab21        +44(0)1524/510.514
 Lancaster, LA1 4WA, UK             Fax:+44(0)1524/510.492
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-



More information about the ntg-context mailing list