November 2 font not recognised

General notation questions, including advanced notation, formatting, etc., go here.

Moderators: Peter Thomsen, miker

User avatar
N Grossingink
Posts: 1786
Joined: Mon Dec 19, 2016 2:50 pm
Finale Version: 27.3
Operating System: Mac

Post by N Grossingink » Thu Apr 11, 2019 3:27 pm

Quit and restart Finale so MacSymbolFonts.txt reloads.

N.
N. Grossingink
Educational Band, Orchestra and Jazz Ensemble a specialty
Sample: https://drive.google.com/file/d/1pFF5OeJDeLFGHMRyXrubFqZWXBubErw4/view?usp=share_link


Mac Mini 2014 2.6 Ghz, 8Gb RAM
OSX 10.15.7
Finale 2012c, 25.5, 26.3, 27.3


User avatar
elbsound
Posts: 196
Joined: Wed Aug 03, 2016 10:06 am
Finale Version: Finale 2014.5
Operating System: Windows

Post by elbsound » Thu Apr 11, 2019 6:26 pm

November2 must not be added to MacSymbolFonts.txt.
It's a unicode font.

MacSymbolFonts.txt only needs the old "0-255 symbol" fonts, but not modern unicode fonts like November2, Aruvarb or the LilyPond fonts.

User avatar
elbsound
Posts: 196
Joined: Wed Aug 03, 2016 10:06 am
Finale Version: Finale 2014.5
Operating System: Windows

Post by elbsound » Mon Apr 15, 2019 9:54 am

You write that you removed the three references. You should remove only November2.
The other fonts (I assume November and NovemberExtra) are non-unicode fonts. AFAIK they should be included in MacSymbolFonts.txt.

User avatar
elbsound
Posts: 196
Joined: Wed Aug 03, 2016 10:06 am
Finale Version: Finale 2014.5
Operating System: Windows

Post by elbsound » Mon Apr 15, 2019 11:43 am

Yes, that is correct. You always get a warning (at least on Windows, don't know about MacOS) when you use a music font that is not included in MacSymbolFonts.txt.

Post Reply