Embedded bitmap strikes research. #9
Description
One of the reasons Greybeard no longer provides a single .ttf is because bitmap strikes don't seem to be a viable option in the modern era. Therefore I switched from using fontforge to using Bits'N'Picas to synthesize the font as pseudo-pixel outlines. This works great, and seems to do a lot of inspection on the BDF to get things right, but now each size has to be its own font.
This was considered a worthwhile tradeoff for the convenience of automatic building, plus it makes it much more clear what size the font is intended to be used at, instead of providing list of "good point sizes" and "bad point sizes". That said, it would be nice to have them all in one file again.
mkttf attempts to automate this using the trick of adding CKJ glyphs and setting the codepage to trick Windows into actually rendering bitmap strikes, however it's unclear if this is viable for usage on Windows, given the issues described in the link above.
If you have experience making Windows do the right thing with fonts that have bitmap strikes, please comment here or issue a PR!