Received: from mail-qy0-f189.google.com ([209.85.216.189]:53258) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1RR8zG-0000ZL-Lm; Thu, 17 Nov 2011 12:55:11 -0800 Received: by qyk29 with SMTP id 29sf7395817qyk.16 for ; Thu, 17 Nov 2011 12:55:03 -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; bh=8TZKkbiX6K87c1lp7VYl2fljLEP/QaFEVOsTepekvZ8=; b=BQnFCQl2I0pDxU/KG9p+kVEEKtKtW6p340AB/IzjYsFxn1IGteKpJMykzSQykgVQPr Qa10g8mhoVYfDd/OvNWSOujjdg9DsMM0nam5vtJSCYnI7qZJs3w33gRr53mumXAZnjCy pZieDNUk8SlMlU+lvjBJ44sLdPsOyWW67HNMQ= Received: by 10.224.78.197 with SMTP id m5mr56953qak.6.1321563301326; Thu, 17 Nov 2011 12:55:01 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.224.209.134 with SMTP id gg6ls5577532qab.2.gmail; Thu, 17 Nov 2011 12:55:00 -0800 (PST) MIME-Version: 1.0 Received: by 10.224.0.200 with SMTP id 8mr61589qac.1.1321563300350; Thu, 17 Nov 2011 12:55:00 -0800 (PST) Received: by d17g2000yql.googlegroups.com with HTTP; Thu, 17 Nov 2011 12:55:00 -0800 (PST) Date: Thu, 17 Nov 2011 12:55:00 -0800 (PST) In-Reply-To: <201111171409.08825.phma@phma.optus.nu> References: <20b482a7-b58a-4e4a-a3f7-27b49ba861c0@p9g2000vbb.googlegroups.com> <201111171409.08825.phma@phma.optus.nu> 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: <4d00e419-9ede-42cf-963e-7a394bcbed13@d17g2000yql.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=ISO-8859-1 X-Spam-Score: -0.7 (/) X-Spam_score: -0.7 X-Spam_score_int: -6 X-Spam_bar: / Pierre: The change of {fi'u} *does* seem to break existing text, and that is bad. I could find no other PA, though, which needed to take both the previous and the following number string. I'm also curious as to how many texts has a {fi'u}-fraction - perhaps they could be changed? When alone, fi'u could easily be defined as the golden ratio, though this slightly breaks the consistensy. Still, how often does one use that? I seem to have missed {ci'i} altogether. I'm initially sceptical as to whether an Aleph cardinal should have its "own" cmavo, but if it's placed in PA3, it can take the next number string. I don't know enough about aleph cardinality to know if the construct {ci'i NUMBER} means infinity for any NUMBER. If so, this could be the default value with no string following. Perhaps we need new cmavo for keeping order on number strings, but I'm not sure we need one for the two uses of {pi'e}. They seem to work in the same way, differing only in semantics? This is easily resolved by context. In my system, {pa pi'e pi so pi'e pi rau} is grammatical. It probably means 1:9/10:enough. Using the clock as an example, this could mean 1:00:54+enough. {pi} and {ra'u} make no sense when they are the only numbers in a number string. This is a problem. I take my suggestion back that {ji'i} should be grammatical on its own. I'd like to see that a number string cannot contain only PA5. Perhaps {pi pai} is nonsense - you might be right. Djandus: I, too, agree that selma'o should be based purely on function. So yes, there is no reason not to combine PA2 and PA6. Let's call this hypothetical PA for PA2* If we fuse PA2 and PA6, we need a word for "end number string". Otherwise, I think we could do without, since you could just end a number string by beginning a new one. After all, why have two number strings of the same selma'o describing the same number? PA4 and PA5 cannot be combined though, since only 1 of each PA5 makes sense in a number string. (this, by the way is also a problem! if {li pi pa ji'i} is grammatical, why not {li pi pa pi}? Solution: Only one of each PA5 is permitted. That's a violation of the definition of a selma'o, right? Darn.) I wouldn't like to see extra grammatical rules for subgroups inside one selma'o - then I'd rather see ten selma'o of PA. (why not? It encompasses 40 cmavo or so) Right. Every grammatical string should not necesarrily be meaningful, but it'd be nice if it were so, even if the meaning it conveys is contradicory or silly. I see it as right-grouping, because {za'u su'o fi'u vo} (more than at least one divided by four) is understood (za'u(su'o(fi'u vo))). Futhermore, {pa re ci} is structured (semantically, not necessarily grammatically) Otherwise, I agree with you completely. -- 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@googlegroups.com. For more options, visit this group at http://groups.google.com/group/lojban?hl=en.