On Tue, 27 Feb 2024 12:59:54 -0700, Vitaliy Aksyonov -> Nicholas Boel wrote:

 NB>> This is why I wonder if he has a cp437 terminal setup, and this is why
 NB>> these messages look fine to him. Whereas, I'm using a utf-8 terminal
 NB>> so I have to translate everything to look ok.

 VA> Yes. You need to use translation in this case. The problem is that
 VA> GoldEd may translate from one byte charset to UTF-8, but not in reverse
 VA> direction yet. That mean that you'll be able to read messages, but not
 VA> write them. Actually, you'll be able to write them if no symbols with
 VA> codes > 127 are used. But CHRS kludge in message will look like UTF-8 2.

Yes, I've known this for quite some time. And my current issue has to do
with reading messages (the one we've been using as an example) specifically
translated from cp437 to utf-8.

Otherwise, if I absolutely have to reply to a message containing cp437
characters, I just don't quote those - as I know they won't be translated
properly.

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb