Comment #11 on issue 1014 by brownian.box: Full/multi measure rests should
be semibreve (for any but 4/2)
http://code.google.com/p/lilypond/issues/detail?id=1014
Yes, for the exception it's quite ok.
Thank you very much, indeed.
___
bug-lilypond
Updates:
Status: Accepted
Comment #1 on issue 1756 by brownian.box: architecture diagram image is
missing
http://code.google.com/p/lilypond/issues/detail?id=1756
(No comment was entered for this change.)
___
bug-lilypond mailing list
Updates:
Status: Verified
Comment #9 on issue 1714 by brownian.box: Build error regarding mf2pt1 with
latest texlive (2011) and lilypond
http://code.google.com/p/lilypond/issues/detail?id=1714
(No comment was entered for this change.)
___
Updates:
Labels: -Patch-review fixed_2_15_5
Comment #3 on issue 1710 by lemniska...@gmail.com: rearrange flag
definitions in feta-flags.mf
http://code.google.com/p/lilypond/issues/detail?id=1710
(No comment was entered for this change.)
Updates:
Status: Fixed
Comment #4 on issue 1710 by lemniska...@gmail.com: rearrange flag
definitions in feta-flags.mf
http://code.google.com/p/lilypond/issues/detail?id=1710
(No comment was entered for this change.)
___
bug-lilypond
Comment #5 on issue 1710 by brownian.box: rearrange flag definitions in
feta-flags.mf
http://code.google.com/p/lilypond/issues/detail?id=1710
Please, fixed with which commit ID? I am not sure but this probably can
help us to verify.
Thanks!
Comment #6 on issue 1710 by lemniska...@gmail.com: rearrange flag
definitions in feta-flags.mf
http://code.google.com/p/lilypond/issues/detail?id=1710
Oh, sorry.
it was commit 2904d403afed15fe87e05bc869590ce57dc00aa7
cheers,
Janek
___
Comment #7 on issue 1734 by pkx1...@gmail.com: Lilypond crashes
on fingeringOrientations = #'right if set in \layout { \ context {
\Score ... } }
http://code.google.com/p/lilypond/issues/detail?id=1734
new patch uploaded
http://codereview.appspot.com/4654090/
Status: Accepted
Owner:
Labels: Type-Enhancement
New issue 1757 by pkx1...@gmail.com: Footnotes cannot attach to many layout
objects/grobs
http://code.google.com/p/lilypond/issues/detail?id=1757
This was discussed with Mike Solomon and myself while doing the
documentation for
Comment #6 on issue 1752 by percival.music.ca: redesigning G clef in our
Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
I agree with James -- why the change?
I'd like to see an alternate method of working here. Janek, could you work
on a framework to easily switch
Updates:
Labels: -Priority-High Priority-Low
Comment #2 on issue 1756 by percival.music.ca: architecture diagram image
is missing
http://code.google.com/p/lilypond/issues/detail?id=1756
(No comment was entered for this change.)
___
Updates:
Labels: -Priority-High Priority-Low
Comment #5 on issue 1750 by percival.music.ca: Documentation suggestion:
transposition resulting in triple accidentals
http://code.google.com/p/lilypond/issues/detail?id=1750
(No comment was entered for this change.)
Updates:
Status: Started
Owner: reinhold...@gmail.com
Labels: Patch-review
Comment #1 on issue 1256 by reinhold...@gmail.com: Extra SlurEvent modifies
extents of broken slurs
http://code.google.com/p/lilypond/issues/detail?id=1256
My patch to fix #75 is now updated to
Comment #3 on issue 1234 by reinhold...@gmail.com: Fill-line should not use
word space, but should use springs-and-rods
http://code.google.com/p/lilypond/issues/detail?id=1234
Can this issue be closed? Or shall we remove the fixed_2_13_31 tag?
Updates:
Status: Fixed
Comment #4 on issue 1234 by percival.music.ca: Fill-line should not use
word space, but should use springs-and-rods
http://code.google.com/p/lilypond/issues/detail?id=1234
(No comment was entered for this change.)
Comment #5 on issue 1234 by brownian.box: Fill-line should not use word
space, but should use springs-and-rods
http://code.google.com/p/lilypond/issues/detail?id=1234
The second line in that code exceeds linewidth with 2.15.4. It should not,
I guess?
Comment #2 on issue 734 by reinhold...@gmail.com: tremolos beams placement
on a (single) whole note
http://code.google.com/p/lilypond/issues/detail?id=734
I couldn't find any mention in Gardner Read. But Elaine Gould's Behind Bars
explicitly says: Tremolo strokes must stay within the stave
Updates:
Status: Accepted
Comment #6 on issue 1234 by brownian.box: Fill-line should not use word
space, but should use springs-and-rods
http://code.google.com/p/lilypond/issues/detail?id=1234
(I've not trimmed the image, to see that it's a full page)
Attachments:
test.png
Comment #7 on issue 1234 by brownian.box: Fill-line should not use word
space, but should use springs-and-rods
http://code.google.com/p/lilypond/issues/detail?id=1234
The image was the same (as in comment #6) with 2.13.31, too.
Now i think that this issue should be closed, and another one
Comment #2 on issue 1735 by reinhold...@gmail.com: modifying default
behaviour of tremolo slashes
http://code.google.com/p/lilypond/issues/detail?id=1735
Comment by Joe Neeman (lilypond-devel):
Actually, non-rectangular, constant-sloped beams used to be the default,
but I changed them (some
Updates:
Status: Fixed
Comment #7 on issue 1750 by pkx1...@gmail.com: Documentation suggestion:
transposition resulting in triple accidentals
http://code.google.com/p/lilypond/issues/detail?id=1750
(No comment was entered for this change.)
Updates:
Labels: -backport2_14 backport2_15_5 fixed2_15_5
Comment #6 on issue 1750 by pkx1...@gmail.com: Documentation suggestion:
transposition resulting in triple accidentals
http://code.google.com/p/lilypond/issues/detail?id=1750
(No comment was entered for this change.)
Comment #7 on issue 1752 by lemniska...@gmail.com: redesigning G clef in
our Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
New version of the clef (slightly higher).
Attachments:
clef-demo current Lily.pdf 26.1 KB
clef-demo new proposal.pdf 25.2 KB
Comment #9 on issue 1752 by lemniska...@gmail.com: redesigning G clef in
our Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
2011/7/10 lilyp...@googlecode.com:
Comment #5 on issue 1752 by pkx166h: redesigning G clef in our Feta font
Comment #8 on issue 1752 by lemniska...@gmail.com: redesigning G clef in
our Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
I'm changing it because it doesn't look good. There is enough
not-goodness that it warrants the change in my opinon.
The notehead seems to be a bit
Updates:
Status: Started
Owner: reinhold...@gmail.com
Comment #1 on issue 1563 by reinhold...@gmail.com: strange vertical line at
staff begin using StaffSymbol #'staff-space
http://code.google.com/p/lilypond/issues/detail?id=1563
The problem here is that the check for
Comment #10 on issue 1752 by lemniska...@gmail.com: redesigning G clef in
our Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
I'm not sure if my replies to previous comments were properly sent... If
you didn't get them, check issue webpage.
2011/7/11
Updates:
Labels: Patch-new
Comment #2 on issue 1563 by reinhold...@gmail.com: strange vertical line at
staff begin using StaffSymbol #'staff-space
http://code.google.com/p/lilypond/issues/detail?id=1563
Patch is up for review:
http://codereview.appspot.com/4693043
Comment #6 on issue 1216 by reinhold...@gmail.com: DynamicTextSpanners
should end like hairpins
http://code.google.com/p/lilypond/issues/detail?id=1216
Test case from dupliate issue #1398:
http://lists.gnu.org/archive/html/bug-lilypond/2010-11/msg00030.html
%--
Updates:
Status: Duplicate
Mergedinto: 1216
Comment #1 on issue 1398 by reinhold...@gmail.com: Hairpin following a text
crescendo starts too late
http://code.google.com/p/lilypond/issues/detail?id=1398
(No comment was entered for this change.)
Comment #7 on issue 1216 by reinhold...@gmail.com: DynamicTextSpanners
should end like hairpins
http://code.google.com/p/lilypond/issues/detail?id=1216
Issue 1398 has been merged into this issue.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
Comment #11 on issue 1752 by bordage@gmail.com: redesigning G clef in
our Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
The last version is much better! It is perfectly balanced.
I think we should use this by default, since tis closer to traditional
clefs than the
Comment #13 on issue 1752 by percival.music.ca: redesigning G clef in our
Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
Unless absolutely every single person prefers the new clef, I have serious
concerns about changing it. This sounds like a Critical regression to me.
Comment #9 on issue 1234 by n.putt...@gmail.com: Fill-line should not use
word space, but should use springs-and-rods
http://code.google.com/p/lilypond/issues/detail?id=1234
Keep this as an enhancement.
The commit from comment #2 is for issue #1116 and issue #382.
Updates:
Status: Fixed
Labels: -Patch-review fixed_2_15_5
Comment #3 on issue 1711 by n.putt...@gmail.com: Pitch bend tuning
adjustments
http://code.google.com/p/lilypond/issues/detail?id=1711
6908517be0826a3386264cd6d26d742b18e3a227
Updates:
Labels: -backport2_15_5 -fixed2_15_5 fixed_2_15_5 backport
Comment #8 on issue 1750 by n.putt...@gmail.com: Documentation suggestion:
transposition resulting in triple accidentals
http://code.google.com/p/lilypond/issues/detail?id=1750
(No comment was entered for this
Updates:
Labels: -Patch-new Patch-review
Comment #2 on issue 1676 by pkx1...@gmail.com: Tremolo with change staff
produces false dotted note
http://code.google.com/p/lilypond/issues/detail?id=1676
Passes Make and Reg tests. James
___
Updates:
Labels: -Patch-new Patch-review
Comment #3 on issue 1390 by pkx1...@gmail.com: Tied acciaccaturas should
not be printed with a slur
http://code.google.com/p/lilypond/issues/detail?id=1390
Passes Make and Reg Tests
___
Updates:
Labels: -Patch-new Patch-review
Comment #3 on issue 1581 by pkx1...@gmail.com: Pitched trill between tied
notes causes `unterminated tie' warning
http://code.google.com/p/lilypond/issues/detail?id=1581
Passes Make and Reg tests
Comment #14 on issue 1752 by percival.music.ca: redesigning G clef in our
Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
wait, let me rephrase that: it wouldn't be a Critical regression because it
would be a deliberate change.
However, I think it could still be a bad
Updates:
Status: Verified
Mergedinto:
Comment #2 on issue 1398 by colinpkc...@gmail.com: Hairpin following a text
crescendo starts too late
http://code.google.com/p/lilypond/issues/detail?id=1398
(No comment was entered for this change.)
Comment #4 on issue 814 by colinpkc...@gmail.com: warning-as-error should
be enabled when compiling the regtests
http://code.google.com/p/lilypond/issues/detail?id=814
Phil, is this relevant you your work on the build system generally? If so,
should we update this, perhaps by merging into
Updates:
Owner: ---
Comment #5 on issue 814 by percival.music.ca: warning-as-error should be
enabled when compiling the regtests
http://code.google.com/p/lilypond/issues/detail?id=814
No, it's separate.
Also, note that the this won't happen until after 2.14 was a necessary
Updates:
Owner: mts...@gmail.com
Comment #8 on issue 737 by colinpkc...@gmail.com: Enhancement: support for
footnotes and/or endnotes.
http://code.google.com/p/lilypond/issues/detail?id=737
AFAICS, these are the patches referenced:
4167063 - now closed (draw line above footnotes)
Comment #2 on issue 1705 by colinpkc...@gmail.com: New breve rest with
ledger lines
http://code.google.com/p/lilypond/issues/detail?id=1705
Graham, would you push, please, as Bertrand (and Janek, who I believe to be
his mentor) hasn't got committer access.
Thanks,
Colin
45 matches
Mail list logo
