Subj : Changes in golded+ sources To : golded+ inspector From : Nicholas Boel Date : Sat Nov 04 2023 10:48 am 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) .