Received: from mail-wi0-f187.google.com ([209.85.212.187]:51381) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1Tnv7k-0003Jy-FL; Wed, 26 Dec 2012 09:50:44 -0800 Received: by mail-wi0-f187.google.com with SMTP id hm6sf3508056wib.24 for ; Wed, 26 Dec 2012 09:50:29 -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=O94Gb89DVy0YMEc/Cn5+BMswQnlzbGrb+qhlqGvGQ1o=; b=JqHEbNQcwi6xeoD5ygyXCebMkH47lV4SOq+4dUxcnNwE6R7BdmZwpk3RnUH7LQczeO 7cutDNDuroy/190gDXVctMSJ+ejuEz+kjb2WK6thY9vrvh5i1DizyIZtDFiqfpSGAWqx K8kCJx8SF99Yn1RjxJsz6t2LR71agUfXv8V1XvGWPgz9aLvKyJIN5aDAPZJW24rqVMRH 95Gq6agXiNnffJ1Sd5zrlNER27SGcdCIAFk1qQRwV2l0MxFSwaG2ROACjD29zIuv/Im9 tdW+OdWkGtfIuLybzol5BuS4aQ9wm7OnDkue/ZIVNlMUH87Ho2PlETw/MV2cClQosEyt nRTw== X-Received: by 10.180.101.99 with SMTP id ff3mr3328869wib.19.1356544228879; Wed, 26 Dec 2012 09:50:28 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.180.87.130 with SMTP id ay2ls3311974wib.41.gmail; Wed, 26 Dec 2012 09:50:28 -0800 (PST) X-Received: by 10.14.0.196 with SMTP id 44mr35685077eeb.6.1356544228268; Wed, 26 Dec 2012 09:50:28 -0800 (PST) X-Received: by 10.14.0.196 with SMTP id 44mr35685075eeb.6.1356544228255; Wed, 26 Dec 2012 09:50:28 -0800 (PST) Received: from dd17822.kasserver.com (dd17822.kasserver.com. [85.13.138.119]) by gmr-mx.google.com with ESMTPS id z44si10252798een.0.2012.12.26.09.50.28 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 26 Dec 2012 09:50:28 -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-4dbc2cdc.pool.mediaWays.net [77.188.44.220]) by dd17822.kasserver.com (Postfix) with ESMTPA id 8370586508D for ; Wed, 26 Dec 2012 18:50:27 +0100 (CET) Date: Wed, 26 Dec 2012 18:50:26 +0100 From: v4hn To: lojban@googlegroups.com Subject: Re: [lojban] "Any" and {ro} Message-ID: <20121226175026.GG7855@samsa.fritz.box> References: <44e6fb5c-91f3-47ba-817c-8560c9c6ca14@googlegroups.com> <50DB2FE2.5090009@gmx.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="RDS4xtyBfx+7DiaI" Content-Disposition: inline In-Reply-To: <50DB2FE2.5090009@gmx.de> 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: / --RDS4xtyBfx+7DiaI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 26, 2012 at 06:12:02PM +0100, selpa'i wrote: > Thinking back to this topic, I'm wondering why nobody suggested > simple {lo}. It's more or less perfect for this kind of thing. >=20 > ko dunda lo plise pe lo lanka mi > Give me any apple from the basket. Because according to your usual arguments, this sentence can also mean "Give me an apple (and I might have a specific one in mind) from the basket" and "Give me the apple from the basket." Therefore it would be unclear whether you have a specific one in mind. So what do you reply if someone asks you in response "Which apple exactly?", e.g. {lo plise poi mo} or whatever. You could answer {ko cuxna}, but the major question is, whether you can avoid such a question in the first place. v4hn --RDS4xtyBfx+7DiaI Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlDbOOIACgkQMBKLZs4+wjymTgCglO9ovZGft01WYaU2pXvgLE2T yx0AoLu0KKDiAvA9e0MmA2m1h9gMXgil =g0gn -----END PGP SIGNATURE----- --RDS4xtyBfx+7DiaI--