NOTATIO

Hi Dan. I looked over the voice-leading lines in both as Lyric and Text entry in Finale 25.5.

1. The single voice-leading lines work well now using the semicolon for Lyric entry. One can enter a single centered hyphen with the hyphen key stroke, a long line with the semicolon, and an initial single hyphen with the semicolon. One can do the same with the Text tool using only the hyphen key or only with the semicolon. The only difference is that the hyphen starts closer to the numeral with the semicolon keystroke. Perhaps you intended that.

2. Double, Triple, and Independent double voice-leading lines all work as expected as Text. However, none of the hyphen keystrokes work in the Finale Lyric Tool. Perhaps you are intending to replace them also with the semicolon key stroke.

3. I was not able to duplicate your example with the independent triple voice leading lines in either the Text or Lyric Tools following the given keystrokes. Instead of: I get the following:
In any case, the independent triple voice-leading lines seem to work because there are no hyphen keystrokes used. But I will need to experiment further because the commands are a little involved. You might consider more explanation.

Thanks John, yes I just noticed last night that it’s an error in the documentation there. And I will add additional explanation, as I understand that’s a bit more complicated.

And no, that spacing shouldn’t be closer. That’s a bit of kerning that needs to be corrected.

The main area of concern is the hyphen keystroke in the Finale Lyric tool which makes some double and triplet combinations impossible.

John Ruggero wrote: ↑11 May 2021, 13:55 The main area of concern is the hyphen keystroke in the Finale Lyric tool which makes some double and triplet combinations impossible.

But as before, can’t you easily use the non-breaking hyphen as a substitute? That’s exactly what Dorico requires as well, since the hyphen behavior there is the same. I’m loathe to relinquish the hyphen as the default behavior.

Edit: I see you mentioned earlier there isn’t this option. But I don’t think that’s true. I’ve used it, and I’ve seen it documented online.

I will ask about the non-breaking hyphen over at the Finale board. Finale does have a hard hyphen. Maybe that is what you remember? But I'm acting like I know the difference between the two, which I don't.

In any case, the hyphen does not work for double and triple voice-leading lines, so I would just draw those in with the line tool if needed.

If you're able to get the non-breaking hyphen working, that should solve all those issues with leading lines. I'm 98% sure that's possible.

Apparently there was recent discussion about this at:
https://www.finaleforum.com/viewtopic.p ... hen#p83361

From what I gather there may not be a non-breaking hyphen in the Mac version, only in the Windows version. As for the hard hyphen in the Mac lyrics tool:

I would like this from your documentation: But I get this when I insert a hard hyphen:

Well, infuriatingly, MusAnalysis doesn't work on Finale for Windows at the moment because it doesn't recognize the ligatures correctly. I have some font-expert friends on the case, and they're stumped. There's nothing wrong with the font.

So Finale on Windows is dead in the water, and Finale on Mac can't correctly parse a non-breaking hyphen. Curse you, Finale!

John, try this beta: https://www.dropbox.com/s/4fzv7msk9dhdv ... n.otf?dl=0

Try V64....3 and V64====53 and V64++++5

Use a period for the lower dash, not a hyphen. Still plus for the upper dash and equals for the double.

If that works correctly, I'll make a Finale version that subs the period (or adds it as an additional option) for the hyphen everywhere it occurs. Perhaps that would be better anyways, to avoid the confusion with the hyphen (since Dorico uses the hyphen to advance lyric entry as well).

Getting closer!

Oh, dumb error. The period prefix was set to return numerals slightly smaller than full-size.

I've now remapped the period-number combinations to ampersand-number. Download the same link, re-install the updated font, and try those leaders now.

If this works, I will move forward with re-mapping all the other contextual alternates to reflect this change. Thanks.