From pycyn@aol.com Sun Jul 22 12:20:03 2001
Return-Path: <Pycyn@aol.com>
X-Sender: Pycyn@aol.com
X-Apparently-To: lojban@yahoogroups.com
Received: (EGP: mail-7_2_0); 22 Jul 2001 19:20:03 -0000
Received: (qmail 28892 invoked from network); 22 Jul 2001 19:20:02 -0000
Received: from unknown (10.1.10.142) by l9.egroups.com with QMQP; 22 Jul 2001 19:20:02 -0000
Received: from unknown (HELO imo-d03.mx.aol.com) (205.188.157.35) by mta3 with SMTP; 22 Jul 2001 19:20:02 -0000
Received: from Pycyn@aol.com by imo-d03.mx.aol.com (mail_out_v31.9.) id r.e4.18250761 (3877) for <lojban@yahoogroups.com>; Sun, 22 Jul 2001 15:20:01 -0400 (EDT)
Message-ID: <e4.18250761.288c8160@aol.com>
Date: Sun, 22 Jul 2001 15:20:00 EDT
Subject: Re: [lojban] On a number of parts of threads and single threads disguised as sev
To: lojban@yahoogroups.com
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_e4.18250761.288c8160_boundary"
X-Mailer: AOL 6.0 for Windows US sub 10531
From: pycyn@aol.com

--part1_e4.18250761.288c8160_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Is it time for the sesquennnial plan to split the list into several or to 
label each message with a code about what kinds to topics are to be dealt 
with? I don't expect it to work a lot better than in the past, for, despite 
frequent claims to the contrary, all these things tend to work together: 
theoretical points tend toa rise out of practical problems and return to them 
for support and testing. And even the most remote issues seem to come back 
around to problems with Lojban text -- creation or interpretation. If it is 
weird, skip it for a while, but keep an eye on it for solutions to problems 
-- or, at least, discussion of problems you may have. If you ask a question 
and the answer seems to wander off, stick with it-- it will come back again, 
even if only to say that the hot shots are as confused as you are about how 
to do it. And that means that your solution may well be the best one -- yet, 
anyhow. 

--part1_e4.18250761.288c8160_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><BODY BGCOLOR="#ffffff"><FONT SIZE=2>Is it time for the sesquennnial plan to split the list into several or to 
<BR>label each message with a code about what kinds to topics are to be dealt 
<BR>with? &nbsp;I don't expect it to work a lot better than in the past, for, despite 
<BR>frequent claims to the contrary, all these things tend to work together: 
<BR>theoretical points tend toa rise out of practical problems and return to them 
<BR>for support and testing. &nbsp;And even the most remote issues seem to come back 
<BR>around to problems with Lojban text -- creation or interpretation. &nbsp;If it is 
<BR>weird, skip it for a while, but keep an eye on it for solutions to problems 
<BR>-- or, at least, discussion of problems you may have. &nbsp;If you ask a question 
<BR>and the answer seems to wander off, stick with it-- it will come back again, 
<BR>even if only to say that the hot shots are as confused as you are about how 
<BR>to do it. And that means that your solution may well be the best one -- yet, 
<BR>anyhow. &nbsp;</FONT></HTML>

--part1_e4.18250761.288c8160_boundary--

