TID: FMail-W32 2.1.3.7-B20170919   
   RFC-X-No-Archive: Yes   
   TZUTC: 0100   
   CHRS: UTF-8 4   
   MSGID: 2:280/5555 5e638704   
   REPLY: 2:240/6309 5e636c62   
   Hello Joachim,   
      
   On Saturday March 07 2020 10:40, you wrote to me:   
      
    MV>> IBMPC was indeed originally meant to be CP437. But somehow it   
    MV>> evolved to mean ANY IBM PC codepage and so another kludge was   
    MV>> introduced as an addendum. The CODEPAGE kludge. All that is   
    MV>> deprecated. The correct wat to indicate the encoding is the CHRS   
    MV>> kludge.   
      
   Ss documented in FTS-5003:  http://ftsc.org/docs/fts-5003.001   
      
    JP> Yes, I know, the mails in question do only have the IBMPC line, but   
    JP> before looking for misconfigurations on others, I thought getting   
    JP> clear that there is no misconfiguration on my side :)   
      
   This is what I have in my Golded.cfg:   
      
   XlatCharSetAlias LATIN-1 LATIN   
   XlatCharSetAlias LATIN-1 ISO-8859-1   
   XlatcharSetAlias LATIN-1 LATIN1   
   XlatCharSetAlias CP437 IBMPC   
   XlatCharSetAlias CP850 IBMPC   
   XlatCharsetAlias CP850 PC-8   
   XlatCharSetAlias CP1252 WINDOWS   
   XlatCharSetAlias NORWEIG ISO646-NO   
   XlatCharSetAlias DUTCH ISO664-NL   
   XlatCharSetalias SWEDISH ISO664-SE   
   XlatCharSetAlias SWEDISH ISO-60   
   XlatCharSetAlias CP866 +7_FIDO   
   Xlatcharsetalias CP866 +7   
      
      
   Cheers, Michiel   
      
   --- GoldED+/W32-MSVC 1.1.5-b20170303   
    * Origin: http://www.vlist.eu (2:280/5555)   
   SEEN-BY: 1/123 18/200 90/1 103/705 154/10 203/0 221/0 227/114 229/101   
   SEEN-BY: 229/426 452 1014 240/5832 249/206 317 400 280/464 5003 5555   
   SEEN-BY: 292/854 310/31 317/3 322/757 342/200 396/45 410/9 423/120   
   SEEN-BY: 633/280 712/848 770/1 2452/250 5019/40 5020/1042 5053/58   
   SEEN-BY: 5075/35   
   PATH: 280/5555 464 229/426