MSGID: 1:154/10 65de6ee8
REPLY: 1:104/117 65ddeb6c
PID: Smapinntpd/Linux 2.0 b20240216
CHRS: UTF-8 4
TZUTC: -0600
TID: hpt/lnx 1.9 2024-02-05
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
 * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)
SEEN-BY: 10/0 1 15/0 18/200 90/1 102/401 103/1 705 105/81 106/201
SEEN-BY: 120/616 123/10 128/260 129/305 135/225 153/7715 154/10 30
SEEN-BY: 154/40 50 700 214/22 218/0 1 215 601 700 720 840 860 870
SEEN-BY: 218/880 930 220/90 221/6 226/18 30 227/114 229/110 112 113
SEEN-BY: 229/206 307 317 400 426 428 470 664 700 266/512 280/464 282/1038
SEEN-BY: 291/111 292/854 301/1 320/219 322/757 342/200 396/45 460/58
SEEN-BY: 633/280 712/848 2320/105 3634/12
PATH: 154/10 301/1 218/700 229/426