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

"David Kastrup" address@hidden writes:

"Knut Petersen" address@hidden writes:

This is a new version of the autoextender patch, based on current
master. Documentation unchanged.

There is a new boolean property no-auto-extenders. If set true it only
allows forced extenders.
The double-underscore Extender token is revived and generates a forced
extender. The result should be identical to the old behaviour.

If no-auto-extenders is true, extenders are automatically
generated. Extender tokens are interpreted as forced extenders.

Have a look at the code whenever you feel better.

Thanks for pitching in here. I just went through the mail for the day
and I am afraid that I need to get back to bed right now as I am really
in lousy shape (sinuses hurting like anything and I am not even stuffed
up all that much). Let's hope that I am in better shape tomorrow.

Ah, but one thing I thought I should mention: it occured to me if we
made minimum-width obey its standard-behavior known from elsewhere (ok,
elsewhere one needs to set some spacing-rods property in addition but
probably noone will notice), we would require no forced-width in
addition.

And the particular use case of Trevor, namely setting it to zero, should
work out just the same as before, shouldn't it?

--
David Kastrup

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

Status: Started
Created: Sat Jul 18, 2015 03:23 AM UTC by Anonymous
Last Updated: Tue Jan 31, 2017 06:58 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:	Wed, 01 Feb 2017 14:56:26 +0000