BF>    Since my 2:203/6 entry still doesn't compile, I guess we're still   
    BF> stuck with the 26 character set, dictated by zone 1? Can this really   
    BF> be true, in this year of 2013?   
      
    MvdV> I am all for lifting the ASCII only limitation for the nodelist.   
    MvdV> Seo Andrew how about an option:   
      
    MvdV> AllowNonAscii 0|1    ??   
      
   why? why not just allow the the current set plus those above 127? i don't   
   recall the nodelist being specified as CP437 but traditionally, that is what   
   it has been...   
      
    BF>    If you had rather used my Y2K patched version (where the outdated   
    BF> 26 character limitation was one of corrections I made), available for   
    BF> more than 12 years now, 2:203/6 would read correctly.   
      
    MvdV> Correctly in what character encoding scheme?   
      
   ewww... that's gonna be a very ugly can-o-worms :/   
      
    MvdV> Because here is where I see an issue. If 7 bit only was forced on   
    MvdV> us by what now is a majority, we do not want to do the same unto   
    MvdV> others do we? I strongly suspect that you used an 8 bit character   
    MvdV> set for your Umlaut experiment. Like CP850 or Latin-1. That is   
    MvdV> fine for us Western Europeans who need umlauts and accnets.  But   
    MvdV> not so fine for what is now the majority: those who use a   
    MvdV> cyrillic character set for their native languages. It is them   
    MvdV> that are the majority now. They need CP866 or KOI8R...   
      
   so from a human aspect, if one cannot read cryllic, how is one supposed to   
   address messages to someone using cryllic glyphs? address numbering aside, how   
   can they tell they are choosing the proper entry from the nodelist?   
      
    MvdV> Surely we do not want to force CP850 or Latin-1 one onto them do   
    MvdV> we?    
      
   what are they using now for communicating with the rest of the network?   
      
    MvdV> Unfortunately I see no practical way to swicth charactere   
    MvdV> encoding on the fly in the nodelist. Also unfortunately there is   
    MvdV> no 8 bit character set that covers both umlauts, accents AND   
    MvdV> cyrillic.   
      
   agreed... the nodelist is the glue that holds the network together... as such,   
   there must be a baseline that all systems and participants can use, IM(H)O...   
      
    MvdV> So... /if/ we allow non ASCII in the nodleist, it will have to be   
    MvdV> encoded as UTF-8.   
      
   don't want to go there... it'll be almost the same "argument" that there was   
   years ago about other changes in the nodelist... perhaps it would be better to   
   have two formats... the traditional one opened up somewhat for characters   
   above 127 and another one using utf-8 or so?   
      
   )\/(ark   
      
   ---    
    * Origin:  (1:3634/12.42)