Received: from mail-ve0-f183.google.com ([209.85.128.183]:40457) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1VF5Nf-0000q2-Mc; Thu, 29 Aug 2013 09:47:46 -0700 Received: by mail-ve0-f183.google.com with SMTP id db10sf185176veb.20 for ; Thu, 29 Aug 2013 09:47:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=date:from:to:message-id:subject:mime-version:x-original-sender :reply-to:precedence:mailing-list:list-id:list-post:list-help :list-archive:sender:list-subscribe:list-unsubscribe:content-type; bh=KSoZjKi+a0tvZOXlnClK3Ro724/hTWw7NMTeVs96aio=; b=Wl0y/B6w6KZWGkUWB1brHfGPG1i5levqWad4QMwXYEj9yAgEDvWaMbYN00KQbmfrjS B62ZnhBQ9fapBU/vB7lSQXaMdVMM0NB1ml9nEOOTmzoNZpPPcWN87scQZHoN887rV1h5 iWx1V541/oc4YrYnoaIlqtNf1yB9b/tDUwTmTBLpN76ZUEQqtdyUGvFiaQ4lxPmm5o5q 22v7Fp5t4n89HIGUw8CU+N3wTLexhk7wfAo5R0tpa7uAjniDXEhbZCH/y8KfCt11C39S SXDsbqtgpllOcp1EeUewlXKUJBDrmXJMYd9qHl0JSAje1Ma4N5J6gJAjnW3E7DcRKmec au/g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:message-id:subject:mime-version:x-original-sender :reply-to:precedence:mailing-list:list-id:list-post:list-help :list-archive:sender:list-subscribe:list-unsubscribe:content-type; bh=KSoZjKi+a0tvZOXlnClK3Ro724/hTWw7NMTeVs96aio=; b=JLz4uAJ4tQXHmPEPsVC2jUCLUaMlaicFczjQXSqTDrhIMV9TgPVxetnOhjlnHKCR1C YHrys4VzttcXowJ/Jm18LKR9hHtlxqGeJp2r3VFRIKR7GS4mrg2pNC6M7237lGL4op9d BvOQwQDBjeAZN0gA6Taa2TYrv8YCoQ10vPk1uBNGdZTp0MSaDYQ78AbHKfTfi96AZFJk XHuD4kSZQuwgBmdFap7gwmM065tVSWsHyl8PupYXefpm42vxdQZKXgA7eKDWM/Pi5uuo PlpJGve5H5Cy9qUd4yDgu0699b2UWyIFCRdijdunXq9ythYqmwnXSg+fanK/QekuSvt4 BJSw== X-Received: by 10.49.56.7 with SMTP id w7mr156542qep.16.1377794848739; Thu, 29 Aug 2013 09:47:28 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.49.95.138 with SMTP id dk10ls928879qeb.23.gmail; Thu, 29 Aug 2013 09:47:28 -0700 (PDT) X-Received: by 10.49.70.138 with SMTP id m10mr158541qeu.9.1377794848217; Thu, 29 Aug 2013 09:47:28 -0700 (PDT) Date: Thu, 29 Aug 2013 09:47:27 -0700 (PDT) From: la gleki To: bpfk-list@googlegroups.com Message-Id: <43d47cc7-0c52-47ac-acb1-82928096f3f6@googlegroups.com> Subject: [bpfk] Changing the definitions of {ba'o} and {co'i} MIME-Version: 1.0 X-Original-Sender: gleki.is.my.name@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="----=_Part_4357_27900709.1377794847768" X-Spam-Score: -0.1 (/) X-Spam_score: -0.1 X-Spam_score_int: 0 X-Spam_bar: / Content-Length: 3782 ------=_Part_4357_27900709.1377794847768 Content-Type: text/plain; charset=ISO-8859-1 1. ba'o is currently defined (according to CLL) as ba'o ZAhO perfective If we are to use normal linguistic terminology then this is wrong. {ba'o} is perfect, not perfective - those are completely different things. According to Wikipedia it's better to avoid using the term "perfect" and change to "retrospective". So I propose changing the definition of ba'o to ba'o ZAhO retrospective 2. As for "perfective" it looks like it's expressed using {co'i}. Another independent proposal is that co'i should be defined as co'i ZAhO perfective/achievative "perfective" is used quite extensively when describing Chinese and Russian grammar so normalising terminology is a must pe'i. Neither proposal changes anything in Lojban itself, only in translation. -- 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/groups/opt_out. ------=_Part_4357_27900709.1377794847768 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
1.

ba'o is currently defined (according= to CLL) as
     ba'o    ZAhO                perfective

If we are to use normal linguistic terminol= ogy then this is wrong.

{ba'o} is perfect, not per= fective - those are completely different things.
According to Wikipedia it's= better to avoid using the term "perfect" and change to "retrospective".

So I propose changing the definition of ba'o to
<= /div>

     ba'o    ZAhO             =
   retrospective


2.

=
As for "perfective" it looks like it's expressed using {co'i}.
Another independent proposal is that co'i should be defined = as 

     co'i    ZAhO     =
           perfective/achievative

"perfective" is used quite extensively when= describing Chinese and Russian grammar so normalising terminology is a mus= t pe'i.

Neither proposal changes anything in Lojba= n itself, only in translation.

--
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 https://groups.google.com/groups/opt_out.
------=_Part_4357_27900709.1377794847768--