Received: from mail-bw0-f61.google.com ([209.85.214.61]:50357) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1RRGPo-0003Qk-Df; Thu, 17 Nov 2011 20:51:09 -0800 Received: by bkat2 with SMTP id t2sf2792944bka.16 for ; Thu, 17 Nov 2011 20:50:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:mime-version:in-reply-to:references:from :date:message-id:subject: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=go9sDNAAFmdpozfM2CZV+5Gud/IGVZI7KSh/hXwrFHg=; b=Ii6c0lcHab+2c6+m2vONQcPjB90FjBlVlJEuzoDxvhv+Fvug9DkgR8IO5vH2/EB+xW QdbAU3vMvtvf4n/d5B3Ue8CRxgYB3bVS1XdnUUmuza38ar0I2/HS9rPxX2hwzDDIgdXl 914Hgo3Ku6hsilno4/lZx8dAAON/jT54cU2XI= Received: by 10.205.128.137 with SMTP id he9mr198396bkc.33.1321591853854; Thu, 17 Nov 2011 20:50:53 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.204.152.154 with SMTP id g26ls313323bkw.3.gmail; Thu, 17 Nov 2011 20:50:52 -0800 (PST) Received: by 10.204.151.81 with SMTP id b17mr198624bkw.3.1321591852525; Thu, 17 Nov 2011 20:50:52 -0800 (PST) Received: by 10.204.151.81 with SMTP id b17mr198623bkw.3.1321591852496; Thu, 17 Nov 2011 20:50:52 -0800 (PST) Received: from mail-bw0-f52.google.com (mail-bw0-f52.google.com [209.85.214.52]) by gmr-mx.google.com with ESMTPS id o14si5743534bkc.1.2011.11.17.20.50.52 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 17 Nov 2011 20:50:52 -0800 (PST) Received-SPF: pass (google.com: domain of lytlesw@gmail.com designates 209.85.214.52 as permitted sender) client-ip=209.85.214.52; Received: by mail-bw0-f52.google.com with SMTP id s6so4143478bka.11 for ; Thu, 17 Nov 2011 20:50:52 -0800 (PST) Received: by 10.204.148.146 with SMTP id p18mr1564536bkv.36.1321591852229; Thu, 17 Nov 2011 20:50:52 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.60.198 with HTTP; Thu, 17 Nov 2011 20:50:31 -0800 (PST) In-Reply-To: <4d00e419-9ede-42cf-963e-7a394bcbed13@d17g2000yql.googlegroups.com> References: <20b482a7-b58a-4e4a-a3f7-27b49ba861c0@p9g2000vbb.googlegroups.com> <201111171409.08825.phma@phma.optus.nu> <4d00e419-9ede-42cf-963e-7a394bcbed13@d17g2000yql.googlegroups.com> From: MorphemeAddict Date: Thu, 17 Nov 2011 23:50:31 -0500 Message-ID: Subject: Re: [lojban] Re: New PA-proposal To: lojban@googlegroups.com X-Original-Sender: lytlesw@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of lytlesw@gmail.com designates 209.85.214.52 as permitted sender) smtp.mail=lytlesw@gmail.com; dkim=pass (test mode) 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: multipart/alternative; boundary=0015175ce046e3e65e04b1fb14de X-Spam-Score: -0.7 (/) X-Spam_score: -0.7 X-Spam_score_int: -6 X-Spam_bar: / --0015175ce046e3e65e04b1fb14de Content-Type: text/plain; charset=ISO-8859-1 It seems that people are attempting to create a grammar for PA that produces all and ONLY those number strings that make sense. This is worthwhile, I think, but also unnecessary. We don't worry about which letters produce grammatical sentences, only which words. Also, given that Lojban's grammar treats all gismu equally and all members of a selma'o equally, there is strong precedent for not creating special grammar for PA. stevo On Thu, Nov 17, 2011 at 3:55 PM, la klaku wrote: > 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. > > -- 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. --0015175ce046e3e65e04b1fb14de Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
It seems that people are attempting to create a grammar for PA that pr= oduces all and ONLY those number strings that make sense. This is worthwhil= e, I think, but also unnecessary. We don't worry about which letters pr= oduce grammatical sentences, only which words. Also, given that Lojban'= s grammar treats all gismu equally and all members of a selma'o equally= , there is strong precedent=A0for not creating special grammar for PA.
=A0
stevo

On Thu, No= v 17, 2011 at 3:55 PM, la klaku <jakobnybonissen@gmail.com> wrote:
=
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&= #39;s
placed in PA3, it can take the next number string. I don't know enough<= br> 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<= br> 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 probab= ly
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 num= ber
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,<= br> 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, sinc= e 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 rul= es
for subgroups inside one selma'o - then I'd rather see ten selma= 9;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 t= han 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 &= quot;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/lojba= n?hl=3Den.


--
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.
--0015175ce046e3e65e04b1fb14de--