Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    JAMNNTPD    |    Support for the JAMNNTPD software client    |    2,630 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 589 of 2,630    |
|    mark lewis to Bj”rn Felten    |
|    English_tutor    |
|    29 Apr 13 15:17:25    |
       ml> this last line doesn't exist in the original xlat file from the         ml> jamnntpd archive...               BF> My xlat file doesn't look anything like the original one. 8-)               i believe that ;)              mine didn't either when i started messing around with trying to support UTF-8       as well as the existing formats... i finally had to dump it all and go back       the the original xlat file that i started with to get things working properly       again...               BF> During the soon to be ten years I've dabbled with this, I've        BF> done numerous experiments with the xlat function. Still a process        BF> in progress...               i can understand that...              FWIW: i've also just posted a question in the GOLDED echo to see if the chs       file format has changed since 2005... my thought is that if the format has not       changed, then we could refresh our chs files from the GOLDED repository... for       one thing, this should make more chs files available than the 8 standard and 5       unicode ones that come with jamnntpd...              the idea is that not only are 437<->ISO needed but also 437<->850, 437<->865,       850<->865, etc are needed as well... unless there's a double xlat being done       where each is first xlated to ISO (for instance) and then xlated from that to       the destination chrs...              )\/(ark              ---         * Origin: (1:3634/12.42)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca