TID: FMail-lnx64 2.1.0.18-B20170815
RFC-X-No-Archive: Yes
TZUTC: 0100
CHRS: UTF-8 2
PID: GED+LNX 1.1.5-b20161221
MSGID: 2:280/464 61e6c2c9
REPLY: 2:221/1.58@fidonet f88bceaa
Hi August,

On 2022-01-18 08:15:00, you wrote to me:

 AA> @CHRS: CP437 2

 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...

 AA> The "€a" char made it back intact here. But your observation is
 AA> useful.  Perhaps the @CHRS detection in OpenXP should extend to
 AA> looking at the characters in the Origin line as well.  I
 AA> believe the FTSC spec defined the "message body" to include the
 AA> text in the Origin line.

Since there is only one way/place to define the used character set for a
message, it applies to the complete message... Or maybe it is defined
somewhere that an origin line, and the header fields should be strict ascii...
But then we couldn't have names with high ascii/utf in them. Which isn't
current practice...

 AA> This reply will have no special chars in the Origin line.
 AA> Prehaps the @CHARS line will be different now.

The @CHRS (not @CHARS) kludge is indeed different.

Bye, Wilfred.
--- FMail-lnx64 2.1.0.18-B20170815
 * Origin: FMail development HQ (2:280/464)
SEEN-BY: 1/123 14/0 15/0 30/0 90/1 103/705 105/81 106/201 120/340
SEEN-BY: 123/131 124/5016 129/305 153/757 7715 154/10 203/0 218/700
SEEN-BY: 221/0 1 6 226/30 227/114 229/110 307 317 400 424 426 664
SEEN-BY: 229/700 240/1120 5832 249/206 266/512 280/464 5003 282/464
SEEN-BY: 282/1038 292/854 8125 301/0 1 101 113 310/31 317/3 320/219
SEEN-BY: 322/757 335/364 341/234 342/200 396/45 423/120 633/280 712/848
SEEN-BY: 770/1 920/1 2452/250 5058/104
PATH: 280/464 301/1 229/426