How to PUA encode an existing font?

[mekkablue (Rainer Erich Scheichelbauer)]

The font you sent me works, the ligatures th and tt form as expected. There must be something wrong in the way the font is applied and which settings are set in Word. The font itself is OK.

Perhaps try experimenting with the settings, selections, etc. Make sure the font is really replaced and you are not accessing an outdated version. Do you know how to clear font caches in Windows?

[Bhavika (Bhavika Malhotra)]

Hey,

I’m using mac and I’ve cleared all caches and applied the settings too. Played around with it as well. Can’t figure out what could be the issue. The client who is using the font also can’t get it right. He’s on windows. He has tried using other fonts and they seem to be working fine. The issue crops up only with my font.

I also created a new font and installed it for the first time so there can’t be any cache’s. But it too has the same issue. The ligatures don’t work and the option to use them is also greyed out in the ‘text effects’ drop down.

[harbortype (Henrique Beier)]

I believe this is a languagesystem issue. I just tested two versions of a font of mine. The first one had

languagesystem DFLT dflt;

and the second one had

languagesystem DFLT dflt; languagesystem latn dflt;

As you can see from the screenshot below, Word needs the latn dflt bit for the OpenType features to work. All text has ligatures enabled.

Glyphs used to add both lines automatically, but now only adds the first one. This problem has been around for a while:
https://forum.glyphsapp.com/t/opentype-features-ms-word/

No kerning in Office

Hey GeorgeSeifert and mekkablue, An update on the kerning issue: I erased all kerning data and started over with kerning in the glyphs file. So now it works in Word (15.9.1). However, the kerning still doesn’t work in Powerpoint (15.19.1) I tested with both otf and ttf exported from Glyphs 2.3 (OSX 10.11.4) Kerning works fine in Adobe CC, Safari, Firefox and Chrome. Hope you can help

@GeorgSeifert and @mekkablue, is there a reason Glyphs stopped adding the latn dflt line? Is it possible to revert the previous behavior?

[Bhavika (Bhavika Malhotra)]

Hey, Thanks a lot for confirming this.
I was reading another thread and I thought this could be an issue. I had tried adding languagesystem latn dflt; but I couldn’t. It kept going back to DFLT as soon as it updated.

Not sure how to add it to check the same.

[mekkablue (Rainer Erich Scheichelbauer)]

Uncheck the automatic.

[Bhavika (Bhavika Malhotra)]

@harbortype

languagesystem latn dflt;

Man! I can never thank you enough! It worked!!! Thank you SOOO much!

Also, @mekkablue like @harbortype asked, is there no way to get back to having the line added automatically?

[mekkablue (Rainer Erich Scheichelbauer)]

It adds automatically once you have one locl feature in Latin.

1. e.g., add the glyphs iacute and jacute
2. automate all features
3. update feature code