ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Adam Lindsay" <atl@comp.lancs.ac.uk>
Subject: Re: Defining new font switches (solved?)
Date: Sat, 9 Apr 2005 00:09:17 +0100	[thread overview]
Message-ID: <20050409000917.6990@mail.comp.lancs.ac.uk> (raw)
In-Reply-To: <4267D445@webmail.colostate.edu>

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@comp.lancs.ac.uk
 Lancaster University, InfoLab21        +44(0)1524/510.514
 Lancaster, LA1 4WA, UK             Fax:+44(0)1524/510.492
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2005-04-08 23:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-08 21:43 Idris Samawi Hamid
2005-04-08 23:09 ` Adam Lindsay [this message]
2005-04-09  2:07 Idris Samawi Hamid

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=20050409000917.6990@mail.comp.lancs.ac.uk \
    --to=atl@comp.lancs.ac.uk \
    --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).