Issue 179 in project lilypond

Issue 179: broken text spanners don't end at same horizontal position http://code.google.com/p/lilypond/issues/detail?id=179 Comment #10 by lemzwerg: It's fixed. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You

Re: font-config problem

James E. Bailey wrote: Thank you, this worked. So, do I have to delete the .fontconfig file everytime I use a new version? I mean, is this going to be a regular part of the update process? 'cause the average macintosh user doesn't know how to find hidden files. I've been updating my versions

Re: font-config problem

Thank you, this worked. So, do I have to delete the .fontconfig file everytime I use a new version? I mean, is this going to be a regular part of the update process? 'cause the average macintosh user doesn't know how to find hidden files. Am 26.02.2007 um 15:42 schrieb Graham Percival: Ja

Re: Aligned-above lyrics stick to wrong staff when stretching

On Tuesday 27 February 2007 14:52, Graham Percival wrote: > Joe Neeman wrote: > > On Tuesday 27 February 2007 08:45, Arvid Grøtting wrote: > >> Joe Neeman gmail.com> writes: > >>> This is easy to workaround, but I don't know how to make lilypond > >>> detect it by itself. [...] > >> > >> Ah, OK.

segfault 2.11.20

I can't narrow this one down too much, it's really weird. For example when I remove the two commented out lines the segfault goes away. -Jay (I'm on Fedora Core 6) = \version "2.11.20" \score { \new PianoStaff << \new Staff="RH" \relative c' { c4 d e f | } \new Dyna

Issue 310 in project lilypond

Issue 310: systems are spaced unevenly http://code.google.com/p/lilypond/issues/detail?id=310 Comment #2 by joeneeman: The gaps between the systems are not exactly the same in 2.11.20, but if you try it with 2.11.16 through 2.11.19, you will see a big difference in how uneven they are. -- Y

Issue 312 in project lilypond

Issue 312: minimum-Y-extent is ignored in vertical spacing http://code.google.com/p/lilypond/issues/detail?id=312 Comment #2 by joeneeman: The point is that there should be large spaces between the systems -- 20 units above the top staff and twenty units below the bottom one. I've attached the o

Re: \ictus spacing in Gregorian chant contexts

Thanks, http://code.google.com/p/lilypond/issues/detail?id=316 Tim Fitzgerald wrote: I'm not top posting. % The \ictus has incorrect horizontal spacing, it should be centered under (or over, in some cases) the nuem. It is too far to the left. % Regards Tim. See code below. \version "2.10.

Issue 316 in project lilypond

Issue 316: ancient \ictus not centered http://code.google.com/p/lilypond/issues/detail?id=316 New issue report by gpermus: % The \ictus has incorrect horizontal spacing, it should be centered under % (or % over, in some cases) the nuem. It is too far to the left. % Regards Tim. See code below.

Re: Vaticana porrectus sometimes solid

Thanks, http://code.google.com/p/lilypond/issues/detail?id=315 Tim Fitzgerald wrote: I'm not top posting. %% Last note of porrectus (large E in section 7.7.10.2 of the manual), when only one space higher on staff than the previous note, appears like a solid blob. There should be a little whi

Issue 315 in project lilypond

Issue 315: ancient porrectus should look like punctum http://code.google.com/p/lilypond/issues/detail?id=315 New issue report by gpermus: %% Last note of porrectus (large E in section 7.7.10.2 of the manual), when only %one space higher on staff than the previous note, appears like a solid blob.

Re: Vaticana Climacus spacing

Thanks, added as http://code.google.com/p/lilypond/issues/detail?id=314 It might be a while before this is fixed; the maintainer of the ancient music code is currently very busy. Cheers, - Graham Tim Fitzgerald wrote: I'm not top posting. %% the \inclinatum used in the Climacus does not h

Issue 314 in project lilypond

Issue 314: incorrect ancient \inclinatum spacing http://code.google.com/p/lilypond/issues/detail?id=314 New issue report by gpermus: %% the \inclinatum used in the Climacus does not have correct spacing or % appearance. The top right, and bottom left edge of each diamond shaped % nuem should be c

Issue 212 in project lilypond

Issue 212: Context-initial afterGrace generates programming error http://code.google.com/p/lilypond/issues/detail?id=212 Comment #2 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the

Issue 79 in project lilypond

Issue 79: text spanner dashes too low after \break http://code.google.com/p/lilypond/issues/detail?id=79 Comment #2 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fie

Issue 284 in project lilypond

Issue 284: Segmentation fault -- tried to space systems on a bad number of pages http://code.google.com/p/lilypond/issues/detail?id=284 Comment #2 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you ar

Issue 282 in project lilypond

Issue 282: tuplet bracket printed over the wrong staff http://code.google.com/p/lilypond/issues/detail?id=282 Comment #2 by gpermus: Joe, this was marked as a duplicate of 279 (x-staff tuplets cause havoc) but this bug still has a messed-up slur. Issue attribute updates: Status: Started

Issue 252 in project lilypond

Issue 252: collision beam notehead in polyphony http://code.google.com/p/lilypond/issues/detail?id=252 Comment #3 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC field

Issue 179 in project lilypond

Issue 179: broken text spanners don't end at same horizontal position http://code.google.com/p/lilypond/issues/detail?id=179 Comment #9 by gpermus: I think this was fixed in .14, but I'm not certain, so I won't add that tag. Issue attribute updates: Status: Verified -- You received thi

Re: Aligned-above lyrics stick to wrong staff when stretching

Joe Neeman wrote: On Tuesday 27 February 2007 08:45, Arvid Grøtting wrote: Joe Neeman gmail.com> writes: This is easy to workaround, but I don't know how to make lilypond detect it by itself. [...] Ah, OK. I'll update my templates. Consider the bug report retracted. ;-) No, it's still a

