ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: How to use Helvetica Neue Light (OS X)?
Date: Wed, 10 Feb 2016 20:16:54 +0100	[thread overview]
Message-ID: <56BB8CA6.2040903@wxs.nl> (raw)
In-Reply-To: <n9fqmt$skj$1@ger.gmane.org>

On 2/10/2016 6:06 PM, Nicola wrote:
> On 2016-02-10 15:49:37 +0000, Taco Hoekwater said:
>
>> It seems the ttc extractor fails in the current beta, at least on osx.
>>
>> After a —reload of the fonts, I get similar results to Nicola: only one
>> indexed font is found for each of the .ttc files (always the last index).
>
> I have exactly the same for the beta. Let me add that things do not look
> right with ConTeXt from TeX Live either. Try this:
>
> 1) remove the cache from ~/Library/texlive/2015/texmf-var
> 2) luatools --generate
> 3) mtxrun --script fonts --list --all --pattern=avenirnextcondensed*
> 4) Typeset my test document using Avenir Next Condensed.
> 5) mtxrun --script fonts --reload
> 6) mtxrun --script fonts --list --all --pattern=avenirnextcondensed*
> 7) Typeset again.
>
> My results:
>
> 3) I see all the entries, plus some spurious ones, which are probably
>    synthesized by the script (e.g., avenirnextcondensedblack).
> 4) The PDF is an empty document (`unknown font` in the console).
> 6) I see only avenirnextcondensed and avenirnextcondensedbold: the rest
>    is gone.
> 7) The document is typeset in boldface (at least the font is found).

can you delete the fonts path in the texmf-cache

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
       tel: 038 477 53 69 | www.pragma-ade.com | 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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2016-02-10 19:16 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 [this message]
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

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=56BB8CA6.2040903@wxs.nl \
    --to=pragma@wxs.nl \
    --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).