Not really an issue, I just wanted to let you know I've implemented your font file formats in my
Scalable Screen Font library and font editor.
Just a humble suggestion, it would be much easier to parse .kbitx and .kbits files if the following 3 values were stored in properties / header: font's width, height (overall canvas size) and baseline. The first is max(x + w), the second max(baseline - y + h) and the last max(y) of every glyphs (as you can see, the second depends on the third, yet not stored like lineAscent for example).
Hi,
Not really an issue, I just wanted to let you know I've implemented your font file formats in my Scalable Screen Font library and font editor.
Just a humble suggestion, it would be much easier to parse .kbitx and .kbits files if the following 3 values were stored in properties / header: font's width, height (overall canvas size) and baseline. The first is max(x + w), the second max(baseline - y + h) and the last max(y) of every glyphs (as you can see, the second depends on the third, yet not stored like lineAscent for example).
Nice editor, btw!
Cheers, bzt