Generating Devanagari Fonts Bug in GPOS

Hi everyone,

I’m not sure if this is a Glyphs App bug or something else, I’m working on a devanagari font, I have my OpenType layout features file separated, I have my own glyphs names and I export the kerning, the dist feature, the mark classes and anchors in a text files which I call from my .fea file. The thing is when I export sometimes the GPOS table is fine and many times it’s having errors in the dist feature. I’m working on an Imac with Catalina, Glyphs app version 3260 (top of the picture) and on a Mac Mini with Catalina, same Glyphs version (bottom of the picture). Any hints to solve this will be much appreciated. Regards!

But you export the font with Glyphs? Why do you write your own dist feature? Can you check the fea code where that -306 comes from?

Thank you for your reply Georg, I’m exporting the font from Glyphs app, for my OTL.fea I have an ‘include’ instruction. I write my dist feature because according to the spec the ‘dist’ feature doesn’t rely on the software ‘kern’ feature support, otherwise dist is included inside the kern feature. When I deactivate the abvm feature the combination shown works fine, but that makes a mess with other glyph and mark clusters. I thought it was the dist and kern feature, but when I deactivate the ‘abvm’ it works, if I remove my lookups from abvm the problem is still there, I mean even an empty abvm feature makes this problem. I don’t have any -306 number in my code, could it be my python version or some plugin I need to get? (Python 3.10.8 Homebrew)

Glyphs is doing that automatically. But because of your custom glyphs names, it doesn’t know about the script of the glyphs. So you can either switch to the build in names, or build a custom GlyphData (Roll your own glyph data | Glyphs). Or at least manually set the script for each glyph. I suspect that some of the other problems are related to the same missing glyph infos.

then there are two lookups that are applied on top of each other. But I can’t help more without seeing the code.

probably not.

Thank you Georg, your reply was very helpful, the glyph category in my custom GlyphData file was “Mark” rather than “Letter”, and the subcategory was “Spacing Combining” instead of “Matra”, that solved the issue. Regards!