Re: sh command bogus output in UTF-8 text

[Robert Elz <kre%munnari.OZ.AU@localhost>]

    Date:        Thu, 06 Feb 2020 15:36:08 +0900 (JST)
    From:        Jun Ebihara <jun%soum.co.jp@localhost>
    Message-ID:  <20200206.153608.846488818879034315.jun%soum.co.jp@localhost>

  | sh seems broken,e3-81-ab -> e3-81-81-ab

I will look into that, and see what is not being done that should be.
(0x81 is a magic character in sh strings that need to be processed, which
a here document with an unquoted end delimiter is, that is cat <<EOF
rather than cat <<'EOF') -- but that is supposed to be all cleared up
before the data ever leaves the shell.

This has nothing in particilar to do with UTF-8 (or any other character
encoding) which sh really knows nothing about at all (it should, for
some things, but simply doesn't).   When I saw the subject of the message
I was expecting to simply say "yes, known, in some future revision perhaps"
but that is not what this is, so it should get fixed quite soon!

kre