OBD:TSGA: Difference between revisions

OBD:TSGA (view source)

Revision as of 00:26, 26 November 2022

209 bytes added , 26 November 2022

m

no edit summary

Geyser

Administrators

5,389

edits

Revision as of 22:12, 24 November 2022 (view source) Geyser (talk \| contribs) mNo edit summary ← Older edit		Revision as of 00:26, 26 November 2022 (view source) Geyser (talk \| contribs) mNo edit summary Newer edit →
Line 36:		Line 36:


	A glyph is basically a grayscale bitmap which is (width * height) pixels in size. ~~Each pixel is stored in one byte in the~~ [[OBD:TSFT\|TSFT]] file ~~(fonts are antialiased so shades of gray are needed rather than storing~~ each pixel in ~~one bit; although~~ for the smallest font size there is no antialiasing ~~in use and~~ the 8-bit pixels are either fully black or fully white).		A glyph is basically a grayscale bitmap which is (width * height) pixels in size. The [[OBD:TSFT\|TSFT]] file stores each pixel as a byte, with 256 degrees of brightness/opacity, which in theory allows for rather subtle antialiasing. In practice, for the smallest font size there is no antialiasing at all (the 8-bit pixels are either fully black or fully white, and are suitable for 1-bit storage), and larger font sizes actually use only 17 degrees of brightness/opacity - from 0xFF to 0x0F, and then 0x00 - which the engine further posterizes to proper 4-bit when rendering.

	The pixels stored in TSFT (packed 4-by-4 as little-Endian unsigned int32s) are treated as a scanline, row major, top to bottom and left to right. The width of a glyph is not always a multiple of 4 pixels, so the scanline can wrap around, i.e. a new row of pixels can start in the middle of a 4-byte element. The start of a glyph, however, is always aligned on a 4-byte element of the TSFT array. The end of a glyph is padded with 0xDEAD.		The pixels stored in TSFT (packed 4-by-4 as little-Endian unsigned int32s) are treated as a scanline, row major, top to bottom and left to right. The width of a glyph is not always a multiple of 4 pixels, so the scanline can wrap around, i.e., a new row of pixels can start in the middle of a 4-byte element. The start of a glyph, however, is always aligned on a 4-byte element of the TSFT array. The end of a glyph is padded with 0xDEAD.