On Mon, 27 Mar 2023 Jude DaShiell wrote:
[My mail client is] alpine for now. If I can't fix it I'll have to
switch and that's alpine running on panix.com. I'll look through
the configuration and find what I can.
I read most email in a VT (ie, a linux console) with alpine. And I set
emacs as my editor in my alpine config.
When a message contains a few isolated unicode characters that the
VT's codeset* doesn't distinguish (displays as diamonds), I sometimes
start a reply (including original message), and then I can use emacs's
describe-char function to get descriptions of them.
A workaround, in other words.
On Mon, 27 Mar 2023, Greg Wooledge wrote:
On Mon, Mar 27, 2023 at 04:10:37PM -0400, Jude DaShiell wrote:
I'm using espeak-ng and reading this message with the symbols in it only
generated silence when trying to read the symbols.
AFAIK, all unicode characters are assigned unique descriptive names.
I'm using utf-8 here and don't have any kind of font chosen or set
so far as I know. On my end all of this is happening in the
console environment.
You may be using UTF-8 in your terminal, but your email was sent with
"7bit" encoding. The playing card suit glyphs were all replaced with
question marks.
So, I think there's something wrong in your mail client.
* From console-setup(5): "The font specification consists of three
parameters - codeset, font face and font size. The codeset
specifies what characters will be supported by the font."
--
Believe you do in the church, not infront of the computer, when we see
the output we can conclude ourself. -- deloptes
