Updates:
Owner: colinpkc...@gmail.com
Comment #5 on issue 1762 by pkx1...@gmail.com: mutual cues fail
http://code.google.com/p/lilypond/issues/detail?id=1762
(No comment was entered for this change.)
___
bug-lilypond mailing list
Comment #14 on issue 1735 by pkx1...@gmail.com: modifying default behaviour
of tremolo slashes
http://code.google.com/p/lilypond/issues/detail?id=1735
Will these affect cross-staff tremolos and repeat tremolos I don't see any
examples in the ly file of those.
Updates:
Labels: -Patch-review Patch-needs_work
Comment #30 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/26 Trevor Daniels t.dani...@treda.co.uk
The G clef font was changed 18 months or so
Hi,
there is a problem with comments in the tracker. At least 2 comments
didn't make it to the changing G clef issue page:
- Trevor's comment from July 26th, containing sentence The G clef
font was changed 18 months or so ago by Carl without all this fuss
- Carls comment, perhaps from July 25th,
Am 26.07.2011 21:30, schrieb Till Paala:
Hi,
finally corrected in lilypond/translation,
When will this be visible? When displaying the German version of.
http://www.lilypond.org, I still get the wrong links (although the link
text is now different for the new version 2.15.6).
Best
Urs
Janek
)-Original Message-
)From: lilypond-devel-bounces+james.lowe=datacore@gnu.org
)[mailto:lilypond-devel-bounces+james.lowe=datacore@gnu.org] On
)Behalf Of Janek Warchol
)Sent: 27 July 2011 09:55
)To: lilypond-de...@gnu.org; Lilypond Bugreports
)Subject: some comments do not
On Jul 27, 2011, at 12:22 PM, lilyp...@googlecode.com wrote:
Updates:
Owner: ---
Labels: -Priority-High -Patch-needs_work Priority-Medium Patch-abandoned
Comment #6 on issue 36 by pkx1...@gmail.com: collision cresc and kneed beams
Comment #3 on issue 1780 by d...@gnu.org: Scheme format functions with no
destination parameter cause deprecation warnings in Guile V2
http://code.google.com/p/lilypond/issues/detail?id=1780
Uh, stupid question. Right now I discovered in lily.scm
(define-public (ergonomic-simple-format
Chris Snyder csny...@adoromusicpub.com wrote in message
news:4e2eeba7.1030...@adoromusicpub.com...
When LilyPond is called with the -danti-alias-factor option (for PNG
output), the scaling stage fails if the filename contains spaces. For
example:
For the record, Colin added this as
Updates:
Labels: -Patch-needs_work Patch-new
Comment #8 on issue 620 by pkx1...@gmail.com: It should be possible to
specify more specific spanner bounds.
http://code.google.com/p/lilypond/issues/detail?id=620
On 2011/07/27 16:45:02, MikeSol wrote:
A new version of this patch is up
Updates:
Owner: mts...@gmail.com
Labels: -Patch-new Patch-review
Comment #9 on issue 620 by pkx1...@gmail.com: It should be possible to
specify more specific spanner bounds.
http://code.google.com/p/lilypond/issues/detail?id=620
Passes make and reg tests.
Updates:
Labels: -Patch-new Patch-review
Comment #17 on issue 163 by pkx1...@gmail.com: huge (ugly) slur (both
phrasing and normal)
http://code.google.com/p/lilypond/issues/detail?id=163
Passes Make - new reg test differences attached
Attachments:
Screenshot1.png 28.3 KB
Status: Accepted
Owner: mts...@gmail.com
Labels: Type-Enhancement Priority-Medium Patch-review
New issue 1784 by pkx1...@gmail.com: Adds epsilon to Bezier range
calculations
http://code.google.com/p/lilypond/issues/detail?id=1784
http://codereview.appspot.com/4820048/
(no idea what this
Comment #18 on issue 163 by mts...@gmail.com: huge (ugly) slur (both
phrasing and normal)
http://code.google.com/p/lilypond/issues/detail?id=163
Thanks, James! Your regtest run was a big help, as all of the results you
found did not show up when I ran them (before my last update, which
Comment #1 on issue 1784 by mts...@gmail.com: Adds epsilon to Bezier range
calculations
http://code.google.com/p/lilypond/issues/detail?id=1784
The issue is that LilyPond has roundoff error that creeps into slur layout
decisions. This patch tries to patch up that roundoff error.
Updates:
Labels: -Patch-review Patch-needs_work
Comment #19 on issue 163 by pkx1...@gmail.com: huge (ugly) slur (both
phrasing and normal)
http://code.google.com/p/lilypond/issues/detail?id=163
(No comment was entered for this change.)
Comment #7 on issue 36 by pkx1...@gmail.com: collision cresc and kneed beams
http://code.google.com/p/lilypond/issues/detail?id=36
Because there are numerous ways to fix this problem, and because no one way
is objectively better, and because all ways are doable via overrides and
short
Updates:
Summary: collision cresc and kneed beams -
Owner: pkx1...@gmail.com
Labels: -Type-Collision -Patch-abandoned Type-Documentation
Patch-needs_work
Comment #8 on issue 36 by pkx1...@gmail.com: collision cresc and kneed
beams -
Updates:
Labels: -Patch-needs_work Patch-review
Comment #31 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've looked on bug- archives and i see that i've missed a lot of
discussion! About 10
Updates:
Status: Fixed
Labels: -Patch-needs_work fixed2_14_0
Comment #9 on issue 36 by k-ohara5...@oco.net: collision cresc and kneed
beams -
http://code.google.com/p/lilypond/issues/detail?id=36
Fixed with commit ad45306
Comment #3 on issue 1779 by k-ohara5...@oco.net: accidentaled notes too far
from the barline
http://code.google.com/p/lilypond/issues/detail?id=1779
The change is, whenever the first note in a measure has a 'decoration' on
the left, place the main note-column as close as possible to where
Updates:
Labels: -Patch-needs_work Patch-review
Comment #4 on issue 1779 by k-ohara5...@oco.net: accidentaled notes too far
from the barline
http://code.google.com/p/lilypond/issues/detail?id=1779
(No comment was entered for this change.)
Status: Accepted
Owner:
Labels: Type-Defect Priority-Medium Patch-review
New 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
Things like Clefs and KeySignatures have a list of parameters
Updates:
Status: Fixed
Comment #7 on issue 1768 by colinpkc...@gmail.com: Tremoli can collide with
flags in tight spacing situations.
http://code.google.com/p/lilypond/issues/detail?id=1768
Per Mike Solomon:
Pushed as def419dfd961fee6fd0bf49321ae130143b618af.
Cheers,
MS
Comment #20 on issue 163 by hanw...@gmail.com: huge (ugly) slur (both
phrasing and normal)
http://code.google.com/p/lilypond/issues/detail?id=163
Mike,
maybe you can dig into the different examples a bit more? I think there are
multiple independent issues.
\paper {
ragged-right = ##f
The automatic positioning of Slurs and PhrasingSlurs that both either
start or finish on the same note is not very good. See below. Commercial
scores that I have where this happens position the two slurs so that
they don't intersect or touch, as in the second bar where the
PhrasingSlur has
Comment #7 on issue 1776 by lemniska...@gmail.com: Doc: NR - Polymetric
Notation \compoundMeter isn't documented
http://code.google.com/p/lilypond/issues/detail?id=1776
I suggest this:
\relative c' {
\compoundMeter #'(2 2 2 8)
\repeat unfold 6 c8 \repeat unfold 12 c16
}
\relative c' {
Comment #8 on issue 1776 by lemniska...@gmail.com: Doc: NR - Polymetric
Notation \compoundMeter isn't documented
http://code.google.com/p/lilypond/issues/detail?id=1776
Ah, i should learn to read :) Yes, the description from the regtest says
this: #'((3 2 8)) is how LilyPond likes it, but
Comment #3 on issue 1785 by lemniska...@gmail.com: Compressible space
before the first note of a line ?
http://code.google.com/p/lilypond/issues/detail?id=1785
Nice catch!
___
bug-lilypond mailing list
bug-lilypond@gnu.org
29 matches
Mail list logo
