Received: from vms.dc.lsoft.com (vms.dc.lsoft.com [205.186.43.2]) by locke.ccil.org (8.6.9/8.6.10) with ESMTP id TAA02036 for ; Tue, 16 Jan 1996 19:41:08 -0500 Message-Id: <199601170041.TAA02036@locke.ccil.org> Received: from PEACH.EASE.LSOFT.COM (205.186.43.4) by vms.dc.lsoft.com (LSMTP for OpenVMS v1.0a) with SMTP id 2A882746 ; Tue, 16 Jan 1996 19:13:22 -0500 Date: Tue, 16 Jan 1996 22:10:16 -0300 Reply-To: Paulo Barreto Sender: Lojban list From: Paulo Barreto Subject: Re: TECH QUERY: variant fu'ivla To: lojban@cuvmb.cc.columbia.edu Status: OR X-Mozilla-Status: 0011 Content-Length: 1032 X-From-Space-Date: Tue Jan 16 19:41:18 1996 X-From-Space-Address: LOJBAN%CUVMB.BITNET@UBVM.CC.BUFFALO.EDU cu'u la djan. >A parallel situation exists in type 3 fu'ivla (those made with gismu-based >prefixes): either a four-letter rafsi or a CCV rafsi can be used as the >prefix (CVC and CVV rafsi aren't safe): I think you mean either a four-letter rafsi or a CVC rafsi, and that CCV and CVV aren't safe: {pa dja,r,ki} -> {pad-jarki} >I favor declaring them equivalent: while this limits the theoretical >size of fu'ivla space, it makes for simplicity: you need not remember >whether "cipnrdodo" or "cpirdodo" is the official word for "dodo". > >Comments? Needless to say (at least to John, as we have just talked about this :-), I'm completely favorable. I also suggest the term "canonical fu'ivla" for type 3, as this is the safest form, and in practice the preferred one. co'o mi'e paulos. ni'o P.S.: > "ricrxacere" and "tricrxacere" .ui You used the latin ablative to form the fu'ivla! Paulo S.L.M. Barreto -- Software Analyst *** PGP public key available on known keyservers *** e'osai ko sarji la lojban