Issue 578: Regression: Completion heads mess up lyrics
http://code.google.com/p/lilypond/issues/detail?id=578
Comment #1 by arvidgr:
A small, additional observation:
With 2.11.11 (the last version that doesn't flip around syllables in
this case),
lyric extenders are sometimes (but not always) s
Issue 578: Regression: Completion heads mess up lyrics
http://code.google.com/p/lilypond/issues/detail?id=578
Comment #2 by arvidgr:
I've also attached preview images (this time in normal resolution) of
the 2.11.41
output (completely messed up) as well as output from 2.8.8 (OK; some
minor and
Valentin Villenave wrote:
2008/3/10, Trevor Daniels <[EMAIL PROTECTED]>:
Under 2.11.42 the fonts are cached in C:\Documents and
Settings\[username]\.lilypond-fonts.cache-2. This also
contains 2 small and one large (682 KB) files, but when
LilyPond compiles it changes just the large fi
For the record, the recommended procedure in version 2.10 and later is
lilypond-book --pdf -o out ...
cd out
pdflatex ...
I don't remember if this works also in 2.8.
/Mats
Kevin Donnelly wrote:
The only docs I can find on lilypond-book
(http://www.lilypond.org/doc/v2.1/Documentation/user/ou
For the record, a possible workaround until the bug has been fixed, is to
explicitly create a Voice context:
\new Staff \new Voice {
\relative c'' {
\times 2/3 { \acciaccatura d8 c8 b c }
}
}
/Mats
[EMAIL PROTECTED] wrote:
Issue 587: Segfault: \acciaccatura inside \times when using \ne
2008/3/11, Mats Bengtsson <[EMAIL PROTECTED]>:
> If this problem has appeared also on XP, then it's a regression bug.
Should I just add a comment to issue #545, or open a new issue?
Cheers,
Valentin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
Yes, definitely a regression. I've gone back to using
2.11.34 which does not suffer this bug, as most of my
documentation work is fiddling with tiny snippets, and a 1
minute delay every time I make a change makes it impossible
to work.
Trevor
> -Original Message-
> From: Mats Bengtsson
Issue 588: Regression: LilyPond excessively slow on Windows XP
http://code.google.com/p/lilypond/issues/detail?id=588
New issue report by v.villenave:
Lilypond 2.11.42 takes around a minute to parse and render a minimal .ly
file on Windows XP, whereas it used to take only a few seconds with 2.11.
Issue 545: LilyPond is excessively slow on Windows Vista
http://code.google.com/p/lilypond/issues/detail?id=545
Comment #2 by v.villenave:
This issue seems to be reproduced on Windows XP as of version 2.11.42
(see issue #588)
--
You received this message because you are listed in the owner
o
2008/3/11, Trevor Daniels <[EMAIL PROTECTED]>:
>
> Yes, definitely a regression. I've gone back to using
> 2.11.34 which does not suffer this bug, as most of my
> documentation work is fiddling with tiny snippets, and a 1
> minute delay every time I make a change makes it impossible
> to work
yep. please fix
2008/3/9, Stan Sanderson <[EMAIL PROTECTED]>:
> 2.11.42 regressions: grace-stem-length.ly
>
> problem: clarity in text
>
> current: "...even if that would lead to beam quanting program."
>
> Should "program" be "problems"?
>
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://ww
2008/3/9, Stan Sanderson <[EMAIL PROTECTED]>:
> 2.11.42 regressions: markup-user.ly
>
> problem: clarity in text
>
> current: "Own markup commands may be defined ..."
>
> suggest: "Markup commands may be defined..."
> (or) "Unique markup commands may be defined..."
> (or) "Special markup comma
2008/3/9, Stan Sanderson <[EMAIL PROTECTED]>:
> 2.11.42 regressions: property-nested-reverted.ly
>
> problem: reversion not complete- is there missing code?
No, I think the objective is to show that you can revert individual
nested properties, without affecting others. The implementation makes
th
2008/3/9, Stan Sanderson <[EMAIL PROTECTED]>:
> 2.11.42 regressions: system-start-bracket.ly
>
> problem (?): confusion in text
>
> The text reads, "The piano brace should be shifted horizontally if it
> is enclosed in a bracket."
>
> I am confused by the "...if...", since the piano brace itsel
Sorry for the vague subject line. Hopefully the picture helps...
\version "2.11.41"
\paper {
ragged-right = ##f
}
<<
{g'4 s2. g'4 s2.} \\
{g'2 s2 g'2. s4}
>>
When the same note appears simultaneously in two voices and the
noteheads are different, they should appear right
Given the right note spacing and tie directions, ties can collide with
rhythmic augmentation dots. In this example, if the line width is
reduced to 52 LilyPond avoids the collision. Increasing the line width
reduces the severity of the collision by reducing the initial slope of
the tie. (Bug found
I wrote out an organ accompaniment in LilyPond (to get it onto 4 pages
instead of 13), and it illustrates this situation very well. In eight
separate places there was a major or minor second between a dotted and
undotted note, with the dotted note on a staff space - exactly the
condition that produ
17 matches
Mail list logo
