Hello mark!   
      
   Thursday January 10 2013 14:47, mark lewis wrote to Michiel van der Vlist:   
      
    ml> why? why not just allow the the current set plus those above 127? i   
    ml> don't recall the nodelist being specified as CP437 but traditionally,   
    ml> that is what it has been...   
      
   The current version of FTS5000 specifies the 7-bit ASCII character set, with   
   only CR (0x0D), LF (0x0A), and EOF (0x1A) control characters permitted.   
      
    MvdV>> Correctly in what character encoding scheme?   
      
    ml> ewww... that's gonna be a very ugly can-o-worms :/   
      
   You can say that again!   
      
    MvdV>> So... /if/ we allow non ASCII in the nodleist, it will have to   
    MvdV>> be encoded as UTF-8.   
      
    ml> don't want to go there... it'll be almost the same "argument" that   
    ml> there was years ago about other changes in the nodelist... perhaps it   
    ml> would be better to have two formats... the traditional one opened up   
    ml> somewhat for characters above 127 and another one using utf-8 or so?   
      
   Since the nodelist defines FidoNet, I don't think we can really do that   
   without a mechanism for resolving differences between the two formats.   
      
   Andrew   
      
   ---   
    * Origin: Bits & Bytes BBS * V.Everything! * 860/535-4284 (1:320/119)