Received: from mail-la0-f56.google.com ([209.85.215.56]:47437) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1XghxA-0007H9-5n; Tue, 21 Oct 2014 15:31:04 -0700 Received: by mail-la0-f56.google.com with SMTP id pv20sf181386lab.11 for ; Tue, 21 Oct 2014 15:30:48 -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=Jqfe12iKO0TvaFuMjnQCebch9mb06SlljCxIZpwxlEY=; b=zHUBCLlBKsyR3ivSMJk5MfV9iNdVuXRboMc+kI9VbSfjcyJ42Og/qyur9o9DtGqVYi xuyVXoFIugH34qkFPPH29VZiHMagDHRvmsG/yZBxFkgBAd9Ssc9cHJY8BSBYAFER3PgY rQMFJaZHMKS5MoHdjx2l0SfUMvLj7gvB17nyyCiBhooIGRQc9gWIMERj+Nx4b452Gb9j SV5HH+t352SEW+LxR9hgYH4wgx+7fktHPBLDedqduPELBBtkUZlptNIJLbUbnfkhy2d+ zZBnbPL+TnNZuu8J6+klvzM63sDj3/r2rXhkxW61fgFMSeKRAOegQ9Fk+5HOO40QATbx iqJA== X-Received: by 10.152.203.130 with SMTP id kq2mr36162lac.20.1413930648454; Tue, 21 Oct 2014 15:30:48 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.152.88.13 with SMTP id bc13ls105485lab.21.gmail; Tue, 21 Oct 2014 15:30:47 -0700 (PDT) X-Received: by 10.152.3.168 with SMTP id d8mr5652356lad.0.1413930647638; Tue, 21 Oct 2014 15:30:47 -0700 (PDT) Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com. [2a00:1450:400c:c00::22d]) by gmr-mx.google.com with ESMTPS id jx4si15595wid.1.2014.10.21.15.30.47 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 21 Oct 2014 15:30:47 -0700 (PDT) Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 2a00:1450:400c:c00::22d as permitted sender) client-ip=2a00:1450:400c:c00::22d; Received: by mail-wg0-x22d.google.com with SMTP id m15so2442855wgh.28 for ; Tue, 21 Oct 2014 15:30:47 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.23.104 with SMTP id l8mr45085768wjf.26.1413930647543; Tue, 21 Oct 2014 15:30:47 -0700 (PDT) Received: by 10.217.105.201 with HTTP; Tue, 21 Oct 2014 15:30:47 -0700 (PDT) In-Reply-To: <54462205.3070605@gmail.com> References: <5444FEBF.10200@gmx.de> <544507CD.9050608@gmail.com> <54462205.3070605@gmail.com> Date: Tue, 21 Oct 2014 19:30:47 -0300 Message-ID: Subject: Re: [bpfk] official cmavo form 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:c00::22d 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=047d7b41cdd0fbe3360505f661b6 X-Spam-Score: -1.9 (-) X-Spam_score: -1.9 X-Spam_score_int: -18 X-Spam_bar: - --047d7b41cdd0fbe3360505f661b6 Content-Type: text/plain; charset=UTF-8 On Tue, Oct 21, 2014 at 6:06 AM, And Rosta wrote: > > I would forbid /ii, uu/, but if you were set on allowing them, then things > could be kept in order by a rule that requires every phonological string to > be parsable as a CV sequence, which would rule out /cia/. > It would have been better to not allow them from the start, disallowing them now would be a lot of work. We could still salvage both the CV rule and /cia/ if the buffer vowel is allowed between consonant and glide. > And then could be an orthographic variant of , of > . I doubt the isomorphicists would be very happy with two words written together like that. It would also be somewhat inconsistent that we can't write ".iia" as ".ia", unless ".ia" must be interpreted as ".iia" and "ia" can't be written with a dot in front. But then that would interfere with dotside and names like ".iakob."... 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. --047d7b41cdd0fbe3360505f661b6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Tue, Oct 21, 2014 at 6:06 AM, And Rosta <and.rosta@gmail.com&= gt; wrote:

I would forbid /ii, uu/, but if you were set on allowing them, then things = could be kept in order by a rule that requires every phonological string to= be parsable as a CV sequence, which would rule out /cia/.
=

It would have been better to not allow them from the st= art, disallowing them now would be a lot of work.=C2=A0

We could still salvage both the CV rule and /cia/ if the buffer vowel= is allowed between consonant and glide.=C2=A0
=C2=A0
And then <a'ua> could be an orthographic variant of <a'uua= >, <cia> of <ciia>.

I doubt = the isomorphicists would be very happy with two words written together like= that. It would also be somewhat inconsistent that we can't write "= ;.iia" as ".ia", unless ".ia" must be interpreted = as ".iia" and "ia" can't be written with a dot in f= ront. But then that would interfere with dotside and names like ".iako= b."...

mu'o mi'e xorxes

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