On 2018-11-20 10:22 a.m., James Godfrey-Kittle wrote:

> It's possible that this font actually contains illegal feature syntax,
> which is still accepted by Glyphs. Or of course it could be an issue
> with some component of fontmake; it's worth posting an issue on Github
> to have it triaged (I was planning to do this soon when I have time).

It is also possible that the font source worked at some point with the
build tool chain, then the tool chain changed, breaking the build. I am
not saying this is the case here, I have not looked into the details.
Just to say I have seen similar issue with my team's own fonts where a
font built with the toolchain, then the toolchain was updated (in one
case to fix a bug), and the build broke.

So in some sense, the source was not incorrect until the build system
found it to be incorrect.

Bobby

-- 
Bobby de Vos
/bobby_de...@sil.org/

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to