Quit and restart Finale so MacSymbolFonts.txt reloads.
N.
November 2 font not recognised
Moderators: Peter Thomsen, miker
- N Grossingink
- Posts: 1788
- Joined: Mon Dec 19, 2016 2:50 pm
- Finale Version: 27.3
- Operating System: Mac
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
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
- elbsound
- Posts: 196
- Joined: Wed Aug 03, 2016 10:06 am
- Finale Version: Finale 2014.5
- Operating System: Windows
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.
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.
- elbsound
- Posts: 196
- Joined: Wed Aug 03, 2016 10:06 am
- Finale Version: Finale 2014.5
- Operating System: Windows
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.
The other fonts (I assume November and NovemberExtra) are non-unicode fonts. AFAIK they should be included in MacSymbolFonts.txt.