Re: point and click and with-url behavior

Thanks; this has been fixed in 2.11.20. Cheers, - Graham Mats Bengtsson wrote: You are right that this is a bug/limitation. I forward your email to bug-lilypond to turn it into a bug report. The simple reason for the current behaviour is that the same postscript function is used to handle po

Re: markup font bug

Dan Eble wrote: Thanks for the reply, but because the example is intentionally simple, the simple workaround is unsatisfying. Imagine this fragment as part of bookTitleMarkup in an include file: Why not define myFlat = \markup{ \normal-text { \flat } } and then do \header = { instrument =

Issue 135 in project lilypond

Issue 135: markup on spacer rests doesn't obey \emptyText http://code.google.com/p/lilypond/issues/detail?id=135 Comment #6 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner o

Issue 306 in project lilypond

Issue 306: \with-url only works if p&c enabled. http://code.google.com/p/lilypond/issues/detail?id=306 Comment #1 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC field

Issue 289 in project lilypond

Issue 289: grace note cancels \voiceOne http://code.google.com/p/lilypond/issues/detail?id=289 Comment #7 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of thi

Issue 312 in project lilypond

Issue 312: minimum-Y-extent is ignored in vertical spacing http://code.google.com/p/lilypond/issues/detail?id=312 Comment #1 by gpermus: I can't see any difference between the two spaces -- should I? It doesnt look like this bug is fixed. Issue attribute updates: Status: Started -- Y

Issue 311 in project lilypond

Issue 311: systems are stretched off the bottom of the page http://code.google.com/p/lilypond/issues/detail?id=311 Comment #1 by gpermus: There's still a warning: warning: Can't fit systems on page -- ignoring between-system-padding but the bug is fixed. Issue attribute updates: Statu

Issue 310 in project lilypond

Issue 310: systems are spaced unevenly http://code.google.com/p/lilypond/issues/detail?id=310 Comment #1 by gpermus: I don't see this fixed in 2.11.20 on OSX. Am I supposed to set a special \paper{} variable to enable the even spacing? (I'm not certain that we _do_ want even spacing by default

Issue 309 in project lilypond

Issue 309: single note cluster doesn't crash. http://code.google.com/p/lilypond/issues/detail?id=309 Comment #1 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields

Issue 303 in project lilypond

Issue 303: Beam #'breakable = ##t does not draw with \remove Bar_engraver http://code.google.com/p/lilypond/issues/detail?id=303 Comment #3 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are liste

Issue 285 in project lilypond

Issue 285: tremolo whole notes http://code.google.com/p/lilypond/issues/detail?id=285 Comment #2 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of this issue,

Issue 279 in project lilypond

Issue 279: x-staff tuplets cause havoc http://code.google.com/p/lilypond/issues/detail?id=279 Comment #10 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of thi

Re: markup font bug

Dan Eble wrote: % Note the missing flat in the markup. % Should \flat use the flat sign from Lilypond's font, % or is this something I'm not supposed to want to do? I'd call it a missing warning. Try this: bf1^\markup{ \override #'(font-name . "Courier") { Ceci n'est pas une B

Issue 313 in project lilypond

Issue 313: missing warning for \markup{ \override #'(font-name . "Other") \flat } http://code.google.com/p/lilypond/issues/detail?id=313 New issue report by gpermus: There is no \flat in the "Courier" font type, so there is no flat displayed. It would be nice if lilypond displayed an error messa

Re: font-config problem

James E. Bailey wrote: Odd, 2.10.15-1-2.10.17-1 don’t error, but it also don't output a file. The file goes as far as pre-processing graphical objects and then nothing. And to be clear, I’m using the file that opens with the program as my test file. I don't know if this matters, but the most re

Re: Lilypond Mac OSX Intel error

Phaedon Sinis wrote: I downloaded the latest Lilypond version 2.11.19-2 for the Intel Mac OSX, and when I tried to unzip the file, I got the following error: "Archive Utility: Unable to unarchive "lilypond-2.11.19-2.darwin-x86.tar.bz2" into "Desktop". (Error 2 - No such file or directory.)" Tr

Re: Aligned-above lyrics stick to wrong staff when stretching

Joe Neeman gmail.com> writes: > No, it's still a bug. The fact that there's a workaround just means that we > can give it a lower priority. OK, as long as it stays manually overridable. In some (eh, make that "many") songs, all (or the middle) voices sing the same lyrics, and in that case I'll

Re: Aligned-above lyrics stick to wrong staff when stretching

On Tuesday 27 February 2007 08:45, Arvid Grøtting wrote: > Joe Neeman gmail.com> writes: > > This is easy to workaround, but I don't know how to make lilypond detect > > it by itself. [...] > > Ah, OK. I'll update my templates. Consider the bug report retracted. ;-) No, it's still a bug. The

Re: Aligned-above lyrics stick to wrong staff when stretching

Joe Neeman gmail.com> writes: > This is easy to workaround, but I don't know how to make lilypond detect it > by > itself. [...] Ah, OK. I'll update my templates. Consider the bug report retracted. ;-) I might even clean up my TTBB template once I get this in and post it somewhere. Cheer

Re: Documentation: ABC link has changed

Le samedi 24 février 2007 à 14:22 +0100, Hans Aberg a écrit : > The link given for ABC in lilypond.pdf, version 2.11.19, 15.4, p. 319 > is dead. Some alternatives: >http://www.walshaw.plus.com/abc/ >http://abcnotation.org.uk/ >http://en.wikipedia.org/wiki/ABC_%28musical_notation%29 >

Re: Aligned-above lyrics stick to wrong staff when stretching

On Monday 26 February 2007 20:32, Arvid Grøtting wrote: > >:-) > > Hi, > > let me first say that 2.11.20 does seem to resolve most of the bugs in the > new vertical spacing engine. Right now I only have one small nit to pick: > Lyrics contexts aligned above a given staff should stay close to that

Aligned-above lyrics stick to wrong staff when stretching

>:-) Hi, let me first say that 2.11.20 does seem to resolve most of the bugs in the new vertical spacing engine. Right now I only have one small nit to pick: Lyrics contexts aligned above a given staff should stay close to that staff when stretching. That is, in the case below, you should have: