The reason named only MSX and FPseNG fonts, while fm7.zip and fm77av.zip
hold a Fujitsu kanji ROM (MAME kanji.rom, crc32 62402ac9). Rendered at
the codes kanji.c:353-380 swaps between JIS78 and JIS83 (0x3646, 0x445B,
0x4768), it draws the JIS83 forms: the ROM is a first standard JIS83
table, not the JIS78 one XM7 reads as KANJI.ROM.
Each standalone profile records where its version is read: the source
at its pin (clk 2026-07-23-136-g9020107, shadps4 0.20.1 WIP, eden
v0.2.0-401-g26a03d2), the APK, binary or archive read (kind package),
or, where no reading can be made, kind unverified with the reason: a
host the tools cannot read, a forge gone or not answering, no build
recorded as read, a pin on another branch. Those keep their value,
unconfirmed.
100 emulator names the two platforms run had no profile, so their packs carried nothing for them. Each was read from the platform's own launcher or scriptmodule: the same program as an existing profile takes the name in cores:, a different build gets its own profile read from that version, a launcher or self-contained game goes to remove_cores, and the rest are new profiles written from their source or shipped binary. The files they need that the collection lacked are collected from the upstream distributions. Bungie and splitwolf trees are read by path and stay out of dedup.
Abdessamad Derraz