Received: from mail-yh0-f56.google.com ([209.85.213.56]:53626) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1Wxkuy-0007Rx-EH; Thu, 19 Jun 2014 15:34:58 -0700 Received: by mail-yh0-f56.google.com with SMTP id a41sf677537yho.21 for ; Thu, 19 Jun 2014 15:34:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :x-original-sender:x-original-authentication-results:reply-to :precedence:mailing-list:list-id:list-post:list-help:list-archive :sender:list-subscribe:list-unsubscribe:content-type; bh=1Ma4g6ehEldocuaiEmrddndAcLRbCkNR5mlq/XqRLhY=; b=C7yZJuW/8oJUBkEyZaklm5Em3Ig52L8Y8HWVm0nEPWibh9+3aomnsRV2rFL28Q7+6y lLvKXXndhKcP8qtzhiZbvWuLSOvqQfJsf7PEHLOri9ivzACRfQu5fOwJbK2MnI7gbE57 kWSDYbvEcQSdX3WgnO0Mehm0B810wPx3XHlA2P2obsx4yVkwdHzw3yIEZjuI91yxhWyv 6VDTksKuuAFrw/oQdJZwIdJAlFhdQlH3LwQvcfJednN2R5RWKUi8pQvSKDxToV3gWCfA 9AACdvjaEZUq4OGD3seBskzr2szdJCMQPDxKelEJ+RC8g33eIfOdcRgNAYgvIJamPBt4 aOnw== X-Received: by 10.51.17.34 with SMTP id gb2mr181989igd.4.1403217285967; Thu, 19 Jun 2014 15:34:45 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.50.225.10 with SMTP id rg10ls1046976igc.15.gmail; Thu, 19 Jun 2014 15:34:45 -0700 (PDT) X-Received: by 10.42.233.133 with SMTP id jy5mr3248057icb.32.1403217285737; Thu, 19 Jun 2014 15:34:45 -0700 (PDT) Received: from mail-vc0-x234.google.com (mail-vc0-x234.google.com [2607:f8b0:400c:c03::234]) by gmr-mx.google.com with ESMTPS id l7si297169vda.3.2014.06.19.15.34.45 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 19 Jun 2014 15:34:45 -0700 (PDT) Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 2607:f8b0:400c:c03::234 as permitted sender) client-ip=2607:f8b0:400c:c03::234; Received: by mail-vc0-f180.google.com with SMTP id im17so2822873vcb.39 for ; Thu, 19 Jun 2014 15:34:45 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.58.22.130 with SMTP id d2mr23332vef.55.1403217285566; Thu, 19 Jun 2014 15:34:45 -0700 (PDT) Received: by 10.220.170.73 with HTTP; Thu, 19 Jun 2014 15:34:45 -0700 (PDT) In-Reply-To: <20140618231641.GC856@mercury.ccil.org> References: <538A252F.6060204@gmx.de> <20140618231641.GC856@mercury.ccil.org> Date: Thu, 19 Jun 2014 19:34:45 -0300 Message-ID: Subject: Re: [bpfk] BPFK section: TAhE (ta'e vs na'o) From: =?UTF-8?Q?Jorge_Llamb=C3=ADas?= To: bpfk-list@googlegroups.com X-Original-Sender: jjllambias@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jjllambias@gmail.com designates 2607:f8b0:400c:c03::234 as permitted sender) smtp.mail=jjllambias@gmail.com; dkim=pass header.i=@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=gmail.com Reply-To: bpfk-list@googlegroups.com Precedence: list Mailing-list: list bpfk-list@googlegroups.com; contact bpfk-list+owners@googlegroups.com List-ID: X-Google-Group-Id: 972099695765 List-Post: , List-Help: , List-Archive: Sender: bpfk-list@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary=047d7b2e7c50d9583904fc37fb6a X-Spam-Score: -1.9 (-) X-Spam_score: -1.9 X-Spam_score_int: -18 X-Spam_bar: - Content-Length: 3857 --047d7b2e7c50d9583904fc37fb6a Content-Type: text/plain; charset=UTF-8 On Wed, Jun 18, 2014 at 8:16 PM, John Cowan wrote: > selpa'i scripsit: > > > It seems the distinction between {ta'e} and {na'o} has never been > > very clear. > > I don't see any unclarity unless you assume that "The rock habitually > rolled down the hill" necessarily means anything. > But what is the difference between "ta'e broda" and "na'o broda" when broda is agentive? If the only difference between ta'e and na'o is that "ta'e broda" is an acceptable variant of "na'o broda" as long as "broda" is agentive, and otherwise it is nonsense, then "ta'e" would be redundant, since it could always be replaced by "na'o". (I'm not sure exactly why, but since I never saw any relevant distinction between the two I've always preferred "ta'e". Perhaps because na/na'e/nau are used in similar positions and may interfere with "na'o" whereas "ta'e" is more distinct.) mu'o mi'e xorxes -- You received this message because you are subscribed to the Google Groups "BPFK" group. To unsubscribe from this group and stop receiving emails from it, send an email to bpfk-list+unsubscribe@googlegroups.com. To post to this group, send email to bpfk-list@googlegroups.com. Visit this group at http://groups.google.com/group/bpfk-list. For more options, visit https://groups.google.com/d/optout. --047d7b2e7c50d9583904fc37fb6a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On Wed, Jun 18, 2014 at 8:16 PM, John Cowan <cowan@mercury.ccil.org= > wrote:
selpa'i scripsit:

> It seems the distinction between {ta'e} and {na'o} has never b= een
> very clear.

I don't see any unclarity unless you assume that "The rock h= abitually
rolled down the hill" necessarily means anything.

But what is the difference between "ta'e broda&quo= t; and "na'o broda" when broda is agentive?

If the only difference between ta'e and na'o is that &qu= ot;ta'e broda" is an acceptable variant of "na'o broda&qu= ot; as long as "broda" is agentive, and otherwise it is nonsense,= then "ta'e" would be redundant, since it could always be rep= laced by "na'o". =C2=A0

(I'm not sure exactly why, but since I never saw an= y relevant distinction between the two I've always preferred "ta&#= 39;e". Perhaps because na/na'e/nau are used in similar positions a= nd may interfere with "na'o" whereas "ta'e" is = more distinct.)

mu'o mi'e xorxes

--
You received this message because you are subscribed to the Google Groups &= quot;BPFK" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bpfk-list= +unsubscribe@googlegroups.com.
To post to this group, send email to bpfk-list@googlegroups.com.
Visit this group at ht= tp://groups.google.com/group/bpfk-list.
For more options, visit http= s://groups.google.com/d/optout.
--047d7b2e7c50d9583904fc37fb6a--