[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Ticket 4509 di

From:

Auto mailings of changes to Lily Issues

Subject:

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Ticket 4509 discussion

Date:

Thu, 05 Jan 2017 15:02:14 +0000

Hi all.

The visual diffs are expected and okay.
I suggest to replace \skip2 by "" in input/regression/page-spacing-nonstaff-lines-independent.ly, though.

The stderr diffs are debatable.
For display-lily-tests.ly, the output is expected and could be marked "NOT A BUG", but it isn't pretty. Since there is no need to enter __ manually anymore (and it is ignored by the parser), \displayLilyMusic should not emit it either.
typography-demo.ly points to an actual oversight in the extender handling of the patch set: the broken extenders from the first to second system seem not to be subject to collapse-length. The warning stems from the fact that the second part of broken extender before "Licht!" has no room available. (Note that it is not related to the fact that there is an acciaccatura there.)

On a more or less unrelated note, it seems that we have no way to stop an extender before an acciaccatura or grace note. That's not a new problem, as far as I can see, but might be slighly more annoying with automatic extenders:

\fixed c'' { c4 \acciaccatura { e16 d } c4 4 \appoggiatura { d8 } c4 }
\addlyrics { A B C D }

Attachments:

test.preview.png (6.5 kB; image/png)

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

Status: Started
Created: Sat Jul 18, 2015 03:23 AM UTC by Anonymous
Last Updated: Mon Jan 02, 2017 04:08 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.

Possibly related:
issue 4098

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