Received: from mail-pa0-f64.google.com ([209.85.220.64]:49515) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1Xg3b8-0003zP-7e; Sun, 19 Oct 2014 20:25:39 -0700 Received: by mail-pa0-f64.google.com with SMTP id hz1sf750210pad.9 for ; Sun, 19 Oct 2014 20:25:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=date:from:to:message-id:in-reply-to:references: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=5UPWNBtRWGTpNjTtTTrPCDV8zkhEg0umnaMTeT1pa8E=; b=Poxh5X/KnMxv0Bcl+rCdzSjmvifRbXS096sye7PMNiJW2GYr09XJeVv7dLMC2q+Z4C DMXA4waIBprJ5F5fYBe+7bGqvm0HtgL0DIvSM/oDwaywQ++eHtI47hpLAyWt1UY/K0Ik 0qSMrJp/v6Ut+aiwjHRe17FqVUPoD7qhE7CmmgmRYAj0eKXUjQGPqcwATpDtMNlQLYU4 nPCwqqZesqW+zrezgIYpZ/7zi6Ih37zFfr88xXTdnJoisE8CgBcLjEilPvAZVVbpanC5 2+TlI0JVikvZhNA6JtZlULte4LKdh8d/K4JRxe+3wUlGaTj0nABSUIdaBm6+CpAGNYdq 9gvw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:message-id:in-reply-to:references: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=5UPWNBtRWGTpNjTtTTrPCDV8zkhEg0umnaMTeT1pa8E=; b=iPGdgIAjfjzsFT5faKjGNvZUGqyg2kV5JK463tbLhimbv+kObhqbZ2u5q+mpJGWNlF eFKgGybPohX7cthtXAFn1nr/tixhUYiezh7gPmvvN7S6wOpiFK9Z9WMeZiR6gwXKzomo t1FqaFd/tjfabJ/OJVQYghc5l+2CelsV8L8wQ7h06vr1UZ6Qrnznf1lpEbGVb79vTPfU rWNhQdxDvaELBGeBdq71ltJb6WM8lV8Wfio2ezJoLwYkUXukTGuEsvFg0rYqZs3fIZ4A cd4Rv4VPsfbTFqfr49mpU0HVAu0ppLDvQ0GKewqrOrK3iLloK/qY3P/3ouco+pYDPnOP IW2g== X-Received: by 10.140.20.175 with SMTP id 44mr397226qgj.4.1413775523443; Sun, 19 Oct 2014 20:25:23 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.140.49.67 with SMTP id p61ls259261qga.96.gmail; Sun, 19 Oct 2014 20:25:23 -0700 (PDT) X-Received: by 10.140.20.175 with SMTP id 44mr397225qgj.4.1413775523275; Sun, 19 Oct 2014 20:25:23 -0700 (PDT) Date: Sun, 19 Oct 2014 20:25:22 -0700 (PDT) From: mukti To: bpfk-list@googlegroups.com Message-Id: In-Reply-To: References: Subject: [bpfk] Re: official cmavo form MIME-Version: 1.0 X-Original-Sender: shunpiker@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: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary="----=_Part_2822_30463946.1413775522461" X-Spam-Score: -2.0 (--) X-Spam_score: -2.0 X-Spam_score_int: -19 X-Spam_bar: -- ------=_Part_2822_30463946.1413775522461 Content-Type: text/plain; charset=UTF-8 On Sunday, October 19, 2014 9:19:33 PM UTC-3, guskant wrote: > > La jbovlaste allows it based on peg morphology, and la gleki and I don't > agree to the new rule. Concretely, an experimental cmavo "jie'e'e" is now > discussed: > > http://jbovlaste.lojban.org/comments.html?valsi=27527;natlangword=0;commentid=0;definition=0 > A note to clarify why, when and how jbovlaste came to use the camxes BPFK morphology. In March a bug was filed against jbovlaste, citing problems with words that were being rejected on the basis of not being approved by "vlatai" -- a tool which is part of "jbofihe ", and which jbovlaste previously used to validate words. Since jbofihe/vlatai was not maintained, in April I posted a message to the lojban list proposing to replace it with camxes, and asking for feedback. I ran all of the words in the database through camxes, and only a small number of cmevla and fu'ivla were classified differently by camxes than they had been by jbofihe/vlatai. I published a list of those words for confirmation. In June I posted a follow-up , announcing that jbovlaste had been updated to use a python implementation of camxes , and detailing the attendant reclassifications: Out of 21,940 words, only about 100 were affected by the change in the morphological verifier. Most of the effected words were non-conforming fu'ivla. All of the implementations of the implementations of camxes distributed at that time, including the the one added to jbovlaste, were using an older version of the camxes BPFK morphology: Probably version 108 , from November 2005. The most recent version of the morphology had been completed in June 2008. The fact that an older morphology was being used came up in discussions of {relmast}, which had been permitted by jbofihe/vlatai, but was forbidden by camxes. After it became apparent that camxes was not using the latest BPFK morphology, I updated camxes/vlatai to do so. 20 cmevla that were previously disallowed were reinstated. Since that time, the various implementations of camxes have been updated to use the 2008 camxes BPFK morphology, including Ilmen's camxes.js implementation , which powers the camxes bot in IRC, and python-camxes , which is actually a wrapper around Robin's original Java implementation, and which is used by camxes.lojban.org. mi'e la mukti mu'o -- 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. ------=_Part_2822_30463946.1413775522461 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Sunday, October 19, 2014 9:19:33 PM UTC-3, guskant wrot= e:
La jbovlast= e allows it based on peg morphology, and la gleki and I don't agree to the = new rule. Concretely, an experimental cmavo "jie'e'e" is now discussed:
= http://jbovlaste.lojban.org/comment= s.html?valsi=3D27527;natlangword=3D0;commentid=3D0;definition=3D0=

