Fonts: anti-aliasing flag, overhanging glyphs, Font Creator byte 18
The Font Creator's anti-aliased fonts are 1-bit glyphs with header flag 0x1E (the simulator draws them with two colours). Map bytes 3/4 are extra columns left/right of the advance width; glyphs are drawn starting 'left' px early. Editor-generated fonts now round-trip byte for byte. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
6616b47cb4
commit
55c2f9d6b6
6 files changed
+49
-12
No files matched your search
+9
-3
@@ -247,7 +247,14 @@ multi-byte range (2 bytes), code range first/last, u32 character count, u8 versi
|
||||
u8 name length (twice) + 0, u32 length of name+map+glyphs, u32 name offset = 0x2C, 16 unknown
|
||||
bytes. Then the name, the character map, the glyph data.
|
||||
|
||||
Character map: 10 bytes per character: u16 code, u8 glyph width, 2 unknown bytes,
|
||||
Header byte 0x1E = 1 when the Font Creator's "Anti-aliasing of fonts" box was ticked. Such fonts
|
||||
still hold 1-bit glyphs (Windows' thinner anti-aliased outline, thresholded); the Intelligent
|
||||
simulator draws them with two colours only. Byte 18 (second name length) is 0 in fresh Font
|
||||
Creator output and the name length after a re-save; both load.
|
||||
|
||||
Character map: 10 bytes per character: u16 code, u8 glyph advance width, u8 extra columns on the
|
||||
left, u8 extra columns on the right (glyphs that overhang, e.g. `j`, `f`, `W`; the stored glyph is
|
||||
advance + left + right wide and drawn starting `left` px before the pen position),
|
||||
u24 glyph offset (relative to the map start), u16 glyph length. In Intelligent projects the glyph
|
||||
data starts 4-byte aligned (zero padding after the map); Basic fonts have no padding.
|
||||
|
||||
@@ -269,8 +276,7 @@ converts a 90
|
||||
The Editor encodes greedily (transparent run + 1..4 ink if possible, else the 3+3-bit form, else a
|
||||
plain run); our encoder reproduces a 224-glyph Editor font byte for byte. The v3/v5 write-ups in
|
||||
github.com/hagronnestad/nextion-font-editor were a useful starting point; v6 differs (scan order,
|
||||
B/W codes `10`/`11`). **OPEN**: anti-aliased glyphs (other mode bytes), multi-byte encodings,
|
||||
the 16 unknown header bytes.
|
||||
B/W codes `10`/`11`). **OPEN**: multi-byte encodings, the remaining unknown header bytes.
|
||||
|
||||
## 6. Not yet covered
|
||||
|
||||
|
||||
Reference in new issue
Block a user