Received: from mail-wi0-f189.google.com ([209.85.212.189]:34540) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1T6UM0-0005Rz-4Q; Tue, 28 Aug 2012 15:33:58 -0700 Received: by wibhr14 with SMTP id hr14sf1818895wib.16 for ; Tue, 28 Aug 2012 15:33:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=x-beenthere: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=9JJwdwEabItEJalPIC5wo6v7Bs8ZU3UFP4CsCccEVvI=; b=Kw9qpFQrPyzJCVt+RHSosy4fRQe83TLK1OenOtNK4wprdELDS54t8m31oiBUBWOx0v iV9NQG5wHJtnbnQ+FbmoUGrk28BAaYCkcByEg4A94BENGAx8jldw6Oc21Cg6Qx2tBn9o oddAUvP3xeQJ+x4iVznxiKqpgQOWvurN1arOR/Yy4Q1CukxkhHBgVfANOgwAWPM5wMLo f/MpMRftGOP5mQI+w26OUegMhpGjtH8H99M+Z3orE34l8WixxwHcb8ZSo1wFicsbka7n uTdqN1Nf391OJNwzb3tOmmCo4pTx7Zrngz3VNOIa1yj16YmhkjO7Jb0FxHLNQEZyzfdv HPew== Received: by 10.180.93.137 with SMTP id cu9mr1899420wib.1.1346193220636; Tue, 28 Aug 2012 15:33:40 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.180.83.226 with SMTP id t2ls6287057wiy.3.canary; Tue, 28 Aug 2012 15:33:40 -0700 (PDT) Received: by 10.216.237.155 with SMTP id y27mr1060652weq.11.1346193219897; Tue, 28 Aug 2012 15:33:39 -0700 (PDT) Received: by 10.216.237.155 with SMTP id y27mr1060651weq.11.1346193219870; Tue, 28 Aug 2012 15:33:39 -0700 (PDT) Received: from dd17822.kasserver.com (dd17822.kasserver.com. [85.13.138.119]) by gmr-mx.google.com with ESMTPS id e5si891030wiw.0.2012.08.28.15.33.39 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 28 Aug 2012 15:33:39 -0700 (PDT) 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-d9bade9c.pool.mediaWays.net [217.186.222.156]) by dd17822.kasserver.com (Postfix) with ESMTPA id 2010A86060F for ; Wed, 29 Aug 2012 00:33:39 +0200 (CEST) Date: Wed, 29 Aug 2012 00:33:39 +0200 From: v4hn To: lojban@googlegroups.com Subject: Re: [lojban] "Any" and {ro} Message-ID: <20120828223338.GA26211@samsa> References: <5039204B.1060401@gmail.com> <325f818f-76ce-4f3c-b0c0-03dc4db2e9d8@googlegroups.com> <503B8ED4.200@gmail.com> <9019D4E1-8993-4AF4-BD70-AC76E5A9620F@yahoo.com> <1346161778.18681.YahooMailNeo@web184406.mail.bf1.yahoo.com> <20120828201927.GI25027@samsa> <503D28D0.5070206@gmx.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Qxx1br4bt0+wmkIi" Content-Disposition: inline In-Reply-To: <503D28D0.5070206@gmx.de> User-Agent: Mutt/1.5.20 (2009-06-14) 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.7 (/) X-Spam_score: -0.7 X-Spam_score_int: -6 X-Spam_bar: / --Qxx1br4bt0+wmkIi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable DISCLAIMER: The following is highly subjective and should probably not be taken too serious. On Tue, Aug 28, 2012 at 10:23:44PM +0200, selpa'i wrote: > Am 28.08.2012 22:19, schrieb v4hn: > >Why should people stop to use {le} if it literally means "the > >thing you have in mind".. mu'o >=20 > Because it doesn't mean that any more than "lo" does. Both are > defined in terms of "zo'e", so "lo" is just as specific as "le", and > "le" can be just as vague as "lo". There isn't anything that "le" > does that "lo" cannot do. You know, there's a term for your usage of the {lo} in german. It's "eierlegende Wollmilchsau". If you read more of the gadri proposal than just the formal definitions, then you find that {lo} is described as "generic article" whereas {le} gets quite a bit of attention as well and is described as "specific article". This proposal does not make any "specific" usage of {le} deprecated as far as I can see. The distinction made in the proposal looks to me like the core of the "any" vs "specific ones" discussion. You're right in that this generic/specific distinction does not seem to exist in the given formal definitions. Is this intensional? What's the point in describing in two pages two different concepts for {le} and {lo} if you afterwards define both in terms of {zo'e} without mentioning the generic/specific distinction? mu'o mi'e la .van. --Qxx1br4bt0+wmkIi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlA9R0IACgkQMBKLZs4+wjzfMwCeMDD6uB/x1kIEhkZAFTKmHkox uC4AoIe/4mgK9/44JasWVs5RIezhckHo =gCa9 -----END PGP SIGNATURE----- --Qxx1br4bt0+wmkIi--