Received: from mail-lb0-f189.google.com ([209.85.217.189]:53513) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1Xi7NY-0001d2-7l; Sat, 25 Oct 2014 12:52:08 -0700 Received: by mail-lb0-f189.google.com with SMTP id f15sf280003lbj.6 for ; Sat, 25 Oct 2014 12:51:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :x-original-sender:x-original-authentication-results:reply-to :precedence:mailing-list:list-id:list-post:list-help:list-archive :sender:list-subscribe:list-unsubscribe:content-type; bh=KU5RBXmrHxLGQ7FOXrfZGFq3JMVlXff+6EAa7eGT5gM=; b=ByVqZXGwCYnAW/MywMQVacm3oQ71d+RVn4Mr+YrzFREVUSCTEtVUS/Y7EgZheiqN92 0N9L2mOy6CDuLkb3tcXjOJfsgZoz9DTsUdxpKStd0JEa1EnQPZ5ICsr8P963WFxtVRpg 8Uj1Csk5gNd6/FBKicMcIdxaY79KwmPs0/8R2UZPAPF7OI40zA6yshhZlOu0B6wtDU2g MjyMJDDUFvBUbEMQJ7AfipWHTCj2eEMQp07zrK+FEC0Gs6TszOu4lvtwPKe8raAWg/d8 te7d0oOjnBsnRg6EGXOePYl79tI//+xazp5pSKpH5Qk0LHu2EqQtpkhh2XHSyyqJlrIk 9B1g== X-Received: by 10.180.9.163 with SMTP id a3mr37257wib.1.1414266712192; Sat, 25 Oct 2014 12:51:52 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.180.97.40 with SMTP id dx8ls287380wib.28.canary; Sat, 25 Oct 2014 12:51:51 -0700 (PDT) X-Received: by 10.194.242.36 with SMTP id wn4mr13366wjc.4.1414266711883; Sat, 25 Oct 2014 12:51:51 -0700 (PDT) Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com. [2a00:1450:400c:c05::229]) by gmr-mx.google.com with ESMTPS id cy3si275837wib.2.2014.10.25.12.51.51 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 25 Oct 2014 12:51:51 -0700 (PDT) Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 2a00:1450:400c:c05::229 as permitted sender) client-ip=2a00:1450:400c:c05::229; Received: by mail-wi0-f169.google.com with SMTP id q5so3377448wiv.0 for ; Sat, 25 Oct 2014 12:51:51 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.90.210 with SMTP id by18mr13540586wjb.34.1414266711792; Sat, 25 Oct 2014 12:51:51 -0700 (PDT) Received: by 10.217.105.201 with HTTP; Sat, 25 Oct 2014 12:51:51 -0700 (PDT) In-Reply-To: <544BF508.3060500@gmail.com> References: <33A9DB5129C54FFF85FCDD708B6909D8@gmail.com> <9c2066d4-8da6-48ec-9cfb-63f79ca42187@googlegroups.com> <20141025153624.GA1727@mercury.ccil.org> <544BF508.3060500@gmail.com> Date: Sat, 25 Oct 2014 16:51:51 -0300 Message-ID: Subject: Re: [bpfk] camxes and syllabification in zi'evla From: =?UTF-8?Q?Jorge_Llamb=C3=ADas?= To: bpfk-list@googlegroups.com X-Original-Sender: jjllambias@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jjllambias@gmail.com designates 2a00:1450:400c:c05::229 as permitted sender) smtp.mail=jjllambias@gmail.com; dkim=pass header.i=@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=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=047d7bfcf662f961d8050644a0f1 X-Spam-Score: -1.9 (-) X-Spam_score: -1.9 X-Spam_score_int: -18 X-Spam_bar: - --047d7bfcf662f961d8050644a0f1 Content-Type: text/plain; charset=UTF-8 On Sat, Oct 25, 2014 at 4:07 PM, And Rosta wrote: > > But if Lojban syllabification is essentially CV (or simplex onset + > simplex nucleus), give or take any complications with glides, why bother > with a bunch of morphophonological constraints? Is it just because they are > codified in CLL (albeit in erroneously phonological terms) and therefore > cannotbe abandoned? Would abandoning morphophonological constraints > invalidate existing words or text? > Abandoning the constraints against double consonants, voiced-unvoiced clusters, sibilant-sibilant clusters, x-c/k clusters and mz would not invalidate anything, as far as I can tell. The distinction between valid and invalid "onsets" is mostly what is needed to delimit words. mu'o mi'e xorxes -- 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. --047d7bfcf662f961d8050644a0f1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Sat, Oct 25, 2014 at 4:07 PM, And Rosta <and.rosta@gmail.com&= gt; wrote:

But if Lojban syllabification is essentially CV (or simplex onset + simplex= nucleus), give or take any complications with glides, why bother with a bu= nch of morphophonological constraints? Is it just because they are codified= in CLL (albeit in erroneously phonological terms) and therefore cannotbe a= bandoned?=C2=A0 Would abandoning morphophonological constraints invalidate = existing words or text?

Abandoning the = constraints against double consonants, voiced-unvoiced clusters, sibilant-s= ibilant clusters, x-c/k clusters and mz would not invalidate anything, as f= ar as I can tell. The distinction between valid and invalid "onsets&qu= ot; is mostly what is needed to delimit words.

mu&= #39;o mi'e xorxes=C2=A0
=C2=A0

--
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.
--047d7bfcf662f961d8050644a0f1--