|From:||Auto mailings of changes to Lily Issues|
|Subject:||[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Re: Ticket 4509 discussion|
|Date:||Thu, 26 Jan 2017 10:12:15 +0000|
For the time being,
\displayLilyMusic is already changed such that the
__ are not printed anymore. So from a user perspective, the issue is remedied.
I agree that the existence (and automatic generation) of ExtenderEvents is merely an implementation detail that allows to re-use the existing codebase with minimal changes. IIUC, the premature ending of extenders by null markups or
"" works by suppresing the automatic generation of ExtenderEvents, which I consider quite elegant. Still, I can see that this could be moved to LyricEvent handling instead.
Do you have an idea how difficult or invasive it is to change move the functionality to LyricEvent? (In other words: do you think it's worth the trouble?) I can imagine that, in the long run, it might be easier to maintain a variant where ExtenderEvents are buried.
[issues:#4509] Enhancement: automatically engrave lyric extenders
Created: Sat Jul 18, 2015 03:23 AM UTC by Anonymous
Last Updated: Thu Jan 26, 2017 07:38 AM UTC
Owner: Alexander Kobel
Originally created by: *anonymous
Originally created by: address@hidden
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.
Version 2.12 had this listed as a Known issue.
Sent from sourceforge.net because address@hidden 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 address@hidden https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
|[Prev in Thread]||Current Thread||[Next in Thread]|