Received: from mail-wi0-f186.google.com ([209.85.212.186]:53821) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1XgCbG-0007Y7-If; Mon, 20 Oct 2014 06:02:22 -0700 Received: by mail-wi0-f186.google.com with SMTP id fb4sf420373wid.13 for ; Mon, 20 Oct 2014 06:02:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-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 :content-transfer-encoding; bh=MW/mahbEVgbZ7EPiukecJyWuf1zGkzLQDHF1A7QiB7E=; b=yS301wXRwYCpzFF635KD3J3fAcxc+Nwd+G4cOaMbMZML4z+D7SH3332fBQ0qC0HUnM KNENw9fsDptLUWFnXpDr+X29gSCNMIFl5wuoIMivrJXXKqpYvee6Z2uPmVHSgPEKUmk9 BlErJMA+bh26Hsw9Puj7pjhnraTdtgRsESRItWVm5U/kQ7QdQJGqGT3FlCYj2cwXm5Sv QNokHpUUqqZ5NIqsGDQd8KGrJoWxKA9HfFggJTrrPX8Cd0CNXm2Axpbapb/5ita2tCIS lOYAwjGrzWpVlctAbAZCLjFQV59Lybtkb25+XxSRDQ6RuDbQiYW3tXkbAbqte9/gVAgu Eq9w== X-Received: by 10.152.6.193 with SMTP id d1mr1424laa.24.1413810125733; Mon, 20 Oct 2014 06:02:05 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.152.25.165 with SMTP id d5ls432979lag.1.gmail; Mon, 20 Oct 2014 06:02:05 -0700 (PDT) X-Received: by 10.152.88.70 with SMTP id be6mr4052000lab.1.1413810125097; Mon, 20 Oct 2014 06:02:05 -0700 (PDT) Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com. [2a00:1450:400c:c05::22d]) by gmr-mx.google.com with ESMTPS id o2si360268wib.2.2014.10.20.06.02.05 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 20 Oct 2014 06:02:05 -0700 (PDT) Received-SPF: pass (google.com: domain of and.rosta@gmail.com designates 2a00:1450:400c:c05::22d as permitted sender) client-ip=2a00:1450:400c:c05::22d; Received: by mail-wi0-x22d.google.com with SMTP id fb4so7084343wid.0 for ; Mon, 20 Oct 2014 06:02:05 -0700 (PDT) X-Received: by 10.194.85.229 with SMTP id k5mr31109935wjz.19.1413810124942; Mon, 20 Oct 2014 06:02:04 -0700 (PDT) Received: from [192.168.1.208] ([95.147.226.113]) by mx.google.com with ESMTPSA id wm6sm11844173wjb.5.2014.10.20.06.02.03 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 20 Oct 2014 06:02:04 -0700 (PDT) Message-ID: <544507CD.9050608@gmail.com> Date: Mon, 20 Oct 2014 14:02:05 +0100 From: And Rosta User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120711 Thunderbird/14.0 MIME-Version: 1.0 To: bpfk-list@googlegroups.com Subject: Re: [bpfk] official cmavo form References: <5444FEBF.10200@gmx.de> In-Reply-To: <5444FEBF.10200@gmx.de> X-Original-Sender: and.rosta@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of and.rosta@gmail.com designates 2a00:1450:400c:c05::22d as permitted sender) smtp.mail=and.rosta@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: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-Spam-Score: -2.6 (--) X-Spam_score: -2.6 X-Spam_score_int: -25 X-Spam_bar: -- selpa'i, On 20/10/2014 13:23: > la .xorxes. cu cusku di'e >> The PEG morphology is not yet official. I would have been happy to >> disallow "consonant glide" as a valid onset altogether, but other people >> were opposed to that at the time. Some would have even allowed "CC >> glide" as a syllable onset, so allowing a single consonant was something >> of a compromise. I would be happy to go with the more strict "onset <- >> h / glide / initial" if that's the new consensus, although in that case >> there are probably several words in jbovlaste that would have to be revi= sed. > > My personal position is that I definitely would want to disallow any CiV = where C is a sibilant (e.g. ?{sia}) or a dental (e.g. ?{tia}) [1], because = they tend to degenerate into simpler forms over time (e.g. {ca} and {tca} r= espectively) and are hard to distiniguish for many people. I would ban them= in any word, not just in cmavo. > > Regarding forms like {kia} (which must be pronounced [kja]), they bother = me slightly less, but I wouldn't miss them if they got removed. Why must Lojban have onsets and syllabification? /Cia/ is problematic only = if /Ci-/ must constitute an onset. > So one could either ban just the ones that are likely to cause > problems, or ban all for simplicity's sake. I'd ban none. > I see no problems with {ie'o} as a cmavo form. How about {a'ua}? > [1] The are some additional phonotactic constraints I would install, but = the details seem irrelevant here. I think Lojban already has way more phonotactic constraints than is necessa= ry... --And. =20 --=20 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 e= mail 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.