On Sat, Mar 3, 2012 at 11:30 AM, Remo Dentato
<rdentato@gmail.com> wrote:
2012/3/3 Felipe Gonçalves Assis <felipeg.assis@gmail.com>:
> I suggest starting with
>
> 2. mi me la .clalis.
Why not simply {mi'e la .clalis} ?
No second- or third-person equivalent to mi'e exists in Lojban currently.
BTW, {clalis} doesn't have the same sound of the orginal that is (if I
understood correctly) roughly equivalent to the Chinese "Chen Li" I'd
prefer {tcenlis}
Yes, I know. I mentioned as much when I spoke about my reasons for choosing .clalis.
> 3. ta me la .djan.
This seems a good place to assign {ko'a} -> 3. ta goi ko'a me la .djan.
No, a good place to assign ko'a is in panel #2:
![]()
![]()
![]()
![]()
![]()
1. coi
2. mi se cmene zo.clalis.
3. ko'a goi la.djan
4. ko'a se cmene zo.djan.
5. cy: coi.djan.
dy: coi.clalis.
> 4. zo .djan. cmene ta
I would use the lujvo {selme'e} -> 4. ko'a selme'e zo .djan.
This would avoid using {se}, I agree it's too early, the nintandi
would not know about the relationship between {selme'e} and {cmene},
they would just guess it means "is named".
Um, except for the missing "used by namer x3", that IS what {se cmene} means. I don't see the problem.
> Also, I recommend using the ti-series in place of the ko'a-series.
Not sure. I would prefer introducing {ko'a} and friends.
> Using the latter while pointing can cause so much confusion...
>
> In 12 we may do
> 12. lo prenu cu zvati tu
My preference would be {vuku ko'e goi tu zvati}
Using {tu} as zvati2 seems too prone to ambiguity. At least it should
be {lovu} so that it is clear you're talking about "there yonder".
lovu what? gadri (lo) convert selbri into sumti. tense markers apply location and/or time information to a bridi. {lovu} by itself is not a sumti.
remod