From: Leah Neukirchen via ntg-context <ntg-context@ntg.nl>
To: <ntg-context@ntg.nl>
Cc: Leah Neukirchen <leah@vuxu.org>, Max Chernoff <mseven@telus.net>
Subject: Re: LMTX generates PDFs with non-working fonts on real printers
Date: Wed, 12 Oct 2022 13:14:52 +0200 [thread overview]
Message-ID: <87czaxcmz7.fsf@vuxu.org> (raw)
In-Reply-To: <9055e47ef181dbf215c9563199b3eb00ba970213.camel@telus.net> (Max Chernoff via ntg-context's message of "Tue, 11 Oct 2022 22:56:27 -0600")
Max Chernoff via ntg-context <ntg-context@ntg.nl> writes:
> Hi Leah,
>
>
>> > Leah and I are zooming in on the issue. It might relate to wrong font
>> > matrix default behavior in the pdf printer driver, and GS got a fix
>> > for that long ago, so maybe old printers with not-updated drivers can
>> > be affected.
>> >
>> > Once we're confident that we can catch it Leah (who does the low level
>> > introspective testing with viewers, printers and tools) likely will
>> > report on it and there will be a test file for users to test if what
>> > we do is okay before we apply the safeguard.
>>
>> There's a write up now on the issue:
>> https://leahneukirchen.org/blog/archive/2022/10/50-blank-pages-or-black-box-debugging-of-pdf-rendering-in-printers.html
>
> Great write up! I was expecting the issue to be something quite simple,
> but it's actually fairly complicated. Especially considering that the
> issue only happens with a few printer models, I'm pretty impressed that
> you managed to find the problem. At least the fix appears quite easy.
>
> Seeing that you're modifying the font encoding, could you perhaps
> reconsider supporting hinting in LMTX?
>
> https://mailman.ntg.nl/pipermail/ntg-context/2022/106311.html
>
> Even with a high resolution screen, I can still see a difference, and
> the issue can show up in print too:
>
>
> https://graphicdesign.stackexchange.com/q/5874
>
> I'm fairly confident that these issues are all hinting-related:
>
> https://mailman.ntg.nl/pipermail/ntg-context/2022/106874.html
> https://mailman.ntg.nl/pipermail/ntg-context/2022/105212.html
>
> Considering that all of the fonts included with ConTeXt are hinted, it
> seems like a shame to not include any of that data in the generated
> PDFs.
The last version of font-cff.lua should also copy the hinting-related
values of the CFF properly (/BlueScale, /StemSnap[HV] etc).
We fixed that on the side. ;)
--
Leah Neukirchen <leah@vuxu.org> https://leahneukirchen.org
___________________________________________________________________________________
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-10-12 11:14 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 17:17 Leah Neukirchen via ntg-context
2022-10-03 18:57 ` Leah Neukirchen via ntg-context
2022-10-05 16:02 ` Pablo Rodriguez via ntg-context
2022-10-05 21:25 ` Hans Hagen via ntg-context
2022-10-03 21:57 ` Hans Hagen via ntg-context
2022-10-03 22:34 ` Leah Neukirchen via ntg-context
2022-10-04 2:16 ` Angel M Alganza via ntg-context
2022-10-04 7:33 ` Hans Hagen via ntg-context
2022-10-04 10:53 ` Leah Neukirchen via ntg-context
2022-10-04 11:54 ` Hans Hagen via ntg-context
2022-10-04 12:35 ` Leah Neukirchen via ntg-context
2022-10-04 12:50 ` Hans Hagen via ntg-context
2022-10-04 12:54 ` Hans Hagen via ntg-context
2022-10-04 15:52 ` Leah Neukirchen via ntg-context
2022-10-04 16:29 ` Hans Hagen via ntg-context
2022-10-04 12:59 ` Hans Hagen via ntg-context
2022-10-04 15:44 ` Henning Hraban Ramm via ntg-context
2022-10-04 16:11 ` Hans Hagen via ntg-context
2022-10-04 17:23 ` Henning Hraban Ramm via ntg-context
2022-10-04 11:59 ` Henning Hraban Ramm via ntg-context
2022-10-04 13:21 ` Angel M Alganza via ntg-context
2022-10-04 16:03 ` Henning Hraban Ramm via ntg-context
2022-10-04 16:09 ` Hans Hagen via ntg-context
2022-10-06 10:31 ` Ulrike Fischer via ntg-context
2022-10-06 11:23 ` Hans Hagen via ntg-context
2022-10-06 12:42 ` Leah Neukirchen via ntg-context
2022-10-06 14:23 ` Hans Hagen via ntg-context
2022-10-06 16:42 ` Leah Neukirchen via ntg-context
2022-10-09 6:03 ` Max Chernoff via ntg-context
2022-10-09 10:08 ` Hans Hagen via ntg-context
2022-10-11 19:07 ` Leah Neukirchen via ntg-context
2022-10-12 4:41 ` Aditya Mahajan via ntg-context
2022-10-12 4:56 ` Max Chernoff via ntg-context
2022-10-12 11:14 ` Leah Neukirchen via ntg-context [this message]
2022-10-12 22:50 ` Max Chernoff via ntg-context
2022-10-13 17:41 ` Pablo Rodriguez via ntg-context
2022-10-13 18:36 ` Henning Hraban Ramm via ntg-context
2022-10-13 20:35 ` Hans Hagen via ntg-context
2022-10-13 20:32 ` Hans Hagen via ntg-context
2022-10-13 19:30 ` Willi Egger 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=87czaxcmz7.fsf@vuxu.org \
--to=ntg-context@ntg.nl \
--cc=leah@vuxu.org \
--cc=mseven@telus.net \
/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).