A note to clarify why, when and = how jbovlaste came to use the camxes BPFK morphology.

<= div>In March a bu= g was filed against jbovlaste, citing problems with words that wer= e being rejected on the basis of not being approved by "vlatai" -- a tool w= hich is part of "jbofihe"= , and which jbovlaste previously used to validate words. Since jbofihe/vlat= ai was not maintained, in April I posted a message to the lojban list = ;proposing to replace it with camxes, and asking for feedback. I ran al= l of the words in the database through camxes, and only a small number of <= a href=3D"https://github.com/lojban/jbovlaste/issues/39">cmevla an= d fu'ivla&nbs= p;were classified differently by camxes than they had been by jbofihe/vlata= i. I published a list of those words for confirmation.

=
In June I posted a follow-up, announcing that jbovlaste had been = updated to use a pyth= on implementation of camxes, and detailing the attendant reclassificati= ons: Out of 21,940 words, only about 100 were affected by the change in the= morphological verifier. Most of the effected words were non-conforming fu'= ivla.

All of the implementations of the implementa= tions of camxes distributed at that time, including the the one added to jb= ovlaste, were using an older version of the camxes BPFK morphology: Probabl= y version 108, from = November 2005. The most recent version of the morphology had been completed= in June 2008. 

The fact that an older morpho= logy was being used came up in discussions of {relmast}, which had been per= mitted by jbofihe/vlatai, but was forbidden by camxes. After it became appa= rent that camxes was not using the latest BPFK morphology, I updated camxes/vlatai to do= so. 20 cmevla that were previously disallowed were reinstated.
<= br>
Since that time, the various implementations of camxes have b= een updated to use the 2008 camxes BPFK morphology, including Ilmen's camxes.js implementation, which powers the camxes bot in IRC, and python-camxes, which is actually a wrapper around R= obin's original Java implementation, and which is used by camxes.lojban.org.

mi= 'e la mukti mu'o

--
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.
------=_Part_2822_30463946.1413775522461--