REPLY: 1:154/10 65dd15c0
MSGID: 1:104/117 65ddeb6c
CHRS: US-ASCII 2
TZUTC: -0700
TID: hpt/lnx 1.9 2022-07-03
Hello Nicholas.

26 Feb 24 16:50, you wrote to me:

 ?aVA>>>>>> Especially if you have xlatcharsetalias entries in your
 ?aVA>>>>>> config.

 ?aWvV>>>>> I don't use any of those though...

 ?aVA>>>> But you have xlatcharset in your config. That was changed
 ?aVA>>>> too.

 ?aWvV>>> I don't have any in my standard configuration. But if I
 ?aWvV>>> include charsets.cfg from the project. All messages in the
 ?aWvV>>> stats area with linedrawing characters don't look ok. But
 ?aWvV>>> that's the same in the previous version of golded that I was
 ?aWvV>>> using.

 VA>> If you don't have any - pseudo-graphics won't work unless you
 VA>> have console in same encoding as message.

 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.

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

Vitaliy

--- GoldED+/LNX 1.1.5-b20240223
 * Origin: Aurora, Colorado (1:104/117)
SEEN-BY: 15/0 18/200 50/109 90/1 104/117 105/81 106/201 128/260 129/305
SEEN-BY: 135/225 153/7715 218/700 226/30 227/114 229/110 112 113 206
SEEN-BY: 229/307 317 400 426 428 470 664 700 266/512 280/464 5555
SEEN-BY: 282/1038 291/111 292/854 301/1 320/219 322/757 342/200 396/45
SEEN-BY: 460/16 58 256 1124 5858 463/68 467/888 633/280 712/848 3634/12
SEEN-BY: 5000/111 5001/100 5005/49 5015/46 5020/828 846 1042 4441
SEEN-BY: 5030/49 5054/8 30 5061/133 5075/128 5083/444 5090/958
PATH: 104/117 5020/1042 460/58 229/426