From 54e2072eccb236af3f8b27af25da1fc00141f0c4 Mon Sep 17 00:00:00 2001 From: Adam Twardoch Date: Wed, 9 Mar 2022 18:09:52 +0100 Subject: [PATCH] Add debug logger showing the glyph name for which gvar is built MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit When building gvar, some situations cause fontmake/varLib to fail, for example if a component has a coordinate that's >32k or <-32k. This adds a debug line that prints each glyph name for which gvar is built, so it’s easier to pinpoint where the faulty glyph is. --- Lib/fontTools/varLib/__init__.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Lib/fontTools/varLib/__init__.py b/Lib/fontTools/varLib/__init__.py index db10a72f5..15c2e7007 100644 --- a/Lib/fontTools/varLib/__init__.py +++ b/Lib/fontTools/varLib/__init__.py @@ -230,7 +230,7 @@ def _add_gvar(font, masterModel, master_ttfs, tolerance=0.5, optimize=True): for m in master_ttfs] for glyph in font.getGlyphOrder(): - + log.debug("building gvar for glyph '%s'", glyph) isComposite = glyf[glyph].isComposite() allData = [