Wanker.. The offset is the character offset in ram or vram. The raw data.
Wanker... It's always fixed to eitheir 8bit or 16bit multiplied by height! (which I would fix as well, btw)
Well that's upto the end user.. I'm not going to deside that
I, the end user, tell you this: fixing the width of a proportional font is a big waste of RAM (or VRAM).
Jus tuse a table with offsets and calculate the width (or - heck- even use 2 tables)!
width(C) = offset(C+1)-offset(C)
(It is decided)
That's why I have two tables. Well only one at the moment. But for proportional I will add another one
I, the end user, tell you this: fixing the width of a proportional font is a big waste of RAM (or VRAM).
Jus tuse a table with offsets and calculate the width (or - heck- even use 2 tables)!
width(C) = offset(C+1)-offset(C)
(It is decided)They are bitfons aurora, are you honestly suggesting msd bitshift his way through a gazillion bitvectors till he finds the start of a character? No, I didn't think so....
charaters will be always be rounded to a byte... but this doesn't mean a multiple of width 8 or 16