Modern UTF-8 encoding and present day tools makes it relatively easy to make many codepoints work relatively better even on DOS, thanks to readily available bitmap fonts.
Here's some code that's easy for a lot of people to play with, especially if you are looking to have it running on your firmware / other embedded projects.
Interesting. I wonder how memory is handled due to the # of potential characters in UTF-8, or maybe only a subset of characters are allowed. Or is there a TSR handling that from a database on disk.
I cannot get to the twitter site and xcancel just loops so I could n0t see the post.
Modern UTF-8 encoding and present day tools makes it relatively easy to make many codepoints work relatively better even on DOS, thanks to readily available bitmap fonts.
Here's some code that's easy for a lot of people to play with, especially if you are looking to have it running on your firmware / other embedded projects.
https://github.com/guilt/3DGFX
Interesting. I wonder how memory is handled due to the # of potential characters in UTF-8, or maybe only a subset of characters are allowed. Or is there a TSR handling that from a database on disk.
I cannot get to the twitter site and xcancel just loops so I could n0t see the post.
Here is the post:
https://xcancel.com/_vkaku/status/2071469740141224272
It's mainly just an image and link to
https://github.com/guilt/3DGFX
Check the commit history for the addition of Unicode