[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Chordname collisions
From: |
Jean-Alexis Montignies |
Subject: |
Re: Chordname collisions |
Date: |
Sun, 9 Sep 2012 21:48:44 +0200 |
Hi
Doesn't look like a regression (at least it's there since 2.12), see bug 1700.
They are some work around proposal.
I would recommend that if you're annoyed by this issue, you star it in google
code.
Greetings,
Jean-Alexis
On 9 sept. 2012, at 12:59, Phil Holmes <address@hidden> wrote:
> ----- Original Message ----- From: "Jim Long" <address@hidden>
> To: <address@hidden>
> Sent: Sunday, September 09, 2012 9:15 AM
> Subject: Chordname collisions
>
>
>> I'm having the problem illustrated in the attachment, the
>> collision of the markup for the second and third chords in the
>> ChordNames staff. If this is a bug, is there a simple workaround
>> I can use until the collision issue is addressed?
>>
>> Thank you!
>>
>> Jim
>
>
> Don't know about a workaround, but this looks like a regression bug,
> introduced between 2.15.21 and 2.15.23.
>
> --
> Phil Holmes
>
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-user