REPLY: 2:5020/1042.3 7ff0654017b0   
   MSGID: 1:154/10 6546b010   
   CHRS: UTF-8 2   
   TZUTC: -0500   
   TID: hpt/lnx 1.9 2023-02-24   
   Hello golded+,   
      
   On Monday October 30 2023 23:53, you wrote to All:   
      
    gi> Legend: (A) Added, (C) Copied, (D) Deleted, (M) Modified, (R) Renamed,   
    gi>         (T) Type changed, (U) Unmerged, (X) Unknown, (B) Pairing   
    gi> Broken   
    gi> ===========================   
    gi> Fixed aliases processing.   
    gi> Author: Vitaliy Aksyonov   
    gi> <18148062+vitaliy-aksyonov@users.noreply.github.com>   
    gi> Date: 2023-10-30 14:03:12 -0600   
    gi> Committed by: Vitaliy Aksyonov   
    gi> <18148062+vitaliy-aksyonov@users.noreply.github.com>   
    gi> Files:   
    gi> M       golded3/geline.cpp   
    gi> M       golded3/gepost.cpp   
    gi> ===========================   
    gi> fix Codacy issues   
    gi> Author: Vitaliy Aksyonov   
    gi> <18148062+vitaliy-aksyonov@users.noreply.github.com>   
    gi> Date: 2023-10-30 14:03:12 -0600   
    gi> Committed by: Vitaliy Aksyonov   
    gi> <18148062+vitaliy-aksyonov@users.noreply.github.com>   
    gi> Files:   
    gi> M       golded3/geline.cpp   
    gi> ===========================   
    gi> detect zero conversion   
    gi> LoadCharset now detects when import and export charsets are the same.   
    gi> Restore previous charset will work faster.   
      
    gi> Author: Vitaliy Aksyonov   
    gi> <18148062+vitaliy-aksyonov@users.noreply.github.com>   
    gi> Date: 2023-10-30 14:03:12 -0600   
    gi> Committed by: Vitaliy Aksyonov   
    gi> <18148062+vitaliy-aksyonov@users.noreply.github.com>   
    gi> Files:   
    gi> M       docs/notework.rus   
    gi> M       docs/notework.txt   
    gi> M       golded.spec   
    gi> M       golded3/gecmfd.cpp   
    gi> M       golded3/geedit.cpp   
    gi> M       golded3/geline.cpp   
    gi> M       golded3/gelmsg.cpp   
    gi> M       golded3/gemlst.cpp   
    gi> M       golded3/gemnus.cpp   
    gi> M       golded3/gepost.cpp   
    gi> M       golded3/geprot.h   
    gi> M       golded3/gesoup.cpp   
    gi> M       goldlib/gall/gespell.cpp   
    gi> M       srcdate.h   
    gi> --- hpt/lnx 1.9.0   
    gi>  * Origin: Moscow, Russia (2:5020/1042.3)   
      
   Wondering if any one of these commits changed something in regards to a   
   workaround a small (probably very small) handful of people have been using   
   since about as far back as I can remember.    
      
   I'm currently using all available conversions (xlatcharset) to utf-8, with:   
      
   xlatimport utf-8   
      
   This has been swapped back and forth between cp437 and utf-8. It seems most   
   messages without a CHRS kludge are in the CP437 realm, but having a utf-8   
   terminal still doesn't display a lot of cp437 characters properly even with   
   the conversion tables, and I understand why (256 character limit).   
      
   xlatexport utf-8   
   xlatlocalset utf-8   
      
   Then I'm using a conversion table simply named utf_utf.chs with the following:   
      
   [begin utf_utf.chs]   
      
    This file is a charset conversion module in text form.   
      
   100000          ; ID number (when >65535, all 255 chars will be translated)   
   0               ; version number   
      
   4               ; level number   
      
   UTF-8   
   UTF-8   
      
   END   
      
   [end utf_utf.chs]   
      
   This was only to trick Golded into using the 'CHRS: UTF-8 4' kludge, otherwise   
   it would always post with 'CHRS: UTF-8 2', which is basically irrelevant. This   
   makeshift conversion table doesn't seem to be working any more for that   
   purpose.   
      
   Using tmux with Golded, and an external editor (nano or vim) this has allowed   
   me to read and write utf-8 messages properly for quite some time (and really,   
   nothing has changed recently except the CHRS kludge. ;))   
      
   I guess, instead of asking for this workaround to work again (if any of the   
   above has actually done something to break/fix this; however you want to look   
   at it), maybe I should be asking the question to actually change/fix the issue   
   instead.   
      
   When posting outgoing messages with 'xlatexport utf-8' is there an easy way to   
   hard code using the proper 'CHRS: UTF-8 4' kludge instead of it using the   
   level 2 parameter?   
      
   Regards,   
   Nick   
      
   ... "Take my advice, I don't use it anyway."   
   --- GoldED+/LNX 1.1.5-b20231030   
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)   
   SEEN-BY: 1/120 123 10/0 1 15/0 18/0 200 50/109 80/1 90/1 102/401 103/1   
   SEEN-BY: 103/705 104/117 105/81 106/201 116/116 120/616 123/0 10 25   
   SEEN-BY: 123/131 180 200 755 3001 129/305 135/115 300 153/7715 154/10   
   SEEN-BY: 154/30 40 50 700 214/22 218/0 1 215 601 700 720 840 860 870   
   SEEN-BY: 218/880 930 220/90 221/1 6 222/2 226/18 30 227/114 229/110   
   SEEN-BY: 229/112 113 206 307 317 400 426 428 452 470 664 700 240/1120   
   SEEN-BY: 250/1 266/512 275/1000 280/464 5555 282/1038 291/111 292/854   
   SEEN-BY: 299/6 301/1 113 123 812 305/3 317/3 320/219 322/757 335/364   
   SEEN-BY: 341/66 342/200 396/45 460/58 463/68 467/888 633/280 712/848   
   SEEN-BY: 712/1321 2320/105 3634/0 12 27 57 119 5000/111 5001/100 5005/49   
   SEEN-BY: 5015/46 5020/828 846 1042 4441 5030/49 5054/8 5061/133 5075/128   
   SEEN-BY: 5083/444 5090/958   
   PATH: 154/10 3634/12 5020/1042 301/1 218/700 229/426