ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Bruce Horrocks via ntg-context <ntg-context@ntg.nl>
To: ntg-context mailing list <ntg-context@ntg.nl>
Cc: Bruce Horrocks <ntg@scorecrow.com>
Subject: Re: [NTG-context] Font error in PDF using ConTeXt and Kepler typeface
Date: Tue, 25 Apr 2023 22:21:57 +0100	[thread overview]
Message-ID: <7C1F5796-0F48-4102-B5E6-F738B9FFB316@scorecrow.com> (raw)
In-Reply-To: <2462344ab9193bd3d61889dc43678297@polarcom.com>

Another check you can do is to run

  $ mtxrun --script font --list --name '--pattern=*kepler*'

and see if the file for keplerstd-light is the one you are expecting and not a second copy somewhere that is upsetting things.


> On 25 Apr 2023, at 21:40, lynx--- via ntg-context <ntg-context@ntg.nl> wrote:
> 
> Werner:
> This is the one that I think will help the most (taken from the Fonts out of Context manual, pp 147 - 148
> "If you want to use Lucida, all you have to do when you have bought the fonts, is to put
> the OpenType files in a place where they can be found, for instance:
> 
> tex/texmf-fonts/fonts/data/lucida
> 
> Of course you need to run mtxrun --generate afterwards so that the files can be found.
> 
> 
> 
> On 2023-04-25 12:34, lynx--- via ntg-context wrote:
>> Hello, Werner:
>> Have you tried some diagnostic tests, such as trying to get the PDF output via DVIPS? I suspect that you are, in fact, more knowledgeable and experience with ConTeXt than I am, but for what it is worth you may want to look at:
>>     • \setupoutput[dvips,acrobat] (see: Context-The Manual (Hans Hagen; English, page 24))
>>     • \showbodyfont[Options] (see: Not-so-short Intro to ConTeXt (J. Ataz-Lopez;English, page 114))
>>     • $ mtxrun  (mtxrun  is the ConTeXt TDS Runner Tool) command from a terminal window it has has a large number of options for finding the fonts installed, and for querying their characteristics (see: Fonts out of ConTeXt (Hans Hagen, pg 52 and ff))
>> Em
>> 
>> On 2023-04-25 08:50, Werner Schmidt via ntg-context wrote:
>> Hi conTeXt folks,
>> 
>> may I ask again. How could I debug the font typesetting of PDF files with conTeXt?
>> 
>> Any help is highly appreciated.
>> 
>> Best Werner
>> 
>> On April 21, 2023 1:29:18 PM UTC, Werner Schmidt via ntg-context <ntg-context@ntg.nl> wrote: Hi all,
>> 
>> I'd like to use the commercial Adobe Kepler typeface (Kepler Std - version 2.020) in conTeXt (v2023-04-15) as text (serif) font. Although the font files are loaded correctly (see log below), the generated PDF is unreadable (see attached image).
>> 
>> Notes:
>> - Only serif font (keplerstd-light.otf) is not working. It's not embedded in the generated PDF.
>> - italics and bold fonts are embedded and are rendered well
>> - Can't provide font files because Kepler is a commercial typeface
>> 
>> Do you have any ideas how to debug this issue?
>> 
>> Thanks Werner
>> 
>> log file:
>> mkiv lua stats > loaded fonts: 10 files: fontawesome6freesolid900.otf, frutigernextpro-bold.otf, frutigernextpro-regular.otf, iosevka-term-ss09-light.ttf, keplerstd-light.otf, keplerstd-lightcapt.otf, keplerstd-lightit.otf, keplerstd-semibold.otf, latinmodern-math.otf, lmroman10-regular.otf
>> mkiv lua stats > font engine: otf 3.133, afm 1.513, tfm 1.000, 30 instances, 18 shared in backend, 3 common vectors, 15 common hashes, load time 0.449 seconds
>> Example:
>> 
>> This text can't be read in PDF.par
>> {it However, italics are working.}par
>> {bold Also Bold and bfem BoldItalics!}par
>> input{zapf} 

> 

—
Bruce Horrocks
Hampshire, UK

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2023-04-25 21:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-21 13:29 Werner Schmidt via ntg-context
2023-04-25 15:50 ` Werner Schmidt via ntg-context
2023-04-25 19:34   ` lynx--- via ntg-context
2023-04-25 20:40     ` lynx--- via ntg-context
2023-04-25 21:21       ` Bruce Horrocks via ntg-context [this message]
2023-04-26 21:56         ` Werner Schmidt via ntg-context

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=7C1F5796-0F48-4102-B5E6-F738B9FFB316@scorecrow.com \
    --to=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).