From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: juh via ntg-context <ntg-context@ntg.nl>
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: Re: PDF viewer
Date: Sun, 25 Sep 2022 18:41:55 +0200 [thread overview]
Message-ID: <9e48cc16-43ef-c0c5-bdb7-548240499e3a@gmx.es> (raw)
In-Reply-To: <YzBywdP8lagiziuv@odysseus>
On 9/25/22 17:24, juh via ntg-context wrote:
> Am Thu, Sep 22, 2022 at 06:47:50PM -0600 schrieb Max Chernoff via ntg-context:
>> I think that pdf.js (the Firefox PDF viewer) meets most of these
>> requirements. There are a few requirements that it doesn't meet, but
>> it's open source and written in JavaScript, so we should be able to add
>> anything that's missing.
>
> I found a nasty bug in firefox.
>
> https://mailman.ntg.nl/pipermail/ntg-context/2022/105212.html
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=1781022
As Jonathan Kew explained, TeX Gyre Heros is also poorly displayed with
Acrobat. The issue may be trickier than we thought (since fixing Firefox
with Heros+LMTX is only part of the issue).
Just as a personal note, I tend to avoid using Heros with LMTX, since
resulting PDF documents may be displayed (poorly on screen) with Acrobat.
I wonder whether this is related to common code for both Acrobat and
Firefox (originally comming from
https://lists.nongnu.org/archive/html/freetype-devel/2013-05/msg00000.html).
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:[~2022-09-25 16:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 18:07 Henning Hraban Ramm via ntg-context
2022-09-23 0:47 ` Max Chernoff via ntg-context
2022-09-23 2:30 ` Alan Braslau via ntg-context
2022-09-23 7:59 ` Henning Hraban Ramm via ntg-context
2022-09-23 10:18 ` Max Chernoff via ntg-context
2022-09-23 15:56 ` Pablo Rodriguez via ntg-context
2022-09-23 15:34 ` Bruce Horrocks via ntg-context
2022-09-25 15:24 ` juh via ntg-context
2022-09-25 16:41 ` Pablo Rodriguez via ntg-context [this message]
2022-09-23 9:52 ` luigi scarso via ntg-context
2022-09-23 15:23 ` Pablo Rodriguez via ntg-context
2022-09-26 14:44 ` Willi Egger via ntg-context
2022-09-26 17:15 ` Pablo Rodriguez 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=9e48cc16-43ef-c0c5-bdb7-548240499e3a@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).