[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: I cannot run make check since Issue 5450: Introduce new

From: Knut Petersen
Subject: Re: I cannot run make check since Issue 5450: Introduce new command `set?'
Date: Thu, 24 Jan 2019 00:22:56 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0

On 23.01.19 22:50, Thomas Morley wrote:

While I agree it has nothing to do with the current problem, it may be
an argument against _requirement_ of extractpdfmark
Though, I'm not familiar with this stuff, I may be wrong.

extractpdfmark saves more than 100 MB of disk space if you only look at the 
final documentation pdfs, a lot more if you also look at the intermediate files 
generated during the build process.

The real problem with gs commit is that the 
workaround suggested by Ken Sharp in is also broken, see

As far as I see we don't use CID fonts in our current documentation, so it's 
not a problem for master, staging or stable/2.20. But my private branch with 
CID versions of Emmentaler and other optimizations is affected, and anybody who 
uses CID fonts and pdf postprocessing (e.g. some lyluatex users).

Ghostscript is easy to build, and "git revert 04a517f39cc3e2" is the 
recommended fix until Ken decides that it is time to fix the broken workaround.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]