Issue 304 in project lilypond

Issue 304: phrasing slurs and graces http://code.google.com/p/lilypond/issues/detail?id=304 New issue report by lemzwerg: \version quot;2.11.18quot; \header { texidoc = quot; Start and end points of phrasing slurs must not collide with start and end points of normal slurs. Below is a

Issue 304 in project lilypond

Issue 304: phrasing slurs and graces http://code.google.com/p/lilypond/issues/detail?id=304 Comment #1 by lemzwerg: The ugly shape looks the same problem as reported in #163, but the collision isn't, I think -- You received this message because you are listed in the owner or CC fields of this

[meta] how to fix wrong status in bug database

Hi, if a bug has been too hastily marked as a duplicate in the bug database, how does it get its status changed? Do I re-report the bug? Nag someone in private email? Give up on that bug? Give up on bug reporting altogether? I'd suggest commenting on the status change here, but someone

Re: [meta] how to fix wrong status in bug database

Arvid Grøtting wrote: if a bug has been too hastily marked as a duplicate in the bug database, how does it get its status changed? Han-Wen or I change it when we re-evaluate the bugs. Do I re-report the bug? Nag someone in private email? Give up on that bug? Give up on bug reporting

Issue 292 in project lilypond

Issue 292: ugly lyrics with ragged-bottom = ##f http://code.google.com/p/lilypond/issues/detail?id=292 Comment #1 by joeneeman: (No comment was entered for this change.) Issue attribute updates: Status: Fixed Labels: fixed_2_11_20 -- You received this message because you are

Re: Chordmode breaks in 2.10 and 2.11

I looked at the .ps file that Brett sent me, and couldn't notice anything strange there. The problems seems somehow to be related to the Verdana TrueType font that's used for the chord names, but I don't understand why your Ghostscript (which should be the one included in the LilyPond

Issue 289 in project lilypond

Issue 289: grace note cancels \voiceOne http://code.google.com/p/lilypond/issues/detail?id=289 Comment #4 by arvidgr: I just tested with all versions between 2.11.5 and 2.11.16, and this bug was introduced in 2.11.16. -- You received this message because you are listed in the owner or CC

Issue 289 in project lilypond

Issue 289: grace note cancels \voiceOne http://code.google.com/p/lilypond/issues/detail?id=289 Comment #5 by hanwenn: Fixed in GIT. The puzzling thing isn't that is not working, but rather that it used to work ; that's also why I marked it duplicate. Issue attribute updates: Labels:

Issue 289 in project lilypond

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

Issue 74 in project lilypond

Issue 74: grace note interferes with lt;lt; \\ gt;gt; format http://code.google.com/p/lilypond/issues/detail?id=74 Comment #1 by hanwenn: slightly more musical example: \layout {ragged-right=##t} \new Staff \relative c'' lt;lt; f4 \\ { \grace b,16 %% \voiceTwo c4}

Issue 305 in project lilypond

Issue 305: positioning of hairpins and dynamics http://code.google.com/p/lilypond/issues/detail?id=305 New issue report by lemzwerg: \version quot;2.11.19quot; \header { texidoc = quot; It must be possible to position hairpins and dynamics independently. Here is a counterexample. quot; }

Issue 293 in project lilypond

Issue 293: warning: Can't fit systems on page -- ignoring between-system-padding http://code.google.com/p/lilypond/issues/detail?id=293 Comment #1 by joeneeman: In 2.11.20 you will still get the warning, but it will break pages and there won't be overprint. Issue attribute updates:

Issue 293 in project lilypond

Issue 293: warning: Can't fit systems on page -- ignoring between-system-padding http://code.google.com/p/lilypond/issues/detail?id=293 Comment #2 by joeneeman: (No comment was entered for this change.) Issue attribute updates: Owner: joeneeman Labels: Type-Defect -- You

Issue 279 in project lilypond

Issue 279: x-staff tuplets cause havoc http://code.google.com/p/lilypond/issues/detail?id=279 Comment #8 by joeneeman: Ah, OK. The minimal example works for me, but the original one doesn't. I'll get back to work on this. Issue attribute updates: Status: started Labels: