Updates:
Status: Fixed
Labels: fixed_2_13_7
Comment #2 on issue 807 by n.puttock: inconsistent behavior of padded
brackets
http://code.google.com/p/lilypond/issues/detail?id=807
(No comment was entered for this change.)
--
You received this message because you are listed in t
Comment #1 on issue 807 by d...@gnu.org: inconsistent behavior of padded
brackets
http://code.google.com/p/lilypond/issues/detail?id=807
The HTML message URL is not helpful for applying the patch.
--
You received this message because you are listed in the owner
or CC fields of this issue, or
Comment #1 on issue 732 by v.villenave: Alignment problems when vertically
stacking horizontally centered stencils.
http://code.google.com/p/lilypond/issues/detail?id=732
Issue 882 has been merged into this issue.
--
You received this message because you are listed in the owner
or CC fields
Updates:
Status: Duplicate
Mergedinto: 732
Comment #2 on issue 882 by v.villenave: Markup columns collisions
http://code.google.com/p/lilypond/issues/detail?id=882
Indeed. I did find 732, but it's described in a more complex way and I
didn't make
the connection.
--
You receiv
Updates:
Status: Duplicate
Mergedinto: 850
Comment #2 on issue 876 by v.villenave: Spacing bug: text exceeding page
footer
http://code.google.com/p/lilypond/issues/detail?id=876
Indeed. Sorry for the noise.
--
You received this message because you are listed in the owner
or C
Comment #3 on issue 850 by v.villenave: Vertical spacing: text lines
exceeding page bottom
http://code.google.com/p/lilypond/issues/detail?id=850
Issue 876 has been merged into this issue.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because
Comment #1 on issue 882 by n.puttock: Markup columns collisions
http://code.google.com/p/lilypond/issues/detail?id=882
Duplicate of #732.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue not
Comment #2 on issue 889 by Carl.D.Sorensen: SystemStartBrace's variable
vertical extent should not affect their weight
http://code.google.com/p/lilypond/issues/detail?id=889
Perhaps this could be resolved by changing the way the brace scales with
size in the font sources.
--
You received
Comment #1 on issue 889 by v.villenave: SystemStartBrace's variable
vertical extent should not affect their weight
http://code.google.com/p/lilypond/issues/detail?id=889
I'm not sure if this is a good idea, but it could be interesting to have an
alternative font for braces rather than blindly
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Medium Engraving-nitpick
New issue 889 by v.villenave: SystemStartBrace's variable vertical extent
should not affect their weight
http://code.google.com/p/lilypond/issues/detail?id=889
New report from Jonathan Wilkes:
In the fo
Status: Accepted
Owner: v.villenave
Labels: Type-Enhancement Priority-Medium
New issue 888 by v.villenave: Enhancement: ly:stencil-scale
http://code.google.com/p/lilypond/issues/detail?id=888
New request from Robin:
We currently have two basic transformations: ly:stencil-translate and
ly:stenci
Comment #1 on issue 887 by harmathdenes: PDF point-and-click URI links with
special chars wrongly encoded depending on the OS
http://code.google.com/p/lilypond/issues/detail?id=887
As it can be seen, the difference between the encoding of directory and
file names
refers only to the OS X beh
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Medium OpSys-Linux OpSys-OSX
New issue 887 by v.villenave: PDF point-and-click URI links with special
chars wrongly encoded depending on the OS
http://code.google.com/p/lilypond/issues/detail?id=887
New report from Dénes:
http:/
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Medium
New issue 886 by v.villenave: ChordNames horizontal extent may affect note
spacing
http://code.google.com/p/lilypond/issues/detail?id=886
From Jean-Alexis Montignies:
In the following example (reproduced with both 2.12 a
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Low
New issue 885 by v.villenave: Uninstallation issues
http://code.google.com/p/lilypond/issues/detail?id=885
I'm opening this issue to gather all problems we may encounter when
uninstalling LilyPond.
For instance, Patrick has re
Status: Accepted
Owner: v.villenave
CC: nicolas.sceaux, joeneeman
Labels: Type-Defect Priority-Medium
New issue 884 by v.villenave: pageBreak resets page-count property
http://code.google.com/p/lilypond/issues/detail?id=884
From Chris Snyder:
"According to LNR 4.1.2, the page-count setting set
Status: Accepted
Owner: v.villenave
Labels: Type-Collision Priority-Regression
New issue 883 by v.villenave: stems may collide with noteheads in
tightly-spaced music
http://code.google.com/p/lilypond/issues/detail?id=883
In the following example, some notes collide with the chord's stem while
Status: Accepted
Owner: v.villenave
Labels: Type-Collision Priority-Regression
New issue 881 by v.villenave: Arpeggios may collide with laissezVibrer ties
http://code.google.com/p/lilypond/issues/detail?id=881
% From Robin:
% As shown in the attached example, the collision is only reproduced
%
Status: Accepted
Owner: v.villenave
Labels: Type-Collision Priority-Regression
New issue 882 by v.villenave: Markup columns collisions
http://code.google.com/p/lilypond/issues/detail?id=882
In the following example, only the very last part (a column followed with a
regular word) doesn't produce
Status: Accepted
Owner: v.villenave
Labels: Type-Collision Priority-Medium
New issue 880 by v.villenave: Arpeggios collide with notes when
connectArpeggios is set
http://code.google.com/p/lilypond/issues/detail?id=880
% From Robin Bannister:
% When the connectArpeggios mode includes an arpeg
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Medium
New issue 879 by v.villenave: RemoveEmptyStaffContext doesn't need to
disable auto-knee-gap
http://code.google.com/p/lilypond/issues/detail?id=879
As of version 2.13.6, RemoveEmptyStaff still unsets auto-knee-gap, which
s
Comment #1 on issue 876 by paconet.org: Spacing bug: text exceeding page
footer
http://code.google.com/p/lilypond/issues/detail?id=876
This is a dupe of #850 and was fixed by Joe b51279cfe1a
--
You received this message because you are listed in the owner
or CC fields of this issue, or becau
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Medium Engraving-nitpick
New issue 878 by v.villenave: Bowing indications need higher priority than
fingerings
http://code.google.com/p/lilypond/issues/detail?id=878
Please read the discussion on
http://lists.gnu.org/archive/htm
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Medium Engraving-nitpick
New issue 877 by v.villenave: Ottava clefs may not look good
http://code.google.com/p/lilypond/issues/detail?id=877
% Clef-ottavas may be printed too far from the clef: in the "F^8"
% example below, one can
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Medium
New issue 876 by v.villenave: Spacing bug: text exceeding page footer
http://code.google.com/p/lilypond/issues/detail?id=876
From Nicolas Sceaux:
%%% in the first page, text spreads on the page footer (and beyond)
%%% befor
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Low Script
New issue 875 by v.villenave: Generated lilypond-words files are not
complete
http://code.google.com/p/lilypond/issues/detail?id=875
It seems that automatically-generated word files do not include many words
used in L
Comment #5 on issue 874 by jameseli...@googlemail.com: fingerings with show
last length are stacked on the first note
http://code.google.com/p/lilypond/issues/detail?id=874
Ah, I see. That works.
--
You received this message because you are listed in the owner
or CC fields of this issue, or
Updates:
Status: Accepted
Labels: Type-Defect Priority-Low
Comment #4 on issue 874 by jameseli...@googlemail.com: fingerings with show
last length are stacked on the first note
http://code.google.com/p/lilypond/issues/detail?id=874
(No comment was entered for this change.)
--
Comment #3 on issue 874 by percival.music.ca: fingerings with show last
length are stacked on the first note
http://code.google.com/p/lilypond/issues/detail?id=874
No, you're already logged in... I took a guess at your email address, which
turned
out to be wrong. But even worse, the change
Comment #2 on issue 874 by jameseli...@googlemail.com: fingerings with show
last length are stacked on the first note
http://code.google.com/p/lilypond/issues/detail?id=874
Apparently I fail at logging in to the system. That's okay, I fail at most
of google.
Is there a how-to for google co
Comment #1 on issue 874 by percival.music.ca: fingerings with show last
length are stacked on the first note
http://code.google.com/p/lilypond/issues/detail?id=874
I've just added you as a project member, so could you change the status to
accepted,
and give it a defect and low-priority tag?
Status: New
Owner:
New issue 874 by jameselihubailey: fingerings with show last length are
stacked on the first note
http://code.google.com/p/lilypond/issues/detail?id=874
fingerings from skipped music get stacked onto the first duration
when using showLastLength
\version "2.13.6"
show
Updates:
Status: Invalid
Comment #1 on issue 873 by percival.music.ca: 2.13.6-1 fails to render
chords + lyrics at the same time
http://code.google.com/p/lilypond/issues/detail?id=873
Please don't add items directly to the tracker; send an email to the
bug-lilypond
list instead. A
Status: New
Owner:
New issue 873 by cska...@freemail.hu: 2.13.6-1 fails to render chords +
lyrics at the same time
http://code.google.com/p/lilypond/issues/detail?id=873
2.12 worked well, but I need to use 2.13 because of SVG.
Lilypond + PDF files attached.
If you check, the chords are
Comment #2 on issue 706 by paconet.org: ledger lines should take
simultaneous notes' accidentals into account
http://code.google.com/p/lilypond/issues/detail?id=706
The last comment's example is clearly due to ledger lines being printed
multiple
times, despite of what I wrongly said.
--
Y
Comment #2 on issue 872 by percival.music.ca: Changes split-page has broken
images
http://code.google.com/p/lilypond/issues/detail?id=872
We don't *have* to discuss it as a tracker issue, but I'm finding it
alarmingly easy
for me to forget things these days. I suppose I could keep my own p
Updates:
Status: Invalid
Comment #1 on issue 872 by john.mandereau: Changes split-page has broken
images
http://code.google.com/p/lilypond/issues/detail?id=872
This bug is easily fixed in postprocess_html.py, but I don't see why you
want to
produce both a splitted and a non-splitted
Status: Accepted
Owner: percival.music.ca
Labels: Type-Other Priority-High
New issue 872 by percival.music.ca: Changes split-page has broken images
http://code.google.com/p/lilypond/issues/detail?id=872
after I moved Changes to be a split-page manual, the images are fine in the
one-big-page vers
Comment #1 on issue 706 by paconet.org: ledger lines should take
simultaneous notes' accidentals into account
http://code.google.com/p/lilypond/issues/detail?id=706
% another example shows the problem on simple chords, caused possibly not
anymore by
ledger lines being printed multiple time
Status: Accepted
Owner: percival.music.ca
Labels: Type-Defect Priority-Medium OpSys-OSX
New issue 871 by percival.music.ca: support for MacOS X 10.6 snow leopard
http://code.google.com/p/lilypond/issues/detail?id=871
MacOS X 10.6 seems to have broken something; building the font cache for
the fi
Comment #8 on issue 34 by percival.music.ca: Grace synchronization
http://code.google.com/p/lilypond/issues/detail?id=34
Fair enough, but nobody *else* has the resources to dive that deep.
Believe me, we
know about the bug. But unless anybody steps forward to tackle it, adding
more noise
Comment #7 on issue 34 by harmathdenes: Grace synchronization
http://code.google.com/p/lilypond/issues/detail?id=34
I understand that this would be a tremendous amount work, since handling
grace notes
this way seems like a fundamental design decision. Unfortunately, although a
developer mysel
Status: Accepted
Owner: v.villenave
Labels: Type-Enhancement Priority-Low OpSys-All Font
New issue 870 by v.villenave: Enhancement: easier support for alternative
music fonts
http://code.google.com/p/lilypond/issues/detail?id=870
So far, LilyPond only supports the Feta music font. However, S
Comment #6 on issue 34 by grahamnus: Grace synchronization
http://code.google.com/p/lilypond/issues/detail?id=34
It's low priority because nobody wants to work on it.
If you're interested in helping out, please do! If you're not willing to
work on it
yourself, then realise that we have exac
Comment #5 on issue 34 by harmathdenes: Grace synchronization
http://code.google.com/p/lilypond/issues/detail?id=34
May I ask why this is Low priority? This is a serious issue: consider a huge
partition beginning with grace notes... I can't achieve correct output even
after
putting grace skips
Comment #5 on issue 771 by n.puttock: Instrument names should be centered
accordingly to StartSystem objects in other staves
http://code.google.com/p/lilypond/issues/detail?id=771
You can certainly add a global override to a \layout block; the example I
posted
above used the follow:
\layo
Updates:
Labels: Bounty
Comment #3 on issue 839 by v.villenave: Enhancement: improving midi2ly
conversion
http://code.google.com/p/lilypond/issues/detail?id=839
John Mandereau and Daniel Cartron (a French contributor) have been
discussing
additional improvements to midi2ly, esp. wr
Status: Accepted
Owner: percival.music.ca
Labels: Type-Defect Priority-High Maintainability
New issue 869 by percival.music.ca: input/regression/ renaming to
regression/
http://code.google.com/p/lilypond/issues/detail?id=869
This should be done after the last 2.12 release, but before the firs
Updates:
Status: Fixed
Labels: fixed_2_13_6
Comment #2 on issue 850 by joeneeman: Vertical spacing: text lines
exceeding page bottom
http://code.google.com/p/lilypond/issues/detail?id=850
(No comment was entered for this change.)
--
You received this message because you are l
Comment #4 on issue 771 by paconet.org: Instrument names should be centered
accordingly to StartSystem objects in other staves
http://code.google.com/p/lilypond/issues/detail?id=771
Neil: yes, I really meant negative padding, provided that the names remain
centered.
Could it be applied once
Comment #3 on issue 771 by n.puttock: Instrument names should be centered
accordingly to StartSystem objects in other staves
http://code.google.com/p/lilypond/issues/detail?id=771
Hi Francisco,
When you say `negative offset', do you mean move the column of instrument
names
closer to the s
Comment #2 on issue 771 by paconet.org: Instrument names should be centered
accordingly to StartSystem objects in other staves
http://code.google.com/p/lilypond/issues/detail?id=771
This is now somewhat fixed. A small problem remains: could an additional
negative
offset be automatically se
Comment #4 on issue 612 by frederic...@m4x.org: spacing problem in tied
chords with accidentals
http://code.google.com/p/lilypond/issues/detail?id=612
Same issue with 2.12.2 and 2.13.15 with two voices instead of a chord:
% the sharp of fis should be closer to the note head
% it is shifted t
Comment #10 on issue 783 by percival.music.ca: release list for 2.14
http://code.google.com/p/lilypond/issues/detail?id=783
oh, sorry. I didn't realize that it changed the normal \paper stuff.
--
You received this message because you are listed in the owner
or CC fields of this issue, or becau
Comment #9 on issue 783 by reinhold.kainhofer: release list for 2.14
http://code.google.com/p/lilypond/issues/detail?id=783
With all due respect, I don't regard all \paper variables, like
between-system-
http://kainhofer.com/~lilypond/ajax/user/lilypond/Page-formatting.html) as
tweaks.
Most
Comment #8 on issue 783 by percival.music.ca: release list for 2.14
http://code.google.com/p/lilypond/issues/detail?id=783
I don't think we need convert-ly rules for vertical spacing changes. I
mean, yes,
that would be nice, but I'm not going to delay the release for them.
Tweaks are
alwa
Updates:
Labels: Syntax
Comment #3 on issue 817 by v.villenave: Enhancement: new syntax for more
flexible cresc/dim spanners
http://code.google.com/p/lilypond/issues/detail?id=817
Then this is only waiting for a major version bump to be fully taken
advantage of,
since it would impl
Comment #7 on issue 783 by reinhold.kainhofer: release list for 2.14
http://code.google.com/p/lilypond/issues/detail?id=783
What is still missing are:
-) Good defaults for the vertical spacing. Current problems:
o) Without stretching, the staves are far too close
o) With stretching, the stav
Comment #2 on issue 817 by reinhold.kainhofer: Enhancement: new syntax for
more flexible cresc/dim spanners
http://code.google.com/p/lilypond/issues/detail?id=817
The patch for the backend is commited (snippet has been added showing how
to define
one's own commands or override the default
Comment #3 on issue 832 by reinhold.kainhofer: Wrong UTF-8 encoded
filenames passed to gs
http://code.google.com/p/lilypond/issues/detail?id=832
This issue has been fixed meanwhile. A file named e.g. câcâ.ly compiles
just fine
with current 2.13.5
--
You received this message because you
Updates:
Labels: Priority-Low
Comment #1 on issue 712 by percival.music.ca: alignment of multiple \tempo
marks over `church rests'
http://code.google.com/p/lilypond/issues/detail?id=712
(No comment was entered for this change.)
--
You received this message because you are listed in t
Updates:
Labels: Priority-Low
Comment #6 on issue 708 by percival.music.ca: convert-ly fails to convert
keySignature
http://code.google.com/p/lilypond/issues/detail?id=708
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or CC
Updates:
Labels: Priority-High
Comment #6 on issue 783 by percival.music.ca: release list for 2.14
http://code.google.com/p/lilypond/issues/detail?id=783
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or CC fields of this issue
Updates:
Labels: Priority-Low
Comment #1 on issue 830 by percival.music.ca: Task: rename feta filenames
in English
http://code.google.com/p/lilypond/issues/detail?id=830
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or CC f
Updates:
Labels: Priority-Medium
Comment #1 on issue 831 by percival.music.ca: add progress indicator
http://code.google.com/p/lilypond/issues/detail?id=831
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or CC fields of this is
Updates:
Labels: Priority-Low
Comment #1 on issue 721 by percival.music.ca: Dynamics can collide with
notes when applied to cross-staff voices
http://code.google.com/p/lilypond/issues/detail?id=721
(No comment was entered for this change.)
--
You received this message because you are
Updates:
Labels: Priority-Medium
Comment #2 on issue 832 by percival.music.ca: Wrong UTF-8 encoded filenames
passed to gs
http://code.google.com/p/lilypond/issues/detail?id=832
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
Updates:
Labels: Priority-Low
Comment #2 on issue 774 by percival.music.ca: wrong horizontal trill
position in small staff lines
http://code.google.com/p/lilypond/issues/detail?id=774
(No comment was entered for this change.)
--
You received this message because you are listed in the
Updates:
Labels: Priority-Low
Comment #1 on issue 771 by percival.music.ca: Instrument names should be
centered accordingly to StartSystem objects in other staves
http://code.google.com/p/lilypond/issues/detail?id=771
(No comment was entered for this change.)
--
You received this mes
Updates:
Labels: Priority-Low
Comment #4 on issue 711 by percival.music.ca: Filter out unknown font
formats
http://code.google.com/p/lilypond/issues/detail?id=711
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or CC fields o
Updates:
Labels: -Priority-Medium Priority-Regression
Comment #1 on issue 850 by nicolas.sceaux: Vertical spacing: text lines
exceeding page bottom
http://code.google.com/p/lilypond/issues/detail?id=850
(No comment was entered for this change.)
--
You received this message because yo
Updates:
Status: Fixed
Labels: fixed_2_13_6
Comment #3 on issue 69 by n.puttock: automatically add mark to end of score
request (easy workaround)
http://code.google.com/p/lilypond/issues/detail?id=69
(No comment was entered for this change.)
--
You received this message beca
Updates:
Summary: \parenthesize does not take accidentals into account
Labels: -Type-Enhancement Type-Collision
Comment #4 on issue 155 by v.villenave: \parenthesize does not take
accidentals into account
http://code.google.com/p/lilypond/issues/detail?id=155
Definitely! Added
Status: Accepted
Owner: v.villenave
Labels: Type-Collision Priority-Medium
New issue 868 by v.villenave: \parenthesize does not take dotted notes into
account
http://code.google.com/p/lilypond/issues/detail?id=868
% In the following example, the right parenthese overlaps with the dot.
\versi
Comment #3 on issue 155 by perpeduumimmobile: \parenthesize should include
accidentals as well as note heads
http://code.google.com/p/lilypond/issues/detail?id=155
The same should hold for dotted notes.
\version "2.13.5"
\relative c'' { <\parenthesize cis>2. }
Attachments:
paren.png
Updates:
Status: Verified
Comment #5 on issue 656 by v.villenave: -dclip-systems error
when 'header:title is defined
http://code.google.com/p/lilypond/issues/detail?id=656
Never mind. I was actually running an old build (I forgot to 'make install'
after
'make' :-).
--
You received
Comment #4 on issue 656 by n.puttock: -dclip-systems error
when 'header:title is defined
http://code.google.com/p/lilypond/issues/detail?id=656
I can only test the MinGW versions, but both are fine here.
--
You received this message because you are listed in the owner
or CC fields of this is
Comment #3 on issue 853 by n.puttock: use .ily for "setup" input files
http://code.google.com/p/lilypond/issues/detail?id=853
I have a convert-ly rule ready and waiting. :)
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this
Comment #2 on issue 853 by n.puttock: use .ily for "setup" input files
http://code.google.com/p/lilypond/issues/detail?id=853
I have a convert-ly ready and waiting. :)
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
Status: Accepted
Owner: percival.music.ca
Labels: Type-Enhancement Priority-Medium Maintainability
New issue 867 by percival.music.ca: lilypond-book can have hash collisions
http://code.google.com/p/lilypond/issues/detail?id=867
It would be nice if lilypond-book checked if a filename already exi
Status: Accepted
Owner: percival.music.ca
Labels: Type-Defect Priority-Medium Maintainability
New issue 866 by percival.music.ca: gub should use a real buildnumber
http://code.google.com/p/lilypond/issues/detail?id=866
Currently I build GUB with the attached disgusting patch. It would be nice
i
Updates:
Status: Started
Comment #1 on issue 836 by v.villenave: Enhancement: output-suffix as a
(Score) context property
http://code.google.com/p/lilypond/issues/detail?id=836
Ian is "trying to get [his] head around how to implement this properly".
Good luck to
you Ian!
Whenever
Comment #11 on issue 714 by v.villenave: let the .ly file specify the
output filename
http://code.google.com/p/lilypond/issues/detail?id=714
OK, Ian appears to be working hard on Issue 836 so the regtest will have to
wait.
I'll mark this one as verified when 836 is closed as well.
--
You
Comment #4 on issue 648 by paconet.org: Add glyph for longa note in French
style
http://code.google.com/p/lilypond/issues/detail?id=648
Breve? wait a minute. I could be wrong, but this sample suggests that the
double-lines glyph is for longa, and single- is for breve.
ftp://ftp.cs.dartmouth.
Comment #10 on issue 698 by pnorcks: Windows users should be offered a
better first impression
http://code.google.com/p/lilypond/issues/detail?id=698
In response to Valentin's original post, I don't think it's worth working
too much on
the *existing* LilyPad for Windows, per se. This edito
Comment #3 on issue 648 by v.villenave: Add glyph for longa note in French
style
http://code.google.com/p/lilypond/issues/detail?id=648
Oops, it's already in changes.tely. I was grepping for "longa" instead
of "breve".
Sorry for the noise!
--
You received this message because you are list
Comment #1 on issue 865 by Carl.D.Sorensen: Enhancement: ancient tablatures
support
http://code.google.com/p/lilypond/issues/detail?id=865
There was some discussion about this on the -devel website some time ago
with Dana Emery, but I'm not sure
anything useful came of it.
http://lists.gn
Status: Accepted
Owner: v.villenave
CC: paconet.org
Labels: Type-Enhancement Priority-Postponed Bounty tablatures
New issue 865 by v.villenave: Enhancement: ancient tablatures support
http://code.google.com/p/lilypond/issues/detail?id=865
Francisco Vila has found a nice feature that could be imp
Updates:
Status: Verified
Comment #3 on issue 325 by v.villenave: system-count stops stretching
http://code.google.com/p/lilypond/issues/detail?id=325
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or CC fields of this issue, o
Updates:
Status: Verified
Comment #4 on issue 328 by v.villenave: collision right-oriented fingering
and augmentation dot
http://code.google.com/p/lilypond/issues/detail?id=328
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
Updates:
Status: Verified
Comment #4 on issue 452 by v.villenave: shortInstrumentName change gets
confused when changing directly at a linebreak
http://code.google.com/p/lilypond/issues/detail?id=452
(No comment was entered for this change.)
--
You received this message because you a
Updates:
Status: Verified
Comment #6 on issue 453 by v.villenave: \scaleDurations adds too many beams
to tremolos
http://code.google.com/p/lilypond/issues/detail?id=453
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or CC fi
Updates:
Status: Verified
Comment #5 on issue 462 by v.villenave: horizontal space of invisible
barline
http://code.google.com/p/lilypond/issues/detail?id=462
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or CC fields of th
Updates:
Status: Verified
Comment #5 on issue 496 by v.villenave: page-splitting calculation needs
work
http://code.google.com/p/lilypond/issues/detail?id=496
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or CC fields of th
Updates:
Status: Verified
Comment #59 on issue 504 by v.villenave: lilypond broken on osx 10.5 x86
http://code.google.com/p/lilypond/issues/detail?id=504
(Snow Leopard support seems to be in pretty good shape compared to the 10.5
mess.)
http://lists.gnu.org/archive/html/bug-lilypond/
Updates:
Status: Verified
Comment #19 on issue 546 by v.villenave: Incorrect merging when a same note
has different accidentals
http://code.google.com/p/lilypond/issues/detail?id=546
Verified on the stable branch.
--
You received this message because you are listed in the owner
or CC
Updates:
Status: Verified
Comment #10 on issue 569 by v.villenave: Consistency in property names:
beam-thickness
http://code.google.com/p/lilypond/issues/detail?id=569
The convert rules look fine to me, so I'm marking this as Verified. Thanks!
--
You received this message because you
Updates:
Status: Verified
Comment #2 on issue 581 by v.villenave: add engraver for dynamics;
simplifies piano-centered-dynamics
http://code.google.com/p/lilypond/issues/detail?id=581
Nice :-)
--
You received this message because you are listed in the owner
or CC fields of this issue,
Updates:
Status: Verified
Comment #5 on issue 593 by v.villenave: FiguredBass context is placed too
close to the Staff
http://code.google.com/p/lilypond/issues/detail?id=593
... And verified. Thanks!
--
You received this message because you are listed in the owner
or CC fields of thi
Updates:
Status: Verified
Comment #2 on issue 648 by v.villenave: Add glyph for longa note in French
style
http://code.google.com/p/lilypond/issues/detail?id=648
Does this deserve a NEWS item?
--
You received this message because you are listed in the owner
or CC fields of this issue
1 - 100 of 2702 matches
Mail list logo
