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

Re: [lojban] lujvo deconstruction



I wrote up my own low-level understanding of the {lujvo}-splitting algorithm a
while ago; it should conform perfectly to the CLL (with errata), i.e., it
doesn't handle superfluous hyphens.  You can read it at
<http://github.com/jwodder/jbobaf/blob/master/share/tadji/jvokatna.txt>; it
shouldn't be too hard to convert into a program.

de'i li 29 pi'e 10 pi'e 2010 la'o fy. Luke Bergen .fy. cusku zoi skamyxatra.
> Wait, what are syllabic consonants?
.skamyxatra

A lone consonant that is pronounced as a syllable (roughly, a consonant
followed by a schwa [ə]).  In Lojban, 'l', 'm', 'n', and 'r' can all be
pronounced syllabically or non-syllabically.

> So, if I'm trying to parse out a lujvo into its component rafsi, should I
> not worry when I see "m" or "l"?  There's no way that they could be anything
> but part of a rafsi?

Correct.

> Further, what is this about hyphen-letters only being allowed after the
> first rafsi?  I can understand why the rafsi before an r/n-hyphen would need
> to be CVV or CV'V, but why can't r/n-hyphen come after the second or third
> rafsi?

Allowing them after non-initial {rafsi} would not cause any problems (except
for converting some {fu'ivla} forms into {lujvo}), but the CLL does not
currently allow this (though some, e.g., xorxes, would like to change that).

mu'omi'e .kamymecraijun.

-- 
ko senpi lo du'u do bilga lonu senpi

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