Received: from mail-gh0-f189.google.com ([209.85.160.189]:41963) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1T2NQD-0000Kk-No; Fri, 17 Aug 2012 07:21:19 -0700 Received: by ghbf16 with SMTP id f16sf4057096ghb.16 for ; Fri, 17 Aug 2012 07:21:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:mime-version:sender:in-reply-to:references :date:message-id:subject:from:to:x-original-sender :x-original-authentication-results:reply-to:precedence:mailing-list :list-id:x-google-group-id:list-post:list-help:list-archive :list-subscribe:list-unsubscribe:content-type; bh=Kdfiv+OZhI87QeEybBle5Cx0/Pr9YOIR/KfBOdSYRis=; b=Zu2XhIJYD6vEw99u74rKAujBUx5bEmS4qN//7oRdp97l3794HnM6PNlXITh4IyISRV eOm3N//2EViRjt4mr89RRZhESe77DR2mTm8TE0do3R9XYkh4lsNlkh9WLv+vaSZHjkFM ULo7qGDWB5KEG1KXWr2x4DeGWfcdRQ19PpNCQ= Received: by 10.52.34.115 with SMTP id y19mr712243vdi.1.1345213262940; Fri, 17 Aug 2012 07:21:02 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.52.100.135 with SMTP id ey7ls2760366vdb.6.gmail; Fri, 17 Aug 2012 07:21:02 -0700 (PDT) Received: by 10.58.170.4 with SMTP id ai4mr959648vec.10.1345213262208; Fri, 17 Aug 2012 07:21:02 -0700 (PDT) Received: by 10.58.170.4 with SMTP id ai4mr959647vec.10.1345213262199; Fri, 17 Aug 2012 07:21:02 -0700 (PDT) Received: from mail-vb0-f50.google.com (mail-vb0-f50.google.com [209.85.212.50]) by gmr-mx.google.com with ESMTPS id t4si398446vds.3.2012.08.17.07.21.02 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 17 Aug 2012 07:21:02 -0700 (PDT) Received-SPF: pass (google.com: domain of paskios@gmail.com designates 209.85.212.50 as permitted sender) client-ip=209.85.212.50; Received: by mail-vb0-f50.google.com with SMTP id l1so4353442vba.23 for ; Fri, 17 Aug 2012 07:21:02 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.36.36 with SMTP id n4mr2159327vdj.80.1345213261985; Fri, 17 Aug 2012 07:21:01 -0700 (PDT) Sender: lojban@googlegroups.com Received: by 10.58.190.169 with HTTP; Fri, 17 Aug 2012 07:21:01 -0700 (PDT) In-Reply-To: References: <44e6fb5c-91f3-47ba-817c-8560c9c6ca14@googlegroups.com> <502B9E61.8060808@gmx.de> <502BA634.3030007@gmx.de> <502C50EB.3090704@gmail.com> <5f1664a8-ea52-4a70-8cce-7beb0b626ad6@googlegroups.com> Date: Fri, 17 Aug 2012 15:21:01 +0100 Message-ID: Subject: Re: [lojban] "Any" and {ro} From: tijlan To: lojban@googlegroups.com X-Original-Sender: paskios@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of paskios@gmail.com designates 209.85.212.50 as permitted sender) smtp.mail=paskios@gmail.com; dkim=pass header.i=@gmail.com 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-Subscribe: , List-Unsubscribe: , Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: -0.7 (/) X-Spam_score: -0.7 X-Spam_score_int: -6 X-Spam_bar: / On 17 August 2012 13:50, Paul Predkiewicz wrote: > Well, i can't really see any difference between unspecified and unspecific. A thing can be specific without being specified by the speaker. You are probably looking at some specific computer display but you can just leave it unspecified in your utterance by calling it "zo'e": a specific unspecified thing. > also, i don't get your point. if i neither state nor point at which of those > fruits i desire to eat, then it doesn't really matter. "I want to eat the apple (not the orange)" and "I want to eat anything (an apple, an orange, or else)" are obviously different situations, and the statement {mi djica lo nu citka zo'e} would be valid for both. I'm giving you this example to demonstrate that {zo'e} can refer to specific (particular) or unspecific (general) objects. In the apple case, {zo'e} would have the value of "the apple"; in the anything case, the value would be "anything". > Even if there were > lying an apple and an orange, if i tell my wife i wanted to eat something > and she got no means to tell what i want, she would give me anything. Yes, she could give you the orange instead of the apple that you want. But the {zo'e} that you uttered has meant the apple, since that's the value that makes {mi djica lo nu citka zo'e} true here. If you had to tell her that you want specifically the apple, you normally wouldn't use {zo'e} -- this isn't a problem. The problem would be when you used {zo'e} to mean "anything": mi djica lo nu citka zo'e How could your wife be sure that you meant Any citka2 can make this bridi true. and not There is a citka2 that makes this bridi true. Both interpretations would seem possible. And only the latter would warrant a further question ("What citka2 are you talking about?"). > I still have the feeling using {zo'e} as "anything" would be ok. Maybe not > in all situations but if what i say is ambiguis, the person im talking to > could still ask if i meant the apple, the orange, the cheese, which is in > the fridge, or maybe the table if i was a beaver. How would you respond if you meant anything, not the apple etc.? mu'o -- You received this message because you are subscribed to the Google Groups "lojban" group. To post to this group, send email to lojban@googlegroups.com. To unsubscribe from this group, send email to lojban+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/lojban?hl=en.