On Wed, Feb 15, 2012 at 3:25 PM, Reinhold Kainhofer
<[email protected]> wrote:
> On 06/02/2012 18:50, [email protected] wrote:
>> In my opinion, these times are too high to justify the gain
>> that one gets from using fine-tuned vertical skylines.
>
> Agreed.
I strongly disagree. The gain is enormous - how much time would it
take to correct all these issues by hand? (not mentioning that manual
corrections will break every time layout changes!)
>> In the final version of the patch, I'll limit them to
>> slurs, ties, tuplet-brackets, volta repeats, and treble clefs.
>
> What about hairpins? They are one of the main problem areas in my scores
> (and they are even worse in a piano staff).
what about beams?
{ g''16[ d'' a' e'] }
\addlyrics { la }
And while we're at it, what about rotated trillspans? ;)
LilyPond's greatest strength is beautiful /automated engraving/, even
for the people who don't have specialistic knowledge about engraving.
If we turn this feature off for some objects, it will mean that many
users will have sub-optimal scores.
I have one thought concerning computation time.
>From what i see, currently every stencil's skyline is created from 10
boxes. That's a good amount for medium-sized slur, but it's not
necessary for a short (~5 ss long) tie, or a clef. And it's
definitely overkill for an accidental; on the other hand, full-line
phrasing slur should have much more boxes.
Maybe it would be feasible to have varying amount of boxes for
different objects? In it's simplest form, the number of boxes could
depend on object's width.
cheers,
Janek
_______________________________________________
lilypond-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
