Hello Björn!   
      
   03 Feb 14 18:59, you wrote to me:   
      
    BF>    Usually known as the ASCII characters higher than 0x7f.   
      
    There are no ASCII characters higher as 0x7f. The 8th bit depended on the   
    parity sceme used.   
      
    KvE>> Because there is no consensus on what is to be represented by these   
    KvE>> so called high-ASCII.   
      
    BF>    No need to. Every region (outside of Z1 and Z3) -- meaning parts of the   
    BF> world using completely different languages -- takes care of it's own. The   
    BF> rest can simply either ignore it or take the recent technical developments   
    BF> and handle it accordingly.   
      
    Apparently they do.   
      
    BF>>> many years now, and I'm still just Bj?rn in the nodelist there... :(   
      
    KvE>> It is not the magic on how it is to be done.   
      
    BF>    No magic needed. My 15yo Y2K patch can handle it.   
      
    Your patch can only be used on an obsolete OS.   
      
    BF>    Maybe you haven't have time to read my recent comments yet? What I'm   
    BF> asking is, why this option is even needed. And if it is, why is the   
    BF> default to have it disabled and not vice versa?   
      
    I have read a lot of comments and I have engaged in discussions on this   
    subject, maybe not in echo's that you read, but still.   
      
    KvE>> you have written there is no single way to write Bj?rn.   
      
    BF>    But there is! *I* write it the way I want it. In my Region20 file it's   
    BF> written the way I want it. That's simply the way *I* want it. Freedom of   
    BF> expression, anyone...?   
      
    Well so what is your problem? You have it your way where you decide,   
    others have it their way where they decide. I can assure you that the   
    nodelist looks very different, where I decide.   
      
    Have you ever looked at the distribution list compiled by Z3, it has been   
    totally different for many years.   
      
    KvE>> But I am still curious, what definition of high-ASCII will be used?   
      
    BF>    None at all. If we regard the nodelist as the simple, binary file that   
    BF> it was intended to be from the very beginning, we can put whatever   
    BF> characters that we want in there.   
      
    It has never been a binary file and during the time I have been in Fidonet,   
    it was never intended to be a binary file. It is a structured file and that   
    brings limitations. You must always consider that there is 15 old software   
    that has to parse the file. Using 2 byte characters could confuse the parser.   
      
   Kees   
      
   --- FPD v2.9.040207  GoldED+/LNX 1.1.5   
    * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)