From: Nicola <nvitacolonna@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: How to use Helvetica Neue Light (OS X)?
Date: Thu, 11 Feb 2016 14:38:59 +0100 [thread overview]
Message-ID: <n9i2tj$aev$1@ger.gmane.org> (raw)
In-Reply-To: <56BC6A8D.5070708@gmail.com>
On 2016-02-11 11:03:41 +0000, Wolfgang Schuster said:
> Nicola 11. Februar 2016 um 11:49
> On 2016-02-11 10:32:14 +0000, Wolfgang Schuster said:
>
>
> Thanks! The typescript works for me, at least with the beta.
> This is no surprise because typescripts are contexts native way to load fonts
> and even the \definefontfamily command creates a typescript for your fonts.
Does the typescript rely on some features present in the beta but not in
TeX Live 2015? I ask because with ConTeXt from TeX Live the first two \input
blocks are typeset with the default font (Latin Modern, I think) and the last
two blocks in Avenir Next Light (no boldface). The log has:
fonts > otf loading > loading '/System/Library/Fonts/Avenir
Next.ttc', hash 'avenir-next-avenirnext-regular'
fonts > otf loading > loading done
fonts > otf loading > loading failed due to read error
fonts > defining > font with asked name 'Avenir Next' is not
found using lookup 'file'
fonts > defining > unknown font 'Avenir Next', loading aborted
fonts > defining > unable to define 'Avenir Next' as
'avenir-12pt-ss-tf-0--0'
[...]
fonts > otf loading > loading '/System/Library/Fonts/Avenir
Next.ttc', hash 'avenir-next-avenirnext-bold'
fonts > otf loading > loading done
fonts > otf loading > loading failed due to read error
fonts > defining > font with asked name 'Avenir Next' is not
found using lookup 'file'
fonts > defining > unknown font 'Avenir Next', loading aborted
fonts > defining > unable to define 'Avenir Next' as
'avenir-12pt-ss-bf-0--0'
[...]
fonts > otf loading > loading '/System/Library/Fonts/Avenir
Next.ttc', hash 'avenir-next-avenirnext-medium'
fonts > otf loading > loading done
fonts > otf loading > loading failed due to read error
fonts > defining > font with asked name 'Avenir Next' is not
found using lookup 'file'
fonts > defining > unknown font 'Avenir Next', loading aborted
fonts > defining > unable to define 'Avenir Next' as
'avenir-light-12pt-ss-bf-0--0'
Nicola
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2016-02-11 13:38 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
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 [this message]
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='n9i2tj$aev$1@ger.gmane.org' \
--to=nvitacolonna@gmail.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).