Received: from mail-vb0-f61.google.com ([209.85.212.61]:46069) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1Sld8e-0000qn-G3; Mon, 02 Jul 2012 02:42:00 -0700 Received: by vbzb23 with SMTP id b23sf5747873vbz.16 for ; Mon, 02 Jul 2012 02:41:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=x-beenthere:date:from:to:message-id:in-reply-to:references:subject :mime-version: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:content-type; bh=nHeIFfkNYR4aEGMPFJscAhUX/itRFFMom9viPF0m3wo=; b=hF+U0FMZrZJNja7Wb90WAUtmPkgkm41D3IUOrVSh+4FYLQSFNbSG+BkpZHaUFRCl+h glnux9/c73ldVFEXKaIqctWhH5Y7ryCUMnpTRXjtee/l3fLAa242xTvKS4GX+RvrCyqV DqRd4NKni1X5YGJKL+LLQFR0ihFSCQ9c6hkEE= Received: by 10.52.174.167 with SMTP id bt7mr528032vdc.15.1341222100742; Mon, 02 Jul 2012 02:41:40 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.220.119.137 with SMTP id z9ls2922525vcq.2.gmail; Mon, 02 Jul 2012 02:41:39 -0700 (PDT) Received: by 10.52.179.98 with SMTP id df2mr527438vdc.3.1341222099760; Mon, 02 Jul 2012 02:41:39 -0700 (PDT) Date: Mon, 2 Jul 2012 02:41:39 -0700 (PDT) From: gleki To: lojban@googlegroups.com Message-Id: <62818d3a-c188-43d5-ad25-09c4cc9aca6c@googlegroups.com> In-Reply-To: References: <90a7e54c-42fe-4ee0-9693-8155db9a7646@googlegroups.com> Subject: [lojban] Re: Is there any demand for LoCCan3? MIME-Version: 1.0 X-Original-Sender: gleki.is.my.name@gmail.com X-Original-Authentication-Results: ls.google.com; spf=pass (google.com: domain of gleki.is.my.name@gmail.com designates internal as permitted sender) smtp.mail=gleki.is.my.name@gmail.com; dkim=pass header.i=@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_21480124.1341222099294" X-Spam-Score: -0.7 (/) X-Spam_score: -0.7 X-Spam_score_int: -6 X-Spam_bar: / ------=_Part_85_21480124.1341222099294 Content-Type: text/plain; charset=ISO-8859-1 Let's discuss it now ))). After reading the article I want new language even less. *The monkey took the banana and ate it.* *Pam went home because she felt sick.* *The dog ate the bird and it died.* (!!!!!!!!!!!) In each case I can use {ta} and the context will decide who felt sick (the house or Pam) and who died (the dog or the bird). In other cases vo'a, ko'a can solve the problem. {sei} can be problematic for me but I hope CLL 1.1 will explain it. I can think of no other cases of anaphora. And it's still am mystery for me what can be done with 2. There should be new cmavo for individuals, sets and masses 3. new design of connectives On Monday, July 2, 2012 10:26:12 AM UTC+4, la .lindar. wrote: > > It's come up a few times. > https://en.wikipedia.org/wiki/Anaphora_(linguistics) > > I think we're working on the rest. > > It's a theoretical next-step language, but I don't see it happening any > time soon since we're changing up our game. > -- You received this message because you are subscribed to the Google Groups "lojban" group. To view this discussion on the web visit https://groups.google.com/d/msg/lojban/-/ZqkHTaoWCKAJ. To post to this group, send email to lojban@googlegroups.com. To unsubscribe from this group, send email to lojban+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/lojban?hl=en. ------=_Part_85_21480124.1341222099294 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Let's discuss it now ))).
After reading the article I want new language= even less.
The monkey took the banana and at= e it. 
Pam went home because she fel= t sick.  
The dog ate the bird and it died.  (!!!!!!!!!!!)

In each case I can use {ta} and the context will decide wh= o felt sick (the house or Pam) and who died (the dog or the bird).

In other cases  vo'a, ko'a can solve the problem.

{sei} can be problematic for me but I hope CLL 1.1 wi= ll explain it.

I can think of no other cases of an= aphora.

And it's still am mystery for me what can = be done with
2. There should be new cmavo for individuals, sets a= nd masses
3. new design of connectives

On Monday, July 2, 2012 10:26:12 AM UTC+4, la .lindar. wr= ote:
It's come up a few times.<= div>https://en.wikipedia.org/wiki/Anaphora_(linguistics)

I think we're working on the rest.
It's a theoretical next-step language, but I don't see it happ= ening any time soon since we're changing up our game.

--
You received this message because you are subscribed to the Google Groups "= lojban" group.
To view this discussion on the web visit https://groups.google.com/d/msg/lojban/-/Zq= kHTaoWCKAJ.
=20 To post to this group, send email to lojban@googlegroups.com.
To unsubscribe from this group, send email to lojban+unsubscribe@googlegrou= ps.com.
For more options, visit this group at http://groups.google.com/group/lojban= ?hl=3Den.
------=_Part_85_21480124.1341222099294--