REPLY: 1:153/7001.2989 5cabb62d   
   MSGID: 1:3634/12.73 5cabcbb0   
   PID: GED+LNX 1.1.5-b20180707   
   CHRS: CP437 2   
   TZUTC: -0400   
   TID: hpt/lnx 1.9.0-cur 07-09-15   
      
    On 2019 Apr 08 20:59:24, you wrote to me:   
      
    ml>> yes, as i've noted in this thread previously   
      
    MK> I must have missed that but now that you bring it up I will start   
    MK> paying attention to it.  Usually when I see 8 bit characters I tend to   
    MK> think of them as printable such as your cp437 example of 0x8d and not   
    MK> control codes. It is easy enough to scan for.   
      
   not a problem...   
      
    ml>> so someone using notepad as their editor is breaking FTN   
    ml>> standards?   
      
    MK> That isn't what I meant.   
      
   i know... i was being facetious :)   
      
    MK> All I meant is that 0x8d must not be an approved control code  given   
    MK> that if exists in a message it should be ignored.   
      
   it should be ignored, yes, as far as processing goes... reader software that   
   can act on it may still act... the problem there would be the same as forced   
   wrapping to a certain terminal width... granted, this is not mentioned but we   
   need to look at the given spec in the same level it was written for... by that   
   i mean tossers should not mess with it... mailers won't because they don't   
   look at messages at that level... so that leaves BBS software and users'   
   readers...   
      
    MK> However the mention of it must have meant that there was software that   
    MK> produced 0x8d as soft line feeds or soft carriage returns despite   
    MK> there being no indication of what software that was and still might   
    MK> be.   
      
   true...   
      
    MK> The only reference I can find pertains to c1 codes and IBM,   
    MK> specifically 0x85 as a replacement for \r\n which are liberally used   
    MK> in MS and DOS-think software to terminate lines.  I am betting notepad   
    MK> is one of them that uses \r\n rather than 0x85 ... or 0x8d for that   
    MK> matter.   
      
   right but again, we're talking about fidonet... not any docs from IBM, AT&T,   
   USC, RFCs, or other similar so-called ""official"" documentation... remember,   
   some of the folks in fido's heyday were professional programmers and document   
   writers... they brought some of that knowledge to fidonet but they also used   
   their own ideas... the rest of "us" merely followed along and tried to be   
   conformant to what was written and how it was documented...   
      
   i was going to write more and a little better but my meds are kinda kicking in   
   ATM...   
      
   )\/(ark   
      
   Always Mount a Scratch Monkey   
   Do you manage your own servers? If you are not running an IDS/IPS yer doin' it   
   wrong...   
   ... Ye didna' tell him how long it would REALLY take, did ye?   
   ---   
    * Origin:  (1:3634/12.73)   
   SEEN-BY: 1/120 15/2 18/0 200 116/116 123/0 25 50 150 755 1970 135/300   
   SEEN-BY: 153/7001 7715 154/10 20 30 40 700 203/0 221/0 1 6 360 226/17   
   SEEN-BY: 227/400 229/107 354 426 452 1014 230/0 240/5832 249/206 317   
   SEEN-BY: 249/400 261/38 280/464 5003 317/3 320/219 322/757 340/800   
   SEEN-BY: 342/200 393/68 460/58 633/0 267 280 281 412 640/1321 1384   
   SEEN-BY: 712/848 3634/0 12 15 27 50   
   PATH: 3634/12 154/10 221/6 1 640/1384 633/280 229/426