From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>, ntg@scorecrow.com
Subject: Re: Problem using a TTF font
Date: Sat, 7 Nov 2020 15:48:31 +0100 [thread overview]
Message-ID: <b50316b4-bb49-5c7e-b97e-061503816fd8@xs4all.nl> (raw)
In-Reply-To: <93E32F3C-C326-4183-8AE9-89742502EA36@scorecrow.com>
On 11/6/2020 3:54 PM, ntg@scorecrow.com wrote:
> This, I'm certain, used to work with an LMTX from the beginning of the year but I've upgraded to "ConTeXt ver: 2020.11.05 23:01 LMTX fmt: 2020.11.6 int: english/english" and now it doesn't.
>
> I have a single .tex file in a directory, containing:
>
> ---begin---
> \definefont [TwelveC] [file:Bondi12CPlus.TTF at 14pt]
> \starttext
> Keycaps: \TwelveC 123.45 \tf and back again
> \stoptext
> ---end---
>
> In the same directory I have the TTF font file which can be obtained from <https://www.educalc.net/2336507.page>. It is calculator keycap images for use in documentation.
>
> In the PDF I get just blank space where the keycaps should be and Adobe Reader's document info seems to think there is only one font in the file i.e. the keycap font didn't get embedded. However, the console output includes the lines:
>
> mkiv lua stats > result saved in file: 12C_test.pdf, compresslevel 3, objectcompresslevel 1
> mkiv lua stats > loaded patterns: en::1, load time: 0.000
> mkiv lua stats > loaded fonts: 3 files: latinmodern-math.otf, lmroman12-regular.otf, bondi12cplus.ttf
> mkiv lua stats > font engine: otf 3.111, afm 1.513, tfm 1.000, 8 instances, 3 shared in backend, 3 common vectors, 0 common hashes, load time 0.132 seconds
> mkiv lua stats > font embedding time: 0.006 seconds, 2 fonts
>
> which suggests LMTX thinks it loaded the font but decided not to embed it for some reason.
>
> I'm probably doing something silly since it's been several months since I last looked at this but I can't see what I might be doing wrong :-( so any and all help much appreciated.
>
> PS: The font installs and displays in MacOS fine.
>
> I've also tried
> \definefont [TwelveC] [Bondi12CPlus at 14pt]
> and that fails the same way.
for now rename the file to one with a lowercase suffix (i'll check for
that)
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2020-11-07 14:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 14:54 ntg
2020-11-07 14:48 ` Hans Hagen [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=b50316b4-bb49-5c7e-b97e-061503816fd8@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.nl \
--cc=ntg@scorecrow.com \
/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).