ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Thangalin <thangalin@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Upgrade to 2015.11.19 breaks OTF reader?
Date: Thu, 3 Dec 2015 18:39:01 -0800	[thread overview]
Message-ID: <CAANrE7pW0Wn4O4BnCmjqieKADkvpcectW-MOK_h2KULn=pjF6g@mail.gmail.com> (raw)
In-Reply-To: <5660B447.6080805@wxs.nl>

The problem persisted with Courier New, not only Source Sans Pro (SSP).

The font file for Source Sans Pro came directly from the Google's font service.

The SSP (on my machine) works fine in Inkscape.

The exact same font was also working before the ConTeXt upgrade.
___________________________________________________________________________________
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:[~2015-12-04  2:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02 23:36 Thangalin
2015-12-02 23:41 ` Thangalin
2015-12-03  0:14   ` Thangalin
2015-12-03  7:27     ` Philipp Gesang
2015-12-03 13:35       ` Hans Hagen
2015-12-03 17:39         ` Philipp Gesang
2015-12-03 21:29           ` Hans Hagen
2015-12-04  2:39             ` Thangalin [this message]
2015-12-06 21:14               ` Philipp Gesang
2015-12-06 21:44                 ` Hans Hagen
2015-12-08  0:22                   ` Philipp Gesang
2015-12-10 23:10                     ` talazem
2015-12-11  9:15                       ` talazem
2015-12-11 22:51                       ` talazem
2015-12-12 10:32                         ` Philipp Gesang

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='CAANrE7pW0Wn4O4BnCmjqieKADkvpcectW-MOK_h2KULn=pjF6g@mail.gmail.com' \
    --to=thangalin@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).