The SMuFL fonts that are installed with Finale v27, are easy to find:

Their font names all begin with ‘Finale’.

Example:

Maestro is the “legacy” version of the Maestro font.

Finale Maestro is the new SMuFL version of Maestro - with lots of new font characters.

If you have other (third party) SMuFL fonts, then you have to know their actual font names.

But take a look at the font names displayed in this web site:

https://www.smufl.org/ 

Can Finale show me only the SMuFL-fonts?

I don't think so but for a new doc, the default is SMUFL Finale Maestro unless you change it. When you use the Document Wizard at the top of the setup screen you can choose SMFUL Finale Maestro or Finale Broadway.

Thank you, Peter and Ernest, now I see.

There are a few more that come with Finale like Ash, Copyists and Jazz.

Like Peter said above you can tell them apart because they all start with "Finale ----"

Yes, but it would be nice if FINALE would offer a box "Show only SMuFL-Fonts", because there are many third-part SMuFL Fonts available.

Yeah, I guess so but all fonts don't start with the word Finale in their name. I really don't know how they would be able to do it. Especially when someone can name their font anything they like. But I am not a programmer. And, if you go to the Font box in Finale it does list all the Finale smufl fonts together since they do all start with "Finale".

If one downloads a font, one ought to know what kind of font it is.

If one downloads a font, one ought to know what kind of font it is.

True. But I’ve downloaded a few SMuFL fonts like Petaluma, Sebastian, Sonata and probably 1-2 others and as more are added by users, it will absolutely get confusing to know which is SMuFL and which is not. Just as macOS can easily produce a display of which apps are 32-bit vs 64-bit, or are Universal Binaries vs Intel vs Apple Silicon, why can’t Finale produce a list of fonts that are SMuFL and which are not? Or have a checkbox in the fonts selection dialogue to show just SMuFL fonts. Seriously, it can’t be that daunting regardless of how a font is named. You can’t expect all users to know that having Finale in the font name means it’s SMuFL. That seems like an odd way to do this. Better to have a selection checkbox to do that. GIven that SMuFL fonts all rely on a .json folder, perhaps there is a way to use that feature to discriminate between SMuFL and non-SMuFL. Surely the geniuses who came up with the SMuFL standard thought of something like that? 

At the same time, how much any of this matters depends on the user and her/his needs. In many ways, it doesn’t matter at all if one uses Broadway Copyist or Finale Broadway. 

If one downloads a font, one ought to know what kind of font it is.

I believe the OP knows when he d/l the font. The question is why can't Finale show only smufl fonts in a single screen and ignore others. Afterall smufl was the big deal with the newest Finale.

"Can Finale show me only the SMuFL-fonts?"

Considering all the challenges Finale developers face, I do not think that creating a routine for a few users who won't bother to keep track of their own fonts should be a major priority. YMMV, but most composers and engravers limit themselves to a very few fonts that they learn and use consistently; it is not as if a wide swath of Finale users jump randomly from font to font every time they start a new piece.

I’m confident the developers are up to the challenge. I mean, give me a break. 

David,

It seems people always pooh-pooh features they don't see and a good thing for themselves. I am only now really getting started with smful so it would be nice to know which are and which are not in a grouping. Would I make it a top priority for MM, a new upgrade feature, probably not but if it is a easy addition, why not?

Agreed, Ernest. I also think it's presumptuous for users to assume developers "can't" do something. The way it works is the users tell the devs what they would like and the devs can weigh in on whether something is possible and then, prioritize it. 

Point of correction to the post above: Finale Copyist isn't a SMuFL font: it's a text font. Finale's SMuFL fonts are easily identified as those fonts whose names start with Finale but don't end in Text nor in a word describing a subset of notation.

So Finale Maestro, Finale Ash, Finale Broadway; but not Finale Broadway Text and not Finale Lyrics nor Finale Mallets, Numerics, Percussion, AlphaNotes. But there's no way of readily identifying third-party SMuFL fonts, like Bravura, Sebastian, November2, etc.

I agree that in SMuFL mode, it makes sense to offer only SMuFL fonts as options for changing the default music font. And there's an easy way for the app to identify these fonts: they all come with a metadata "JSON" file, that includes information beyond what can be stored in the font file (kind of like a FAN). And indeed, other music notation apps only display fonts in their list of Music Fonts if they have JSON files. 

Unfortunately, MM installs JSON files for the TEXT fonts, too -- like Finale Broadway Text -- even though they contain no music symbols and there is no useful purpose in doing so --  which therefore confuses the issue.

Finale Copyist isn't a SMuFL font: it's a text font.

yup. Which is exactly why the concept of using Finale-prefixed font names to identify those that are SMuFL is a very lame and ineffectual methodology. It’s lazy. Especially since as mentioned , many of us are adding third-party SMuFL fonts that of course do not use that convention. I mentioned the possibility of Finale identifying which fonts have .json files associated with them but as you point out, that won’t work if the programmers add these for some text fonts without any known purpose. This is lazy. But it’s also fixable if the developers simply ditch .json files for text fonts and then have a simple checkbox to only display (true) SMuFL music fonts.

I’m not a programmer but even as a gynecologist this doesn’t seem like something that is insurmountable in the least. 

It does seem like there is enough confusion to warrant some fix. 

Finale's SMuFL fonts are easily identified as those fonts whose names start with Finale but don't end in Text ..."

Both Finale Broadway Legacy Text and Finale Broadway Text have "text" in their name.  However according to the Finale manual, "The Finale Broadway Legacy Text font is the SMuFL-compliant version of the handwritten Broadway Copyist Text and Broadway Copyist Text Ext fonts."  And, "The Finale Broadway Text font is the SMuFL-compliant version of the handwritten Finale Copyist Text and Finale Copyist Text Ext fonts. This font includes enclosures and basic notes and accidentals for creating chord suffixes".

From an inspection of each font's glyphs: Finale Broadway Legacy Text, Finale Jazz Text, Finale Ash Text and Finale Copyist Text have NO SMuFL chars that I can see.

Finale Broadway Text has 16 SMuFL characters, I'll grant you, and these are indeed those suitable for making chord symbols and metric equations. However, you couldn't usefully select it as a Music Font, because it lacks noteheads, clefs, etc.

Finale Maestro Text also has 102 SMuFL characters, though again these are things for use in Chord symbols, Repeat Marks, Tempo equations; and not sufficient to use as even the most basic music font -- no noteheads, flags, rests, time sigs.

But even so, there's no requirement for "Music text" fonts to have JSON files. Bravura Text, the version of Bravura for use in text blocks, has no such JSON file.

I only wanted to show the confusion. The font naming does not clearly define the font type.

In Finale 27.2 you can tell if a font is SMuFL or not by whether the "Import engraving settings from SMuFL font" check box is active (SMuFL) or dimmed out (not SMuFL). I know that's not the same as being able to filter out the non-SMuFL fonts, but you can tell before choosing a font.

Ben, there's no difference in the SMuFL metadata recommendations for text or notation fonts. The SMuFL spec reads "To help software developers integrate SMuFL-compliant fonts, it is recommended that font designers provide a font-specific metadata file, in JSON format, in the distribution package for their fonts."

In general, there are limitations and issues in SMuFL metadata that the W3C Music Notation Community Group plans to address for the next version of the SMuFL spec. If you're interested in helping improve the SMuFL spec, it's free to join the Community Group - the link is on the group's home page.

Thanks, Michael, for the clarification. I did sign up for the W3C emails at some point, but a lot of it flew above me...

I may add to the github issues discussions.