Open simoncozens opened 3 years ago
fontdiffenator is deliberately aimed at the semantic level - what are the user-facing differences between two font files?
Yep.
I like what you're doing here however, we already check the hhea, head, OS/2 tables etc. They're bundled together in the diff category attribs.
Perhaps breaking apart this attribs table into their actual tables like you're doing is the better approach.
If this is a feature you desperately need, I have no qualms in merging this. However, we could do a tidy up but I'm going to rewrite some parts of this tool this year (will consult you first about the design) so I'm not sure it's worth the effort to get it 100%.
I do need a good tool to help me understand any differences between fonts produced by my toolchain and fontmake, and I find this helps me. But maybe it doesn't need to be added to fontdiffenator if you're going to work on a new approach; I'm happy just to run the test from my own fork.
fontdiffenator is deliberately aimed at the semantic level - what are the user-facing differences between two font files? However, it's also a good basis for asking structural questions: how does the data in these two fonts differ? This adds a "structural" test which reports on differences within the OpenType tables. It isn't on by default, but can be asked for with
--td structural
. I plan to extend it to cover all the tables in the OT spec.Here's some sample output: