From arosta@uclan.ac.uk Wed Nov 14 05:45:22 2001 Return-Path: X-Sender: arosta@uclan.ac.uk X-Apparently-To: lojban@yahoogroups.com Received: (EGP: mail-8_0_0_1); 14 Nov 2001 13:45:22 -0000 Received: (qmail 522 invoked from network); 14 Nov 2001 13:45:21 -0000 Received: from unknown (216.115.97.171) by m2.grp.snv.yahoo.com with QMQP; 14 Nov 2001 13:45:21 -0000 Received: from unknown (HELO com1.uclan.ac.uk) (193.61.255.3) by mta3.grp.snv.yahoo.com with SMTP; 14 Nov 2001 13:45:20 -0000 Received: from gwise-gw1.uclan.ac.uk by com1.uclan.ac.uk with SMTP (Mailer); Wed, 14 Nov 2001 13:21:37 +0000 Received: from DI1-Message_Server by gwise-gw1.uclan.ac.uk with Novell_GroupWise; Wed, 14 Nov 2001 13:57:38 +0000 Message-Id: X-Mailer: Novell GroupWise 5.5.2 Date: Wed, 14 Nov 2001 13:56:56 +0000 To: lojban Subject: RE: [lojban] Why is there so much irregularity in cmavo/gismu? Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline From: And Rosta X-Yahoo-Profile: andjamin X-Yahoo-Message-Num: 12124 >>> Craig 11/13/01 10:43pm >>> #>> Oh, and I seem to rememeber you using 'xu' and '.ui' the last time this #>> came up. Is 'xu' being in UI the only thing that bothers you about se #>> cmavo? If you want to junk something, I'd hope there is at least more than #>> one instance of it annoying you. # #I missed this comment the first time, so I will respond now. The answer is #that xu and .ui are a particularly blatant example, but far from the only #one.=20 it's not that good an example, because {xu} really ought to have been=20 in JAhA (the ja'a/na selmaho), so this is an example of a misplaced cmavo r= ather than an example of a totally screwed up selmaho system. --And.