03-08-2025, 11:06 PM
https://www.unifoundry.com/unifont/index.html --> GNU Unifont has 65,536 characters stored inside one single font.
The way you use it (with QB64PE) is to _LOADFONT the font, then you format a string in UTF-8 normally, then you _UPrinttString to the screen.
It's a little more complex than ASCII-formatted text to deal with, as UTF-8 is a variable-length text. Due to the way those 65,536 characters are mapped, each one might be 5 or 6 bytes in that string. You can't just assume a 33-byte string is 33-characters in length, like with an ASCII string, and you can't just easily LEFT$ and RIGHT$ parts of it.
IF you have UTF-16 formatted strings (or UTF-32), you would still use _UPrintString to display them, and in many ways they're easier to deal with as every character is going to be 2 bytes (or 4 bytes).
But to *properly* use unicode, you have to write and save your strings in unicode. Having 65,536 glyphs available to use doesn't mean much when you strings only represent 256 characters that you're using out of that list.
The way you use it (with QB64PE) is to _LOADFONT the font, then you format a string in UTF-8 normally, then you _UPrinttString to the screen.
It's a little more complex than ASCII-formatted text to deal with, as UTF-8 is a variable-length text. Due to the way those 65,536 characters are mapped, each one might be 5 or 6 bytes in that string. You can't just assume a 33-byte string is 33-characters in length, like with an ASCII string, and you can't just easily LEFT$ and RIGHT$ parts of it.
IF you have UTF-16 formatted strings (or UTF-32), you would still use _UPrintString to display them, and in many ways they're easier to deal with as every character is going to be 2 bytes (or 4 bytes).
But to *properly* use unicode, you have to write and save your strings in unicode. Having 65,536 glyphs available to use doesn't mean much when you strings only represent 256 characters that you're using out of that list.