Received: from mail-qg0-f62.google.com ([209.85.192.62]:34322) by stodi.digitalkingdom.org with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.85) (envelope-from ) id 1ZRYn5-00046q-3U for lojban-list-archive@lojban.org; Mon, 17 Aug 2015 21:46:35 -0700 Received: by qgey105 with SMTP id y105sf38960181qge.1 for ; Mon, 17 Aug 2015 21:46:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=date:from:to:subject:message-id:mail-followup-to:mime-version :content-type:content-disposition:user-agent:x-original-sender :x-original-authentication-results:reply-to :content-transfer-encoding:precedence:mailing-list:list-id :x-spam-checked-in-group:list-post:list-help:list-archive:sender :list-subscribe:list-unsubscribe; bh=+yw+kPhEVz+CDPIXbBs3mMKDj/QlpYPieUSMmIXCCSw=; b=AfToT0HOHfbOG5s98aZ008viTaHfTcb4xtJEErsAHJv+JjMrJNJ+2SuTF4xKxRJ/hi lUEqD6gvyg0HEE2x+GOz8PCLFzpLMrjdpHRDA8zsGmdyTXMixezTOvzQAJtEnc+IMZ6W gjJWnKJJoS99g6NR+JXsJXfXKoH3LN9NDxCp1YKBJLx5AoHOd6aC8PBiiesGInsoJgnq 7/sBIqvukqc2BRcjmzqaBrwhT+69p/eZOZtB4IUa3+0bTWRF5e7LoU0Lsv21nwKG09eP oGxEz8glDQsAo6qDvXCwitZ+oP/6ItwYvMu9V1p/FEz8XJVoxec5SnPeMylnEO5nG9kw O74A== X-Received: by 10.140.22.113 with SMTP id 104mr55207qgm.11.1439873181128; Mon, 17 Aug 2015 21:46:21 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.140.25.131 with SMTP id 3ls1131503qgt.12.gmail; Mon, 17 Aug 2015 21:46:20 -0700 (PDT) X-Received: by 10.129.135.7 with SMTP id x7mr4291461ywf.38.1439873180351; Mon, 17 Aug 2015 21:46:20 -0700 (PDT) Received: from stodi.digitalkingdom.org (mail.digitalkingdom.org. [173.13.139.236]) by gmr-mx.google.com with ESMTPS id zg3si1782524pbc.1.2015.08.17.21.46.20 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 17 Aug 2015 21:46:20 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of rlpowell@digitalkingdom.org designates 173.13.139.236 as permitted sender) client-ip=173.13.139.236; Received: from rlpowell by stodi.digitalkingdom.org with local (Exim 4.85) (envelope-from ) id 1ZRYmx-00046f-3c for lojban@googlegroups.com; Mon, 17 Aug 2015 21:46:19 -0700 Date: Mon, 17 Aug 2015 21:46:19 -0700 From: Robin Lee Powell To: lojban@googlegroups.com Subject: [lojban] CLL help: jbovlaste words, round 2 Message-ID: <20150818044615.GF22026@stodi.digitalkingdom.org> Mail-Followup-To: lojban@googlegroups.com MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) X-Original-Sender: rlpowell@digitalkingdom.org X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: best guess record for domain of rlpowell@digitalkingdom.org designates 173.13.139.236 as permitted sender) smtp.mailfrom=rlpowell@digitalkingdom.org Reply-To: lojban@googlegroups.com Content-Transfer-Encoding: quoted-printable Precedence: list Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com List-ID: X-Spam-Checked-In-Group: lojban@googlegroups.com X-Google-Group-Id: 1004133512417 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -2.1 (--) X-Spam_score: -2.1 X-Spam_score_int: -20 X-Spam_bar: -- 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. *********************************************************************** bis= ycla chapters/04.xml- da'amei must be a compound cmavo= because it lacks a consonant pair; chapters/04.xml- lojban. must be a name because it lacks = a final vowel. chapters/04.xml- consonant p= airsletter y within yletterbetween letters of consonant pair consonant pairsin brivla brivlaconsonant pairs in Thus, chapters/04.xml: bisycla has the consonant pair chapters/04.xml- sc in the first five non- chapters/04.xml- y letters even though the chapters/04.xml- sc actually appears in the for= m of *********************************************************************** blo= lei chapters/04.xml- lo'ikle chapters/04.xml- chapters/04.xml- lotlei chapters/04.xml: blolei chapters/04.xml- lo'irlei chapters/04.xml- chapters/04.xml- Only -- chapters/04.xml- 5867 chapters/04.xml- chapters/04.xml- chapters/04.xml: blolei chapters/04.xml- 5847 chapters/04.xml- chapters/04.xml- -- chapters/04.xml-Logical Language Group= example chapters/04.xml- chapters/04.xml- So the form chapters/04.xml: blolei is preferred, but only by a tiny = margin over chapters/04.xml- blokle; "lotlei" and "lotkle" are only s= lightly worse; chapters/04.xml- lo'ikle suffers because of its apostroph= e, and chapters/04.xml- lo'irlei because of having both apostrop= he and hyphen. *********************************************************************** cal= kyguzme chapters/05.xml- piece of cloth chapters/05.xml- chapters/05.xml- chapters/05.xml: djacu calkyguzme chapters/05.xml- water calabash chapters/05.xml- Ewe chapters/05.xml- calabash of water -- chapters/05.xml- chapters/05.xml- chapters/05.xml- chapters/05.xml: calkyguzme chapters/05.xml- shell-fruit, calabash chapters/05.xml- chapters/05.xml- *********************************************************************** cin= ctu chapters/04.xml- teacher of male sexuality. Here are the = possible forms of the lujvo, both before and after hyphenation: chapters/04.xml- chapters/04.xml- nak-kem-= cin-ctu chapters/04.xml: nakykemcinctu chapters/04.xml- chapters/04.xml- nak-kem-= cin-ctuca chapters/04.xml: nakykemcinctuca chapters/04.xml- chapters/04.xml- nak-kem-= cins-ctu chapters/04.xml- nakykemcinsyctu -- chapters/04.xml- nakykemcinsyctuca chapters/04.xml- chapters/04.xml- nakn-kem= -cin-ctu chapters/04.xml: naknykemcinctu= chapters/04.xml- chapters/04.xml- nakn-kem= -cin-ctuca chapters/04.xml: naknykemcinctuca chapters/04.xml- chapters/04.xml- nakn-kem= -cins-ctu chapters/04.xml- naknykemcinsyctu -- chapters/04.xml- naknykemcinsyctuca chapters/04.xml- chapters/04.xml- gismualgorithm for Of these forms, chapters/04.xml: nakykemcinctu is the shortest and is pre= ferred by the scoring algorithm. On the whole, however, it might be better = to just make a lujvo for chapters/04.xml- cinse ctuca (which would be chapters/04.xml: cinctu) since the sex of the teacher is = rarely important. If there was a reason to specify chapters/04.xml- male, then the simpler tanru chapters/04.xml: nakni cinctu ( chapters/04.xml- male sexual-teacher) would be appropriat= e. This tanru is actually shorter than the four-part lujvo, since the chapters/04.xml- ke required for grouping need not be exp= ressed. chapters/04.xml- *********************************************************************** cma= crnintegrale chapters/04.xml- cmacrntegrale, if the chapters/04.xml- i of chapters/04.xml- integrale is removed, or something like chapters/04.xml: cmacrnintegrale, if a new consonant is a= dded to the beginning; chapters/04.xml- cmac- is the rafsi for chapters/04.xml- cmaci ( chapters/04.xml- mathematics). The architectural sense of *********************************************************************** cma= crntegrale chapters/04.xml-integralarchitectural conceptexample integralma= thematical conceptexample chapters/04.xml- chapters/04.xml-The prefix method would render the mathematical concept as chapters/04.xml: cmacrntegrale, if the chapters/04.xml- i of chapters/04.xml- integrale is removed, or something like chapters/04.xml- cmacrnintegrale, if a new consonant is a= dded to the beginning; *********************************************************************** dji= nrnintegrale chapters/04.xml- mathematics). The architectural sense of chapters/04.xml- integral might be conveyed with chapters/04.xml- chapters/04.xml: djinrnintegrale or chapters/04.xml- tarmrnintegrale, where chapters/04.xml- dinju and chapters/04.xml- tarmi mean *********************************************************************** don= ta'a chapters/07.xml-you-talkexample chapters/07.xml- chapters/07.xml- pro-sumti rafsieffect of on place structure of lujvo lujvopro-sumt= i rafsi effect on place structure of Thus chapters/07.xml: donta'a, meaning chapters/07.xml- you-talk, would be interpreted as chapters/07.xml- tavla be do, and would have the = place structure chapters/07.xml- *********************************************************************** fet= sygau chapters/12.xml- galfi (meaning chapters/12.xml- modify) may be more appropriate for chapters/12.xml- causes to become a liquid. On the other = hand, chapters/12.xml: fetsygau is potentially confusing, becau= se it could mean chapters/12.xml- agent in the event of something becoming female<= /quote> (the implicit-abstraction interpretation) or simply chapters/12.xml- female agent (the parallel interpretatio= n), so using implicit-abstraction lujvo is always accompanied with some ris= k of being misunderstood. chapters/12.xml- *********************************************************************** ge'= urzdani chapters/04.xml- ge'u-zdani, however, req= uires an chapters/04.xml- r-hyphen; otherwise, the chapters/04.xml- ge'u- part would fall off as a cmavo. So= this form of the lujvo is chapters/04.xml: ge'urzdani. chapters/04.xml- 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- gerzdani. chapters/04.xml- The third form, chapters/04.xml- ge'u-zda, needs no hyphen= , because even though the first rafsi is CVV, the second one is CCV, so the= re is a consonant cluster in the first five letters. So chapters/04.xml: ge'uzda is this form of the lujvo. chapters/04.xml- The fourth form, chapters/04.xml- ge'u-zdani, however, req= uires an chapters/04.xml- r-hyphen; otherwise, the *********************************************************************** gek= mau chapters/12.xml- other than a big boat. chapters/12.xml- chapters/12.xml- lujvo creat= ionuse of multiple SE in If th= e lujvo we want to modify with SE has a seltau already starting with a SE r= afsi, we can take a shortcut. For instance, chapters/12.xml: gekmau means chapters/12.xml- happier than, while chapters/12.xml: selgekmau means chapters/12.xml- making people happier than, more enjoyable than,= more of a 'se gleki' than. If something is less enjoyable than som= ething else, we can say it is chapters/12.xml: se selgekmau. chapters/12.xml- But we can also say it is chapters/12.xml: selselgekmau. Two chapters/12.xml- se cmavo in a row cancel each other ( chapters/12.xml- se se gleki means the same as ju= st chapters/12.xml- gleki), so there would be no good reason= to have *********************************************************************** ger= kyzda chapters/04.xml- 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: gerkyzda and chapters/04.xml: gerkyzdani respectively. chapters/04.xml- chapters/04.xml- chapters/04.xml-boat classexample *********************************************************************** ger= kyzdani chapters/04.xml- y-hyphens, as all 4-letter rafsi do, and so are chapters/04.xml- chapters/04.xml- gerkyzda and chapters/04.xml: gerkyzdani respectively. chapters/04.xml- chapters/04.xml- chapters/04.xml-boat classexample *********************************************************************** ger= selzda chapters/12.xml- s1 is housed by nest s2 chapters/12.xml- chapters/12.xml- and so the three-part lujvo chapters/12.xml: gerselzda would have the place structure= chapters/12.xml- chapters/12.xml- chapters/12.xml- <anchor xml:id=3D"c12e5d6"/> -- chapters/12.xml- <para><definition><content>s1=3Dg1 is a dog housed in= nest s2 of dog breed g2</content></definition></para> chapters/12.xml- </example> chapters/12.xml- <para role=3D"indent">However, although chapters/12.xml: <valsi>gerselzda</valsi> is a valid lujvo, it doesn't t= ranslate chapters/12.xml- <quote>doghouse</quote>; its first place is the dog, no= t 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 asym= metrical, 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 plaus= ibility must be applied, just as in interpreting tanru.</para> chapters/12.xml- chapters/12.xml- <para> *********************************************************************** ger= zdani chapters/04.xml- <valsi>ge</valsi> cannot fall off the front, because th= e 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 the= re is a consonant cluster in the first five letters. So chapters/04.xml- <valsi>ge'uzda</valsi> is this form of the lujvo.</para= > *********************************************************************** gic= mu chapters/04.xml- <valsi>gismu</valsi> is in the set of gismu, chapters/04.xml- <valsi valid=3D"false">kismu</valsi>, chapters/04.xml- <valsi valid=3D"false">xismu</valsi>, chapters/04.xml: <valsi valid=3D"false">gicmu</valsi>, chapters/04.xml- <valsi valid=3D"false">gizmu</valsi>, and chapters/04.xml- <valsi valid=3D"false">gisnu</valsi> cannot be.</para> chapters/04.xml- <para> <indexterm type=3D"general"><primary>gismu</prim= ary><secondary>source of</secondary></indexterm> Almost all Lojban gismu ar= e 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 speaker= s 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 provid= e a better rafsi. A few gismu were changed in error as a result of transcri= ption 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 n= ow).</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> *********************************************************************** gri= pau chapters/18.xml- <listitem><definition><content>x1 is a member of se= t 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 se= t x2 [<valsi>girzu</valsi> <valsi>pagbu</valsi>, set-part]</content></defin= ition></listitem> chapters/18.xml- </varlistentry> chapters/18.xml- <varlistentry> *********************************************************************** gru= trceraso chapters/05.xml- <para> <indexterm type=3D"general"><primary>asymmetrica= l tanru types</primary><secondary>similar-appearance-object + object</secon= dary></indexterm> As a particular case (when the property is that of resemb= lance): the seltau specifies an object which the referent of the tanru rese= mbles.</para> chapters/05.xml- <informaltable> chapters/05.xml- <tr> chapters/05.xml: <td><jbophrase>grutrceraso jbama</jbophrase></t= d> 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> b= ased on Linnean name</para></listitem> chapters/05.xml- </varlistentry> chapters/05.xml- </variablelist> *********************************************************************** int= egrale chapters/04.xml- <para> <indexterm type=3D"general"><primary>fu'ivla cat= egorizer</primary><secondary>for distinguishing specialized meanings</secon= dary></indexterm> For another example, chapters/04.xml- <quote>integral</quote> has a specific meaning to a mat= hematician. But the Lojban fu'ivla chapters/04.xml- chapters/04.xml: <valsi>integrale</valsi>, which is a valid Stage 4 fu'i= vla, does not convey that mathematical sense to a non-mathematical listener= , even one with an English-speaking background; its source – the Engl= ish word chapters/04.xml- <quote>integral</quote> – has various other speci= alized meanings in other fields.</para> chapters/04.xml- chapters/04.xml- <para>Left uncontrolled, chapters/04.xml: <valsi>integrale</valsi> almost certainly would eventua= lly come to mean the same collection of loosely related concepts that Engli= sh associates with chapters/04.xml- <quote>integral</quote>, with only the context to indic= ate (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 a= dded 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 *********************************************************************** kam= bla 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 nat= ure, 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=3D"section-seltau-SE"/>.</para> *********************************************************************** kar= cykla 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 k= a3</para> chapters/12.xml- </example> chapters/12.xml- <para role=3D"indent">A asymmetrical interpretation of chapters/12.xml: <valsi>karcykla</valsi> that is strictly analogous to t= he place structure of chapters/12.xml- <valsi>gerzda</valsi>, equating the kl2 (destination) a= nd ka1 (car) places, would lead to the place structure</para> chapters/12.xml- <example xml:id=3D"example-random-id-GgxL"> chapters/12.xml- <title> *********************************************************************** kla= mau 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 like= d by n1 in amount z4</para> chapters/12.xml- <para> chapters/12.xml: <valsi>klamau</valsi>: z1, more than z2, goes to k2 f= rom k3 via k4 by means of k5</para> chapters/12.xml- <para> chapters/12.xml: <valsi>selklamau</valsi>: z1, more than z2, is gone t= o 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 ori= gin point from destination k2 for k1's going via k4 by means of k5</para> chapters/12.xml- </example> chapters/12.xml- <para role=3D"noindent">(See chapters/12.xml- <xref linkend=3D"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 compare= d first, and the other seltau places following. Unfortunately the z4 place,= which expresses by how much one entity exceeds the other, is displaced int= o a lujvo place whose number is different for each lujvo. For example, whil= e 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 t= agged with chapters/12.xml- <valsi>vemau</valsi> (for chapters/12.xml- <valsi>zmadu</valsi>) or chapters/12.xml- <valsi>veme'a</valsi> (for *********************************************************************** lab= mau 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 b= oth a CCV-form and a CVV-form rafsi assigned, and still fewer have all thre= e forms of short rafsi. However, gismu with both a CVC-form and another sho= rt rafsi are fairly common, partly because more possible CVC-form rafsi exi= st. Yet CVC-form rafsi, even though they are fairly easy to remember, canno= t be used at the end of a lujvo (because lujvo must end in vowels), so just= ifying the assignment of an additional short rafsi to many gismu.</para> *********************************************************************** lam= gri 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> *********************************************************************** lan= ge'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=3D"section-asymmetric-tanru"/>, is chapters/12.xml: <valsi>lange'u</valsi>, meaning chapters/12.xml- <quote>sheepdog</quote>. Clearly a sheepdog is not a do= g which is a sheep (the symmetrical interpretation is wrong), nor a dog of = the sheep breed (the asymmetrical interpretation is wrong). Indeed, there i= s 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, t= he 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 o= f the longer lujvo, for which chapters/12.xml: <valsi>lange'u</valsi> can be understood as an abbrevia= tion.</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 compo= nent place structures are:</para> *********************************************************************** lan= tro chapters/12.xml- <valsi>lanme</valsi> and chapters/12.xml- <valsi>gerku</valsi> at all. Rather, the lujvo refers t= o 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:</par= a> chapters/12.xml- <example xml:id=3D"example-random-id-TW5Q"> chapters/12.xml- <title> chapters/12.xml- <anchor xml:id=3D"c12e14d5"/> -- chapters/12.xml- <valsi>jitro</valsi>: j1 controls j2 in activity j3</= para> chapters/12.xml- </example> chapters/12.xml- <para role=3D"indent">Note that this lujvo is symmetric= al 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, t= he 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 o= f the longer lujvo, for which chapters/12.xml- <valsi>lange'u</valsi> can be understood as an abbrevia= tion.</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 velj= vo. And it also means that, for a place structure derivation that actually = makes sense, rather than being ad-hoc, the Lojbanist should probably go thr= ough a derivation for chapters/12.xml- <valsi>xancypliminde</valsi> or one of the other possib= ilities that is analogous to the analysis of chapters/12.xml: <valsi>terlantroge'u</valsi> above, even if he or she d= ecides to stick with a shorter, more convenient form like chapters/12.xml- <valsi>xanmi'e</valsi>. In addition, of course, the pos= sibilities of elliptical lujvo increase their potential ambiguity enormousl= y – an unavoidable fact which should be borne in mind.</para> chapters/12.xml- </section> chapters/12.xml- <section xml:id=3D"section-comparatives"> *********************************************************************** lik= ygau 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=3D"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=3D"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></def= inition></para> chapters/12.xml- </example> chapters/12.xml- <para role=3D"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 e= vent rather than a person: chapters/12.xml- <jbophrase>lo rinka</jbophrase> is a cause, not a cause= r. 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=3D"example-random-id-1HT3"> chapters/12.xml- <title> chapters/12.xml- <anchor xml:id=3D"c12e13d11"/> *********************************************************************** lik= yri'a chapters/12.xml- <valsi>rinka</valsi> is less generally useful than chapters/12.xml- <valsi>gasnu</valsi>, because its r1 place is another e= vent rather than a person: chapters/12.xml- <jbophrase>lo rinka</jbophrase> is a cause, not a cause= r. 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=3D"example-random-id-1HT3"> chapters/12.xml- <title> *********************************************************************** liv= gyterbilma chapters/04.xml- <anchor xml:id=3D"c4e6d15"/> chapters/04.xml- chapters/04.xml- chapters/04.xml: na'e zei .a zei na'e zei by. livgyterbilma chapters/04.xml- non-A, non-B liver-disease chapters/04.xml- non-A, non-B hepatitis chapters/04.xml- -- chapters/04.xml- zeis from it doesn't end with a brivla, = and in fact is not even grammatical. As written, the example is a tanru wit= h two components, but by adding a chapters/04.xml- zei between chapters/04.xml- by. and chapters/04.xml: livgyterbilma to produce chapters/04.xml- chapters/04.xml- chapters/04.xml- -- chapters/04.xml- <anchor xml:id=3D"c4e6d17"/> chapters/04.xml- chapters/04.xml- chapters/04.xml: na'e zei .a zei na'e zei by. zei livgyterbilma= chapters/04.xml- non-A-non-B-hepatitis chapters/04.xml- chapters/04.xml- *********************************************************************** lo'= ikle chapters/04.xml- chapters/04.xml- lotkle chapters/04.xml- blokle chapters/04.xml: lo'ikle chapters/04.xml- chapters/04.xml- lotlei chapters/04.xml- blolei -- chapters/04.xml- 5858 chapters/04.xml- chapters/04.xml- chapters/04.xml: lo'ikle chapters/04.xml- 6367 chapters/04.xml- chapters/04.xml- -- chapters/04.xml- So the form chapters/04.xml- blolei is preferred, but only by a tiny = margin over chapters/04.xml- blokle; "lotlei" and "lotkle" are only s= lightly worse; chapters/04.xml: lo'ikle suffers because of its apostroph= e, and chapters/04.xml- lo'irlei because of having both apostrop= he and hyphen. chapters/04.xml- Our third example will result in forming both a l= ujvo and a name from the tanru chapters/04.xml- logji bangu girzu, or *********************************************************************** lo'= irlei chapters/04.xml- chapters/04.xml- lotlei chapters/04.xml- blolei chapters/04.xml: lo'irlei chapters/04.xml- chapters/04.xml- Only chapters/04.xml: lo'irlei requires hyphenation (to avoid = confusion with the cmavo sequence chapters/04.xml- lo'i lei). All six forms are val= id versions of the lujvo, as are the six further forms using long rafsi; ho= wever, the scoring algorithm produces the following results: chapters/04.xml- chapters/04.xml- -- chapters/04.xml- 5847 chapters/04.xml- chapters/04.xml- chapters/04.xml: lo'irlei chapters/04.xml- 7456 chapters/04.xml- chapters/04.xml- -- chapters/04.xml- blolei is preferred, but only by a tiny = margin over chapters/04.xml- blokle; "lotlei" and "lotkle" are only s= lightly worse; chapters/04.xml- lo'ikle suffers because of its apostroph= e, and chapters/04.xml: lo'irlei because of having both apostrop= he and hyphen. chapters/04.xml- Our third example will result in forming both a l= ujvo and a name from the tanru chapters/04.xml- logji bangu girzu, or chapters/04.xml- logical-language group in English. ( *********************************************************************** loj= bangri chapters/04.xml- chapters/04.xml- After hyphenation, we have: chapters/04.xml- chapters/04.xml: lojbangri chapters/04.xml- lojbaugri chapters/04.xml- lojbangygri chapters/04.xml- -- chapters/04.xml- chapters/04.xml- The only fully reduced lujvo forms are chapters/04.xml- chapters/04.xml: lojbangri and chapters/04.xml- lojbaugri, of which the latter has a sli= ghtly lower score: 8827 versus 8796, respectively. However, for the name of= the organization, we chose to make sure the name of the language was embed= ded in it, and to use the clearer long-form rafsi for chapters/04.xml- girzu, producing chapters/04.xml- lojbangirz. *********************************************************************** loj= baugri chapters/04.xml- After hyphenation, we have: chapters/04.xml- chapters/04.xml- lojbangri chapters/04.xml: lojbaugri chapters/04.xml- lojbangygri chapters/04.xml- chapters/04.xml- logjybangri -- chapters/04.xml- The only fully reduced lujvo forms are chapters/04.xml- chapters/04.xml- lojbangri and chapters/04.xml: lojbaugri, of which the latter has a sli= ghtly lower score: 8827 versus 8796, respectively. However, for the name of= the organization, we chose to make sure the name of the language was embed= ded in it, and to use the clearer long-form rafsi for chapters/04.xml- girzu, producing chapters/04.xml- lojbangirz. chapters/04.xml- Finally, here is a four-part lujvo with a cmavo i= n it, based on the tanru *********************************************************************** lot= kle chapters/04.xml- -kle- and chapters/04.xml- -lei-. Both these gismu are among the ha= ndful which have both CVV-form and CCV-form rafsi, so there is an unusual n= umber of possibilities available for a two-part tanru: chapters/04.xml- chapters/04.xml: lotkle chapters/04.xml- blokle chapters/04.xml- lo'ikle chapters/04.xml- -- chapters/04.xml- lo'i lei). All six forms are val= id versions of the lujvo, as are the six further forms using long rafsi; ho= wever, the scoring algorithm produces the following results: chapters/04.xml- chapters/04.xml- chapters/04.xml: lotkle chapters/04.xml- 5878 chapters/04.xml- chapters/04.xml- -- chapters/04.xml- chapters/04.xml- So the form chapters/04.xml- blolei is preferred, but only by a tiny = margin over chapters/04.xml: blokle; "lotlei" and "lotkle" are only s= lightly worse; chapters/04.xml- lo'ikle suffers because of its apostroph= e, and chapters/04.xml- lo'irlei because of having both apostrop= he and hyphen. chapters/04.xml- Our third example will result in forming both a l= ujvo and a name from the tanru *********************************************************************** lot= lei chapters/04.xml- blokle chapters/04.xml- lo'ikle chapters/04.xml- chapters/04.xml: lotlei chapters/04.xml- blolei chapters/04.xml- lo'irlei chapters/04.xml- -- chapters/04.xml- 6367 chapters/04.xml- chapters/04.xml- chapters/04.xml: lotlei chapters/04.xml- 5867 chapters/04.xml- chapters/04.xml- -- chapters/04.xml- chapters/04.xml- So the form chapters/04.xml- blolei is preferred, but only by a tiny = margin over chapters/04.xml: blokle; "lotlei" and "lotkle" are only s= lightly worse; chapters/04.xml- lo'ikle suffers because of its apostroph= e, and chapters/04.xml- lo'irlei because of having both apostrop= he and hyphen. chapters/04.xml- Our third example will result in forming both a l= ujvo and a name from the tanru *********************************************************************** mam= pa'u chapters/04.xml- chapters/04.xml- chapters/04.xml- chapters/04.xml: mampa'u chapters/04.xml- chapters/04.xml- chapters/04.xml- which refers specifically to th= e concept chapters/04.xml- maternal grandfather. The two gismu that= constitute the tanru are represented in chapters/04.xml: mampa'u by the rafsi chapters/04.xml- mam- and chapters/04.xml- -pa'u, respectively; these two rafsi are= then concatenated together to form chapters/04.xml: mampa'u. chapters/04.xml- long rafsi = formcompared with short form in effect on lujvo meanin= g short rafsi= formcompared with long form in effect on lujvo meanin= g rafsi form<= /primary>effect of choice on meaning of lujvo lujvomulti= ple forms of = lujvomeaning of Like gismu, lu= jvo have only one meaning. When a lujvo is formally entered into a dictiona= ry of the language, a specific definition will be assigned based on one par= ticular interrelationship between the terms. (See chapters/04.xml- for how this has been= done.) Unlike gismu, lujvo may have more than one form. This is because th= ere 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 noi= sy environments, in place of a short rafsi; the result is considered the sa= me lujvo, even though the word is spelled and pronounced differently. Thus = the word chapters/04.xml- -- chapters/04.xml- chapters/04.xml- chapters/04.xml- chapters/04.xml: mampa'u chapters/04.xml- mamta patfu chapters/04.xml- mother father chapters/04.xml- or maternal grandfather *********************************************************************** man= skapi chapters/01.xml- this bookreviewers of reviewers of this book I would lik= e to thank the following people for their detailed reviews, suggestions, co= mments, and early detection of my embarrassing errors in Lojban, logic, Eng= lish, and cross-references: Nick Nicholas, Mark Shoulson, Veijo Vilva, Coli= n Fine, And Rosta, Jorge Llambias, Iain Alexander, Paulo S. L. M. Barreto, = Robert J. Chassell, Gale Cowan, Karen Stein, Ivan Derzhanski, Jim Carter, I= rene Gates, Bob LeChevalier, John Parks-Clifford (also known as chapters/01.xml- pc), and Nora Tansky LeChevalier. chapters/01.xml- Nick Nicholas (NSN) would like to thank the follo= wing Lojbanists: Mark Shoulson, Veijo Vilva, Colin Fine, And Rosta, and Iai= n Alexander for their suggestions and comments; John Cowan, for his extensi= ve comments, his exemplary trailblazing of Lojban grammar, and for solving = the chapters/01.xml: manskapi dilemma for NSN; Jorge Llambias= , for his even more extensive comments, and for forcing NSN to think more t= han 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 pro= gram converting old rafsi text to new rafsi text, and sparing NSN from emba= rrassing errors; and Jim Carter, for his dogged persistence in analyzing lu= jvo algorithmically, which inspired this research, and for first identifyin= g the three lujvo classes. chapters/01.xml- chapters/01.xml- BrownJames Cooke Of course, the entire Lo= glan Project owes a considerable debt to James Cooke Brown as the language = inventor, and also to several earlier contributors to the development of th= e language. Especially noteworthy are Doug Landauer, Jeff Prothero, Scott L= ayson, Jeff Taylor, and Bob McIvor. Final responsibility for the remaining = errors and infelicities is solely mine. chapters/01.xml- *********************************************************************** mi'= erxanpli chapters/12.xml- chapters/12.xml- which lead to the three differe= nt lujvo chapters/12.xml- xanplimi'e, chapters/12.xml: mi'erxanpli, and chapters/12.xml- minkemxanpli respectively. chapters/12.xml- latent comp= onent Does this make chapters/12.xml- xanmi'e wrong? By no means. But it does = mean that there is a latent component to the meaning of *********************************************************************** min= kemxanpli chapters/12.xml- which lead to the three differe= nt lujvo chapters/12.xml- xanplimi'e, chapters/12.xml- mi'erxanpli, and chapters/12.xml: minkemxanpli respectively. chapters/12.xml- latent comp= onent Does this make chapters/12.xml- xanmi'e wrong? By no means. But it does = mean that there is a latent component to the meaning of chapters/12.xml- *********************************************************************** mud= ysiclu chapters/04.xml- mudri siclu ( chapters/04.xml- wooden whistle) cannot form the lujvo chapters/04.xml- mudsiclu; instead, chapters/04.xml: mudysiclu must be used. (Remember that chapters/04.xml- y is not counted in determining wh= ether the first five letters of a brivla contain a consonant cluster: this = is why.) chapters/04.xml- rafsifour-letterrequirement for y-hyphen The chapters/04.xml- y-hyphen is also used to attach a 4-letter rafsi, forme= d by dropping the final vowel of a gismu, to the following rafsi. (This pro= cedure was shown, but not explained, in *********************************************************************** nal= brablo chapters/12.xml- to go to a walking surface. Instead, we = would need chapters/12.xml- selkemdzukla, with an explicit rafsi for chapters/12.xml- ke. Similarly, chapters/12.xml: nalbrablo (from chapters/12.xml- na'e barda bloti) means chapters/12.xml- non-big boat, whereas chapters/12.xml- *********************************************************************** nal= mle chapters/15.xml- -no'e-. The selbri in chapters/15.xml- through chapters/15.xml- could be rep= laced by the lujvo chapters/15.xml: nalmle, chapters/15.xml- normle, and chapters/15.xml- tolmle respectively. chapters/15.xml- This large variety of scalar negations is provide= d because different scales have different properties. Some scales are open-= ended in both directions: there is no *********************************************************************** nel= cymau chapters/12.xml- chapters/12.xml- chapters/12.xml- comparative= lujvopotential ambiguity in F= or example, does chapters/12.xml: nelcymau mean chapters/12.xml- X likes Y more than X likes Z, or chapters/12.xml- X likes Y more than Z likes Y? Does chapters/12.xml- klamau mean: -- chapters/12.xml- chapters/12.xml- chapters/12.xml- chapters/12.xml: nelcymau: z1, more than z2, likes n2 b= y amount z4 chapters/12.xml- chapters/12.xml: selnelcymau: z1, more than z2, is like= d by n1 in amount z4 chapters/12.xml- chapters/12.xml- klamau: z1, more than z2, goes to k2 f= rom k3 via k4 by means of k5 chapters/12.xml- -- chapters/12.xml- (See chapters/12.xml- for the way in= which this problem is resolved when lujvo aren't used.) chapters/12.xml- The ordering rule places the things being compare= d first, and the other seltau places following. Unfortunately the z4 place,= which expresses by how much one entity exceeds the other, is displaced int= o a lujvo place whose number is different for each lujvo. For example, whil= e chapters/12.xml: nelcymau has z4 as its fourth place, chapters/12.xml- klamau has it as its sixth place. In any= sentence where a difficulty arises, this amount-place can be redundantly t= agged with chapters/12.xml- vemau (for chapters/12.xml- zmadu) or *********************************************************************** nil= kla chapters/12.xml- nu, as well as the other abstractors men= tioned in this section, is given in chapters/12.xml- . chapters/12.xml- lujvo place= structuremulti-place abstraction lujvo lujvo place structure"ni" lujvo For those abstr= actors which have a second place as well, the standard convention is to pla= ce this place after, rather than before, the places of the brivla being abs= tracted. The place structure of chapters/12.xml: nilkla, the lujvo derived from chapters/12.xml- ni klama, is the imposing: chapters/12.xml- chapters/12.xml- *********************************************************************** nor= mle chapters/15.xml- <xref linkend=3D"example-random-id-qh9U"/> through chapters/15.xml- <xref linkend=3D"example-random-id-qHAV"/> could be rep= laced 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 provide= d 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 *********************************************************************** nun= ctikezgau 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 exc= essively 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=3D"example-random-id-bSDW"> chapters/12.xml- <title> -- chapters/12.xml- <para><definition><content>n1 is the event of c1 eati= ng c2</content></definition></para> chapters/12.xml- </example> chapters/12.xml- <para role=3D"indent">Now we can transform the veljvo o= f 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=3D"example-random-id-izvp"> chapters/12.xml- <title> -- chapters/12.xml- <para role=3D"indent">But it is also possible to omit t= he n1 place itself! The n1 place describes the event brought about; an even= t 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 (t= hey're in the lujvo place structure). So n1 would not give us any informati= on we didn't already know. In fact, the n1=3Dg2 place is dependent on c1 an= d c2 jointly – 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=3D"example-random-id-9oTP"> chapters/12.xml- <title> chapters/12.xml- <anchor xml:id=3D"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 – that the seltau of a chapters/12.xml- <valsi>gasnu</valsi> lujvo is an event. If we drop thes= e rafsi out, and use instead the shorter lujvo chapters/12.xml- <valsi>ctigau</valsi>, rejecting its symmetrical interp= retation ( 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=3D"example-random-id-ITvd"> chapters/12.xml- <title> chapters/12.xml- <anchor xml:id=3D"c12e13d5"/> *********************************************************************** nun= ji'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> *********************************************************************** nun= kalte 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> *********************************************************************** nun= kilbra chapters/05.xml- <para> <indexterm type=3D"general"><primary>asymmetrica= l tanru types</primary><secondary>object-of-action + action</secondary></in= dexterm> The tertau represents an action, and the seltau then represents th= e 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></listite= m> chapters/05.xml- </varlistentry> chapters/05.xml- <varlistentry> *********************************************************************** nun= klama chapters/12.xml- <para><definition><content>nu1 is the event of k1's c= oming/going to k2 from k3 via route k4 by means k5.</content></definition><= /para> chapters/12.xml- </example> chapters/12.xml- <para role=3D"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 info= rmation on chapters/12.xml- <valsi>nu</valsi>, as well as the other abstractors men= tioned in this section, is given in chapters/12.xml- <xref linkend=3D"chapter-abstractions"/>.</para> *********************************************************************** nun= pinxe 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> *********************************************************************** nun= 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=3D"indent">It is not uncommon for abstractor= s 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=3D"interlinear-gloss-example" xml:id=3D"e= xample-random-id-RKcH"> chapters/12.xml- <title> chapters/12.xml- <anchor xml:id=3D"c12e12d4"/> -- chapters/12.xml- <para role=3D"noindent">where the d2 place has disappea= red altogether, being replaced by the places of the seltau. As shown in chapters/12.xml- <xref linkend=3D"example-random-id-8Nos"/>, the orderin= g follows this idea of replacement: the seltau places are inserted at the p= oint 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 or= dinary asymmetric lujvo chapters/12.xml- chapters/12.xml- <valsi>soidji</valsi>, a chapters/12.xml- <quote>soldier desirer</quote>, whose place structure i= s just</para> -- chapters/12.xml- <para><definition><content>d1 desires (a soldier of a= rmy s2) for purpose d3</content></definition></para> chapters/12.xml- </example> chapters/12.xml- <para role=3D"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 nee= d for explicit chapters/12.xml- *********************************************************************** nun= te'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> *********************************************************************** nun= terji'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> *********************************************************************** pac= raistu 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></listi= tem> chapters/05.xml- </varlistentry> chapters/05.xml- </variablelist> *********************************************************************** pev= risnyjelca chapters/13.xml- <valsi>risnyjelca</valsi> (heart burn) might have a pla= ce 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 figu= rative, might have the place structure:</para> chapters/13.xml- <definition><content>x1 is indigestion/heartburn suffer= ed 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 *********************************************************************** pos= ydji chapters/12.xml- <section xml:id=3D"section-tertau-SE"> chapters/12.xml- <title>Eliding SE rafsi from tertau chapters/12.xml- lujvo place= structureeffect of "SE"-dropping in tertau<= /secondary> Eliding SE rafsi from tertau gets us into much more= trouble. To understand why, recall that lujvo, following their veljvo, des= cribe some type of whatever their tertau describe. Thus, chapters/12.xml: posydji describes a type of chapters/12.xml- djica, chapters/12.xml- gerzda describes a type of chapters/12.xml- zdani, and so on. What is certain is tha= t *********************************************************************** rai= rgugde chapters/18.xml- chapters/18.xml- chapters/18.xml- indefinite valuessubjective subjective amountsexpressing All of the numbers discussed so far= are objective, even if indefinite. If there are exactly six superpowers ( chapters/18.xml: rairgugde, chapters/18.xml- superlative-states) in the world, then chapters/18.xml: ro rairgugde means the same as chapters/18.xml: xa rairgugde. It is often useful= , however, to express subjective indefinite values. The cmavo chapters/18.xml- chapters/18.xml- rau (enough), chapters/18.xml- *********************************************************************** ric= rxaceru chapters/04.xml- maple sugar could get the fu'ivla chapters/04.xml- chapters/04.xml- saktrxaceru, or could be represented by = the tanru chapters/04.xml: tricrxaceru sakta. Technically, chapters/04.xml: ricrxaceru and chapters/04.xml: tricrxaceru are distinct fu'ivla, but th= ey would surely be given the same meanings if both happened to be in use. chapters/04.xml- chapters/04.xml- chapters/04.xml- *********************************************************************** ris= nyjelca 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 figur= ative (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 pla= ce 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 figu= rative, might have the place structure:</para> chapters/13.xml- <definition><content>x1 is indigestion/heartburn suffer= ed 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 for= m 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 b= ecause the apostrophes are not counted for this purpose.</para> chapters/04.xml- <para> <indexterm type=3D"general"><primary>brivla</pri= mary><secondary>subtypes of</secondary></indexterm> The three subtypes of b= rivla are:</para> chapters/04.xml- <orderedlist> -- chapters/04.xml- <jbophrase valid=3D"false">ro'ire'o</jbophrase> (which = breaks up into two cmavo), nor can it be chapters/04.xml- <jbophrase valid=3D"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 hyphe= nated 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=3D"general"><primary>lujvo</primary><second= ary>with zei</secondary></indexterm> *********************************************************************** rok= re'o chapters/04.xml- <jbophrase valid=3D"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 hyphe= nated 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=3D"general"><primary>lujvo</primary><second= ary>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 c= an make a phrase containing any desired words, joining each pair of them wi= th the special cmavo *********************************************************************** sak= trxaceru 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 th= ey would surely be given the same meanings if both happened to be in use.</= para> *********************************************************************** sel= dzukla chapters/12.xml- <para role=3D"indent">We can swap the k1 and k2 places = using chapters/12.xml- <jbophrase>se dzukla</jbophrase>, but we cannot directl= y make chapters/12.xml- <jbophrase>se dzukla</jbophrase> into chapters/12.xml: <valsi>seldzukla</valsi>, which would represent the vel= jvo chapters/12.xml- <jbophrase>selcadzu klama</jbophrase> and plausibly mea= n 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 *********************************************************************** sel= gekmau chapters/12.xml- <para> <indexterm type=3D"general"><primary>lujvo creat= ion</primary><secondary>use of multiple SE in</secondary></indexterm> If th= e lujvo we want to modify with SE has a seltau already starting with a SE r= afsi, 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 som= ething 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 ju= st chapters/12.xml- <valsi>gleki</valsi>), so there would be no good reason= to have *********************************************************************** sel= jdasku chapters/12.xml- </example> chapters/12.xml- <para role=3D"indent">The l3 place (the beliefs of the = religion) is dependent on the l1 place (the religion) and so is omitted.</p= ara> 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=3D"example-random-id-7Tdb"> chapters/12.xml- <title> chapters/12.xml- <anchor xml:id=3D"c12e14d4"/> -- chapters/12.xml- </example> chapters/12.xml- <para role=3D"noindent">which, according to the rule ex= pressed in chapters/12.xml- <xref linkend=3D"section-seltau-SE"/>, can be further e= xpressed 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 r= ules 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 th= at religion. Rather, it is what they say under the authority of that religi= on, or using the religion as a medium, or following the rules associated wi= th the religion, or something of the kind. So the veljvo is somewhat ellipt= ical.</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 requir= es.</para> chapters/12.xml- <para>Another example of this kind of anomalous lujvo, = drawn from the tanru lists in chapters/12.xml- *********************************************************************** sel= kanla 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 att= empt to accommodate the resulting lujvo into our guidelines for place struc= ture is fitting a square peg in a round hole. Since they can be so misleadi= ng, lujvo with SE rafsi elided from the tertau should be avoided in favor o= f their more explicit counterparts: in this case, chapters/12.xml: <valsi>blaselkanla</valsi>.</para> chapters/12.xml- </section> chapters/12.xml- <section xml:id=3D"section-eliding-ke-kehe"> chapters/12.xml- <title>Eliding KE and KEhE rafsi from lujvo *********************************************************************** sel= kemdzukla chapters/12.xml- seldzukla, which would represent the vel= jvo chapters/12.xml- selcadzu klama and plausibly mea= n something like chapters/12.xml- to go to a walking surface. Instead, we = would need chapters/12.xml: selkemdzukla, with an explicit rafsi for chapters/12.xml- ke. Similarly, chapters/12.xml- nalbrablo (from chapters/12.xml- na'e barda bloti) means *********************************************************************** sel= klamau chapters/12.xml- chapters/12.xml- klamau: z1, more than z2, goes to k2 f= rom k3 via k4 by means of k5 chapters/12.xml- chapters/12.xml: selklamau: z1, more than z2, is gone t= o by k1 from k3 via k4 by means of k5 chapters/12.xml- chapters/12.xml- terklamau: z1, more than z2, is an ori= gin point from destination k2 for k1's going via k4 by means of k5 chapters/12.xml- *********************************************************************** sel= nelcymau chapters/12.xml- chapters/12.xml- nelcymau: z1, more than z2, likes n2 b= y amount z4 chapters/12.xml- chapters/12.xml: selnelcymau: z1, more than z2, is like= d by n1 in amount z4 chapters/12.xml- chapters/12.xml- klamau: z1, more than z2, goes to k2 f= rom k3 via k4 by means of k5 chapters/12.xml- *********************************************************************** sel= selgekmau chapters/12.xml- making people happier than, more enjoyable than,= more of a 'se gleki' than. If something is less enjoyable than som= ething else, we can say it is chapters/12.xml- se selgekmau. chapters/12.xml- But we can also say it is chapters/12.xml: selselgekmau. Two chapters/12.xml- se cmavo in a row cancel each other ( chapters/12.xml- se se gleki means the same as ju= st chapters/12.xml- gleki), so there would be no good reason= to have *********************************************************************** sel= seljdasku chapters/12.xml- chapters/12.xml- which, according to the rule ex= pressed in chapters/12.xml- , can be further e= xpressed as chapters/12.xml: selseljdasku. However, there is no need = for the ugly chapters/12.xml- selsel- prefix just to get the r= ules right: chapters/12.xml- jdaselsku is a reasonable, if anomalous,= lujvo. chapters/12.xml- However, there is a further problem with *********************************************************************** sel= ti'i chapters/12.xml- chapters/12.xml- lined up This lujvo does not fit any of our exis= ting molds: it is the second seltau place, st2, that is equivalent to one o= f the tertau places, namely f1. However, if we understand chapters/12.xml- ti'ifla as an abbreviation for the lujvo chapters/12.xml: selti'ifla, then we get the first places= of seltau and tertau lined up. The place structure of chapters/12.xml- chapters/12.xml: selti'i is: chapters/12.xml- chapters/12.xml- chapters/12.xml- <anchor xml:id=3D"c12e9d2"/> chapters/12.xml- chapters/12.xml- chapters/12.xml: selti'i: idea/action se1 is suggested = by agent se2 to audience se3 chapters/12.xml- chapters/12.xml- 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: chapters/12.xml- -- chapters/12.xml- where the last place (st3) is p= robably some sort of legislature. chapters/12.xml- lujvoabbreviated Abbreviated lujvo like chapters/12.xml- ti'ifla are more intuitive (for the lujv= o-maker) than their more explicit counterparts like chapters/12.xml: selti'ifla (as well as shorter). They do= n't require the coiner to sit down and work out the precise relation betwee= n the seltau and the tertau: he or she can just rattle off a rafsi pair. Bu= t should the lujvo get to the stage where a place structure needs to be wor= ked out, then the precise relation does need to be specified. And in that c= ase, such abbreviated lujvo form a trap in lujvo place ordering, since they= obscure the most straightforward relation between the seltau and tertau. T= o 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- *********************************************************************** sel= zda chapters/12.xml- , where we le= arned that the g1 place was equivalent to the z2 place. In order to get the= places aligned, we could convert chapters/12.xml- zdani to chapters/12.xml- se zdani (or chapters/12.xml: selzda when expressed as a lujvo). The p= lace structure of chapters/12.xml: selzda is chapters/12.xml- chapters/12.xml- chapters/12.xml- <anchor xml:id=3D"c12e5d5"/> -- chapters/12.xml- <para><definition><content>s1 is housed by nest s2</c= ontent></definition></para> chapters/12.xml- </example> chapters/12.xml- <para role=3D"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=3D"example-random-id-KqE4"> chapters/12.xml- <title> chapters/12.xml- <anchor xml:id=3D"c12e5d6"/> -- chapters/12.xml- <para><definition><content>s1=3Dg1 is a dog housed in= nest s2 of dog breed g2</content></definition></para> chapters/12.xml- </example> chapters/12.xml- <para role=3D"indent">However, although chapters/12.xml: <valsi>gerselzda</valsi> is a valid lujvo, it doesn't t= ranslate chapters/12.xml- <quote>doghouse</quote>; its first place is the dog, no= t 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 asym= metrical, 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 plaus= ibility must be applied, just as in interpreting tanru.</para> chapters/12.xml- chapters/12.xml- <para> *********************************************************************** sik= curnu 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> *********************************************************************** soi= dji 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=3D"indent">It is not uncommon for abstractor= s 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=3D"interlinear-gloss-example" xml:id=3D"e= xample-random-id-RKcH"> chapters/12.xml- <title> chapters/12.xml- <anchor xml:id=3D"c12e12d4"/> -- chapters/12.xml- <para role=3D"noindent">where the d2 place has disappea= red altogether, being replaced by the places of the seltau. As shown in chapters/12.xml- <xref linkend=3D"example-random-id-8Nos"/>, the orderin= g follows this idea of replacement: the seltau places are inserted at the p= oint 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 or= dinary asymmetric lujvo chapters/12.xml- chapters/12.xml: <valsi>soidji</valsi>, a chapters/12.xml- <quote>soldier desirer</quote>, whose place structure i= s just</para> chapters/12.xml- <example xml:id=3D"example-random-id-2VMP"> chapters/12.xml- <title> -- chapters/12.xml- <para><definition><content>d1 desires (a soldier of a= rmy s2) for purpose d3</content></definition></para> chapters/12.xml- </example> chapters/12.xml- <para role=3D"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 nee= d for explicit chapters/12.xml- chapters/12.xml- <valsi>kei</valsi> in tanru: *********************************************************************** spa= trkoka 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></pa= ra></listitem> chapters/05.xml- </varlistentry> chapters/05.xml- <varlistentry> *********************************************************************** spr= aile chapters/04.xml- <orderedlist> chapters/04.xml- <listitem> chapters/04.xml- <para> <indexterm type=3D"general"><primary>fu'ivla= </primary><secondary>initial consonant cluster in</secondary></indexterm> = <indexterm type=3D"general"><primary>fu'ivla</primary><secondary>rules for = formation of</secondary></indexterm> must contain a consonant cluster in th= e first five letters of the word; if this consonant cluster is at the begin= ning, it must either be a permissible initial consonant pair, or a longer c= luster such that each pair of adjacent consonants in the cluster is a permi= ssible initial consonant pair: chapters/04.xml: <valsi>spraile</valsi> is acceptable, but not chapters/04.xml- <valsi valid=3D"false">ktraile</valsi> or chapters/04.xml- <valsi valid=3D"false">trkaile</valsi>;</para> chapters/04.xml- </listitem> *********************************************************************** tar= mrnintegrale 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 *********************************************************************** ter= ci'e chapters/18.xml- <listitem><definition><content>x1 is approximately = equal to x2 [<valsi>namcu</valsi> <valsi>jibni</valsi>, number-near]</conte= nt></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 wi= th function x2 of system x3</content></definition></listitem> chapters/18.xml- </varlistentry> chapters/18.xml- </variablelist> *********************************************************************** ter= gusni 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=3D"general"><primary>asymmetrica= l tanru types</primary><secondary>energy-source + powered</secondary></inde= xterm> The seltau specifies a source of energy for the referent of the tert= au.</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></listite= m> chapters/05.xml- </varlistentry> chapters/05.xml- </variablelist> *********************************************************************** ter= kakpa 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> *********************************************************************** ter= klamau chapters/12.xml- <para> chapters/12.xml- <valsi>selklamau</valsi>: z1, more than z2, is gone t= o 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 ori= gin point from destination k2 for k1's going via k4 by means of k5</para> chapters/12.xml- </example> chapters/12.xml- <para role=3D"noindent">(See chapters/12.xml- <xref linkend=3D"chapter-abstractions"/> for the way in= which this problem is resolved when lujvo aren't used.)</para> *********************************************************************** ter= lantroge'u chapters/12.xml- <valsi>lanme</valsi> and chapters/12.xml- <valsi>gerku</valsi> at all. Rather, the lujvo refers t= o 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:</par= a> chapters/12.xml- <example xml:id=3D"example-random-id-TW5Q"> chapters/12.xml- <title> chapters/12.xml- <anchor xml:id=3D"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, t= he 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 o= f the longer lujvo, for which chapters/12.xml- <valsi>lange'u</valsi> can be understood as an abbrevia= tion.</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 velj= vo. And it also means that, for a place structure derivation that actually = makes sense, rather than being ad-hoc, the Lojbanist should probably go thr= ough a derivation for chapters/12.xml- <valsi>xancypliminde</valsi> or one of the other possib= ilities that is analogous to the analysis of chapters/12.xml: <valsi>terlantroge'u</valsi> above, even if he or she d= ecides to stick with a shorter, more convenient form like chapters/12.xml- <valsi>xanmi'e</valsi>. In addition, of course, the pos= sibilities of elliptical lujvo increase their potential ambiguity enormousl= y – an unavoidable fact which should be borne in mind.</para> chapters/12.xml- </section> chapters/12.xml- <section xml:id=3D"section-comparatives"> *********************************************************************** ti'= ifla chapters/12.xml- <title>Eliding SE rafsi from seltau chapters/12.xml- lujvodropping SE rafsi It is common to fo= rm 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 constr= uctions shorter. Since it puts more strain on the listener who has not hear= d the lujvo before, the shortness of the word should not necessarily outwei= gh ease in understanding, especially if the lujvo refers to a rare or unusu= al concept. chapters/12.xml- proposed la= w Consider as an example the lujvo chapters/12.xml: ti'ifla, from the veljvo chapters/12.xml- stidi flalu, and meaning chapters/12.xml- bill, proposed law. The gismu place stru= ctures are: chapters/12.xml- -- chapters/12.xml- by lawgiver f5 chapters/12.xml- chapters/12.xml- lined up This lujvo does not fit any of our exis= ting molds: it is the second seltau place, st2, that is equivalent to one o= f the tertau places, namely f1. However, if we understand chapters/12.xml: ti'ifla as an abbreviation for the lujvo chapters/12.xml: selti'ifla, then we get the first places= of seltau and tertau lined up. The place structure of chapters/12.xml- chapters/12.xml- selti'i is: chapters/12.xml- -- chapters/12.xml- chapters/12.xml- where the last place (st3) is p= robably some sort of legislature. chapters/12.xml- lujvoabbreviated Abbreviated lujvo like chapters/12.xml: ti'ifla are more intuitive (for the lujv= o-maker) than their more explicit counterparts like chapters/12.xml: selti'ifla (as well as shorter). They do= n't require the coiner to sit down and work out the precise relation betwee= n the seltau and the tertau: he or she can just rattle off a rafsi pair. Bu= t should the lujvo get to the stage where a place structure needs to be wor= ked out, then the precise relation does need to be specified. And in that c= ase, such abbreviated lujvo form a trap in lujvo place ordering, since they= obscure the most straightforward relation between the seltau and tertau. T= o 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: ti'ifla are given the place structure th= ey would have with the appropriate SE added to the seltau. chapters/12.xml- plausibilit= yin abbreviated lujvo abbreviated lujvo and plausibility<= /indexterm> implausible Note that, with these lujvo, an interpretation requiring SE insert= ion 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 shoul= d be aware of the risk of ambiguity. chapters/12.xml- chapters/12.xml- *********************************************************************** tri= crxaceru chapters/04.xml- maple sugar could get the fu'ivla chapters/04.xml- chapters/04.xml- saktrxaceru, or could be represented by = the tanru chapters/04.xml: tricrxaceru sakta. Technically, chapters/04.xml- ricrxaceru and chapters/04.xml: tricrxaceru are distinct fu'ivla, but th= ey would surely be given the same meanings if both happened to be in use. chapters/04.xml- chapters/04.xml- chapters/04.xml- *********************************************************************** tur= du'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- *********************************************************************** vel= mikce chapters/05.xml- <para> <indexterm type=3D"general"><primary>asymmetrica= l 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></li= stitem> chapters/05.xml- </varlistentry> chapters/05.xml- </variablelist> *********************************************************************** xan= cypliminde chapters/12.xml- chapters/12.xml- <valsi>xanmi'e</valsi>, the gismu chapters/12.xml- <valsi>pilno</valsi>, which is not explicit in the velj= vo. And it also means that, for a place structure derivation that actually = makes sense, rather than being ad-hoc, the Lojbanist should probably go thr= ough a derivation for chapters/12.xml: <valsi>xancypliminde</valsi> or one of the other possib= ilities that is analogous to the analysis of chapters/12.xml- <valsi>terlantroge'u</valsi> above, even if he or she d= ecides to stick with a shorter, more convenient form like chapters/12.xml- <valsi>xanmi'e</valsi>. In addition, of course, the pos= sibilities of elliptical lujvo increase their potential ambiguity enormousl= y – an unavoidable fact which should be borne in mind.</para> chapters/12.xml- </section> *********************************************************************** xan= mi'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 o= f the longer lujvo, for which chapters/12.xml- <valsi>lange'u</valsi> can be understood as an abbrevia= tion.</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 compo= nent place structures are:</para> chapters/12.xml- chapters/12.xml- <example xml:id=3D"example-random-id-VjbP"> -- chapters/12.xml- </example> chapters/12.xml- <para role=3D"indent">The relation between the seltau a= nd 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 e= lided 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=3D"general"><primary>latent comp= onent</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 velj= vo. And it also means that, for a place structure derivation that actually = makes sense, rather than being ad-hoc, the Lojbanist should probably go thr= ough a derivation for chapters/12.xml- <valsi>xancypliminde</valsi> or one of the other possib= ilities that is analogous to the analysis of chapters/12.xml- <valsi>terlantroge'u</valsi> above, even if he or she d= ecides to stick with a shorter, more convenient form like chapters/12.xml: <valsi>xanmi'e</valsi>. In addition, of course, the pos= sibilities of elliptical lujvo increase their potential ambiguity enormousl= y – an unavoidable fact which should be borne in mind.</para> chapters/12.xml- </section> chapters/12.xml- <section xml:id=3D"section-comparatives"> chapters/12.xml- <title>Comparatives and superlatives *********************************************************************** xan= plimi'e chapters/12.xml- chapters/12.xml- chapters/12.xml- which lead to the three differe= nt lujvo chapters/12.xml: xanplimi'e, chapters/12.xml- mi'erxanpli, and chapters/12.xml- minkemxanpli respectively. chapters/12.xml- latent comp= onent Does this make *********************************************************************** xas= kemcakcurnu chapters/12.xml- chapters/12.xml- chapters/12.xml- shellfish<= /indexterm> There are cases, however, where omitting a KE or KEhE rafsi can= produce another lujvo, equally useful. For example, chapters/12.xml: xaskemcakcurnu means chapters/12.xml- oceanic shellfish, and has the veljvo chapters/12.xml- chapters/12.xml- *********************************************************************** xas= ycakcurnu chapters/12.xml- invertebrate ( chapters/12.xml- worm in Lojban refers to any invertebrat= e), but chapters/12.xml- chapters/12.xml: xasycakcurnu has the veljvo chapters/12.xml- chapters/12.xml- chapters/12.xml- *********************************************************************** xel= klama chapters/10.xml- <indexterm type=3D"example"><primary>boat sailed</p= rimary></indexterm> chapters/10.xml- chapters/10.xml- chapters/10.xml: le bloti pu za'o xelklama chapters/10.xml- The boat [past] [superfective] is-a-transpor= t-mechanism chapters/10.xml- chapters/10.xml- -- chapters/10.xml- chapters/10.xml- chapters/10.xml- Probably it sailed up onto the do= ck. One point of clarification: although chapters/10.xml: xelklama appears to mean simply chapters/10.xml- is-a-mode-of-transport, it does not &nda= sh; the bridi of chapters/10.xml- has four omi= tted arguments, and thus has the (physical) journey which goes on too long = as part of its meaning. chapters/10.xml- *********************************************************************** zil= pavypinxe chapters/07.xml- se pinxe be zi'o, the lujvo corr= esponding to this is chapters/07.xml- zilrelselpinxe (deleting the second plac= e of chapters/07.xml- se pinxe). Deleting the x1 place= in this fashion would move all remaining places up by one. This would mean= that chapters/07.xml: zilpavypinxe has the same place structur= e as chapters/07.xml- zilrelselpinxe, and chapters/07.xml: lo zilpavypinxe, like chapters/07.xml- lo zilrelselpinxe, refers to a b= everage, and not to a non-existent drinker. chapters/07.xml- chapters/07.xml- pro-bridi r= afsias producing context-dependent meanings The pro-bridi *********************************************************************** zil= relselpinxe chapters/07.xml- chapters/07.xml- chapters/07.xml- se pinxe be zi'o, the lujvo corr= esponding to this is chapters/07.xml: zilrelselpinxe (deleting the second plac= e of chapters/07.xml- se pinxe). Deleting the x1 place= in this fashion would move all remaining places up by one. This would mean= that chapters/07.xml- zilpavypinxe has the same place structur= e as chapters/07.xml: zilrelselpinxe, and chapters/07.xml- lo zilpavypinxe, like chapters/07.xml: lo zilrelselpinxe, refers to a b= everage, and not to a non-existent drinker. chapters/07.xml- chapters/07.xml- pro-bridi r= afsias producing context-dependent meanings The pro-bridi chapters/07.xml- co'e, *********************************************************************** zul= jamfu chapters/04.xml- The lujvo forms chapters/04.xml- zunlyjamfu, chapters/04.xml- zunlyjma, chapters/04.xml: zuljamfu, and chapters/04.xml- zuljma are all legitimate and equivalent= forms made from the tanru chapters/04.xml- zunle jamfu ( chapters/04.xml- left foot). Of these, *********************************************************************** zun= lyjamfu chapters/04.xml- to chapters/04.xml- .) chapters/04.xml- The lujvo forms chapters/04.xml: zunlyjamfu, chapters/04.xml- zunlyjma, chapters/04.xml- zuljamfu, and chapters/04.xml- zuljma are all legitimate and equivalent= forms made from the tanru *********************************************************************** zun= lyjma chapters/04.xml- .) chapters/04.xml- The lujvo forms chapters/04.xml- zunlyjamfu, chapters/04.xml: zunlyjma, chapters/04.xml- zuljamfu, and chapters/04.xml- zuljma are all legitimate and equivalent= forms made from the tanru chapters/04.xml- zunle jamfu ( --=20 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 --=20 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 e= mail 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.