State of Text Rendering 2024
(behdad.org)
from Chewy7324@discuss.tchncs.de to linux@lemmy.ml on 11 Jul 2024 10:49
https://discuss.tchncs.de/post/18711947
from Chewy7324@discuss.tchncs.de to linux@lemmy.ml on 11 Jul 2024 10:49
https://discuss.tchncs.de/post/18711947
[The author assumes] a high-level understanding of how text rendering works, for example, what shaping is. If that does not sound familiar to you, you might want to review State of Text Rendering (2009), and Modern text rendering with Linux: Overview (2019).
threaded - newest
I’m not entirely sure how I feel about fonts containing WASM code… It feels like we’re overcomplicating things a bit.
Don’t you want to run an ai assistant directly from your favourite font? /s
Fonts have been programs for a long time. Better to have the code in a safe VM than natively executed.
Do you have a link for that, or a term I can search for? I’m not finding anything about it.
Here are a couple of links that should be good starting points:
superuser.com/…/can-truetype-fonts-contain-malici…
…stackexchange.com/…/how-can-a-font-be-used-for-p…
That is interesting. WASM seems like it’s just a replacement for the TrueType hinting language (which is already a VM). So I guess it’s benefiting from a more standardised and audited virtual machine.
It’s also fairly limited to what it can do (source):
I don’t see how the mentioned future drawing API will fit into that though.
Yeah, the real benefit will be the ability to re-use well tested and hopefully even proven WASM VMs.
.