Closed Quorsor closed 1 year ago
This seems to be a limitation of the BDF format; CozetteVector gets built from the BDF file, which does not contain codepoints above U+FFFF
. It's something I would like to fix in the future, but that would mean rewriting the vector font build pipeline entirely - which I'm not too sure about comitting to, since Cozette is a bitmap font first and foremost and I don't test the Vector versions, nor can I verify that they work on Windows or Mac.
I got a step closer to fixing this with 1.19.2-hidpi; I have a proof-of-concept working, but I still need to fix the font metadata before I can export TTF from a "better" format.
Does this also make it any closer to bringing ligatures back in the roadmap?
Extremely unlikely. Everything is currently built from the bitmap font sources, which have no support for ligatures; to even start, I'd have to find a way to introduce ligatures at build time - which is already highly nontrivial and I'm not sure can be done here without writing a font compiler pretty much from scratch.
They finally work in 1.20.0 and also even works in Word.
This is on Windows 11, app is Powerpoint 365.
This is on the Windows 11 fonts settings
I tried putting it on the fonts settings and it shows the square instead of the symbol I'm looking for. I switched around otf and ttf to see if there are any differences but I found none.