From jjllambias2000@yahoo.com.ar Fri May 07 14:13:20 2004
Received: with ECARTIS (v1.0.0; list lojban-list); Fri, 07 May 2004 14:13:20 -0700 (PDT)
Received: from web41901.mail.yahoo.com ([66.218.93.152])
	by chain.digitalkingdom.org with smtp (Exim 4.31)
	id 1BMCeg-0000hD-3j
	for lojban-list@lojban.org; Fri, 07 May 2004 14:13:14 -0700
Message-ID: <20040507211243.95368.qmail@web41901.mail.yahoo.com>
Received: from [200.49.74.2] by web41901.mail.yahoo.com via HTTP; Fri, 07 May 2004 14:12:43 PDT
Date: Fri, 7 May 2004 14:12:43 -0700 (PDT)
From: Jorge "Llambías" <jjllambias2000@yahoo.com.ar>
Subject: [lojban] Re: My parser, SI, SA, and ZOI
To: lojban-list@lojban.org
In-Reply-To: <20040507204725.GB27947@digitalkingdom.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-archive-position: 7693
X-ecartis-version: Ecartis v1.0.0
Sender: lojban-list-bounce@lojban.org
Errors-to: lojban-list-bounce@lojban.org
X-original-sender: jjllambias2000@yahoo.com.ar
Precedence: bulk
Reply-to: lojban-list@lojban.org
X-list: lojban-list


--- Robin Lee Powell <rlpowell@digitalkingdom.org> wrote:
> > I think that the Right Thing is to treat {zo <word>} and {zoi <word>
> > <anything> <word>} as single tokens of selmaho KOhA.
> 
> Why KOhA?

What else? They behave as KOhAs in all other respects. This would
only affect their behaviour vis-a-vis {si}, {bu} and {zei}.
(Also {ba'e}, but the effect here is almost irrelevant.)

{zo zo}, {zo zoi}, {zoi zoi ... zoi} and {zoi zo ... zo} would 
remain valid because they act first. 

mu'o mi'e xorxes




	
		
__________________________________
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs  
http://hotjobs.sweepstakes.yahoo.com/careermakeover