Received: from mail-lb0-f192.google.com ([209.85.217.192]:40910) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1XeJsg-0005DA-VZ for lojban-list-archive@lojban.org; Wed, 15 Oct 2014 01:24:32 -0700 Received: by mail-lb0-f192.google.com with SMTP id n15sf61098lbi.19 for ; Wed, 15 Oct 2014 01:24:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:x-original-sender:x-original-authentication-results :reply-to:precedence:mailing-list:list-id:list-post:list-help :list-archive:sender:list-subscribe:list-unsubscribe:content-type; bh=NavYgkI0rzmKwGmclq83jANAxLgkPkPpuEu5iqG2Ffs=; b=D3hDcSW8NVRxHkdyiHx6nBTUVNhI/EJr2TOLI5sTh3aJ7a9aRtRGvYHs/YOxPjVdFA N0+frT1vWODzZPeBbBu+MILUrbCQksR98xD9/YXvu0j5sp6z5QL4YiqHGmPKiJ4Swc6C /qqYby8VY+eNl48wQDSrXRaQLc0Vu/OFagNNbEgXBM4NKSruZPwuOATR6A547eRC83yD c9BcwLUs9d2rHRPIoUiNfzemZCMHxWgxBPRZmQpo8H1ZFtG4FulKnL1e857O3yGsl3gl DIhfUIN8aXzOzVvxfirGJ89ODvXn9LbSKlCUab2G0E7BU67Hj2ZyWRgQc5VZcaYvJPe/ 0sHg== X-Received: by 10.152.7.99 with SMTP id i3mr2529laa.18.1413361458936; Wed, 15 Oct 2014 01:24:18 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.153.11.164 with SMTP id ej4ls31306lad.83.gmail; Wed, 15 Oct 2014 01:24:17 -0700 (PDT) X-Received: by 10.112.40.161 with SMTP id y1mr173478lbk.13.1413361457852; Wed, 15 Oct 2014 01:24:17 -0700 (PDT) Received: from mout.gmx.net (mout.gmx.net. [212.227.17.20]) by gmr-mx.google.com with ESMTPS id rb5si1426348lbb.0.2014.10.15.01.24.17 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Oct 2014 01:24:17 -0700 (PDT) Received-SPF: pass (google.com: domain of seladwa@gmx.de designates 212.227.17.20 as permitted sender) client-ip=212.227.17.20; Received: from [192.168.2.118] ([93.220.90.159]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0LnUna-1Y5PMV1AZ4-00heim for ; Wed, 15 Oct 2014 10:24:17 +0200 Message-ID: <543E2F31.1050302@gmx.de> Date: Wed, 15 Oct 2014 10:24:17 +0200 From: selpa'i User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: lojban@googlegroups.com Subject: Re: [lojban] Re: tersmu 0.2 References: <20141011021201.GH22868@gonzales> <20141011143749.GD23876@gonzales> <20141012012427.GF23876@gonzales> <20141012173533.GG23876@gonzales> <20141014010742.GF19061@gonzales> <20141015005542.GC3713@gonzales> In-Reply-To: <20141015005542.GC3713@gonzales> X-Provags-ID: V03:K0:xlKDVnZMkcQ4jN5f1eEG/c0rndaK7r8P1pPtawvJ3zEw115C030 Xh3qM43n5L1Muq49bp2aUUA29W+8pzWNs6WRjPNfYSVCrPPxhab5v62gd6vnb17X/X8wsLf 58LPocj5/lY36/bCaWhWRY0a/k/gv7rMzU6IDPmhyXKF7vGrZGFOatscB3fJ+zX4RAv9hQC b+t39YJjedFyoKMVNikiA== X-UI-Out-Filterresults: notjunk:1; X-Original-Sender: seladwa@gmx.de X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of seladwa@gmx.de designates 212.227.17.20 as permitted sender) smtp.mail=seladwa@gmx.de Reply-To: lojban@googlegroups.com Precedence: list Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com List-ID: X-Google-Group-Id: 1004133512417 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , Content-Type: text/plain; charset=ISO-8859-1; format=flowed X-Spam-Score: -1.9 (-) X-Spam_score: -1.9 X-Spam_score_int: -18 X-Spam_bar: - la'o me. Martin Bays .me cusku di'e >> kukte fa lo plise .e su'a nai re lo ci plise noi vi zvati > > OK, I think that does rule out \iota! If domain shifting were allowed > within a single proposition like that, we'd need to find a new way to > understand quantifiers, and the sky would generally fall in. > > So maybe {lo} isn't quite \iota, but it's something like "\iota applied > to some ad-hoc but somehow natural subset of the extension"? If that > isn't to reduce to just "lo broda is something(s) satisfying broda", > this "natural" will have to be doing a lot of work... I don't have much > of an idea what it could be. > > Possibly it can all be done by specifying the tense and aspect of > {broda}? With the kind reading corresponding to gnomic aspect? I definitely think tense can do a lot of this (maybe even all of it) while retaining maximality. For example, when there are two cats in the room, one black and one white: (1) lo mlatu cu xekri would be false if {lo mlatu} had to include both cats (and xekri is distributive), so one could consider it a misleading statement in that context. However, it is still true that: (2) lo mlatu vi xekri .i je lo mlatu va blabi if we choose to read {lo mlatu} as Mr. Cat, while: (3) lo vi mlatu cu xekri .i je lo va mlatu cu blabi can be read easily as two different cats (satisfying the two different predicates {vi mlatu} and {va mlatu}). Therefore the original statement (1) could be saved by saying that {lo mlatu} has implicit tense that restricts the cats we know to be in the domain to those satisfying that implicit tense. How legitimate this is as a general rule to use in real-life communication is another question, but it would save certain usages of {lo} from being outlawed. Certainly tense can be implicit anywhere else in the language, so it wouldn't be strange at all for it to be implicit here, would it? (In misleading cases, one should of course not leave tense up to context, but this, too, applies throughout the language) I have also used the gnomic aspect to describe the generic reading, but we don't currently have a cmavo that indicates gnomic aspect. I have proposed to redefine the underused {na'o} as gnomic aspect, but we can use something else too. mi'e la selpa'i mu'o -- You received this message because you are subscribed to the Google Groups "lojban" group. To unsubscribe from this group and stop receiving emails from it, send an email to lojban+unsubscribe@googlegroups.com. To post to this group, send email to lojban@googlegroups.com. Visit this group at http://groups.google.com/group/lojban. For more options, visit https://groups.google.com/d/optout.