Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 2647  |
|  August Abolins to Wilfred van Velzen  |
|  adhoc origin line feature  |
|  18 Jan 22 08:15:00  |
 MSGID: 2:221/1.58@fidonet f88bceaa REPLY: 2:280/464 61e6b95a PID: OpenXP/5.0.51 (Win32) CHRS: CP437 2 TZUTC: -0500 Hello Wilfred! ** On Tuesday 18.01.22 - 13:58, you wrote to me: AA>> @PID: OpenXP/5.0.51 (Win32) AA>> @CHRS: ASCII 1 WvV> ^^^^^^^ AA>> * Origin: CommeCi, Comme€a, QueSeraSera, OoblaDeeOoblaDaa. WvV> ^^ WvV> There's also the above problem... WvV> (And yes I know my "@CHRS: UTF-8 2" kludge isn't correct ;-)) The "€a" char made it back intact here. But your observation is useful. Perhaps the @CHRS detection in OpenXP should extend to looking at the characters in the Origin line as well. I believe the FTSC spec defined the "message body" to include the text in the Origin line. This reply will have no special chars in the Origin line. Prehaps the @CHARS line will be different now. -- ../|ug --- OpenXP 5.0.51 * Origin: The ONLY point that matters! --> . <-- (2:221/1.58) SEEN-BY: 1/123 14/0 15/0 30/0 90/1 103/705 105/81 106/201 120/340 SEEN-BY: 123/131 129/305 153/7715 203/0 218/700 221/1 6 360 226/30 SEEN-BY: 227/114 229/110 307 317 400 424 426 664 700 240/1120 5832 SEEN-BY: 249/206 266/512 280/464 5003 282/464 1038 292/854 301/0 1 SEEN-BY: 301/101 113 317/3 320/219 322/757 335/364 342/200 396/45 SEEN-BY: 423/81 633/280 712/848 920/1 5058/104 PATH: 221/1 301/1 229/426 |
[ << oldest | < older | list | newer > | newest >> ]