[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Re: #5201 Use -b together with -dgs-never-embed-fonts

2017-10-02 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto
Yes, it might be pushed. --- ** [issues:#5201] Use -b together with -dgs-never-embed-fonts** **Status:** Started **Created:** Sat Sep 23, 2017 03:53 PM UTC by Knut Petersen **Last Updated:** Mon Oct 02, 2017 08:55 AM UTC **Owner:** Knut Petersen Use -b together with -dgs-never-embed-fonts Si

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Re: #5201 Use -b together with -dgs-never-embed-fonts

2017-10-07 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto
I vote to include this patch in lilypond 2.20. Changing the code for print_glyph, trying to force Identity-H, supporting other notation fonts with the old --bigpdf or the new --pspdfopt=TeX-GS options and some other optimizations is definitely something for 2.21. --- ** [issues:#5201] Use -b

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Re: #5201 Use -b together with -dgs-never-embed-fonts

2017-10-10 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto
"this patch", as I understand it being the Rietveld issue in its final state, removed --bigpdf completely. At least that's what patch set 2 and patch set 3 claim in their message. It has a scope that was quite exceeding the scope that was agreed on to be sensible for 2.20 on the developer list

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Re: #5201 Use -b together with -dgs-never-embed-fonts

2017-10-10 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto
> "this patch", as I understand it being the Rietveld issue in its final state, > removed --bigpdf completely. Yes. > This here is issue 5201, and the commit message for this issue states: commit 398c2e17d45bf4d18723e14d52531e4e7d006dea Yes. It's completely useless with gs 9.22. > At least