I contacted Kim Heino, author of BBBS regarding Utf-8. This was his response:   
      
   =============cut here===========   
   > but I'm wondering if BBBS supports utf-8 in the message areas, and if it   
   > doesn't, how much of a PIA it would be to incorporate it?   
      
   There are multiple levels to support UTF-8:   
      
   1) Full UTF-8 support, so that internal storage is UTF-8 etc.   
      
   2) Import support only, so that incoming UTF-8 is converted to limited local   
   storage format and some chars are lost in the process.   
      
   3) Export support.   
      
   Currently BBBS has limited import support only, no export. Having full UTF-8   
   is major work and it's not going to happen.   
      
   For new software the only sane option is number one, of course.   
      
   > it's just there's a fellow in makenl_ng who thinks this will be a simple   
   > change for Fidonet..   
      
   Having for example nodelist file in UTF-8 is okay, there's no problem in that.   
   Forcing UTF-8 in echo areas is a dead idea for two reasons:   
      
   1) UTF-8 support is so much work for old softwares that's impossible to do.   
      
   2) Fidonet already has ^ACHARSET-kludge line. Each message can already have   
   different charset, so that UTF-8 can be mixed with ISO 8859-15 etc in same   
   echo area, per message basis.   
      
   Forcing UTF-8 *only* instead of CHARSET-kludge is the wrong way. Allowing   
   UTF-8 in CHARSET is fine and is highly recommended.   
      
   =============cut here==========   
      
   Take care,   
   Janis   
      
   --- BBBS/Li6 v4.10 Dada-1   
    * Origin: Prism bbs (1:261/38)