You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At least for some CJK character sets, FontForge writes a font which
includes a METRICSSET section in the preamble, and later in some glyphs
skips the SWIDTH/DWIDTH lines in preference to the default values specified
in the METRICSSET. According to the Adobe document describing the 2.2
format, this is ia size optimization for storing bdf fonts because many
glyphs have the same metrics, particular for vertical text layouts.
X's bdftopcf never accepted these extensions not present in BDF 2.1,
but fontforge writes them anyway. (I'm not sure who is using fontforge's
BDF output, given this fact)
This adds minimal support for these elements of the font.
Testing performed:
* converted yasa-200.bdf to pcf, then rendered with Adafruit_CircuitPython_BitmapFont's simpletest on a host computer
with adafruit/Adafruit_CircuitPython_Bitmap_Font#34 applied. (this was broken before this PR)
* converted a bdf file produced by otf2bdf and displayed it similarly (this was working before)
0 commit comments