Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 76  |
|  Carlos Navarro to Michiel van der Vlist  |
|  GoldEd UTF-8  |
|  01 Dec 22 19:34:09  |
 TID: FMail-W32 2.0.1.4 TZUTC: 0100 CHRS: UTF-8 4 MSGID: 2:341/234.1 6388f3a5 REPLY: 2:280/5555 6387cfcf 30 Nov 2022 22:40, you wrote to me: MV> I could type GPB or £ (Alt 156) and it will be correctly translated to MV> UTF-8 in my outgoing messages. The problem is /incoming/. Yes, I know. MV> I do not have control over that. What are the chances that an incoming MV> well formed UTF-8 sequence with the last byte is meant as a Pound sign MV> or as an 'a' with tilde? In /my/ case? Since I do not master the MV> portugese language and fidonet participants do not write to me in MV> Portugese, the chance that it is meant as a Pound sign is far greater MV> than it is meant as an 'a'with tilde. MV> Your case may be different... Yes, I prefer support for languages, more than for special symbols. Each case is different. :-) Anyway, a workaround could be: save one of the files with a different name, e.g. utf8_850alt.chs, then add this to golded.cfg: XLATCHARSET UTF8ALT CP850 utf8_850alt.chs Then you can press Ctrl-J and switch to UTF8ALT to view it with the "alternative" conversion. I've just done it now to be able to quote your pound sign above. ;-) Carlos --- GoldED+/W32-MSVC 1.1.5-b20180707 * Origin: cyberiada point (2:341/234.1) SEEN-BY: 106/201 114/705 123/120 124/5016 153/757 7715 154/10 203/0 SEEN-BY: 218/700 840 220/70 221/0 6 226/17 30 229/110 111 112 113 SEEN-BY: 229/114 317 426 428 470 700 240/1120 5832 250/5 8 267/800 SEEN-BY: 280/464 5003 5555 292/854 8125 298/25 301/1 305/3 310/31 SEEN-BY: 317/3 320/219 341/66 234 423/120 460/58 712/848 770/1 100 SEEN-BY: 770/340 772/210 220 230 PATH: 341/234 280/464 770/1 317/3 229/426 |
[ << oldest | < older | list | newer > | newest >> ]