Issue 211: cluster pieces don't join
http://code.google.com/p/lilypond/issues/detail?id=211
New issue report by hanwenn:
input/regression/cluster-style.ly
Issue attributes:
Status: Fixed
Owner: hanwenn
Labels: Type-Defect Priority-Medium fixed_2_10_8 fixed_2_11_8
--
Issue 210: clusters don't break correctly
http://code.google.com/p/lilypond/issues/detail?id=210
New issue report by hanwenn:
input/regression/cluster-break.ly
Issue attributes:
Status: Fixed
Owner: hanwenn
Labels: Type-Defect Priority-Medium fixed_2_10_8 fixed_2_11_8
Issue 93: lyric extender going too far
http://code.google.com/p/lilypond/issues/detail?id=93
Comment #4 by hanwenn:
oops, didn't make it into the .7 build.
Issue attribute updates:
Labels: -fixed_2_10_7 -fixed_2_11_7 fixed_2_10_8 fixed_2_11_8
--
You received this message because you ar
>> (Please disregard this line. No, Gmane; I'm not top-posting.)
\version "2.11.5"
\paper {
ragged-last-bottom = ##f
texidoc = "
Two-pass page layout sometimes stretches too much.
When run without a tweak file, three pages of 3 + 3 + 2 systems are created.
After two-pass space tweaking, I g
Issue 202: merge-differntly-headed only works for the first two voices in
3-voice contexts
http://code.google.com/p/lilypond/issues/detail?id=202
Comment #3 by Carl.D.Sorensen:
Here is an example of a single-staff guitar piece that has four voices in one
staff.
Merges are apparent between voice
Graham Percival wrote:
Thanks for the suggestion! I've added three index entries for these
terms, although not to 2.18 -- we do not put index entries pointing to
the tutorial.
Why not? Sometimes, the best description is in the Tutorial.
I don't remember if we have some index terms that po
Issue 93: lyric extender going too far
http://code.google.com/p/lilypond/issues/detail?id=93
Comment #3 by hanwenn:
(No comment was entered for this change.)
Issue attribute updates:
Status: Fixed
Labels: fixed_2_10_7 fixed_2_11_7
--
You received this message because you are li
Issue 31: modern-cautionary incorrectly marks some accidentals as cautionary
http://code.google.com/p/lilypond/issues/detail?id=31
Comment #1 by hanwenn:
Seems ok in 2.11.6 / 7
Issue attribute updates:
Status: Fixed
--
You received this message because you are listed in the owner
or
Issue 192: clef change in second staff stops tie in first staff
http://code.google.com/p/lilypond/issues/detail?id=192
Comment #1 by hanwenn:
(No comment was entered for this change.)
Issue attribute updates:
Status: Fixed
Labels: fixed_2_10_7 fixed_2_11_7
--
You received this
Issue 58: polyphonic Rest #'position should only be set if other voice is
printing
http://code.google.com/p/lilypond/issues/detail?id=58
Comment #6 by hanwenn:
note that there is no coordination going on between the 2 types of
collision resolution. Strange results are still likely to happen
in
Issue 58: polyphonic Rest #'position should only be set if other voice is
printing
http://code.google.com/p/lilypond/issues/detail?id=58
Comment #5 by hanwenn:
(No comment was entered for this change.)
Issue attribute updates:
Status: Fixed
Labels: fixed_2_10_7 fixed_2_11_7
-
Issue 190: Unexpected beam slanting in the opposite direction
http://code.google.com/p/lilypond/issues/detail?id=190
Comment #1 by hanwenn:
Unfortutaly, can't reproduce.
It's helpful for this to provide a png with
debug-beam-scoring = ##t
in the \layout{} block, and to use
\override Beam
Paul Scott wrote:
Han-Wen Nienhuys wrote:
The mm rest text has to be centered between barlines, making it a
spanner.
If you are talking about the number (of bars rest) this makes sense.
If it's a tempo indication (Allegro vivace) it doesn't. Why would the
results of the \markup comm
Issue 104: emptyText doesn't work with lyricmode
http://code.google.com/p/lilypond/issues/detail?id=104
Comment #2 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
Issue 104: emptyText doesn't work with lyricmode
http://code.google.com/p/lilypond/issues/detail?id=104
Comment #1 by hanwenn:
Invalid bugreport, strictly speaking.
Lyrics does not attach to a voice, so it is centered on the (rather wide,
due to "Immer ... ") PaperColumn. Use \lyricsto.
Added
>I am top posting -- oops
I've done further work, and as written this is not a bug. Voices 3 and
4 have a shift, which keeps the notes from colliding with those from
Voices 1 and 2. Therefore, the notes don't collide and they aren't
merged.
However, when I remove the shift, the heads of the mer
Issue 125: progerror \bendAfter collision
http://code.google.com/p/lilypond/issues/detail?id=125
Comment #3 by hanwenn:
Please make a new issue for the progerror if it gets reported again.
In general trying to attach spanners to skip notes (as happens here)
is weird so, it may trigger various s
Issue 32: use skyline spacing for rods between notes.
http://code.google.com/p/lilypond/issues/detail?id=32
Comment #4 by hanwenn:
sorry, this is not a good test-case. Tuning down linewidth will show it, as
does
input/regression/spacing-horizontal-skyline.ly
Issue attribute updates:
Issue 122: stemlet beams incorrect angle
http://code.google.com/p/lilypond/issues/detail?id=122
Comment #1 by hanwenn:
(No comment was entered for this change.)
Issue attribute updates:
Status: Fixed
Labels: fixed_2_10_7 fixed_2_11_7
--
You received this message because you are
Issue 176: programming error: strict-note-spacing together with \afterGrace
http://code.google.com/p/lilypond/issues/detail?id=176
Comment #8 by hanwenn:
(No comment was entered for this change.)
Issue attribute updates:
Status: Fixed
--
You received this message because you are listed
Issue 209: test of lilypond-cvs gateway.
http://code.google.com/p/lilypond/issues/detail?id=209
Comment #2 by hanwenn:
(No comment was entered for this change.)
Issue attribute updates:
Status: Invalid
--
You received this message because you are listed in the owner
or CC fields of thi
Issue 209: test of lilypond-cvs gateway.
http://code.google.com/p/lilypond/issues/detail?id=209
Comment #1 by hanwenn:
actually, bug-lilypond seems more appropriate.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue
22 matches
Mail list logo
