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

"Alexander Kobel" address@hidden writes:

[...] if we made minimum-width obey its standard-behavior known from
elsewhere [...]
[...] Implementing a proper minimum width would help to solve some
old issues ... [...]

You are talking about a minimum-width that affects the horizontal
spacing? I can't immediately see great benefits from it, but also no
shortcomings. I agree that minimum-width = #0 combined with
collapse-width > 0 should satisfy most requirements.

Sorry, still out of commission. Today was the first day where the
temperature dipped for half a degree temporarily but I'm still basically
knocked out. Fourth day in a row: way more than I am used to.

Back in bed in a few minutes, sorry for not keeping up with the mess I
stir.

--
David Kastrup

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

Status: Started
Created: Sat Jul 18, 2015 03:23 AM UTC by Anonymous
Last Updated: Thu Feb 02, 2017 10:36 AM 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:	Thu, 02 Feb 2017 21:02:46 +0000