Return-Path: Received: from access1.digex.net by xiron.pc.helsinki.fi with smtp (Linux Smail3.1.28.1 #1) id m0qj05W-00005FC; Fri, 9 Sep 94 10:09 EET DST Received: by access1.digex.net id AA07457 (5.67b8/IDA-1.5 for veion@xiron.pc.helsinki.fi); Fri, 9 Sep 1994 03:09:26 -0400 Date: Fri, 9 Sep 1994 03:09:26 -0400 From: Logical Language Group Message-Id: <199409090709.AA07457@access1.digex.net> To: veion@xiron.pc.helsinki.fi Subject: Re: WWW Server Statistics Cc: lojbab@access.digex.net Content-Length: 1907 Lines: 34 Terminalk emulation is a functrion of my terminal software. I just need to learn how to use it and what if any limitatiosn it has, or use different software. Needless to say, I am trying not to spend time on this. Independent backup is always a good idea. Maybe we ought to exchange if I can find a way to send many many megabytes to you after you get the big disk %^) (I use stream tape with Colorado Systems 'Trakker' for my large scale backups if this means anything to you). VV>If digex has kermit available, you could first save things in pure VV> ASCII to digex and then download them with kermit. IRC may be a VV> problem, though. OTOH, if you can upload the IRC logs to xiron, VV> I can try filtering them with AWK (which I must learn very VV> thoroughly as it will be one of our main data filtering tools). The problkem is that terminal stuff uses codes to reposition the cursor. This often causes jumps all over the place. With IRC, for example, you get jumps back and forth betwen two places on the screen if two people are typing at once, with one character then control codes than another character and control codes - cut the control codes and you have gibberish since the text consists of two independent English (or Lojban! even worse) texts interspersed. YOu need a terminal emulation analyuzer that somehow recponstructs entire lines and knows when they are not changing any more - an AI taks that might require info abnout the specific program function in order to work. Thus, I end up editing manually, since I can tell more or less what the control codes are doing and more over I can recognize the text that results as being meaningful or not and thus check my readings of the codes. I though that gzip was NOT the same format as PKZIP. I recall someone once reporting that thgey were unable using PKUNZIP to expand the gzip files on the ftp server. lojbab