Received: from mail-ea0-f188.google.com ([209.85.215.188]:60123) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1TnwBD-0003m4-Gl; Wed, 26 Dec 2012 10:58:38 -0800 Received: by mail-ea0-f188.google.com with SMTP id l12sf3540708eaa.25 for ; Wed, 26 Dec 2012 10:58:07 -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=FnDplOT7WpvoTI/X6/5WsjV26EyCAk6/UNwiic5j0Qk=; b=oZou92t8gYenHt2Pm6wKfQAWBaGr5nyrt54TMNOFi2F//Pn7W1KEDOtjQrwet9Kwo0 iXJME1+7XGlH2xb5/RiZDVyVDcXPZTBYd46dhOOLLpI4QnBzNoIBO00ntrQi/pquJpvw RTg+inlGLZuoGOi/BR+Nym/1wm2/+aEbO/JXdf83hU0mHVsVHzox29GpMtVacR3xwDI9 MB3vAtx+iV4+QxZPI+HVEB17c5XsC8U/s1jxf2A78xwSRRV0Q82+MKOAX1oSAJJQnxoX mz+aIl+kraOf/SgqiIWnazcr0A73NhArSf+3+Rdb6VbaU8nktpNqj/etsIQAX29zJcx/ cISA== X-Received: by 10.180.101.195 with SMTP id fi3mr3421609wib.20.1356548287370; Wed, 26 Dec 2012 10:58:07 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.180.95.225 with SMTP id dn1ls4148288wib.7.canary; Wed, 26 Dec 2012 10:58:06 -0800 (PST) X-Received: by 10.14.0.196 with SMTP id 44mr35894690eeb.6.1356548286814; Wed, 26 Dec 2012 10:58:06 -0800 (PST) X-Received: by 10.14.0.196 with SMTP id 44mr35894689eeb.6.1356548286799; Wed, 26 Dec 2012 10:58:06 -0800 (PST) Received: from dd17822.kasserver.com (dd17822.kasserver.com. [85.13.138.119]) by gmr-mx.google.com with ESMTPS id z44si10339753een.0.2012.12.26.10.58.06 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 26 Dec 2012 10:58:06 -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 17CE986508D for ; Wed, 26 Dec 2012 19:58:06 +0100 (CET) Date: Wed, 26 Dec 2012 19:58:05 +0100 From: v4hn To: lojban@googlegroups.com Subject: Re: [lojban] "Any" and {ro} Message-ID: <20121226185805.GH7855@samsa.fritz.box> References: <44e6fb5c-91f3-47ba-817c-8560c9c6ca14@googlegroups.com> <50DB2FE2.5090009@gmx.de> <20121226175026.GG7855@samsa.fritz.box> <50DB3C14.9060303@gmx.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TBNym+cBXeFsS4Vs" Content-Disposition: inline In-Reply-To: <50DB3C14.9060303@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: / --TBNym+cBXeFsS4Vs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 26, 2012 at 07:04:04PM +0100, selpa'i wrote: > {lo} by itself doesn't refer to a specific apple, but me wanting a > specific one doesn't make {lo} false. It's an important distinction, {.ue mi nelci di'u .ije ju'o mi tugni} > which, I admit, I didn't see as clearly then (in fact some of what I > said in this thread doesn't seem quite right now in retrospect, and > I certainly didn't express myself well!). However, as things stand, > what I said above is true, {lo} is not specific, but you might very > well have a specific apple in mind (without making {lo plise} > incorrect). It's just not conveyed by {lo}, and if context isn't > strong enough, some relative clause that clarifies the intended > referent will be needed e.g. {lo plise poi pritu traji} or similar. >=20 > {le} will give you a specific apple (though the listener still has > no idea which one), but I don't feel like using {le} myself. >=20 > >So what do you reply if someone asks you in response "Which apple exactl= y?", > >e.g. {lo plise poi mo} or whatever. >=20 > lo va plise poi se barna lo so'i cmalu ke manku xunre The question is, what do you answer, if you _don't_ have a specific one=20 (or a group of specific ones) in mind, but {lo plise} is the most specific thing you can say? > >You could answer {ko cuxna}, but the major question is, whether you can > >avoid such a question in the first place. >=20 > Using {lo} should avoid it, {da} will only work if the scope is right. Sure, uttering {ko dunda lo plise mi} means that you want an apple, but it _leaves open_ whether it's specific or not. If you want a specific one, you can use {lo plise poi broda} to make use of contexual saliency or simply use {le}. However, there does not seem to be a short(any?) construct to say, you _don't_ want a specific one (or you don't have it in mind). All you seem to be able to do is using {lo} and referring to the Gricean ma= xim of quality to argue that you would have said something more specific if you wanted something more specific. The trouble is, it seems many people don't apply this maxim in such a situa= tion (at least in my experience) and will still ask you which one you like. In english you reply with "any", in german you reply with "irgendeinen", bu= t in Lojban you have to say something like "your choice" {ko cuxna}. v4hn --TBNym+cBXeFsS4Vs Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlDbSL0ACgkQMBKLZs4+wjyWvACfZe5eU+GKtsL2is6Gt+qUNa1V 8K0AoI2aIBhPTaLtZdv9Hq30ASL+kNLJ =Z/UA -----END PGP SIGNATURE----- --TBNym+cBXeFsS4Vs--