ml> FWIW: i've also just posted a question in the GOLDED echo to see    
    ml> if the chs file format has changed since 2005...   
      
    PQ> That post hasn't appeared in my version of the echo, yet.   
      
   let me know if it doesn't appear over there ;)   
      
    ml> my thought is that if the format has not changed, then we could    
    ml> refresh our chs files from the GOLDED repository... for one thing,    
    ml> this should make more chs files available than the 8 standard and    
    ml> 5 unicode ones that come with jamnntpd...   
      
    PQ> I changed my ~xlat files yesterday to use GoldEd's "866_850.chs".    
    PQ> Of course, no one has yet attempted to post using CP866.  I've   
    PQ> checked the *.chs files, as you have no doubt also, and they seem   
    PQ> compatible (even the TimEd ones too, though the naming isn't).   
      
   TimED, the original one, also takes them and combines them into a binary file   
   for its use... i have no idea what the newer TimED does...   
      
    PQ> I have found a .PDF version of some notes on JamNNTPd put together   
    PQ> by Scott Street, which makes mention of the apparent compatibility   
    PQ> of the charset translation tables.  I don't know where I picked it   
    PQ> up from... oh, wait... it's in an archive called   
    PQ> JamNNTPd-1.2.3-Win32.zip (FREQ-able as JamNNTPd-1), dated June last   
    PQ> year.  I can't recall where I picked it up from... I've had a sleep   
    PQ> or two, since.  :)   
      
   ahh... that must be the one that he worked on adding a secure mode and   
   cleaning up some bugs... i've been waiting and waiting for some notice that it   
   has been accepted and merged into the main project repository with a new   
   release being available... my version is compiled locally on OS2 with EMX... i   
   can only hope that the new version, if/when it is released will also compile   
   the same ;)   
      
   )\/(ark   
      
   ---    
    * Origin:  (1:3634/12.42)