@travisgoodspeed @lafp I noticed that there are 66 rows, which are 2 more than the 64 what would be needed for exactly 2kbytes of ROM. Maybe there's 1 parity bit for every 32 bits of data?
@travisgoodspeed @lafp With this custom build you can run any of these Z8-based emulators with MAME's -debug option which will give you an interactive debugger, letting you inspect memory contents, view disasm listings, place breakpoints, etc.
@travisgoodspeed @lafp For a custom build:
QT_SELECT=5 make SUBTARGET=z8devices SOURCES=src/mame/handheld/pensebem.cpp,src/mame/fidelity/msc.cpp,src/mame/learsiegler/adm23.cpp,src/mame/metro/metro.cpp,src/mame/misc/amerihok.cpp,src/mame/quantel/dpb7000.cpp,src/mame/skeleton/bert.cpp TOOLS=1 REGENIE=1
@travisgoodspeed @lafp These are the MAME drivers that rely on the Z8 mcu: src/mame/ddr/jtc.cpp
src/mame/fidelity/msc.cpp
src/mame/learsiegler/adm23.cpp
src/mame/metro/metro.cpp
src/mame/misc/amerihok.cpp
src/mame/quantel/dpb7000.cpp
src/mame/skeleton/bert.cpp
@travisgoodspeed @lafp There are a few devices emulated on MAME that use a Z8 chip, so we may take a look at the ROMs (and disasm) of those to collect some samples of typical code patterns. Also MAME has a good disassembler for the Z8.
@eliheuer@FontTools The goal is to make it even clearer to the users (and developers) that FontBakery is not vendor-biased and can be used by anyone who needs automated quality assurance for fonts!
I wrote a new FontBakery check that was merged into the Universal Profile recently! It gives a WARN if uppercase glyphs are not vertically centered in the em box (with %5 of the UPM as a margin of error).
https://t.co/yU6gIJqxQP