From: Michael Murphy <michael.murphy@uni-ulm.de>
To: ntg-context@ntg.nl
Subject: getting new font variants to work
Date: Thu, 03 Jun 2010 13:52:51 +0200 [thread overview]
Message-ID: <4C079793.4090309@uni-ulm.de> (raw)
In-Reply-To: <20100602223233.GA8009@urvas>
Hi all,
I'd like to get some new font variants defined, such as Medium,
Semibold, etc. What I have so far is the following.
\definealternativestyle[medium][\me][]
\starttypescript [serif] [minionpro]
...
\definefontsynonym[MinionPro-Medium][name:MinionPro-Medium]
...
\stoptypescript
\starttypescript [serif] [minionpro] [name]
...
\definefontsynonym[SerifMedium][MinionPro-Medium]
...
\stoptypescript
\starttypescript [serif] [regular] [size]
\definebodyfont [10pt, 11pt, 12pt] [rm] [%
it=SerifItalic sa 1,
bi=SerifBoldItalic sa 1,
bf=SerifBold sa 1,
tf=SerifRegular sa 1,
me=SerifMedium sa 1]
\stoptypescript
then I set up the font with
\definetypeface [adobe] [rm] [serif] [minionpro] [regular]
\setupbodyfont[11pt]
This all looks fine, but then
{\me This should be medium}
doesn't work, and neither does \me{...} or \medium{...}. I should say that
\definedfont[SerifMedium]
does work though. How can I fix this, short of
\def\me{\definedfont[SerifMedium]}
--
Michael Murphy
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2010-06-03 11:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 22:32 list of figures (bug?) Rogutės Sparnuotos
2010-06-03 11:52 ` Michael Murphy [this message]
2010-06-03 12:09 ` getting new font variants to work Bernhard Rosensteiner
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=4C079793.4090309@uni-ulm.de \
--to=michael.murphy@uni-ulm.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).