From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: defining font family for several options
Date: Tue, 1 Sep 2020 22:36:29 +0200 [thread overview]
Message-ID: <24FB33D7-7B26-416F-A6ED-59B48C61D47C@fiee.net> (raw)
In-Reply-To: <1ce45396-e5f2-0986-722a-70c5e05a857d@gmail.com>
> Am 01.09.2020 um 05:22 schrieb jbf <roma83537@gmail.com>:
>
> Perhaps someone can assist me with the following query. I have a situation where I need to use more than one sans serif fonts (especially within complicated chapter heads). I currently have the following:
>
> \definefontfamily [mainface] [rm] [alegreya]
> \definefontfamily [mainface] [ss] [dax][tf=file:dax-regular]
> \definefontfamily [mainface] [mm] [alegreya]
> \setupbodyfont[mainface]
> \setupbodyfont[11pt]
>
> But what if I need to have, in addition to the Dax sans serif typeface, an additional sans serif typeface such as ITCAvantGarde? How do I declare that? Do I just give it another name, e.g. \definefontfamily[chapter][itcavantgarde] etc? If I did that, how then do I refer to it? Obviously not just as {\ss my text} since that would call in the dax font.
If you don’t need the roman font, you can (ab)use that. Or try handwriting/hw (it was commonly declared in MkII; didn’t try if it just works nowadays).
Otherwise, since you probably will use only special font variants in setups like headers, use something like \definedfont[ITCAvantGarde-Semibold*default at 36pt].
Hraban
___________________________________________________________________________________
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 prev parent reply other threads:[~2020-09-01 20:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 3:22 jbf
2020-09-01 20:36 ` Henning Hraban Ramm [this message]
2020-09-01 23:08 ` Aditya Mahajan
2020-09-01 23:22 ` jbf
2020-09-01 23:59 ` Otared Kavian
2020-09-02 0:10 ` jbf
[not found] ` <7e248e94-f223-6850-7b69-402939425229@gmail.com>
[not found] ` <DFAA6733-13EF-463A-9786-0E5352182E88@gmail.com>
[not found] ` <60f78515-9d33-c944-c8ad-9dcbc7053247@gmail.com>
[not found] ` <AAFB42C0-CCC0-47BD-8FAA-8E9E2EFBC73C@gmail.com>
2020-09-03 21:06 ` jbf
2020-09-03 21:16 ` Aditya Mahajan
2020-09-03 22:17 ` jbf
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=24FB33D7-7B26-416F-A6ED-59B48C61D47C@fiee.net \
--to=texml@fiee.net \
--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).