Mime-Version: 1.0 (Apple Message framework v752.2)
In-Reply-To: <20071112024654.5ktfafi2sg0wc080@webmail.ixkey.info>
References: <20071112024654.5ktfafi2sg0wc080@webmail.ixkey.info>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <8BFD8631-3DFB-41D4-9EB0-520F4A9EBB1C@umich.edu>
Content-Transfer-Encoding: 7bit
From: Alex Joseph Martini <alexjm@umich.edu>
Subject: [lojban-beginners] Re: UI2 & UI3
Date: Mon, 12 Nov 2007 11:10:55 -0500
To: lojban-beginners@lojban.org
Sender: lojban-beginners-bounce@lojban.org
Errors-to: lojban-beginners-bounce@lojban.org
Precedence: bulk
Reply-to: lojban-beginners@lojban.org
Content-Length: 995

mungojelly@ixkey.info wrote:
> coi ro do .ui
>
> I just got the clue that the UI2 (pe'i/se'o/etc) and UI3 (mu'a/la'a/ 
> etc) are some sort of UI!  They bind to the thing to their left,  
> then, eh?
>
> .i mi pu viska lo nu ko'a za'a la djan. ti'e tavla
> I saw ko'a talking to someone who I heard was John.
>
> So I can say "ko'a za'a" I observed that it was ko'a and also "la  
> djan. ti'e" I know through hearsay that it was John.  Right?
>
> mi'e bret.

coi bret.

I have to say, while I can understand your example, I'm not sure  
whether it works or no. It certainly parses as you'd think it does.

Usually {za'a} and {ti'e} get attached to the equivalent of English  
clauses. Then the meaning is pretty clear. For example:

	.i za'a ko'a pu tavla la djan.
	I observe that ko'a was talking to John.

	.i ti'e ko'a pu tavla la djan.
	I hear that ko'a was talking to John.

In general, I think the first example is equivalent to {ko'a pu tavla  
za'a la djan.} also.

mu'o mi'e .aleks.