lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 2.15.22 Regtests


From: Phil Holmes
Subject: Re: 2.15.22 Regtests
Date: Sun, 18 Dec 2011 16:31:09 -0000

----- Original Message ----- From: "David Kastrup" <address@hidden>
To: <address@hidden>
Cc: <address@hidden>
Sent: Sunday, December 18, 2011 3:49 PM
Subject: Re: 2.15.22 Regtests


"address@hidden" <address@hidden> writes:

On Dec 18, 2011, at 4:18 PM, Kieren MacMillan wrote:

Hello all,

Uh, in particular the "wahh" looks totally horrible. It is one thing to go over the bar line. It is another to run into the next name without a
modicum of padding.

Agreed — I actually prefer the ability (i.e., option) for the chord
name to hang over the barline, but padding is definitely required
before the next chord name.

There are a few ways to get the padding.
You can add an extra-spacing-width of #'(0 . 0.3).
You can also add the Bar_line_engraver to the ChordNames context if
you don't like the bar-line hangover and then make the bar-line
Y-extent '(0 . 0) and the BarLine transparent.

Can we agree that Lilypond's defaults should not look awful?  It is nice
to be able to tweak the output in case of unforeseeable emergencies, but
I think we can more or less agree that the use case in the regtest is
nothing out of the ordinary.

--
David Kastrup


Took me a while, but I did get that agreed last year, during the discussion about \override PaperColumn #'keep-inside-line. It was agreed that good-looking should be the default, over-ridden if necessary. Based on the discussions to date, I think this should be a regression bug. I've added it as http://code.google.com/p/lilypond/issues/detail?id=2122.

--
Phil Holmes





reply via email to

[Prev in Thread] Current Thread [Next in Thread]