You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed the comparefamily report for some code points in Source Serif was suspicious:
Warning. Font uses working name 'u1F16A' rather than Adobe final name 'u1F160'. SourceSerif4-Regular
Warning. Font uses working name 'u1F16B' rather than Adobe final name 'u1F160'. SourceSerif4-Regular
The code points in question are
U+1F16A RAISED MC SIGN 🅪
U+1F16B RAISED MD SIGN 🅫
comparefamily suggests the final name (and hence the code point) should be U+1F160 NEGATIVE CIRCLED LATIN CAPITAL LETTER Q 🅠 – wrong, of course.
I noticed the
comparefamily
report for some code points in Source Serif was suspicious:The code points in question are
U+1F16A RAISED MC SIGN 🅪
U+1F16B RAISED MD SIGN 🅫
comparefamily suggests the final name (and hence the code point) should be
U+1F160 NEGATIVE CIRCLED LATIN CAPITAL LETTER Q 🅠
– wrong, of course.When investigating, I noticed that the method for getting the final glyph name returns false results for almost all five-digit code points:
(this code is mostly pulled from
comparefamily.py
)Looking through agd.py it seems that five-digit Unicode names are simply not expected:
afdko/python/afdko/agd.py
Line 47 in 20b4817
afdko/python/afdko/agd.py
Line 63 in 20b4817
I fixed this in my local agd.py, and will send a PR in a minute.
The text was updated successfully, but these errors were encountered: