Issue 620: It should be possible to specify more specific spanner bounds.
http://code.google.com/p/lilypond/issues/detail?id=620
New issue report by joeneeman:
There are several situations where spanners are bounded by paper columns.
It would be nice to be able to specify attachment points more p
Issue 591: Left edge of hairpin aligns with arpeggio
http://code.google.com/p/lilypond/issues/detail?id=591
Comment #5 by joeneeman:
It seems that lilypond implicitly creates two voices in that situation.
I agree that
the current behaviour causes problems; it would be nice to have a
general way
2008/5/13 Neil Puttock <[EMAIL PROTECTED]>:
> 2008/5/12 Matthew <[EMAIL PROTECTED]>:
>
> > oops... Pressed the wrong button. I meant to add:
> >
> > I'm pretty sure that this reproduces the previous behaviour for RIGHT
> edges, and
> > adds the same capabilities for LEFT. Redundant computat
> I'm not top posting.
\version "2.11.45"
\paper { ragged-right = ##t }
\score {
\new GrandStaff <<
\new Staff \relative c' { c1 | c8\fff c2.. }
\new Staff { R1 | R1 }
>>
}
In this snippet, the tail of the first f in the fff goes over the bar line t
Issue 461: enharmonic ties
http://code.google.com/p/lilypond/issues/detail?id=461
Comment #6 by paconet.org:
In the last example: where is the difference, apart from the A sharp?
In the bass, it
is difficult to say what exact notes are they, for there are no visible
clef or key
signature.
-
Issue 461: enharmonic ties
http://code.google.com/p/lilypond/issues/detail?id=461
Comment #5 by n.puttock:
Here's another example, from Fauré's gorgeous G flat Barcarolle (spot the
difference).
Attachments:
faure.PNG 45.4 KB
--
You received this message because you are listed in the
Issue 591: Left edge of hairpin aligns with arpeggio
http://code.google.com/p/lilypond/issues/detail?id=591
Comment #4 by n.puttock:
Oops, you're right, I'd forgotten about the parallel usage; I'd misread
a post that
Mats made concerning dynamics in a separate voice.
Saying that though, it's n
2008/5/12 Matthew <[EMAIL PROTECTED]>:
> oops... Pressed the wrong button. I meant to add:
>
> I'm pretty sure that this reproduces the previous behaviour for RIGHT edges,
> and
> adds the same capabilities for LEFT. Redundant computation is carried out for
> LEFT if it's == 0, but I figured
It seems to me that this probably is another incarnation of the bug
discussed in the
thread
http://lists.gnu.org/archive/html/lilypond-devel/2007-04/msg00136.html,
which as far as I can see is missing in the bug tracker.
There are also close connections to
http://code.google.com/p/lilypond/iss
