Received: from mail-vw0-f61.google.com ([209.85.212.61]:45985)
	by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76)
	(envelope-from <lojban+bncCJzE7b_XFxCn3LD2BBoEiT7oBw@googlegroups.com>)
	id 1RSzdQ-0002qj-HW; Tue, 22 Nov 2011 15:20:22 -0800
Received: by vbbfs19 with SMTP id fs19sf1673778vbb.16
        for <multiple recipients>; Tue, 22 Nov 2011 15:20:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=googlegroups.com; s=beta;
        h=x-beenthere:received-spf:date:from:reply-to:to:message-id
         :in-reply-to:references:subject:mime-version:x-original-sender
         :x-original-authentication-results:precedence:mailing-list:list-id
         :x-google-group-id:list-post:list-help:list-archive:sender
         :list-subscribe:list-unsubscribe:content-type;
        bh=NIHUdo7V5yWjC95KGpUANNUT5JjaGVjninwO8J0Vcks=;
        b=j2KKrnw8LkoOfeqcLQ14fag6ASNemcuWGEf678uTLRX6AHlZ7QZ7D9ty0PyIwbKrRM
         R5kLVfa9UMh1zk5J1GUOpb+rrnDuQXIs0ohBel5KaVi1Lhw7jdKAtlHJMV61kvRFkdmf
         u+EFJOurbvVhWAvGBeVNqD6FpcB5Aqi6IWYrk=
Received: by 10.52.72.199 with SMTP id f7mr10923936vdv.11.1322004007407;
        Tue, 22 Nov 2011 15:20:07 -0800 (PST)
X-BeenThere: lojban@googlegroups.com
Received: by 10.220.149.17 with SMTP id r17ls3331608vcv.0.gmail; Tue, 22 Nov
 2011 15:20:05 -0800 (PST)
Received: by 10.52.67.145 with SMTP id n17mr4929151vdt.0.1322004005809;
        Tue, 22 Nov 2011 15:20:05 -0800 (PST)
Received: by 10.52.67.145 with SMTP id n17mr4929148vdt.0.1322004005796;
        Tue, 22 Nov 2011 15:20:05 -0800 (PST)
Received: from mail-vx0-f189.google.com (mail-vx0-f189.google.com [209.85.220.189])
        by gmr-mx.google.com with ESMTPS id cn4si7335375vdb.3.2011.11.22.15.20.05
        (version=TLSv1/SSLv3 cipher=OTHER);
        Tue, 22 Nov 2011 15:20:05 -0800 (PST)
Received-SPF: pass (google.com: domain of jandew@gmail.com designates 209.85.220.189 as permitted sender) client-ip=209.85.220.189;
Received: by vcbfk1 with SMTP id fk1so4724716vcb.6
        for <lojban@googlegroups.com>; Tue, 22 Nov 2011 15:20:05 -0800 (PST)
Received: by 10.52.94.13 with SMTP id cy13mr11306587vdb.1.1322004005727;
        Tue, 22 Nov 2011 15:20:05 -0800 (PST)
Date: Tue, 22 Nov 2011 15:20:04 -0800 (PST)
From: djandus <jandew@gmail.com>
Reply-To: lojban@googlegroups.com
To: lojban@googlegroups.com
Message-ID: <26790031.186.1322004004975.JavaMail.geo-discussion-forums@yqni5>
In-Reply-To: <CAO7tK2dzL7Ro+gop-n2VQoeczm-vbooko8noLATM=659HCc7tg@mail.gmail.com>
References: <20b482a7-b58a-4e4a-a3f7-27b49ba861c0@p9g2000vbb.googlegroups.com>
 <32855204.975.1321990011505.JavaMail.geo-discussion-forums@yqhd1>
 <CAO7tK2dzL7Ro+gop-n2VQoeczm-vbooko8noLATM=659HCc7tg@mail.gmail.com>
Subject: Re: [lojban] Re: New PA-proposal
MIME-Version: 1.0
X-Original-Sender: jandew@gmail.com
X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com:
 domain of jandew@gmail.com designates 209.85.220.189 as permitted sender) smtp.mail=jandew@gmail.com
