|From:||Auto mailings of changes to Lily Issues|
|Subject:||[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Ticket 4509 discussion|
|Date:||Thu, 12 Jan 2017 16:12:16 +0000|
Dan's point is certainly valid, but I'm unsure how to proceed about it.
There is one reasonable argument for having
__ ignored instead of invalid, namely backwards compatibility of the lyrics with older versions (in particular, to 2.18.x). I don't care enough personally to oppose either approach. If noone cares (read: nobody else utters a complaint) and this is a show-stopper for integration, I guess Knut will agree to make
Depending on the policy for the state of a patch before acceptance, this still needs_work w.r.t. the regtests and code examples in the docs anyway (see my comment #11 on Rietveld). That's something I can do without Knut's support. Should I prepare this already (I think that it will clutter the diff on Rietveld, though...)?
[issues:#4509] Enhancement: automatically engrave lyric extenders
Created: Sat Jul 18, 2015 03:23 AM UTC by Anonymous
Last Updated: Thu Jan 12, 2017 03:54 PM 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.
------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi
_______________________________________________ Testlilyissues-auto mailing list address@hidden https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
|[Prev in Thread]||Current Thread||[Next in Thread]|