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