I wouldn't scale at compile time (as said, storage constrained payloads might not be happy about that).
I wouldn't scale each character up on each access though (we won't hardware accelerate the scaling, and yes, that does get slow - framebuffers aren't always the fastest type of memory and that way the access pattern is the same set of memcpy()s as for any other huge font, so we won't need to deal with "fast fonts" and "slow fonts" beyond basic geometry characteristics), but synthesize a new font in the regular font table at init-time and then use it like any pre-existing font (just that it happened to be added after load). 2017-07-17 21:47 GMT+02:00 Julius Werner <jwer...@chromium.org>: > I agree with most of what Patrick said, I think dynamic scaling to integer > multiples may be best. Scaling the font up at compile-time seems like > unnecessary bloat to the binary (although I'm not sure, how big are these > fonts?). If you do want to include them at compile time, you may as well > include a real larger font rather than just a scaled one. > -- Google Germany GmbH, ABC-Str. 19, 20354 Hamburg Registergericht und -nummer: Hamburg, HRB 86891, Sitz der Gesellschaft: Hamburg Geschäftsführer: Matthew Scott Sucherman, Paul Terence Manicle
-- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot
