[Lilypond-auto] Issue 4509 in lilypond: Enhancement: automatically engrave lyric extenders

[lilypond]

Status: Accepted
Owner: ----
Labels: Type-Enhancement

New issue 4509 by address@hidden: Enhancement: automatically engrave  
lyric extenders
https://code.google.com/p/lilypond/issues/detail?id=4509

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.

Possibly related:
issue 4098

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.

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings