Dear LilyPonders,

by default LilyPond hides the hyphen after a line break.
Is it possible to make it always visible?

There is a regtest file to check this behavior: lyric-hyphen-break.ly.
I'm using it as a test file.

Hyphens are spanners, right?
In the doc I found this hint:

"The visibility of spanners which end on the first note following a line
break is controlled by the after-line-breaking callback
ly:spanner::kill-zero-spanned-time.

For objects such as glissandos and hairpins, the default behaviour is to
hide the spanner after a break; disabling the callback will allow the
left-broken span to be shown. "

Source:
http://lilypond.org/doc/v2.14/Documentation/snippets/expressive-marks#controlling-spanner-visibility-after-a-line-break
 

I played with \override LyricHyphen #'after-line-breaking (see file
attached), but nothing changed in the output.

Actually, I'm not directly interested in this issue.  I'm just trying to
help Luca (reviewer of Italian documentation), who asked a couple of
times about this and never got a reply:
https://lists.gnu.org/archive/html/lilypond-user/2010-02/msg00330.html 
https://lists.gnu.org/archive/html/lilypond-user/2011-04/msg00470.html 

Thanks in advance for your help,
Federico
\version "2.14.1"

\header {

  texidoc = "Hyphens are printed at the beginning of the line only when
they go past the first note. "

}


\layout   {
  indent = 0.0 \cm
  line-width = 3.4 \cm

  \context {
    \Staff \remove "Time_signature_engraver"
  }
  \context {
	  \Lyrics
		\override LyricHyphen #'minimum-distance = #1.5
		\override LyricHyphen #'after-line-breaking = ##f % it doesn't work neither ##t or ##f
  }
}



<<
  \new Voice \relative c'' {
    \time 1/4
		c16[ c c  c]
		\time 1/4
		c16[ c c c]
    \time 1/4
    r c16[ c c]
  } \addlyrics {
    bla16 -- bla -- bla -- bla --
    bla -- bla -- bla -- bla8 --
    bla16 -- bla -- bla 
  }
>>
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to