From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: luigi scarso via ntg-context <ntg-context@ntg.nl>
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: Re: update / punctuation / math
Date: Sun, 2 Apr 2023 17:42:25 +0200 [thread overview]
Message-ID: <3cbb2ed6-19b8-fbca-cf5e-034dd1a996b3@gmx.es> (raw)
In-Reply-To: <CAG5iGsDXfj-0ogL2_Co4RC=Gza9fU06U8uhGRVMpyNmptxhz+Q@mail.gmail.com>
On 4/2/23 14:21, luigi scarso via ntg-context wrote:
> On Sun, 2 Apr 2023 at 13:57, Pablo Rodriguez via ntg-context wrote:
>
> Well, evince displays it wrong (this is an already known issue with fake
> bold fonts in evince/poppler, reported years ago
> https://gitlab.freedesktop.org/poppler/poppler/-/issues/645).
>
> hm, 4years ago, quite old... and this is not a fake bold, this is an
> instance of a variable font.
> But yes, it seems that evince still has the same problem.
Sorry, Luigi, I meant
http://mailman.ntg.nl/pipermail/ntg-context/attachments/20230401/1f8c6cc9/attachment-0001.pdf.
According to type-imp-concrete.mkiv, text has the feature boldened-10
applied to it.
Even with a variable font (which might not be the case in the link
above), extending the font fakes the bold, such as in:
\definefontfamily
[mainface]
[rm]
[Source Sans 3 VF]
[features={default, boldened-10}]
\setupbodyfont[mainface]
\starttext
\input zapf
\stoptext
Evince displays it poorly and this is what happens in the link above.
Pablo
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2023-04-02 15:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-01 8:27 Hans Hagen via ntg-context
2023-04-01 13:46 ` Willi Egger via ntg-context
2023-04-02 1:46 ` Alan Braslau via ntg-context
2023-04-02 8:35 ` luigi scarso via ntg-context
2023-04-02 9:05 ` Mikael Sundqvist via ntg-context
2023-04-02 9:19 ` luigi scarso via ntg-context
2023-04-02 11:57 ` Pablo Rodriguez via ntg-context
2023-04-02 12:21 ` luigi scarso via ntg-context
2023-04-02 15:42 ` Pablo Rodriguez via ntg-context [this message]
2023-04-02 9:29 ` luigi scarso via ntg-context
2023-04-02 9:41 ` Mikael Sundqvist 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=3cbb2ed6-19b8-fbca-cf5e-034dd1a996b3@gmx.es \
--to=ntg-context@ntg.nl \
--cc=oinos@gmx.es \
/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).