lilypond-user
[Top][All Lists]
Advanced

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

Re: Text centralized above a TextSpan


From: Simon Albrecht
Subject: Re: Text centralized above a TextSpan
Date: Tue, 22 Sep 2015 22:23:07 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0

On 22.09.2015 22:03, Trevor Daniels wrote:
David Nalesnik wrote Monday, September 21, 2015 5:13 PM

I'm attaching a rewrite of the code which allows an easy mix of
markups/strings and interprets hyphens as connectors.
Now there's no need for a TextSpanner.connectors property.
... and hardly any need for the text-spanner-line-count, as it's easy
to split up the text by system (since manual breaks are needed
anyway to control the placement) like this:

music = \relative {
%  \override TextSpanner.text-spanner-line-count = #'(8 5)
   \addTextSpannerText \lyricmode {
     \markup \fontsize #1 \upright \smallCaps Abe:
     "Say" "this" "over" "measures" "one" "and" "two"
   }
   <>\startTextSpan
   a'4 a a a
   a4 a a a
   \stopTextSpan
   \break
   \addTextSpannerText \lyricmode {
     "and" "this" "over" "measure" "three"
   }
   <>\startTextSpan
   a4 a a a
   \stopTextSpan
}

I don’t quite understand your reasoning here; in my eyes it’s better to have only one TextSpanner and override its text-spanner-line-count than to split up the spanners. David N.s examples show the use of this in conjunction with manual breaks, which works fine.

A function to split text at white space rather than having to surround
each word with quotes would make this quite useable, I think.

The quotes are unnecessary anyway (except if we want to use \markup): we are in lyricmode. They only stayed there as an oversight.

Certainly better than the way I did it in the NR.

One problem remains: the text overlaps if there is not enough room,

A known limitation: note spacing stays as-is.

Yours, Simon



reply via email to

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