From jcowan@reutershealth.com Tue Sep 12 14:42:32 2000 Return-Path: Received: (qmail 32582 invoked from network); 12 Sep 2000 21:40:26 -0000 Received: from unknown (10.1.10.142) by m1.onelist.org with QMQP; 12 Sep 2000 21:40:26 -0000 Received: from unknown (HELO mail.reutershealth.com) (204.243.9.36) by mta3 with SMTP; 12 Sep 2000 21:40:25 -0000 Received: from reutershealth.com (IDENT:cowan@[192.168.3.11]) by mail.reutershealth.com (Pro-8.9.3/8.9.3) with ESMTP id RAA20531 for ; Tue, 12 Sep 2000 17:40:31 -0400 (EDT) Sender: cowan@mail.reutershealth.com Message-ID: <39BEA2C0.EB2ED67B@reutershealth.com> Date: Tue, 12 Sep 2000 17:40:16 -0400 Organization: Reuters Health Information X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5-15 i686) X-Accept-Language: en MIME-Version: 1.0 To: "lojban@onelist.com" Subject: Re: [lojban] Eating glass, events, and rape References: <20000912211446.26240.qmail@pi.meson.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: John Cowan "Mark E. Shoulson" wrote: > {tugni} isn't the right kind > of "consent"; nor {sarxe}. Hmm... Now that I've stated it as dependent on > resistance, what do you think of {se fapro gletu}, "opposed." That could > work. Other choices include {vlile}--which could just mean violent but > consensual, or {zekri}, which could mean incest or statutory rape, not > non-consensual. Something like {palci} is a value judgement, and makes a > statement rather than describes... maybe it could be understood, but it > isn't the point, at least not the one I was looking at. How about "narcrugle" from "na curmi gletu", with place structure "x1 does not permit that x1 copulates with x2"? That covers things that don't directly involve force as such. That would also be the first known example of a lujvo with "nar", representing a bridi negation. -- There is / one art || John Cowan no more / no less || http://www.reutershealth.com to do / all things || http://www.ccil.org/~cowan with art- / lessness \\ -- Piet Hein