Received: from mail-ee0-f59.google.com ([74.125.83.59]:46947) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1TtSLK-0002jr-AU; Thu, 10 Jan 2013 16:19:47 -0800 Received: by mail-ee0-f59.google.com with SMTP id c13sf417285eek.4 for ; Thu, 10 Jan 2013 16:19:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=x-received:x-beenthere:x-received:x-received:received-spf:date:from :to:subject:message-id:references:mime-version:content-type :content-disposition:in-reply-to:user-agent:x-original-sender :x-original-authentication-results:reply-to:precedence:mailing-list :list-id:x-google-group-id:list-post:list-help:list-archive:sender :list-subscribe:list-unsubscribe; bh=IKt37r5ju3xYEuG2V8qFxdD3EBx9NwLZ+kq2kaTj7pY=; b=hlUMwGFwocPLww8eTEsy3x78eNXuXEgawY+tgciYhMb9flC+AaVpflpSzZwQUZ8hkT eswLWb2E7Uud7a3UzrCGgjXosytYzcyu1vubxqSjslrqgJh1KhwQAHTXD9XyMUChHKbg gDTzX3WomXlpSfunrvDZoZBU5Rb/sQShdAsLz5KcIX3hf66+eivps6j/wqDLvm1wksx7 YdYVu5/gL5RLXbLb9u9JwYo6u0KO6CRZ22O0zfG3QTpJDu27EVRC1ylLaXNlyVgVOjVy U1fI1OV7z9r/YaaGW9JE9t4KFwGnfMoTyGJ5kVmsEQKCAEymjWJSKcDYmyROSXUhKJJz 8CXw== X-Received: by 10.180.96.198 with SMTP id du6mr1874025wib.9.1357863562655; Thu, 10 Jan 2013 16:19:22 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.180.88.2 with SMTP id bc2ls3368938wib.40.canary; Thu, 10 Jan 2013 16:19:21 -0800 (PST) X-Received: by 10.14.201.1 with SMTP id a1mr92991829eeo.3.1357863561011; Thu, 10 Jan 2013 16:19:21 -0800 (PST) X-Received: by 10.14.201.1 with SMTP id a1mr92991827eeo.3.1357863560992; Thu, 10 Jan 2013 16:19:20 -0800 (PST) Received: from dd17822.kasserver.com (dd17822.kasserver.com. [85.13.138.119]) by gmr-mx.google.com with ESMTPS id g9si1665226eeo.1.2013.01.10.16.19.20 (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 10 Jan 2013 16:19:20 -0800 (PST) Received-SPF: neutral (google.com: 85.13.138.119 is neither permitted nor denied by best guess record for domain of me@v4hn.de) client-ip=85.13.138.119; Received: from samsa (brln-4db80402.pool.mediaWays.net [77.184.4.2]) by dd17822.kasserver.com (Postfix) with ESMTPA id 2257B865010 for ; Fri, 11 Jan 2013 01:19:20 +0100 (CET) Date: Fri, 11 Jan 2013 01:19:19 +0100 From: v4hn To: lojban@googlegroups.com Subject: Re: [lojban] searching Message-ID: <20130111001919.GA17367@samsa.fritz.box> References: <50EC7334.8040607@gmx.de> <50ECB7C1.2020501@gmx.de> <20130109124414.GD14601@samsa.fritz.box> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2fHTh5uZTiUOsy+g" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Original-Sender: me@v4hn.de X-Original-Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 85.13.138.119 is neither permitted nor denied by best guess record for domain of me@v4hn.de) smtp.mail=me@v4hn.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: Sender: lojban@googlegroups.com List-Subscribe: , List-Unsubscribe: , X-Spam-Score: -0.0 (/) X-Spam_score: -0.0 X-Spam_score_int: 0 X-Spam_bar: / --2fHTh5uZTiUOsy+g Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Yes, we still don't have an "any" in lojban. We discussed that for the last 3 weeks. Still, I don't see that {mi sisku lo crino} fails to mean the right thing - given that we don't have an "any". If you think that is the problem, go back to the last discussion and continue it - It means something like "I'm looking for something that is green". Talking about existence again. The {lo crino} introduces {da poi crino} into the context. This, however, does in my opinion not need to be a specific _physical_ item at this moment. The {da} is one object in the universe of discourse, which _only_ has the primitive property {da crino} f= or now. This object in the UD does not have to map to a physical object(talking abo= ut unicorns) and might also have multiple physical objects it _can_ map to. Looking for (any)something green, you _do_ have an object, in the sense of an element in the universe of discourse, in mind. Namely, an item, whos only relevant property is being green. If someone points you to a blade of grass and you are not satified with it, then you have additional constraints which you didn't mention up to then. Still, you can go on and specify {go'i fe lo crino creka} or something like= that, adding more specific properties to the object in the UD and therefore restricting the possible physical objects it can refer to. If you have a specific item in mind, on the other hand, surly you can just say {mi sisku le crino} and there are no problems with that. On the basis of this interpretation, it seems to work out well, to say {mi sisku lo crino} if you mean to say that you are looking for something green. {ma pinka} v4hn On Thu, Jan 10, 2013 at 10:09:04AM -0500, Ian Johnson wrote: > Look at the "any" discussion, as it's the same idea. {lo crino} can very > well have only one referent, even if there are many green things in the U= D. > It *shouldn't *have only one referent, if the distinction matters to you = as > the speaker; that's (part of?) what {le} is for. But it can anyway. This > means you can't say "I'm looking for a green thing" and be absolutely > certain that your listener knows you don't care which one (without a > separate bridi). >=20 > mi'e la latro'a mu'o --2fHTh5uZTiUOsy+g Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlDvWocACgkQMBKLZs4+wjz9ZgCdEfGBEo8CHFRWLORANH6C6L5x gJoAnjt4rfokhDJHX48iEdwFzuK2D5Ia =F8dE -----END PGP SIGNATURE----- --2fHTh5uZTiUOsy+g--