Lyrics don't overlap stave elements

See my comments in both #5261: Lyrics for melismas should not respace notes if there is room before next syllable and #33246: Hyphenated melisma requires too much space. I can make this happen via manual override; it isn't going to be good to do automatically because it could conceivably cause problems (really long syllables running completey off the page).

Here's my code:

https://github.com/musescore/MuseScore/pull/1330

should be fixed since ab15653

No, I did not implement this particular optimization, because there would be no way to automatically prevent overlap. The original example will still produce the layout shown as "actual".

With the recent improvements to lyric positioning, perhaps it's time to revisit this feature?

Fixed in branch master, commit 962076fa18

fix #22696 Lyrics dont overlap stave elements

I doubt this was the Chen Lung's intention:

This fix has good results for the initial system, but not on subsequent systems.

Interesting, it seems it is the presence of a time signature that causes the margin to be obeyed for the first system but not for others. Try adding a time signature to any subseuent system and the marign is then respected. A key signature has the same effect.

Actually, FWIW, I do wonder about what the desired behavior would be here. Currently for systems other than the first, if you don't want the lyric to extend into the margin, you can manually adjust it. But for the first system, if you *do* want it to extend into the margin, there is no way to make that happen. Moving the lyric to the left just moves it relative to the note it is attached to, moving the note to the right to keep the lyric out of the margin.

In the end, it's probably not a hugely important question as it would probably be relatively uncommon (which is why this subject almost never comes up).

Perhaps a bigger issue: the I don't remember how it was before this change, but currently, a very long syllable at the beginning of a measure will collide with a syllable in a previous measure:

It's the same problem we have with chord symbols (in 2.0.3 as well as current master) - the automatic spacing works *within* a measure only, not *between* measure.

I believe negative and positive leading space for the segment are manual adjustments that solve each problem, respectively. I've opened up some piano/vocal scores with this fix and they look a lot better out of the box than 2.0 because it is less likely that long syllables respace notes, particularly at the beginning of a measure (in 2.0, this was almost guaranteed to happen if a syllable immediately after a barline had more than three letters in it).

Also, it's worth mentioning is that a long syllable under beamed quaver (etc...) overlap with next syllable:

(lyrics: Al- lelele- - lu- ja)

Windows 7-64, ea88600

We should decide what to do with this report since it is not good to have it forever open/needs info :)
The case has been reproduced on current master.

If it is reproduced in current master, there is no need to for info...

It is, indeed. But according to the discussion it could be by design.

Overlaps by design???

As I understand, the initial topic is about lyrics overlapping the space under the clef and key signatures. Overlapping syllables is due to the separate (already existed) issue.
Marc stated "I did not implement this particular optimization, because there would be no way to automatically prevent overlap."

True I was unable to implement a proper fix for this due to the limitations of our older layout algorithm. But presumably it would be possible now, and I agree it should be addressed, so I wouldn't call it by design.

relates to #272132: [EPIC] Text positioning issues

The original bug seems to be fixed in master.

Automatically closed -- issue fixed for 2 weeks with no activity.