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 
http://www.ghostscript.com/cgi-bin/findgit.cgi?04a517f39cc3e2 is that the 
workaround suggested by Ken Sharp in 
https://bugs.ghostscript.com/show_bug.cgi?id=700367 is also broken, see 
https://bugs.ghostscript.com/show_bug.cgi?id=700436.

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.

Knut


_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Reply via email to