Received: from mail-qg0-f63.google.com ([209.85.192.63]:60639) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1XiRwJ-0003pj-8T; Sun, 26 Oct 2014 10:49:23 -0700 Received: by mail-qg0-f63.google.com with SMTP id j5sf270464qga.28 for ; Sun, 26 Oct 2014 10:49:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=date:from:to:subject:message-id:references:mime-version:in-reply-to :user-agent:sender: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:content-disposition; bh=v2oJInQyYuh+9OGQrqcpCHgDGrq9nfJdcXHoC1oMQEA=; b=SAaw25DgzGCXeiDlIIn6yoNhmFvITRNIq8L3FoHnkiJCPoJy6QC9O8Lp8JIV0k9bID N1UEA5zNjqM425mGfD5hdqaDj5mFKTxL14FpUqNZ07lqUjtgXu+b/FO0ml8CM1YHRFMC 8jEyL9WVAQnwixINF4ODMmniT7v73Rto3N8pHiZ0ihQ/pkT2/x+IY7WmjrCSVpzwNoQX qdyf7EPM+oRiKEfI/Lx0iLoujpItsA6Vz2hYPR3Uv0ldtU3c4mWgUGIvrgOJO+gUehpD /uNf2KoFA1jus7rVrIEWCG7levHVGesGTZBoFLrUu8oJsXfOeJXxvm+W2P0D+zH69PZo u7Dg== X-Received: by 10.140.82.75 with SMTP id g69mr3322qgd.9.1414345748320; Sun, 26 Oct 2014 10:49:08 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.140.19.147 with SMTP id 19ls2321804qgh.78.gmail; Sun, 26 Oct 2014 10:49:08 -0700 (PDT) X-Received: by 10.236.53.34 with SMTP id f22mr11411349yhc.51.1414345748152; Sun, 26 Oct 2014 10:49:08 -0700 (PDT) Received: from earth.ccil.org (earth.ccil.org. [192.190.237.11]) by gmr-mx.google.com with ESMTPS id hz7si513726igb.2.2014.10.26.10.49.07 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Sun, 26 Oct 2014 10:49:08 -0700 (PDT) Received-SPF: pass (google.com: domain of cowan@ccil.org designates 192.190.237.11 as permitted sender) client-ip=192.190.237.11; Received: from cowan by earth.ccil.org with local (Exim 4.72) (envelope-from ) id 1XiRwA-0006gl-HL for bpfk-list@googlegroups.com; Sun, 26 Oct 2014 13:49:06 -0400 Date: Sun, 26 Oct 2014 13:49:06 -0400 From: John Cowan To: bpfk-list@googlegroups.com Subject: Re: [bpfk] camxes and syllabification in zi'evla Message-ID: <20141026174903.GC9104@mercury.ccil.org> References: <20141025153624.GA1727@mercury.ccil.org> <544BF508.3060500@gmail.com> <24AD03E6AEA1476F9B53E0EE111750E9@gmail.com> <544BF94F.3040204@gmail.com> <544CB576.2070503@gmail.com> <544CF7D1.9050300@gmail.com> MIME-Version: 1.0 In-Reply-To: <544CF7D1.9050300@gmail.com> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: bpfk-list@googlegroups.com X-Original-Sender: cowan@ccil.org X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of cowan@ccil.org designates 192.190.237.11 as permitted sender) smtp.mail=cowan@ccil.org 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: text/plain; charset=ISO-8859-1 Content-Disposition: inline X-Spam-Score: -1.9 (-) X-Spam_score: -1.9 X-Spam_score_int: -18 X-Spam_bar: - And Rosta scripsit: > A very precise specification of the what, but not so clear on the > why. Are there rationales other than "Because CLL says so"? And > if that is the only rationale, and the rules could be drastically > simplified without invalidating any existing lexis, why not simplify > the rules? (Given that anyway the CLL rules are plainly not complete > and fully specified.) My intention when writing CLL was to specify certain word forms as valid by construction, but not to say what else might be valid, much less what was not valid. I now think that was a mistake, and CLL should have prescribed the word forms of fu'ivla and cmevla much more narrowly. The intention was to allow forms that were as close as possible (but no closer) to the highly varied natural-language sources. I also believe that the attempt to prescribe allophony, even unconditioned allophony, was also a mistake. We should have said "Six vowels, 17 consonants, these are the normative forms, how you talk is up to you as long as your interlocutors understand you." -- John Cowan http://www.ccil.org/~cowan cowan@ccil.org The Unicode Standard does not encode idiosyncratic, personal, novel, or private use characters, nor does it encode logos or graphics. -- 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.