[NTG-context] Help test a LMTX bug fix: tweaks in PDF generation

Leah Neukirchen leah at vuxu.org
Sun Oct 9 20:54:15 CEST 2022


Henning Hraban Ramm via ntg-context <ntg-context at ntg.nl> writes:

> 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.

Should be all black (CMYK black), but we didn't change this.
Picking from the screenshot I get #000000 on Linux with evince, mupdf,
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?)

Yes, unfortunately.  But not related to our changes.

> Hraban

-- 
Leah Neukirchen  <leah at vuxu.org>  https://leahneukirchen.org/


More information about the ntg-context mailing list