MSGID: 1:154/10 65dfd0bc   
   REPLY: 1:104/117 65ded991   
   PID: Smapinntpd/Linux 2.0 b20240216   
   CHRS: UTF-8 4   
   TZUTC: -0600   
   TID: hpt/lnx 1.9 2024-02-05   
   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   
    * 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 124/5016 128/260 129/305 135/225 153/757 7715   
   SEEN-BY: 154/10 30 40 50 700 203/0 214/22 218/0 1 215 601 700 720   
   SEEN-BY: 218/840 860 870 880 930 220/90 221/0 6 226/18 30 227/114   
   SEEN-BY: 229/110 112 113 206 307 317 400 426 428 470 664 700 240/1120   
   SEEN-BY: 240/5832 266/512 280/464 5003 5555 282/1038 291/111 292/854   
   SEEN-BY: 292/8125 301/1 310/31 320/219 322/757 341/66 234 342/200   
   SEEN-BY: 396/45 423/120 460/58 467/888 633/280 712/848 770/1 2320/105   
   SEEN-BY: 3634/12 5020/400   
   PATH: 154/10 280/464 103/705 218/700 229/426