thanks, Werner, for this report!
I've added tracker issue
https://code.google.com/p/lilypond/issues/detail?id=3341thanks=3341ts=1367393280
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/formatting-bug-tp145284p145294.html
Sent from the Dev mailing list archive
Probably quite obvious: we have a number of spacing regressions causing
trouble right now. Particularly worryisome are the page layout
regressions: where is the point in tighter spacing if we fit less
rather than more material on the same page? Yes, I know there is some
point to it, but it is
At any rate, the way it is going I find by far our most important
task for 2.18 is getting the page breaking back into reliability.
More important than all microspacing problems which at least only
have local effects.
+1. I suspect minor oversights in the code which have global
effects...
https://codereview.appspot.com/9036044/diff/1/scm/define-context-properties.scm
File scm/define-context-properties.scm (right):
https://codereview.appspot.com/9036044/diff/1/scm/define-context-properties.scm#newcode143
scm/define-context-properties.scm:143: bars (which get bar numbers in
https://codereview.appspot.com/9073043/diff/1/scm/output-lib.scm
File scm/output-lib.scm (right):
https://codereview.appspot.com/9073043/diff/1/scm/output-lib.scm#newcode861
scm/output-lib.scm:861: (ly:grob-property grob 'outside-staff-padding
0.0))
It would be interesting to know why 1.0 was
Reviewers: lemzwerg,
https://codereview.appspot.com/9073043/diff/1/scm/output-lib.scm
File scm/output-lib.scm (right):
https://codereview.appspot.com/9073043/diff/1/scm/output-lib.scm#newcode861
scm/output-lib.scm:861: (ly:grob-property grob 'outside-staff-padding
0.0))
On 2013/05/01 09:32:51,
