Updates:
Labels: Font
Comment #7 on issue 1839 by bordage@gmail.com: Improves some parmesan
noteheads.
http://code.google.com/p/lilypond/issues/detail?id=1839
I need some help. I wanted to make two glyphs for each type of note longer
than a whole: one with a small and one with a
Updates:
Labels: -Font
Comment #6 on issue 1854 by bordage@gmail.com: Add some polyphonically
directed grobs
http://code.google.com/p/lilypond/issues/detail?id=1854
Oops, wrong issue. Comment 4 was for issue 1839.
___
bug-lilypond mail
Updates:
Labels: Font
Comment #4 on issue 1854 by bordage@gmail.com: Add some polyphonically
directed grobs
http://code.google.com/p/lilypond/issues/detail?id=1854
I need some help. I wanted to make two glyphs for each type of note longer
than a whole: one with a small and one w
Comment #5 on issue 1854 by bordage@gmail.com: Add some polyphonically
directed grobs
http://code.google.com/p/lilypond/issues/detail?id=1854
I need some help. I wanted to make two glyphs for each type of note longer
than a whole: one with a small and one with a large hole.
(As you can
Updates:
Status: Duplicate
Labels: -Patch-needs_work
Comment #2 on issue 1841 by bordage@gmail.com: Add some polyphonically
directed grobs
http://code.google.com/p/lilypond/issues/detail?id=1841
Duplicate of issue 1854.
___
bug
> It's even worse :( The alignment of dynamics against a chord
> depends on which note appears first in the chord definition.
> Well, maybe it's worse - this way one can at least choose
> which note to align to. Here's the input, output attached.
>
> \version "2.15.8"
>
> % Dynamics on chords wit
Updates:
Status: Verified
Labels: -Patch-needs_work
Comment #1 on issue 1851 by bordage@gmail.com: Do not issue rectstroke
if blot diameter is 0.0
http://code.google.com/p/lilypond/issues/detail?id=1851
This has already been pushed as 5291daf785cd215145473781612732de94890b
Updates:
Labels: -Patch-review Patch-needs_work
Comment #6 on issue 509 by colinpkc...@gmail.com: collision nested tuplet
numbers
http://code.google.com/p/lilypond/issues/detail?id=509
Mike Solomon on Rietveld:
Sorry to not have pushed this yet, but I recently rebased this against
c
Updates:
Labels: -Patch-needs_work Patch-review
Comment #9 on issue 1814 by janek.li...@gmail.com: Breve with
double-line "ears" can collide with accidentals and barlines
http://code.google.com/p/lilypond/issues/detail?id=1814
http://codereview.appspot.com/4931043 is no longer valid.
Updates:
Labels: -Type-Enhancement -Priority-Medium -Engraving-nitpick Type-Defect
Needs-design
Comment #7 on issue 298 by tdaniels...@googlemail.com: Ties do not appear
when shortened because of an accidental
http://code.google.com/p/lilypond/issues/detail?id=298
I don't regard this as a
Comment #3 on issue 1869 by d...@gnu.org: Parser.yy: rearrange to allow
more lenient use of music arguments for music functions
http://code.google.com/p/lilypond/issues/detail?id=1869
lilyp...@googlecode.com writes:
It is documented in "Extending", and quite more so than the previous
state.
Updates:
Labels: -Patch-push Patch-needs_work
Comment #8 on issue 1814 by percival.music.ca: Breve with
double-line "ears" can collide with accidentals and barlines
http://code.google.com/p/lilypond/issues/detail?id=1814
Bertrand made some comments which should be addressed.
___
Updates:
Labels: -Priority-High -Patch-push Patch-needs_work
Comment #24 on issue 1776 by percival.music.ca: Doc: NR - Polymetric
Notation \compoundMeter isn't documented
http://code.google.com/p/lilypond/issues/detail?id=1776
(No comment was entered for this change.)
__
Comment #2 on issue 1869 by pkx1...@gmail.com: Parser.yy: rearrange to
allow more lenient use of music arguments for music functions
http://code.google.com/p/lilypond/issues/detail?id=1869
So is there nothing anywhere we should document - in Internals or Usage or
somewhere else in case this
Updates:
Status: Fixed
Labels: -Patch-push fixed_2_15_10
Comment #6 on issue 723 by k-ohara5...@oco.net: wrong horizontal alignement
of pedal brackets with a second inside a chord
http://code.google.com/p/lilypond/issues/detail?id=723
Fixed with commit 21c7a8b7fc473a154836fad5
Comment #3 on issue 840 by k-ohara5...@oco.net: broken ties too short when
time signature changes
http://code.google.com/p/lilypond/issues/detail?id=840
The fix to 724 increased the space from time-signature to accidental,
making the tie visible in situations of the type shown in this issue
Comment #17 on issue 1785 by k-ohara5...@oco.net: Compressible space before
the first note of a line ?
http://code.google.com/p/lilypond/issues/detail?id=1785
The fix to issue 1856 (people don't want the the space after a time
signatures to stretch at all) brings us back to the status sho
Updates:
Status: Fixed
Labels: -Priority-Postponed fixed_2_15_10
Comment #7 on issue 724 by k-ohara5...@oco.net: Staves that begin with an
accidental should have more space before their first note.
http://code.google.com/p/lilypond/issues/detail?id=724
Fixed with 50ccf06ca193c
Updates:
Status: Started
Labels: -fixed_2_15_10 Patch-needs_work
Comment #19 on issue 1742 by janek.li...@gmail.com: print transposed guitar
chords on piano sheets
http://code.google.com/p/lilypond/issues/detail?id=1742
reverted.
_
19 matches
Mail list logo
