Received: from mail-vw0-f61.google.com ([209.85.212.61]:37627) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1RRONJ-0006hS-8y; Fri, 18 Nov 2011 05:21:02 -0800 Received: by vbbez10 with SMTP id ez10sf379973vbb.16 for ; Fri, 18 Nov 2011 05:20:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=x-beenthere:mime-version:date:in-reply-to:references:user-agent :x-http-useragent:message-id:subject:from: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=mQ83GEdih3eNq4p6HzAq4a14e+Fwz/Dyt5r09ZnauTk=; b=i7m9JuMcmsut5Erargm6nWt3ItYhvg8lMPrAjSCy1epNPenFVPYLZnaWrV6okscaSu K1fHE/wo3PzTMmcprhm1D0aBZSlsKgY63vE+RjRiJdeky+baz3pfsWsFWOr6LVRo6jOJ 63lkQq/LV2H3v+3bffbIeQV+eLaIG6C6a0sKw= Received: by 10.52.187.34 with SMTP id fp2mr1355388vdc.9.1321622451994; Fri, 18 Nov 2011 05:20:51 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.220.108.71 with SMTP id e7ls1175363vcp.3.canary; Fri, 18 Nov 2011 05:20:50 -0800 (PST) MIME-Version: 1.0 Received: by 10.52.173.111 with SMTP id bj15mr1144934vdc.0.1321622450420; Fri, 18 Nov 2011 05:20:50 -0800 (PST) Received: by h5g2000yqk.googlegroups.com with HTTP; Fri, 18 Nov 2011 05:20:50 -0800 (PST) Date: Fri, 18 Nov 2011 05:20:50 -0800 (PST) In-Reply-To: References: <20b482a7-b58a-4e4a-a3f7-27b49ba861c0@p9g2000vbb.googlegroups.com> <201111171409.08825.phma@phma.optus.nu> <4d00e419-9ede-42cf-963e-7a394bcbed13@d17g2000yql.googlegroups.com> User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows NT 6.1; rv:8.0) Gecko/20100101 Firefox/8.0,gzip(gfe) Message-ID: <9ae95757-6243-481a-9042-a12a0f2eb834@h5g2000yqk.googlegroups.com> Subject: [lojban] Re: New PA-proposal From: la klaku To: lojban X-Original-Sender: jakobnybonissen@gmail.com X-Original-Authentication-Results: ls.google.com; spf=pass (google.com: domain of jakobnybonissen@gmail.com designates internal as permitted sender) smtp.mail=jakobnybonissen@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=windows-1252 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -0.7 (/) X-Spam_score: -0.7 X-Spam_score_int: -6 X-Spam_bar: / MorphemeAddict: We can't allow different PA to follow different grammar, that much is true. We would need in total four grammatical classes (PA, DUhE, CEhI and PIhE, for instance). PIhE should bind two strings together, so we need a new in PIhE (let's call it {xi'e}, to make an analogy to {pi'e}), which just binds two strings together without any meaning. This is used to say, for instance {li du'a pi'i fi'u ro xi'e mu no} (too many out of them all, which is fifty) to avoid confusion as to what is equal to fifty - them all or the fraction (in this case, it's them all). So I agree. If we just make three classes, one can still say all kinds of nonsense, but it least we know how to parse it correctly. Xorxes (Jorge): I agree to all of the definitions in your proposal, but have a few things against the grammar: 1) How do we know which numbers are contradictory? Are "many" a contradiction to "less than X"? This needs a ton of arbitrary rules. I vote that two number strings should always be joined with .e. In cases where .a is needed, use two numbers. By the way, this also ensures a nice rule: One number, one value. Anyway, this is semantics, and should not affect the decision in making the new grammar. 2) The exact gouping confuses me a bit. How do you know, in your above 50-too-many example, what 50 refers to? The fraction or them all? That is why I propose the use of number strings to avoid confusion. Mark Shoulson: It's totally a cop-out, and if I were in charge, I'd see many more selma'o than now. I'm not, so perhaps we should keep it to a minimum Thus my current suggestion: selma'o PA: xo, all of current PA1 and PA2. Combines with each other in the same string. selma'o DUhE: du'e, mo'a, rau, ro, so'a, so'e, so'i, so'o, so'u, xo'e, no'o, pai, te=92o and tu=92o. Constitute their own string. selma'o CEhI: ce'i, ma'u, me'i, ni'u. za'u, da'a, su'e, su'o, ka'o and fi=92u. (and ci'i?): Takes the next string and convert in into a new string. Right-grouping. selma'o PIhE: pi'e, ki'o, xi'e (NEW), ji'i, pi and ra'e. Internal modifier: Binds two strings together. Needs to be adjectent to a string. This sadly allows for totally crap numbers like {li ce'i pi pi xi'e rau re no}, but at least a computer can parse it, and we should understand it if it made sense (li > re no) I know I seem a bit pushy, but I'd like to see some product so the discussion won't just go to into oblivion when the thread dies. --=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.