From: luigi scarso via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: luigi scarso <luigi.scarso@gmail.com>,
Mikael Sundqvist <mickep@gmail.com>
Subject: Re: update / punctuation / math
Date: Sun, 2 Apr 2023 11:19:05 +0200 [thread overview]
Message-ID: <CAG5iGsCNSuF58aVTFd-edZnHu5o6_o9tV4HPe_FGQZ2nVqeacg@mail.gmail.com> (raw)
In-Reply-To: <CAHy-LL-f8=uynMHhAJ+pM4WJfvR1atvdJymCnM3rjFpU2+xG+g@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1006 bytes --]
On Sun, 2 Apr 2023 at 11:06, Mikael Sundqvist via ntg-context <
ntg-context@ntg.nl> wrote:
>
> If you talk about the math font, I do not see what you mean. Daniel
> has worked a lot on his fonts, and they now work well.
>
indeed the body font is not concrete opentype math but it looks very
similar at first sight
(of course... ). I was deceived because I remember its shapes quite well (C
,g a ).
>
> If you talk about the text font, Hans changed the concrete typescript
> so that it uses the variable "mono" Latin modern instead of the
> concrete text font that comes from Computer modern unicode. But the
> font is also boldened slightly, and perhaps that is what causes your
> problem (It did look weird on my phone for half a second or so before
> it "got normal"). In okular I see no problems.
>
>
here evince & mupdf are quite ok (evince somewhat bolder than mupdf),
okular looks not so good. They all have a caching-something,
after the first zooms the pdf is rendered differently.
--
luigi
[-- Attachment #1.2: Type: text/html, Size: 1630 bytes --]
[-- Attachment #2: Type: text/plain, Size: 496 bytes --]
___________________________________________________________________________________
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 9:19 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 [this message]
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
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=CAG5iGsCNSuF58aVTFd-edZnHu5o6_o9tV4HPe_FGQZ2nVqeacg@mail.gmail.com \
--to=ntg-context@ntg.nl \
--cc=luigi.scarso@gmail.com \
--cc=mickep@gmail.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).