From pycyn@aol.com Wed Nov 06 07:16:08 2002 Return-Path: X-Sender: Pycyn@aol.com X-Apparently-To: lojban@yahoogroups.com Received: (EGP: mail-8_2_3_0); 6 Nov 2002 15:16:08 -0000 Received: (qmail 20212 invoked from network); 6 Nov 2002 15:16:08 -0000 Received: from unknown (66.218.66.217) by m1.grp.scd.yahoo.com with QMQP; 6 Nov 2002 15:16:08 -0000 Received: from unknown (HELO imo-m07.mx.aol.com) (64.12.136.162) by mta2.grp.scd.yahoo.com with SMTP; 6 Nov 2002 15:16:03 -0000 Received: from Pycyn@aol.com by imo-m07.mx.aol.com (mail_out_v34.13.) id r.1ba.901afec (4012) for ; Wed, 6 Nov 2002 10:15:57 -0500 (EST) Message-ID: <1ba.901afec.2afa8c2d@aol.com> Date: Wed, 6 Nov 2002 10:15:57 EST Subject: Re: [lojban] Re: What the heck is this crap? To: lojban@yahoogroups.com MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="part1_1ba.901afec.2afa8c2d_boundary" X-Mailer: AOL 8.0 for Windows US sub 230 From: pycyn@aol.com X-Yahoo-Group-Post: member; u=2455001 X-Yahoo-Profile: kaliputra X-Yahoo-Message-Num: 16945 --part1_1ba.901afec.2afa8c2d_boundary Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In a message dated 11/5/2002 7:42:57 PM Central Standard Time, lojban-out@lojban.org writes: << > This means that FA and SE can both change the actual meaning of > sentences. > > This is not explicitely stated anywhere, except maybe briefly in Chapter > 16, whereas it is apparently something that needs to be kept in mind at > all times. > > I repeat my request for an errata. >> Well, CLL doesn't have it wrong; it just may not have it right often enough to catch the casual reader's eye (and where it has it right may not be indexed in any reasonable way). But, if you follow the list at all, you will have seen cases of what happens with careless FA and SE discussed roughly every six months for as long as there has been a list (and before that as well back to 1976). It is about the third thing newbies get wrong and get corrected on, more or less gently (the first is {cu} and the second is usually {du} for predicate "is"). --part1_1ba.901afec.2afa8c2d_boundary Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: 7bit In a message dated 11/5/2002 7:42:57 PM Central Standard Time, lojban-out@lojban.org writes:
<<

This means that FA and SE can both change the actual meaning of
sentences.

This is not explicitely stated anywhere, except maybe briefly in Chapter
16, whereas it is apparently something that needs to be kept in mind at
all times.

I repeat my request for an errata.

>>
Well, CLL doesn't have it wrong; it just may not have it right often enough to catch the casual reader's eye (and where it has it right may not be indexed in any reasonable way).
But, if you follow the list at all, you will have seen cases of what happens with careless FA and SE discussed roughly every six months for as long as there has been a list (and before that as well back to 1976). It is about the third thing newbies get wrong and get corrected on, more or less gently (the first is {cu} and the second is usually {du} for predicate "is"). --part1_1ba.901afec.2afa8c2d_boundary--