Received: from mail-la0-f62.google.com ([209.85.215.62]:42323) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1Y1vzT-0002gN-9Q; Fri, 19 Dec 2014 03:45:06 -0800 Received: by mail-la0-f62.google.com with SMTP id pv20sf57417lab.7; Fri, 19 Dec 2014 03:44:55 -0800 (PST) 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 :content-type: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; bh=JBLhhH0qLYwdjdc3JIw/u/8/eGCnIOZlFesLa0g106Y=; b=QJH0pBz1Zo0CAf/CEmQjyOxvUlsnyhF7Xc4Yndxol4UUSSz/z8K4PwKeS8jqBhaEWk uRrCfy1Gp7lXd2mPFaOVJIgDADnznFwL8nTtQOAOnZQzbkeEHeFX7Xu2ETFR/Viyv0Wc ZpP2JsVjYOeoCHL5txGlP6aRZcK+lwFfZz+0Ry4y8AMhwGaMbWzbTAaw62peA9d/dgEP 95Hh5CvJA7aEOqtl3Lol6Um9jIBxvTpxSsJS2TKs+YdwMjH+CMz/cSeUGyt1u4QW1JXt 2grdRfQWWyQfujHi8v/1NP3LTvayICmbhe9xLbQmcodf+fHkxWwS1rjtZgLGac8036hL wg8w== X-Received: by 10.152.5.194 with SMTP id u2mr120844lau.3.1418989495763; Fri, 19 Dec 2014 03:44:55 -0800 (PST) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.152.45.97 with SMTP id l1ls1427582lam.59.gmail; Fri, 19 Dec 2014 03:44:55 -0800 (PST) X-Received: by 10.152.2.40 with SMTP id 8mr25725lar.7.1418989495203; Fri, 19 Dec 2014 03:44:55 -0800 (PST) Received: from mail-la0-x236.google.com (mail-la0-x236.google.com. [2a00:1450:4010:c03::236]) by gmr-mx.google.com with ESMTPS id oi7si246436lbb.1.2014.12.19.03.44.55 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 19 Dec 2014 03:44:55 -0800 (PST) Received-SPF: pass (google.com: domain of and.rosta@gmail.com designates 2a00:1450:4010:c03::236 as permitted sender) client-ip=2a00:1450:4010:c03::236; Received: by mail-la0-f54.google.com with SMTP id pv20so689358lab.13 for ; Fri, 19 Dec 2014 03:44:55 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.112.142.201 with SMTP id ry9mr7476495lbb.4.1418989495086; Fri, 19 Dec 2014 03:44:55 -0800 (PST) Received: by 10.114.70.212 with HTTP; Fri, 19 Dec 2014 03:44:54 -0800 (PST) Received: by 10.114.70.212 with HTTP; Fri, 19 Dec 2014 03:44:54 -0800 (PST) In-Reply-To: <5660b66f-68e1-4e9c-b4ce-1713a7bf1491@googlegroups.com> References: <548AC3CB.7090403@gmx.de> <580B9AB84B34485AB4139B921C46CF42@gmail.com> <3ED463A548E74A53BD8F2ECEF0C620F8@gmail.com> <14FDADF47D7841A39D612894E81CC89B@gmail.com> <20141214025736.GB19927@mercury.ccil.org> <20141214190350.GD29313@mercury.ccil.org> <5660b66f-68e1-4e9c-b4ce-1713a7bf1491@googlegroups.com> Date: Fri, 19 Dec 2014 11:44:54 +0000 Message-ID: Subject: Re: [bpfk] official cmavo form From: And Rosta To: bpfk-list@googlegroups.com Content-Type: multipart/alternative; boundary=089e011836aacb7411050a903c00 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:4010:c03::236 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: , X-Spam-Score: -1.9 (-) X-Spam_score: -1.9 X-Spam_score_int: -18 X-Spam_bar: - Content-Length: 4755 --089e011836aacb7411050a903c00 Content-Type: text/plain; charset=UTF-8 On 19 Dec 2014 01:57, "guskant" wrote: > Currently, "2. disallow CgV in cmevla/fu'ivla/ma'ovla" is predominant. > > https://docs.google.com/forms/d/1kJLBvjkoDpmvA9vJS_lf8SpCYAZvY4bMx1pj8uhWqRs/viewanalytics > > > > As a supporter of "1.3.1. allow CgV in cmevla, disallow it in fu'ivla/ma'ovla", I make a comment here: > > CgV in cmevla does not affect lexical analysis, while that in fu'ivla/ma'ovla does. Disallowing CgV in cmevla is very strong restriction. It affects not only traditional names like {nitcion}, or popular names like {tuitr}, but also a standard of lojbanization of words of natural languages. CgV in cmevla sometimes makes things easy. For example, many Chinese names have CgV-like phoneme strings. Chinese "Huan", "Han" and "Hu An" are distinguished from each other. If CgV is disallowed in cmevla, it will be difficult to find out a reasonable standard of lojbanization of them. I'd be in favour of (3), defining CGV as equivalent to CGGV (the same G in each case). The equivalence is certainly orthographic; I can't say if it's also phonological, because there is no credible consensus analysis of Lojban phonology. Any potential phonetic contrast between CGV & CGGV is feeble, and hence a phonological contrast between them is undesirable. This then allows CGV in cmevla. Whether it allows CGV in other sorts of word depends entirely and independently on whether words can begin with GV, which would be a matter for a different poll. --And. -- 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. --089e011836aacb7411050a903c00 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On 19 Dec 2014 01:57, "guskant" <gusni.kantu@gmail.com> wrote:

> Currently, "2. disallow CgV in cmevla/fu'ivla/= ma'ovla" is predominant.
>
> https://docs.google.com/forms/d/1kJLBvjkoD= pmvA9vJS_lf8SpCYAZvY4bMx1pj8uhWqRs/viewanalytics
>
>
>
> As a supporter of "1.3.1. allow CgV in cmevla, disallow it in fu&= #39;ivla/ma'ovla", I make a comment here:
>
> CgV in cmevla does not affect lexical analysis, while that in fu'i= vla/ma'ovla does. Disallowing CgV in cmevla is very strong restriction.= It affects not only traditional names like {nitcion}, or popular names lik= e {tuitr}, but also a standard of lojbanization of words of natural languag= es. CgV in cmevla sometimes makes things easy. For example, many Chinese na= mes have CgV-like phoneme strings. Chinese "Huan", "Han"= ; and "Hu An" are distinguished from each other. If CgV is disall= owed in cmevla, it will be difficult to find out a reasonable standard of l= ojbanization of them.

I'd be in favour of (3), defining CGV as equivalent to C= GGV (the same G in each case). The equivalence is certainly orthographic; I= can't say if it's also phonological, because there is no credible = consensus analysis of Lojban phonology. Any potential phonetic contrast bet= ween CGV & CGGV is feeble, and hence a phonological contrast between th= em is undesirable.

This then allows CGV in cmevla. Whether it allows CGV in oth= er sorts of word depends entirely and independently on whether words can be= gin with GV, which would be a matter for a different poll.

--And.

--
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.
--089e011836aacb7411050a903c00--