Am 14.12.2016 um 10:43 schrieb Alexander Kobel: >> To allow automated creation of lyric extenders a helper function is >> needed > > ... that does exactly this, adding extenders everywhere. > > IMHO, the actual question to decide upon is: Do we want this to be > enabled by default? IIUC, the fact that extenders are not automatic is > a known shortcoming. NR 2.1.1 states under "Known issues and warnings": > "Extender lines under melismata are not created automatically; they > must be inserted manually with a double underscore." (see > http://lilypond.org/doc/v2.19/Documentation/notation/common-notation-for-vocal-music#multiple-notes-to-one-syllable) > > > With Knut's patch, this will mostly impact scores where extenders are > left out unintentionally. Still, it will be a burden for convert-ly > unless we have a global (or per lyric definition) \noAutomaticExtender > rule that is inserted by default. > > On the other hand, there is the chance to get rid of scores where > users don't add extenders simply because they are not aware of their > importance or the proper syntax.
My gut feeling says: Yes, this is an improvement and should be there by default. IIUC the reason why this has to be discussed is because that could change/break existing scores, right? If so, could you please think about an example where the patch would have a negative impact that can't reasonably be caught by convert-ly? Just because you two are much more into the topic, so that could help us others understand ... Urs _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
