[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
limitation with ignoreMelismata?
From: |
Erik Sandberg |
Subject: |
limitation with ignoreMelismata? |
Date: |
Fri, 30 Jan 2004 23:32:04 +0100 |
User-agent: |
KMail/1.5.4 |
Hi,
I'm afraid that the combination ignoreMelismata + melisma[End] is still not
enough. Consider the following:
\version "2.1.16"
\score {
<<
\notes {c4 c c c}
\context LyricsVoice=A \lyrics { foo2. __ bar4 }
\context LyricsVoice=B \lyrics { foo2 -- baz4 bar }
\context LyricsVoice=C \lyrics { foo -- baz4 -- baaz bar }
>>
}
I can't see how I would produce the same output using \lyricsto.
(An analogous situation does occur in a real piece that I am typesetting)
One way of making it possible would be to add a new kind of empty lyric, which
\lyricsto would kill and extend the duration of the preceding note to fill
the space.
i.e., if the notation would be K, the above would become
\notes {c \melisma c c \melismaEnd c }
{ foo __ bar }
{ \property LyricsVoice . ignoreMelismata = ##t foo -- K baz bar }
{ \property LyricsVoice . ignoreMelismata = ##t foo -- baz -- baaz bar }
(I see now that it is not very clean; my brain hurts when I think about cases
like "foo -- K __ baz")
And by the way this shows a bug, too (?): No extender line is produced in the
first stanza of the above piece. This is apparently because of the baz4 in
voice C, but I don't understand why this would make any sense.
As a small bonus, I found a manual typo:
html/input/regression/out-www/collated-files.html#lyric-combine-new.ly
says "With the newaddlyrics mechanism, ...". "newaddlyrics" should be
"lyricsto", right?
thanks,
Erik
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- limitation with ignoreMelismata?,
Erik Sandberg <=