sidorares
commented
6 years ago Sure, I'll have a look. A bit of documentation on how text is rendered with ntk
when you call .fillText it splits string into glyphs and calls
( "split into glyphs" is actually much difficult task in real life and would require harfbuzz library to du correctly, but for Latin scripts it mostly works juts by treating characters as glyphs )
When you specify font via something like `ctx.font = "Courier 10pt" this code is used:
- font file is located using font matcher library
- file is loaded using truetype2 moduly
- glyphset is created and each rendered glyph is uploaded to the server ( I'd like to change this part so that glyphs are uploaded lazily only at the point you use them, not the whole font upfront )
"Spaces show up as blocks" problem is likely located somewhere in last two steps ^.
Whenever a space character is rendered, it shows up as a block. I've tried lots of different fonts and I don't think it has to do with the fonts. The 2d context is causing this. Can we please have this fixed?