[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Re: Ticket 450

Argh, Ctrl-W ate my posting...

AFAICS, with your patch the LyricExtender engraving routines are called irregardless of the existence of an ExtenderEvent, right? So an ExtenderEvent doesn't have to appear even internally anymore? Sounds like the cleanest approach to me.

Now, please don't get me wrong on the following. I appreciate that you participate in that issue, and I value your insight on both the architectural and the UI side a lot. I just want to make sure that you are aware of the thoughts we spent on that issue around the turn of the year, and save everybody time and discussions.

I'm somewhat shivering to hear the you want to "get along without no-extender and force-extender". Are you talking about the internals and/or the UI here?
no-extender is important in some cases, e.g. to replicate sources without extenders or for special-purpose lyrics (e.g., I'm thinking of functional analysis symbols). 'collapse-length = #+inf.0 should be functionally equivalent, but some people expressed the (reasonable, IMHO) desire that collapse-length should be decoupled from an on-/off-toggle.
Forced extenders are required for some manual tweaks or, again, special purposes such as lone notes before volta repeats, where an extender into the second repeat bracket needs to be indicated. (BTW, there have been wishes that the mutually exclusive collapse-length and forced-length are not merged into one property.)

Starting from scratch, I'd opt for translating the __ token to forced extenders. However, a reinterpretation of __ was not well-received. Also, ignoring and deprecating __ for a while leaves lyrics (with manual extenders) compatible between 2.19.55+some and earlier (in particular, 2.18.x) versions.

Again, all these points have been discussed in a heap of mails on -devel end of 2016. Just to make sure we are on the same page.

[issues:#4509] Enhancement: automatically engrave lyric extenders

Status: Started
Created: Sat Jul 18, 2015 03:23 AM UTC by Anonymous
Last Updated: Mon Jan 30, 2017 10:31 PM UTC
Owner: Alexander Kobel
Attachments:

Selection_005.png (263.8 kB; image/png)

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.

Possibly related:
issue 4098

Version 2.12 had this listed as a Known issue.

https://codereview.appspot.com/313240043 )

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.

From:	Auto mailings of changes to Lily Issues
Subject:	[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Re: Ticket 4509 discussion
Date:	Tue, 31 Jan 2017 10:03:18 +0000