Hey Jame!   
      
    JC> Not that I could do much with such, since you're still not putting   
    JC> an copyright/license info in what you do make public   
      
   Not that it really matters in this case, given that I am making   
   no claim to nor distributing, modifying, the source code of any of   
   the applications called from any posted commandline or example text   
   script I am offering on the ftp site, here are some links that ought   
   to clear up any issues you may have;   
      
   The version of bash I am using claims this as it's license; License   
   GPLv3+: GNU GPL version 3 or later    
   and should cover the rest including Perl as per this link;   
   http://dev.perl.org/licenses/   
      
   The rest, coreutils, ascii2binary and sed, all point to   
   http://www.gnu.org/licenses/gpl.txt.   
      
   As for any scripts/functions originating from me I personally don't   
   feel any real ownership over them as most of them are derived from   
   other's examples of their usuage of these apps, especially sed.   
   What a boar's nest that is.  :-/   
      
   I like coreutils and try to employ those utils as much as possible.   
   The rest is pure bash.  If the headers were all 8 bit binary, or just   
   pure text, then I could have pulled this off with pure bash scripting   
   although fmt would more than likely still leaked in simply because   
   of backwards compatibilty but perhaps even for current compatibilty   
   since it does an outstanding job of word wrapping.   
      
   The only other thing I can think of that might not be covered by   
   the GPL is whatever editor one might call up for creating messages   
   but I think that is best left to the user to decide and there is   
   nothing in the current scripts/functions that marry any particular   
   editor into them.  Personally I use vim but have considered using   
   a pure bash scripted solution for this particular cause which would   
   make it more condusive to a typical BBS online 'editor', especially   
   if ANSI-fication was the goal.  Personally I like terminal based   
   solutions, remote or local, and something along this line might spark   
   some interest in good old fashioned BBSing just like Mom used to make.   
      
   Life is good,   
   Maurice   
      
   --- GNU bash, version 4.2.10(2)-release (x86_64-core2-linux-gnu)   
    * Origin: Pointy Stick Society (1:261/38.9)