Updates:
Status: Fixed
Labels: fixed_2_13_31
Comment #9 on issue 1116 by Carl.D.Sorensen: Title not centered
http://code.google.com/p/lilypond/issues/detail?id=1116
Fixed by Alexander Kobel -- commit d3d40f3469eda2cb327bebbd392c1ce88b114394
Updates:
Status: Fixed
Labels: fixed_2_13_31
Comment #3 on issue 382 by Carl.D.Sorensen: misaligned nested \fill-lines
http://code.google.com/p/lilypond/issues/detail?id=382
Fixed by Alexander Kobel -- commit d3d40f3469eda2cb327bebbd392c1ce88b114394
Status: Accepted
Owner:
New issue 1234 by Carl.D.Sorensen: Fill-line should not use word space, but
should use springs-and-rods
http://code.google.com/p/lilypond/issues/detail?id=1234
Please DO NOT add issues directly to this tracker unless
you are certain that they correspond to our
Updates:
Labels: Type-Enhancement Priority-Low
Comment #1 on issue 1234 by Carl.D.Sorensen: Fill-line should not use word
space, but should use springs-and-rods
http://code.google.com/p/lilypond/issues/detail?id=1234
From Alexander's comments on Rietveld issue 1689041:
Comment #1 on issue 1231 by percival.music.ca: New clefs collide with
compressed multimeasure rests
http://code.google.com/p/lilypond/issues/detail?id=1231
When did this begin? Do we have any estimate on the last good version
number?
___
Updates:
Status: Verified
Comment #8 on issue 1203 by percival.music.ca: Page_turn_engraver refuses
to break at R1*12, crams notes and produces blank page in the middle of
score.
http://code.google.com/p/lilypond/issues/detail?id=1203
Reinhold reports that it works fine in his
Carl Sorensen schrieb:
On 8/23/10 3:28 PM, Marc Hohl m...@hohlart.de wrote:
Carl Sorensen schrieb:
[...]
It seems that we should use 0.48 times the *actual* staff space, rather than
the default staff space.
Um, after reading your answer twice - it should
Comment #2 on issue 1231 by brownian.box: New clefs collide with compressed
multimeasure rests
http://code.google.com/p/lilypond/issues/detail?id=1231
eluze says in that thread (answer to original report,
http://lists.gnu.org/archive/html/bug-lilypond/2010-08/msg00427.html):
Comment #23 on issue 989 by percival.music.ca: ensure that no information
about 2.12.3 features is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
I just did a LSR update, but didn't see them. Were they tagged with docs
and approved?
Comment #24 on issue 989 by bealingsplayfordnews: ensure that no
information about 2.12.3 features is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
http://lsr.dsi.unimi.it/LSR/Item?id=706
As stated a few times, it's not them, it's it.
Status: Accepted
Owner:
Labels: Type-Collision Priority-Critical Regression
New issue 1235 by PhilEHolmes: Accidental overlays stem
http://code.google.com/p/lilypond/issues/detail?id=1235
Nick Payne reports:
A beamed note with an accidental on a ledger line above the stave has the
Comment #25 on issue 989 by percival.music.ca: ensure that no information
about 2.12.3 features is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
Sorry for the pronoun misuse.
Apparently a snippet only makes it into our docs if it's tagged with docs
and at
Comment #14 on issue 1162 by percival.music.ca: website bibliography
http://code.google.com/p/lilypond/issues/detail?id=1162
I see accents on the website. What else do you want? I think it's working.
___
bug-lilypond mailing list
Status: Accepted
Owner:
Labels: Type-Documentation Priority-Low Maintainability Frog
New issue 1237 by percival.music.ca: not all doc files are @node @section
compliant
http://code.google.com/p/lilypond/issues/detail?id=1237
With few exceptions all .itely files should be untouched by
On 25/08/10 02:36, Phil Holmes wrote:
Nick Payne nick.pa...@internode.on.net wrote in message
news:4c72f469.4060...@internode.on.net...
I think I have reported this before - a beamed note with an accidental
on a ledger line above the stave has the accidental colliding with the
stem of the
15 matches
Mail list logo