----- Original Message -----
From: "David Kastrup" <[email protected]>
To: <[email protected]>
Cc: <[email protected]>
Sent: Sunday, December 18, 2011 3:49 PM
Subject: Re: 2.15.22 Regtests
"[email protected]" <[email protected]> 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
_______________________________________________
lilypond-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
