typing ub should produce an upbow symbol (looks like a V). It renders fine in the Preview, but it does not work correctly when I install the font.
Qdb/ should produce a diamond notehead with no stem. It displays correctly in Word, but when I export to PDF, it displays the Qdb ligature with a slash after it. Oddly enough, when I type the same ligature in Dorico and output it as PDF, it does display correctly.
All seems to be working fine here in Serif PagePlus and LibreOffice. I do not use Word.
The Ligature 1 lookup is empty and seems to be superfluous. Deleting that does not seem to make any difference. LibreOffice Music Glyphs.pdf (4.21 KB) Music Glyphs.pdf (5.96 KB)
It works just fine in the software I used for testing; the Font Test dialog in FontCreator, Firefox, and Word. So maybe your software does not fully support ligatures, maybe (as Bhikkhu Pesala already mentioned) removing the empty lookup might fix this problem.
When I try this in Word and produce a PDF, it works just fine.
I’m still completely stumped on the upbow mark. I cannot get it to display correctly in Word or Dorico. Other users have confirmed that it does not work for them in Word or Dorico.
I previously had no problem displaying this as a ligature, and all the other 212 ligatures display correctly.
I’ve tried everything: deleting the ligature and re-creating it… assigning it to completely different and random key combinations… Nothing works. I simply cannot get the V mark to display correctly.
A computer restart seemed to fix the other notehead slash issue, but this does not work.
It does work in Word, I am using the latest version. It is hard to understand the issue; maybe Word automatically capitalizes the first characters, so it shows Ub which does not get substituted to your V.
That’s correct that it capitalizes first words, which is very annoying, but I’ve ruled that out. I have tried this so many different ways that I think I will just delete those ligatures entirely. It is really unsettling that I can’t figure out what the problem is here. Thanks for your help.
Thanks to you both. I wonder if I had pushed out too many versions that were the same version number and Word got confused? Anyways, I uninstalled the font entirely, exported the corrected font as a new version, restarted the computer and installed the new version, and now it works.
I confess I don’t entirely understand why, but one more thing to learn. Also, thank you for bringing my attention to the “test in Word” option, which will definitely save me time.
