Received: from mail-yh0-f64.google.com ([209.85.213.64]:46685) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1TznAw-0002ej-9E; Mon, 28 Jan 2013 03:47:05 -0800 Received: by mail-yh0-f64.google.com with SMTP id z6sf1541556yhz.29 for ; Mon, 28 Jan 2013 03:46:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=x-received:x-beenthere:x-received:date:from:to:message-id :in-reply-to:references:subject:mime-version:x-original-sender :reply-to:precedence:mailing-list:list-id:x-google-group-id :list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe:content-type; bh=2MQJfwMg3qH9ygcuSKtTBulh71M4a2vFhpL8fJxOdOw=; b=K2bjPOnbfKGxUrEcGppxX1EpEJmt6M+hvX56/5tkSsmEA5Nz8QnM6cOMDHju1Qr4Gt k3EFjpMkUTs0qRz+xu0LKUVuPQcDBDTy7BFMhQQtoEeMpQPoPny3q/xGrGGwvFJv7lh4 P/7le1Hj4Q+vg6x8srOqMJg0Dyy9zZQgqCjpFdEDUQVmAE7FZkDGEYq0h+ffitNURHht Yp7m/BkC93wDOUJIKAkVpPmej9zzJQ9eOfU6/gf53pVjdZDkgxXMhJm21BtmMpEucyCZ ONSodHBeLdFC5t1fmn6IRVQDlBuspvnIdsiiHr0v0+b+lGyo9SZRapBQBLGkUMVPiknS a40Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:x-beenthere:x-received:date:from:to:message-id :in-reply-to:references:subject:mime-version:x-original-sender :reply-to:precedence:mailing-list:list-id:x-google-group-id :list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe:content-type; bh=2MQJfwMg3qH9ygcuSKtTBulh71M4a2vFhpL8fJxOdOw=; b=ylbW9uGzNq9wvhiHNBvCaDenOfTArENMs93xVaSvmU8JouW5RbG+cbz6D13LnEIopR ytrY4IgBZTzTgDeBGSG/ftQETWcJjJgjcbNxiiejxeTK/s1TSxIwHahoVrDHPrVlL/b2 C2YIc+ZSp/axWiSiDUDE6tWdnPOwYwVGjwxY4rIK+wLvU8s9EGy5sGsIiXEZHLR9HFlI hbpEsCrjJPP7K1ZXvuy55R7hZNo6q19r7KOk+Ttd83MjDVvi7rg793I0gO0eJZdLD1kW 50/M54nfVLnoNajWnO6A/soG29AQSXYEbp2CVXSoQJD39E4L1jiBhqcPS6gPY/10E7t+ vFfw== X-Received: by 10.50.217.201 with SMTP id pa9mr828854igc.17.1359373611563; Mon, 28 Jan 2013 03:46:51 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.50.140.40 with SMTP id rd8ls1829844igb.2.canary; Mon, 28 Jan 2013 03:46:50 -0800 (PST) X-Received: by 10.50.5.174 with SMTP id t14mr819691igt.11.1359373610753; Mon, 28 Jan 2013 03:46:50 -0800 (PST) Date: Mon, 28 Jan 2013 03:46:49 -0800 (PST) From: la gleki To: lojban@googlegroups.com Message-Id: <567c078e-13fa-45c1-b22d-c57a45eed8af@googlegroups.com> In-Reply-To: <20130128102447.GH20956@samsa.fritz.box> References: <1696426.fuu6unn560@caracal> <47fd82fb-126d-41a3-aa58-fca6ab2fdbde@googlegroups.com> <20130128102447.GH20956@samsa.fritz.box> Subject: Re: [lojban] Re: Aesop's "The Wolf and the Crane" MIME-Version: 1.0 X-Original-Sender: gleki.is.my.name@gmail.com 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: , Content-Type: multipart/alternative; boundary="----=_Part_85_9136310.1359373609883" X-Spam-Score: -0.1 (/) X-Spam_score: -0.1 X-Spam_score_int: 0 X-Spam_bar: / ------=_Part_85_9136310.1359373609883 Content-Type: text/plain; charset=ISO-8859-1 On Monday, January 28, 2013 2:24:47 PM UTC+4, v4hn wrote: > > 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 > > >> 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. > Yes, but given that there is only one such object in the previous discourse this {bi'unai} refers only to it. > > > I disagree. {le} is the specific article, he's referring to a specific > > > thing. This is the reason why {le} exists. > > > > > > > Even if so it has nothing to do with {bi'unai}. "specific thing" might > > 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. > {lo} does refer to "any" objects. But this range can be narrowed down to an appropriate interval mostly by using UI, VA etc. > > but not the problem of the definite article in > > the meaning of referring to things previously mentioned. > > That's exactly what KOhA and one letter abbreviations are for. > Yes, I agree. KOhA and letter abbreviations do solve the problem. > 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}. > Probably because {le} has shown clear polysemy. It was used for things like {le cribe} for teddy-bears as opposed to {lo cribe} which were supposed to be Ursidae mammals. That's why selpa'i proposed moving {voi} to UI to have a cmavo for "described objects". We can free {le} from this extraneous meaning. And ok, I'll use it. But if {le} refers to apples that one has in mind who is that "one" who has them in mind? Is it the speaker? Then it sounds like an attitudinal. And next. If {le} refers to things that I have in mind why should we suppose that this thing has been previously mentioned? In this case we have to say {le bi'unai} anyway which will save no syllables although may be indeed more precise in meaning. 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 > beginning. > Sadly, this concept is not much used in NatLangs in my experience. > > v4hn > -- You received this message because you are subscribed to the Google Groups "lojban" group. To unsubscribe from this group and stop receiving emails from it, send an email to lojban+unsubscribe@googlegroups.com. To post to this group, send email to lojban@googlegroups.com. Visit this group at http://groups.google.com/group/lojban?hl=en. For more options, visit https://groups.google.com/groups/opt_out. ------=_Part_85_9136310.1359373609883 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Monday, January 28, 2013 2:24:47 PM UTC+4, v4hn wrote: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 <blindb...= @gmail.com>
> > > wrote:
> >
> >> This should be done with {bi'u nai} instead, if the expli= citness 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 num= ber
of different individuals /in the universe of discourse/, not just the o= ne
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.

Yes, but given that there is only one = such object in the previous discourse  this {bi'unai} refers only to i= t.


> > 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" m= ight=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.

{lo} does  refer to "any" objects= . But this range can be narrowed down to an appropriate interval mostly by = using UI, VA etc.


> 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.

Yes, I agree. KOhA and letter abbrevia= tions do solve the problem.
 
If you don't like these, {le} is the best choice you ha= ve in my opinion
as it is rather close to at least the latter one. (if you think KOhAs d= o
not need to get defined with {goi} also to KOhA)

I really = don't understand this whole movement that tries to prohibit {le}.

Probably because {le} has shown clear = polysemy.
It was used for things like {le cribe} for teddy-bears = as opposed to {lo cribe} which were supposed to be Ursidae mammals.
That's why selpa'i proposed moving {voi} to UI to have a cmavo for "desc= ribed objects".
We can free {le} from this extraneous meaning= . And ok, I'll use it.

But if {le} refers to apple= s that one has in mind who is that "one" who has them in mind? Is it the sp= eaker? Then it sounds like an attitudinal.
And next. If {le} refe= rs to things that I have in mind why should we suppose that this thing has = been previously mentioned?
In this case we have to say {le bi'una= i} anyway which will save no syllables although may be indeed more precise = in meaning.


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 br= odas
one way or the other. It's absolutely enough to state it ones in the be= ginning.
Sadly, this concept is not much used in NatLangs in my experience.

v4hn

--
You received this message because you are subscribed to the Google Groups &= quot;lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to lojban+unsubscribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at http://groups.google.com/group/lojban?hl=3Den.
For more options, visit https://groups.google.com/groups/opt_out.
 
 
------=_Part_85_9136310.1359373609883--