Numbers not all aligned when word of stanza doesn't start on first note

• Jan 26, 2015 - 22:50
Type
Functional
Severity
3
Status
active
Project
MuseScore

1. Open attached score (produced in 1.3).

Expected result:
Numbers not all aligned when word of stanza doesn't start on first note - Expected result.png

Actual result:
Numbers not all aligned when word of stanza doesn't start on first note - Actual result.png

Note: LilyPond produces the same as the expected result:
Numbers not all aligned when word of stanza doesn't start on first note - LilyPond.png

Using MuseScore 2.0 Nightly Build 1634901 - Mac 10.7.5.

Attachment Size
Numbers not all aligned when word of stanza doesn't start on first note.mscz 1.83 KB
Numbers not all aligned when word of stanza doesn't start on first note - Expected result.png 127.06 KB
Numbers not all aligned when word of stanza doesn't start on first note - Actual result.png 35.39 KB
Numbers not all aligned when word of stanza doesn't start on first note - LilyPond.png 38.41 KB

Comments

• Jan 26, 2015 - 23:45
Severity ⇒

Actually, for the mscz, I entered '3.4.' at the second word, when it probably should have been at the first. Should it still parse as such? I'm not sure.

Anyway, even when entering the numbers at the first one (see attached mscz - produced in 1.3), the numbers still don't line up.
Numbers not all aligned when word of stanza doesn't start on first note 2.png

Should I make a new issue?

Attachment Size
Numbers not all aligned when word of stanza doesn't start on first note 2.mscz 1.84 KB
Numbers not all aligned when word of stanza doesn't start on first note 2.png 47.12 KB

Reply

• Jan 27, 2015 - 00:00

You should indeed have entered the numbers on the first note. But it doesn't right align because if the algorithm to ignore leading numbers & punctuation did that, it would be impossible to center a lyric consisting of nothing but numbers and/or punctuation characters, and that is definitely what you want in other situations.

Solution: right align the "syllable" using Text Properties.

Reply

• Jan 27, 2015 - 01:25
Severity ⇒
Status (old) active ⇒ postponed

As far as I am concerned, right now we do about as well as we reasonably can in automatically handling a variety of cases worth handling. But it will no doubt be true that are cases like this where we don't do what one might want. I'm thinking also of #24856: Ignore "parenthesized expressions" that precede lyric syllables. At some point we should have probably have more ways of controlling things, but coming up with something comprehensive enough to be worth doing is beyond the scope of what I'd imagune happening for 2.0. Some day, I could see options to disable the automatic hadnling of apparent verse numbers (globally and per-syllable), a way of attaching text in front of lyric syllables (like the example in [#24856; similar to the now-removed "lyric verse" element), more style options for dashes and melisma, also above & below staff lyric settings, etc. I think these things should work together and look like a coherent whole and not a bunch of ad-hoc features and options cobbled together. Which is why I think it's a task for another day.

Reply