Re: Replace `-dgs-load-fonts' to `--bigpdfs' in lilypond-book (issue 300280043 by truer...@gmail.com)

>>> Do you have time to integrate this into lilypond in the near future? >> >> I would like so. My GUB environment can compile it for GUB inner >> using. (v1.0.0 could not compile.) >> >> But, I think that the integration requires a lot of time. > > Why? Please elaborate. At least, in order

Re: Replace `-dgs-load-fonts' to `--bigpdfs' in lilypond-book (issue 300280043 by truer...@gmail.com)

> At least, in order to avoid broken glyphs, we will need to change > whether or not embedding by the font type. OK, so the issue is not integrating `extractpdfmark' into lilypond but adjusting lilypond's font handling to make it work. > Moreover, we will need to change font resource directory

Re: Replace `-dgs-load-fonts' to `--bigpdfs' in lilypond-book (issue 300280043 by truer...@gmail.com)

>> Do you have time to integrate this into lilypond in the near future? > > I would like so. My GUB environment can compile it for GUB inner > using. (v1.0.0 could not compile.) > > But, I think that the integration requires a lot of time. Why? Please elaborate. Werner

Re: Replace `-dgs-load-fonts' to `--bigpdfs' in lilypond-book (issue 300280043 by truer...@gmail.com)

>>> I've just tested successfully the following method, except item 1, >>> which I've executed manually. [...] >> >> I've tried this way. [...] > > Thank you for your thorough testing, which obviously covers more > situations than my limited tries. > > BTW, I see that your `extractpdfmark'

Re: Replace `-dgs-load-fonts' to `--bigpdfs' in lilypond-book (issue 300280043 by truer...@gmail.com)

>> I've just tested successfully the following method, except item 1, >> which I've executed manually. [...] > > I've tried this way. [...] Thank you for your thorough testing, which obviously covers more situations than my limited tries. BTW, I see that your `extractpdfmark' tool has already

Re: Replace `-dgs-load-fonts' to `--bigpdfs' in lilypond-book (issue 300280043 by truer...@gmail.com)

If I understand the issue correctly, your solution overcomes the last obstacle with ghostscript, so we could actually start with an implementation :-) Unfortunately, Ghostscript 9.19 (newest release version) and prior versions cannot handle some PDF destination names.

Re: Replace `-dgs-load-fonts' to `--bigpdfs' in lilypond-book (issue 300280043 by truer...@gmail.com)

> Extracting page mode and named destinations as PDFmark from the font > less PDF. Both the PDF and the PDFmark are mixed by Ghostscript. Aaah! Very nice idea. If I understand the issue correctly, your solution overcomes the last obstacle with ghostscript, so we could actually start with an

Re: Replace `-dgs-load-fonts' to `--bigpdfs' in lilypond-book (issue 300280043 by truer...@gmail.com)

> Unfortunately, Ghostscript (ps2pdf) discards PDF destination names. > So remote PDF links do not work fine. > > http://bugs.ghostscript.com/show_bug.cgi?id=696943 > http://bugs.ghostscript.com/show_bug.cgi?id=695760 This is much more depressing :-( Isn't it possible to modify

Re: Replace `-dgs-load-fonts' to `--bigpdfs' in lilypond-book (issue 300280043 by truer...@gmail.com)

> Moreover, Ghostscript developers seem to want that `.loadfont' is > not used. > > http://bugs.ghostscript.com/show_bug.cgi?id=696823 > http://bugs.ghostscript.com/show_bug.cgi?id=696824 This is something we can trustfully ignore, I think, given that we resolve TTCs to Type42 and OTCs to bare

Re: Replace `-dgs-load-fonts' to `--bigpdfs' in lilypond-book (issue 300280043 by truer...@gmail.com)

On 2016/07/22 15:27:10, wl_gnu.org wrote: > ps2pdf -I \ > -dNOSAFER -P \ > Fontless.pdf WithEmbeddedFonts.pdf This should rather be ps2pdf -I \ -dNOSAFER \ Fontless.pdf WithEmbeddedFonts.pdf I've tested with the fonts in the current

Re: Replace `-dgs-load-fonts' to `--bigpdfs' in lilypond-book (issue 300280043 by truer...@gmail.com)

On 7/22/16 12:35 PM, "James" wrote: > >jlowe@jloweDesktop ~/lilypond-git/build/input $ du -smh * | sort -hr >1.9Gregression >8.0Kout-www >8.0Kout >4.0KGNUmakefile Do we turn off point and click when doing the doc builds? Carl

Re: Replace `-dgs-load-fonts' to `--bigpdfs' in lilypond-book (issue 300280043 by truer...@gmail.com)

