From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: fonts not found with newotf
Date: Mon, 20 Jul 2015 17:08:26 +0200 [thread overview]
Message-ID: <55AD0EEA.8010805@gmx.es> (raw)
In-Reply-To: <55AC2556.4090101@wxs.nl>
On 07/20/2015 12:31 AM, Hans Hagen wrote:
> On 7/19/2015 1:27 PM, Pablo Rodriguez wrote:
>>[...]
>> The attached newotf-error.log contains the error message.
>>
>> Since both font files were generated with FontForge, I would like to
>> know what they are missing to report upstream to the FontForge developers.
>
> there seems to be a cid entry operator seen when populating a private
> dictionary in the cff section
>
> you can add this in line 552 of font-cff:
>
> cid = {
> -- actually an error
> },
>
> and the font will probably load then, unless there is a fundamental flaw
> (i don't know where to get that font)
Many thanks for your fix, Hans.
It works perfectly fine. The font was an improved conversion from a
Type1 font I got from CTAN.
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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:[~2015-07-20 15:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-19 11:27 Pablo Rodriguez
2015-07-19 22:31 ` Hans Hagen
2015-07-20 15:08 ` Pablo Rodriguez [this message]
2015-07-20 20:47 ` Wolfgang Schuster
2015-07-22 14:01 ` Pablo Rodriguez
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=55AD0EEA.8010805@gmx.es \
--to=oinos@gmx.es \
--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).