Comment #4 on issue 890 by jameseli...@googlemail.com: Chord names collide
with staff on second system when lyrics are present
http://code.google.com/p/lilypond/issues/detail?id=890
No worries. Also, on some music that I have, with multiple verses and
different kinds
of chords, I don't get
Comment #3 on issue 890 by jameseli...@googlemail.com: Chord names collide
with staff on second system when lyrics are present
http://code.google.com/p/lilypond/issues/detail?id=890
No worries. Also, on some music that I have, with multiple verses and
different kinds
of chords, I don't get
Updates:
Summary: Chord names collide with staff on second system when lyrics are
present
Labels: Type-Collision
Comment #2 on issue 890 by Carl.D.Sorensen: Chord names collide with staff
on second system when lyrics are present
http://code.google.com/p/lilypond/issues/detail?id=89
On Sat, Oct 31, 2009 at 11:42 AM, Graham Percival
wrote:
> On Fri, Oct 30, 2009 at 4:32 PM, Graham Percival
> wrote:
>> On Wed, Oct 28, 2009 at 03:46:00PM -0700, Patrick McCarty wrote:
>>> Maybe we could try bumping Freetype and Fontconfig to the latest
>>> releases? IIRC, GUB is using an old ve
On 31.10.2009, at 19:34, Laura Conrad wrote:
No, but the attached is the simplest example I can figure out with the
key signature and the notehead specification in a separate block from
the notes. (In real life, they would be in a separate file.) And it
does exhibit the bug.
Can someone sugge
Comment #1 on issue 890 by jameseli...@googlemail.com: Chords and Lyrics
under 2.13.6
http://code.google.com/p/lilypond/issues/detail?id=890
(No comment was entered for this change.)
Attachments:
chords and lyrics.png 12.8 KB
--
You received this message because you are listed in t
Status: Accepted
Owner: jameseli...@googlemail.com
Labels: Priority-Regression
New issue 890 by jameseli...@googlemail.com: Chords and Lyrics under 2.13.6
http://code.google.com/p/lilypond/issues/detail?id=890
Chords and lyrics don't mix well in 2.13.6
\paper { indent = 0\mm }
\version "2.13.6
>Hi,
I've played a little bit with lilypond, minimal sample is below.
I guess that the problem is somehow related to stemDown.
- the minimal sample is wrongly rendered because of b4 (stemDown)
- change b4 -> to a4, the sample is rendered well (stemUp)
- add \stemDown to a4 -> rendering problem
-
On Fri, Oct 30, 2009 at 4:32 PM, Graham Percival
wrote:
> On Wed, Oct 28, 2009 at 03:46:00PM -0700, Patrick McCarty wrote:
>> Maybe we could try bumping Freetype and Fontconfig to the latest
>> releases? IIRC, GUB is using an old version of Freetype.
>
> This'll be more complicated than I origina
> "Valentin" == Valentin Villenave writes:
>> The attached lilypond file, which I would expect to produce baroque
>> noteheads (i.e., square notes for the breves) produces whole notes
>> with bars around them for breves.
Valentin> Hm. I can't understand exactly what's happen
2009/10/30 Trevor Daniels :
> I honestly can't remember whether I looked at it further or not.
> But as I don't seem to have posted any more about it I guess
> I didn't. Or maybe I did but discovered nothing more. We were
> not sure why this extra space had been added, so were reluctant
> to rem
On 31.10.2009, at 08:58, Karai Csaba wrote:
Hi,
It seems, that it would take too much time for me to understand how
lilypond +
SCM works, so I can't send a patch how to fix it.
I've compared 2.13.3 and 2.13.4, but I couldn't figure out where
the problem was.
Would it be possible to reo
Hi,
It seems, that it would take too much time for me to understand how lilypond +
SCM works, so I can't send a patch how to fix it.
I've compared 2.13.3 and 2.13.4, but I couldn't figure out where the problem
was.
Would it be possible to reopen 873 not to forget this bug?
Thanks,
Csaba
13 matches
Mail list logo
