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

"Knut Petersen" address@hidden writes:

@David: We all know that you were a valuable member of the lilypond
community for a long time. You were missed, and we are glad that you
are back in the pond although we wished you the best for the job you
tried. So don't feel too bad for jumping in late.

Currently I have little time as I need to debug my car. Some slack
joint or cable break hidden somewhere deep inside the wiring loom or
the electronics of the automated gear shift ;-(

Only a few comments: Detecting grace notes by the font size is an ugly
hack. I did not know how to detect grace notes in a clean
way. Everybody is invited to improve that portion of the code.

Look at the grace part of its moment? I think music columns have a
property "when" or so recording it.

So look at the grace time component of note->get_column ()->get_property
("when") or so?

Your proposed patch has one problem not found in the original patch:
It also adds extenders in addition to hyphens. So we probably also
need to listen to LyricHyphen events here.

Ah yes, of course. And of course I only sketched the changes in
extender-engraver.cc and not yet in lyric-extender.cc and the latter
will likely render some of the former nonsensical.

Also listen_lyric_event() needs to be listen_lyric() for current
master.

Ouch. I think I am currently at the limit of my concentration and need
to go into bed. Coughing and hurting all over.

I'll try to get back to it later today.

--
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 12:26 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 12:43:40 +0000