Return-Path: LOJBAN%CUVMB.BITNET@vms.dc.LSOFT.COM Received: from SEGATE.SUNET.SE (segate.sunet.se [192.36.125.6]) by xiron.pc.helsinki.fi (8.6.12/8.6.9) with ESMTP id BAA04256 for ; Fri, 8 Dec 1995 01:35:43 +0200 Message-Id: <199512072335.BAA04256@xiron.pc.helsinki.fi> Received: from listmail.sunet.se by SEGATE.SUNET.SE (LSMTP for OpenVMS v1.0a) with SMTP id 92573052 ; Fri, 8 Dec 1995 0:35:43 +0100 Date: Thu, 7 Dec 1995 18:34:11 -0500 Reply-To: Jorge Llambias Sender: Lojban list From: Jorge Llambias Subject: Re: TECH: PROPOSED GRAMMAR CHANGE X5: Restriction of JOI X-To: lojban@cuvmb.cc.columbia.edu, jorge@minerva.phyast.pitt.edu To: Veijo Vilva Content-Length: 1369 Lines: 37 lojbab: > Historically JOI entered the language as a tanru connective. > A black-and-red beach ball is neithr black nor red because it is > equally both. {ta xunre je xekri bolci} does not claim that the ball is black and that it is red, either, so it is a perfectly good translation. Tanru logical connectives are non-logical in the sense that they don't expand to two connected bridi like all the others. (It is not clear to me that you can't say {ta xunre} when ta is only partly but significantly red, but that is another issue, concerning how one understands the meaning of {xunre}.) > Thus JCB used "ze" which we made "joi". But JCB's language is not Lojban. Were JCB's tanru logical connectives shortened forms of full bridi? > nanmu jo'u ninmu jgina > presumably talks about all the non-Y chromosome genes. Why not {nanmu je ninmu jgina}? I suppose that the expanded tanru would be something like {jgina be lo'e nanmu .e lo'e ninmu}, so {je} is not perfect for the tanru, but how is {jo'u} any better? I suppose you would not be talking about {jgina be lo'e nanmu jo'u ninmu} any more than about {jgina be lo'e nanmu je ninmu}. > There - two joi tanru examples in 20 seconds. Well, I did admit that {joi} and {jo'u} were not meaningless, but I argued that they duplicate the job of {je}. Do you have examples with ce, ce'o, jo'e, ku'a, or pi'u? Jorge