I am just experimenting with UTF-8 fonts.
And while it mostly worked so far (one font had i/o/u on a different baseline than the rest and 'a'),
also German öäü worked fine after I figured out that I had to tell Visual-Studio to save the source-file as UTF-8.
Converting fonts with the EVE Asset builder takes a lot of time though.
A tool to relocate fonts would be nice, something to feed a .xfont into plus an address that generates a new file
with re-calculated offsets.
What seems to be working is changing the compression speed to "veryfast", at least the .xfont that is generated for that using the same address is 100% the same as the one that was generated when using "thorough".
Edit: For the better part of the evening I was trying to put together a flash image with 5 fonts and a test-picture.
I stripped NotoSans-Regular.ttf of most of its 3426 glyhs using:
https://www.fontsquirrel.com/tools/webfont-generatorThe resulting notosans-regular-webfont.ttf only has 222 glyphs.
Then I converted the font using the EVE Asset Builder.
ASTC block footprints: Auto
Compression Speed: thorough
Addr of Font Data: FLASH
I did this for font-sizes of 12, 14, 16, 18 and 20.
At first I converted all fonts to FLASH address 4096.
Then I put together a flash file, putting .glyph and .xfont files in pairs in it:
notosans-regular-webfont_12_4096.glyph : 4096 : 119936
notosans-regular-webfont_12_4906.xfont : 124032 : 5056
notosans-regular-webfont_14_129088.glyph : 129088 : 120064
notosans-regular-webfont_14_129088.xfont : 249152 : 5056
notosans-regular-webfont_16_254208.glyph : 254208 : 269760
notosans-regular-webfont_16_254208.xfont : 523968 : 5056
notosans-regular-webfont_18_529024.glyph : 529024 : 270016
notosans-regular-webfont_18_529024.xfont : 799040 : 5120
notosans-regular-webfont_20_4096.glyph : 804160 : 180032
notosans-regular-webfont_20_804160.xfont : 984192 : 5120
chipsie_40x56_40x56_COMPRESSED_RGBA_ASTC_8x8_KHR.raw : 989312 : 576
Then I redid the .xfont files by re-compressing the fonts in "veryfast" for the addresses.
I wrote a litte test code, put in the numbers and got five lines of cmd_text() output.
Ah yes, I copied all the .xfont data to graphics memory and I used bitmap-handles 10...14.
Now, the problem was, only the first and the last line were okay, the other three had broken chars.
So I re-compressed the 14/16/18 fonts again in "thorough" for these addresses and replaced all files.
Now the third and the fourth line still have broken chars. And in different places.
So I started to hack this into a spreadsheet.
All the addresses are 64 byte aligned.
Then I tried to read notosans-regular-webfont_16_254208.xfont with a hex-editor.
0x0100aaff - signature
0x00001395 - size of 5013, gen-flash rounds that up to 5056 which is a multiple of 64
0x000093b5 - format
0x0000024a - swizzle
0x00000030 - width
0x00000006 - height
0x00000018 - pixel width
0x0000001e - pixel height
0x00801f08 - start -> 0x1f08 = 254208
0x00010000 - num of glyphs -> 65536 - this is wrong and the one other font (184 glyphs) I checked also had this number
gptr/wptr/widh data - not sure how to really interpret these
Now, what else could I try to put a bunch of fonts into the FLASH?
And on a side-note, the amount of bitmap-handles really is a tad bit low, having annother 32 at least would be nice.