From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Alan Braslau <braslau.list@comcast.net>
Subject: Re: definefontfamily use
Date: Tue, 22 Jan 2019 19:39:05 +0100 [thread overview]
Message-ID: <6589a545-c249-5666-77e8-ddaf9e81b08a@xs4all.nl> (raw)
In-Reply-To: <20190122104233.3d5d15e8@comcast.net>
On 1/22/2019 6:42 PM, Alan Braslau wrote:
> Hello,
>
> Previously, in order to make punctual use of a true-type font in a title for example, I did the following:
>
> \definefontfamily [myfont] [serif] [myfont]
>
> where myfont.ttf is located in the current project directory, and selecting the font was simply
>
> {\switchtobodyfont[myfont]My Font!}
>
>
>
> Using the present context, this yields the error
>
> selectfont > The requested font 'myfont' has no files for the 'tf' alternative, Latin Modern is used instead.
>
> What has changed and what should be the proper use?
> (I have tried setting explicitly [tf=file:myfont.ttf], which was only a guess.)
one can do
\definefont[MyTitleFont][file:myfont.ttf*default sa 3]
\setuphead[chapter][style=\MyTitlefont]
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2019-01-22 18:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 17:42 Alan Braslau
2019-01-22 18:39 ` Hans Hagen [this message]
2019-01-22 18:57 ` Alan Braslau
2019-01-23 16:32 ` definefont (was: definefontfamily use) Henning Hraban Ramm
2019-01-23 16:37 ` definefont Wolfgang Schuster
2019-01-23 16:49 ` definefont (was: definefontfamily use) Alan Braslau
2019-01-23 17:03 ` definefont Wolfgang Schuster
2019-01-23 17:17 ` definefont Alan Braslau
2019-01-23 17:05 ` definefontfamily use Wolfgang Schuster
2019-01-23 17:22 ` Alan Braslau
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=6589a545-c249-5666-77e8-ddaf9e81b08a@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=braslau.list@comcast.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).