Received: from mail-bk0-f61.google.com ([209.85.214.61]:51016) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1T1S7x-0006iy-AO; Tue, 14 Aug 2012 18:10:43 -0700 Received: by bkwj4 with SMTP id j4sf304594bkw.16 for ; Tue, 14 Aug 2012 18:10:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=x-beenthere:received-spf: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:x-google-group-id:list-post:list-help:list-archive:sender :list-subscribe:list-unsubscribe:content-type :content-transfer-encoding; bh=nWfWcHOrPnLq2zIbnxu0dvOX2ZJEOzgnaLu5JGcv0nw=; b=zLHdWZ5DPaTRcziBHBiVTE23Bbzf6EgbhDFTg0Zw4XZleeM0I5mJ9LHaJfjBzS0h5c FU08LCdt8amNqV1paHNdp3X2RL73LhuadK9+/VlYCpF5+zhSLd54+M7ityWd2DBobTv9 MP6uiGZNYQZe16QWMKvawCnEIGwCvdPYUVoBM= Received: by 10.216.133.156 with SMTP id q28mr342039wei.53.1344993018259; Tue, 14 Aug 2012 18:10:18 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.216.141.22 with SMTP id f22ls1282736wej.0.gmail; Tue, 14 Aug 2012 18:10:17 -0700 (PDT) Received: by 10.180.96.42 with SMTP id dp10mr2463609wib.2.1344993017404; Tue, 14 Aug 2012 18:10:17 -0700 (PDT) Received: by 10.180.96.42 with SMTP id dp10mr2463608wib.2.1344993017395; Tue, 14 Aug 2012 18:10:17 -0700 (PDT) Received: from mail-wg0-f43.google.com (mail-wg0-f43.google.com [74.125.82.43]) by gmr-mx.google.com with ESMTPS id cx9si1154wib.0.2012.08.14.18.10.17 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 14 Aug 2012 18:10:17 -0700 (PDT) Received-SPF: pass (google.com: domain of and.rosta@gmail.com designates 74.125.82.43 as permitted sender) client-ip=74.125.82.43; Received: by wgbdr1 with SMTP id dr1so800848wgb.12 for ; Tue, 14 Aug 2012 18:10:17 -0700 (PDT) Received: by 10.216.236.24 with SMTP id v24mr8839035weq.18.1344993017225; Tue, 14 Aug 2012 18:10:17 -0700 (PDT) Received: from [192.168.1.77] (87-194-76-177.bethere.co.uk. [87.194.76.177]) by mx.google.com with ESMTPS id ck9sm23304wib.2.2012.08.14.18.10.14 (version=SSLv3 cipher=OTHER); Tue, 14 Aug 2012 18:10:16 -0700 (PDT) Message-ID: <502AF6F0.8050601@gmail.com> Date: Wed, 15 Aug 2012 02:10:08 +0100 From: And Rosta User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.28) Gecko/20120306 Thunderbird/3.1.20 MIME-Version: 1.0 To: lojban@googlegroups.com Subject: Re: [lojban] Re: Are Natlang the best case for entropy in communication ? References: <502A6B71.7080407@gmail.com> In-Reply-To: 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 74.125.82.43 as permitted sender) smtp.mail=and.rosta@gmail.com; dkim=pass header.i=@gmail.com Reply-To: lojban@googlegroups.com Precedence: list Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com List-ID: X-Google-Group-Id: 1004133512417 List-Post: , List-Help: , List-Archive: Sender: lojban@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-Spam-Score: -0.7 (/) X-Spam_score: -0.7 X-Spam_score_int: -6 X-Spam_bar: / Michael Turniansky, On 14/08/2012 18:16: > I am sorry you don't see my point. I will try to clarify. I never > said that the digits aren't maximally distinct (although in addition > to rei/re confusion, "pi" can easily be confused with bi (and to a > lesser extent, pa) in a noisy environment.) But you make two claims > above -- A) "[maximal distinctiveness] is a virtue, especially in > lexical domains where context is unlikely to be able to disambiguate, > such digits and letters" and B) "partial internal sameness enhances > learnability" These are contradictory claims. Which is the virtuous > one? They're both virtues, but, as is often the case with virtues, not fully com= patible. For the digits, I think Lojban is right to prioritize distinctiven= ess over learnability, tho something like {ki ke ka ko ku mi me ma mo mu} w= ould also have worked equally well (i.e. not varying the consonant for ever= y digit, and choosing very distinct consonants). Elsewhere, I think (as I s= aid in my last msg) the pattern of keeping the consonant the same within pa= radigms and varying the vowel is a good one. >In original Loglan, the digits 0-9 were ni, ne, to, te, fo fe, > so, se, vo, ve, which directly addresses point B,but in lojban we > chose to chose A over B WITH REGARD TO DIGITS, and tout it in the CLL > with a direct call-out. In letters (and in many other selma'o) , on > the other hand, we chose option B, despite the fact that "letters" is > one of the places that you say A is better suited. Sure: just as credit is due for the digit names, debit is duefor the letter= names. I don't think that means CLL should keep shtoom about the credit fo= r the digit names, tho. > And in fact, cmavo > space is so tight, confusion will always be a problem in noisy > environments ("Did he say "lo pa jatna cu morsi" or "lo ba jatna cu > morsi"?") The big answer is "So what? Nothing we can do about it to > satisfy all situations. Of course there's something that can be done about it! Ensure that words th= at context will be least likely to be able to disambiguate have the more di= stinct forms. That minimizes the chances of mishearing. > Humans have evolved to deal with ambiguity in communication, inlcuding "k= i'a/ke'o. As I said in my last, when context doesn't disambiguate, the language chang= es. >So why draw attention to it in the CLL?" was my only point here. Because it's a good design feature. It's an area of the language that doesn= 't need to be fixed. --And. --=20 You received this message because you are subscribed to the Google Groups "= lojban" group. To post to this group, send email to lojban@googlegroups.com. To unsubscribe from this group, send email to lojban+unsubscribe@googlegrou= ps.com. For more options, visit this group at http://groups.google.com/group/lojban= ?hl=3Den.