Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 2226  |
|  Nicholas Boel to Vitaliy Aksyonov  |
|  Need volonteers to test another patch  |
|  02 Mar 24 14:44:42  |
 REPLY: 1:104/117 65e354b9 MSGID: 1:154/10 65e39208 CHRS: UTF-8 4 TZUTC: -0600 TID: hpt/lnx 1.9 2024-02-05 Hello Vitaliy, On Saturday March 02 2024 09:13, you wrote to me: VA> Most probably it was some combination which made it looking almost VA> correct. I think that screen may be the reason you saw pseudo-graphics I'm no longer using screen or tmux, and this version (along with all previous versions since you made the ncurses change) work the same and show UTF-8 properly, except for what you describe below: VA> more or less correctly. Remember those line wraps? That happens VA> because GoldEd converts those symbols to UTF-8 first. All VA> pseudo-graphics symbols represented as 3 bytes. So that line become 3 VA> times longer in bytes. Then GoldEd tries to split message to lines and VA> it uses bytes! not symbols. That's why it splits the line in the VA> middle of those pseudo-graphics. Even worse, it may tear apart one VA> UTF-8 symbol to two lines and it will be displayed incorrectly. Yeah, I've noticed most of this.. and thank you for your explanation. At least now I know why it is happening. VA> GoldEd cannot work correctly with multibyte sequences. And even if it VA> looks "correct", it's just because most English letters has same codes VA> in cp437 and UTF-8. Maybe simple ones, like german umlauts and whatnot. But cp437 doesn't have any Cyrillic, Greek, Japanese, Chinese, etc. VA> If you want to keep using UTF-8, I may only suggest to find version, VA> which "works" for you and stick to it. I already have! VA> Until full UTF-8 support implemented in GoldEd (if that ever happen), VA> don't expect it to work correctly, sorry. That's ok. I had it somewhat working for awhile, the latest reverts have changed that. I don't have an issue going back to a "lucky" version. ;) VA> It's your choice. Just be aware, that if it works - it's just pure VA> luck and don't expect it to last. Until we implement UTF-8 support. It VA> may take years. Or never happen. It's not so easy to do it with VA> backward compatibility wih all older systems like DOS or OS/2. I don't mind being lucky sometimes. Regards, Nick ... "Take my advice, I don't use it anyway." --- GoldED+/LNX 1.1.5-b20231112 * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10) SEEN-BY: 15/0 18/200 90/1 103/705 105/81 106/201 120/616 123/10 124/5016 SEEN-BY: 128/260 129/305 135/225 153/757 7715 154/10 30 40 50 700 SEEN-BY: 203/0 218/700 220/90 221/0 6 226/18 30 227/114 229/110 112 SEEN-BY: 229/113 206 307 317 400 426 428 470 664 700 240/1120 5832 SEEN-BY: 266/512 280/464 5003 5555 282/1038 291/111 292/854 8125 301/1 SEEN-BY: 310/31 320/219 322/757 341/66 234 342/200 396/45 423/120 SEEN-BY: 460/16 58 256 1124 5858 467/888 633/280 712/848 770/1 2320/105 SEEN-BY: 3634/12 5020/400 1042 5054/30 PATH: 154/10 280/464 460/58 229/426 |
[ << oldest | < older | list | newer > | newest >> ]