But Gary's multiple CHR$(160)s aren't ASCII
declare CHARSET=8859-1 for CHR$(160)
or
CHARSET=UTF-8 for CHR$(&hA0, &hC2) 'if poking a word C2A0
(the A0 is a coincidence because in UTF-8 bits 7 and 6 of byte 0 mark as multibyte character.)
or
CHARSET=UTF-16 for CHR$$(&h00A0)
Forcing a character from one CHARSET into an assumed other, or declared as other CHARSET is invalid from git-go. PICK ONE!
Comment