Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
On 06/06/2560 14:37, George wrote:
> As it stands, it's possible in Bash to use bytes in the 0x80-0xFF range as
> part of function names, for instance, because the Bash parser treats all of
> these byte values as valid "word" characters. This makes the Bash parser
> fairly "encoding neutral", which is why scripts using non-ASCII characters in
> command names or function names work even if the script is run on a different
> locale in current versions of Bash. Bash just ignores the issue, and
> that works for a fair number of encodings.
Thanks for the elucidation. Sorry, my terminology was off. I meant to
say, same glyphs, different encodings/locale. A TIS-620 encoded script
works in UTF-8, like you said above.
Peter