From: Idris Samawi Hamid <ishamid@lamar.colostate.edu>
Subject: RE: Defining new font switches (solved?)
Date: Fri, 8 Apr 2005 15:43:49 -0600 [thread overview]
Message-ID: <4267D445@webmail.colostate.edu> (raw)
Ok, I think I have come closer to understanding the \definestyle problem. The
problem (bug?) is in \definetypeface. Consider the following test typescript:
==============type-testlm.tex===============
\definestyle [mvmystyle] [\mv] []
\starttypescript [serif] [mystyle] [name]
\definefontsynonym [MySerif] [cmcsc10]
\definefontsynonym [Serif] [MySerif]
\stoptypescript
\starttypescript [serif] [mystyle] [size]
\definebodyfont
[20.7pt,17.3pt,14.4pt,12pt,11pt,10pt,
9pt,8pt,7pt,6pt,5pt,4pt]
[rm]
[tf=Serif sa 1,
mv=Serif sa 1]
\stoptypescript
\starttypescript [MYTest]
\definebodyfontenvironment
[mytest]
[default]
[interlinespace=2.8ex]
\definetypeface [mytest] [rm] [serif] [mystyle]
%[mystyle] [encoding=default]
\stoptypescript
==============================================
Now consider the following test file:
===========test.tex================
% output=pdf interface=en
\usetypescriptfile[type-testlm]
\usetypescript[MYTest]
\setupbodyfont[mytest,12pt]
\starttext
{\tf This is a test.}
{\normal This is a test.}
{\mv This is a test.}
{\mvmystyle This is a test.}
\stoptext
=================================
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.
Why do predefined switches like \tf work with 4 options while user-defined
style options fail? Is this a bug or feature (seems inconsistent)?
Thnx in advance as always, and happy weekend
Idris
============================
Professor Idris Samawi Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
next reply other threads:[~2005-04-08 21:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-08 21:43 Idris Samawi Hamid [this message]
2005-04-08 23:09 ` Adam Lindsay
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=4267D445@webmail.colostate.edu \
--to=ishamid@lamar.colostate.edu \
--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).