From: Michael Urban <urban.m@ca.rr.com>
To: ntg-context@ntg.nl
Subject: OK, I Don't Quite Understand \definefontfamily
Date: Fri, 25 Sep 2020 12:12:35 -0700 [thread overview]
Message-ID: <137E7B2C-DFE3-4169-921A-7B363D6139A6@ca.rr.com> (raw)
I don't seem quite able to put it all together, forgive the question.
I have a 'Bookman' font setup, pretty vanilla:
\definetypeface [Bookman] [rm] [serif] [bonum] [sl=name:unituscndboldoblique]
\definetypeface [Bookman] [tt] [mono] [modern] [default]
\definetypeface [Bookman] [ss] [sans] [unitus] [default]
\definetypeface [Bookman] [mm] [math] [modern] [default]
(Unitus is the fontsite 500 'Univers' substitute, works fine)
Now, the built-in gyre bonum font doesn't have a slanted/oblique variant, so if I have Bookman as my main body
font, \sl produces (unsurprisingly) the same result as \it, TexGyreBonum-Italic. If I want \sl to summon
Latin Modern for the variant, I have tried variations on
\definetypeface [Bookman] [rm] [serif] [bonum] [sl=file:Latin Modern Roman Slanted]
but to no avail — not helped by the fact that the \definetypeface contextgarden page doesn't have any pointer to just what that fifth
argument can contain.
How do I accomplish this?
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2020-09-25 19:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 19:12 Michael Urban [this message]
2020-09-25 21:45 ` Michael Urban
2020-09-28 19:39 ` Wolfgang Schuster
2020-09-28 21:49 ` Michael Urban
2020-09-29 14:10 ` Wolfgang Schuster
2020-09-29 17:07 ` Michael Urban
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=137E7B2C-DFE3-4169-921A-7B363D6139A6@ca.rr.com \
--to=urban.m@ca.rr.com \
--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).