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
Notodiff works well for different versions of the same font. However, sometimes it is useful to compare similar fonts of different vendors.
Despite their glyph coverage can be very close, notodiff finds and reports lots of differences, because glyph names assignment is not standardized and font vendors can assign completely different names for glyphs that look identical and mapped to the same unicode characters.
Though strict mapping is impossible, provide some heuristics that can map some of glyph names and reduce number of reported false differences.
Notodiff works well for different versions of the same font. However, sometimes it is useful to compare similar fonts of different vendors.
Despite their glyph coverage can be very close, notodiff finds and reports lots of differences, because glyph names assignment is not standardized and font vendors can assign completely different names for glyphs that look identical and mapped to the same unicode characters.
Though strict mapping is impossible, provide some heuristics that can map some of glyph names and reduce number of reported false differences.
Examples:
Rule-based names: ‘glyphXXXX’ to ‘uniXXXX‘
Cmap reverse mapping ‘glyphXXXX’ (font 1 cmap) -> code point XXXX -> (font 2 cmap) ‘uniXXXX’
The text was updated successfully, but these errors were encountered: