On Wed, 28 Feb 2024 05:53:06 -0700, Vitaliy Aksyonov -> Nicholas Boel wrote:

 VA> I played with your configuration and have a good and bad news for you.

 VA> Good:
 VA> - I reproduced your issue.
 VA> - GoldEd correctly converts pseudo-graphics from cp437 to utf-8.

Well, it did. Until you reverted those changes. :(

 VA> Bad:
 VA> - GoldEd does not support unicode. Even if you compile it with ncursesw,
 VA> it still uses non unicode versions of functions to print text. That's
 VA> why you see those escape sequences instead of pseudo-graphics symbols.

Something happened recently where it made it quite a bit worse. I was
reading utf-8 Cyrillic, Greek, Japanese, Chinese, etc just fine in Golded
until the most recent version.

What changed with the ncurses init that was reverted?

And why does that change affect me opposite of a cp437 locale user?

If all I'm doing is translating from cp437 to utf-8 (or anything to utf-8)
I should still be able to read it properly, as I have been.. until
recently. Whatever you were doing with ncurses init helped me. I was able
to read utf-8 messages perfectly fine. Almost every single "Merry
Christmas" or "Happy New Year" Michiel posts yearly (except maybe a 2 or 3)
were perfectly readable in Golded. The latest version they are not.

 VA> I still suggest you to use one-byte locale for GoldEd. And remember, you
 VA> don't need to switch whole system to that locale, because in Linux
 VA> locale is a property of a process. So you may have UTF-8 everywhere and
 VA> cp437 for GoldEd. Most of terminals (including Putty) support different
 VA> charsets.

I'll pass on the suggestion :). I'll just keep using the last version that
worked for me (minus a couple badly displayed ascii line characters, and
keep testing newer versions to see if I ever get the display back that I
lost. :)

 VA> Another option - is to use external editor, but that won't help you with
 VA> message reader.

I already do this (I have always used nano with Golded). Viewing and
writing in an external editor has never been a problem. Until recently,
only reading became an issue. So the whole time it was working for me you
actually broke something instead? :((

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