Return-Path: X-Sender: lojban-out@lojban.org X-Apparently-To: lojban@yahoogroups.com Received: (qmail 75946 invoked from network); 9 May 2006 23:11:14 -0000 Received: from unknown (66.218.66.217) by m26.grp.scd.yahoo.com with QMQP; 9 May 2006 23:11:14 -0000 Received: from unknown (HELO chain.digitalkingdom.org) (64.81.49.134) by mta2.grp.scd.yahoo.com with SMTP; 9 May 2006 23:11:13 -0000 Received: from lojban-out by chain.digitalkingdom.org with local (Exim 4.61) (envelope-from ) id 1FdbKj-0005zN-Kn for lojban@yahoogroups.com; Tue, 09 May 2006 16:09:37 -0700 Received: from chain.digitalkingdom.org ([64.81.49.134]) by chain.digitalkingdom.org with esmtp (Exim 4.61) (envelope-from ) id 1FdbJL-0005xm-Jz; Tue, 09 May 2006 16:08:12 -0700 Received: with ECARTIS (v1.0.0; list lojban-list); Tue, 09 May 2006 16:08:03 -0700 (PDT) Received: from nobody by chain.digitalkingdom.org with local (Exim 4.61) (envelope-from ) id 1FdbIs-0005wz-DP for lojban-list-real@lojban.org; Tue, 09 May 2006 16:07:42 -0700 Received: from nz-out-0102.google.com ([64.233.162.207]) by chain.digitalkingdom.org with esmtp (Exim 4.61) (envelope-from ) id 1FdbIp-0005wr-Kk for lojban-list@lojban.org; Tue, 09 May 2006 16:07:42 -0700 Received: by nz-out-0102.google.com with SMTP id n29so1462349nzf for ; Tue, 09 May 2006 16:07:38 -0700 (PDT) Received: by 10.36.135.10 with SMTP id i10mr6026689nzd; Tue, 09 May 2006 16:07:37 -0700 (PDT) Received: by 10.36.37.6 with HTTP; Tue, 9 May 2006 16:07:37 -0700 (PDT) Message-ID: Date: Tue, 9 May 2006 17:07:37 -0600 In-Reply-To: <20060509160830.76878.qmail@web81310.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by Ecartis Content-Disposition: inline References: <20060509160830.76878.qmail@web81310.mail.mud.yahoo.com> X-Spam-Score: -2.6 (--) X-archive-position: 11453 X-ecartis-version: Ecartis v1.0.0 Errors-to: lojban-list-bounce@lojban.org X-original-sender: maxim.katcharov@gmail.com X-list: lojban-list X-Spam-Score: -2.6 (--) To: lojban@yahoogroups.com X-Originating-IP: 64.81.49.134 X-eGroups-Msg-Info: 1:12:0:0 X-eGroups-From: "Maxim Katcharov" From: "Maxim Katcharov" Reply-To: maxim.katcharov@gmail.com Subject: [lojban] Re: Usage of lo and le X-Yahoo-Group-Post: member; u=116389790; y=Iwz6iHunlLzqPVeyVLVMYF5rSuUm2iQZrTFR2bGGRVD7LajBfg X-Yahoo-Profile: lojban_out X-Yahoo-Message-Num: 25870 Content-Length: 3833 Lines: 113 On 5/9/06, John E Clifford wrote: > --- Maxim Katcharov > wrote: > > {__ __ ro cribe} refers to all bears. At the > > very least all things > > that were, are, and will be bears, everywhere > > (maybe even imaginary > > bears, story-bears, dreamt-bears, or > > hypothetical > > I'm-afraid-a-bear-will-eat-me bears) - > > henceforth "all bears". > > Well, no. {_ _ ro cribe} refers to all the bears > relevant in the present context, which may be > anything from the couple specifed to all the > actual and possible bears. In a neutral context, > it usually means all current actual bears. I understand this and see the utility. But I also see a major problem: this approach makes it so that Lojban has no way to refer to all bears specifically (specifically as in the opposite of vague in "in Lojban you can express things as specifically or vaguely as you'd like"). What if context overwhelmingly favors three bears? For example, three bears are chasing us -- I say {__ __ ro cribe}, and obviously I mean all these three bears, right? But what if my intent is to say "all bears can't climb trees"? (however wrong I may be.) I have no proper (and consistent) way to say this, because in this case using an inner {ro} clearly would default it to "all of the bears chasing us here-now can't climb trees", which is not what I want to say. The rest of the examples in the email that you just replied to rely heavily on the assumption that this is how things must work, and if you disagree, then we'd be talking of different things. If you now agree with the above paragraph, that {__ __ ro} must include "/all/ ever" (not just those in context), then please re-respond to my examples with this in mind, because they would not be as I intended otherwise. I suggest that: {__ l_ ro cribe} mean all bears (as I've described it above) {__ l_ su'o/pa/etc. cribe} mean some bears (in context)/ one bear (in context) and {__ l_ cribe} mean "all in context" which would address your concerns regarding not confusing the listener with potentially thousands of restrictions. > > An inner {ro} finalizes/commits your > > restriction in that it says "no > > other restrictions need apply". If you say: > > > > {ro __ ro cribe} > > > > you cannot say that you meant the same > > identity-group/referant/entity/"set" as > > > > {ro __ ro cribe poi bunre} > > > > unless you show that > > > > {ro __ ro cribe cu bunre} > > > > ...good so far? > > Let's see: if I say {_ ro cribe poi jersi mi'o} I > can't add further restrictions and be sure I am > still referring to the same thing. But there is > nothing special about {ro} in this; anytime I add > new restrictions I am in danger of changing the > referent. Is it that, if I claim to be talking not so when you use su'o or pa as the inner. Surely {ro __ pa cribe} can be the same identity-group/referent/entity/"set" as ro __ pa cribe poi bunre} without having to prove that {ro __ ro cribe cu bunre} correct? > < mentioned, or perhaps I never > had it. See, for that latter one, I'd just say > (in your terms): > > {cisu'o le ro cribe cu bunre} (or maybe exactly > ci)>> > > Which latter one, I've lost track of the lists. > Certainly {cisu'o le ro cribe} isn't specific > (isn't it {su'o ci}?) > The latter one that I meant was: lo: I don't have three bears in mind. But, I want to say that three bears are brown. You're right regarding it being {su'oci}. {cisu'o le ro cribe} certainly isn't specific (though it uses le), and that's exactly my point. To unsubscribe from this list, send mail to lojban-list-request@lojban.org with the subject unsubscribe, or go to http://www.lojban.org/lsg2/, or if you're really stuck, send mail to secretary@lojban.org for help.