ml>> ok... have added utf-8 read translation in addition to the existing    
    ml>> iso translation in my xlat.cfg...   
      
    ml> as noted before, i've removed these again because they did not do what    
    ml> i expected...   
      
    BP> what did you expect ?   
      
   i expected it to work but there are obviously some parts missing...   
      
    BP> utf-8 is nice in the way nntp readers only need to support unicode,   
      
   ok...   
      
    BP> while ftn senders can use any charset supported in ftn networks,   
      
   and utf-8 readers can read them... but let's go the other way...   
      
    BP> this part works for me :)    
      
    ml> in the mean time, i've attempted to create a utf-8 to iso-8859-1 chs    
      
    BP> this table will loose chars from utf-8, so no go   
      
   then this is the problem... and is why i have attempted to create the reverse   
   crossover chart... i can't see where any letters would be lost but they would   
   be transliterated to their equivelant as has been done for a long time... for   
   most character sets, anyway...   
      
   )\/(ark   
      
    * Origin:  (1:3634/12)