-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue building Varta VF #648
Comments
It was the original error. I already disabled the Observed behaviourWe disabled the Expected behaviourFor Devanagari to work correctly on both static and variable fonts generated from Fontmake. Resources and exact process needed to replicateHere are images of comparisons between Glyphs and Fontmake fonts. |
@m4rc1e please use |
the AttributeError is raised from this line in fontTools.feaLib.builder Adding a check diff --git a/Lib/fontTools/feaLib/builder.py b/Lib/fontTools/feaLib/builder.py
index 6e654374..51d57c79 100644
--- a/Lib/fontTools/feaLib/builder.py
+++ b/Lib/fontTools/feaLib/builder.py
@@ -1311,9 +1311,10 @@ class ChainContextSubstBuilder(LookupBuilder):
if lookups == self.SUBTABLE_BREAK_:
continue
for lookup in lookups:
- alts = lookup.getAlternateGlyphs()
- for glyph, replacements in alts.items():
- result.setdefault(glyph, set()).update(replacements)
+ if lookup is not None:
+ alts = lookup.getAlternateGlyphs()
+ for glyph, replacements in alts.items():
+ result.setdefault(glyph, set()).update(replacements)
return result
def find_chainable_single_subst(self, glyphs): however I am not sure if it's the correct fix and want to futher investigate why some values in that A bit further above this, there is a similar check for None-ness: |
…o attribute 'getAlternateGlyphs' googlefonts/fontmake#648
I just released fonttools v4.8.1 with the fix https://github.com/fonttools/fonttools/releases/tag/4.8.1 |
Just tried to build Varta.glyphs.zip and got the following traceback:
The VF will generate if I delete the 'aalt' OT feature in the .glyphs file.
cc @vv-monsalve
The text was updated successfully, but these errors were encountered: