Updates:
Status: Fixed
Comment #13 on issue 695 by mts...@gmail.com: slurs may take too much
vertical extent
http://code.google.com/p/lilypond/issues/detail?id=695
Pushed to staging as 19520fd5bbd221ca1d35011d7710e233c92a44b0
___
Updates:
Status: Fixed
Comment #8 on issue 257 by mts...@gmail.com: collision accent and tuplet
bracket
http://code.google.com/p/lilypond/issues/detail?id=257
Pushed as 26d40794616f7dc6d47af25bb373a5d2353633cf.
___
bug-lilypond mailing
Updates:
Status: Fixed
Comment #2 on issue 1361 by mts...@gmail.com: Collision: TupletNumber and
Script
http://code.google.com/p/lilypond/issues/detail?id=1361
Fixed with 26d40794616f7dc6d47af25bb373a5d2353633cf.
___
bug-lilypond mailing
Updates:
Status: Fixed
Comment #6 on issue 1861 by mts...@gmail.com: DynamicText attached to
spacer rest not correctly aligned
http://code.google.com/p/lilypond/issues/detail?id=1861
Pushed as 47236e0a7a5a75d5dd2be521c44102b20d8c76ce
___
Updates:
Status: Fixed
Comment #9 on issue 2084 by mts...@gmail.com: script-accidental avoidance
fails for articulations
http://code.google.com/p/lilypond/issues/detail?id=2084
Pushed as d4d2066396729b224a3b041d37573efbb30c5303.
___
Updates:
Status: Fixed
Comment #5 on issue 1947 by mts...@gmail.com: Stem Tremoli for
double-stemmed notes are too short on the right side.
http://code.google.com/p/lilypond/issues/detail?id=1947
Pushed to staging as 297e9f6f16be3a451f2381c00e7f44ac61232154.
Updates:
Labels: Patch-new
Comment #2 on issue 1629 by mts...@gmail.com: Tuplet line collides with
fingering
http://code.google.com/p/lilypond/issues/detail?id=1629#c2
Avoids TupletBracket-Fingering and TupletBracket-StringNumber collisions.
http://codereview.appspot.com/5505079
Comment #9 on issue 2066 by janek.li...@gmail.com: Patch: Prevents
accidentals from hanging over barlines.
http://code.google.com/p/lilypond/issues/detail?id=2066
Guys, what are you tryng to do?! Accidentals that can overhang barlines
are good for the look of the music. Don't you think
Comment #10 on issue 2066 by m...@apollinemike.com: Patch: Prevents
accidentals from hanging over barlines.
http://code.google.com/p/lilypond/issues/detail?id=2066
I would prefer the second example below over the first.
\relative c {
R1 |
\repeat unfold 12 { ais bis cis dis eis4 }
}
Status: Accepted
Owner:
CC: mts...@gmail.com, milimet...@gmail.com
Labels: Type-Enhancement
New issue 2141 by janek.li...@gmail.com: accidental spacing - some
accidentals are too far from each other
http://code.google.com/p/lilypond/issues/detail?id=2141
Some combinations of
Status: Accepted
Owner:
CC: milimet...@gmail.com
Labels: Type-Enhancement
New issue 2142 by janek.li...@gmail.com: accidental right-padding should
depend on the tightness of music
http://code.google.com/p/lilypond/issues/detail?id=2142
When notes are close togehter, accidentals should
Status: Accepted
Owner:
CC: milimet...@gmail.com
Labels: Type-Enhancement
New issue 2143 by janek.li...@gmail.com: accidental arrangement should
depend on tightness of music
http://code.google.com/p/lilypond/issues/detail?id=2143
depending on space available, accidentals should be
Status: Accepted
Owner:
New issue 2144 by janek.li...@gmail.com: accidentals should be able to
slide over/under suspended notes without problems
http://code.google.com/p/lilypond/issues/detail?id=2144
Currently Lily tries too hard to keep accidentals not colliding with
notes. The
Status: Accepted
Owner:
New issue 2145 by janek.li...@gmail.com: shorter versions of accidentals
for use in tight situations
http://code.google.com/p/lilypond/issues/detail?id=2145
As issue 2143 and issue 2144 say, sometimes accidentals should be packed
tightly. It would give good
Comment #1 on issue 2141 by janek.li...@gmail.com: accidental spacing -
some accidentals are too far from each other
http://code.google.com/p/lilypond/issues/detail?id=2141
More real engraving examples.
Once again a list of related issues (this time with links - previously the
tracker
Comment #1 on issue 2144 by janek.li...@gmail.com: accidentals should be
able to slide over/under suspended notes without problems
http://code.google.com/p/lilypond/issues/detail?id=2144
Another example:
\relative {
g' a gis'! a b gis'! b c gis'! c d gis!
{
gis'! gis! gis! gis!
} \\
Comment #6 on issue 726 by janek.li...@gmail.com: Request: accidentals in
the same octave would look better not aligned (in some cases)
http://code.google.com/p/lilypond/issues/detail?id=726
More examples attached.
Also, the behaviour mentioned in comment #1 is not fixed. Issue 2144 was
Status: Accepted
Owner:
Labels: Type-Build
New issue 2146 by philehol...@gmail.com: Error: Illegal entry in bfrange
block in ToUnicode CMap
http://code.google.com/p/lilypond/issues/detail?id=2146
The error in the title occurs when trying to create LilyPond documentation
that contains
Status: New
Owner:
Labels: Type-Patch Patch-new
New issue 2147 by philehol...@gmail.com: Patch: Fixes width of NR A.11 -
List of special character
http://code.google.com/p/lilypond/issues/detail?id=2147
Fixes width of NR A.11 - List of special character
Comment #1 on issue 2147 by philehol...@gmail.com: Patch: Fixes width of NR
A.11 - List of special character
http://code.google.com/p/lilypond/issues/detail?id=2147
At present, the NR section A.11 has a table which flows off the side of the
PDF page. This patch fixes that, with the table
Status: Accepted
Owner:
CC: milimet...@gmail.com
Labels: Type-Ugly
New issue 2148 by janek.li...@gmail.com: object outlines shouldn't be
rectangular
http://code.google.com/p/lilypond/issues/detail?id=2148
Currently many objects are treated as rectangles (dynamics, lyrics, lyric
Updates:
Labels: Type-Enhancement Needs-design
Comment #1 on issue 2145 by janek.li...@gmail.com: shorter versions of
accidentals for use in tight situations
http://code.google.com/p/lilypond/issues/detail?id=2145
(No comment was entered for this change.)
Comment #11 on issue 2066 by janek.li...@gmail.com: Patch: Prevents
accidentals from hanging over barlines.
http://code.google.com/p/lilypond/issues/detail?id=2066
I partly agree, but what about
\relative c {
c1 | c1
\repeat unfold 8 { ais bis
Updates:
Status: Fixed
Labels: -Patch-push fixed_2_15_24
Comment #7 on issue 2094 by carl.d.s...@gmail.com:
spacing-measure-length.ly regtest has time sig overlaying rest
http://code.google.com/p/lilypond/issues/detail?id=2094
Pushed to staging as 297e9f6..8118309
Comment #12 on issue 2066 by m...@apollinemike.com: Patch: Prevents
accidentals from hanging over barlines.
http://code.google.com/p/lilypond/issues/detail?id=2066
As always, I think the most important thing is to check the literature.
I'd look at the scores of Messiaen and Feldman to start,
Comment #2 on issue 2141 by lemzw...@gmail.com: accidental spacing - some
accidentals are too far from each other
http://code.google.com/p/lilypond/issues/detail?id=2141
I agree with all your suggestions except bar 75: I somehow dislike making
the naturals smaller; the shape changes too
Comment #1 on issue 2142 by lemzw...@gmail.com: accidental right-padding
should depend on the tightness of music
http://code.google.com/p/lilypond/issues/detail?id=2142
Providing squeezed glyph variants for tight typesetting is a good idea!
___
Comment #1 on issue 2143 by lemzw...@gmail.com: accidental arrangement
should depend on tightness of music
http://code.google.com/p/lilypond/issues/detail?id=2143
I strongly disagree to align two sharp signs vertically for a sixth! This
looks really bad IMHO, even in the real-world
Comment #2 on issue 2143 by n.putt...@gmail.com: accidental arrangement
should depend on tightness of music
http://code.google.com/p/lilypond/issues/detail?id=2143
I agree with Werner. That example looks awful.
Unless I'm mistaken, the accurate box code deliberated prevents the sixths
Thanks Heiko
Forwarding to the bug list, as I know nothing about emacs.
To help, could you please reply to all with the url of the offending page.
Trevor
- Original Message -
From: Heiko Schroeder hei...@evb-1.od.shuttle.de
To: t.dani...@treda.co.uk
Sent: Wednesday, December 28,
Comment #2 on issue 2142 by m...@apollinemike.com: accidental right-padding
should depend on the tightness of music
http://code.google.com/p/lilypond/issues/detail?id=2142
Welcome to my world of pain.
I toyed around with ideas like this in my summer-of-lily but gave up
because of the
Comment #13 on issue 2066 by n.putt...@gmail.com: Patch: Prevents
accidentals from hanging over barlines.
http://code.google.com/p/lilypond/issues/detail?id=2066
I've just had a quick flick through Turangalîla-Symphonie and Quatuor pour
la Fin du Temps. There are no cases where
Comment #3 on issue 2143 by philehol...@gmail.com: accidental arrangement
should depend on tightness of music
http://code.google.com/p/lilypond/issues/detail?id=2143
FWIW, Elaine Gould allows accidentals a sixth apart to align when the upper
one is a flat, but says they should be offset
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2149 by mts...@gmail.com: Patch: Creates non-negative-integer?
predicate.
http://code.google.com/p/lilypond/issues/detail?id=2149
Creates non-negative-integer? predicate.
http://codereview.appspot.com/5501081
Comment #1 on issue 2149 by mts...@gmail.com: Patch: Creates
non-negative-integer? predicate.
http://code.google.com/p/lilypond/issues/detail?id=2149#c1
Creates non-negative-integer? predicate.
http://codereview.appspot.com/5501081
___
Comment #3 on issue 2141 by janek.li...@gmail.com: accidental spacing -
some accidentals are too far from each other
http://code.google.com/p/lilypond/issues/detail?id=2141
Werner,
I would force naturals in sixths (m. 75) closer than they are typeset
currently by Lily only when music is
Comment #23 on issue 1943 by chh...@gmail.com: lilypond after 2.15.8 fails
on x86 Macs
http://code.google.com/p/lilypond/issues/detail?id=1943
Here is a next trial to finally resolve this issue. I tested the x86
version on 10.5.8 and 10.7.2. Please test on as many configurations (x86,
Comment #3 on issue 2142 by janek.li...@gmail.com: accidental right-padding
should depend on the tightness of music
http://code.google.com/p/lilypond/issues/detail?id=2142
Mike,
do you mean that generally changing accidentals' right-padding depending on
situation is very hard, or is it
Hello,
On 28 December 2011 17:17, Trevor Daniels t.dani...@treda.co.uk wrote:
Thanks Heiko
Forwarding to the bug list, as I know nothing about emacs.
To help, could you please reply to all with the url of the offending page.
Trevor
- Original Message - From: Heiko Schroeder
Comment #4 on issue 2143 by k-ohara5...@oco.net: accidental arrangement
should depend on tightness of music
http://code.google.com/p/lilypond/issues/detail?id=2143
Schirmer's engraver for the Carl Mikuli edition followed the rules --
including aligning accidentals in octaves (issue 726) at
Comment #14 on issue 2066 by d...@gnu.org: Patch: Prevents accidentals from
hanging over barlines.
http://code.google.com/p/lilypond/issues/detail?id=2066
Personally, similar to chord names hanging over, I see little problem with
letting accidentals hang over barlines. It would be a
Comment #4 on issue 2142 by m...@apollinemike.com: accidental right-padding
should depend on the tightness of music
http://code.google.com/p/lilypond/issues/detail?id=2142
The problem is that right-padding is calculated in order to calculate the
springs that are then used in spring-and-rod
Comment #5 on issue 2142 by m...@apollinemike.com: accidental right-padding
should depend on the tightness of music
http://code.google.com/p/lilypond/issues/detail?id=2142
In the current model, I think that the only way to get this sorta thing
implemented is by faking a spacing calculation
Comment #6 on issue 2142 by lemzw...@gmail.com: accidental right-padding
should depend on the tightness of music
http://code.google.com/p/lilypond/issues/detail?id=2142
This `conditional skylines' approach is overkill IMHO for chords and its
accidentals. I would rather consider the
Comment #5 on issue 2143 by lemzw...@gmail.com: accidental arrangement
should depend on tightness of music
http://code.google.com/p/lilypond/issues/detail?id=2143
It's obviously a matter of tightness...
My feeling is that we should delay handling of non-standard alignment (this
is, not
Comment #6 on issue 2143 by janek.li...@gmail.com: accidental arrangement
should depend on tightness of music
http://code.google.com/p/lilypond/issues/detail?id=2143
Ok, i agree that aligning vertically sharps in sixth doesn't look good;
especially in Lily engraving (sharps from Feta font
Comment #7 on issue 2142 by janek.li...@gmail.com: accidental right-padding
should depend on the tightness of music
http://code.google.com/p/lilypond/issues/detail?id=2142
Hmm? Accidentals' right-padding isn't calculated, it's a constant value.
It doesn't depend on anything, as far as i
Comment #24 on issue 1943 by stans...@gmail.com: lilypond after 2.15.8
fails on x86 Macs
http://code.google.com/p/lilypond/issues/detail?id=1943
I tested the applications on an iMac x86 running OS X 10.5.8 and on a
PowerBook G4 running OS X 10.5.8. LilyPond loaded without error on both
Is there a way to make add/remove-grace-property cooperate with midi ?
\version 2.15.18 % In earlier versions, replace $ by #
\score {
\new Staff {
$(add-grace-property 'Voice 'Fingering 'font-size -6)
\new Voice { b2 \grace b-2 c'-3 }
}
\layout{}
\midi{} %% Wrong type argument
Status: New
Owner:
New issue 2150 by tomspuh...@gmail.com: 2.15.23 doesn't compile on Mageia
http://code.google.com/p/lilypond/issues/detail?id=2150
This is the line where it stops
Comment #10 on issue 1826 by k-ohara5...@oco.net: Guile 2.0 compat:
`conditional-circle-markup' definition needs to be relocated
http://code.google.com/p/lilypond/issues/detail?id=1826
Issue 2150 has been merged into this issue.
___
bug-lilypond
Updates:
Status: Duplicate
Mergedinto: 1826
Comment #1 on issue 2150 by k-ohara5...@oco.net: 2.15.23 doesn't compile on
Mageia
http://code.google.com/p/lilypond/issues/detail?id=2150
Tom, please email bug reports to bug-lilypond@gnu.org
The 2 MB attachment eats into a 50 MB
Updates:
Labels: Patch-review
Comment #2 on issue 2147 by lilypond...@gmail.com: Patch: Fixes width of NR
A.11 - List of special character
http://code.google.com/p/lilypond/issues/detail?id=2147#c2
Patchy the autobot says: LGTM.
___
Updates:
Labels: Patch-review
Comment #2 on issue 2149 by lilypond...@gmail.com: Patch: Creates
non-negative-integer? predicate.
http://code.google.com/p/lilypond/issues/detail?id=2149#c2
Patchy the autobot says: LGTM.
___
bug-lilypond
Updates:
Labels: Patch-review
Comment #3 on issue 1629 by lilypond...@gmail.com: Tuplet line collides
with fingering
http://code.google.com/p/lilypond/issues/detail?id=1629#c3
Patchy the autobot says: LGTM.
___
bug-lilypond mailing list
Status: Accepted
Owner:
New issue 2151 by idragos...@gmail.com: add-grace-note usage interferes
with MIDI output in same score block
http://code.google.com/p/lilypond/issues/detail?id=2151
add/remove-grace-property does not cooperate with midi in the same score
block. Compile
On Wed, Dec 28, 2011 at 9:55 PM, Keith OHara k-ohara5...@oco.net wrote:
Is there a way to make add/remove-grace-property cooperate with midi ?
Hi Keith --
Thanks for your bug report. I reproduced this issue in 2.14 also. I've
added this as issue 2151
--
Brett W. McCoy --
Updates:
Labels: Patch-review
Comment #4 on issue 2137 by lilypond...@gmail.com: Patch: Doc: NR
improve 'visibility' of 'q' operation
http://code.google.com/p/lilypond/issues/detail?id=2137#c4
Patchy the autobot says: LGTM.
___
Updates:
Labels: Patch-new
Comment #6 on issue 2092 by carl.d.s...@gmail.com: lily-git.tcl should
using a working branch
http://code.google.com/p/lilypond/issues/detail?id=2092#c6
Update lilygit.tcl (Issue 2092)
Makes lilygit.tcl respect the environment variable $LILYPOND_GIT.
If
Comment #1 on issue 2146 by lemzw...@gmail.com: Error: Illegal entry in
bfrange block in ToUnicode CMap
http://code.google.com/p/lilypond/issues/detail?id=2146
Of course you mean texi2pdf...
___
bug-lilypond mailing list
bug-lilypond@gnu.org
Updates:
Labels: Patch-review
Comment #23 on issue 2026 by lilypond...@gmail.com: Make markup utility
definitions available via new (scm markup-utility-defs) scheme module
http://code.google.com/p/lilypond/issues/detail?id=2026#c23
Patchy the autobot says: LGTM.
Comment #2 on issue 2146 by lemzw...@gmail.com: Error: Illegal entry in
bfrange block in ToUnicode CMap
http://code.google.com/p/lilypond/issues/detail?id=2146
This is a bug directly in pdftex; I've just reported the problem as
http://tug.org/pipermail/pdftex/2011-December/008788.html
In
62 matches
Mail list logo
