Received: from mail-we0-f187.google.com ([74.125.82.187]:45901) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1Tzlta-0002Sg-00; Mon, 28 Jan 2013 02:25:12 -0800 Received: by mail-we0-f187.google.com with SMTP id t11sf1130498wey.4 for ; Mon, 28 Jan 2013 02:24:50 -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=NmM7xhip2FQuGxBzQX9mrgvu3MleMsEzSjLlfgkJTuU=; b=KtFZtuxZjLtO9op/2z9Y1SX1Y5NUyOiS5JIyVjf8XfZOSm5sXzkfqg7/b+AdThn6zv mXNHyugbJaK2N0CkgG5S7+mSORnfTFwxBAjGtjdhl/fqCrnZkV6cn0S58DD/KqDv9It1 IrVVy7CF2Hj7BbLL0k+woZ3/GeZweuYZOXuYRWTznEjbq/uXbGwZToDiJggWNanfcmrV 6NgZzUctjeF5zBLHIxakFUJGIXCQad+/VIg4n8J+/VPK1VUxc0Dl3xZO0A8KxgCDwqGQ Lh7yUqL5u4gVhjclYQHrJ2XRpPh5A29o49Pme2n1tlrGVz7N4NkRTl7x0GMD0OVPeEOG gLyQ== X-Received: by 10.180.73.10 with SMTP id h10mr282762wiv.0.1359368690126; Mon, 28 Jan 2013 02:24:50 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.181.12.113 with SMTP id ep17ls847141wid.22.gmail; Mon, 28 Jan 2013 02:24:49 -0800 (PST) X-Received: by 10.180.89.133 with SMTP id bo5mr1537310wib.6.1359368689096; Mon, 28 Jan 2013 02:24:49 -0800 (PST) X-Received: by 10.180.89.133 with SMTP id bo5mr1537309wib.6.1359368689084; Mon, 28 Jan 2013 02:24:49 -0800 (PST) Received: from dd17822.kasserver.com (dd17822.kasserver.com. [85.13.138.119]) by gmr-mx.google.com with ESMTPS id d1si330316wie.0.2013.01.28.02.24.48 (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 28 Jan 2013 02:24:49 -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-4dbc2e1b.pool.mediaWays.net [77.188.46.27]) by dd17822.kasserver.com (Postfix) with ESMTPA id 3DFA5860317 for ; Mon, 28 Jan 2013 11:24:48 +0100 (CET) Date: Mon, 28 Jan 2013 11:24:47 +0100 From: v4hn To: lojban@googlegroups.com Subject: Re: [lojban] Re: Aesop's "The Wolf and the Crane" Message-ID: <20130128102447.GH20956@samsa.fritz.box> References: <1696426.fuu6unn560@caracal> <47fd82fb-126d-41a3-aa58-fca6ab2fdbde@googlegroups.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="J+eNKFoVC4T1DV3f" Content-Disposition: inline In-Reply-To: <47fd82fb-126d-41a3-aa58-fca6ab2fdbde@googlegroups.com> 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: / --J+eNKFoVC4T1DV3f Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 27, 2013 at 10:43:54PM -0800, la gleki wrote: > On Monday, January 28, 2013 9:07:21 AM UTC+4, aionys wrote: > > On Sun, Jan 27, 2013 at 9:11 PM, Ian Johnson > > > wrote: > > > >> This should be done with {bi'u nai} instead, if the explicitness is=20 > >> desired. It is somewhat of a shame that {lo bi'u nai} is as long as it= is. "the not-newly-introduced thing that brodas" can still refer to any number of different individuals /in the universe of discourse/, not just the one you're talking about in this specific sentence. {lo bi'u nai} has its uses, but that's not one of them in my opinion. > > I disagree. {le} is the specific article, he's referring to a specific= =20 > > thing. This is the reason why {le} exists. > > >=20 > Even if so it has nothing to do with {bi'unai}. "specific thing" might=20 > solve the problem of "any" Did you read the last discussion on that? No it does not fix "any", whatever this is supposed to mean. > but not the problem of the definite article in=20 > the meaning of referring to things previously mentioned. That's exactly what KOhA and one letter abbreviations are for. If you don't like these, {le} is the best choice you have in my opinion as it is rather close to at least the latter one. (if you think KOhAs do not need to get defined with {goi} also to KOhA) I really don't understand this whole movement that tries to prohibit {le}. For me, {le} is a realization of Keith Donnellan's purely referential use of definite descriptions and it is perfectly justified in its existance. You don't need to state each time you refer to an individual that he brodas one way or the other. It's absolutely enough to state it ones in the beginn= ing. Sadly, this concept is not much used in NatLangs in my experience. v4hn --J+eNKFoVC4T1DV3f Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlEGUe8ACgkQMBKLZs4+wjwuwACfX2kUswdFMv2jY8jgyUsiXLF8 YWwAnjXMHhdxDYHhgO9gEq75uKsSRT4C =gA/q -----END PGP SIGNATURE----- --J+eNKFoVC4T1DV3f--