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

[bpfk] Re: {.i} and {ni'o}, continuation or new jufra



Umm... Doesn't {di'ai} already mean "Wellwish - Curse"?

On Oct 12, 2:49 pm, Jorge Llambías <jjllamb...@gmail.com> wrote:
> On Tue, Oct 12, 2010 at 2:20 PM, Adam Lopresto <adamlopre...@gmail.com> wrote:
> > "conversation" is the new top-level rule in the parser. it gracefully
> > degrades to just a single text.
> > So given an exchange in IRC
> > A: do klama ma
> > B: lo zarci
> > We can either parse each line completely independently, or we can make our
> > logs in a parseable format thus:
> > A: fa'ai do klama ma fa'o
> > B: fa'ai lo zarci fa'o
>
> > That entire block is a single lojban conversation, and can be parsed.
>
> So the conversation generator gets a sequence of "text"s as input and
> outputs one "conversation", right? All it does is surround each text
> with fa'ai/fa'o (when they are not already present, I suppose) and
> then outputs their concatenation. That seems simple enough.
>
> The problem I see is that we must already have the string of texts to
> feed the conversationer. You can't feed it the string of phonemes "do
> klama ma lo zarci" and expect it to split it into two texts, you must
> feed it first chunk "do klama ma", second chunk "lo zarci". In other
> words, the hard work will be done somewhere else, not by the
> conversationer.
>
> mu'o mi'e xorxes

-- 
You received this message because you are subscribed to the Google Groups "BPFK" group.
To post to this group, send email to bpfk-list@googlegroups.com.
To unsubscribe from this group, send email to bpfk-list+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/bpfk-list?hl=en.