Received: from mail-ww0-f61.google.com ([74.125.82.61]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1PAkpJ-0008Vp-KO; Tue, 26 Oct 2010 07:48:40 -0700 Received: by wwb34 with SMTP id 34sf3350192wwb.16 for ; Tue, 26 Oct 2010 07:48:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=domainkey-signature:received:x-beenthere:received:received:received :received:received-spf:received:received:mime-version:sender :received:in-reply-to:references:from:date:message-id:subject:to :x-original-sender:x-original-authentication-results:reply-to :precedence:mailing-list:list-id:list-post:list-help:list-archive :list-subscribe:list-unsubscribe:content-type; bh=i40xyeqpwT022jrGQ9R6d+wZotxBw5QyTiToikhS6jk=; b=MBgsUwKlH4CtZdkv5YlOAeW6oTs2CStMoYTbhQuFm3ToNHSwZqgCoCiK21IvMN53gL ffbfgapD+Lwg19OKOmgW2DleTv6fpmIg2vl4kqu9NTZYwJD9iPV44fornb5Cl7dTOD7X nyuLW/RCKeyMNANARxB10F75KIKClUNM39/Rc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:mime-version:sender:in-reply-to:references :from:date:message-id:subject:to:x-original-sender :x-original-authentication-results:reply-to:precedence:mailing-list :list-id:list-post:list-help:list-archive:list-subscribe :list-unsubscribe:content-type; b=OPU5DZhBtfjg7WrIlVyRTcipTaxxNr2e5bzs6U6dobVgjYxImpHLslpa4WLF93jZnd /hfis1x43HzjmEOoK9KaLAnt81hb6ju3pP0LhMYNCbB/Wff1wcCIzctlrjg5O3UaxgFK eqqLPVpFW8Bq+4u6y/SGk+JOKr0/F4B7QHeIo= Received: by 10.217.5.9 with SMTP id v9mr165731wes.14.1288104505082; Tue, 26 Oct 2010 07:48:25 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.216.58.143 with SMTP id q15ls3276347wec.1.p; Tue, 26 Oct 2010 07:48:22 -0700 (PDT) Received: by 10.216.53.147 with SMTP id g19mr46950wec.9.1288104502140; Tue, 26 Oct 2010 07:48:22 -0700 (PDT) Received: by 10.216.53.147 with SMTP id g19mr46948wec.9.1288104502047; Tue, 26 Oct 2010 07:48:22 -0700 (PDT) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by gmr-mx.google.com with ESMTP id x80si2540869weq.12.2010.10.26.07.48.20; Tue, 26 Oct 2010 07:48:21 -0700 (PDT) Received-SPF: pass (google.com: domain of johnwcowan@gmail.com designates 74.125.82.50 as permitted sender) client-ip=74.125.82.50; Received: by wwb24 with SMTP id 24so4482457wwb.7 for ; Tue, 26 Oct 2010 07:48:20 -0700 (PDT) Received: by 10.227.128.196 with SMTP id l4mr7947964wbs.32.1288104500843; Tue, 26 Oct 2010 07:48:20 -0700 (PDT) MIME-Version: 1.0 Sender: bpfk-list@googlegroups.com Received: by 10.216.67.129 with HTTP; Tue, 26 Oct 2010 07:48:00 -0700 (PDT) In-Reply-To: <201010260927.37640.phma@phma.optus.nu> References: <201010260117.28780.phma@phma.optus.nu> <201010260927.37640.phma@phma.optus.nu> From: John Cowan Date: Tue, 26 Oct 2010 10:48:00 -0400 Message-ID: Subject: Re: [bpfk] type-3 fu'ivla with different kinds of rafsi To: bpfk-list@googlegroups.com X-Original-Sender: johnwcowan@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of johnwcowan@gmail.com designates 74.125.82.50 as permitted sender) smtp.mail=johnwcowan@gmail.com; dkim=pass (test mode) header.i=@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: List-Post: , List-Help: , List-Archive: List-Subscribe: , List-Unsubscribe: , Content-Type: text/plain; charset=ISO-8859-1 Content-Length: 1844 On Tue, Oct 26, 2010 at 9:27 AM, Pierre Abbat wrote: > That would invalidate both "cmacrntegrale" and "bangrblgaria". I don't think > it's necessary to require this, as the set of foreign words beginning > with "rn" or "rln" or other consonant clusters that give this trouble is > pretty small compared to the set of foreign words that begin with valid > medials that aren't valid initials. Quite so. > Should the Book be edited to > 1. specify that if a fu'ivla can be interpreted as beginning with CVC or CVCC, > then CVCC takes precedence? I think this would be a clarification, not a > change. > 2. specify that a type-3 fu'ivla cannot begin with CVV or CCV? This would be a > change, and would require removing the example "djarspageti". The difference between type-3 and type-4 is relevant to fu'ivla construction, not to analysis. A fu'ivla can look like a type-3 while in fact being defined as a type-4. For example, one could read "spargani'umi" as a type-3 lujvo for some sort of plant (spati) for which "gani'umi" is the Lojbanization, or it could be a type-4 lujvo for the genus _Sparganium_, the bur-reeds (which are plants). If I tried harder, I could probably find a similar example with an apparent 4-letter rafsi. There can be no guaranteed analysis of a fu'ivla: it's any brivla-shaped word that is not a gismu, lujvo, or slinku'i. The point of the type-3 rules is simply to help someone reliably build a fu'ivla and not wind up with any of the other word forms. -- You received this message because you are subscribed to the Google Groups "BPFK" group. To post to this group, send email to bpfk-list@googlegroups.com. To unsubscribe from this group, send email to bpfk-list+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/bpfk-list?hl=en.