Hi,
That's cool. UTF-8 sometimes does bother ( there at Linux distros from the Slackware family for instance, just say 13.1 versions and perhaps newer ones, having windows partitions to be backup, what a headache due the encoding, they don't even "speak" the same UTF-8 )
Indeed ( don't ask me "when was that?", i guess it by 2019 or so ),
Surprisingly or not, a whole conference ran somewhere at USA entirely about Unicode ( that weird idea about grouping charset tables and more ).
Just like that, due C++ programners have to deal with it and often find trouble over there. bad conversions, ... data corruptions, ..
Then i said, wait, it must be a stub, sure yes, not the complete thing ( unicode ).
Cheers.
P.S.: Hey!, look, you know, modern gnu bash implementations bring as part of coreutils an echo command with a -e option, the you double quote an escape sequence like in: echo -e "\x2f" for printing things if you did enter them as is, would be interpreted in a wrong way due consisting of characters with a special purpose.
Greek, Hebrew, .. and other characters may have a similar way to be "safely" placed in outputs.
But what happens when they are already present inside a script GP must read ?
skipping the script due ambiguous or unknown representations, sounds to me the wise choice.
Cheers