Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    MAKENL_NG    |    MakeNL Next Generation.    |    1,725 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 1,194 of 1,725    |
|    Kees van Eeten to Björn Felten    |
|    The seven-bit restriction    |
|    03 Feb 14 17:42:50    |
      Hello Björn!              03 Feb 14 16:45, you wrote to All:               BF> Just out of curiosity: why in Heavens Name are you keeping the seven-bit        BF> restriction in the program?               BF> Already in 1999 when I hacked the EXE-file and made it Y2K compliant, I        BF> removed that restriction. Those of you who have used my patch from then no        BF> longer have a robot that changes hi-ASCII characters to a "?".               Just out of curiosity, what is high-ASCII ?               BF> So why, why, why? Why does this "new" version have this        BF> restriction?               Because tere is no consensus on what is to be represented by these so called        high-ASCII.               BF> Check out the listing of 2:203/6 to see what little progress we        BF> have        BF> made for soon to be 15 years. I've had that listing, properly spelled, for        BF> many years now, and I'm still just Bj?rn in the nodelist there... :(               It is not the magic on how it is to be done.               The option for the control file to enable 8 bit characters is Allow8Bit and        should then be set to "1".               It was added as an option in v3.4.0 dated October 6, 2013 on popular request        by Michiel van der Vlist and possibly others.               As you will have seen, in many answers that have responded to messages that        you have written there is no single way to write Bj?rn.               Apparently many use what they call a codepage, that defines what their system        presents as high-ASCII.               In messages however, many claim, that there is a CHRS kludge in the message,        that tells you about the used codepage.               That is however of little use if you are generating a messages index and        for speed only read the binary header.               With nodelist there is no CHRS klude, so what is the default.               Now if you could arrange, that the sysops of fidonet come to a consensus        to what high-ASCII is, I am certain that the ZC's will cooperate and        enable the use of 8bit characters at their level.               Apparently I overlooked a message in REGCON.EUR, it seems that Ward has        enabled the option already               But I am still curious, what definition of high-ASCII will be used?              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)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca