[YG Conlang Archives] > [jboske group] > messages [Date Index] [Thread Index] >


[Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: [lojban] Re: nai in UI (was: BPFK phpbb)



la djorden cusku di'e

> > They seem analogous to me:
> > 
> > simple-tense-modal = [NAhE] [SE] BAI [NAI] [KI]
> >                    | [NAhE] (time [space]| space [time]) & CAhA [KI]
> >                    | KI
> >                    | CUhE 
> > 
> > PU is the nucleus of 'time' and FAhA of 'space'. So BAI, PU, FAhA,
> > CAhA, KI, CUhE and others can all function as simple-tense-modal,
> [...]
> 
> Err, but if you look at that rule there, they aren't analagous.

analogous
adj 1: similar or correspondent in some respects though otherwise dissimilar

They don't have to have identical grammar to be analogous. If they did,
we wouldn't be having this discussion.

> You can't say mi ne'i ka'e pu ca'a klama. 

Well, you can, but it breaks as {mi ne'iku ka'eku pu ca'a klama}.
But the point is that there is no founded reason for the restriction.

> Any given tense ends
> with the modal aspect (or the ki) and you need to join them with a
> connective like je.

Right, that's the rule. An unnecessarily arbitrary rule.

> This makes perfect sense if you think about it.

I think about it and it makes no sense to me. What is so senseless
about {pu bai klama}?

> I think you mentioned {mi pu na'eka'e broda}.  This doesn't make
> sense either, since either the whole tense should be negated or
> not. 

It makes perfect sense: impossible in the past. This is different
from possible in the non-past.

> That sentence could either mean {puku mi na'eka'e broda} or
> {mi na'e pu ka'e broda}. 

I don't see how you can get the second meaning from it.

> It could've been allowed if one of those
> meanings were required, I suppose, but it's not obvious which it
> should be, and so I don't see what allowing it gets you (I suppose
> that you could argue that if it has the puku meaning it saves you
> a syllable, though).

No, it is not a matter of saving syllables. It is a question of not 
forbidding sensible strings just for the sake of forbidding them.

> (And I think robin's wrong that this is required for LALR(1)).

In which case the restriction is pointless.

(I'm sending this to jboske and also a copy to you Jordan as I'm
not sure you are reading jboske, sorry if you get it twice.)

mu'o mi'e xorxes



__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com