Precedence: list
Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com
List-ID: <lojban.googlegroups.com>
X-Google-Group-Id: 1004133512417
List-Post: <http://groups.google.com/group/lojban/post?hl=en_US>, <mailto:lojban@googlegroups.com>
List-Help: <http://groups.google.com/support/?hl=en_US>, <mailto:lojban+help@googlegroups.com>
List-Archive: <http://groups.google.com/group/lojban?hl=en_US>
Sender: lojban@googlegroups.com
List-Subscribe: <http://groups.google.com/group/lojban/subscribe?hl=en_US>, <mailto:lojban+subscribe@googlegroups.com>
List-Unsubscribe: <http://groups.google.com/group/lojban/subscribe?hl=en_US>, <mailto:lojban+unsubscribe@googlegroups.com>
Content-Type: multipart/alternative; 
	boundary="----=_Part_185_11315508.1322004004972"
X-Spam-Score: 0.0 (/)
X-Spam_score: 0.0
X-Spam_score_int: 0
X-Spam_bar: /

------=_Part_185_11315508.1322004004972
Content-Type: text/plain; charset=ISO-8859-1


>
> I consider "ji'i" one of the "preceding modifiers".
>
This system doesn't parse any differently from how you'd expect for {ji'i 
xa pi xa}, as in the linked example you gave, but simply allows for 
constructs like {pa ji'i xa} for "16, with 6 being uncertain" -- clearly 
intended for simplifying significant figures and error analysis. This is 
the behavior I grabbed straight from the cll<http://dag.github.com/cll/18/9/>. 
The "rounded" semantics is implied, but not the "rounded up/down" 
semantics. (Which I'm perfectly fine with.) What I'm not fine with is that 
{ji'i PAI} makes logical sense, and sometimes {ji'i DUhE}, but these are 
currently disallowed since they would put {ji'i} in a separate pagselma'o. 
I wrote a possible work-around in the google doc definition, but I don't 
particularly like it. Given, it's basically the same sort of thing I did 
with {pi DUhE}...

I've been trying to match the current system as much as possible, primarily 
disliking {ce'i}. I didn't know there were previous thread expressing 
dislike with {ji'i} -- personally, I'd like to see both interpretations 
able to coexist.

mu'o mi'e djos

>

-- 
You received this message because you are subscribed to the Google Groups "lojban" group.
To view this discussion on the web visit https://groups.google.com/d/msg/lojban/-/fpHm60qXuFEJ.
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.


------=_Part_185_11315508.1322004004972
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<blockquote class=3D"gmail_quote" style=3D"margin: 0;margin-left: 0.8ex;bor=
der-left: 1px #ccc solid;padding-left: 1ex;"><p>I consider "ji'i" one of th=
e "preceding modifiers".</p></blockquote><div>This system doesn't parse any=
 differently from how you'd expect for {ji'i xa pi xa}, as in the linked ex=
ample you gave, but simply allows for constructs like {pa ji'i xa} for "16,=
 with 6 being uncertain" -- clearly intended for simplifying significant fi=
gures and error analysis. This is the behavior I grabbed <a href=3D"http://=
dag.github.com/cll/18/9/">straight from the cll</a>. The "rounded" semantic=
s is implied, but not the "rounded up/down" semantics. (Which I'm perfectly=
 fine with.) What I'm not fine with is that {ji'i PAI} makes logical sense,=
 and sometimes {ji'i DUhE}, but these are currently disallowed since they w=
ould put {ji'i} in a separate pagselma'o. I wrote a possible work-around in=
 the google doc definition, but I don't particularly like it. Given, it's b=
asically the same sort of thing I did with {pi DUhE}...</div><div><br></div=
><div>I've been trying to match the current system as much as possible, pri=
marily disliking {ce'i}. I didn't know there were previous thread expressin=
g dislike with {ji'i} -- personally, I'd like to see both interpretations a=
ble to coexist.</div><div><br></div><div>mu'o mi'e djos</div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin: 0;margin-left: 0.8ex;border-left: 1px =
#ccc solid;padding-left: 1ex;"><p></p><p></p><p></p></blockquote>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups "=
lojban" group.<br />
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/d/msg/lojban/-/fpHm60qXuFEJ">https://groups.google.com/d/msg/lojban/-/fp=
Hm60qXuFEJ</a>.<br />=20
To post to this group, send email to lojban@googlegroups.com.<br />
To unsubscribe from this group, send email to lojban+unsubscribe@googlegrou=
ps.com.<br />

For more options, visit this group at http://groups.google.com/group/lojban=
?hl=3Den.<br />



------=_Part_185_11315508.1322004004972--