[lojban] CLL help: jbovlaste words, round 2

[Robin Lee Powell <rlpowell@digitalkingdom.org>]

So here's the list again, but this time they should mostly be actual
words we care about.

Please enter these all into jbovlaste!  It would really help!

I've included context so that people can evaluate which words should
*not* go in the golssary.

For lujvo synonyms, I'm just having the book ignore everything but
whatever form people put into jbovlaste, so just let me know which
ones I should ignore.

Ideally in a future version we'd have "see also blah" or whatever,
but I can't be bothered for this run; someone else is welcome to set
that up.

*********************************************************************** bisycla
chapters/04.xml-    <jbophrase>da'amei</jbophrase> must be a compound cmavo because it lacks a consonant pair;
chapters/04.xml-    <valsi>lojban.</valsi> must be a name because it lacks a final vowel.</para>
chapters/04.xml-    <para> <indexterm type="general"><primary>consonant pairs</primary><secondary>letter y within</secondary></indexterm>  <indexterm type="general"><primary>y</primary><secondary>letter</secondary><tertiary>between letters of consonant pair</tertiary></indexterm>  <indexterm type="general"><primary>consonant pairs</primary><secondary>in brivla</secondary></indexterm>  <indexterm type="general"><primary>brivla</primary><secondary>consonant pairs in</secondary></indexterm> Thus,
chapters/04.xml:    <valsi>bisycla</valsi> has the consonant pair
chapters/04.xml-    <morphology>sc</morphology> in the first five non-
chapters/04.xml-    <letteral>y</letteral> letters even though the
chapters/04.xml-    <morphology>sc</morphology> actually appears in the form of
*********************************************************************** blolei
chapters/04.xml-      <member><valsi>lo'ikle</valsi></member>
chapters/04.xml-
chapters/04.xml-      <member><valsi>lotlei</valsi></member>
chapters/04.xml:      <member><valsi>blolei</valsi></member>
chapters/04.xml-      <member><valsi>lo'irlei</valsi></member>
chapters/04.xml-    </simplelist>
chapters/04.xml-    <para>Only
--
chapters/04.xml-            <td>5867</td>
chapters/04.xml-          </tr>
chapters/04.xml-          <tr>
chapters/04.xml:            <td><valsi>blolei</valsi></td>
chapters/04.xml-            <td>5847</td>
chapters/04.xml-          </tr>
chapters/04.xml-          <tr>
--
chapters/04.xml-<indexterm type="general"><primary>Logical Language Group</primary><secondary>example</secondary></indexterm>
chapters/04.xml-
chapters/04.xml- So the form
chapters/04.xml:    <valsi>blolei</valsi> is preferred, but only by a tiny margin over
chapters/04.xml-    <valsi>blokle</valsi>; "lotlei" and "lotkle" are only slightly worse;
chapters/04.xml-    <valsi>lo'ikle</valsi> suffers because of its apostrophe, and
chapters/04.xml-    <valsi>lo'irlei</valsi> because of having both apostrophe and hyphen.</para>
*********************************************************************** calkyguzme
chapters/05.xml-            <td>piece of cloth</td>
chapters/05.xml-          </tr>
chapters/05.xml-          <tr>
chapters/05.xml:            <td><jbophrase>djacu calkyguzme</jbophrase></td>
chapters/05.xml-            <td>water calabash</td>
chapters/05.xml-            <td>Ewe</td>
chapters/05.xml-            <td>calabash of water</td>
--
chapters/05.xml-    </informaltable>
chapters/05.xml-    <variablelist>
chapters/05.xml-      <varlistentry>
chapters/05.xml:        <term><valsi>calkyguzme</valsi></term>
chapters/05.xml-        <listitem><para>shell-fruit, calabash</para></listitem>
chapters/05.xml-      </varlistentry>
chapters/05.xml-    </variablelist>
*********************************************************************** cinctu
chapters/04.xml-    <quote>teacher of male sexuality</quote>. Here are the possible forms of the lujvo, both before and after hyphenation:</para>
chapters/04.xml-    <simplelist type="horiz" columns="2">
chapters/04.xml-      <member><rafsi>nak</rafsi><rafsi>-kem</rafsi><rafsi>-cin</rafsi><rafsi>-ctu</rafsi></member>
chapters/04.xml:      <member><valsi>nakykemcinctu</valsi></member>
chapters/04.xml-
chapters/04.xml-      <member><rafsi>nak</rafsi><rafsi>-kem</rafsi><rafsi>-cin</rafsi><rafsi>-ctuca</rafsi></member>
chapters/04.xml:      <member><valsi valid="false">nakykemcinctuca</valsi></member>
chapters/04.xml-
chapters/04.xml-      <member><rafsi>nak</rafsi><rafsi>-kem</rafsi><rafsi>-cins</rafsi><rafsi>-ctu</rafsi></member>
chapters/04.xml-      <member><valsi valid="false">nakykemcinsyctu</valsi></member>
--
chapters/04.xml-      <member><valsi valid="false">nakykemcinsyctuca</valsi></member>
chapters/04.xml-
chapters/04.xml-      <member><rafsi>nakn</rafsi><rafsi>-kem</rafsi><rafsi>-cin</rafsi><rafsi>-ctu</rafsi></member>
chapters/04.xml:      <member><valsi valid="false">naknykemcinctu</valsi></member>
chapters/04.xml-
chapters/04.xml-      <member><rafsi>nakn</rafsi><rafsi>-kem</rafsi><rafsi>-cin</rafsi><rafsi>-ctuca</rafsi></member>
chapters/04.xml:      <member><valsi valid="false">naknykemcinctuca</valsi></member>
chapters/04.xml-
chapters/04.xml-      <member><rafsi>nakn</rafsi><rafsi>-kem</rafsi><rafsi>-cins</rafsi><rafsi>-ctu</rafsi></member>
chapters/04.xml-      <member><valsi valid="false">naknykemcinsyctu</valsi></member>
--
chapters/04.xml-      <member><valsi valid="false">naknykemcinsyctuca</valsi></member>
chapters/04.xml-    </simplelist>
chapters/04.xml-    <para> <indexterm type="general"><primary>gismu</primary><secondary>algorithm for</secondary></indexterm> Of these forms,
chapters/04.xml:    <valsi>nakykemcinctu</valsi> is the shortest and is preferred by the scoring algorithm. On the whole, however, it might be better to just make a lujvo for
chapters/04.xml-    <jbophrase>cinse ctuca</jbophrase> (which would be
chapters/04.xml:    <valsi>cinctu</valsi>) since the sex of the teacher is rarely important. If there was a reason to specify
chapters/04.xml-    <quote>male</quote>, then the simpler tanru
chapters/04.xml:    <jbophrase>nakni cinctu</jbophrase> (
chapters/04.xml-    <quote>male sexual-teacher</quote>) would be appropriate. This tanru is actually shorter than the four-part lujvo, since the
chapters/04.xml-    <valsi>ke</valsi> required for grouping need not be expressed.</para>
chapters/04.xml-  </section>
*********************************************************************** cmacrnintegrale
chapters/04.xml-    <valsi>cmacrntegrale</valsi>, if the
chapters/04.xml-    <letteral>i</letteral> of
chapters/04.xml-    <valsi>integrale</valsi> is removed, or something like
chapters/04.xml:    <valsi>cmacrnintegrale</valsi>, if a new consonant is added to the beginning;
chapters/04.xml-    <rafsi>cmac-</rafsi> is the rafsi for
chapters/04.xml-    <valsi>cmaci</valsi> (
chapters/04.xml-    <quote>mathematics</quote>). The architectural sense of
*********************************************************************** cmacrntegrale
chapters/04.xml-<indexterm type="general"><primary>integral</primary><secondary>architectural concept</secondary><tertiary>example</tertiary></indexterm>  <indexterm type="general"><primary>integral</primary><secondary>mathematical concept</secondary><tertiary>example</tertiary></indexterm>
chapters/04.xml-
chapters/04.xml-The prefix method would render the mathematical concept as
chapters/04.xml:    <valsi>cmacrntegrale</valsi>, if the
chapters/04.xml-    <letteral>i</letteral> of
chapters/04.xml-    <valsi>integrale</valsi> is removed, or something like
chapters/04.xml-    <valsi>cmacrnintegrale</valsi>, if a new consonant is added to the beginning;
*********************************************************************** djinrnintegrale
chapters/04.xml-    <quote>mathematics</quote>). The architectural sense of
chapters/04.xml-    <quote>integral</quote> might be conveyed with
chapters/04.xml-
chapters/04.xml:    <valsi>djinrnintegrale</valsi> or
chapters/04.xml-    <valsi>tarmrnintegrale</valsi>, where
chapters/04.xml-    <valsi>dinju</valsi> and
chapters/04.xml-    <valsi>tarmi</valsi> mean
*********************************************************************** donta'a
chapters/07.xml-<indexterm type="general"><primary>you-talk</primary><secondary>example</secondary></indexterm>
chapters/07.xml-
chapters/07.xml-  <indexterm type="general"><primary>pro-sumti rafsi</primary><secondary>effect of on place structure of lujvo</secondary></indexterm>  <indexterm type="general"><primary>lujvo</primary><secondary>pro-sumti rafsi effect on place structure of</secondary></indexterm> Thus
chapters/07.xml:    <valsi>donta'a</valsi>, meaning
chapters/07.xml-    <quote>you-talk</quote>, would be interpreted as
chapters/07.xml-    <jbophrase>tavla be do</jbophrase>, and would have the place structure</para>
chapters/07.xml-
*********************************************************************** fetsygau
chapters/12.xml-    <valsi>galfi</valsi> (meaning
chapters/12.xml-    <quote>modify</quote>) may be more appropriate for
chapters/12.xml-    <quote>causes to become a liquid</quote>. On the other hand,
chapters/12.xml:    <valsi>fetsygau</valsi> is potentially confusing, because it could mean
chapters/12.xml-    <quote>agent in the event of something becoming female</quote> (the implicit-abstraction interpretation) or simply
chapters/12.xml-    <quote>female agent</quote> (the parallel interpretation), so using implicit-abstraction lujvo is always accompanied with some risk of being misunderstood.</para>
chapters/12.xml-
*********************************************************************** ge'urzdani
chapters/04.xml-    <valsi valid="false">ge'u-zdani</valsi>, however, requires an
chapters/04.xml-    r-hyphen; otherwise, the
chapters/04.xml-    <rafsi>ge'u-</rafsi> part would fall off as a cmavo. So this form of the lujvo is
chapters/04.xml:    <valsi>ge'urzdani</valsi>.</para>
chapters/04.xml-    <para>The last two forms require
chapters/04.xml-    y-hyphens, as all 4-letter rafsi do, and so are
chapters/04.xml-
*********************************************************************** ge'uzda
chapters/04.xml-    <valsi>gerzdani</valsi>.</para>
chapters/04.xml-    <para>The third form,
chapters/04.xml-    <rafsi>ge'u</rafsi><rafsi>-zda</rafsi>, needs no hyphen, because even though the first rafsi is CVV, the second one is CCV, so there is a consonant cluster in the first five letters. So
chapters/04.xml:    <valsi>ge'uzda</valsi> is this form of the lujvo.</para>
chapters/04.xml-    <para>The fourth form,
chapters/04.xml-    <valsi valid="false">ge'u-zdani</valsi>, however, requires an
chapters/04.xml-    r-hyphen; otherwise, the
*********************************************************************** gekmau
chapters/12.xml-    <quote>other than a big boat</quote>.</para>
chapters/12.xml-
chapters/12.xml-    <para> <indexterm type="general"><primary>lujvo creation</primary><secondary>use of multiple SE in</secondary></indexterm> If the lujvo we want to modify with SE has a seltau already starting with a SE rafsi, we can take a shortcut. For instance,
chapters/12.xml:    <valsi>gekmau</valsi> means
chapters/12.xml-    <quote>happier than</quote>, while
chapters/12.xml:    <valsi>selgekmau</valsi> means
chapters/12.xml-    <quote>making people happier than, more enjoyable than, more of a 'se gleki' than</quote>. If something is less enjoyable than something else, we can say it is
chapters/12.xml:    <jbophrase>se selgekmau</jbophrase>.</para>
chapters/12.xml-    <para>But we can also say it is
chapters/12.xml:    <valsi>selselgekmau</valsi>. Two
chapters/12.xml-    <valsi>se</valsi> cmavo in a row cancel each other (
chapters/12.xml-    <jbophrase>se se gleki</jbophrase> means the same as just
chapters/12.xml-    <valsi>gleki</valsi>), so there would be no good reason to have
*********************************************************************** gerkyzda
chapters/04.xml-    <para>The last two forms require
chapters/04.xml-    y-hyphens, as all 4-letter rafsi do, and so are
chapters/04.xml-
chapters/04.xml:    <valsi>gerkyzda</valsi> and
chapters/04.xml:    <valsi>gerkyzdani</valsi> respectively.</para>
chapters/04.xml-    <para>
chapters/04.xml-
chapters/04.xml-<indexterm type="general"><primary>boat class</primary><secondary>example</secondary></indexterm>
*********************************************************************** gerkyzdani
chapters/04.xml-    y-hyphens, as all 4-letter rafsi do, and so are
chapters/04.xml-
chapters/04.xml-    <valsi>gerkyzda</valsi> and
chapters/04.xml:    <valsi>gerkyzdani</valsi> respectively.</para>
chapters/04.xml-    <para>
chapters/04.xml-
chapters/04.xml-<indexterm type="general"><primary>boat class</primary><secondary>example</secondary></indexterm>
*********************************************************************** gerselzda
chapters/12.xml-      <para><definition><content>s1 is housed by nest s2</content></definition></para>
chapters/12.xml-    </example>
chapters/12.xml-    <para role="noindent">and so the three-part lujvo
chapters/12.xml:    <valsi>gerselzda</valsi> would have the place structure</para>
chapters/12.xml-    <example xml:id="example-random-id-KqE4">
chapters/12.xml-      <title>
chapters/12.xml-        <anchor xml:id="c12e5d6"/>
--
chapters/12.xml-      <para><definition><content>s1=g1 is a dog housed in nest s2 of dog breed g2</content></definition></para>
chapters/12.xml-    </example>
chapters/12.xml-    <para role="indent">However, although
chapters/12.xml:    <valsi>gerselzda</valsi> is a valid lujvo, it doesn't translate
chapters/12.xml-    <quote>doghouse</quote>; its first place is the dog, not the doghouse. Furthermore, it is more complicated than necessary;
chapters/12.xml-    <valsi>gerzda</valsi> is simpler than
chapters/12.xml:    <valsi>gerselzda</valsi>.</para>
chapters/12.xml-    <para>From the reader's or listener's point of view, it may not always be obvious whether a newly met lujvo is symmetrical or asymmetrical, and if the latter, what kind of asymmetrical lujvo. If the place structure of the lujvo isn't given in a dictionary or elsewhere, then plausibility must be applied, just as in interpreting tanru.</para>
chapters/12.xml-
chapters/12.xml-    <para>
*********************************************************************** gerzdani
chapters/04.xml-    <valsi>ge</valsi> cannot fall off the front, because the following word would begin with
chapters/04.xml-    <morphology>rz</morphology>, which is not a permissible initial consonant pair. So the lujvo forms are
chapters/04.xml-    <valsi>gerzda</valsi> and
chapters/04.xml:    <valsi>gerzdani</valsi>.</para>
chapters/04.xml-    <para>The third form,
chapters/04.xml-    <rafsi>ge'u</rafsi><rafsi>-zda</rafsi>, needs no hyphen, because even though the first rafsi is CVV, the second one is CCV, so there is a consonant cluster in the first five letters. So
chapters/04.xml-    <valsi>ge'uzda</valsi> is this form of the lujvo.</para>
*********************************************************************** gicmu
chapters/04.xml-    <valsi>gismu</valsi> is in the set of gismu,
chapters/04.xml-    <valsi valid="false">kismu</valsi>,
chapters/04.xml-    <valsi valid="false">xismu</valsi>,
chapters/04.xml:    <valsi valid="false">gicmu</valsi>,
chapters/04.xml-    <valsi valid="false">gizmu</valsi>, and
chapters/04.xml-    <valsi valid="false">gisnu</valsi> cannot be.</para>
chapters/04.xml-    <para> <indexterm type="general"><primary>gismu</primary><secondary>source of</secondary></indexterm> Almost all Lojban gismu are constructed from pieces of words drawn from other languages, specifically Chinese, English, Hindi, Spanish, Russian, and Arabic, the six most widely spoken natural languages. For a given concept, words in the six languages that represent that concept were written in Lojban phonetics. Then a gismu was selected to maximize the recognizability of the Lojban word for speakers of the six languages by weighting the inclusion of the sounds drawn from each language by the number of speakers of that language. See
--
chapters/04.xml-      <listitem>
chapters/04.xml-        <para>The gismu form with the highest score usually became the actual gismu. Sometimes a lower-scoring form was used to provide a better rafsi. A few gismu were changed in error as a result of transcription blunders (for example, the gismu
chapters/04.xml-        <valsi>gismu</valsi> should have been
chapters/04.xml:        <valsi>gicmu</valsi>, but it's too late to fix it now).</para>
chapters/04.xml-        <para>The language weights used to make most of the gismu were as follows:</para>
chapters/04.xml-        <informaltable>
chapters/04.xml-              <tr>
*********************************************************************** gripau
chapters/18.xml-        <listitem><definition><content>x1 is a member of set x2</content></definition></listitem>
chapters/18.xml-      </varlistentry>
chapters/18.xml-      <varlistentry>
chapters/18.xml:        <term><valsi>gripau</valsi></term>
chapters/18.xml-        <listitem><definition><content>x1 is a subset of set x2 [<valsi>girzu</valsi> <valsi>pagbu</valsi>, set-part]</content></definition></listitem>
chapters/18.xml-      </varlistentry>
chapters/18.xml-      <varlistentry>
*********************************************************************** grutrceraso
chapters/05.xml-    <para> <indexterm type="general"><primary>asymmetrical tanru types</primary><secondary>similar-appearance-object + object</secondary></indexterm> As a particular case (when the property is that of resemblance): the seltau specifies an object which the referent of the tanru resembles.</para>
chapters/05.xml-    <informaltable>
chapters/05.xml-          <tr>
chapters/05.xml:            <td><jbophrase>grutrceraso jbama</jbophrase></td>
chapters/05.xml-            <td>cherry bomb</td>
chapters/05.xml-          </tr>
chapters/05.xml-          <tr>
--
chapters/05.xml-    </informaltable>
chapters/05.xml-    <variablelist>
chapters/05.xml-      <varlistentry>
chapters/05.xml:        <term><valsi>grutrceraso</valsi></term>
chapters/05.xml-        <listitem><para>fu'ivla for <quote>cherry</quote> based on Linnean name</para></listitem>
chapters/05.xml-      </varlistentry>
chapters/05.xml-    </variablelist>
*********************************************************************** integrale
chapters/04.xml-    <para> <indexterm type="general"><primary>fu'ivla categorizer</primary><secondary>for distinguishing specialized meanings</secondary></indexterm> For another example,
chapters/04.xml-    <quote>integral</quote> has a specific meaning to a mathematician. But the Lojban fu'ivla
chapters/04.xml-
chapters/04.xml:    <valsi>integrale</valsi>, which is a valid Stage 4 fu'ivla, does not convey that mathematical sense to a non-mathematical listener, even one with an English-speaking background; its source &ndash; the English word
chapters/04.xml-    <quote>integral</quote> &ndash; has various other specialized meanings in other fields.</para>
chapters/04.xml-
chapters/04.xml-    <para>Left uncontrolled,
chapters/04.xml:    <valsi>integrale</valsi> almost certainly would eventually come to mean the same collection of loosely related concepts that English associates with
chapters/04.xml-    <quote>integral</quote>, with only the context to indicate (possibly) that the mathematical term is meant.</para>
chapters/04.xml-
chapters/04.xml-    <para>
--
chapters/04.xml-The prefix method would render the mathematical concept as
chapters/04.xml-    <valsi>cmacrntegrale</valsi>, if the
chapters/04.xml-    <letteral>i</letteral> of
chapters/04.xml:    <valsi>integrale</valsi> is removed, or something like
chapters/04.xml:    <valsi>cmacrnintegrale</valsi>, if a new consonant is added to the beginning;
chapters/04.xml-    <rafsi>cmac-</rafsi> is the rafsi for
chapters/04.xml-    <valsi>cmaci</valsi> (
chapters/04.xml-    <quote>mathematics</quote>). The architectural sense of
chapters/04.xml-    <quote>integral</quote> might be conveyed with
chapters/04.xml-
chapters/04.xml:    <valsi>djinrnintegrale</valsi> or
chapters/04.xml:    <valsi>tarmrnintegrale</valsi>, where
chapters/04.xml-    <valsi>dinju</valsi> and
chapters/04.xml-    <valsi>tarmi</valsi> mean
chapters/04.xml-    <quote>building</quote> and
*********************************************************************** kambla
chapters/12.xml-    <rafsi>kam-</rafsi> lujvo (
chapters/12.xml-    <rafsi>kam-</rafsi> is the rafsi for
chapters/12.xml-    <valsi>ka</valsi>);
chapters/12.xml:    <valsi>kambla</valsi> is
chapters/12.xml-    <quote>blueness</quote>.</para>
chapters/12.xml-    <para>Even though the cmavo of NU are long-scope in nature, governing the whole following bridi, the NU rafsi should generally be used as short-scope modifiers, like the SE and NAhE rafsi discussed in
chapters/12.xml-    <xref linkend="section-seltau-SE"/>.</para>
*********************************************************************** karcykla
chapters/12.xml-
chapters/12.xml-
chapters/12.xml- The lujvo
chapters/12.xml:    <valsi>karcykla</valsi>, for example, is based on
chapters/12.xml-    <jbophrase>karce klama</jbophrase>, or
chapters/12.xml-    <quote>car goer</quote>. The place structure of
chapters/12.xml-
--
chapters/12.xml-      <para>karce: ka1 is a car carrying ka2 propelled by ka3</para>
chapters/12.xml-    </example>
chapters/12.xml-    <para role="indent">A asymmetrical interpretation of
chapters/12.xml:    <valsi>karcykla</valsi> that is strictly analogous to the place structure of
chapters/12.xml-    <valsi>gerzda</valsi>, equating the kl2 (destination) and ka1 (car) places, would lead to the place structure</para>
chapters/12.xml-    <example xml:id="example-random-id-GgxL">
chapters/12.xml-      <title>
*********************************************************************** klamau
chapters/12.xml-    <valsi>nelcymau</valsi> mean
chapters/12.xml-    <quote>X likes Y more than X likes Z</quote>, or
chapters/12.xml-    <quote>X likes Y more than Z likes Y</quote>? Does
chapters/12.xml:    <valsi>klamau</valsi> mean:
chapters/12.xml-    <quote>X goes to Y more than to Z</quote>,
chapters/12.xml-    <quote>X goes to Y more than Z does</quote>,
chapters/12.xml-    <quote>X goes to Y from Z more than from W</quote>, or what?</para>
--
chapters/12.xml-      <para>
chapters/12.xml-      <valsi>selnelcymau</valsi>: z1, more than z2, is liked by n1 in amount z4</para>
chapters/12.xml-      <para>
chapters/12.xml:      <valsi>klamau</valsi>: z1, more than z2, goes to k2 from k3 via k4 by means of k5</para>
chapters/12.xml-      <para>
chapters/12.xml:      <valsi>selklamau</valsi>: z1, more than z2, is gone to by k1 from k3 via k4 by means of k5</para>
chapters/12.xml-      <para>
chapters/12.xml:      <valsi>terklamau</valsi>: z1, more than z2, is an origin point from destination k2 for k1's going via k4 by means of k5</para>
chapters/12.xml-    </example>
chapters/12.xml-    <para role="noindent">(See
chapters/12.xml-    <xref linkend="chapter-abstractions"/> for the way in which this problem is resolved when lujvo aren't used.)</para>
chapters/12.xml-    <para>The ordering rule places the things being compared first, and the other seltau places following. Unfortunately the z4 place, which expresses by how much one entity exceeds the other, is displaced into a lujvo place whose number is different for each lujvo. For example, while
chapters/12.xml-    <valsi>nelcymau</valsi> has z4 as its fourth place,
chapters/12.xml:    <valsi>klamau</valsi> has it as its sixth place. In any sentence where a difficulty arises, this amount-place can be redundantly tagged with
chapters/12.xml-    <valsi>vemau</valsi> (for
chapters/12.xml-    <valsi>zmadu</valsi>) or
chapters/12.xml-    <valsi>veme'a</valsi> (for
*********************************************************************** labmau
chapters/04.xml-
chapters/04.xml-    <quote>-er</quote> such as
chapters/04.xml-    <quote>whiter</quote> (Lojban
chapters/04.xml:    <valsi>labmau</valsi>). On the other hand,
chapters/04.xml-    <valsi>bakri</valsi> (
chapters/04.xml-    <quote>chalk</quote>) has no short rafsi and few lujvo.</para>
chapters/04.xml-    <para>There are at most one CVC-form, one CCV-form, and one CVV-form rafsi per gismu. In fact, only a tiny handful of gismu have both a CCV-form and a CVV-form rafsi assigned, and still fewer have all three forms of short rafsi. However, gismu with both a CVC-form and another short rafsi are fairly common, partly because more possible CVC-form rafsi exist. Yet CVC-form rafsi, even though they are fairly easy to remember, cannot be used at the end of a lujvo (because lujvo must end in vowels), so justifying the assignment of an additional short rafsi to many gismu.</para>
*********************************************************************** lamgri
chapters/05.xml-            <td>house row</td>
chapters/05.xml-          </tr>
chapters/05.xml-          <tr>
chapters/05.xml:            <td><jbophrase>selci lamgri</jbophrase></td>
chapters/05.xml-            <td>cell block</td>
chapters/05.xml-          </tr>
chapters/05.xml-          <tr>
--
chapters/05.xml-        <listitem><para>line-group</para></listitem>
chapters/05.xml-      </varlistentry>
chapters/05.xml-      <varlistentry>
chapters/05.xml:        <term><valsi>lamgri</valsi></term>
chapters/05.xml-        <listitem><para>adjacent-group</para></listitem>
chapters/05.xml-      </varlistentry>
chapters/05.xml-      <varlistentry>
*********************************************************************** lange'u
chapters/12.xml-    <para>Another example of this kind of anomalous lujvo, drawn from the tanru lists in
chapters/12.xml-
chapters/12.xml-    <xref linkend="section-asymmetric-tanru"/>, is
chapters/12.xml:    <valsi>lange'u</valsi>, meaning
chapters/12.xml-    <quote>sheepdog</quote>. Clearly a sheepdog is not a dog which is a sheep (the symmetrical interpretation is wrong), nor a dog of the sheep breed (the asymmetrical interpretation is wrong). Indeed, there is simply no overlap in the places of
chapters/12.xml-
chapters/12.xml-
--
chapters/12.xml-    <valsi>lantro</valsi> (sheep-controller) and
chapters/12.xml-    <valsi>gerku</valsi>, but
chapters/12.xml-    <valsi>lantro</valsi> is itself an asymmetrical lujvo. The l2 place, the breed of sheep, is removed as dependent on l1. However, the lujvo
chapters/12.xml:    <valsi>lange'u</valsi> is both shorter than
chapters/12.xml-    <valsi>terlantroge'u</valsi> and sufficiently clear to warrant its use: its place structure, however, should be the same as that of the longer lujvo, for which
chapters/12.xml:    <valsi>lange'u</valsi> can be understood as an abbreviation.</para>
chapters/12.xml-    <para>Another example is
chapters/12.xml-    <valsi>xanmi'e</valsi>,
chapters/12.xml-    <quote>to command by hand, to beckon</quote>. The component place structures are:</para>
*********************************************************************** lantro
chapters/12.xml-    <valsi>lanme</valsi> and
chapters/12.xml-    <valsi>gerku</valsi> at all. Rather, the lujvo refers to a dog which controls sheep flocks, a
chapters/12.xml-    <jbophrase>terlanme jitro gerku</jbophrase>, the lujvo from which is
chapters/12.xml:    <valsi>terlantroge'u</valsi> with place structure:</para>
chapters/12.xml-    <example xml:id="example-random-id-TW5Q">
chapters/12.xml-      <title>
chapters/12.xml-        <anchor xml:id="c12e14d5"/>
--
chapters/12.xml-      <valsi>jitro</valsi>: j1 controls j2 in activity j3</para>
chapters/12.xml-    </example>
chapters/12.xml-    <para role="indent">Note that this lujvo is symmetrical between
chapters/12.xml:    <valsi>lantro</valsi> (sheep-controller) and
chapters/12.xml-    <valsi>gerku</valsi>, but
chapters/12.xml:    <valsi>lantro</valsi> is itself an asymmetrical lujvo. The l2 place, the breed of sheep, is removed as dependent on l1. However, the lujvo
chapters/12.xml-    <valsi>lange'u</valsi> is both shorter than
chapters/12.xml:    <valsi>terlantroge'u</valsi> and sufficiently clear to warrant its use: its place structure, however, should be the same as that of the longer lujvo, for which
chapters/12.xml-    <valsi>lange'u</valsi> can be understood as an abbreviation.</para>
chapters/12.xml-    <para>Another example is
chapters/12.xml-    <valsi>xanmi'e</valsi>,
--
chapters/12.xml-    <valsi>xanmi'e</valsi>, the gismu
chapters/12.xml-    <valsi>pilno</valsi>, which is not explicit in the veljvo. And it also means that, for a place structure derivation that actually makes sense, rather than being ad-hoc, the Lojbanist should probably go through a derivation for
chapters/12.xml-    <valsi>xancypliminde</valsi> or one of the other possibilities that is analogous to the analysis of
chapters/12.xml:    <valsi>terlantroge'u</valsi> above, even if he or she decides to stick with a shorter, more convenient form like
chapters/12.xml-    <valsi>xanmi'e</valsi>. In addition, of course, the possibilities of elliptical lujvo increase their potential ambiguity enormously &ndash; an unavoidable fact which should be borne in mind.</para>
chapters/12.xml-  </section>
chapters/12.xml-  <section xml:id="section-comparatives">
*********************************************************************** likygau
chapters/12.xml-      <para><definition><content>l1 is a quantity of liquid of composition l2 under conditions l3</content></definition></para>
chapters/12.xml-    </example>
chapters/12.xml-    <para role="noindent">can give
chapters/12.xml:    <valsi>likygau</valsi>, meaning
chapters/12.xml-    <quote>to liquefy</quote>:</para>
chapters/12.xml-
chapters/12.xml-    <example xml:id="example-random-id-p5Bt">
--
chapters/12.xml-      <para><definition><content>g1 (agent) causes l1 to be a quantity of liquid of composition l2 under conditions l3.</content></definition></para>
chapters/12.xml-    </example>
chapters/12.xml-    <para role="indent">While
chapters/12.xml:    <valsi>likygau</valsi> correctly represents
chapters/12.xml-    <quote>causes to be a liquid</quote>, a different lujvo based on
chapters/12.xml-    <valsi>galfi</valsi> (meaning
chapters/12.xml-    <quote>modify</quote>) may be more appropriate for
--
chapters/12.xml-    <valsi>gasnu</valsi>, because its r1 place is another event rather than a person:
chapters/12.xml-    <jbophrase>lo rinka</jbophrase> is a cause, not a causer. Thus the place structure of
chapters/12.xml-    <valsi>likyri'a</valsi>, a lujvo analogous to
chapters/12.xml:    <valsi>likygau</valsi>, is</para>
chapters/12.xml-    <example xml:id="example-random-id-1HT3">
chapters/12.xml-      <title>
chapters/12.xml-        <anchor xml:id="c12e13d11"/>
*********************************************************************** likyri'a
chapters/12.xml-    <valsi>rinka</valsi> is less generally useful than
chapters/12.xml-    <valsi>gasnu</valsi>, because its r1 place is another event rather than a person:
chapters/12.xml-    <jbophrase>lo rinka</jbophrase> is a cause, not a causer. Thus the place structure of
chapters/12.xml:    <valsi>likyri'a</valsi>, a lujvo analogous to
chapters/12.xml-    <valsi>likygau</valsi>, is</para>
chapters/12.xml-    <example xml:id="example-random-id-1HT3">
chapters/12.xml-      <title>
*********************************************************************** livgyterbilma
chapters/04.xml-        <anchor xml:id="c4e6d15"/>
chapters/04.xml-      </title>
chapters/04.xml-      <lujvo-making>
chapters/04.xml:        <jbo>na'e zei .a zei na'e zei by. livgyterbilma</jbo>
chapters/04.xml-        <gloss>non-A, non-B liver-disease</gloss>
chapters/04.xml-        <natlang>non-A, non-B hepatitis</natlang>
chapters/04.xml-      </lujvo-making>
--
chapters/04.xml-    <valsi>zei</valsi>s from it doesn't end with a brivla, and in fact is not even grammatical. As written, the example is a tanru with two components, but by adding a
chapters/04.xml-    <valsi>zei</valsi> between
chapters/04.xml-    <valsi>by.</valsi> and
chapters/04.xml:    <valsi>livgyterbilma</valsi> to produce</para>
chapters/04.xml-    <example role="lujvo-example" xml:id="example-random-id-Wnaz">
chapters/04.xml-      <title>
chapters/04.xml-
--
chapters/04.xml-        <anchor xml:id="c4e6d17"/>
chapters/04.xml-      </title>
chapters/04.xml-      <lujvo-making>
chapters/04.xml:        <jbo>na'e zei .a zei na'e zei by. zei livgyterbilma</jbo>
chapters/04.xml-        <natlang>non-A-non-B-hepatitis</natlang>
chapters/04.xml-      </lujvo-making>
chapters/04.xml-    </example>
*********************************************************************** lo'ikle
chapters/04.xml-    <simplelist type="horiz" columns="3">
chapters/04.xml-      <member><valsi>lotkle</valsi></member>
chapters/04.xml-      <member><valsi>blokle</valsi></member>
chapters/04.xml:      <member><valsi>lo'ikle</valsi></member>
chapters/04.xml-
chapters/04.xml-      <member><valsi>lotlei</valsi></member>
chapters/04.xml-      <member><valsi>blolei</valsi></member>
--
chapters/04.xml-            <td>5858</td>
chapters/04.xml-          </tr>
chapters/04.xml-          <tr>
chapters/04.xml:            <td><valsi>lo'ikle</valsi></td>
chapters/04.xml-            <td>6367</td>
chapters/04.xml-          </tr>
chapters/04.xml-          <tr>
--
chapters/04.xml- So the form
chapters/04.xml-    <valsi>blolei</valsi> is preferred, but only by a tiny margin over
chapters/04.xml-    <valsi>blokle</valsi>; "lotlei" and "lotkle" are only slightly worse;
chapters/04.xml:    <valsi>lo'ikle</valsi> suffers because of its apostrophe, and
chapters/04.xml-    <valsi>lo'irlei</valsi> because of having both apostrophe and hyphen.</para>
chapters/04.xml-    <para>Our third example will result in forming both a lujvo and a name from the tanru
chapters/04.xml-    <jbophrase>logji bangu girzu</jbophrase>, or
*********************************************************************** lo'irlei
chapters/04.xml-
chapters/04.xml-      <member><valsi>lotlei</valsi></member>
chapters/04.xml-      <member><valsi>blolei</valsi></member>
chapters/04.xml:      <member><valsi>lo'irlei</valsi></member>
chapters/04.xml-    </simplelist>
chapters/04.xml-    <para>Only
chapters/04.xml:    <valsi>lo'irlei</valsi> requires hyphenation (to avoid confusion with the cmavo sequence
chapters/04.xml-    <jbophrase>lo'i lei</jbophrase>). All six forms are valid versions of the lujvo, as are the six further forms using long rafsi; however, the scoring algorithm produces the following results:</para>
chapters/04.xml-    <informaltable>
chapters/04.xml-          <tr>
--
chapters/04.xml-            <td>5847</td>
chapters/04.xml-          </tr>
chapters/04.xml-          <tr>
chapters/04.xml:            <td><valsi>lo'irlei</valsi></td>
chapters/04.xml-            <td>7456</td>
chapters/04.xml-          </tr>
chapters/04.xml-    </informaltable>
--
chapters/04.xml-    <valsi>blolei</valsi> is preferred, but only by a tiny margin over
chapters/04.xml-    <valsi>blokle</valsi>; "lotlei" and "lotkle" are only slightly worse;
chapters/04.xml-    <valsi>lo'ikle</valsi> suffers because of its apostrophe, and
chapters/04.xml:    <valsi>lo'irlei</valsi> because of having both apostrophe and hyphen.</para>
chapters/04.xml-    <para>Our third example will result in forming both a lujvo and a name from the tanru
chapters/04.xml-    <jbophrase>logji bangu girzu</jbophrase>, or
chapters/04.xml-    <quote>logical-language group</quote> in English. (
*********************************************************************** lojbangri
chapters/04.xml-    </simplelist>
chapters/04.xml-    <para>After hyphenation, we have:</para>
chapters/04.xml-    <simplelist type="horiz" columns="3">
chapters/04.xml:      <member><valsi valid="false">lojbangri</valsi></member>
chapters/04.xml-      <member><valsi valid="false">lojbaugri</valsi></member>
chapters/04.xml-      <member><valsi valid="false">lojbangygri</valsi></member>
chapters/04.xml-
--
chapters/04.xml-
chapters/04.xml- The only fully reduced lujvo forms are
chapters/04.xml-
chapters/04.xml:    <valsi>lojbangri</valsi> and
chapters/04.xml-    <valsi>lojbaugri</valsi>, of which the latter has a slightly lower score: 8827 versus 8796, respectively. However, for the name of the organization, we chose to make sure the name of the language was embedded in it, and to use the clearer long-form rafsi for
chapters/04.xml-    <valsi>girzu</valsi>, producing
chapters/04.xml-    <cmevla>lojbangirz.</cmevla></para>
*********************************************************************** lojbaugri
chapters/04.xml-    <para>After hyphenation, we have:</para>
chapters/04.xml-    <simplelist type="horiz" columns="3">
chapters/04.xml-      <member><valsi valid="false">lojbangri</valsi></member>
chapters/04.xml:      <member><valsi valid="false">lojbaugri</valsi></member>
chapters/04.xml-      <member><valsi valid="false">lojbangygri</valsi></member>
chapters/04.xml-
chapters/04.xml-      <member><valsi valid="false">logjybangri</valsi></member>
--
chapters/04.xml- The only fully reduced lujvo forms are
chapters/04.xml-
chapters/04.xml-    <valsi>lojbangri</valsi> and
chapters/04.xml:    <valsi>lojbaugri</valsi>, of which the latter has a slightly lower score: 8827 versus 8796, respectively. However, for the name of the organization, we chose to make sure the name of the language was embedded in it, and to use the clearer long-form rafsi for
chapters/04.xml-    <valsi>girzu</valsi>, producing
chapters/04.xml-    <cmevla>lojbangirz.</cmevla></para>
chapters/04.xml-    <para>Finally, here is a four-part lujvo with a cmavo in it, based on the tanru
*********************************************************************** lotkle
chapters/04.xml-    <rafsi>-kle-</rafsi> and
chapters/04.xml-    <rafsi>-lei-</rafsi>. Both these gismu are among the handful which have both CVV-form and CCV-form rafsi, so there is an unusual number of possibilities available for a two-part tanru:</para>
chapters/04.xml-    <simplelist type="horiz" columns="3">
chapters/04.xml:      <member><valsi>lotkle</valsi></member>
chapters/04.xml-      <member><valsi>blokle</valsi></member>
chapters/04.xml-      <member><valsi>lo'ikle</valsi></member>
chapters/04.xml-
--
chapters/04.xml-    <jbophrase>lo'i lei</jbophrase>). All six forms are valid versions of the lujvo, as are the six further forms using long rafsi; however, the scoring algorithm produces the following results:</para>
chapters/04.xml-    <informaltable>
chapters/04.xml-          <tr>
chapters/04.xml:            <td><valsi>lotkle</valsi></td>
chapters/04.xml-            <td>5878</td>
chapters/04.xml-          </tr>
chapters/04.xml-          <tr>
--
chapters/04.xml-
chapters/04.xml- So the form
chapters/04.xml-    <valsi>blolei</valsi> is preferred, but only by a tiny margin over
chapters/04.xml:    <valsi>blokle</valsi>; "lotlei" and "lotkle" are only slightly worse;
chapters/04.xml-    <valsi>lo'ikle</valsi> suffers because of its apostrophe, and
chapters/04.xml-    <valsi>lo'irlei</valsi> because of having both apostrophe and hyphen.</para>
chapters/04.xml-    <para>Our third example will result in forming both a lujvo and a name from the tanru
*********************************************************************** lotlei
chapters/04.xml-      <member><valsi>blokle</valsi></member>
chapters/04.xml-      <member><valsi>lo'ikle</valsi></member>
chapters/04.xml-
chapters/04.xml:      <member><valsi>lotlei</valsi></member>
chapters/04.xml-      <member><valsi>blolei</valsi></member>
chapters/04.xml-      <member><valsi>lo'irlei</valsi></member>
chapters/04.xml-    </simplelist>
--
chapters/04.xml-            <td>6367</td>
chapters/04.xml-          </tr>
chapters/04.xml-          <tr>
chapters/04.xml:            <td><valsi>lotlei</valsi></td>
chapters/04.xml-            <td>5867</td>
chapters/04.xml-          </tr>
chapters/04.xml-          <tr>
--
chapters/04.xml-
chapters/04.xml- So the form
chapters/04.xml-    <valsi>blolei</valsi> is preferred, but only by a tiny margin over
chapters/04.xml:    <valsi>blokle</valsi>; "lotlei" and "lotkle" are only slightly worse;
chapters/04.xml-    <valsi>lo'ikle</valsi> suffers because of its apostrophe, and
chapters/04.xml-    <valsi>lo'irlei</valsi> because of having both apostrophe and hyphen.</para>
chapters/04.xml-    <para>Our third example will result in forming both a lujvo and a name from the tanru
*********************************************************************** mampa'u
chapters/04.xml-        <anchor xml:id="c4e5d7"/>
chapters/04.xml-      </title>
chapters/04.xml-      <lujvo-making>
chapters/04.xml:        <jbo>mampa'u</jbo>
chapters/04.xml-      </lujvo-making>
chapters/04.xml-    </example>
chapters/04.xml-    <para role="noindent">which refers specifically to the concept
chapters/04.xml-    <quote>maternal grandfather</quote>. The two gismu that constitute the tanru are represented in
chapters/04.xml:    <valsi>mampa'u</valsi> by the rafsi
chapters/04.xml-    <rafsi>mam-</rafsi> and
chapters/04.xml-    <rafsi>-pa'u</rafsi>, respectively; these two rafsi are then concatenated together to form
chapters/04.xml:    <valsi>mampa'u</valsi>.</para>
chapters/04.xml-    <para> <indexterm type="general"><primary>long rafsi form</primary><secondary>compared with short form in effect on lujvo meaning</secondary></indexterm>  <indexterm type="general"><primary>short rafsi form</primary><secondary>compared with long form in effect on lujvo meaning</secondary></indexterm>  <indexterm type="general"><primary>rafsi form</primary><secondary>effect of choice on meaning of lujvo</secondary></indexterm>  <indexterm type="general"><primary>lujvo</primary><secondary>multiple forms of</secondary></indexterm>  <indexterm type="general"><primary>lujvo</primary><secondary>meaning of</secondary></indexterm> Like gismu, lujvo have only one meaning. When a lujvo is formally entered into a dictionary of the language, a specific definition will be assigned based on one particular interrelationship between the terms. (See
chapters/04.xml-    <xref linkend="chapter-lujvo"/> for how this has been done.) Unlike gismu, lujvo may have more than one form. This is because there is no difference in meaning between the various rafsi for a gismu when they are used to build a lujvo. A long rafsi may be used, especially in noisy environments, in place of a short rafsi; the result is considered the same lujvo, even though the word is spelled and pronounced differently. Thus the word
chapters/04.xml-
--
chapters/04.xml-        <anchor xml:id="c4e6d10"/>
chapters/04.xml-      </title>
chapters/04.xml-      <lujvo-making>
chapters/04.xml:        <jbo>mampa'u</jbo>
chapters/04.xml-        <veljvo>mamta patfu</veljvo>
chapters/04.xml-        <gloss><quote>mother father</quote></gloss>
chapters/04.xml-        <natlang>or <quote>maternal grandfather</quote></natlang>
*********************************************************************** manskapi
chapters/01.xml-    <para> <indexterm type="general"><primary>this book</primary><secondary>reviewers of</secondary></indexterm>  <indexterm type="general"><primary>reviewers of this book</primary></indexterm> I would like to thank the following people for their detailed reviews, suggestions, comments, and early detection of my embarrassing errors in Lojban, logic, English, and cross-references: Nick Nicholas, Mark Shoulson, Veijo Vilva, Colin Fine, And Rosta, Jorge Llambias, Iain Alexander, Paulo S. L. M. Barreto, Robert J. Chassell, Gale Cowan, Karen Stein, Ivan Derzhanski, Jim Carter, Irene Gates, Bob LeChevalier, John Parks-Clifford (also known as
chapters/01.xml-    <quote>pc</quote>), and Nora Tansky LeChevalier.</para>
chapters/01.xml-    <para>Nick Nicholas (NSN) would like to thank the following Lojbanists: Mark Shoulson, Veijo Vilva, Colin Fine, And Rosta, and Iain Alexander for their suggestions and comments; John Cowan, for his extensive comments, his exemplary trailblazing of Lojban grammar, and for solving the
chapters/01.xml:    <valsi>manskapi</valsi> dilemma for NSN; Jorge Llambias, for his even more extensive comments, and for forcing NSN to think more than he was inclined to; Bob LeChevalier, for his skeptical overview of the issue, his encouragement, and for scouring all Lojban text his computer has been burdened with for lujvo; Nora Tansky LeChevalier, for writing the program converting old rafsi text to new rafsi text, and sparing NSN from embarrassing errors; and Jim Carter, for his dogged persistence in analyzing lujvo algorithmically, which inspired this research, and for first identifying the three lujvo classes.</para>
chapters/01.xml-
chapters/01.xml-    <para> <indexterm type="general"><primary>Brown</primary><secondary>James Cooke</secondary></indexterm> Of course, the entire Loglan Project owes a considerable debt to James Cooke Brown as the language inventor, and also to several earlier contributors to the development of the language. Especially noteworthy are Doug Landauer, Jeff Prothero, Scott Layson, Jeff Taylor, and Bob McIvor. Final responsibility for the remaining errors and infelicities is solely mine.</para>
chapters/01.xml-
*********************************************************************** mi'erxanpli
chapters/12.xml-    </example>
chapters/12.xml-    <para role="noindent">which lead to the three different lujvo
chapters/12.xml-    <valsi>xanplimi'e</valsi>,
chapters/12.xml:    <valsi>mi'erxanpli</valsi>, and
chapters/12.xml-    <valsi>minkemxanpli</valsi> respectively.</para>
chapters/12.xml-    <para> <indexterm type="general"><primary>latent component</primary></indexterm> Does this make
chapters/12.xml-    <valsi>xanmi'e</valsi> wrong? By no means. But it does mean that there is a latent component to the meaning of
*********************************************************************** minkemxanpli
chapters/12.xml-    <para role="noindent">which lead to the three different lujvo
chapters/12.xml-    <valsi>xanplimi'e</valsi>,
chapters/12.xml-    <valsi>mi'erxanpli</valsi>, and
chapters/12.xml:    <valsi>minkemxanpli</valsi> respectively.</para>
chapters/12.xml-    <para> <indexterm type="general"><primary>latent component</primary></indexterm> Does this make
chapters/12.xml-    <valsi>xanmi'e</valsi> wrong? By no means. But it does mean that there is a latent component to the meaning of
chapters/12.xml-
*********************************************************************** mudysiclu
chapters/04.xml-    <jbophrase>mudri siclu</jbophrase> (
chapters/04.xml-    <quote>wooden whistle</quote>) cannot form the lujvo
chapters/04.xml-    <valsi valid="false">mudsiclu</valsi>; instead,
chapters/04.xml:    <valsi>mudysiclu</valsi> must be used. (Remember that
chapters/04.xml-    <letteral>y</letteral> is not counted in determining whether the first five letters of a brivla contain a consonant cluster: this is why.)</para>
chapters/04.xml-    <para> <indexterm type="general"><primary>rafsi</primary><secondary>four-letter</secondary><tertiary>requirement for y-hyphen</tertiary></indexterm> The
chapters/04.xml-    y-hyphen is also used to attach a 4-letter rafsi, formed by dropping the final vowel of a gismu, to the following rafsi. (This procedure was shown, but not explained, in
*********************************************************************** nalbrablo
chapters/12.xml-    <quote>to go to a walking surface</quote>. Instead, we would need
chapters/12.xml-    <valsi>selkemdzukla</valsi>, with an explicit rafsi for
chapters/12.xml-    <valsi>ke</valsi>. Similarly,
chapters/12.xml:    <valsi>nalbrablo</valsi> (from
chapters/12.xml-    <jbophrase>na'e barda bloti</jbophrase>) means
chapters/12.xml-    <quote>non-big boat</quote>, whereas
chapters/12.xml-
*********************************************************************** nalmle
chapters/15.xml-    <rafsi>-no'e-</rafsi>. The selbri in
chapters/15.xml-    <xref linkend="example-random-id-qh9U"/> through
chapters/15.xml-    <xref linkend="example-random-id-qHAV"/> could be replaced by the lujvo
chapters/15.xml:    <valsi>nalmle</valsi>,
chapters/15.xml-    <valsi>normle</valsi>, and
chapters/15.xml-    <valsi>tolmle</valsi> respectively.</para>
chapters/15.xml-    <para>This large variety of scalar negations is provided because different scales have different properties. Some scales are open-ended in both directions: there is no
*********************************************************************** nelcymau
chapters/12.xml-
chapters/12.xml-
chapters/12.xml-    <para> <indexterm type="general"><primary>comparative lujvo</primary><secondary>potential ambiguity in</secondary></indexterm> For example, does
chapters/12.xml:    <valsi>nelcymau</valsi> mean
chapters/12.xml-    <quote>X likes Y more than X likes Z</quote>, or
chapters/12.xml-    <quote>X likes Y more than Z likes Y</quote>? Does
chapters/12.xml-    <valsi>klamau</valsi> mean:
--
chapters/12.xml-        <anchor xml:id="c12e15d6"/>
chapters/12.xml-      </title>
chapters/12.xml-      <para>
chapters/12.xml:      <valsi>nelcymau</valsi>: z1, more than z2, likes n2 by amount z4</para>
chapters/12.xml-      <para>
chapters/12.xml:      <valsi>selnelcymau</valsi>: z1, more than z2, is liked by n1 in amount z4</para>
chapters/12.xml-      <para>
chapters/12.xml-      <valsi>klamau</valsi>: z1, more than z2, goes to k2 from k3 via k4 by means of k5</para>
chapters/12.xml-      <para>
--
chapters/12.xml-    <para role="noindent">(See
chapters/12.xml-    <xref linkend="chapter-abstractions"/> for the way in which this problem is resolved when lujvo aren't used.)</para>
chapters/12.xml-    <para>The ordering rule places the things being compared first, and the other seltau places following. Unfortunately the z4 place, which expresses by how much one entity exceeds the other, is displaced into a lujvo place whose number is different for each lujvo. For example, while
chapters/12.xml:    <valsi>nelcymau</valsi> has z4 as its fourth place,
chapters/12.xml-    <valsi>klamau</valsi> has it as its sixth place. In any sentence where a difficulty arises, this amount-place can be redundantly tagged with
chapters/12.xml-    <valsi>vemau</valsi> (for
chapters/12.xml-    <valsi>zmadu</valsi>) or
*********************************************************************** nilkla
chapters/12.xml-    <valsi>nu</valsi>, as well as the other abstractors mentioned in this section, is given in
chapters/12.xml-    <xref linkend="chapter-abstractions"/>.</para>
chapters/12.xml-    <para> <indexterm type="general"><primary>lujvo place structure</primary><secondary>multi-place abstraction lujvo</secondary></indexterm>  <indexterm type="general"><primary>lujvo place structure</primary><secondary>&quot;ni&quot; lujvo</secondary></indexterm> For those abstractors which have a second place as well, the standard convention is to place this place after, rather than before, the places of the brivla being abstracted. The place structure of
chapters/12.xml:    <valsi>nilkla</valsi>, the lujvo derived from
chapters/12.xml-    <jbophrase>ni klama</jbophrase>, is the imposing:</para>
chapters/12.xml-    <example xml:id="example-random-id-yURu">
chapters/12.xml-      <title>
*********************************************************************** normle
chapters/15.xml-    <xref linkend="example-random-id-qh9U"/> through
chapters/15.xml-    <xref linkend="example-random-id-qHAV"/> could be replaced by the lujvo
chapters/15.xml-    <valsi>nalmle</valsi>,
chapters/15.xml:    <valsi>normle</valsi>, and
chapters/15.xml-    <valsi>tolmle</valsi> respectively.</para>
chapters/15.xml-    <para>This large variety of scalar negations is provided because different scales have different properties. Some scales are open-ended in both directions: there is no
chapters/15.xml-    <quote>ultimately ugly</quote> or
*********************************************************************** nunctikezgau
chapters/12.xml-
chapters/12.xml-
chapters/12.xml-    <para>Let us make a detailed analysis of the lujvo
chapters/12.xml:    <valsi>nunctikezgau</valsi>, meaning
chapters/12.xml-    <quote>to feed</quote>. (If you think this lujvo is excessively longwinded, be patient.) The veljvo of
chapters/12.xml-
chapters/12.xml:    <valsi>nunctikezgau</valsi> is
chapters/12.xml-    <jbophrase>nu citka kei gasnu</jbophrase>. The relevant place structures are:</para>
chapters/12.xml-    <example xml:id="example-random-id-bSDW">
chapters/12.xml-      <title>
--
chapters/12.xml-      <para><definition><content>n1 is the event of c1 eating c2</content></definition></para>
chapters/12.xml-    </example>
chapters/12.xml-    <para role="indent">Now we can transform the veljvo of
chapters/12.xml:    <valsi>nunctikezgau</valsi> into
chapters/12.xml-    <jbophrase>nuncti gasnu</jbophrase>. The g2 place (what is brought about by the actor g1) obviously denotes the same thing as n1 (the event of eating). So we can eliminate g2 as redundant, leaving us with a tentative place structure of</para>
chapters/12.xml-    <example xml:id="example-random-id-izvp">
chapters/12.xml-      <title>
--
chapters/12.xml-    <para role="indent">But it is also possible to omit the n1 place itself! The n1 place describes the event brought about; an event in Lojban is described as a bridi, by a selbri and its sumti; the selbri is already known (it's the seltau), and the sumti are also already known (they're in the lujvo place structure). So n1 would not give us any information we didn't already know. In fact, the n1=g2 place is dependent on c1 and c2 jointly &ndash; it does not depend on either c1 or c2 by itself. Being dependent and derived from the seltau, it is omissible. So the final place structure of
chapters/12.xml-
chapters/12.xml-
chapters/12.xml:    <valsi>nunctikezgau</valsi> is:</para>
chapters/12.xml-    <example xml:id="example-random-id-9oTP">
chapters/12.xml-      <title>
chapters/12.xml-        <anchor xml:id="c12e13d4"/>
--
chapters/12.xml-    <jbophrase>se gasnu</jbophrase>, then the rafsi
chapters/12.xml-    <rafsi>nun</rafsi> and
chapters/12.xml-    <rafsi>kez</rafsi> in
chapters/12.xml:    <valsi>nunctikezgau</valsi> are only telling us what we would already have guessed &ndash; that the seltau of a
chapters/12.xml-    <valsi>gasnu</valsi> lujvo is an event. If we drop these rafsi out, and use instead the shorter lujvo
chapters/12.xml-    <valsi>ctigau</valsi>, rejecting its symmetrical interpretation (
chapters/12.xml-    <quote>someone who both does and eats</quote>;
--
chapters/12.xml-    <valsi>gasnu</valsi>.)</para>
chapters/12.xml-    <para>So we can simply use
chapters/12.xml-    <valsi>ctigau</valsi> with the same place structure as
chapters/12.xml:    <valsi>nunctikezgau</valsi>:</para>
chapters/12.xml-    <example xml:id="example-random-id-ITvd">
chapters/12.xml-      <title>
chapters/12.xml-        <anchor xml:id="c12e13d5"/>
*********************************************************************** nunji'a
chapters/05.xml-    <valsi>ja</valsi> is appropriate:</para>
chapters/05.xml-    <informaltable>
chapters/05.xml-          <tr>
chapters/05.xml:            <td><jbophrase>nunji'a nunterji'a</jbophrase></td>
chapters/05.xml-            <td>victory defeat</td>
chapters/05.xml-            <td>Skt</td>
chapters/05.xml-            <td>victory or defeat</td>
--
chapters/05.xml-    </informaltable>
chapters/05.xml-    <variablelist>
chapters/05.xml-      <varlistentry>
chapters/05.xml:        <term><valsi>nunji'a</valsi></term>
chapters/05.xml-        <listitem><para>event-of-winning</para></listitem>
chapters/05.xml-      </varlistentry>
chapters/05.xml-      <varlistentry>
*********************************************************************** nunkalte
chapters/05.xml-            <td>Hun</td>
chapters/05.xml-          </tr>
chapters/05.xml-          <tr>
chapters/05.xml:            <td><jbophrase>mirli nunkalte</jbophrase></td>
chapters/05.xml-            <td>deer hunting</td>
chapters/05.xml-            <td>Hun</td>
chapters/05.xml-          </tr>
chapters/05.xml-          <tr>
chapters/05.xml:            <td><jbophrase>finpe nunkalte</jbophrase></td>
chapters/05.xml-            <td>fish hunting</td>
chapters/05.xml-            <td>Tur,Kor,Udm,Aba</td>
chapters/05.xml-            <td>fishing</td>
--
chapters/05.xml-        <listitem><para>event-of-teaching</para></listitem>
chapters/05.xml-      </varlistentry>
chapters/05.xml-      <varlistentry>
chapters/05.xml:        <term><valsi>nunkalte</valsi></term>
chapters/05.xml-        <listitem><para>event-of-hunting</para></listitem>
chapters/05.xml-      </varlistentry>
chapters/05.xml-      <varlistentry>
*********************************************************************** nunkilbra
chapters/05.xml-    <para> <indexterm type="general"><primary>asymmetrical tanru types</primary><secondary>object-of-action + action</secondary></indexterm> The tertau represents an action, and the seltau then represents the object of that action:</para>
chapters/05.xml-    <informaltable>
chapters/05.xml-          <tr>
chapters/05.xml:            <td><jbophrase>pinsi nunkilbra</jbophrase></td>
chapters/05.xml-            <td>pencil sharpener</td>
chapters/05.xml-            <td>Hun</td>
chapters/05.xml-          </tr>
--
chapters/05.xml-    </informaltable>
chapters/05.xml-    <variablelist>
chapters/05.xml-      <varlistentry>
chapters/05.xml:        <term><valsi>nunkilbra</valsi></term>
chapters/05.xml-        <listitem><para>sharpness-apparatus</para></listitem>
chapters/05.xml-      </varlistentry>
chapters/05.xml-      <varlistentry>
*********************************************************************** nunklama
chapters/12.xml-      <para><definition><content>nu1 is the event of k1's coming/going to k2 from k3 via route k4 by means k5.</content></definition></para>
chapters/12.xml-    </example>
chapters/12.xml-    <para role="indent">Here the first place of
chapters/12.xml:    <valsi>nunklama</valsi> is the first and only place of
chapters/12.xml-    <valsi>nu</valsi>, and the other five places have been pushed down by one to occupy the second through the sixth places. Full information on
chapters/12.xml-    <valsi>nu</valsi>, as well as the other abstractors mentioned in this section, is given in
chapters/12.xml-    <xref linkend="chapter-abstractions"/>.</para>
*********************************************************************** nunpinxe
chapters/05.xml-            <td>extremity</td>
chapters/05.xml-          </tr>
chapters/05.xml-          <tr>
chapters/05.xml:            <td><jbophrase>nuncti nunpinxe</jbophrase></td>
chapters/05.xml-            <td>eating drinking</td>
chapters/05.xml-            <td>Udm</td>
chapters/05.xml-            <td>cuisine</td>
--
chapters/05.xml-        <listitem><para>event-of-eating</para></listitem>
chapters/05.xml-      </varlistentry>
chapters/05.xml-      <varlistentry>
chapters/05.xml:        <term><valsi>nunpinxe</valsi></term>
chapters/05.xml-        <listitem><para>event-of-drinking</para></listitem>
chapters/05.xml-      </varlistentry>
chapters/05.xml-    </variablelist>
*********************************************************************** nunsoidji
chapters/12.xml-      <para><definition><content>ni1 is the amount of k1's coming/going to k2 from k3 via route k4 by means k5, measured on scale ni2.</content></definition></para>
chapters/12.xml-    </example>
chapters/12.xml-    <para role="indent">It is not uncommon for abstractors to participate in the making of more complex lujvo as well. For example,
chapters/12.xml:    <valsi>nunsoidji</valsi>, from the veljvo</para>
chapters/12.xml-    <example role="interlinear-gloss-example" xml:id="example-random-id-RKcH">
chapters/12.xml-      <title>
chapters/12.xml-        <anchor xml:id="c12e12d4"/>
--
chapters/12.xml-    <para role="noindent">where the d2 place has disappeared altogether, being replaced by the places of the seltau. As shown in
chapters/12.xml-    <xref linkend="example-random-id-8Nos"/>, the ordering follows this idea of replacement: the seltau places are inserted at the point where the omitted abstraction place exists in the tertau.</para>
chapters/12.xml-    <para>The lujvo
chapters/12.xml:    <valsi>nunsoidji</valsi> is quite different from the ordinary asymmetric lujvo
chapters/12.xml-
chapters/12.xml-    <valsi>soidji</valsi>, a
chapters/12.xml-    <quote>soldier desirer</quote>, whose place structure is just</para>
--
chapters/12.xml-      <para><definition><content>d1 desires (a soldier of army s2) for purpose d3</content></definition></para>
chapters/12.xml-    </example>
chapters/12.xml-    <para role="indent">A
chapters/12.xml:    <valsi>nunsoidji</valsi> might be someone who is about to enlist, whereas a
chapters/12.xml-    <valsi>soidji</valsi> might be a camp-follower.</para>
chapters/12.xml-    <para>One use of abstract lujvo is to eliminate the need for explicit
chapters/12.xml-
*********************************************************************** nunte'a
chapters/05.xml-            <td>host</td>
chapters/05.xml-          </tr>
chapters/05.xml-          <tr>
chapters/05.xml:            <td><jbophrase>zerle'a nunte'a</jbophrase></td>
chapters/05.xml-            <td>thief fear</td>
chapters/05.xml-            <td>Skt</td>
chapters/05.xml-            <td>fear of thieves</td>
--
chapters/05.xml-        <listitem><para>crime-taker</para></listitem>
chapters/05.xml-      </varlistentry>
chapters/05.xml-      <varlistentry>
chapters/05.xml:        <term><valsi>nunte'a</valsi></term>
chapters/05.xml-        <listitem><para>event-of-fearing</para></listitem>
chapters/05.xml-      </varlistentry>
chapters/05.xml-    </variablelist>
*********************************************************************** nunterji'a
chapters/05.xml-    <valsi>ja</valsi> is appropriate:</para>
chapters/05.xml-    <informaltable>
chapters/05.xml-          <tr>
chapters/05.xml:            <td><jbophrase>nunji'a nunterji'a</jbophrase></td>
chapters/05.xml-            <td>victory defeat</td>
chapters/05.xml-            <td>Skt</td>
chapters/05.xml-            <td>victory or defeat</td>
--
chapters/05.xml-        <listitem><para>event-of-winning</para></listitem>
chapters/05.xml-      </varlistentry>
chapters/05.xml-      <varlistentry>
chapters/05.xml:        <term><valsi>nunterji'a</valsi></term>
chapters/05.xml-        <listitem><para>event-of-losing</para></listitem>
chapters/05.xml-      </varlistentry>
chapters/05.xml-      <varlistentry>
*********************************************************************** pacraistu
chapters/05.xml-            <td>pinky</td>
chapters/05.xml-          </tr>
chapters/05.xml-          <tr>
chapters/05.xml:            <td><jbophrase>pacraistu zdani</jbophrase></td>
chapters/05.xml-            <td>hell house</td>
chapters/05.xml-            <td>Skt</td>
chapters/05.xml-          </tr>
--
chapters/05.xml-    </informaltable>
chapters/05.xml-    <variablelist>
chapters/05.xml-      <varlistentry>
chapters/05.xml:        <term><valsi>pacraistu</valsi></term>
chapters/05.xml-        <listitem><para>evil-superlative-site</para></listitem>
chapters/05.xml-      </varlistentry>
chapters/05.xml-    </variablelist>
*********************************************************************** pevrisnyjelca
chapters/13.xml-    <valsi>risnyjelca</valsi> (heart burn) might have a place structure like:</para>
chapters/13.xml-    <definition><content>x1 is the heart of x2, burning in atmosphere x3 at temperature x4</content></definition>
chapters/13.xml-    <para>whereas
chapters/13.xml:    <valsi>pevrisnyjelca</valsi>, explicitly marked as figurative, might have the place structure:</para>
chapters/13.xml-    <definition><content>x1 is indigestion/heartburn suffered by x2</content></definition>
chapters/13.xml-    <para>which obviously has nothing to do with the places of either
chapters/13.xml-    <valsi>risna</valsi> or
*********************************************************************** posydji
chapters/12.xml-  <section xml:id="section-tertau-SE">
chapters/12.xml-    <title>Eliding SE rafsi from tertau</title>
chapters/12.xml-    <para> <indexterm type="general"><primary>lujvo place structure</primary><secondary>effect of &quot;SE&quot;-dropping in tertau</secondary></indexterm> Eliding SE rafsi from tertau gets us into much more trouble. To understand why, recall that lujvo, following their veljvo, describe some type of whatever their tertau describe. Thus,
chapters/12.xml:    <valsi>posydji</valsi> describes a type of
chapters/12.xml-    <valsi>djica</valsi>,
chapters/12.xml-    <valsi>gerzda</valsi> describes a type of
chapters/12.xml-    <valsi>zdani</valsi>, and so on. What is certain is that
*********************************************************************** rairgugde
chapters/18.xml-      </interlinear-gloss>
chapters/18.xml-    </example>
chapters/18.xml-    <para role="indent"> <indexterm type="general"><primary>indefinite values</primary><secondary>subjective</secondary></indexterm>  <indexterm type="general"><primary>subjective amounts</primary><secondary>expressing</secondary></indexterm> All of the numbers discussed so far are objective, even if indefinite. If there are exactly six superpowers (
chapters/18.xml:    <valsi>rairgugde</valsi>,
chapters/18.xml-    <quote>superlative-states</quote>) in the world, then
chapters/18.xml:    <jbophrase>ro rairgugde</jbophrase> means the same as
chapters/18.xml:    <jbophrase>xa rairgugde</jbophrase>. It is often useful, however, to express subjective indefinite values. The cmavo
chapters/18.xml-
chapters/18.xml-    <valsi>rau</valsi> (enough),
chapters/18.xml-
*********************************************************************** ricrxaceru
chapters/04.xml-    <quote>maple sugar</quote> could get the fu'ivla
chapters/04.xml-
chapters/04.xml-    <valsi>saktrxaceru</valsi>, or could be represented by the tanru
chapters/04.xml:    <jbophrase>tricrxaceru sakta</jbophrase>. Technically,
chapters/04.xml:    <valsi>ricrxaceru</valsi> and
chapters/04.xml:    <valsi>tricrxaceru</valsi> are distinct fu'ivla, but they would surely be given the same meanings if both happened to be in use.</para>
chapters/04.xml-    <example role="lojbanization-example" xml:id="example-random-id-C0YS">
chapters/04.xml-      <title>
chapters/04.xml-
*********************************************************************** risnyjelca
chapters/13.xml-    <valsi>pe'a</valsi> has a rafsi, namely
chapters/13.xml-
chapters/13.xml-    <rafsi>pev</rafsi>. This rafsi is used in forming figurative (culturally dependent) lujvo, whose place structure need have nothing to do with the place structure of the components. Thus
chapters/13.xml:    <valsi>risnyjelca</valsi> (heart burn) might have a place structure like:</para>
chapters/13.xml-    <definition><content>x1 is the heart of x2, burning in atmosphere x3 at temperature x4</content></definition>
chapters/13.xml-    <para>whereas
chapters/13.xml:    <valsi>pevrisnyjelca</valsi>, explicitly marked as figurative, might have the place structure:</para>
chapters/13.xml-    <definition><content>x1 is indigestion/heartburn suffered by x2</content></definition>
chapters/13.xml-    <para>which obviously has nothing to do with the places of either
chapters/13.xml-    <valsi>risna</valsi> or
*********************************************************************** ro'inre'o
chapters/04.xml-    <letteral>y</letteral> letters even though the
chapters/04.xml-    <morphology>sc</morphology> actually appears in the form of
chapters/04.xml-    <valsi>sy.</valsi>. Similarly, the word
chapters/04.xml:    <valsi>ro'inre'o</valsi> contains
chapters/04.xml-    <morphology>nr</morphology> in the first five letters because the apostrophes are not counted for this purpose.</para>
chapters/04.xml-    <para> <indexterm type="general"><primary>brivla</primary><secondary>subtypes of</secondary></indexterm> The three subtypes of brivla are:</para>
chapters/04.xml-    <orderedlist>
--
chapters/04.xml-    <jbophrase valid="false">ro'ire'o</jbophrase> (which breaks up into two cmavo), nor can it be
chapters/04.xml-    <jbophrase valid="false">ro'irre'o</jbophrase> (which has an impermissible double consonant); the
chapters/04.xml-    n-hyphen is required, and the correct form of the hyphenated lujvo is
chapters/04.xml:    <valsi>ro'inre'o</valsi>. The same lujvo could also be expressed without hyphenation as
chapters/04.xml-    <valsi>rokre'o</valsi>.</para>
chapters/04.xml-    <para>
chapters/04.xml-<indexterm type="general"><primary>lujvo</primary><secondary>with zei</secondary></indexterm>
*********************************************************************** rokre'o
chapters/04.xml-    <jbophrase valid="false">ro'irre'o</jbophrase> (which has an impermissible double consonant); the
chapters/04.xml-    n-hyphen is required, and the correct form of the hyphenated lujvo is
chapters/04.xml-    <valsi>ro'inre'o</valsi>. The same lujvo could also be expressed without hyphenation as
chapters/04.xml:    <valsi>rokre'o</valsi>.</para>
chapters/04.xml-    <para>
chapters/04.xml-<indexterm type="general"><primary>lujvo</primary><secondary>with zei</secondary></indexterm>
chapters/04.xml-There is also a different way of building lujvo, or rather phrases which are grammatically and semantically equivalent to lujvo. You can make a phrase containing any desired words, joining each pair of them with the special cmavo
*********************************************************************** saktrxaceru
chapters/04.xml-    <quote>tree</quote>. Note that by the same principles,
chapters/04.xml-    <quote>maple sugar</quote> could get the fu'ivla
chapters/04.xml-
chapters/04.xml:    <valsi>saktrxaceru</valsi>, or could be represented by the tanru
chapters/04.xml-    <jbophrase>tricrxaceru sakta</jbophrase>. Technically,
chapters/04.xml-    <valsi>ricrxaceru</valsi> and
chapters/04.xml-    <valsi>tricrxaceru</valsi> are distinct fu'ivla, but they would surely be given the same meanings if both happened to be in use.</para>
*********************************************************************** seldzukla
chapters/12.xml-    <para role="indent">We can swap the k1 and k2 places using
chapters/12.xml-    <jbophrase>se dzukla</jbophrase>, but we cannot directly make
chapters/12.xml-    <jbophrase>se dzukla</jbophrase> into
chapters/12.xml:    <valsi>seldzukla</valsi>, which would represent the veljvo
chapters/12.xml-    <jbophrase>selcadzu klama</jbophrase> and plausibly mean something like
chapters/12.xml-    <quote>to go to a walking surface</quote>. Instead, we would need
chapters/12.xml-    <valsi>selkemdzukla</valsi>, with an explicit rafsi for
*********************************************************************** selgekmau
chapters/12.xml-    <para> <indexterm type="general"><primary>lujvo creation</primary><secondary>use of multiple SE in</secondary></indexterm> If the lujvo we want to modify with SE has a seltau already starting with a SE rafsi, we can take a shortcut. For instance,
chapters/12.xml-    <valsi>gekmau</valsi> means
chapters/12.xml-    <quote>happier than</quote>, while
chapters/12.xml:    <valsi>selgekmau</valsi> means
chapters/12.xml-    <quote>making people happier than, more enjoyable than, more of a 'se gleki' than</quote>. If something is less enjoyable than something else, we can say it is
chapters/12.xml:    <jbophrase>se selgekmau</jbophrase>.</para>
chapters/12.xml-    <para>But we can also say it is
chapters/12.xml:    <valsi>selselgekmau</valsi>. Two
chapters/12.xml-    <valsi>se</valsi> cmavo in a row cancel each other (
chapters/12.xml-    <jbophrase>se se gleki</jbophrase> means the same as just
chapters/12.xml-    <valsi>gleki</valsi>), so there would be no good reason to have
*********************************************************************** seljdasku
chapters/12.xml-    </example>
chapters/12.xml-    <para role="indent">The l3 place (the beliefs of the religion) is dependent on the l1 place (the religion) and so is omitted.</para>
chapters/12.xml-    <para>We could make this lujvo less messy by replacing it with
chapters/12.xml:    <jbophrase>se seljdasku</jbophrase>, where
chapters/12.xml:    <valsi>seljdasku</valsi> is a normal symmetrical lujvo with place structure:</para>
chapters/12.xml-    <example xml:id="example-random-id-7Tdb">
chapters/12.xml-      <title>
chapters/12.xml-        <anchor xml:id="c12e14d4"/>
--
chapters/12.xml-    </example>
chapters/12.xml-    <para role="noindent">which, according to the rule expressed in
chapters/12.xml-    <xref linkend="section-seltau-SE"/>, can be further expressed as
chapters/12.xml:    <valsi>selseljdasku</valsi>. However, there is no need for the ugly
chapters/12.xml-    <jbophrase>selsel-</jbophrase> prefix just to get the rules right:
chapters/12.xml-    <valsi>jdaselsku</valsi> is a reasonable, if anomalous, lujvo.</para>
chapters/12.xml-    <para>However, there is a further problem with
chapters/12.xml-    <valsi>jdaselsku</valsi>, not resolvable by using
chapters/12.xml:    <valsi>seljdasku</valsi>. No veljvo involving just the two gismu
chapters/12.xml-    <valsi>lijda</valsi> and
chapters/12.xml-    <valsi>cusku</valsi> can fully express the relationship implicit in prayer. A prayer is not just anything said by the adherents of a religion; nor is it even anything said by them acting as adherents of that religion. Rather, it is what they say under the authority of that religion, or using the religion as a medium, or following the rules associated with the religion, or something of the kind. So the veljvo is somewhat elliptical.</para>
chapters/12.xml-    <para>As a result, both
chapters/12.xml:    <valsi>seljdasku</valsi> and
chapters/12.xml-    <valsi>jdaselsku</valsi> belong to the second class of anomalous lujvo: the veljvo doesn't really supply all that the lujvo requires.</para>
chapters/12.xml-    <para>Another example of this kind of anomalous lujvo, drawn from the tanru lists in
chapters/12.xml-
*********************************************************************** selkanla
chapters/12.xml-    <para>What is happening here is that we are translating the tertau wrongly, under the influence of English. The English suffix
chapters/12.xml-    <quote>-eyed</quote> does not mean
chapters/12.xml-    <quote>eye</quote>, but someone with an eye, which is
chapters/12.xml:    <valsi>selkanla</valsi>.</para>
chapters/12.xml-    <para>Because we've got the wrong tertau (eliding a
chapters/12.xml-    <valsi>se</valsi> that really should be there), any attempt to accommodate the resulting lujvo into our guidelines for place structure is fitting a square peg in a round hole. Since they can be so misleading, lujvo with SE rafsi elided from the tertau should be avoided in favor of their more explicit counterparts: in this case,
chapters/12.xml:    <valsi>blaselkanla</valsi>.</para>
chapters/12.xml-  </section>
chapters/12.xml-  <section xml:id="section-eliding-ke-kehe">
chapters/12.xml-    <title>Eliding KE and KEhE rafsi from lujvo</title>
*********************************************************************** selkemdzukla
chapters/12.xml-    <valsi>seldzukla</valsi>, which would represent the veljvo
chapters/12.xml-    <jbophrase>selcadzu klama</jbophrase> and plausibly mean something like
chapters/12.xml-    <quote>to go to a walking surface</quote>. Instead, we would need
chapters/12.xml:    <valsi>selkemdzukla</valsi>, with an explicit rafsi for
chapters/12.xml-    <valsi>ke</valsi>. Similarly,
chapters/12.xml-    <valsi>nalbrablo</valsi> (from
chapters/12.xml-    <jbophrase>na'e barda bloti</jbophrase>) means
*********************************************************************** selklamau
chapters/12.xml-      <para>
chapters/12.xml-      <valsi>klamau</valsi>: z1, more than z2, goes to k2 from k3 via k4 by means of k5</para>
chapters/12.xml-      <para>
chapters/12.xml:      <valsi>selklamau</valsi>: z1, more than z2, is gone to by k1 from k3 via k4 by means of k5</para>
chapters/12.xml-      <para>
chapters/12.xml-      <valsi>terklamau</valsi>: z1, more than z2, is an origin point from destination k2 for k1's going via k4 by means of k5</para>
chapters/12.xml-    </example>
*********************************************************************** selnelcymau
chapters/12.xml-      <para>
chapters/12.xml-      <valsi>nelcymau</valsi>: z1, more than z2, likes n2 by amount z4</para>
chapters/12.xml-      <para>
chapters/12.xml:      <valsi>selnelcymau</valsi>: z1, more than z2, is liked by n1 in amount z4</para>
chapters/12.xml-      <para>
chapters/12.xml-      <valsi>klamau</valsi>: z1, more than z2, goes to k2 from k3 via k4 by means of k5</para>
chapters/12.xml-      <para>
*********************************************************************** selselgekmau
chapters/12.xml-    <quote>making people happier than, more enjoyable than, more of a 'se gleki' than</quote>. If something is less enjoyable than something else, we can say it is
chapters/12.xml-    <jbophrase>se selgekmau</jbophrase>.</para>
chapters/12.xml-    <para>But we can also say it is
chapters/12.xml:    <valsi>selselgekmau</valsi>. Two
chapters/12.xml-    <valsi>se</valsi> cmavo in a row cancel each other (
chapters/12.xml-    <jbophrase>se se gleki</jbophrase> means the same as just
chapters/12.xml-    <valsi>gleki</valsi>), so there would be no good reason to have
*********************************************************************** selseljdasku
chapters/12.xml-    </example>
chapters/12.xml-    <para role="noindent">which, according to the rule expressed in
chapters/12.xml-    <xref linkend="section-seltau-SE"/>, can be further expressed as
chapters/12.xml:    <valsi>selseljdasku</valsi>. However, there is no need for the ugly
chapters/12.xml-    <jbophrase>selsel-</jbophrase> prefix just to get the rules right:
chapters/12.xml-    <valsi>jdaselsku</valsi> is a reasonable, if anomalous, lujvo.</para>
chapters/12.xml-    <para>However, there is a further problem with
*********************************************************************** selti'i
chapters/12.xml-    </example>
chapters/12.xml-    <para role="indent"> <indexterm type="general"><primary>lined up</primary></indexterm> This lujvo does not fit any of our existing molds: it is the second seltau place, st2, that is equivalent to one of the tertau places, namely f1. However, if we understand
chapters/12.xml-    <valsi>ti'ifla</valsi> as an abbreviation for the lujvo
chapters/12.xml:    <valsi>selti'ifla</valsi>, then we get the first places of seltau and tertau lined up. The place structure of
chapters/12.xml-
chapters/12.xml:    <valsi>selti'i</valsi> is:</para>
chapters/12.xml-    <example xml:id="example-random-id-j98h">
chapters/12.xml-      <title>
chapters/12.xml-        <anchor xml:id="c12e9d2"/>
chapters/12.xml-      </title>
chapters/12.xml-      <para>
chapters/12.xml:      <valsi>selti'i</valsi>: idea/action se1 is suggested by agent se2 to audience se3</para>
chapters/12.xml-    </example>
chapters/12.xml-    <para role="indent">Here we can see that se1 (what is suggested) is equivalent to f1 (the law), and we get a normal symmetrical lujvo. The final place structure is:</para>
chapters/12.xml-
--
chapters/12.xml-    <para role="noindent">where the last place (st3) is probably some sort of legislature.</para>
chapters/12.xml-    <para> <indexterm type="general"><primary>lujvo</primary><secondary>abbreviated</secondary></indexterm> Abbreviated lujvo like
chapters/12.xml-    <valsi>ti'ifla</valsi> are more intuitive (for the lujvo-maker) than their more explicit counterparts like
chapters/12.xml:    <valsi>selti'ifla</valsi> (as well as shorter). They don't require the coiner to sit down and work out the precise relation between the seltau and the tertau: he or she can just rattle off a rafsi pair. But should the lujvo get to the stage where a place structure needs to be worked out, then the precise relation does need to be specified. And in that case, such abbreviated lujvo form a trap in lujvo place ordering, since they obscure the most straightforward relation between the seltau and tertau. To give our lujvo-making guidelines as wide an application as possible, and to encourage analyzing the seltau-tertau relation in lujvo, lujvo like
chapters/12.xml-
chapters/12.xml-
chapters/12.xml-
*********************************************************************** selzda
chapters/12.xml-    <xref linkend="section-lujvo-meanings"/>, where we learned that the g1 place was equivalent to the z2 place. In order to get the places aligned, we could convert
chapters/12.xml-    <valsi>zdani</valsi> to
chapters/12.xml-    <jbophrase>se zdani</jbophrase> (or
chapters/12.xml:    <valsi>selzda</valsi> when expressed as a lujvo). The place structure of
chapters/12.xml:    <valsi>selzda</valsi> is</para>
chapters/12.xml-    <example xml:id="example-random-id-IXoj">
chapters/12.xml-      <title>
chapters/12.xml-        <anchor xml:id="c12e5d5"/>
--
chapters/12.xml-      <para><definition><content>s1 is housed by nest s2</content></definition></para>
chapters/12.xml-    </example>
chapters/12.xml-    <para role="noindent">and so the three-part lujvo
chapters/12.xml:    <valsi>gerselzda</valsi> would have the place structure</para>
chapters/12.xml-    <example xml:id="example-random-id-KqE4">
chapters/12.xml-      <title>
chapters/12.xml-        <anchor xml:id="c12e5d6"/>
--
chapters/12.xml-      <para><definition><content>s1=g1 is a dog housed in nest s2 of dog breed g2</content></definition></para>
chapters/12.xml-    </example>
chapters/12.xml-    <para role="indent">However, although
chapters/12.xml:    <valsi>gerselzda</valsi> is a valid lujvo, it doesn't translate
chapters/12.xml-    <quote>doghouse</quote>; its first place is the dog, not the doghouse. Furthermore, it is more complicated than necessary;
chapters/12.xml-    <valsi>gerzda</valsi> is simpler than
chapters/12.xml:    <valsi>gerselzda</valsi>.</para>
chapters/12.xml-    <para>From the reader's or listener's point of view, it may not always be obvious whether a newly met lujvo is symmetrical or asymmetrical, and if the latter, what kind of asymmetrical lujvo. If the place structure of the lujvo isn't given in a dictionary or elsewhere, then plausibility must be applied, just as in interpreting tanru.</para>
chapters/12.xml-
chapters/12.xml-    <para>
*********************************************************************** sikcurnu
chapters/05.xml-            <td>Chi</td>
chapters/05.xml-          </tr>
chapters/05.xml-          <tr>
chapters/05.xml:            <td><jbophrase>sikcurnu silka</jbophrase></td>
chapters/05.xml-            <td>silkworm silk</td>
chapters/05.xml-            <td>Chi</td>
chapters/05.xml-          </tr>
--
chapters/05.xml-    </informaltable>
chapters/05.xml-    <variablelist>
chapters/05.xml-      <varlistentry>
chapters/05.xml:        <term><valsi>sikcurnu</valsi></term>
chapters/05.xml-        <listitem><para>silk-worm</para></listitem>
chapters/05.xml-      </varlistentry>
chapters/05.xml-      <varlistentry>
*********************************************************************** soidji
chapters/12.xml-      <para><definition><content>ni1 is the amount of k1's coming/going to k2 from k3 via route k4 by means k5, measured on scale ni2.</content></definition></para>
chapters/12.xml-    </example>
chapters/12.xml-    <para role="indent">It is not uncommon for abstractors to participate in the making of more complex lujvo as well. For example,
chapters/12.xml:    <valsi>nunsoidji</valsi>, from the veljvo</para>
chapters/12.xml-    <example role="interlinear-gloss-example" xml:id="example-random-id-RKcH">
chapters/12.xml-      <title>
chapters/12.xml-        <anchor xml:id="c12e12d4"/>
--
chapters/12.xml-    <para role="noindent">where the d2 place has disappeared altogether, being replaced by the places of the seltau. As shown in
chapters/12.xml-    <xref linkend="example-random-id-8Nos"/>, the ordering follows this idea of replacement: the seltau places are inserted at the point where the omitted abstraction place exists in the tertau.</para>
chapters/12.xml-    <para>The lujvo
chapters/12.xml:    <valsi>nunsoidji</valsi> is quite different from the ordinary asymmetric lujvo
chapters/12.xml-
chapters/12.xml:    <valsi>soidji</valsi>, a
chapters/12.xml-    <quote>soldier desirer</quote>, whose place structure is just</para>
chapters/12.xml-    <example xml:id="example-random-id-2VMP">
chapters/12.xml-      <title>
--
chapters/12.xml-      <para><definition><content>d1 desires (a soldier of army s2) for purpose d3</content></definition></para>
chapters/12.xml-    </example>
chapters/12.xml-    <para role="indent">A
chapters/12.xml:    <valsi>nunsoidji</valsi> might be someone who is about to enlist, whereas a
chapters/12.xml:    <valsi>soidji</valsi> might be a camp-follower.</para>
chapters/12.xml-    <para>One use of abstract lujvo is to eliminate the need for explicit
chapters/12.xml-
chapters/12.xml-    <valsi>kei</valsi> in tanru:
*********************************************************************** spatrkoka
chapters/05.xml-            <td>Chi</td>
chapters/05.xml-          </tr>
chapters/05.xml-          <tr>
chapters/05.xml:            <td><jbophrase>spatrkoka lanka</jbophrase></td>
chapters/05.xml-            <td>coca basket</td>
chapters/05.xml-            <td>Que</td>
chapters/05.xml-          </tr>
--
chapters/05.xml-    </informaltable>
chapters/05.xml-    <variablelist>
chapters/05.xml-      <varlistentry>
chapters/05.xml:        <term><valsi>spatrkoka</valsi></term>
chapters/05.xml-        <listitem><para>fu'ivla for <quote>coca</quote></para></listitem>
chapters/05.xml-      </varlistentry>
chapters/05.xml-      <varlistentry>
*********************************************************************** spraile
chapters/04.xml-    <orderedlist>
chapters/04.xml-      <listitem>
chapters/04.xml-        <para> <indexterm type="general"><primary>fu'ivla</primary><secondary>initial consonant cluster in</secondary></indexterm>  <indexterm type="general"><primary>fu'ivla</primary><secondary>rules for formation of</secondary></indexterm> must contain a consonant cluster in the first five letters of the word; if this consonant cluster is at the beginning, it must either be a permissible initial consonant pair, or a longer cluster such that each pair of adjacent consonants in the cluster is a permissible initial consonant pair:
chapters/04.xml:        <valsi>spraile</valsi> is acceptable, but not
chapters/04.xml-        <valsi valid="false">ktraile</valsi> or
chapters/04.xml-        <valsi valid="false">trkaile</valsi>;</para>
chapters/04.xml-      </listitem>
*********************************************************************** tarmrnintegrale
chapters/04.xml-    <quote>integral</quote> might be conveyed with
chapters/04.xml-
chapters/04.xml-    <valsi>djinrnintegrale</valsi> or
chapters/04.xml:    <valsi>tarmrnintegrale</valsi>, where
chapters/04.xml-    <valsi>dinju</valsi> and
chapters/04.xml-    <valsi>tarmi</valsi> mean
chapters/04.xml-    <quote>building</quote> and
*********************************************************************** terci'e
chapters/18.xml-        <listitem><definition><content>x1 is approximately equal to x2 [<valsi>namcu</valsi> <valsi>jibni</valsi>, number-near]</content></definition></listitem>
chapters/18.xml-      </varlistentry>
chapters/18.xml-      <varlistentry>
chapters/18.xml:        <term><valsi>terci'e</valsi></term>
chapters/18.xml-        <listitem><definition><content>x1 is a component with function x2 of system x3</content></definition></listitem>
chapters/18.xml-      </varlistentry>
chapters/18.xml-    </variablelist>
*********************************************************************** tergusni
chapters/05.xml-            <td>tombstone</td>
chapters/05.xml-          </tr>
chapters/05.xml-          <tr>
chapters/05.xml:            <td><jbophrase>jubme tergusni</jbophrase></td>
chapters/05.xml-            <td>table lamp</td>
chapters/05.xml-            <td>Chi</td>
chapters/05.xml-          </tr>
--
chapters/05.xml-    <para> <indexterm type="general"><primary>asymmetrical tanru types</primary><secondary>energy-source + powered</secondary></indexterm> The seltau specifies a source of energy for the referent of the tertau.</para>
chapters/05.xml-    <informaltable>
chapters/05.xml-          <tr>
chapters/05.xml:            <td><jbophrase>dikca tergusni</jbophrase></td>
chapters/05.xml-            <td>electric lamp</td>
chapters/05.xml-            <td>Chi</td>
chapters/05.xml-          </tr>
--
chapters/05.xml-    </informaltable>
chapters/05.xml-    <variablelist>
chapters/05.xml-      <varlistentry>
chapters/05.xml:        <term><valsi>tergusni</valsi></term>
chapters/05.xml-        <listitem><para>illumination-source</para></listitem>
chapters/05.xml-      </varlistentry>
chapters/05.xml-    </variablelist>
*********************************************************************** terkakpa
chapters/05.xml-            <td>Chi</td>
chapters/05.xml-          </tr>
chapters/05.xml-          <tr>
chapters/05.xml:            <td><jbophrase>kolme terkakpa</jbophrase></td>
chapters/05.xml-            <td>coal mine</td>
chapters/05.xml-            <td>Chi</td>
chapters/05.xml-          </tr>
--
chapters/05.xml-    </informaltable>
chapters/05.xml-    <variablelist>
chapters/05.xml-      <varlistentry>
chapters/05.xml:        <term><valsi>terkakpa</valsi></term>
chapters/05.xml-        <listitem><para>source of digging</para></listitem>
chapters/05.xml-      </varlistentry>
chapters/05.xml-    </variablelist>
*********************************************************************** terklamau
chapters/12.xml-      <para>
chapters/12.xml-      <valsi>selklamau</valsi>: z1, more than z2, is gone to by k1 from k3 via k4 by means of k5</para>
chapters/12.xml-      <para>
chapters/12.xml:      <valsi>terklamau</valsi>: z1, more than z2, is an origin point from destination k2 for k1's going via k4 by means of k5</para>
chapters/12.xml-    </example>
chapters/12.xml-    <para role="noindent">(See
chapters/12.xml-    <xref linkend="chapter-abstractions"/> for the way in which this problem is resolved when lujvo aren't used.)</para>
*********************************************************************** terlantroge'u
chapters/12.xml-    <valsi>lanme</valsi> and
chapters/12.xml-    <valsi>gerku</valsi> at all. Rather, the lujvo refers to a dog which controls sheep flocks, a
chapters/12.xml-    <jbophrase>terlanme jitro gerku</jbophrase>, the lujvo from which is
chapters/12.xml:    <valsi>terlantroge'u</valsi> with place structure:</para>
chapters/12.xml-    <example xml:id="example-random-id-TW5Q">
chapters/12.xml-      <title>
chapters/12.xml-        <anchor xml:id="c12e14d5"/>
--
chapters/12.xml-    <valsi>gerku</valsi>, but
chapters/12.xml-    <valsi>lantro</valsi> is itself an asymmetrical lujvo. The l2 place, the breed of sheep, is removed as dependent on l1. However, the lujvo
chapters/12.xml-    <valsi>lange'u</valsi> is both shorter than
chapters/12.xml:    <valsi>terlantroge'u</valsi> and sufficiently clear to warrant its use: its place structure, however, should be the same as that of the longer lujvo, for which
chapters/12.xml-    <valsi>lange'u</valsi> can be understood as an abbreviation.</para>
chapters/12.xml-    <para>Another example is
chapters/12.xml-    <valsi>xanmi'e</valsi>,
--
chapters/12.xml-    <valsi>xanmi'e</valsi>, the gismu
chapters/12.xml-    <valsi>pilno</valsi>, which is not explicit in the veljvo. And it also means that, for a place structure derivation that actually makes sense, rather than being ad-hoc, the Lojbanist should probably go through a derivation for
chapters/12.xml-    <valsi>xancypliminde</valsi> or one of the other possibilities that is analogous to the analysis of
chapters/12.xml:    <valsi>terlantroge'u</valsi> above, even if he or she decides to stick with a shorter, more convenient form like
chapters/12.xml-    <valsi>xanmi'e</valsi>. In addition, of course, the possibilities of elliptical lujvo increase their potential ambiguity enormously &ndash; an unavoidable fact which should be borne in mind.</para>
chapters/12.xml-  </section>
chapters/12.xml-  <section xml:id="section-comparatives">
*********************************************************************** ti'ifla
chapters/12.xml-    <title>Eliding SE rafsi from seltau</title>
chapters/12.xml-    <para> <indexterm type="general"><primary>lujvo</primary><secondary>dropping SE rafsi</secondary></indexterm> It is common to form lujvo that omit the rafsi based on cmavo of selma'o SE, as well as other cmavo rafsi. Doing so makes lujvo construction for common or useful constructions shorter. Since it puts more strain on the listener who has not heard the lujvo before, the shortness of the word should not necessarily outweigh ease in understanding, especially if the lujvo refers to a rare or unusual concept.</para>
chapters/12.xml-    <para> <indexterm type="general"><primary>proposed law</primary></indexterm> Consider as an example the lujvo
chapters/12.xml:    <valsi>ti'ifla</valsi>, from the veljvo
chapters/12.xml-    <jbophrase>stidi flalu</jbophrase>, and meaning
chapters/12.xml-    <quote>bill, proposed law</quote>. The gismu place structures are:</para>
chapters/12.xml-
--
chapters/12.xml-      <para>by lawgiver f5</para>
chapters/12.xml-    </example>
chapters/12.xml-    <para role="indent"> <indexterm type="general"><primary>lined up</primary></indexterm> This lujvo does not fit any of our existing molds: it is the second seltau place, st2, that is equivalent to one of the tertau places, namely f1. However, if we understand
chapters/12.xml:    <valsi>ti'ifla</valsi> as an abbreviation for the lujvo
chapters/12.xml:    <valsi>selti'ifla</valsi>, then we get the first places of seltau and tertau lined up. The place structure of
chapters/12.xml-
chapters/12.xml-    <valsi>selti'i</valsi> is:</para>
chapters/12.xml-    <example xml:id="example-random-id-j98h">
--
chapters/12.xml-    </example>
chapters/12.xml-    <para role="noindent">where the last place (st3) is probably some sort of legislature.</para>
chapters/12.xml-    <para> <indexterm type="general"><primary>lujvo</primary><secondary>abbreviated</secondary></indexterm> Abbreviated lujvo like
chapters/12.xml:    <valsi>ti'ifla</valsi> are more intuitive (for the lujvo-maker) than their more explicit counterparts like
chapters/12.xml:    <valsi>selti'ifla</valsi> (as well as shorter). They don't require the coiner to sit down and work out the precise relation between the seltau and the tertau: he or she can just rattle off a rafsi pair. But should the lujvo get to the stage where a place structure needs to be worked out, then the precise relation does need to be specified. And in that case, such abbreviated lujvo form a trap in lujvo place ordering, since they obscure the most straightforward relation between the seltau and tertau. To give our lujvo-making guidelines as wide an application as possible, and to encourage analyzing the seltau-tertau relation in lujvo, lujvo like
chapters/12.xml-
chapters/12.xml-
chapters/12.xml-
chapters/12.xml-
chapters/12.xml-
chapters/12.xml:    <valsi>ti'ifla</valsi> are given the place structure they would have with the appropriate SE added to the seltau.</para>
chapters/12.xml-    <para> <indexterm type="general"><primary>plausibility</primary><secondary>in abbreviated lujvo</secondary></indexterm>  <indexterm type="general"><primary>abbreviated lujvo and plausibility</primary></indexterm>  <indexterm type="general"><primary>implausible</primary></indexterm> Note that, with these lujvo, an interpretation requiring SE insertion is safe only if the alternatives are either implausible or unlikely to be needed as a lujvo. This may not always be the case, and Lojbanists should be aware of the risk of ambiguity.</para>
chapters/12.xml-
chapters/12.xml-  </section>
*********************************************************************** tricrxaceru
chapters/04.xml-    <quote>maple sugar</quote> could get the fu'ivla
chapters/04.xml-
chapters/04.xml-    <valsi>saktrxaceru</valsi>, or could be represented by the tanru
chapters/04.xml:    <jbophrase>tricrxaceru sakta</jbophrase>. Technically,
chapters/04.xml-    <valsi>ricrxaceru</valsi> and
chapters/04.xml:    <valsi>tricrxaceru</valsi> are distinct fu'ivla, but they would surely be given the same meanings if both happened to be in use.</para>
chapters/04.xml-    <example role="lojbanization-example" xml:id="example-random-id-C0YS">
chapters/04.xml-      <title>
chapters/04.xml-
*********************************************************************** turdu'i
chapters/18.xml-      </varlistentry>
chapters/18.xml-
chapters/18.xml-      <varlistentry>
chapters/18.xml:        <term><valsi>turdu'i</valsi></term>
chapters/18.xml-        <listitem><definition><content>x1 is isomorphic to x2 [<valsi>stura</valsi> <valsi>dunli</valsi>, structure-equal]</content></definition></listitem>
chapters/18.xml-      </varlistentry>
chapters/18.xml-
*********************************************************************** velmikce
chapters/05.xml-    <para> <indexterm type="general"><primary>asymmetrical tanru types</primary><secondary>locus-of-application + object</secondary></indexterm> The seltau specifies the locus of application of the tertau.</para>
chapters/05.xml-    <informaltable>
chapters/05.xml-          <tr>
chapters/05.xml:            <td><jbophrase>kanla velmikce</jbophrase></td>
chapters/05.xml-            <td>eye medicine</td>
chapters/05.xml-            <td>Chi</td>
chapters/05.xml-          </tr>
--
chapters/05.xml-    </informaltable>
chapters/05.xml-    <variablelist>
chapters/05.xml-      <varlistentry>
chapters/05.xml:        <term><valsi>velmikce</valsi></term>
chapters/05.xml-        <listitem><para>treatment used by doctor</para></listitem>
chapters/05.xml-      </varlistentry>
chapters/05.xml-    </variablelist>
*********************************************************************** xancypliminde
chapters/12.xml-
chapters/12.xml-    <valsi>xanmi'e</valsi>, the gismu
chapters/12.xml-    <valsi>pilno</valsi>, which is not explicit in the veljvo. And it also means that, for a place structure derivation that actually makes sense, rather than being ad-hoc, the Lojbanist should probably go through a derivation for
chapters/12.xml:    <valsi>xancypliminde</valsi> or one of the other possibilities that is analogous to the analysis of
chapters/12.xml-    <valsi>terlantroge'u</valsi> above, even if he or she decides to stick with a shorter, more convenient form like
chapters/12.xml-    <valsi>xanmi'e</valsi>. In addition, of course, the possibilities of elliptical lujvo increase their potential ambiguity enormously &ndash; an unavoidable fact which should be borne in mind.</para>
chapters/12.xml-  </section>
*********************************************************************** xanmi'e
chapters/12.xml-    <valsi>terlantroge'u</valsi> and sufficiently clear to warrant its use: its place structure, however, should be the same as that of the longer lujvo, for which
chapters/12.xml-    <valsi>lange'u</valsi> can be understood as an abbreviation.</para>
chapters/12.xml-    <para>Another example is
chapters/12.xml:    <valsi>xanmi'e</valsi>,
chapters/12.xml-    <quote>to command by hand, to beckon</quote>. The component place structures are:</para>
chapters/12.xml-
chapters/12.xml-    <example xml:id="example-random-id-VjbP">
--
chapters/12.xml-    </example>
chapters/12.xml-    <para role="indent">The relation between the seltau and tertau is close enough for there to be an overlap: xa2 (the person with the hand) is the same as m1 (the one who commands). But interpreting
chapters/12.xml-
chapters/12.xml:    <valsi>xanmi'e</valsi> as a symmetrical lujvo with an elided
chapters/12.xml-    <jbophrase>sel-</jbophrase> in the seltau, as if from
chapters/12.xml-    <jbophrase>se xance minde</jbophrase>, misses the point: the real relation expressed by the lujvo is not just
chapters/12.xml-    <quote>one who commands and has a hand</quote>, but
--
chapters/12.xml-    <valsi>mi'erxanpli</valsi>, and
chapters/12.xml-    <valsi>minkemxanpli</valsi> respectively.</para>
chapters/12.xml-    <para> <indexterm type="general"><primary>latent component</primary></indexterm> Does this make
chapters/12.xml:    <valsi>xanmi'e</valsi> wrong? By no means. But it does mean that there is a latent component to the meaning of
chapters/12.xml-
chapters/12.xml:    <valsi>xanmi'e</valsi>, the gismu
chapters/12.xml-    <valsi>pilno</valsi>, which is not explicit in the veljvo. And it also means that, for a place structure derivation that actually makes sense, rather than being ad-hoc, the Lojbanist should probably go through a derivation for
chapters/12.xml-    <valsi>xancypliminde</valsi> or one of the other possibilities that is analogous to the analysis of
chapters/12.xml-    <valsi>terlantroge'u</valsi> above, even if he or she decides to stick with a shorter, more convenient form like
chapters/12.xml:    <valsi>xanmi'e</valsi>. In addition, of course, the possibilities of elliptical lujvo increase their potential ambiguity enormously &ndash; an unavoidable fact which should be borne in mind.</para>
chapters/12.xml-  </section>
chapters/12.xml-  <section xml:id="section-comparatives">
chapters/12.xml-    <title>Comparatives and superlatives</title>
*********************************************************************** xanplimi'e
chapters/12.xml-      </interlinear-gloss>
chapters/12.xml-    </example>
chapters/12.xml-    <para role="noindent">which lead to the three different lujvo
chapters/12.xml:    <valsi>xanplimi'e</valsi>,
chapters/12.xml-    <valsi>mi'erxanpli</valsi>, and
chapters/12.xml-    <valsi>minkemxanpli</valsi> respectively.</para>
chapters/12.xml-    <para> <indexterm type="general"><primary>latent component</primary></indexterm> Does this make
*********************************************************************** xaskemcakcurnu
chapters/12.xml-
chapters/12.xml-
chapters/12.xml-  <indexterm type="general"><primary>shellfish</primary></indexterm> There are cases, however, where omitting a KE or KEhE rafsi can produce another lujvo, equally useful. For example,
chapters/12.xml:    <valsi>xaskemcakcurnu</valsi> means
chapters/12.xml-    <quote>oceanic shellfish</quote>, and has the veljvo</para>
chapters/12.xml-
chapters/12.xml-    <example role="interlinear-gloss-example" xml:id="example-random-id-0W5t">
*********************************************************************** xasycakcurnu
chapters/12.xml-    <para role="noindent"> <indexterm type="general"><primary>invertebrate</primary></indexterm> (
chapters/12.xml-    <quote>worm</quote> in Lojban refers to any invertebrate), but
chapters/12.xml-
chapters/12.xml:    <valsi>xasycakcurnu</valsi> has the veljvo</para>
chapters/12.xml-
chapters/12.xml-    <example role="interlinear-gloss-example" xml:id="example-random-id-HEjn">
chapters/12.xml-      <title>
*********************************************************************** xelklama
chapters/10.xml-        <indexterm type="example"><primary>boat sailed</primary></indexterm>
chapters/10.xml-      </title>
chapters/10.xml-      <interlinear-gloss>
chapters/10.xml:        <jbo>le bloti pu za'o xelklama</jbo>
chapters/10.xml-        <gloss>The boat [past] [superfective] is-a-transport-mechanism</gloss>
chapters/10.xml-      </interlinear-gloss>
chapters/10.xml-      <interlinear-gloss>
--
chapters/10.xml-      </interlinear-gloss>
chapters/10.xml-    </example>
chapters/10.xml-    <para role="indent">Probably it sailed up onto the dock. One point of clarification: although
chapters/10.xml:    <valsi>xelklama</valsi> appears to mean simply
chapters/10.xml-    <quote>is-a-mode-of-transport</quote>, it does not &ndash; the bridi of
chapters/10.xml-    <xref linkend="example-random-id-PABV"/> has four omitted arguments, and thus has the (physical) journey which goes on too long as part of its meaning.</para>
chapters/10.xml-
*********************************************************************** zilpavypinxe
chapters/07.xml-    <jbophrase>se pinxe be zi'o</jbophrase>, the lujvo corresponding to this is
chapters/07.xml-    <valsi>zilrelselpinxe</valsi> (deleting the second place of
chapters/07.xml-    <jbophrase>se pinxe</jbophrase>). Deleting the x1 place in this fashion would move all remaining places up by one. This would mean that
chapters/07.xml:    <valsi>zilpavypinxe</valsi> has the same place structure as
chapters/07.xml-    <valsi>zilrelselpinxe</valsi>, and
chapters/07.xml:    <jbophrase>lo zilpavypinxe</jbophrase>, like
chapters/07.xml-    <jbophrase>lo zilrelselpinxe</jbophrase>, refers to a beverage, and not to a non-existent drinker.</para>
chapters/07.xml-
chapters/07.xml-    <para> <indexterm type="general"><primary>pro-bridi rafsi</primary><secondary>as producing context-dependent meanings</secondary></indexterm> The pro-bridi
*********************************************************************** zilrelselpinxe
chapters/07.xml-
chapters/07.xml-
chapters/07.xml-    <jbophrase>se pinxe be zi'o</jbophrase>, the lujvo corresponding to this is
chapters/07.xml:    <valsi>zilrelselpinxe</valsi> (deleting the second place of
chapters/07.xml-    <jbophrase>se pinxe</jbophrase>). Deleting the x1 place in this fashion would move all remaining places up by one. This would mean that
chapters/07.xml-    <valsi>zilpavypinxe</valsi> has the same place structure as
chapters/07.xml:    <valsi>zilrelselpinxe</valsi>, and
chapters/07.xml-    <jbophrase>lo zilpavypinxe</jbophrase>, like
chapters/07.xml:    <jbophrase>lo zilrelselpinxe</jbophrase>, refers to a beverage, and not to a non-existent drinker.</para>
chapters/07.xml-
chapters/07.xml-    <para> <indexterm type="general"><primary>pro-bridi rafsi</primary><secondary>as producing context-dependent meanings</secondary></indexterm> The pro-bridi
chapters/07.xml-    <valsi>co'e</valsi>,
*********************************************************************** zuljamfu
chapters/04.xml-    <para>The lujvo forms
chapters/04.xml-    <valsi>zunlyjamfu</valsi>,
chapters/04.xml-    <valsi>zunlyjma</valsi>,
chapters/04.xml:    <valsi>zuljamfu</valsi>, and
chapters/04.xml-    <valsi>zuljma</valsi> are all legitimate and equivalent forms made from the tanru
chapters/04.xml-    <jbophrase>zunle jamfu</jbophrase> (
chapters/04.xml-    <quote>left foot</quote>). Of these,
*********************************************************************** zunlyjamfu
chapters/04.xml-    <xref linkend="example-random-id-qj84"/> to
chapters/04.xml-    <xref linkend="example-random-id-qjbP"/>.)</para>
chapters/04.xml-    <para>The lujvo forms
chapters/04.xml:    <valsi>zunlyjamfu</valsi>,
chapters/04.xml-    <valsi>zunlyjma</valsi>,
chapters/04.xml-    <valsi>zuljamfu</valsi>, and
chapters/04.xml-    <valsi>zuljma</valsi> are all legitimate and equivalent forms made from the tanru
*********************************************************************** zunlyjma
chapters/04.xml-    <xref linkend="example-random-id-qjbP"/>.)</para>
chapters/04.xml-    <para>The lujvo forms
chapters/04.xml-    <valsi>zunlyjamfu</valsi>,
chapters/04.xml:    <valsi>zunlyjma</valsi>,
chapters/04.xml-    <valsi>zuljamfu</valsi>, and
chapters/04.xml-    <valsi>zuljma</valsi> are all legitimate and equivalent forms made from the tanru
chapters/04.xml-    <jbophrase>zunle jamfu</jbophrase> (

-- 
http://intelligence.org/ :  Our last, best hope for a fantastic future.
.i ko na cpedu lo nu stidi vau loi jbopre .i dafsku lu na go'i li'u .e
lu go'i li'u .i ji'a go'i lu na'e go'i li'u .e lu go'i na'i li'u .e
lu no'e go'i li'u .e lu to'e go'i li'u .e lu lo mamta be do cu sofybakni li'u

-- 
You received this message because you are subscribed to the Google Groups "lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lojban+unsubscribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at http://groups.google.com/group/lojban.
For more options, visit https://groups.google.com/d/optout.