From: Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl>
To: Leah Neukirchen via ntg-context <ntg-context@ntg.nl>
Cc: Henning Hraban Ramm <texml@fiee.net>
Subject: Re: Help test a LMTX bug fix: tweaks in PDF generation
Date: Sun, 9 Oct 2022 19:20:18 +0200 [thread overview]
Message-ID: <c688713f-0899-3f08-6ddc-7de4ad69812c@fiee.net> (raw)
In-Reply-To: <877d19dnbe.fsf@vuxu.org>
Am 09.10.22 um 17:33 schrieb Leah Neukirchen via ntg-context:
> Hi,
>
> last week we had a long thread about non-printing PDF on this list and
> together with Hans I tracked down the issue and we found a fix.
> Since it changes some details of how PDFs are generated by LMTX, we'd
> like to test this change first on a wide range of software and
> printers.
>
> So please: Try to preview and then try to print the attached PDF;
> and report back if either preview or printout does not look like
> the attached reference PNG image (i.e. something is missing,
> the fonts look different, or have wrong relative size.)
>
> If you use other PDF tools in your workflow, please also check they
> continue to work as before (and just as well as with MKIV-generated PDFs).
Hi Leah, thank you!
I viewed and printed the PDF with pdf.js in Thunderbird, Apple Preview
and Adobe Acrobat Pro 9 to my Kyocera FS-C5100DN color laserprinter via
KPDL (PS-compatible) driver.
I don’t see any font problems, but neither text nor the bar are 100%
black – is this intentional? Doesn’t look like RGB black, there are no
other colors involved except in the printout from pdf.js.
pdf.js seems to print as image and blurs the outlines. (I never tried to
print from pdf.js before, is this normal?)
Hraban
___________________________________________________________________________________
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-09 17:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-09 15:33 Leah Neukirchen via ntg-context
2022-10-09 17:20 ` Henning Hraban Ramm via ntg-context [this message]
2022-10-09 18:54 ` Leah Neukirchen via ntg-context
2022-10-10 8:50 ` Keith McKay via ntg-context
2022-10-10 9:24 ` Henning Hraban Ramm via ntg-context
2022-10-10 12:43 ` Willi Egger via ntg-context
2022-10-10 13:24 ` Rik Kabel via ntg-context
2022-10-10 15:31 ` Pablo Rodriguez via ntg-context
2022-10-11 11:26 ` Gerion Entrup 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=c688713f-0899-3f08-6ddc-7de4ad69812c@fiee.net \
--to=ntg-context@ntg.nl \
--cc=texml@fiee.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).