Re: make doc still fails - problem with lilypond-book - was: Still cannot make doc

2016-06-04 15:12 GMT+02:00 Masamichi Hosoda : >> In addition, the following command sequence succeeds: >> >> lilypond-book aaa-lilybook-test.lytex >> latex aaa-lilybook-test.tex >> dvips aaa-lilybook-test.dvi >> ps2pdf aaa-lilybook-test.ps >> evince aaa-lilybook-test.pdf >>

Re: Issue 3945: fix (De)crescendo with unspecified starting volume in MIDI (issue 294700043 by nine.fierce.ball...@gmail.com)

https://codereview.appspot.com/294700043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Add ly:get-font-format to get the font format (issue 296350043 by truer...@gmail.com)

My main purpose was the distinction between the TTC and OTC. So this patch cannot distinguish between the PFA and PFB. OK, but IMHO we should get rid of being dependent on the file name suffix. I'm trying the following `font-file-as-ps-string' with this Patch Set 2. Hmm, this looks like the

Re: Add ly:get-font-format to get the font format (issue 296350043 by truer...@gmail.com)

LGTM, but note that FreeType's `FT_Get_Font_Format` doesn't really return the font format but the name of the module used to handle a font. In particular, it doesn't make a difference between PFA and PFB. My main purpose was the distinction between the TTC and OTC. So this patch cannot

Re: make doc still fails - problem with lilypond-book - was: Still cannot make doc

> In addition, the following command sequence succeeds: > > lilypond-book aaa-lilybook-test.lytex > latex aaa-lilybook-test.tex > dvips aaa-lilybook-test.dvi > ps2pdf aaa-lilybook-test.ps > evince aaa-lilybook-test.pdf > > aaa-lilybook-test.ps is >16MB again, though. Thank you for your results.