Return-Path: <@CUNYVM.CUNY.EDU:LOJBAN@CUVMB.BITNET> Received: from kantti.helsinki.fi by xiron.pc.helsinki.fi with smtp (Linux Smail3.1.28.1 #1) id m0sx9CX-0000ZOC; Mon, 25 Sep 95 10:47 EET Received: from fiport.funet.fi (fiport.funet.fi [128.214.109.150]) by kantti.helsinki.fi (8.6.12+Emil1.1/8.6.5) with ESMTP id KAA20604 for ; Mon, 25 Sep 1995 10:47:49 +0200 Received: from CUNYVM.CUNY.EDU (MAILER@CUNYVMV2) by FIPORT.FUNET.FI (PMDF V5.0-3 #2494) id <01HVOX9K744G000XBW@FIPORT.FUNET.FI> for veion@XIRON.PC.HELSINKI.FI; Mon, 25 Sep 1995 11:47:57 +0200 (EET) Received: from CUNYVM.CUNY.EDU (NJE origin LISTSERV@CUNYVM) by CUNYVM.CUNY.EDU (LMail V1.2a/1.8a) with BSMTP id 1100; Thu, 21 Sep 1995 23:17:37 -0400 Date: Thu, 21 Sep 1995 23:17:04 -0400 (EDT) From: jorge@PHYAST.PITT.EDU Subject: Re: {soi} Sender: Lojban list To: Veijo Vilva Reply-to: jorge@PHYAST.PITT.EDU Message-id: <01HVOXAD54A4000XBW@FIPORT.FUNET.FI> Content-transfer-encoding: 7BIT X-To: lojban@cuvmb.cc.columbia.edu MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Length: 629 Lines: 18 And: > We should distinguish either between > sumti v. vlasui/sumvla > duu, bridi v. vlabri/brivla > (but this last standardly means selbrivla) > or > sibsui/sumsio v. sumti > duu, sibbri/brisio v. bridi > > The giuste supports the former. Actual usage supports the latter. That's my impression too. When I asked Goran whether he thought {mi sumti} or {zo mi sumti} was correct in some context like {mi klama}, he said that the second one was right. That's how we use "sumti", even though the definition suggests that {mi sumti} should be right. Jorge