Re: Lyrics break estimation of vertical spacing

2010-03-23 Thread Joe Neeman
On Tue, 2010-03-23 at 22:51 -0400, Boris Shingarov wrote: > > The estimated height for the whole system _should_ take into account the > > fact that the lyrics can be squeezed between the systems. Have a look at > > the comment in align-interface.cc:104 (which should get called as a > > resul

Re: Lyrics break estimation of vertical spacing

2010-03-23 Thread Joe Neeman
On Tue, 2010-03-23 at 19:57 -0400, Boris Shingarov wrote: > > The estimated height for the whole system _should_ take into account the > > fact that the lyrics can be squeezed between the systems. Have a look at > > the comment in align-interface.cc:104 (which should get called as a > > result o

Re: Lyrics break estimation of vertical spacing

2010-03-23 Thread Boris Shingarov
The estimated height for the whole system _should_ take into account the > fact that the lyrics can be squeezed between the systems. Have a look at > the comment in align-interface.cc:104 (which should get called as a > result of sys->pure_height()). The begin_of_line_extent should be zero >

Re: Lyrics break estimation of vertical spacing

2010-03-23 Thread Boris Shingarov
> The estimated height for the whole system _should_ take into account the > fact that the lyrics can be squeezed between the systems. Have a look at > the comment in align-interface.cc:104 (which should get called as a > result of sys->pure_height())   Trying to make head or tail of which chi

Re: Issue 1044 in lilypond: strip-whitespace in lily-git

2010-03-23 Thread lilypond
Comment #3 on issue 1044 by percival.music.ca: strip-whitespace in lily-git http://code.google.com/p/lilypond/issues/detail?id=1044 Doesn't work. The rebase just says "current master is up to date". (yes, I also tried HEAD^ , but I used HEAD~1 below since that's what most of the web git hel

Re: Issue 1027 in lilypond: Lyrics ignore minimum-Y-extent

2010-03-23 Thread lilypond
Updates: Labels: -Type-Defect Type-Documentation Comment #1 on issue 1027 by percival.music.ca: Lyrics ignore minimum-Y-extent http://code.google.com/p/lilypond/issues/detail?id=1027 Neil: This is a documentation issue, since minimum-Y-extent is no longer used with VerticalAxisGroup

Re: Issue 995 in lilypond: tuplets at the begin of a piece cannot begin with a \tempo indication

2010-03-23 Thread lilypond
Comment #4 on issue 995 by percival.music.ca: tuplets at the begin of a piece cannot begin with a \tempo indication http://code.google.com/p/lilypond/issues/detail?id=995 Valentin: you should have tested it like this: c'1 \times 2/3 { \tempo 2=52 %messes up the tuplet c'2 c' c'

Hidden note erases dotted note from chord in the first voice

2010-03-23 Thread Anthony
> I'm not top posting. Nope. Not me. I wouldn't expect a hidden note to be able to erase the dot from a dotted note from a different voice but that is what currently happens. Again, there is an alternate way to get the notes tied together using \stemUp and ignoring clashing stems but I usually

Re: 2.13.16 crashes while processing old good file (2.8.8 and 2.12.3 do not)

2010-03-23 Thread Dmytro O. Redchuk
У вт, 2010-03-23 у 08:25 -0600, Carl Sorensen пише: > The clue here is that there is some kind of break in the middle of the score > that you've put in manually that confuses the layout engine. My fault! > Just remove the /pageBreak in the middle of your score and it works > perfectly. Yes, almost

Re: 2.13.16 crashes while processing old good file (2.8.8 and 2.12.3 do not)

2010-03-23 Thread Reinhold Kainhofer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Dienstag, 23. März 2010 15:25:55 schrieb Carl Sorensen: > On 3/23/10 2:26 AM, "Dmytro O. Redchuk" wrote: > > Btw, uncommenting page-count and commenting out > > system-count gives strange result: lilypond says "Solving 2 > > page-breaking chunks...

Re: 2.13.16 crashes while processing old good file (2.8.8 and 2.12.3 do not)

2010-03-23 Thread Carl Sorensen
On 3/23/10 2:26 AM, "Dmytro O. Redchuk" wrote: > Hi. > > My problem (again, yes, my own,) now is that 2.13.16 crashes on a > file, which can happily be compiled with 2.12.3 and 2.8.8 (2.13.0 > segfaults, did not try others yet). > > Having no idea how to debug, i would like to ask what can

2.13.16 crashes while processing old good file (2.8.8 and 2.12.3 do not)

2010-03-23 Thread Dmytro O. Redchuk
Hi. My problem (again, yes, my own,) now is that 2.13.16 crashes on a file, which can happily be compiled with 2.12.3 and 2.8.8 (2.13.0 segfaults, did not try others yet). Having no idea how to debug, i would like to ask what can i do to narrow down this problem. (Stripping the code to thr