Confirmed a handful of fonts fail the checksum from the latest ISO, but succeed after replacing those files from a fully up-to-date installation of Windows 11.
The PKGBUILD readme should probably mention that the checksums intend to track an actual installation and not the ISO that's linked in that file. (This isn't "some random ISO," this is the file that is linked in the build instructions.) The (mostly complete) instructions for extracting from the ISO aren't entirely pointless, since people who don't care about their fonts being up-to-date can just ignore the checksums, but it's a little misleading as-is, imo.
Pinned Comments
Vaporeon commented on 2025-10-12 10:13 (UTC)
For reference, Windows 11 25H2 is the same core base as 24H2 with an "enablement package" applied. What this means is that the fonts from 26100.XXXX and 26200.XXXX should be the same, provided the XXXX part is equal (or later). This should be true for at least the life of 25H2, provided your 24H2 SKU is still getting updates. So keep this in mind if staying on the 24H2 branch for any reason.
Vaporeon commented on 2025-05-25 06:23 (UTC)
THE INTENTION OF THIS PACKAGE IS TO EASILY INTEGRATE THE LATEST FONTS FROM A FULLY UPDATED WINDOWS 11 INSTALL INTO AN ARCH LINUX SYSTEM.
PLEASE DO NOT COMPLAIN IF THE FONTS MISMATCH OLDER VERSIONS FROM SOME RANDOM ISO.
PLEASE DO NOT FILE A REQUEST TO MERGE THIS PACKAGE WITH ONE THAT PULLS OLDER VERSIONS FROM SOME RANDOM ISO.
THANK YOU.