lilypond-devel
[Top][All Lists]
Advanced

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

Re: Replace `-dgs-load-fonts' to `--bigpdfs' in lilypond-book (issue 300


From: dak
Subject: Re: Replace `-dgs-load-fonts' to `--bigpdfs' in lilypond-book (issue 300280043 by address@hidden)
Date: Tue, 14 Jun 2016 06:32:09 -0700

On 2016/06/14 13:20:48, trueroad wrote:
> Mhmm.  As James writes, this can easily break.

My proposal never change the font selection method.

It changes the font embedding method for intermediate EPS.

Current "make doc" works as follows:

For all fonts, the font file name is embedded.
In other words, the font glyphs are not embedded.
So EPS file size can be small.

My proposal works as follows:

For "LilyPond fonts", the font file name is embedded.
For other fonts, the font glyphs are embedded.
In other words, most fonts file name is embedded. (Emmentaler and TeX
Gyre)
The glyphs of few fonts are embedded. (e.g. Linux Libertine etc.)
So EPS file size does not almost increase.

Either way, intermediate and final PDF is embedded subset fonts in the
same way.

I think that my proposal is temporary solution.

It can solve the problem that lilypond-book can not use OTC fonts.
In other words, "make doc" can use OTC fonts.
Required disk space for "make doc" does not almost increase.

If quickly the ideal can be achieved, my proposal is not required.

We are currently using about 4GB of disk space for building in spite of
-dgs-load-fonts being used.  Embedding/subsetting non-LilyPond fonts
seems like a plausible step but would further increase disk usage.  Does
anybody have an idea _why_ we currently use so much disk space even
while using -dgs-load-fonts and how we could get this under control?

https://codereview.appspot.com/300280043/



reply via email to

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