printing characters > chr$(127)

[SMcNeill]

If you click and expand the image above, you'll see that the STARTCHAR for 128 isn't what you'd expect to be seeing here.

I don't have time tonight to dig into it (it's past mine and my little doggo's beddy bye time), but you may try and use _MAPUNICODE to get the QB64 unicode character value for that character and plug it in instead of 128.  

If you remember, we use _MAPUNICODE to make those extended characters to the upper 128 ASCII codes, depending on which code page is in use.  If I had to guess, I'd guess the glitch is in there.

---

Code: (Select All)

temp$ = Chr$(128)

Print Asc(temp$)

Print _MapUnicode(128)

For example, with the above, you can see that ASCII 128 actually comes from UNICODE 199. Instead of trying to map to 128, map to 199 instead.