ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: juh+ntg-context--- via ntg-context <ntg-context@ntg.nl>
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: Re: debugging lmtx and firefox (was: TeXGyre Heros on Firefox)
Date: Mon, 25 Jul 2022 19:52:00 +0200	[thread overview]
Message-ID: <e3097fe5-547f-7810-77b2-029a8b1b84ff@gmx.es> (raw)
In-Reply-To: <01d386fa-ea87-4502-250a-f4c0804502a8@mailbox.org>

[-- Attachment #1: Type: text/plain, Size: 1692 bytes --]

On 7/25/22 14:00, juh+ntg-context--- via ntg-context wrote:
>
> I reported the bug to Mozilla and they answered very fast.
>
> Sadly up too now without a good solution.

Many thanks for the bug report.

> They hint to LuaMetaTex as the cause of the problem. You can follow the
> discussion here.

I would like to compare the LMTX output with the one from LuaTeX.

Sadly, as already reported, LuaTeX doesn’t work on Linux anymore.

> https://bugzilla.mozilla.org/show_bug.cgi?id=1781022

From the two questions from Jonathan Kew, HTML with TeX Gyre Heros is
displayed fine.

I extracted the font from the PDF output document (with a source
document similar to
https://mailman.ntg.nl/pipermail/ntg-context/2022/106302.html) with
"mutools extract", but some info may be missing and Firefox cannot use
it to display the HTML file.

I extracted the font with Fontforge and it was displayed perfectly fine.
But I guess Fontforge is adding some info when generating the OTF font
(font size is bigger: 4KB and 2.3KB when extracted with mutools).

I’m no font expert, but what astonishes me is that it isn’t clear
whether the font has lost the hinting information or not with LMTX
(sorry if I got this wrong).

I have no idea whether Identity-H may be preventing the FreeType
autohinter from working properly. But ft-view (from freetype-demos)
displays poorly the font extracted without FontForge (unlike the font
extracted with it). I attach the first font.

After switching hinting from on to auto, the autohinter displays the
font way better.

To reproduce the issue "ftview  20 font-0009.otf" and press "a".

Just in case it might help,

Pablo

[-- Attachment #2: tgyre.html --]
[-- Type: text/html, Size: 1175 bytes --]

[-- Attachment #3: font-0009.otf --]
[-- Type: font/otf, Size: 2404 bytes --]

[-- Attachment #4: 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
___________________________________________________________________________________

  reply	other threads:[~2022-07-25 17:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10 12:44 TeXGyre Heros on Firefox juh via ntg-context
2022-03-10 14:57 ` Hans Hagen via ntg-context
2022-03-10 21:11   ` juh+ntg-context--- via ntg-context
2022-07-22 10:37 ` debugging lmtx and firefox (was: TeXGyre Heros on Firefox) juh+ntg-context--- via ntg-context
2022-07-22 17:34   ` Pablo Rodriguez via ntg-context
2022-07-22 21:41   ` Max Chernoff via ntg-context
2022-07-25 12:00     ` juh+ntg-context--- via ntg-context
2022-07-25 17:52       ` Pablo Rodriguez via ntg-context [this message]
2022-07-25 18:11         ` Hans Hagen via ntg-context
2022-07-25 18:19         ` luigi scarso via ntg-context
2022-07-26 15:34           ` Pablo Rodriguez via ntg-context
2022-10-16 18:43       ` Pablo Rodriguez via ntg-context
2022-10-19  8:31         ` juh 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=e3097fe5-547f-7810-77b2-029a8b1b84ff@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).