I’m testing this new font, MusAnalysis, on a number of music notation programs. Only one major program, Finale, is not recognizing ligatures in this font, and only on Windows (it works correctly on Mac).
However, this other font I created, MusGlyphs, does display correctly in Finale for Windows - ligatures work as expected.
I see there are some differences between the two fonts, obviously, but I don’t know which differences are pertinent to this mystery. I know you don’t know how Finale is interpreting the font, of course, but could you suggest what I might need to change here? Thanks!
Do see if you have more success if you export through FC14.
Remember to save your project as a new file from FontCreator 14. They won’t open in FontCreator 13.
I create a new folder for each new FontCreator version.
Unfortunately exporting from FC14 did not fix the problem.
Sorry to ask again, but can you give any suggestion about what might be the difference between the two fonts? I’m unable to figure it out why it does not work on Windows. I’m a bit desperate, since we have rolled it out already. Thanks.
Do remove language ARI from the Latin script and see if that helps.
Otherwise you will have to try to remove other features or lookups to maybe discover the conflict.
Thanks, I tried removing ARI (not sure how it got there), but it didn’t solve it. I’m still stuck.
There is nothing wrong with the font, so better ask the people at Finale why their software fails to display it correctly.
Thanks, I have a support request in to them.
Perfect. Keep us posted here!
Finale support has no idea what the problem could be. I have tried a couple things:
- Deleted all contextual alternates, no success
- Deleted half of the font glyphs to reduce the size, no success
- Exported as true type, no success
- Deleted all of the glyphs that were extremely large, no success
- Deleted all glyphs except for the ligature, success
I am very willing to try deleting individual features by brute force, but do you have any suggestions about ones that might be a particular problem?
Hi everybody, I’m very sorry for the bump, but several days of testing with some colleagues have gotten us nowhere. Can anyone suggest where we might look in the font to start identifying an issue?
To clarify, I know there’s nothing wrong with the font itself, but rather with how Finale is reading it in Windows. But other fonts with GSUB work fine…
Thanks in advance.
The only thing I can do is to repeat this:
Please use FC14 to export the font. That way you know for sure it is not related to bugs in FC13. Hope this helps.
I tried exporting the font using the most recent beta of FC14, but it still didn’t work in Finale.
UPDATE: after hours of testing, I have discovered that deleting the capital M glyph makes it work. Sort of. Most of the ligatures now appear. Kerning and contextual alternates seem to work. But strange things break it. The dollar sign and the equals sign both make it go haywire, converting it to some sort of large sans.
And every ligature advances the cursor too far to the right, adding extra space.
Any ideas on where I should look next? I’m glad to make progress, but I’m still totally baffled as to why this is happening. Thanks.
Can you share the latest project file for FontCreator 13?
There are no contextual ligatures in the MusGlyphs.otf linked to in the first post.
Sorry for the the confusion, MusGlyphs works correctly in Finale, but MusAnalysis doesn’t. Here’s the project file: https://www.dropbox.com/s/go493uietvro4ak/MusAnalysis%201-1.fcp?dl=0
That is one heck of a jigsaw puzzle to solve. I don’t think I have time to figure out how it is supposed to work, let alone why it goes wrong. 
Yes, I know it’s quite complex and a bit big, sorry! It’s really not random though. Here’s a short video that shows some of the things it does: https://youtu.be/EBF5bJUPLK4
And no problem, I think we will just have to push the Finale team to address it. Thanks.