>the FAN files included have the space symbol extremely high
#FINALE 2014.5 COMPATIBILITY PDF#
OTF looks better on Windows screens (but identical in print), on MacOS there is no difference on the screen (that's why I supplied TTF only for MacOS).īut TTF is usually much better supported by 3rd party software, sometimes even the PDF printer works better with TTF or even refuses OTF. The fonts glyphs are identical - but one is OTF and one is TTF.įor differences between OTF/TTF see wikipedia or search google. >Also, why have you created OTF and TTF versions, what is the difference? You should only make sure that on Windows only the symbol 32-255 were used, as only these symbols are available in the MacOS fonts / font annotation files. If you use the Windows fonts on Windows and the MacOS fonts on MacOS, the Finale documents can still be exchanged between MacOS and Windows. When the bug is fixed, only one version of fonts is needed for both MacOS and Windows (the current Windows fonts). MakeMusic promised to fix the bug quickly. By adding the name to MacSymbolFonts.txt you make it 32-255 only. So if you want to have cross-platform compatibility with any font on Windows/Mac, they must be either unicode only or The problem is Finale's confirmed 129-159 bug (that I described on the MakeMusic forum in the 21 new fonts thread) which makes it impossible to have compatible unicode fonts on Finale MacOS and Windows. The Mac fonts are cross-platform compatible, while the Windows fonts are not. That means you must install the Mac fonts on Windows and also add the font names to "Installation on older Finale version on Windows". If you want to go cross-platform with the fonts, you should follow section 5) of the FAQ, Good question! I should add it to the troubleshooting section. >If I share my Finale documents on OS X with a user on Windows, shall we both use OTF?
0 kommentar(er)
