So why ask?

Maybe someone has some usefull remarks .

You mean like "you suck!" or something?

Wait, I have something more useful...

1) Proportional fonts. Shouldn't be too hard, just a small table as a 'parameter' which contains the width of each individual character.
2) The ability to use two fonts, one fill, one outline, for which you can specify a color each. The print version would then first print the outline in the background color, then the fill in the foreground color. Pretty useful when you're not sure on what type of background you're printing...

1) I've tought of propertianal fonts. And already have a flag for it. It already contains an offset table for each character ( you could also make a set with just a few chars). It's to slow to calculate the offset anyway and hard to make generic. The only thing I need to add for propertional is a table with character widths and some 1bit proportinal font data.
2) This can ofcourse already be done by printing a string twice . But maybe I can add something for it.
Any other ideas?

You don't calculate the offset you giant wank, just the width... You space 'em just the same way, in 16x16 or 8x8 blocks. Only, instead of being centered, all the chars are left-aligned. You even plot the characters as whole characters, the only thing different is that instead of increasing the new X position of the next character by the standard 16 or 8 pixels, you increase it by whatever width the width-table indicates... Now that, my friend, is how we do that...

(we of course being excessively lazy ppl like myself )

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

Quote:

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