James writes: > NB> It seems that the Japanese docs are built using its own 'build' > dir (i.e. it has its own out-www build doc and doesn't seem to share > any of the files the other docs do while building, but I am probably > not understanding this). > > Are we wasting build time

Re: Replace `-dgs-load-fonts' to `--bigpdfs' in lilypond-book (issue 300280043 by truer...@gmail.com)

hello, On 22/07/16 18:48, Carl Sorensen wrote: On 7/22/16 9:35 AM, "lilypond-devel on behalf of David Kastrup" wrote: A 30% reduction in the final output file size sounds nice. Personally, I find the prospect of

Re: Replace `-dgs-load-fonts' to `--bigpdfs' in lilypond-book (issue 300280043 by truer...@gmail.com)

On 7/22/16 9:35 AM, "lilypond-devel on behalf of David Kastrup" wrote: > >A 30% reduction in the final output file size sounds nice. Personally, >I find the prospect of not having 4GB of disk usage for running

Re: Replace `-dgs-load-fonts' to `--bigpdfs' in lilypond-book (issue 300280043 by truer...@gmail.com)

>> Comparing the `--bigpdfs' method with the fontless PDF approach as >> outlined above, the latter creates a final output file about 30% >> smaller (at least in my small test). > > A 30% reduction in the final output file size sounds nice. This is an *additional* 30%, since `--bigpdfs' already

Re: Replace `-dgs-load-fonts' to `--bigpdfs' in lilypond-book (issue 300280043 by truer...@gmail.com)

Werner LEMBERG writes: > About a month ago we discussed how to reduce the disk space necessary > for builing the lilypond documentation. > >> [...] Since lilypond itself converts all fonts to PostScript >> resources, why not writing those resources to a `fontresource' >> directory

Re: Replace `-dgs-load-fonts' to `--bigpdfs' in lilypond-book (issue 300280043 by truer...@gmail.com)

> ps2pdf -I \ > -dNOSAFER -P \ > Fontless.pdf WithEmbeddedFonts.pdf This should rather be ps2pdf -I \ -dNOSAFER \ Fontless.pdf WithEmbeddedFonts.pdf I've tested with the fonts in the current directory, thus `-P'. Werner

Re: Replace `-dgs-load-fonts' to `--bigpdfs' in lilypond-book (issue 300280043 by truer...@gmail.com)

About a month ago we discussed how to reduce the disk space necessary for builing the lilypond documentation. > [...] Since lilypond itself converts all fonts to PostScript > resources, why not writing those resources to a `fontresource' > directory instead of embedding? We could add a

Re: Replace `-dgs-load-fonts' to `--bigpdfs' in lilypond-book (issue 300280043 by truer...@gmail.com)

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.

Re: Replace `-dgs-load-fonts' to `--bigpdfs' in lilypond-book (issue 300280043 by truer...@gmail.com)

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.

Re: Replace `-dgs-load-fonts' to `--bigpdfs' in lilypond-book (issue 300280043 by truer...@gmail.com)

>> Remove `-dgs-load-fonts` from lilypond-book default. During >> LilyPond and its documents are built, `-dgs-load-lily-fonts` option >> instead of `-dgs-load-fonts` is used. `-dgs-load-lily-fonts` means >> "Load only the LilyPond fonts via Ghostscript." >> >> "LilyPond fonts" mean the fonts in

Re: Replace `-dgs-load-fonts' to `--bigpdfs' in lilypond-book (issue 300280043 by truer...@gmail.com)

On 2016/06/13 14:00:57, trueroad wrote: I came up with another idea. Remove `-dgs-load-fonts` from lilypond-book default. During LilyPond and its documents are built, `-dgs-load-lily-fonts` option instead of `-dgs-load-fonts` is used. `-dgs-load-lily-fonts` means "Load only the LilyPond

Re: Replace `-dgs-load-fonts' to `--bigpdfs' in lilypond-book (issue 300280043 by truer...@gmail.com)

I came up with another idea. Remove `-dgs-load-fonts` from lilypond-book default. During LilyPond and its documents are built, `-dgs-load-lily-fonts` option instead of `-dgs-load-fonts` is used. `-dgs-load-lily-fonts` means "Load only the LilyPond fonts via Ghostscript." "LilyPond fonts" mean

Re: Replace `-dgs-load-fonts' to `--bigpdfs' in lilypond-book (issue 300280043 by truer...@gmail.com)

On 2016/06/11 08:56:19, dak wrote: On 2016/06/11 08:40:12, trueroad wrote: > Remove `-dgs-load-fonts' in lilypond-book The problem I have with that behavior is the ridiculous amount of disk space it consumes. I believe we use this for building the LilyPond docs already, and I need about

Re: Replace `-dgs-load-fonts' to `--bigpdfs' in lilypond-book (issue 300280043 by truer...@gmail.com)

On 2016/06/11 08:40:12, trueroad wrote: Remove `-dgs-load-fonts' in lilypond-book The problem I have with that behavior is the ridiculous amount of disk space it consumes. I believe we use this for building the LilyPond docs already, and I need about 4GB of free disk space to run a build with

Re: Replace `-dgs-load-fonts' to `--bigpdfs' in lilypond-book (issue 300280043 by truer...@gmail.com)

LGTM – please update the title of this Rietveld issue https://codereview.appspot.com/300280043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel