From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: How to use Helvetica Neue Light (OS X)?
Date: Thu, 11 Feb 2016 11:14:10 +0100 [thread overview]
Message-ID: <BA927D00-57CC-4CF8-8332-B9A72415D08F@elvenkind.com> (raw)
In-Reply-To: <n9hke3$pv2$1@ger.gmane.org>
> On 11 Feb 2016, at 10:31, Nicola <nvitacolonna@gmail.com> wrote:
>
> On 2016-02-11 08:36:12 +0000, Taco Hoekwater said:
>
>>> On 10 Feb 2016, at 21:04, Hans Hagen <pragma@wxs.nl> wrote:
>>> On 2/10/2016 5:44 PM, Nicola wrote:
>>>> On 2016-02-10 15:19:01 +0000, Pablo Rodriguez said:
>>>>> I’m not OS user, but the following works with Junction
>>>>> (https://www.theleagueofmoveabletype.com/junction):
>>>>> \definefontfamily[mainface][ss][Junction][tf=style:light]
>>>> Thanks, that indeed does the trick (modulo Taco's comment in another post).
>>> mtxrun --script font --reload —force
>> That fixed the issue for me.
>
> Not for me. After that command, I do see all the entries again, but when I
> typeset my document the font is not found. I paste the log below.
It looks like \definefontfamily depends on actual separate font files.
This worked for me:
\definefontfamily [myfamily] [serif] [Avenir Next Condensed]
[tf=name:Avenir Next Condensed Regular,
bf=name:Avenir Next Condensed Bold,
bi=name:Avenir Next Condensed Bold Italic,
it=name:Avenir Next Condensed Italic]
Best wishes,
Taco
___________________________________________________________________________________
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:[~2016-02-11 10:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 22:15 Nicola
2016-02-10 11:36 ` Nicola
2016-02-10 12:48 ` Hans Hagen
2016-02-10 13:51 ` Nicola
2016-02-10 14:13 ` Hans Hagen
2016-02-10 14:45 ` Nicola
2016-02-10 15:19 ` Pablo Rodriguez
2016-02-10 15:49 ` Taco Hoekwater
2016-02-10 17:06 ` Nicola
2016-02-10 19:16 ` Hans Hagen
2016-02-10 16:44 ` Nicola
2016-02-10 20:04 ` Hans Hagen
2016-02-11 8:36 ` Taco Hoekwater
2016-02-11 9:31 ` Nicola
2016-02-11 9:48 ` Hans Hagen
2016-02-11 10:14 ` Taco Hoekwater [this message]
2016-02-11 10:46 ` Nicola
2016-02-11 10:32 ` Wolfgang Schuster
2016-02-11 10:49 ` Nicola
2016-02-11 11:03 ` Wolfgang Schuster
2016-02-11 13:38 ` Nicola
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=BA927D00-57CC-4CF8-8332-B9A72415D08F@elvenkind.com \
--to=taco@elvenkind.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).