Behdad Esfahbod
Behdad Esfahbod
Please attach the font files here, so I can take a look.
Are you trying to merge the variable fonts? That's not supported currently, and probably won't be any time soon.
What version of fonttools are you using? I get a different error: ``` ... File "/home/behdad/fonttools/Lib/fontTools/merge/__init__.py", line 162, in _preMerge layoutPreMerge(font) ~~~~~~~~~~~~~~^^^^^^ File "/home/behdad/fonttools/Lib/fontTools/merge/layout.py", line 451, in layoutPreMerge t.table.LookupList.mapMarkFilteringSets(markFilteringSetMap) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^...
> What version of fonttools are you using? I get a different error: > > ``` > ... > File "/home/behdad/fonttools/Lib/fontTools/merge/__init__.py", line 162, in _preMerge > layoutPreMerge(font) > ~~~~~~~~~~~~~~^^^^^^ >...
> Here is another error when merging Please file a different issue and copy the full error log. I'm guessing that one font has the `vhea` table and other doesn't....
That code is archaic and none of us are familiar with it anymore. If you can dig in a bit and see what's going on, that would be fabulous. Thanks.
varLib: `Invalid axis values, must be minimum, default, maximum` if axis mapping inverts value range
This limitation is inherited from OpenType `avar` spec, which requires that the mapping be monotonically increasing. It's annoying, I agree. Since the numbers in output of the designspace mapping are...
Yeah we have deprecated the mailing list and the github readme page is our canonical landing page...
We have to think about this twice, whether it can possibly change the meaning of the lookup.
+1. Just import the spec into fonttools documentation and annotate it with our extensions.