It seems that the problem is in the font name being corrupted when saving from recent FontForge builds. Indeed, Microsoft Font Validator gives (among the other errors also present in the loadable version of the font) a "BAD FONT NAME" for both the otf and the ttf instead of the expected "MScore" (but MS Font Validator does not say anything about this being a problem for the font). See also here: https://github.com/fontforge/fontforge/issues/1229 where a possible workaround is described (open "Font Info" dialogue and close it with OK before saving).
Ciao, ABL -- View this message in context: http://dev-list.musescore.org/Generation-of-TTF-files-with-FontForge-tp7578869p7578870.html Sent from the MuseScore Developer mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft _______________________________________________ Mscore-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mscore-developer
