Hi Adam, Thank you very much for explaining this. After some more research, I actually finally figured it out a few hours ago (including the examination of type-ini), but felt embarrased at bothering the list yet again about it;-) At least I'm "back in business" once again:-) Hopefully my hours of struggling with things like this will pay off in the end... Thnx again, Adam and my best to all Idris

===== Original Message From "Adam Lindsay" ===== 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.

============================ Professor Idris Samawi Hamid Department of Philosophy Colorado State University Fort Collins, CO 80523