Font size setting explanation is a bit misleading in documentation

In the text formatting documentation at http://lilypond.org/doc/v2.15/Documentation/notation/formatting-text, when talking about the size of characters, the phrasing at one point is: "the font size can be set to an absolute value with \fontsize". Maybe this should be changed to something like "

Re: Issue 2432 in lilypond: Patch: Change all occurences of "echo -n" to "printf" for portability

Updates: Labels: Patch-review Comment #3 on issue 2432 by d...@gnu.org: Patch: Change all occurences of "echo -n" to "printf" for portability http://code.google.com/p/lilypond/issues/detail?id=2432#c3 Patchy the autobot says: LGTM. See Rietveld review for whitespace problem to be f

Re: Issue 2426 in lilypond: test-baseline does not include fonts

Updates: Labels: Patch-review Comment #2 on issue 2426 by d...@gnu.org: test-baseline does not include fonts http://code.google.com/p/lilypond/issues/detail?id=2426#c2 Patchy the autobot says: LGTM. ___ bug-lilypond mailing list bug-lilypo

Re: Issue 2433 in lilypond: Patch: score.cc: minor cleanups

Updates: Labels: Patch-review Comment #1 on issue 2433 by d...@gnu.org: Patch: score.cc: minor cleanups http://code.google.com/p/lilypond/issues/detail?id=2433#c1 Patchy the autobot says: LGTM. ___ bug-lilypond mailing list bug-lilypond@gnu.o

Re: Issue 2427 in lilypond: Patch: Add an example implementation of cross-staff stems

Comment #6 on issue 2427 by philehol...@gmail.com: Patch: Add an example implementation of cross-staff stems http://code.google.com/p/lilypond/issues/detail?id=2427 We are working on upgrading the LSR, but the maintainer has been out of action for a while and has only just been able to get

Re: Issue 2408 in lilypond: Inconsistent automatic beaming when using multiple tuplets next to each other

Updates: Status: Fixed Labels: -Patch-review fixed_2_15_35 Comment #9 on issue 2408 by carl.d.s...@gmail.com: Inconsistent automatic beaming when using multiple tuplets next to each other http://code.google.com/p/lilypond/issues/detail?id=2408 Pushed to staging as 1a4767cac76e

Re: Issue 2432 in lilypond: Patch: Change all occurences of "echo -n" to "printf" for portability

Updates: Labels: Patch-new Comment #2 on issue 2432 by carl.d.s...@gmail.com: Patch: Change all occurences of "echo -n" to "printf" for portability http://code.google.com/p/lilypond/issues/detail?id=2432#c2 Change all occurences of "echo -n" to "printf" for portability http://coderev

Re: \bookOutputName not working if a \paper block uses a previously defined variable

-Eluze writes: > this code does not produce the expected output file paper-test.pdf: > > aFivePaper = \paper { paperheight = 21.0 \cm } > \book { > \bookOutputName "paper-test" > \relative {c d e f} > \paper {\aFivePaper} > } \bookOutputName sets the output name in the paper block, so with

\bookOutputName not working if a \paper block uses a previously defined variable

this code does not produce the expected output file paper-test.pdf: aFivePaper = \paper { paperheight = 21.0 \cm } \book { \bookOutputName "paper-test" \relative {c d e f} \paper {\aFivePaper} } thanks Eluze -- View this message in context: http://old.nabble.com/%5CbookOutputName-not-wor

Issue 2433 in lilypond: Patch: score.cc: minor cleanups

Status: New Owner: Labels: Type-Enhancement Patch-new New issue 2433 by d...@gnu.org: Patch: score.cc: minor cleanups http://code.google.com/p/lilypond/issues/detail?id=2433 score.cc: minor cleanups http://codereview.appspot.com/5909044 ___ bug

Re: Issue 2426 in lilypond: test-baseline does not include fonts

Updates: Labels: Patch-new Comment #1 on issue 2426 by d...@gnu.org: test-baseline does not include fonts http://code.google.com/p/lilypond/issues/detail?id=2426#c1 Issue 2426: override hardwired fonts in test-baseline This is not the same as embedding the fonts used at baseline crea