If I use \displayLilyMusic on the lyrics expression in that LSR, I get
~~~
\lyrics \lyricsto "melody" { Aah-\tweak stencil #(lambda (grob)
(let* ((orig (ly:grob-original grob))
(siblings (ly:spanner-broken-into orig)))
(if (or (null? siblings)
(and (>= (length siblings) 2)
(eq? (car (last-pair siblings)) grob)))
(ly:stencil-combine-at-edge
(ly:lyric-extender::print grob)
X
RIGHT
(grob-interpret-markup grob text)
padding))))
__ Ooh-\tweak stencil #(lambda (grob)
(let* ((orig (ly:grob-original grob))
(siblings (ly:spanner-broken-into orig)))
(if (or (null? siblings)
(and (>= (length siblings) 2)
(eq? (car (last-pair siblings)) grob)))
(ly:stencil-combine-at-edge
(ly:lyric-extender::print grob)
X
RIGHT
(grob-interpret-markup grob text)
padding))))
__ }
~~~
Pasting that back into LilyPond gives (actually a syntax error because of
`\lyrics \lyricsto` first: we need to fix that independently):
~~~
lsr643.ly:52:3: warning: Ignoring the deprecated '__' token; see section 2.1
"Extenders and hyphens" of the notation reference!
__ Ooh-\tweak stencil #(lambda (grob)
lsr643.ly:52:3: error: wrong type for argument 3. Expecting music, found
#<unspecified>
__ Ooh-\tweak stencil #(lambda (grob)
lsr643.ly:64:3: warning: Ignoring the deprecated '__' token; see section 2.1
"Extenders and hyphens" of the notation reference!
__ }
lsr643.ly:64:3: error: wrong type for argument 3. Expecting music, found
#<unspecified>
__ }
~~~
So this does not look like the current state of the patch results in good
behavior: EXTENDER is being used in circumstances where `*unspecified*` is not
doing good things in the parser.
Granted, the previous `-\tweak ... __` also did not work since `-` does not
work in lyricsmode for introducing a post-event. But that's a different
problem of `\lyricsmode`.
---
** [issues:#4509] Enhancement: automatically engrave lyric extenders**
**Status:** Started
**Created:** Sat Jul 18, 2015 03:23 AM UTC by Anonymous
**Last Updated:** Thu Jan 26, 2017 07:38 AM UTC
**Owner:** Alexander Kobel
**Attachments:**
-
[Selection_005.png](https://sourceforge.net/p/testlilyissues/issues/4509/attachment/Selection_005.png)
(263.8 kB; image/png)
*Originally created by:* *anonymous
*Originally created by:*
[[email protected]](http://code.google.com/u/116549170756205086316/)
Actually, this is a content vs. presentation issue. The current approach has
lyric extenders ‘hardcoded’ within the lyricmode input, whereas often it
depends on layout whether I want an extender printed or not:
– In tight horizontal spacing, we might not need an extender, but when spacing
is stretched, it might become necessary. This can come through different
\(page/line\) breaking, parallel contexts present only in some editions \(part
vs. score\), Completion\_heads\_engraver \(mensural without
barlines/transcription with barlines\).
– Long syllables might not need an extender, where short syllables do.
– Often, all voices share the same text, but have extenders in different
places. If extenders need not be given explicitly, the lyricmode input code can
be reused much easier.
After all, the extenders don’t add any additional meaning, but only serve to
improve legibility in such cases where they do.
This would require:
– Recognising the end of a word by absence of a hyphen.
– Comparing printed length of the melisma notes vs. the syllable, likely after
line breaking. After all, extenders will never influence horizontal spacing.
They might, however, affect vertical spacing. \(unless we chose to omit \(or
shift\) the extender in that case?\)
– Personally, I think very short extenders shouldn’t be printed. There should
be some kind of threshold.
It’s also one of the usecases where a proper representation of a ‘lyric word’
would be helpful, along with [issue 2458](#2458).
Possibly related:
[issue 4098](#4098)
[Version
2.12](http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Aligning-lyrics-to-a-melody#Multiple-notes-to-one-syllable)
had this listed as a Known issue.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/testlilyissues/issues/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is
a mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Testlilyissues-auto mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
