[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bpfk] dag-cll git updates for Fri Jan 28 14:21:04 EST 2011

To: bpfk@lojban.org
Subject: [bpfk] dag-cll git updates for Fri Jan 28 14:21:04 EST 2011
From: www-data <www-data@oh-www1.lojban.org>
Date: Fri, 28 Jan 2011 14:21:05 -0500
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=domainkey-signature:mime-version:x-beenthere:received-spf:date :message-id:to:subject:from:x-spam_score:x-spam_score_int:x-spam_bar :x-spam_report:x-original-sender:x-original-authentication-results :reply-to:precedence:mailing-list:list-id:list-post:list-help :list-archive:sender:list-subscribe:list-unsubscribe:content-type :content-transfer-encoding; bh=8pWyHqdagAaHlrAB4jaSWyL3szBX/7NvUq7oLiLFRf0=; b=XGbsq39gHQg5p/rzJAXcroIc2thRbT2QO2WSAMcvobik+rjwyl55SlkhYA2gkDEQIV umsj+nucoDpwyCLKwHgCZNJsyLi18Nqo5PkVO8UOgXNZAUTPauejPbqpBPBvxIbxfXTL fHnee+guZeTyCR3w8DDVLFbnSWSkEPZNu3h/g=
Domainkey-signature: a=rsa-sha1; c=nofws; d=googlegroups.com; s=beta; h=mime-version:x-beenthere:received-spf:date:message-id:to:subject :from:x-spam_score:x-spam_score_int:x-spam_bar:x-spam_report :x-original-sender:x-original-authentication-results:reply-to :precedence:mailing-list:list-id:list-post:list-help:list-archive :sender:list-subscribe:list-unsubscribe:content-type :content-transfer-encoding; b=gWoF115sNhTaYopkdBcfv1gnWVdJ71yOvBEGeB52vIG5s6xZuGTY8PC1SHaKrd9tM1 1lwF8zJNUyZLWHliWI25n48404FAWotBPLvQ0fbvy9KuV3Y9VvfkSTo7xv8+r7ptHJsG mzYu+GPQpH1BRRERkhsGT4BayoG/0rUviCTm0=
List-archive: <http://groups.google.com/group/bpfk-list?hl=en_US>
List-help: <http://groups.google.com/support/?hl=en_US>, <mailto:bpfk-list+help@googlegroups.com>
List-id: <bpfk-list.googlegroups.com>
List-post: <http://groups.google.com/group/bpfk-list/post?hl=en_US>, <mailto:bpfk-list@googlegroups.com>
List-subscribe: <http://groups.google.com/group/bpfk-list/subscribe?hl=en_US>, <mailto:bpfk-list+subscribe@googlegroups.com>
List-unsubscribe: <http://groups.google.com/group/bpfk-list/subscribe?hl=en_US>, <mailto:bpfk-list+unsubscribe@googlegroups.com>
Mailing-list: list bpfk-list@googlegroups.com; contact bpfk-list+owners@googlegroups.com
Reply-to: bpfk-list@googlegroups.com
Sender: bpfk-list@googlegroups.com
commit bca3c55d550f31a81a8a57791ea730b98e9260af
Merge: 7125179 60bc622
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date:   Fri Jan 28 11:14:53 2011 -0800

    Merge commit '60bc6229b16509a10e364fda5f6b92b26484a0bd' into gh-pages

commit 712517939c0422e30ad830cbda5c1e6b18e422f6
Merge: 17bc769 81c3b6e
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date:   Fri Jan 28 11:14:45 2011 -0800

    Merge commit '81c3b6e12f8b6ebb43e1c1314e6224716979e03d' into gh-pages

commit 17bc769cef457483791769e19217a62d4308c1b1
Merge: 4319322 2b6f4ff
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date:   Fri Jan 28 10:32:16 2011 -0800

    Merge commit '2b6f4ff09c15210a1d2629011005432a25db9f94' into gh-pages

commit 4319322e06df25d64d1445b362f70a5f6e7f14f6
Merge: 4344396 b4eeb2f
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date:   Fri Jan 28 10:29:05 2011 -0800

    Merge commit 'b4eeb2f6a9118c3c1957199ea69b4f3fd498eaed' into gh-pages

commit 434439685aaf76e23e3de90335f3106181c8328f
Merge: 2e14acd ddc1332
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date:   Fri Jan 28 09:35:02 2011 -0800

    Merge commit 'ddc1332254c74ec6707af35828eb347ea68609c8' into gh-pages

commit 60bc6229b16509a10e364fda5f6b92b26484a0bd
Merge: ae030cb 18bc6ba
Author: Eitan Postavsky <eitanp32@gmail.com>
Date:   Sun Jan 2 19:18:26 2011 -0500

    Merge remote branch 'upstream/gh-pages' into gh-pages

commit ae030cb28b25758fd6c5d8c9c56a091ddeaf414f
Merge: 3d73c55 9c93002
Author: Eitan Postavsky <eitanp32@gmail.com>
Date:   Sun Jan 2 18:51:45 2011 -0500

    Merge remote branch 'upstream/gh-pages' into gh-pages

commit 3d73c5551dc9924dd32453256e6110a4ff3ba1f6
Merge: 81c3b6e 8edb95b
Author: Eitan Postavsky <eitanp32@gmail.com>
Date:   Sun Jan 2 18:45:57 2011 -0500

    Merge remote branch 'upstream/gh-pages' into gh-pages

commit 81c3b6e12f8b6ebb43e1c1314e6224716979e03d
Merge: 2b6f4ff 5ac80f6
Author: Eitan Postavsky <eitanp32@gmail.com>
Date:   Sun Jan 2 18:44:06 2011 -0500

    Merge remote branch 'upstream/gh-pages' into gh-pages

commit 2b6f4ff09c15210a1d2629011005432a25db9f94
Author: Eitan Postavsky <eitanp32@gmail.com>
Date:   Sun Jan 2 17:45:50 2011 -0500

    Chapter 4: section names and "example-imported"s; many FIXMEs.
    
    The FIXMEs are regarding various "example-imported"s, either where to
    put them or whether to duplicate them. Also, I put my progress in TODO
    like I was supposed to and changed an xref in chapter 20.

diff --git a/todocbook/20.xml b/todocbook/20.xml
index 538e8d0..b42aa71 100644
--- a/todocbook/20.xml
+++ b/todocbook/20.xml
@@ -1194,21 +1194,21 @@
     <bridgehead>
     <anchor xml:id="ZAhO"/> selma'o ZAhO ( 
     <xref linkend="cll_chapter10-section10"/>)</bridgehead>
     <para>A tense modifier specifying the contour of an event (e.g. beginning, ending, continuing).</para>
     <programlisting xml:space="preserve">
     mi pu'o damba
     I [inchoative] fight.
     I’m on the verge of fighting.
 </programlisting>
     <bridgehead>
-    <anchor xml:id="ZEI"/> selma'o ZEI (<xref linkend="chapter-morphology-section6"/>)</bridgehead>
+    <anchor xml:id="ZEI"/> selma'o ZEI (<xref linkend="chapter-morphology-section-rafsi"/>)</bridgehead>
     <para>A morphological glue word, which joins the two words it stands between into the equivalent of a lujvo.</para>
     
     <programlisting xml:space="preserve">
     ta xy. zei kantu kacma
     That is-an-(X - ray) camera.
     That is an X-ray camera.
 
 </programlisting>
     <bridgehead>
     <anchor xml:id="ZEhA"/> selma'o ZEhA ( 
diff --git a/todocbook/4.xml b/todocbook/4.xml
index ced2bca..19bd501 100644
--- a/todocbook/4.xml
+++ b/todocbook/4.xml
@@ -1,14 +1,14 @@
 <chapter xml:id="chapter-morphology">
   <title>The Shape Of Words To Come: Lojban Morphology</title>
   
-  <section xml:id="chapter-morphology-section1">
+  <section xml:id="section-introduction">
     <title>Introductory</title>
     <para> <indexterm type="general-imported"><primary>word forms</primary><secondary>in Lojban (see also morphology)</secondary></indexterm>  <indexterm type="general-imported"><primary>morphology</primary><secondary>definition</secondary></indexterm>  <indexterm type="general-imported"><primary>morphology</primary><secondary>simplicity of</secondary></indexterm> Morphology is the part of grammar that deals with the form of words. Lojban's morphology is fairly simple compared to that of many languages, because Lojban words don't change form depending on how they are used. English has only a small number of such changes compared to languages like Russian, but it does have changes like 
     <quote>boys</quote> as the plural of 
     
     <quote>boy</quote>, or 
     <quote>walked</quote> as the past-tense form of 
     <quote>walk</quote>. To make plurals or past tenses in Lojban, you add separate words to the sentence that express the number of boys, or the time when the walking was going on.</para>
     <para> <indexterm type="general-imported"><primary>word forms</primary><secondary>as related to grammatical uses</secondary></indexterm>  <indexterm type="general-imported"><primary>derivational morphology</primary><secondary>definition</secondary></indexterm>  <indexterm type="general-imported"><primary>morphology</primary><secondary>derivational</secondary></indexterm> However, Lojban does have what is called 
     <quote>derivational morphology</quote>: the capability of building new words from old words. In addition, the form of words tells us something about their grammatical uses, and sometimes about the means by which they entered the language. Lojban has very orderly rules for the formation of words of various types, both the words that already exist and new words yet to be created by speakers and writers.</para>
     
@@ -154,21 +154,21 @@
     <quote>the</quote> and 
     <jbophrase>to</jbophrase>; brivla are the content words, corresponding to English words like 
     <quote>come</quote>, 
     <quote>red</quote>, 
     <quote>doctor</quote>, and 
     <quote>freely</quote>; cmene are proper names, corresponding to English 
     <quote>James</quote>, 
     <quote>Afghanistan</quote>, and 
     <quote>Pope John Paul II</quote>.</para>
   </section>
-  <section xml:id="chapter-morphology-section2">
+  <section xml:id="section-cmavo">
     <title>cmavo</title>
     <para> <indexterm type="general-imported"><primary>punctuation marks</primary><secondary>cmavo as Lojban equivalents</secondary></indexterm>  <indexterm type="general-imported"><primary>numbers</primary><secondary>cmavo as Lojban equivalents</secondary></indexterm>  <indexterm type="general-imported"><primary>prepositions</primary><secondary>cmavo as Lojban equivalents</secondary></indexterm>  <indexterm type="general-imported"><primary>conjunctions</primary><secondary>cmavo as Lojban equivalents</secondary></indexterm>  <indexterm type="general-imported"><primary>articles</primary><secondary>cmavo as Lojban equivalents</secondary></indexterm>  <indexterm type="general-imported"><primary>structure words</primary></indexterm>  <indexterm type="general-imported"><primary>selma'o</primary><secondary>definition</secondary></indexterm>  <indexterm type="general-imported"><primary>cmavo</primary><secondary>definition</secondary></indexterm> The first group of Lojban words discussed in this chapter are the cmavo. They are the structure words that hold the Lojban language together. They often have no semantic meaning in themselves, though they may affect the semantics of brivla to which they are attached. The cmavo include the equivalent of English articles, conjunctions, prepositions, numbers, and punctuation marks. There are over a hundred subcategories of cmavo, known as 
     
     
     
     
     
     
     <jbophrase>selma'o</jbophrase>, each having a specifically defined grammatical usage. The various selma'o are discussed throughout 
     <xref linkend="chapter-selbri"/> to 
@@ -206,21 +206,21 @@
     
     <quote>ku'a'e</quote>, 
     
     <quote>sau'e</quote>, and 
     <quote>bai'ai</quote>. All CVV cmavo beginning with the letter 
     <quote>x</quote> are also reserved for experimental use. In general, though, the form of a cmavo tells you little or nothing about its grammatical use.</para>
     <para> <indexterm type="general-imported"><primary>experimental cmavo</primary><secondary>definition</secondary></indexterm>  <indexterm type="general-imported"><primary>cmavo</primary><secondary>experimental</secondary></indexterm> 
     <quote>Experimental use</quote> means that the language designers will not assign any standard meaning or usage to these words, and words and usages coined by Lojban speakers will not appear in official dictionaries for the indefinite future. Experimental-use words provide an escape hatch for adding grammatical mechanisms (as opposed to semantic concepts) the need for which was not foreseen.</para>
     <para> <indexterm type="general-imported"><primary>cmavo</primary><secondary>diphthongs in</secondary></indexterm> The cmavo of VV-form include not only the diphthongs and vowel pairs listed in 
     
-    <xref linkend="chapter-morphology-section1"/>, but also the following ten additional diphthongs:</para>
+    <xref linkend="section-introduction"/>, but also the following ten additional diphthongs:</para>
     <cmavo-list>
       <cmavo-entry>
         <cmavo>.ia .ie .ii</cmavo>
         <selmaho>.io</selmaho>
         <description>.iu</description>
       </cmavo-entry>
       <cmavo-entry>
         <cmavo>.ua .ue .ui</cmavo>
         
         <selmaho>.uo</selmaho>
@@ -296,21 +296,21 @@
     <example role="interlinear-gloss-example" xml:id="example-random-id-CtnR">
       <title>
         <anchor xml:id="c4e2d5"/>
       </title>
       <interlinear-gloss>
         <jbo>cy.ibu.abu</jbo>
         <en>cy. .ibu .abu</en>
       </interlinear-gloss>
     </example>
     <para>Again the pauses are required (see 
-    <xref linkend="chapter-morphology-section9"/>); the pause after 
+    <xref linkend="section-pauses"/>); the pause after 
     <jbophrase>cy.</jbophrase> merges with the pause before 
     <jbophrase>.ibu</jbophrase>.</para>
     <para> <indexterm type="general-imported"><primary>stress</primary><secondary>on cmavo</secondary></indexterm>  <indexterm type="general-imported"><primary>cmavo</primary><secondary>stress on</secondary></indexterm> There is no particular stress required in cmavo or their compounds. Some conventions do exist that are not mandatory. For two-syllable cmavo, for example, stress is typically placed on the first vowel; an example is</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-pdGY">
       <title>
         <anchor xml:id="c4e2d6"/>
       </title>
       <interlinear-gloss>
         <jbo>.e'o ko ko kurji</jbo>
         
@@ -362,42 +362,42 @@
     <example role="interlinear-gloss-example" xml:id="example-random-id-sg0p">
       <title>
         <anchor xml:id="c4e2d10"/>
       </title>
       <interlinear-gloss>
         <jbo>le re NANmu</jbo>
       </interlinear-gloss>
     </example>
     <para>This would probably be the most common usage.</para>
   </section>
-  <section xml:id="chapter-morphology-section3">
+  <section xml:id="section-brivla">
     <title>brivla</title>
     <para> <indexterm type="general-imported"><primary>adverbs</primary><secondary>brivla as Lojban equivalents</secondary></indexterm>  <indexterm type="general-imported"><primary>verbs</primary><secondary>brivla as Lojban equivalents</secondary></indexterm>  <indexterm type="general-imported"><primary>adjectives</primary><secondary>brivla as Lojban equivalents</secondary></indexterm>  <indexterm type="general-imported"><primary>nouns</primary><secondary>brivla as Lojban equivalents</secondary></indexterm>  <indexterm type="general-imported"><primary>brivla</primary><secondary>definition</secondary></indexterm> Predicate words, called 
     <jbophrase>brivla</jbophrase>, are at the core of Lojban. They carry most of the semantic information in the language. They serve as the equivalent of English nouns, verbs, adjectives, and adverbs, all in a single part of speech.</para>
     
     
     
     
     <para> <indexterm type="general-imported"><primary>subtypes of words</primary></indexterm>  <indexterm type="general-imported"><primary>types and subtypes of words</primary></indexterm> Every brivla belongs to one of three major subtypes. These subtypes are defined by the form, or morphology, of the word - all words of a particular structure can be assigned by sight or sound to a particular type (cmavo, brivla, or cmene) and subtype. Knowing the type and subtype then gives you, the reader or listener, significant clues to the meaning and the origin of the word, even if you have never heard the word before.</para>
     
     <para> <indexterm type="general-imported"><primary>flexible vocabulary</primary></indexterm> The same principle allows you, when speaking or writing, to invent new brivla for new concepts 
     <quote>on the fly</quote>; yet it offers people that you are trying to communicate with a good chance to figure out your meaning. In this way, Lojban has a flexible vocabulary which can be expanded indefinitely.</para>
     
     <para> <indexterm type="general-imported"><primary>brivla</primary><secondary>properties of</secondary></indexterm> All brivla have the following properties:</para>
     <orderedlist>
       <listitem>
         <para>always end in a vowel;</para>
       </listitem>
       <listitem>
         <para>always contain a consonant pair in the first five letters, where 
         <jbophrase>y</jbophrase> and apostrophe are not counted as letters for this purpose. (See 
-        <xref linkend="chapter-morphology-section6"/>.)</para>
+        <xref linkend="section-rafsi"/>.)</para>
       </listitem>
       <listitem>
         <para>always are stressed on the next-to-the-last (penultimate) syllable; this implies that they have two or more syllables.</para>
       </listitem>
     </orderedlist>
     <para> <indexterm type="general-imported"><primary>cmene form</primary><secondary>contrasted with brivla form</secondary></indexterm>  <indexterm type="general-imported"><primary>cmavo form</primary><secondary>contrasted with brivla form</secondary></indexterm>  <indexterm type="general-imported"><primary>brivla form</primary><secondary>contrasted with cmene form</secondary></indexterm>  <indexterm type="general-imported"><primary>brivla form</primary><secondary>contrasted with cmavo form</secondary></indexterm>  <indexterm type="general-imported"><primary>brivla</primary><secondary>recognition of</secondary></indexterm> The presence of a consonant pair distinguishes brivla from cmavo and their compounds. The final vowel distinguishes brivla from cmene, which always end in a consonant. Thus 
     <jbophrase>da'amei</jbophrase> must be a compound cmavo because it lacks a consonant pair; 
     <jbophrase>lojban.</jbophrase> must be a name because it lacks a final vowel.</para>
     <para> <indexterm type="general-imported"><primary>consonant pairs</primary><secondary>letter y within</secondary></indexterm>  <indexterm type="general-imported"><primary>y</primary><secondary>letter</secondary><tertiary>between letters of consonant pair</tertiary></indexterm>  <indexterm type="general-imported"><primary>consonant pairs</primary><secondary>in brivla</secondary></indexterm>  <indexterm type="general-imported"><primary>brivla</primary><secondary>consonant pairs in</secondary></indexterm> Thus, 
     <jbophrase>bisycla</jbophrase> has the consonant pair 
@@ -415,33 +415,33 @@
       </listitem>
       <listitem>
         <para> <indexterm type="general-imported"><primary>compound of gismu</primary><secondary>lujvo as</secondary></indexterm>  <indexterm type="general-imported"><primary>lujvo</primary><secondary>as a subtype of brivla</secondary></indexterm> lujvo, the compounds of two or more gismu; and</para>
       </listitem>
       <listitem>
         <para> <indexterm type="general-imported"><primary>borrowing from other language</primary><secondary>fu'ivla as</secondary></indexterm>  <indexterm type="general-imported"><primary>fu'ivla</primary><secondary>as a subtype of brivla</secondary></indexterm> fu'ivla (literally 
         <quote>copy-word</quote>), the specialized words that are not Lojban primitives or natural compounds, and are therefore borrowed from other languages.</para>
       </listitem>
     </orderedlist>
   </section>
-  <section xml:id="chapter-morphology-section4">
+  <section xml:id="section-gismu">
     <title>gismu</title>
     <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>rationale for choice of</secondary></indexterm>  <indexterm type="general-imported"><primary>gismu</primary><secondary>definition</secondary></indexterm> The gismu, or Lojban root words, are those brivla representing concepts most basic to the language. The gismu were chosen for various reasons: some represent concepts that are very familiar and basic; some represent concepts that are frequently used in other languages; some were added because they would be helpful in constructing more complex words; some because they represent fundamental Lojban concepts (like 
     <jbophrase>cmavo</jbophrase> and 
     <jbophrase>gismu</jbophrase> themselves).</para>
     <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>as partitioning semantic space</secondary></indexterm>  <indexterm type="general-imported"><primary>gismu</primary><secondary>selection of</secondary></indexterm> The gismu do not represent any sort of systematic partitioning of semantic space. Some gismu may be superfluous, or appear for historical reasons: the gismu list was being collected for almost 35 years and was only weeded out once. Instead, the intention is that the gismu blanket semantic space: they make it possible to talk about the entire range of human concerns.</para>
     <para> <indexterm type="general-imported"><primary>learning Lojban</primary><secondary>magnitude of task</secondary></indexterm>  <indexterm type="general-imported"><primary>cmavo and gismu</primary><secondary>major</secondary></indexterm>  <indexterm type="general-imported"><primary>gismu</primary><secondary>and cmavo</secondary><tertiary>major</tertiary></indexterm> There are about 1350 gismu. In learning Lojban, you need only to learn most of these gismu and their combining forms (known as 
     
     
     <jbophrase>rafsi</jbophrase>) as well as perhaps 200 major cmavo, and you will be able to communicate effectively in the language. This may sound like a lot, but it is a small number compared to the vocabulary needed for similar communications in other languages.</para>
     <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>rules for</secondary></indexterm> All gismu have very strong form restrictions. Using the conventions defined in 
-    <xref linkend="chapter-morphology-section1"/>, all gismu are of the forms CVC/CV or CCVCV. They must meet the rules for all brivla given in 
-    <xref linkend="chapter-morphology-section3"/>; furthermore, they:</para>
+    <xref linkend="section-introduction"/>, all gismu are of the forms CVC/CV or CCVCV. They must meet the rules for all brivla given in 
+    <xref linkend="section-brivla"/>; furthermore, they:</para>
     <orderedlist>
       <listitem>
         <para>always have five letters;</para>
       </listitem>
       <listitem>
         <para>always start with a consonant and end with a single vowel;</para>
       </listitem>
       <listitem>
         <para>always contain exactly one consonant pair, which is a permissible initial pair (CC) if it's at the beginning of the gismu, but otherwise only has to be a permissible pair (C/C);</para>
       </listitem>
@@ -458,21 +458,21 @@
     <jbophrase>brodo</jbophrase>, and 
     <jbophrase>brodu</jbophrase>, no two gismu differ only in the final vowel. Furthermore, the set of gismu was specifically designed to reduce the likelihood that two similar sounding gismu could be confused. For example, because 
     <jbophrase>gismu</jbophrase> is in the set of gismu, 
     <jbophrase>kismu</jbophrase>, 
     <jbophrase>xismu</jbophrase>, 
     <jbophrase>gicmu</jbophrase>, 
     <jbophrase>gizmu</jbophrase>, and 
     <jbophrase>gisnu</jbophrase> cannot be.</para>
     <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>source of</secondary></indexterm> Almost all Lojban gismu are constructed from pieces of words drawn from other languages, specifically Chinese, English, Hindi, Spanish, Russian, and Arabic, the six most widely spoken natural languages. For a given concept, words in the six languages that represent that concept were written in Lojban phonetics. Then a gismu was selected to maximize the recognizability of the Lojban word for speakers of the six languages by weighting the inclusion of the sounds drawn from each language by the number of speakers of that language. See 
     
-    <xref linkend="chapter-morphology-section14"/> for a full explanation of the algorithm.</para>
+    <xref linkend="section-gismu-making"/> for a full explanation of the algorithm.</para>
     <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>examples of</secondary></indexterm> Here are a few examples of gismu, with rough English equivalents (not definitions):</para>
     <example xml:id="example-random-id-qJ0x" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c4e4d1"/>
       </title>
       <interlinear-gloss>
         <jbo>creka</jbo>
         <en>shirt</en>
       </interlinear-gloss>
     </example>
@@ -533,75 +533,78 @@
     <example xml:id="example-random-id-qj71" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c4e4d8"/>
       </title>
       <interlinear-gloss>
         <jbo>ninmu</jbo>
         <en>woman</en>
       </interlinear-gloss>
     </example>
     <para>A small number of gismu were formed differently; see 
-    <xref linkend="chapter-morphology-section15"/> for a list.</para>
+    <xref linkend="section-cultural-gismu"/> for a list.</para>
   </section>
-  <section xml:id="chapter-morphology-section5">
+  <section xml:id="section-lujvo">
     <title>lujvo</title>
     <para> <indexterm type="general-imported"><primary>modifying brivla (see also seltau)</primary></indexterm>  <indexterm type="general-imported"><primary>seltau</primary><secondary>compared with English adverb</secondary></indexterm>  <indexterm type="general-imported"><primary>seltau</primary><secondary>compared with English adjective</secondary></indexterm>  <indexterm type="general-imported"><primary>tanru</primary><secondary>explanation of</secondary></indexterm> When specifying a concept that is not found among the gismu (or, more specifically, when the relevant gismu seems too general in meaning), a Lojbanist generally attempts to express the concept as a tanru. Lojban tanru are an elaboration of the concept of 
     <quote>metaphor</quote> used in English. In Lojban, any brivla can be used to modify another brivla. The first of the pair modifies the second. This modification is usually restrictive - the modifying brivla reduces the broader sense of the modified brivla to form a more narrow, concrete, or specific concept. Modifying brivla may thus be seen as acting like English adverbs or adjectives. For example,</para>
     
     
     <example role="interlinear-gloss-example" xml:id="example-random-id-xhQP">
       <title>
         <anchor xml:id="c4e5d1"/>
       </title>
       <interlinear-gloss>
         <jbo>skami pilno</jbo>
       </interlinear-gloss>
     </example>
     <para>is the tanru which expresses the concept of 
     <quote>computer user</quote>.</para>
     <para> <indexterm type="general-imported"><primary>tanru</primary><secondary>combination of</secondary></indexterm> The simplest Lojban tanru are pairings of two concepts or ideas. Such tanru take two simpler ideas that can be represented by gismu and combine them into a single more complex idea. Two-part tanru may then be recombined in pairs with other tanru, or with individual gismu, to form more complex or more specific ideas, and so on.</para>
     <para> <indexterm type="general-imported"><primary>tanru</primary><secondary>ambiguity of</secondary></indexterm> The meaning of a tanru is usually at least partly ambiguous: 
     <jbophrase>skami pilno</jbophrase> could refer to a computer that is a user, or to a user of computers. There are a variety of ways that the modifier component can be related to the modified component. It is also possible to use cmavo within tanru to provide variations (or to prevent ambiguities) of meaning.</para>
     <para> <indexterm type="general-imported"><primary>tanru</primary><secondary>and creativity</secondary></indexterm> Making tanru is essentially a poetic or creative act, not a science. While the syntax expressing the grouping relationships within tanru is unambiguous, tanru are still semantically ambiguous, since the rules defining the relationships between the gismu are flexible. The process of devising a new tanru is dealt with in detail in 
     <xref linkend="chapter-selbri"/>.</para>
-    <para> <indexterm type="example-imported"><primary>mother father</primary><secondary>example</secondary></indexterm>  <indexterm type="example-imported"><primary>father mother</primary><secondary>example</secondary></indexterm>  <indexterm type="example-imported"><primary>big boat</primary><secondary>example</secondary></indexterm>  <indexterm type="general-imported"><primary>tanru</primary><secondary>expression of</secondary></indexterm> To express a simple tanru, simply say the component gismu together. Thus the binary metaphor 
+    <para><indexterm type="general-imported"><primary>tanru</primary><secondary>expression of</secondary></indexterm> To express a simple tanru, simply say the component gismu together. Thus the binary metaphor 
     <quote>big boat</quote> becomes the tanru</para>
     
     <example role="interlinear-gloss-example" xml:id="example-random-id-oLE3">
       <title>
+        <indexterm type="example-imported"><primary>big boat</primary><secondary>example</secondary></indexterm>
         <anchor xml:id="c4e5d2"/>
       </title>
       <interlinear-gloss>
         <jbo>barda bloti</jbo>
       </interlinear-gloss>
     </example>
     <para>representing roughly the same concept as the English word 
     <quote>ship</quote>.</para>
     <para> <indexterm type="example-imported"><primary>paternal grandmother</primary><secondary>example</secondary></indexterm> The binary metaphor 
     <quote>father mother</quote> can refer to a paternal grandmother ( 
     
     
     <quote>a father-ly type of mother</quote>), while 
     <quote>mother father</quote> can refer to a maternal grandfather ( 
     
     <quote>a mother-ly type of father</quote>). In Lojban, these become the tanru</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-4wK9">
       <title>
+        <indexterm type="example-imported"><primary>father mother</primary><secondary>example</secondary></indexterm>
         <anchor xml:id="c4e5d3"/>
       </title>
       <interlinear-gloss>
         <jbo>patfu mamta</jbo>
       </interlinear-gloss>
     </example>
     <para>and</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-KQ4s">
       <title>
+        <indexterm type="example-imported"><primary>mother father</primary><secondary>example</secondary></indexterm>
         <anchor xml:id="c4e5d4"/>
       </title>
       <interlinear-gloss>
         <jbo>mamta patfu</jbo>
       </interlinear-gloss>
     </example>
     <para>respectively.</para>
     <para> <indexterm type="general-imported"><primary>tanru</primary><secondary>ambiguity in</secondary></indexterm> The possibility of semantic ambiguity can easily be seen in the last case. To interpret 
     <xref linkend="example-random-id-KQ4s"/>, the listener must determine what type of motherliness pertains to the father being referred to. In an appropriate context, 
     <jbophrase>mamta patfu</jbophrase> could mean not 
@@ -661,52 +664,53 @@
     <jbophrase>brivalsi</jbophrase>, 
     <jbophrase>bridyvla</jbophrase>, and 
     <jbophrase>bridyvalsi</jbophrase>, each of which uses a different combination of rafsi.</para>
     <para> <indexterm type="general-imported"><primary>apostrophe</primary><secondary>and consonant cluster determination in lujvo</secondary></indexterm>  <indexterm type="general-imported"><primary>' symbol</primary><secondary>and consonant cluster determination in lujvo</secondary></indexterm>  <indexterm type="general-imported"><primary>y-hyphen</primary><secondary>and consonant cluster determination</secondary></indexterm>  <indexterm type="general-imported"><primary>rafsi</primary><secondary>rules for combining to form lujvo</secondary></indexterm>  <indexterm type="general-imported"><primary>lujvo</primary><secondary>rules for formation of</secondary></indexterm> When assembling rafsi together into lujvo, the rules for valid brivla must be followed: a consonant cluster must occur in the first five letters (excluding 
     <jbophrase>y</jbophrase> and 
     <quote>'</quote>), and the lujvo must end in a vowel.</para>
     <para> <indexterm type="general-imported"><primary>glue in lujvo</primary><secondary>y-hyphen as</secondary></indexterm>  <indexterm type="general-imported"><primary>y-hyphen</primary><secondary>and stress determination</secondary></indexterm>  <indexterm type="general-imported"><primary>y-hyphen</primary><secondary>use of</secondary></indexterm> A 
     <jbophrase>y</jbophrase> (which is ignored in determining stress or consonant clusters) is inserted in the middle of the consonant cluster to glue the word together when the resulting cluster is either not permissible or the word is likely to break up. There are specific rules describing these conditions, detailed in 
     
     
-    <xref linkend="chapter-morphology-section6"/>.</para>
+    <xref linkend="section-rafsi"/>.</para>
     <para> <indexterm type="general-imported"><primary>glue in lujvo</primary><secondary>n-hyphen as</secondary></indexterm>  <indexterm type="general-imported"><primary>n-hyphen</primary><secondary>use of</secondary></indexterm>  <indexterm type="general-imported"><primary>glue in lujvo</primary><secondary>r-hyphen as</secondary></indexterm>  <indexterm type="general-imported"><primary>r-hyphen</primary><secondary>use of</secondary></indexterm> An 
     <quote>r</quote> (in some cases, an 
     <quote>n</quote>) is inserted when a CVV-form rafsi attaches to the beginning of a lujvo in such a way that there is no consonant cluster. For example, in the lujvo</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-3Qtv">
       <title>
+        <indexterm type="example-imported"><primary>field rations</primary><secondary>example</secondary></indexterm>
         <anchor xml:id="c4e5d8"/>
       </title>
       <interlinear-gloss>
         <jbo>soirsai</jbo>
         <gloss>sonci sanmi</gloss>
         <gloss>soldier meal</gloss>
         <en>field rations</en>
         
       </interlinear-gloss>
     </example>
-    <para> <indexterm type="example-imported"><primary>field rations</primary><secondary>example</secondary></indexterm>  <indexterm type="general-imported"><primary>cmavo</primary><secondary>contrasted with same-form rafsi in meaning</secondary></indexterm>  <indexterm type="general-imported"><primary>rafsi</primary><secondary>contrasted with same-form cmavo in meaning</secondary></indexterm> the rafsi 
+    <para>   <indexterm type="general-imported"><primary>cmavo</primary><secondary>contrasted with same-form rafsi in meaning</secondary></indexterm>  <indexterm type="general-imported"><primary>rafsi</primary><secondary>contrasted with same-form cmavo in meaning</secondary></indexterm> the rafsi 
     <quote>soi-</quote> and 
     <quote>-sai</quote> are joined, with the additional 
     
     <quote>r</quote> making up the 
     <quote>rs</quote> consonant pair needed to make the word a brivla. Without the 
     <quote>r</quote>, the word would break up into 
     <quote>soi sai</quote>, two cmavo. The pair of cmavo have no relation to their rafsi lookalikes; they will either be ungrammatical (as in this case), or will express a different meaning from what was intended.</para>
     
     <para>Learning rafsi and the rules for assembling them into lujvo is clearly seen to be necessary for fully using the potential Lojban vocabulary.</para>
     <para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>invention of</secondary></indexterm> Most important, it is possible to invent new lujvo while you speak or write in order to represent a new or unfamiliar concept, one for which you do not know any existing Lojban word. As long as you follow the rules for building these compounds, there is a good chance that you will be understood without explanation.</para>
   </section>
-  <section xml:id="chapter-morphology-section6">
+  <section xml:id="section-rafsi">
     <title>rafsi</title>
     <para> <indexterm type="general-imported"><primary>rafsi</primary><secondary>selection considerations in making lujvo</secondary></indexterm>  <indexterm type="general-imported"><primary>gismu</primary><secondary>level of uniqueness of rafsi relating to</secondary></indexterm>  <indexterm type="general-imported"><primary>rafsi</primary><secondary>level of uniqueness of relation to gismu</secondary></indexterm>  <indexterm type="general-imported"><primary>rafsi</primary><secondary>multiplicity of for single gismu</secondary></indexterm>  <indexterm type="general-imported"><primary>rafsi</primary><secondary>uniqueness in gismu referent of</secondary></indexterm>  <indexterm type="general-imported"><primary>rafsi</primary><secondary>use of</secondary></indexterm> Every gismu has from two to five rafsi, each of a different form, but each such rafsi represents only one gismu. It is valid to use any of the rafsi forms in building lujvo - whichever the reader or listener will most easily understand, or whichever is most pleasing - subject to the rules of lujvo making. There is a scoring algorithm which is intended to determine which of the possible and legal lujvo forms will be the standard dictionary form (see 
-    <xref linkend="chapter-morphology-section12"/>).</para>
+    <xref linkend="section-lujvo-scoring"/>).</para>
     <para> <indexterm type="general-imported"><primary>unreduced lujvo</primary><secondary>definition</secondary></indexterm>  <indexterm type="general-imported"><primary>long rafsi</primary><secondary>definition</secondary></indexterm>  <indexterm type="general-imported"><primary>4-letter rafsi</primary><secondary>definition</secondary></indexterm>  <indexterm type="general-imported"><primary>5-letter rafsi</primary><secondary>definition</secondary></indexterm>  <indexterm type="general-imported"><primary>gismu</primary><secondary>basic rafsi for</secondary></indexterm>  <indexterm type="general-imported"><primary>lujvo</primary><secondary>unreduced</secondary></indexterm>  <indexterm type="general-imported"><primary>rafsi</primary><secondary>long</secondary></indexterm>  <indexterm type="general-imported"><primary>rafsi</primary><secondary>forms of</secondary></indexterm> Each gismu always has at least two rafsi forms; one is the gismu itself (used only at the end of a lujvo), and one is the gismu without its final vowel (used only at the beginning or middle of a lujvo). These forms are represented as CVC/CV or CCVCV (called 
     <quote>the 5-letter rafsi</quote>), and CVC/C or CCVC (called 
     <quote>the 4-letter rafsi</quote>) respectively. The dashes in these rafsi form representations show where other rafsi may be attached to form a valid lujvo. When lujvo are formed only from 4-letter and 5-letter rafsi, known collectively as 
     
     <quote>long rafsi</quote>, they are called 
     
     <quote>unreduced lujvo</quote>.</para>
     
     <para>Some examples of unreduced lujvo forms are:</para>
     
@@ -759,33 +763,34 @@
         <jbo>prunyplipe</jbo>
         <gloss>from 
         <jbophrase>pruni plipe</jbophrase></gloss>
         <en>
           <quote>elastic (springy) leap</quote> or 
         <quote>spring</quote> (the verb)</en>
       </interlinear-gloss>
     </example>
     <example xml:id="example-random-id-qjbP" role="interlinear-gloss-example">
       <title>
+        <indexterm type="example-imported"><primary>supper</primary><secondary>example</secondary></indexterm>
         <anchor xml:id="c4e6d5"/>
       </title>
       <interlinear-gloss>
         <jbo>vancysanmi</jbo>
         <gloss>from 
         <jbophrase>vanci sanmi</jbophrase></gloss>
         <en>
           <quote>evening meal</quote> or 
         <quote>supper</quote></en>
         
       </interlinear-gloss>
     </example>
-    <para> <indexterm type="example-imported"><primary>supper</primary><secondary>example</secondary></indexterm>  <indexterm type="general-imported"><primary>short rafsi</primary></indexterm>  <indexterm type="general-imported"><primary>rafsi</primary><secondary>short</secondary></indexterm> In addition to these two forms, each gismu may have up to three additional short rafsi, three letters long. All short rafsi have one of the forms CVC, CCV, or CVV. The total number of rafsi forms that are assigned to a gismu depends on how useful the gismu is, or is presumed to be, in making lujvo, when compared to other gismu that could be assigned the rafsi.</para>
+    <para>   <indexterm type="general-imported"><primary>short rafsi</primary></indexterm>  <indexterm type="general-imported"><primary>rafsi</primary><secondary>short</secondary></indexterm> In addition to these two forms, each gismu may have up to three additional short rafsi, three letters long. All short rafsi have one of the forms CVC, CCV, or CVV. The total number of rafsi forms that are assigned to a gismu depends on how useful the gismu is, or is presumed to be, in making lujvo, when compared to other gismu that could be assigned the rafsi.</para>
     <para> <indexterm type="general-imported"><primary>-er</primary><secondary>use of zmadu in forming</secondary></indexterm>  <indexterm type="general-imported"><primary>comparatives</primary><secondary>use of zmadu in forming</secondary></indexterm> For example, 
     <jbophrase>zmadu</jbophrase> ( 
     <quote>more than</quote>) has the two short rafsi 
     <quote>zma</quote> and 
     <jbophrase>mau</jbophrase> (in addition to its unreduced rafsi 
     
     <quote>zmad</quote> and 
     <jbophrase>zmadu</jbophrase>), because a vast number of lujvo have been created based on 
     <jbophrase>zmadu</jbophrase>, corresponding in general to English comparative adjectives ending in 
     
@@ -879,21 +884,21 @@
         <description>-bla-</description>
       </cmavo-entry>
     </cmavo-list>
     <para> <indexterm type="general-imported"><primary>rafsi assignments</primary><secondary>non-reassignability of</secondary></indexterm> (In fact, 
     <jbophrase>blaci</jbophrase> has none of these short rafsi; they are all assigned to other gismu. Lojban speakers are not free to reassign any of the rafsi; the tables shown here are to help understand how the rafsi were chosen in the first place.)</para>
     <para> <indexterm type="general-imported"><primary>rafsi</primary><secondary>considerations restricting construction of</secondary></indexterm> There are a few restrictions: a CVV-form rafsi without an apostrophe cannot exist unless the vowels make up one of the four diphthongs 
     <jbophrase>ai</jbophrase>, 
     <jbophrase>ei</jbophrase>, 
     <jbophrase>oi</jbophrase>, or 
     <jbophrase>au</jbophrase>; and a CCV-form rafsi is possible only if the two consonants form a permissible initial consonant pair (see 
-    <xref linkend="chapter-morphology-section1"/>). Thus 
+    <xref linkend="section-introduction"/>). Thus 
     <jbophrase>mamta</jbophrase>, which has the same form as 
     <jbophrase>salci</jbophrase>, can only have 
     <quote>mam</quote>, 
     <quote>mat</quote>, and 
     <jbophrase>ma'a</jbophrase> as possible rafsi: in fact, only 
     
     <quote>mam</quote> is assigned to it.</para>
     <para> <indexterm type="general-imported"><primary>numbers</primary><secondary>rafsi for</secondary></indexterm>  <indexterm type="general-imported"><primary>rafsi for numbers</primary></indexterm> Some cmavo also have associated rafsi, usually CVC-form. For example, the ten common numerical digits, which are all CV form cmavo, each have a CVC-form rafsi formed by adding a consonant to the cmavo. Most cmavo that have rafsi are ones used in composing tanru (for a complete list, see 
     <xref linkend="chapter-lujvo"/>).</para>
     <para> <indexterm type="general-imported"><primary>fully reduced lujvo</primary><secondary>definition</secondary></indexterm>  <indexterm type="general-imported"><primary>lujvo</primary><secondary>fully reduced</secondary></indexterm> The term for a lujvo made up solely of short rafsi is 
@@ -1038,89 +1043,95 @@
       <interlinear-gloss>
         <jbo>bridi zei valsi</jbo>
       </interlinear-gloss>
     </example>
     <para> <indexterm type="general-imported"><primary>cmavo without rafsi</primary><secondary>method of including in lujvo</secondary></indexterm>  <indexterm type="general-imported"><primary>fu'ivla</primary><secondary>method of including in lujvo</secondary></indexterm>  <indexterm type="general-imported"><primary>cmene</primary><secondary>method of including in lujvo</secondary></indexterm>  <indexterm type="general-imported"><primary>rafsi</primary><secondary>lack of</secondary><tertiary>effect on forming lujvo</tertiary></indexterm>  <indexterm type="general-imported"><primary>lujvo</primary><secondary>from cmavo with no rafsi</secondary></indexterm> is the exact equivalent of 
     <jbophrase>brivla</jbophrase> (but not necessarily the same as the underlying tanru 
     <jbophrase>bridi valsi</jbophrase>, which could have other meanings.) Using 
     <quote>zei</quote> is the only way to get a cmavo lacking a rafsi, a cmene, or a fu'ivla into a lujvo:</para>
     <example xml:id="example-random-id-qJe1" role="interlinear-gloss-example">
       <title>
+        <indexterm type="example-imported"><primary>X-ray</primary><secondary>example</secondary></indexterm>
         <anchor xml:id="c4e6d13"/>
       </title>
       <interlinear-gloss>
         <jbo>xy. zei kantu</jbo>
         <en>X ray</en>
       </interlinear-gloss>
     </example>
     <example xml:id="example-random-id-qJeE" role="interlinear-gloss-example">
       <title>
+        <indexterm type="example-imported"><primary>Persian rug</primary><secondary>example</secondary></indexterm>
+        <indexterm type="example-imported"><primary>rug</primary><secondary>Persian</secondary><tertiary>example</tertiary></indexterm>
         <anchor xml:id="c4e6d14"/>
       </title>
       <interlinear-gloss>
         <jbo>kulnr,farsi zei lolgai</jbo>
         <gloss>Farsi floor-cover</gloss>
         <en>Persian rug</en>
         
         
         
         
       </interlinear-gloss>
     </example>
     <example xml:id="example-random-id-qJef" role="interlinear-gloss-example">
       <title>
+        <indexterm type="example-imported"><primary>hepatitis</primary><secondary>example</secondary></indexterm>
         <anchor xml:id="c4e6d15"/>
       </title>
       <interlinear-gloss>
         <jbo>na'e zei .a zei na'e zei by. livgyterbilma</jbo>
         <gloss>non-A, non-B liver-disease</gloss>
         <en>non-A, non-B hepatitis</en>
         
       </interlinear-gloss>
     </example>
     <example xml:id="example-random-id-qJEh" role="interlinear-gloss-example">
       <title>
+        <indexterm type="example-imported"><primary>Sherman tank</primary><secondary>example</secondary></indexterm>
+        <indexterm type="example-imported"><primary>tank</primary><secondary>Sherman</secondary><tertiary>example</tertiary></indexterm>
         <anchor xml:id="c4e6d16"/>
       </title>
       <interlinear-gloss>
         <jbo>.cerman. zei jamkarce</jbo>
         <gloss>Sherman war-car</gloss>
         <en>Sherman tank</en>
         
         
         
         
       </interlinear-gloss>
     </example>
-    <para> <indexterm type="example-imported"><primary>tank</primary><secondary>Sherman</secondary><tertiary>example</tertiary></indexterm>  <indexterm type="example-imported"><primary>Sherman tank</primary><secondary>example</secondary></indexterm>  <indexterm type="example-imported"><primary>hepatitis</primary><secondary>example</secondary></indexterm>  <indexterm type="example-imported"><primary>rug</primary><secondary>Persian</secondary><tertiary>example</tertiary></indexterm>  <indexterm type="example-imported"><primary>Persian rug</primary><secondary>example</secondary></indexterm>  <indexterm type="example-imported"><primary>X-ray</primary><secondary>example</secondary></indexterm> 
-    <xref linkend="example-random-id-qJef"/> is particularly noteworthy because the phrase that would be produced by removing the 
+    <para><xref linkend="example-random-id-qJef"/> is particularly noteworthy because the phrase that would be produced by removing the 
     <quote>zei</quote> s from it doesn't end with a brivla, and in fact is not even grammatical. As written, the example is a tanru with two components, but by adding a 
     <quote>zei</quote> between 
     <jbophrase>by.</jbophrase> and 
     <jbophrase>livgyterbilma</jbophrase> to produce</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-Wnaz">
       <title>
+        <indexterm type="example-imported"><primary>hepatitis</primary><secondary>example</secondary></indexterm>
         <anchor xml:id="c4e6d17"/>
       </title>
       <interlinear-gloss>
         <jbo>na'e zei .a zei na'e zei by. zei livgyterbilma</jbo>
         <en>non-A-non-B-hepatitis</en>
         
       </interlinear-gloss>
     </example>
     <para>the whole phrase would become a single lujvo. The longer lujvo of 
     <xref linkend="example-random-id-Wnaz"/> may be preferable, because its place structure can be built from that of 
     <jbophrase>bilma</jbophrase>, whereas the place structure of a lujvo without a brivla must be constructed ad hoc.</para>
     <para> <indexterm type="general-imported"><primary>cmavo</primary><secondary>contrasted with rafsi in usage</secondary></indexterm>  <indexterm type="general-imported"><primary>rafsi</primary><secondary>contrasted with cmavo in usage</secondary></indexterm>  <indexterm type="general-imported"><primary>rafsi</primary><secondary>contrasted with words</secondary></indexterm> Note that rafsi may not be used in 
     <quote>zei</quote> phrases, because they are not words. CVV rafsi look like words (specifically cmavo) but there can be no confusion between the two uses of the same letters, because cmavo appear only as separate words or in compound cmavo (which are really just a notation for writing separate but closely related words as if they were one); rafsi appear only as parts of lujvo.</para>
   </section>
-  <section xml:id="chapter-morphology-section7">
+  <section xml:id="section-fuhivla">
     <title>fu'ivla</title>
     <para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>unsuitability of for concrete/specific terms and jargon</secondary></indexterm>  <indexterm type="general-imported"><primary>food</primary><secondary>use of fu'ivla for specific</secondary></indexterm>  <indexterm type="general-imported"><primary>animals</primary><secondary>use of fu'ivla for specific</secondary></indexterm>  <indexterm type="general-imported"><primary>plants</primary><secondary>use of fu'ivla for specific</secondary></indexterm>  <indexterm type="general-imported"><primary>jargon</primary><secondary>use of fu'ivla for</secondary></indexterm>  <indexterm type="general-imported"><primary>specific terms</primary><secondary>use of fu'ivla for</secondary></indexterm>  <indexterm type="general-imported"><primary>concrete terms</primary><secondary>use of fu'ivla for</secondary></indexterm>  <indexterm type="general-imported"><primary>fu'ivla</primary><secondary>use of</secondary></indexterm> The use of tanru or lujvo is not always appropriate for very concrete or specific terms (e.g. 
     
     <quote>brie</quote> or 
     
     <quote>cobra</quote>), or for jargon words specialized to a narrow field (e.g. 
     
     
     <quote>quark</quote>, 
     
@@ -1139,58 +1150,58 @@
       </title>
       <interlinear-gloss>
         <jbo>me la'o ly. spaghetti .ly.</jbo>
         
       </interlinear-gloss>
     </example>
     <para> <indexterm type="general-imported"><primary>spaghetti</primary></indexterm> is a predicate with the place structure 
     <quote>x1 is a quantity of spaghetti</quote>.</para>
     
     <para> <indexterm type="general-imported"><primary>borrowings</primary><secondary>Stage 2</secondary></indexterm>  <indexterm type="general-imported"><primary>borrowings</primary><secondary>using lojbanized name</secondary></indexterm> Stage 2 involves changing the foreign name to a Lojbanized name, as explained in 
-    <xref linkend="chapter-morphology-section8"/>:</para>
+    <xref linkend="section-cmene"/>:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-zijY">
       <title>
         <anchor xml:id="c4e7d2"/>
       </title>
       <interlinear-gloss>
         <jbo>me la spagetis.</jbo>
       </interlinear-gloss>
     </example>
     <para>One of these expedients is often quite sufficient when you need a word quickly in conversation. (This can make it easier to get by when you do not yet have full command of the Lojban vocabulary, provided you are talking to someone who will recognize the borrowing.)</para>
     
     <para> <indexterm type="general-imported"><primary>fu'ivla</primary><secondary>as Stage 3 borrowings</secondary></indexterm>  <indexterm type="general-imported"><primary>borrowings</primary><secondary>Stage 3</secondary></indexterm>  <indexterm type="general-imported"><primary>borrowings</primary><secondary>fu'ivla form with categorizing rafsi</secondary></indexterm> Where a little more universality is desired, the word to be borrowed must be Lojbanized into one of several permitted forms. A rafsi is then usually attached to the beginning of the Lojbanized form, using a hyphen to ensure that the resulting word doesn't fall apart.</para>
     <para> <indexterm type="general-imported"><primary>borrowings</primary><secondary>most common form for</secondary></indexterm>  <indexterm type="general-imported"><primary>fu'ivla</primary><secondary>uniqueness of meaning in</secondary></indexterm>  <indexterm type="general-imported"><primary>rafsi</primary><secondary>as fu'ivla categorizer</secondary></indexterm>  <indexterm type="general-imported"><primary>fu'ivla categorizer</primary></indexterm> The rafsi categorizes or limits the meaning of the fu'ivla; otherwise a word having several different jargon meanings in other languages would require the word-inventor to choose which meaning should be assigned to the fu'ivla, since fu'ivla (like other brivla) are not permitted to have more than one definition. Such a Stage 3 borrowing is the most common kind of fu'ivla.</para>
     
     
     <para> <indexterm type="general-imported"><primary>fu'ivla</primary><secondary>as Stage 4 borrowings</secondary></indexterm>  <indexterm type="general-imported"><primary>borrowings</primary><secondary>Stage 4</secondary></indexterm>  <indexterm type="general-imported"><primary>borrowings</primary><secondary>fu'ivla form without categorizing rafsi</secondary></indexterm> Finally, Stage 4 fu'ivla do not have any rafsi classifier, and are used where a fu'ivla has become so common or so important that it must be made as short as possible. (See 
-    <xref linkend="chapter-morphology-section16"/> for a proposal concerning Stage 4 fu'ivla.)</para>
+    <xref linkend="section-rafsi-fuhivla"/> for a proposal concerning Stage 4 fu'ivla.)</para>
     <para> <indexterm type="general-imported"><primary>fu'ivla</primary><secondary>form of</secondary></indexterm>  <indexterm type="general-imported"><primary>fu'ivla</primary><secondary>construction of</secondary></indexterm> The form of a fu'ivla reliably distinguishes it from both the gismu and the cmavo. Like cultural gismu, fu'ivla are generally based on a word from a single non-Lojban language. The word is 
     <quote>borrowed</quote> (actually 
     <quote>copied</quote>, hence the Lojban tanru 
     <jbophrase>fukpi valsi</jbophrase>) from the other language and Lojbanized - the phonemes are converted to their closest Lojban equivalent and modifications are made as necessary to make the word a legitimate Lojban fu'ivla-form word. All fu'ivla:</para>
     <orderedlist>
       <listitem>
         <para> <indexterm type="general-imported"><primary>fu'ivla</primary><secondary>initial consonant cluster in</secondary></indexterm>  <indexterm type="general-imported"><primary>fu'ivla</primary><secondary>rules for formation of</secondary></indexterm> must contain a consonant cluster in the first five letters of the word; if this consonant cluster is at the beginning, it must either be a permissible initial consonant pair, or a longer cluster such that each pair of adjacent consonants in the cluster is a permissible initial consonant pair: 
         <quote>spraile</quote> is acceptable, but not 
         <quote>ktraile</quote> or 
         <quote>trkaile</quote>;</para>
       </listitem>
       <listitem>
         <para>must end in one or more vowels;</para>
       </listitem>
       <listitem>
         <para> <indexterm type="general-imported"><primary>slinku'i test</primary><secondary>definition</secondary></indexterm> must not be gismu or lujvo, or any combination of cmavo, gismu, and lujvo; furthermore, a fu'ivla with a CV cmavo joined to the front of it must not have the form of a lujvo (the so-called 
         <quote>slinku'i test</quote>, not discussed further in this book);</para>
         
       </listitem>
       <listitem>
-        <para> <indexterm type="example-imported"><primary>syllabic pronunciations of consonants</primary><secondary>in fu'ivla</secondary><tertiary>example</tertiary></indexterm>  <indexterm type="general-imported"><primary>y</primary><secondary>letter</secondary><tertiary>prohibition from fu'ivla</tertiary></indexterm> cannot contain 
+        <para><!-- FIXME: this indexterm fits with five different examples (further down); should it go in all five or just the first? --><indexterm type="example-imported"><primary>syllabic pronunciations of consonants</primary><secondary>in fu'ivla</secondary><tertiary>example</tertiary></indexterm>  <indexterm type="general-imported"><primary>y</primary><secondary>letter</secondary><tertiary>prohibition from fu'ivla</tertiary></indexterm> cannot contain 
         <jbophrase>y</jbophrase>, although they may contain syllabic pronunciations of Lojban consonants;</para>
       </listitem>
       <listitem>
         <para> <indexterm type="general-imported"><primary>fu'ivla</primary><secondary>stress in</secondary></indexterm> like other brivla, are stressed on the penultimate syllable.</para>
       </listitem>
     </orderedlist>
     <para> <indexterm type="general-imported"><primary>fu'ivla</primary><secondary>consonant clusters in</secondary></indexterm> Note that consonant triples or larger clusters that are not at the beginning of a fu'ivla can be quite flexible, as long as all consonant pairs are permissible. There is no need to restrict fu'ivla clusters to permissible initial pairs except at the beginning.</para>
     
     
     <para> <indexterm type="general-imported"><primary>borrowings</primary><secondary>Stage 3 contrasted with Stage 4 in ease of construction</secondary></indexterm>  <indexterm type="general-imported"><primary>fu'ivla</primary><secondary>categorized contrasted with uncategorized in ease of construction</secondary></indexterm> This is a fairly liberal definition and allows quite a lot of possibilities within 
@@ -1220,98 +1231,105 @@
         <quote>n</quote> (or vice versa), or if the rafsi ends in "r" and the rest of the fu'ivla begins with "tc", "ts", "dj", or "dz" (using "n" would result in a phonotactically impermissible cluster), use an 
         <quote>l</quote>-hyphen. (This is the only use of 
         <quote>l</quote>-hyphen in Lojban.)</para>
         <para>Alternatively, if a CVC-form short rafsi is available it can be used instead of the long rafsi.</para>
         
       </listitem>
       <listitem>
         <para>Remember that the stress necessarily appears on the penultimate (next-to-the-last) syllable.</para>
       </listitem>
     </orderedlist>
-    <para> <indexterm type="example-imported"><primary>syllabic pronunciations of consonants</primary><secondary>in fu'ivla category attachment</secondary><tertiary>example</tertiary></indexterm> In this section, the hyphen is set off with commas in the examples, but these commas are not required in writing, and the hyphen need not be pronounced as a separate syllable.</para>
+    <para>  In this section, the hyphen is set off with commas in the examples, but these commas are not required in writing, and the hyphen need not be pronounced as a separate syllable.</para>
     <para>Here are a few examples:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-ufin">
       <title>
+        <indexterm type="example-imported"><primary>spaghetti</primary><secondary>example</secondary></indexterm>
+        <indexterm type="example-imported"><primary>syllabic pronunciations of consonants</primary><secondary>in fu'ivla category attachment</secondary><tertiary>example</tertiary></indexterm> <!-- FIXME: this indexterm fits with five different examples; should it go in all five or just the first? -->
         <anchor xml:id="c4e7d3"/>
       </title>
       <interlinear-gloss>
         <jbo>spaghetti (from English or Italian)</jbo>
         
         <gloss>spageti (Lojbanize)</gloss>
         <gloss>cidj,r,spageti (prefix long rafsi)</gloss>
         
         <en>dja,r,spageti (prefix short rafsi)</en>
       </interlinear-gloss>
     </example>
-    <para> <indexterm type="example-imported"><primary>spaghetti</primary><secondary>example</secondary></indexterm> where 
+    <para>  where 
     <quote>cidj-</quote> is the 4-letter rafsi for 
     <jbophrase>cidja</jbophrase>, the Lojban gismu for 
     <quote>food</quote>, thus categorizing 
     <jbophrase>cidjrspageti</jbophrase> as a kind of food. The form with the short rafsi happens to work, but such good fortune cannot be relied on: in any event, it means the same thing.</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-pzXe">
       <title>
+        <indexterm type="example-imported"><primary>maple trees</primary><secondary>example</secondary></indexterm>
+        <indexterm type="example-imported"><primary>Acer</primary><secondary>example</secondary></indexterm>
+        <indexterm type="example-imported"><primary>maple sugar</primary><secondary>example</secondary></indexterm>
         <anchor xml:id="c4e7d4"/>
       </title>
       <interlinear-gloss>
         <jbo>Acer (the scientific name of maple trees)</jbo>
         
         
         <gloss>acer (Lojbanize)</gloss>
         <gloss>xaceru (add initial consonant and final vowel)</gloss>
         <gloss>tric,r,xaceru (prefix rafsi)</gloss>
         <en>ric,r,xaceru (prefix short rafsi)</en>
       </interlinear-gloss>
     </example>
-    <para> <indexterm type="example-imported"><primary>maple sugar</primary><secondary>example</secondary></indexterm>  <indexterm type="example-imported"><primary>Acer</primary><secondary>example</secondary></indexterm>  <indexterm type="example-imported"><primary>maple trees</primary><secondary>example</secondary></indexterm> where 
+    <para>where 
     <quote>tric-</quote> and 
     <quote>ric-</quote> are rafsi for 
     <jbophrase>tricu</jbophrase>, the gismu for 
     <quote>tree</quote>. Note that by the same principles, 
     <quote>maple sugar</quote> could get the fu'ivla 
     
     <jbophrase>saktrxaceru</jbophrase>, or could be represented by the tanru 
     <jbophrase>tricrxaceru sakta</jbophrase>. Technically, 
     <jbophrase>ricrxaceru</jbophrase> and 
     <jbophrase>tricrxaceru</jbophrase> are distinct fu'ivla, but they would surely be given the same meanings if both happened to be in use.</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-C0YS">
       <title>
+        <indexterm type="example-imported"><primary>brie</primary><secondary>example</secondary></indexterm>
         <anchor xml:id="c4e7d5"/>
       </title>
       <interlinear-gloss>
         <jbo>brie (from French)</jbo>
         
         <gloss>bri (Lojbanize)</gloss>
         <en>cirl,r,bri (prefix rafsi)</en>
       </interlinear-gloss>
     </example>
-    <para> <indexterm type="example-imported"><primary>brie</primary><secondary>example</secondary></indexterm> where 
+    <para>  where 
     <quote>cirl-</quote> represents 
     <jbophrase>cirla</jbophrase> ( 
     <quote>cheese</quote>).</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-DQju">
       <title>
+        <indexterm type="example-imported"><primary>cobra</primary><secondary>example</secondary></indexterm>
         <anchor xml:id="c4e7d6"/>
       </title>
       <interlinear-gloss>
         <jbo>cobra</jbo>
         
         <gloss>kobra (Lojbanize)</gloss>
         <en>sinc,r,kobra (prefix rafsi)</en>
       </interlinear-gloss>
     </example>
-    <para> <indexterm type="example-imported"><primary>cobra</primary><secondary>example</secondary></indexterm> where 
+    <para>  where 
     <quote>sinc-</quote> represents 
     <jbophrase>since</jbophrase> ( 
     <quote>snake</quote>).</para>
-    <para> <indexterm type="example-imported"><primary>quark</primary><secondary>example</secondary></indexterm> FIXME: TAG SPOT</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-TFzH">
       <title>
+        <indexterm type="example-imported"><primary>quark</primary><secondary>example</secondary></indexterm>
         <anchor xml:id="c4e7d7"/>
       </title>
       <interlinear-gloss>
         <jbo>quark</jbo>
         
         <gloss>kuark (Lojbanize)</gloss>
         <gloss>kuarka (add final vowel)</gloss>
         <en>sask,r,kuarka (prefix rafsi)</en>
       </interlinear-gloss>
     </example>
@@ -1346,21 +1364,21 @@
     <para> <indexterm type="general-imported"><primary>fu'ivla categorizer</primary><secondary>for distinguishing specialized meanings</secondary></indexterm> For another example, 
     <quote>integral</quote> has a specific meaning to a mathematician. But the Lojban fu'ivla 
     
     <quote>integrale</quote>, which is a valid Stage 4 fu'ivla, does not convey that mathematical sense to a non-mathematical listener, even one with an English-speaking background; its source - the English word 
     <quote>integral</quote>- has various other specialized meanings in other fields.</para>
     
     <para>Left uncontrolled, 
     <quote>integrale</quote> almost certainly would eventually come to mean the same collection of loosely related concepts that English associates with 
     <quote>integral</quote>, with only the context to indicate (possibly) that the mathematical term is meant.</para>
     
-    <para> <indexterm type="example-imported"><primary>integral</primary><secondary>architectural concept</secondary><tertiary>example</tertiary></indexterm>  <indexterm type="example-imported"><primary>integral</primary><secondary>mathematical concept</secondary><tertiary>example</tertiary></indexterm> The prefix method would render the mathematical concept as 
+    <para> <!-- FIXME: there's nowhere for these two indexterms to go --><indexterm type="example-imported"><primary>integral</primary><secondary>architectural concept</secondary><tertiary>example</tertiary></indexterm>  <indexterm type="example-imported"><primary>integral</primary><secondary>mathematical concept</secondary><tertiary>example</tertiary></indexterm> The prefix method would render the mathematical concept as 
     <jbophrase>cmacrntegrale</jbophrase>, if the 
     <jbophrase>i</jbophrase> of 
     <quote>integrale</quote> is removed, or something like 
     <jbophrase>cmacrnintegrale</jbophrase>, if a new consonant is added to the beginning; 
     <quote>cmac-</quote> is the rafsi for 
     <jbophrase>cmaci</jbophrase> ( 
     <quote>mathematics</quote>). The architectural sense of 
     <quote>integral</quote> might be conveyed with 
     
     <jbophrase>djinrnintegrale</jbophrase> or 
@@ -1385,159 +1403,172 @@
         <anchor xml:id="c4e7d10"/>
       </title>
       <interlinear-gloss>
         <jbo>kuln,r,blgaria</jbo>
         <en>Bulgarian (in culture)</en>
         
       </interlinear-gloss>
     </example>
     <example xml:id="example-random-id-qjGf" role="interlinear-gloss-example">
       <title>
+        <indexterm type="example-imported"><primary>Bulgarian</primary><secondary>example</secondary></indexterm>
         <anchor xml:id="c4e7d11"/>
       </title>
       <interlinear-gloss>
         <jbo>gugd,r,blgaria</jbo>
         <en>Bulgaria (the country)</en>
       </interlinear-gloss>
     </example>
     <example xml:id="example-random-id-qJGv" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c4e7d12"/>
       </title>
       <interlinear-gloss>
         <jbo>bang,r,kore,a</jbo>
         <en>Korean (the language)</en>
         
       </interlinear-gloss>
     </example>
     <example xml:id="example-random-id-qjh0" role="interlinear-gloss-example">
       <title>
+        <indexterm type="example-imported"><primary>Korean</primary><secondary>example</secondary></indexterm>
         <anchor xml:id="c4e7d13"/>
       </title>
       <interlinear-gloss>
         <jbo>kuln,r,kore,a</jbo>
         <en>Korean (the culture)</en>
         
       </interlinear-gloss>
     </example>
-    <para> <indexterm type="example-imported"><primary>Navajo</primary><secondary>example</secondary></indexterm>  <indexterm type="example-imported"><primary>Korean</primary><secondary>example</secondary></indexterm>  <indexterm type="example-imported"><primary>Bulgarian</primary><secondary>example</secondary></indexterm>  <indexterm type="general-imported"><primary>fu'ivla</primary><secondary>considerations for choosing basis word</secondary></indexterm>  <indexterm type="general-imported"><primary>fu'ivla</primary><secondary>with invalid diphthongs</secondary></indexterm>  <indexterm type="general-imported"><primary>invalid diphthongs</primary><secondary>in fu'ivla</secondary></indexterm> Note the commas in 
+    <para><!-- FIXME: there's nowhere for this indexterm to go --><indexterm type="example-imported"><primary>Navajo</primary><secondary>example</secondary></indexterm>      <indexterm type="general-imported"><primary>fu'ivla</primary><secondary>considerations for choosing basis word</secondary></indexterm>  <indexterm type="general-imported"><primary>fu'ivla</primary><secondary>with invalid diphthongs</secondary></indexterm>  <indexterm type="general-imported"><primary>invalid diphthongs</primary><secondary>in fu'ivla</secondary></indexterm> Note the commas in 
     <xref linkend="example-random-id-qJGv"/> and 
     <xref linkend="example-random-id-qjh0"/>, used because 
     <quote>ea</quote> is not a valid diphthong in Lojban. Arguably, some form of the native name 
     <quote>Chosen</quote> should have been used instead of the internationally known 
     <quote>Korea</quote>; this is a recurring problem in all borrowings. In general, it is better to use the native name unless using it will severely impede understanding: 
     
     <quote>Navajo</quote> is far more widely known than 
     
     <quote>Dine'e</quote>.</para>
   </section>
-  <section xml:id="chapter-morphology-section8">
+  <section xml:id="section-cmene">
     <title>cmene</title>
     <para> <indexterm type="general-imported"><primary>names in Lojban (see also cmene)</primary></indexterm>  <indexterm type="general-imported"><primary>cmene</primary><secondary>definition</secondary></indexterm>  <indexterm type="general-imported"><primary>names</primary><secondary>purpose of</secondary></indexterm>  <indexterm type="general-imported"><primary>cmene</primary><secondary>purpose of</secondary></indexterm> Lojbanized names, called 
     <jbophrase>cmene</jbophrase>, are very much like their counterparts in other languages. They are labels applied to things (or people) to stand for them in descriptions or in direct address. They may convey meaning in themselves, but do not necessarily do so.</para>
     
     <para> <indexterm type="general-imported"><primary>names</primary><secondary>rationale for lojbanizing</secondary></indexterm>  <indexterm type="general-imported"><primary>cmene</primary><secondary>rationale for lojbanizing</secondary></indexterm>  <indexterm type="general-imported"><primary>cmene</primary><secondary>and analyzability of speech stream</secondary></indexterm>  <indexterm type="general-imported"><primary>names</primary><secondary>examples of</secondary></indexterm>  <indexterm type="general-imported"><primary>cmene</primary><secondary>examples of</secondary></indexterm> Because names are often highly personal and individual, Lojban attempts to allow native language names to be used with a minimum of modification. The requirement that the Lojban speech stream be unambiguously analyzable, however, means that most names must be modified somewhat when they are Lojbanized. Here are a few examples of English names and possible Lojban equivalents:</para>
     <example xml:id="example-random-id-qjhN" role="interlinear-gloss-example">
       <title>
+        <indexterm type="example-imported"><primary>Jim</primary><secondary>example</secondary></indexterm>
         <anchor xml:id="c4e8d1"/>
       </title>
       <interlinear-gloss>
         <jbo>djim.</jbo>
         <en>Jim</en>
       </interlinear-gloss>
     </example>
     <example xml:id="example-random-id-qjHo" role="interlinear-gloss-example">
       <title>
+        <indexterm type="example-imported"><primary>Jane</primary><secondary>example</secondary></indexterm>
         <anchor xml:id="c4e8d2"/>
       </title>
       <interlinear-gloss>
         <jbo>djein.</jbo>
         <en>Jane</en>
       </interlinear-gloss>
     </example>
     <example xml:id="example-random-id-qjIj" role="interlinear-gloss-example">
       <title>
+        <indexterm type="example-imported"><primary>Arnold</primary><secondary>example</secondary></indexterm>
         <anchor xml:id="c4e8d3"/>
       </title>
       <interlinear-gloss>
         <jbo>.arnold.</jbo>
         <en>Arnold</en>
         
       </interlinear-gloss>
     </example>
     <example xml:id="example-random-id-qjim" role="interlinear-gloss-example">
       <title>
+        <indexterm type="example-imported"><primary>Pete</primary><secondary>example</secondary></indexterm>
         <anchor xml:id="c4e8d4"/>
       </title>
       <interlinear-gloss>
         <jbo>pit.</jbo>
         <en>Pete</en>
         
       </interlinear-gloss>
     </example>
     <example xml:id="example-random-id-qjin" role="interlinear-gloss-example">
       <title>
+        <indexterm type="example-imported"><primary>Katrina</primary><secondary>example</secondary></indexterm>
         <anchor xml:id="c4e8d5"/>
       </title>
       <interlinear-gloss>
         <jbo>katrinas.</jbo>
         <en>Katrina</en>
         
       </interlinear-gloss>
     </example>
     <example xml:id="example-random-id-qjIq" role="interlinear-gloss-example">
       <title>
+        <indexterm type="example-imported"><primary>Catherine</primary><secondary>example</secondary></indexterm>
         <anchor xml:id="c4e8d6"/>
       </title>
       <interlinear-gloss>
         <jbo>kat,r,in.</jbo>
         <en>Catherine</en>
         
       </interlinear-gloss>
     </example>
-    <para> <indexterm type="example-imported"><primary>Catherine</primary><secondary>example</secondary></indexterm>  <indexterm type="example-imported"><primary>Katrina</primary><secondary>example</secondary></indexterm>  <indexterm type="example-imported"><primary>Pete</primary><secondary>example</secondary></indexterm>  <indexterm type="example-imported"><primary>Arnold</primary><secondary>example</secondary></indexterm>  <indexterm type="example-imported"><primary>Jane</primary><secondary>example</secondary></indexterm>  <indexterm type="example-imported"><primary>Jim</primary><secondary>example</secondary></indexterm>  <indexterm type="general-imported"><primary>syllabic consonant</primary><secondary>effect on stress determination</secondary></indexterm> (Note that syllabic 
+    <para><indexterm type="general-imported"><primary>syllabic consonant</primary><secondary>effect on stress determination</secondary></indexterm> (Note that syllabic 
     <quote>r</quote> is skipped in determining the stressed syllable, so 
     
     
     <xref linkend="example-random-id-qjIq"/> is stressed on the 
     <quote>ka</quote>.)</para>
     <example xml:id="example-random-id-qJiv" role="interlinear-gloss-example">
       <title>
+        <indexterm type="example-imported"><primary>Cathy</primary><secondary>example</secondary></indexterm>
         <anchor xml:id="c4e8d7"/>
       </title>
       <interlinear-gloss>
         <jbo>katis.</jbo>
         <en>Cathy</en>
         
       </interlinear-gloss>
     </example>
     <example xml:id="example-random-id-qjIy" role="interlinear-gloss-example">
       <title>
+        <indexterm type="example-imported"><primary>Kate</primary><secondary>example</secondary></indexterm>
         <anchor xml:id="c4e8d8"/>
       </title>
       <interlinear-gloss>
         <jbo>keit.</jbo>
         <en>Kate</en>
         
       </interlinear-gloss>
     </example>
-    <para> <indexterm type="example-imported"><primary>Kate</primary><secondary>example</secondary></indexterm>  <indexterm type="example-imported"><primary>Cathy</primary><secondary>example</secondary></indexterm>  <indexterm type="general-imported"><primary>names</primary><secondary>unusual stress in</secondary></indexterm>  <indexterm type="general-imported"><primary>cmene</primary><secondary>unusual stress in</secondary></indexterm>  <indexterm type="general-imported"><primary>names</primary><secondary>stress in</secondary></indexterm>  <indexterm type="general-imported"><primary>cmene</primary><secondary>stress in</secondary></indexterm>  <indexterm type="general-imported"><primary>names</primary><secondary>rules for formation</secondary></indexterm>  <indexterm type="general-imported"><primary>cmene</primary><secondary>rules for formation</secondary></indexterm> Names may have almost any form, but always end in a consonant, and are followed by a pause. They are penultimately stressed, unless unusual stress is marked with capitalization. A name may have multiple parts, each ending with a consonant and pause, or the parts may be combined into a single word with no pause. For example,</para>
+    <para><indexterm type="general-imported"><primary>names</primary><secondary>unusual stress in</secondary></indexterm>  <indexterm type="general-imported"><primary>cmene</primary><secondary>unusual stress in</secondary></indexterm>  <indexterm type="general-imported"><primary>names</primary><secondary>stress in</secondary></indexterm>  <indexterm type="general-imported"><primary>cmene</primary><secondary>stress in</secondary></indexterm>  <indexterm type="general-imported"><primary>names</primary><secondary>rules for formation</secondary></indexterm>  <indexterm type="general-imported"><primary>cmene</primary><secondary>rules for formation</secondary></indexterm> Names may have almost any form, but always end in a consonant, and are followed by a pause. They are penultimately stressed, unless unusual stress is marked with capitalization. A name may have multiple parts, each ending with a consonant and pause, or the parts may be combined into a single word with no pause. For example,</para>
     
     <example role="interlinear-gloss-example" xml:id="example-random-id-43uP">
       <title>
+        <!-- FIXME: these two indexterms match two different examples; should they go in both or just the first? -->
+        <indexterm type="example-imported"><primary>John Jones</primary><secondary>example</secondary></indexterm>
+        <indexterm type="example-imported"><primary>Jones</primary><secondary>John</secondary><tertiary>example</tertiary></indexterm>
         <anchor xml:id="c4e8d9"/>
       </title>
       <interlinear-gloss>
         <jbo>djan. djonz.</jbo>
       </interlinear-gloss>
     </example>
-    <para> <indexterm type="example-imported"><primary>Jones</primary><secondary>John</secondary><tertiary>example</tertiary></indexterm>  <indexterm type="example-imported"><primary>John Jones</primary><secondary>example</secondary></indexterm> and</para>
+    <para>    and</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-QnyL">
       <title>
         <anchor xml:id="c4e8d10"/>
       </title>
       <interlinear-gloss>
         <jbo>djandjonz.</jbo>
       </interlinear-gloss>
     </example>
     <para>are both valid Lojbanizations of 
     <quote>John Jones</quote>.</para>
@@ -1548,21 +1579,21 @@
     <jbophrase>maris.</jbophrase>, 
     <jbophrase>meiris.</jbophrase>, 
     <jbophrase>merix.</jbophrase>, or even 
     <jbophrase>marys.</jbophrase>. The last alternative is not pronounced much like its English equivalent, but may be desirable to someone who values spelling over pronunciation. The final consonant need not be an 
     <quote>s</quote>; there must, however, be some Lojban consonant at the end.</para>
     <para> <indexterm type="general-imported"><primary>names</primary><secondary>restrictions on form of</secondary></indexterm>  <indexterm type="general-imported"><primary>cmene</primary><secondary>restrictions on form of</secondary></indexterm> Names are not permitted to have the sequences 
     <quote>la</quote>, 
     <quote>lai</quote>, or 
     <jbophrase>doi</jbophrase> embedded in them, unless the sequence is immediately preceded by a consonant. These minor restrictions are due to the fact that all Lojban cmene embedded in a speech stream will be preceded by one of these words or by a pause. With one of these words embedded, the cmene might break up into valid Lojban words followed by a shorter cmene. However, break-up cannot happen after a consonant, because that would imply that the word before the 
     <quote>la</quote>, or whatever, ended in a consonant without pause, which is impossible.</para>
-    <para> <indexterm type="example-imported"><primary>Nederlands</primary><secondary>example</secondary></indexterm>  <indexterm type="example-imported"><primary>Laplace</primary><secondary>example</secondary></indexterm> For example, the invalid name 
+    <para> <!-- FIXME: there's nowhere for these two indexterms to go --><indexterm type="example-imported"><primary>Nederlands</primary><secondary>example</secondary></indexterm>  <indexterm type="example-imported"><primary>Laplace</primary><secondary>example</secondary></indexterm> For example, the invalid name 
     <jbophrase>laplas.</jbophrase> would look like the Lojban words 
     <jbophrase>la plas.</jbophrase>, and 
     <jbophrase>ilanas.</jbophrase> would be misunderstood as 
     <jbophrase>.i la nas.</jbophrase>. However, 
     <quote>NEderlants.</quote> cannot be misheard as 
     <quote>NEder lants.</quote>, because 
     <quote>NEder</quote> with no following pause is not a possible Lojban word.</para>
     <para> <indexterm type="general-imported"><primary>names</primary><secondary>alternatives for restricted sequences in</secondary></indexterm>  <indexterm type="general-imported"><primary>cmene</primary><secondary>alternatives for restricted sequences in</secondary></indexterm> There are close alternatives to these forbidden sequences that can be used in Lojbanizing names, such as 
     <jbophrase>ly</jbophrase>, 
     <quote>lei</quote>, and 
@@ -1585,75 +1616,80 @@
         <quote>.</quote>.</para>
       </listitem>
       <listitem>
         <para> <indexterm type="general-imported"><primary>capitalization</primary><secondary>use of</secondary></indexterm>  <indexterm type="general-imported"><primary>capitalization</primary><secondary>for unusual stress in names</secondary></indexterm>  <indexterm type="general-imported"><primary>capitalization</primary><secondary>use in names</secondary></indexterm>  <indexterm type="general-imported"><primary>names</primary><secondary>stress in</secondary></indexterm>  <indexterm type="general-imported"><primary>cmene</primary><secondary>stress in</secondary></indexterm> They may be stressed on any syllable; if this syllable is not the penultimate one, it must be capitalized when writing. Neither names nor words that begin sentences are capitalized in Lojban, so this is the only use of capital letters.</para>
         
       </listitem>
     </orderedlist>
     <para> <indexterm type="general-imported"><primary>names</primary><secondary>from Lojban words</secondary></indexterm>  <indexterm type="general-imported"><primary>cmene</primary><secondary>from Lojban words</secondary></indexterm> Names meeting these criteria may be invented, Lojbanized from names in other languages, or formed by appending a consonant onto a cmavo, a gismu, a fu'ivla or a lujvo. Some cmene built from Lojban words are:</para>
     <example xml:id="example-random-id-qjj1" role="interlinear-gloss-example">
       <title>
+        <indexterm type="example-imported"><primary>One</primary><secondary>the</secondary><tertiary>example</tertiary></indexterm>
         <anchor xml:id="c4e8d11"/>
       </title>
       <interlinear-gloss>
         <jbo>pav.</jbo>
         <gloss>the One</gloss>
         <en>from the cmavo 
         <jbophrase>pa</jbophrase>, with rafsi 
         <quote>pav</quote>, meaning 
         <quote>one</quote></en>
       </interlinear-gloss>
     </example>
     <example xml:id="example-random-id-qjjN" role="interlinear-gloss-example">
       <title>
+        <indexterm type="example-imported"><primary>Sun</primary><secondary>the</secondary><tertiary>example</tertiary></indexterm>
         <anchor xml:id="c4e8d12"/>
       </title>
       <interlinear-gloss>
         <jbo>sol.</jbo>
         <gloss>the Sun</gloss>
         
         <en>from the gismu 
         <jbophrase>solri</jbophrase>, meaning 
         <quote>solar</quote>, or actually 
         <quote>pertaining to the Sun</quote></en>
         
       </interlinear-gloss>
     </example>
     <example xml:id="example-random-id-qjJz" role="interlinear-gloss-example">
       <title>
+        <indexterm type="example-imported"><primary>Chief</primary><secondary>example</secondary></indexterm>
         <anchor xml:id="c4e8d13"/>
       </title>
       <interlinear-gloss>
         <jbo>ralj.</jbo>
         <gloss>Chief (as a title)</gloss>
         
         <en>from the gismu 
         <jbophrase>ralju</jbophrase>, meaning 
         <quote>principal</quote>.</en>
       </interlinear-gloss>
     </example>
     <example xml:id="example-random-id-qJKt" role="interlinear-gloss-example">
       <title>
+        <indexterm type="example-imported"><primary>Lord</primary><secondary>example</secondary></indexterm>
+        <indexterm type="example-imported"><primary>Lady</primary><secondary>example</secondary></indexterm>
         <anchor xml:id="c4e8d14"/>
       </title>
       <interlinear-gloss>
         <jbo>nol.</jbo>
         <gloss>Lord/Lady</gloss>
         
         
         <en>from the gismu 
         <jbophrase>nobli</jbophrase>, with rafsi 
         <jbophrase>nol</jbophrase>, meaning 
         <quote>noble</quote>.</en>
       </interlinear-gloss>
     </example>
-    <para> <indexterm type="example-imported"><primary>Lady</primary><secondary>example</secondary></indexterm>  <indexterm type="example-imported"><primary>Lord</primary><secondary>example</secondary></indexterm>  <indexterm type="example-imported"><primary>Chief</primary><secondary>example</secondary></indexterm>  <indexterm type="example-imported"><primary>Sun</primary><secondary>the</secondary><tertiary>example</tertiary></indexterm>  <indexterm type="example-imported"><primary>One</primary><secondary>the</secondary><tertiary>example</tertiary></indexterm>  <indexterm type="general-imported"><primary>cmene</primary><secondary>algorithm for</secondary></indexterm>  <indexterm type="general-imported"><primary>names</primary><secondary>algorithm for</secondary></indexterm> To Lojbanize a name from the various natural languages, apply the following rules:</para>
+    <para><indexterm type="general-imported"><primary>cmene</primary><secondary>algorithm for</secondary></indexterm>  <indexterm type="general-imported"><primary>names</primary><secondary>algorithm for</secondary></indexterm> To Lojbanize a name from the various natural languages, apply the following rules:</para>
     <orderedlist>
       <listitem>
         <para>Eliminate double consonants and silent letters.</para>
       </listitem>
       <listitem>
         <para>Add a final 
         <quote>s</quote> or 
         <quote>n</quote> (or some other consonant that sounds good) if the name ends in a vowel.</para>
       </listitem>
       <listitem>
@@ -1828,21 +1864,21 @@
       or Mexican dialect:      don. ki'otes.
       Chinese 
       <quote>Mao Zedong</quote>       maudzydyn.
 
       Japanese 
       <quote>Fujiko</quote>          fudjikos.
 
       or             fujikos.
     </programlisting>
   </section>
-  <section xml:id="chapter-morphology-section9">
+  <section xml:id="section-pauses">
     <title>Rules for inserting pauses</title>
     <para> <indexterm type="general-imported"><primary>pauses</primary><secondary>rules for</secondary></indexterm> Summarized in one place, here are the rules for inserting pauses between Lojban words:</para>
     <orderedlist>
       <listitem>
         <para> <indexterm type="general-imported"><primary>pause</primary><secondary>between words</secondary></indexterm>  <indexterm type="general-imported"><primary>pause</primary><secondary>proscribed within words</secondary></indexterm> Any two words may have a pause between them; it is always illegal to pause in the middle of a word, because that breaks up the word into two words.</para>
       </listitem>
       <listitem>
         <para> <indexterm type="general-imported"><primary>pause</primary><secondary>and consonant-final words</secondary></indexterm>  <indexterm type="general-imported"><primary>consonant-final words</primary><secondary>necessity for pause after</secondary></indexterm> Every word ending in a consonant must be followed by a pause. Necessarily, all such words are cmene.</para>
       </listitem>
       <listitem>
@@ -1863,28 +1899,28 @@
         <jbophrase role="morphology">Cy</jbophrase> must be followed by a pause unless another 
         <jbophrase role="morphology">Cy</jbophrase>-form cmavo follows.</para>
       </listitem>
       <listitem>
         <para> <indexterm type="general-imported"><primary>non-Lojban text</primary><secondary>rules for pause with</secondary></indexterm>  <indexterm type="general-imported"><primary>pause</primary><secondary>and non-Lojban text</secondary></indexterm> When non-Lojban text is embedded in Lojban, it must be preceded and followed by pauses. (How to embed non-Lojban text is explained in 
         
         <xref linkend="chapter-structure"/>.)</para>
       </listitem>
     </orderedlist>
   </section>
-  <section xml:id="chapter-morphology-section10">
+  <section xml:id="section-lujvo-considerations">
     <title>Considerations for making lujvo</title>
     <para>Given a tanru which expresses an idea to be used frequently, it can be turned into a lujvo by following the lujvo-making algorithm which is given in 
-    <xref linkend="chapter-morphology-section11"/>.</para>
+    <xref linkend="section-lujvo-making"/>.</para>
     <para>In building a lujvo, the first step is to replace each gismu with a rafsi that uniquely represents that gismu. These rafsi are then attached together by fixed rules that allow the resulting compound to be recognized as a single word and to be analyzed in only one way.</para>
     <para>There are three other complications; only one is serious.</para>
     <para> <indexterm type="general-imported"><primary>rafsi</primary><secondary>multiple for each gismu</secondary></indexterm> The first is that there is usually more than one rafsi that can be used for each gismu. The one to be used is simply whichever one sounds or looks best to the speaker or writer. There are usually many valid combinations of possible rafsi. They all are equally valid, and all of them mean exactly the same thing. (The scoring algorithm given in 
-    <xref linkend="chapter-morphology-section12"/> is used to choose the standard form of the lujvo - the version which would be entered into a dictionary.)</para>
+    <xref linkend="section-lujvo-scoring"/> is used to choose the standard form of the lujvo - the version which would be entered into a dictionary.)</para>
     <para> <indexterm type="general-imported"><primary>linguistic drift in Lojban</primary><secondary>possible source of</secondary></indexterm>  <indexterm type="general-imported"><primary>lujvo</primary><secondary>consideration in choosing meaning for</secondary></indexterm>  <indexterm type="general-imported"><primary>lujvo</primary><secondary>unambiguity of</secondary></indexterm> The second complication is the serious one. Remember that a tanru is ambiguous - it has several possible meanings. A lujvo, or at least one that would be put into the dictionary, has just a single meaning. Like a gismu, a lujvo is a predicate which encompasses one area of the semantic universe, with one set of places. Hopefully the meaning chosen is the most useful of the possible semantic spaces. A possible source of linguistic drift in Lojban is that as Lojbanic society evolves, the concept that seems the most useful one may change.</para>
     
     
     <para> <indexterm type="lojban-word-imported"><primary>za'e</primary></indexterm>  <indexterm type="general-imported"><primary>za'e</primary><secondary>use to avoid lujvo misunderstandings</secondary></indexterm>  <indexterm type="general-imported"><primary>lujvo</primary><secondary>meaning drift of</secondary></indexterm> You must also be aware of the possibility of some prior meaning of a new lujvo, especially if you are writing for posterity. If a lujvo is invented which involves the same tanru as one that is in the dictionary, and is assigned a different meaning (or even just a different place structure), linguistic drift results. This isn't necessarily bad. Every natural language does it. But in communication, when you use a meaning different from the dictionary definition, someone else may use the dictionary and therefore misunderstand you. You can use the cmavo 
     
     <quote>za'e</quote> (explained in 
     
     <xref linkend="chapter-structure"/>) before a newly coined lujvo to indicate that it may have a non-dictionary meaning.</para>
     <para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>ultimate guideline for choice of meaning/place-structure</secondary></indexterm> The essential nature of human communication is that if the listener understands, then all is well. Let this be the ultimate guideline for choosing meanings and place structures for invented lujvo.</para>
     <para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>dropping elements of</secondary></indexterm>  <indexterm type="general-imported"><primary>Zipf's Law</primary></indexterm> The third complication is also simple, but tends to scare new Lojbanists with its implications. It is based on Zipf's Law, which says that the length of words is inversely proportional to their usage. The shortest words are those which are used more; the longest ones are used less. Conversely, commonly used concepts will be tend to be abbreviated. In English, we have abbreviations and acronyms and jargon, all of which represent complex ideas that are used often by small groups of people, so they shortened them to convey more information more rapidly.</para>
@@ -1895,21 +1931,21 @@
     
     
     <para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>based on multiple tanru</secondary></indexterm> This doesn't lead to ambiguity, as it might seem to. A given lujvo still has exactly one meaning and place structure. It is just that more than one tanru is competing for the same lujvo. But more than one meaning for the tanru was already competing for the 
     <quote>right</quote> to define the meaning of the lujvo. Someone has to use judgment in deciding which one meaning is to be chosen over the others.</para>
     <para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>shorter for more general concepts</secondary></indexterm>  <indexterm type="general-imported"><primary>lujvo</primary><secondary>considerations for retaining elements of</secondary></indexterm> If the lujvo made by a shorter form of tanru is in use, or is likely to be useful for another meaning, the decider then retains one or more of the cmavo, preferably ones that set this meaning apart from the shorter form meaning that is used or anticipated. As a rule, therefore, the shorter lujvo will be used for a more general concept, possibly even instead of a more frequent word. If both words are needed, the simpler one should be shorter. It is easier to add a cmavo to clarify the meaning of the more complex term than it is to find a good alternate tanru for the simpler term.</para>
     
     <para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>and plausibility</secondary></indexterm>  <indexterm type="general-imported"><primary>lujvo</primary><secondary>and the listener</secondary></indexterm> And of course, we have to consider the listener. On hearing an unknown word, the listener will decompose it and get a tanru that makes no sense or the wrong sense for the context. If the listener realizes that the grouping operators may have been dropped out, he or she may try alternate groupings, or try inserting an abstraction operator if that seems plausible. (The grouping of tanru is explained in 
     <xref linkend="chapter-selbri"/>; abstraction is explained in 
     <xref linkend="chapter-abstractions"/>.) Plausibility is the key to learning new ideas and to evaluating unfamiliar lujvo.</para>
   </section>
-  <section xml:id="chapter-morphology-section11">
+  <section xml:id="section-lujvo-making">
     <title>The lujvo-making algorithm</title>
     <para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>algorithm for</secondary></indexterm> The following is the current algorithm for generating Lojban lujvo given a known tanru and a complete list of gismu and their assigned rafsi. The algorithm was designed by Bob LeChevalier and Dr. James Cooke Brown for computer program implementation. It was modified in 1989 with the assistance of Nora LeChevalier, who detected a flaw in the original 
     
     <quote>tosmabru test</quote>.</para>
     
     <para>Given a tanru that is to be made into a lujvo:</para>
     <variablelist>
       <varlistentry>
         <term>1)</term>
         <listitem>
@@ -1997,21 +2033,21 @@
             </varlistentry>
           </variablelist>
         </listitem>
       </varlistentry>
     </variablelist>
     <para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>selection of best form of</secondary></indexterm>  <indexterm type="general-imported"><primary>lujvo</primary><secondary>scoring of</secondary></indexterm> Note that the 
     <quote>tosmabru test</quote> implies that the algorithm will be more efficient if rafsi junctures are tested for required hyphens from right to left, instead of from left to right; when the test is required, it cannot be completed until hyphenation to the right has been determined.</para>
     
     
   </section>
-  <section xml:id="chapter-morphology-section12">
+  <section xml:id="section-lujvo-scoring">
     <title>The lujvo scoring algorithm</title>
     <para>This algorithm was devised by Bob and Nora LeChevalier in 1989. It is not the only possible algorithm, but it usually gives a choice that people find preferable. The algorithm may be changed in the future. The lowest-scoring variant will usually be the dictionary form of the lujvo. (In previous versions, it was the highest-scoring variant.)</para>
     <variablelist>
       <varlistentry>
         <term>1)</term>
         <listitem>
           <para>Count the total number of letters, including hyphens and apostrophes; call it 
           
           <quote>L</quote>.</para>
         </listitem>
@@ -2093,21 +2129,21 @@
           <quote>V</quote>.</para>
         </listitem>
       </varlistentry>
     </variablelist>
     <para> <indexterm type="general-imported"><primary>lujvo form</primary><secondary>hierarchy of priorities for selection of</secondary></indexterm>  <indexterm type="general-imported"><primary>hierarchy of priorities for selecting lujvo form</primary></indexterm> The score is then:</para>
     <programlisting xml:space="preserve">
       (1000 * L) - (500 * A) + (100 * H) - (10 * R) - V
     </programlisting>
     <para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>scored examples of</secondary></indexterm> In case of ties, there is no preference. This should be rare. Note that the algorithm essentially encodes a hierarchy of priorities: short words are preferred (counting apostrophes as half a letter), then words with fewer hyphens, words with more pleasing rafsi (this judgment is subjective), and finally words with more vowels are chosen. Each decision principle is applied in turn if the ones before it have failed to choose; it is possible that a lower-ranked principle might dominate a higher-ranked one if it is ten times better than the alternative.</para>
     
-    <para> <indexterm type="example-imported"><primary>doghouse</primary><secondary>example</secondary></indexterm>  <indexterm type="general-imported"><primary>lujvo</primary><secondary>examples of making</secondary></indexterm> Here are some lujvo with their scores (not necessarily the lowest scoring forms for these lujvo, nor even necessarily sensible lujvo):</para>
+    <para> <!-- FIXME: there's nowhere for this indexterm to go --><indexterm type="example-imported"><primary>doghouse</primary><secondary>example</secondary></indexterm>  <indexterm type="general-imported"><primary>lujvo</primary><secondary>examples of making</secondary></indexterm> Here are some lujvo with their scores (not necessarily the lowest scoring forms for these lujvo, nor even necessarily sensible lujvo):</para>
     <example xml:id="example-random-id-qJKu" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c4e12d1"/>
       </title>
       <interlinear-gloss>
         <jbo>zbasai</jbo>
         <gloss>zba + sai</gloss>
         
         <gloss>(1000 * 6) - (500 * 0) + (100 * 0) - (10 * 15) - 3</gloss>
         <en>= 5847</en>
@@ -2143,29 +2179,29 @@
         <anchor xml:id="c4e12d4"/>
       </title>
       <interlinear-gloss>
         <jbo>zbazbasysarji</jbo>
         <gloss>zba + zbas + y + sarji</gloss>
         <gloss>(1000 * 13) - (500 * 0) + (100 * 1) - (10 * 12) - 4</gloss>
         <en>= 12976</en>
       </interlinear-gloss>
     </example>
   </section>
-  <section xml:id="chapter-morphology-section13">
+  <section xml:id="section-lujvo-making-examples">
     <title>lujvo-making examples</title>
     <para>This section contains examples of making and scoring lujvo. First, we will start with the tanru 
     <jbophrase>gerku zdani</jbophrase> ( 
     <quote>dog house</quote>) and construct a lujvo meaning 
     
     
     <quote>doghouse</quote>, that is, a house where a dog lives. We will use a brute-force application of the algorithm in 
-    <xref linkend="chapter-morphology-section12"/>, using every possible rafsi.</para>
+    <xref linkend="section-lujvo-scoring"/>, using every possible rafsi.</para>
     <para>The rafsi for 
     <jbophrase>gerku</jbophrase> are:</para>
     <programlisting xml:space="preserve">
       -ger-, -ge'u-, -gerk-, -gerku
     </programlisting>
     <para>The rafsi for 
     <jbophrase>zdani</jbophrase> are:</para>
     <programlisting xml:space="preserve">
       -zda-, -zdan-, -zdani.
     </programlisting>
@@ -2197,21 +2233,21 @@
     <para>The fourth form, 
     <quote>ge'u-zdani</quote>, however, requires an 
     <quote>r</quote>-hyphen; otherwise, the 
     <quote>ge'u-</quote> part would fall off as a cmavo. So this form of the lujvo is 
     <jbophrase>ge'urzdani</jbophrase>.</para>
     <para>The last two forms require 
     <jbophrase>y</jbophrase>-hyphens, as all 4-letter rafsi do, and so are 
     
     <jbophrase>gerkyzda</jbophrase> and 
     <jbophrase>gerkyzdani</jbophrase> respectively.</para>
-    <para> <indexterm type="example-imported"><primary>boat class</primary><secondary>example</secondary></indexterm> The scoring algorithm is heavily weighted in favor of short lujvo, so we might expect that 
+    <para> <!-- FIXME: there's nowhere for this indexterm to go --><indexterm type="example-imported"><primary>boat class</primary><secondary>example</secondary></indexterm> The scoring algorithm is heavily weighted in favor of short lujvo, so we might expect that 
     <jbophrase>gerzda</jbophrase> would win. Its L score is 6, its A score is 0, its H score is 0, its R score is 12, and its V score is 3, for a final score of 5878. The other forms have scores of 7917, 6367, 9506, 8008, and 10047 respectively. Consequently, this lujvo would probably appear in the dictionary in the form 
     <jbophrase>gerzda</jbophrase>.</para>
     <para>For the next example, we will use the tanru 
     <jbophrase>bloti klesi</jbophrase> ( 
     <quote>boat class</quote>) presumably referring to the category (rowboat, motorboat, cruise liner) into which a boat falls. We will omit the long rafsi from the process, since lujvo containing long rafsi are almost never preferred by the scoring algorithm when there are short rafsi available.</para>
     
     
     <para>The rafsi for 
     <jbophrase>bloti</jbophrase> are 
     <quote>-lot-</quote>, 
@@ -2274,21 +2310,21 @@
       <!-- not a cmavo list -->
       logjybangri      logjybaugri      logjybangygri
       lojbangirzu      lojbaugirzu      lojbangygirzu
       logjybangirzu    logjybaugirzu    logjybangygirzu
 
       lojbangir.       lojbaugir.       lojbangygir.
       logjybangir.     logjybaugir.     logjybangygir.
       lojbangirz.      lojbaugirz.      lojbangygirz.
       logjybangirz.    logjybaugirz.    logjybangygirz.
     </programlisting>
-    <para> <indexterm type="example-imported"><primary>sexual teacher</primary><secondary>male</secondary><tertiary>example</tertiary></indexterm>  <indexterm type="example-imported"><primary>male sexual teacher</primary><secondary>example</secondary></indexterm> The only fully reduced lujvo forms are 
+    <para> <!-- FIXME: there's nowhere for these two indexterms to go --><indexterm type="example-imported"><primary>sexual teacher</primary><secondary>male</secondary><tertiary>example</tertiary></indexterm>  <indexterm type="example-imported"><primary>male sexual teacher</primary><secondary>example</secondary></indexterm> The only fully reduced lujvo forms are 
     
     <jbophrase>lojbangri</jbophrase> and 
     <jbophrase>lojbaugri</jbophrase>, of which the latter has a slightly lower score: 8827 versus 8796, respectively. However, for the name of the organization, we chose to make sure the name of the language was embedded in it, and to use the clearer long-form rafsi for 
     <jbophrase>girzu</jbophrase>, producing 
     <jbophrase>lojbangirz.</jbophrase></para>
     <para>Finally, here is a four-part lujvo with a cmavo in it, based on the tanru 
     <jbophrase>nakni ke cinse ctuca</jbophrase> or 
     <quote>male (sexual teacher)</quote>. The 
     
     <quote>ke</quote> cmavo ensures the interpretation 
@@ -2306,21 +2342,21 @@
     </programlisting>
     <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>algorithm for</secondary></indexterm> Of these forms, 
     <jbophrase>nakykemcinctu</jbophrase> is the shortest and is preferred by the scoring algorithm. On the whole, however, it might be better to just make a lujvo for 
     <jbophrase>cinse ctuca</jbophrase> (which would be 
     <jbophrase>cinctu</jbophrase>) since the sex of the teacher is rarely important. If there was a reason to specify 
     <quote>male</quote>, then the simpler tanru 
     <jbophrase>nakni cinctu</jbophrase> ( 
     <quote>male sexual-teacher</quote>) would be appropriate. This tanru is actually shorter than the four-part lujvo, since the 
     <quote>ke</quote> required for grouping need not be expressed.</para>
   </section>
-  <section xml:id="chapter-morphology-section14">
+  <section xml:id="section-gismu-making">
     <title>The gismu creation algorithm</title>
     <para> <indexterm type="general-imported"><primary>source languages</primary><secondary>use in creating gismu</secondary></indexterm> The gismu were created through the following process:</para>
     <variablelist>
       <varlistentry>
         <term>1)</term>
         <listitem>
           <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>creation</secondary><tertiary>scoring rules</tertiary></indexterm> At least one word was found in each of the six source languages (Chinese, English, Hindi, Spanish, Russian, Arabic) corresponding to the proposed gismu. This word was rendered into Lojban phonetics rather liberally: consonant clusters consisting of a stop and the corresponding fricative were simplified to just the fricative ( 
           
           
           
@@ -2380,21 +2416,21 @@
             m			n
             n			m
             p			b, f
             r			l
             s			c, z
             t			d
             v			b, f
             x			g, k
             z			j, s
           </programlisting>
-          <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>source-language weights for</secondary></indexterm> See <xref linkend="chapter-morphology-section4"/> for an example.</para>
+          <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>source-language weights for</secondary></indexterm> See <xref linkend="section-gismu"/> for an example.</para>
         </listitem>
       </varlistentry>
       <varlistentry>
         <term>5)</term>
         <listitem>
           <para>The gismu form with the highest score usually became the actual gismu. Sometimes a lower-scoring form was used to provide a better rafsi. A few gismu were changed in error as a result of transcription blunders (for example, the gismu 
           <jbophrase>gismu</jbophrase> should have been 
           <jbophrase>gicmu</jbophrase>, but it's too late to fix it now).</para>
           <para>The language weights used to make most of the gismu were as follows:</para>
           <programlisting>
@@ -2419,21 +2455,21 @@
       </varlistentry>
     </variablelist>
     <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>Lojban-specific</secondary></indexterm> Note that the stressed vowel of the gismu was considered sufficiently distinctive that two or more gismu may differ only in this vowel; as an extreme example, 
     
     <jbophrase>bradi</jbophrase>, 
     <jbophrase>bredi</jbophrase>, 
     <jbophrase>bridi</jbophrase>, and 
     <jbophrase>brodi</jbophrase> (but fortunately not 
     <jbophrase>brudi</jbophrase>) are all existing gismu.</para>
   </section>
-  <section xml:id="chapter-morphology-section15">
+  <section xml:id="section-cultural-gismu">
     <title>Cultural and other non-algorithmic gismu</title>
     <para>The following gismu were not made by the gismu creation algorithm. They are, in effect, coined words similar to fu'ivla. They are exceptions to the otherwise mandatory gismu creation algorithm where there was sufficient justification for such exceptions. Except for the small metric prefixes and the assignable predicates beginning with 
     <quote>brod-</quote>, they all end in the letter 
     <quote>o</quote>, which is otherwise a rare letter in Lojban gismu.</para>
     <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>scientific-mathematical</secondary></indexterm> The following gismu represent concepts that are sufficiently unique to Lojban that they were either coined from combining forms of other gismu, or else made up out of whole cloth. These gismu are thus conceptually similar to lujvo even though they are only five letters long; however, unlike lujvo, they have rafsi assigned to them for use in building more complex lujvo. Assigning gismu to these concepts helps to keep the resulting lujvo reasonably short.</para>
     <programlisting xml:space="preserve">
       broda       1st assignable predicate
       brode       2nd assignable predicate
       brodi       3rd assignable predicate
       brodo       4th assignable predicate
@@ -2598,39 +2634,40 @@
       xriso       Christian
     </programlisting>
     <para> <indexterm type="general-imported"><primary>fu'ivla</primary><secondary>form for rafsi fu'ivla proposal</secondary></indexterm>  <indexterm type="general-imported"><primary>CCVVCV fu'ivla</primary><secondary>and rafsi fu'ivla proposal</secondary></indexterm> A few terms that cover multiple groups of the above:</para>
     <programlisting xml:space="preserve">
       jegvo       Jehovist (Judeo-Christian-Moslem)
       semto       Semitic
       slovo       Slavic
       xispo       Hispanic (New World Spanish)
     </programlisting>
   </section>
-  <section xml:id="chapter-morphology-section16">
+  <section xml:id="section-rafsi-fuhivla">
     <title>rafsi fu'ivla: a proposal</title>
     <para>The list of cultures represented by gismu, given in 
-    <xref linkend="chapter-morphology-section15"/>, is unavoidably controversial. Much time has been spent debating whether this or that culture 
+    <xref linkend="section-cultural-gismu"/>, is unavoidably controversial. Much time has been spent debating whether this or that culture 
     <quote>deserves a gismu</quote> or 
     <quote>must languish in fu'ivla space</quote>. To help defuse this argument, a last-minute proposal was made when this book was already substantially complete. I have added it here with experimental status: it is not yet a standard part of Lojban, since all its implications have not been tested in open debate, and it affects a part of the language (lujvo-making) that has long been stable, but is known to be fragile in the face of small changes. (Many attempts were made to add general mechanisms for making lujvo that contained fu'ivla, but all failed on obvious or obscure counterexamples; finally the general 
     <quote>zei</quote> mechanism was devised instead.)</para>
     <para>The first part of the proposal is uncontroversial and involves no change to the language mechanisms. All valid Type 4 fu'ivla of the form CCVVCV would be reserved for cultural brivla analogous to those described in 
-    <xref linkend="chapter-morphology-section15"/>. For example,</para>
+    <xref linkend="section-cultural-gismu"/>. For example,</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-PMb2">
       <title>
+        <indexterm type="example-imported"><primary>Chilean desert</primary><secondary>example</secondary></indexterm>
         <anchor xml:id="c4e16d1"/>
       </title>
       <interlinear-gloss>
         <jbo>tci'ile</jbo>
         <en>Chilean</en>
       </interlinear-gloss>
     </example>
-    <para> <indexterm type="example-imported"><primary>Chilean desert</primary><secondary>example</secondary></indexterm> is of the appropriate form, and passes all tests required of a Stage 4 fu'ivla. No two fu'ivla of this form would be allowed to coexist if they differed only in the final vowel; this rule was applied to gismu, but does not apply to other fu'ivla or to lujvo.</para>
+    <para>  is of the appropriate form, and passes all tests required of a Stage 4 fu'ivla. No two fu'ivla of this form would be allowed to coexist if they differed only in the final vowel; this rule was applied to gismu, but does not apply to other fu'ivla or to lujvo.</para>
     <para>The second, and fully experimental, part of the proposal is to allow rafsi to be formed from these cultural fu'ivla by removing the final vowel and treating the result as a 4-letter rafsi (although it would contain five letters, not four). These rafsi could then be used on a par with all other rafsi in forming lujvo. The tanru</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-hcR6">
       <title>
         <anchor xml:id="c4e16d2"/>
       </title>
       <interlinear-gloss>
         <jbo>tci'ile ke canre tutra</jbo>
         <gloss>Chilean type-of (sand territory)</gloss>
         <en>Chilean desert</en>
         
diff --git a/todocbook/TODO b/todocbook/TODO
index cf205ce..2455093 100644
--- a/todocbook/TODO
+++ b/todocbook/TODO
@@ -4,21 +4,21 @@
 ==================
 
 Most of the below is intended to be done as needed as you review a
 particular chapter/section.  It looks like more complexity than it
 actually is; you'll get used to it.
 
     SAY HERE WHAT YOU'VE DONE, including parts you haven't completed
     (like index work).
 
 Robin Powell: 5.1, 5.2, 5.3
-Zort: Chapter 3 except index work and examples
+Zort: 3.*, 5.*
 
  ------
 
 Ignore Chapter 2 for now.
 
  ------
 
 If you have any trouble, add a FIXME comment, like so:
 
 <!-- FIXME: detailed explanation here -->

commit b4eeb2f6a9118c3c1957199ea69b4f3fd498eaed
Author: Eitan Postavsky <eitanp32@gmail.com>
Date:   Sun Jan 2 16:49:12 2011 -0500

    Literally just fixing the indentation in chapter 4.

diff --git a/todocbook/4.xml b/todocbook/4.xml
index ebb480f..ced2bca 100644
--- a/todocbook/4.xml
+++ b/todocbook/4.xml
@@ -26,58 +26,58 @@
           <jbophrase>i</jbophrase>, 
           <quote>o</quote>, or 
           <quote>u</quote>.</para>
         </listitem>
       </varlistentry>
       <varlistentry>
         <term>2)</term>
         <listitem>
           <para> <indexterm type="general-imported"><primary>VV string</primary><secondary>as a symbol for a double vowel</secondary></indexterm> VV represents either a diphthong, one of the following: 
           <programlisting xml:space="preserve">
-      ai ei oi au
-</programlisting> or a two-syllable vowel pair with an apostrophe separating the vowels, one of the following: 
-          <cmavo-list>
-            <cmavo-entry>
-              <cmavo>a'a a'e a'i</cmavo>
-              
-              
-              <selmaho>a'o</selmaho>
-              
-              <description>a'u</description>
-            </cmavo-entry>
-            <cmavo-entry>
-              <cmavo>e'a e'e e'i</cmavo>
-              
-              
-              <selmaho>e'o</selmaho>
-              
-              <description>e'u</description>
-            </cmavo-entry>
-            <cmavo-entry>
-              <cmavo>i'a i'e i'i</cmavo>
-              
-              <selmaho>i'o</selmaho>
-              <description>i'u</description>
-            </cmavo-entry>
-            <cmavo-entry>
-              <cmavo>o'a o'e o'i</cmavo>
-              
-              <selmaho>o'o</selmaho>
-              <description>o'u</description>
-              
-            </cmavo-entry>
-            <cmavo-entry>
-              <cmavo>u'a u'e u'i</cmavo>
-              <selmaho>u'o</selmaho>
-              <description>u'u</description>
-              
-            </cmavo-entry>
+            ai ei oi au
+            </programlisting> or a two-syllable vowel pair with an apostrophe separating the vowels, one of the following: 
+            <cmavo-list>
+              <cmavo-entry>
+                <cmavo>a'a a'e a'i</cmavo>
+                
+                
+                <selmaho>a'o</selmaho>
+                
+                <description>a'u</description>
+              </cmavo-entry>
+              <cmavo-entry>
+                <cmavo>e'a e'e e'i</cmavo>
+                
+                
+                <selmaho>e'o</selmaho>
+                
+                <description>e'u</description>
+              </cmavo-entry>
+              <cmavo-entry>
+                <cmavo>i'a i'e i'i</cmavo>
+                
+                <selmaho>i'o</selmaho>
+                <description>i'u</description>
+              </cmavo-entry>
+              <cmavo-entry>
+                <cmavo>o'a o'e o'i</cmavo>
+                
+                <selmaho>o'o</selmaho>
+                <description>o'u</description>
+                
+              </cmavo-entry>
+              <cmavo-entry>
+                <cmavo>u'a u'e u'i</cmavo>
+                <selmaho>u'o</selmaho>
+                <description>u'u</description>
+                
+              </cmavo-entry>
           </cmavo-list></para>
         </listitem>
       </varlistentry>
       <varlistentry>
         <term>3)</term>
         <listitem>
           <para> <indexterm type="general-imported"><primary>apostrophe</primary><secondary>as not a consonant for morphological discussions</secondary></indexterm>  <indexterm type="general-imported"><primary>syllabic r</primary><secondary>as a consonant for morphological discussions</secondary></indexterm>  <indexterm type="general-imported"><primary>syllabic n</primary><secondary>as a consonant for morphological discussions</secondary></indexterm>  <indexterm type="general-imported"><primary>syllabic m</primary><secondary>as a consonant for morphological discussions</secondary></indexterm>  <indexterm type="general-imported"><primary>syllabic l</primary><secondary>considered as a consonant for morphological discussions</secondary></indexterm>  <indexterm type="general-imported"><primary>C string</primary><secondary>as a symbol for a single consonant</secondary></indexterm> C represents a single Lojban consonant, not including the apostrophe, one of 
           <quote>b</quote>, 
           <quote>c</quote>, 
           <quote>d</quote>, 
@@ -101,35 +101,35 @@
           <quote>r</quote> always count as consonants for the purposes of this chapter.</para>
         </listitem>
       </varlistentry>
       <varlistentry>
         <term>4)</term>
         <listitem>
           <para> <indexterm type="general-imported"><primary>CC string</primary><secondary>as a symbol for a permissible initial consonant pair</secondary></indexterm> CC represents two adjacent consonants of type C which constitute one of the 48 permissible initial consonant pairs: 
           
           
           <programlisting xml:space="preserve">
-      bl br
-      cf ck cl cm cn cp cr ct
-      dj dr dz
-      fl fr
-      gl gr
-      jb jd jg jm jv
-      kl kr
-      ml mr
-      pl pr
-      sf sk sl sm sn sp sr st
-      tc tr ts
-      vl vr
-      xl xr
-      zb zd zg zm zv
-</programlisting></para>
+            bl br
+            cf ck cl cm cn cp cr ct
+            dj dr dz
+            fl fr
+            gl gr
+            jb jd jg jm jv
+            kl kr
+            ml mr
+            pl pr
+            sf sk sl sm sn sp sr st
+            tc tr ts
+            vl vr
+            xl xr
+            zb zd zg zm zv
+          </programlisting></para>
         </listitem>
       </varlistentry>
       <varlistentry>
         <term>5)</term>
         <listitem>
           <para> <indexterm type="general-imported"><primary>C/C string</primary><secondary>as a symbol for a permissible consonant pair</secondary></indexterm> C/C represents two adjacent consonants which constitute one of the permissible consonant pairs (not necessarily a permissible initial consonant pair). The permissible consonant pairs are explained in 
           
           <xref linkend="chapter-phonology"/>. In brief, any consonant pair is permissible unless it: contains two identical letters, contains both a voiced (excluding 
           <quote>r</quote>, 
           <quote>l</quote>, 
@@ -712,75 +712,75 @@
     
     <example xml:id="example-random-id-qj84" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c4e6d1"/>
       </title>
       <interlinear-gloss>
         <jbo>mamtypatfu</jbo>
         <gloss>from 
         <jbophrase>mamta patfu</jbophrase></gloss>
         <en>
-        <quote>mother father</quote> or 
-        
+          <quote>mother father</quote> or 
+          
         <quote>maternal grandfather</quote></en>
       </interlinear-gloss>
     </example>
     <example xml:id="example-random-id-qj99" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c4e6d2"/>
       </title>
       <interlinear-gloss>
         <jbo>lerfyliste</jbo>
         <gloss>from 
         <jbophrase>lerfu liste</jbophrase></gloss>
         <gloss>
-        <quote>letter list</quote> or a 
+          <quote>letter list</quote> or a 
         <quote>list of letters</quote></gloss>
         <en>(letters of the alphabet)</en>
       </interlinear-gloss>
     </example>
     <example xml:id="example-random-id-qj9G" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c4e6d3"/>
       </title>
       <interlinear-gloss>
         <jbo>nancyprali</jbo>
         <gloss>from 
         <jbophrase>nanca prali</jbophrase></gloss>
         <en>
-        <quote>year profit</quote> or 
+          <quote>year profit</quote> or 
         <quote>annual profit</quote></en>
       </interlinear-gloss>
     </example>
     <example xml:id="example-random-id-qJbi" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c4e6d4"/>
       </title>
       <interlinear-gloss>
         <jbo>prunyplipe</jbo>
         <gloss>from 
         <jbophrase>pruni plipe</jbophrase></gloss>
         <en>
-        <quote>elastic (springy) leap</quote> or 
+          <quote>elastic (springy) leap</quote> or 
         <quote>spring</quote> (the verb)</en>
       </interlinear-gloss>
     </example>
     <example xml:id="example-random-id-qjbP" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c4e6d5"/>
       </title>
       <interlinear-gloss>
         <jbo>vancysanmi</jbo>
         <gloss>from 
         <jbophrase>vanci sanmi</jbophrase></gloss>
         <en>
-        <quote>evening meal</quote> or 
+          <quote>evening meal</quote> or 
         <quote>supper</quote></en>
         
       </interlinear-gloss>
     </example>
     <para> <indexterm type="example-imported"><primary>supper</primary><secondary>example</secondary></indexterm>  <indexterm type="general-imported"><primary>short rafsi</primary></indexterm>  <indexterm type="general-imported"><primary>rafsi</primary><secondary>short</secondary></indexterm> In addition to these two forms, each gismu may have up to three additional short rafsi, three letters long. All short rafsi have one of the forms CVC, CCV, or CVV. The total number of rafsi forms that are assigned to a gismu depends on how useful the gismu is, or is presumed to be, in making lujvo, when compared to other gismu that could be assigned the rafsi.</para>
     <para> <indexterm type="general-imported"><primary>-er</primary><secondary>use of zmadu in forming</secondary></indexterm>  <indexterm type="general-imported"><primary>comparatives</primary><secondary>use of zmadu in forming</secondary></indexterm> For example, 
     <jbophrase>zmadu</jbophrase> ( 
     <quote>more than</quote>) has the two short rafsi 
     <quote>zma</quote> and 
     <jbophrase>mau</jbophrase> (in addition to its unreduced rafsi 
@@ -954,35 +954,35 @@
     <para>In addition, some of the unreduced forms in the previous example may be fully reduced to:</para>
     <example xml:id="example-random-id-qjdE" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c4e6d10"/>
       </title>
       <interlinear-gloss>
         <jbo>mampa'u</jbo>
         <gloss>from 
         <jbophrase>mamta patfu</jbophrase></gloss>
         <en>
-        <quote>mother father</quote> or 
-        
+          <quote>mother father</quote> or 
+          
         <quote>maternal grandfather</quote></en>
       </interlinear-gloss>
     </example>
     <example xml:id="example-random-id-qJDg" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c4e6d11"/>
       </title>
       <interlinear-gloss>
         <jbo>lerste</jbo>
         <gloss>from 
         <jbophrase>lerfu liste</jbophrase></gloss>
         <en>
-        <quote>letter list</quote> or a 
+          <quote>letter list</quote> or a 
         <quote>list of letters</quote></en>
       </interlinear-gloss>
     </example>
     <para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>recognizing</secondary></indexterm>  <indexterm type="general-imported"><primary>lujvo form</primary><secondary>number of letters in</secondary></indexterm>  <indexterm type="general-imported"><primary>lujvo form</primary><secondary>consonant cluster requirement in</secondary></indexterm>  <indexterm type="general-imported"><primary>lujvo form</primary><secondary>final letter of</secondary></indexterm>  <indexterm type="general-imported"><primary>lujvo</primary><secondary>summary of form characteristics</secondary></indexterm> As noted above, CVC-form rafsi cannot appear as the final rafsi in a lujvo, because all lujvo must end with one or two vowels. As a brivla, a lujvo must also contain a consonant cluster within the first five letters - this ensures that they cannot be mistaken for compound cmavo. Of course, all lujvo have at least six letters since they have two or more rafsi, each at least three letters long; hence they cannot be confused with gismu.</para>
     <para> <indexterm type="general-imported"><primary>lujvo form</primary><secondary>requirements for hyphen insertion in</secondary></indexterm>  <indexterm type="general-imported"><primary>hyphen letter</primary><secondary>definition</secondary></indexterm>  <indexterm type="general-imported"><primary>hyphens</primary><secondary>use of</secondary></indexterm> When attaching two rafsi together, it may be necessary to insert a hyphen letter. In Lojban, the term 
     
     <quote>hyphen</quote> always refers to a letter, either the vowel 
     <jbophrase>y</jbophrase> or one of the consonants 
     <quote>r</quote> and 
     <quote>n</quote>. (The letter 
@@ -1295,21 +1295,21 @@
         <jbo>cobra</jbo>
         
         <gloss>kobra (Lojbanize)</gloss>
         <en>sinc,r,kobra (prefix rafsi)</en>
       </interlinear-gloss>
     </example>
     <para> <indexterm type="example-imported"><primary>cobra</primary><secondary>example</secondary></indexterm> where 
     <quote>sinc-</quote> represents 
     <jbophrase>since</jbophrase> ( 
     <quote>snake</quote>).</para>
-<para> <indexterm type="example-imported"><primary>quark</primary><secondary>example</secondary></indexterm> FIXME: TAG SPOT</para>
+    <para> <indexterm type="example-imported"><primary>quark</primary><secondary>example</secondary></indexterm> FIXME: TAG SPOT</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-TFzH">
       <title>
         <anchor xml:id="c4e7d7"/>
       </title>
       <interlinear-gloss>
         <jbo>quark</jbo>
         
         <gloss>kuark (Lojbanize)</gloss>
         <gloss>kuarka (add final vowel)</gloss>
         <en>sask,r,kuarka (prefix rafsi)</en>
@@ -1735,112 +1735,112 @@
       </listitem>
       <listitem>
         <para>Change final 
         <jbophrase>ie</jbophrase> and 
         <jbophrase>ii</jbophrase> to 
         <jbophrase>i</jbophrase>.</para>
       </listitem>
       <listitem>
         <para>Make the following idiosyncratic substitutions: 
         <programlisting xml:space="preserve">
-      aa     a
-      ae     e
-      ch     k
-      ee     i
-      eigh   ei
-      ew     u
-      igh    ai
-      oo     u
-      ou     u
-      ow     au
-      ph     f
-      q      k
-      sc     sk
-      w      u
-      y      i
-</programlisting> However, the diphthong substitutions should not be done if the two vowels are in two different syllables.</para>
+          aa     a
+          ae     e
+          ch     k
+          ee     i
+          eigh   ei
+          ew     u
+          igh    ai
+          oo     u
+          ou     u
+          ow     au
+          ph     f
+          q      k
+          sc     sk
+          w      u
+          y      i
+        </programlisting> However, the diphthong substitutions should not be done if the two vowels are in two different syllables.</para>
       </listitem>
       <listitem>
         <para>Change 
         <quote>h</quote> between two vowels to 
         <quote>'</quote>, but otherwise remove it completely. If preservation of the 
         <quote>h</quote> seems essential, change it to 
         <quote>x</quote> instead.</para>
       </listitem>
       <listitem>
         <para>Place 
         <quote>'</quote> between any remaining vowel pairs that do not form Lojban diphthongs.</para>
         
       </listitem>
     </orderedlist>
     <para>Some further examples of Lojbanized names are:</para>
     <programlisting xml:space="preserve">
-    English 
-<quote>Mary</quote>             meris.
-                 or            meiris.
-    English 
-<quote>Smith</quote>            smit.
-    English 
-<quote>Jones</quote>            djonz.
-    English 
-<quote>John</quote>             djan. or jan. (American)
-                 or            djon. or jon. (British)
-    English 
-<quote>Alice</quote>            .alis.
-    English 
-<quote>Elise</quote>            .eLIS.
-    English 
-<quote>Johnson</quote>          djansn.
+      English 
+      <quote>Mary</quote>             meris.
+      or            meiris.
+      English 
+      <quote>Smith</quote>            smit.
+      English 
+      <quote>Jones</quote>            djonz.
+      English 
+      <quote>John</quote>             djan. or jan. (American)
+      or            djon. or jon. (British)
+      English 
+      <quote>Alice</quote>            .alis.
+      English 
+      <quote>Elise</quote>            .eLIS.
+      English 
+      <quote>Johnson</quote>          djansn.
 
-    English 
-<quote>William</quote>          .uiliam.
+      English 
+      <quote>William</quote>          .uiliam.
 
-                 or            .uil,iam.
-    English 
-<quote>Brown</quote>            braun.
+      or            .uil,iam.
+      English 
+      <quote>Brown</quote>            braun.
 
-    English 
-<quote>Charles</quote>          tcarlz.
-    French 
-<quote>Charles</quote>           carl.
-    French 
-<quote>De Gaulle</quote>         dyGOL.
+      English 
+      <quote>Charles</quote>          tcarlz.
+      French 
+      <quote>Charles</quote>           carl.
+      French 
+      <quote>De Gaulle</quote>         dyGOL.
 
-    German 
-<quote>Heinrich</quote>          xainrix.
-    Spanish 
-<quote>Joaquin</quote>          xuaKIN.
-    Russian 
-<quote>Svetlana</quote>         sfietlanys.
+      German 
+      <quote>Heinrich</quote>          xainrix.
+      Spanish 
+      <quote>Joaquin</quote>          xuaKIN.
+      Russian 
+      <quote>Svetlana</quote>         sfietlanys.
 
-    Russian 
-<quote>Khrushchev</quote>       xrucTCOF.
+      Russian 
+      <quote>Khrushchev</quote>       xrucTCOF.
 
-    Hindi 
-<quote>Krishna</quote>            kricnas.
+      Hindi 
+      <quote>Krishna</quote>            kricnas.
 
-    Polish 
-<quote>Lech Walesa</quote>       lex. va,uensas.
+      Polish 
+      <quote>Lech Walesa</quote>       lex. va,uensas.
 
-    Spanish 
-<quote>Don Quixote</quote>      don. kicotes.
+      Spanish 
+      <quote>Don Quixote</quote>      don. kicotes.
 
       or modern Spanish:       don. kixotes.
       or Mexican dialect:      don. ki'otes.
-    Chinese 
-<quote>Mao Zedong</quote>       maudzydyn.
+      Chinese 
+      <quote>Mao Zedong</quote>       maudzydyn.
 
-    Japanese 
-<quote>Fujiko</quote>          fudjikos.
+      Japanese 
+      <quote>Fujiko</quote>          fudjikos.
 
-                or             fujikos.
-</programlisting>
+      or             fujikos.
+    </programlisting>
   </section>
   <section xml:id="chapter-morphology-section9">
     <title>Rules for inserting pauses</title>
     <para> <indexterm type="general-imported"><primary>pauses</primary><secondary>rules for</secondary></indexterm> Summarized in one place, here are the rules for inserting pauses between Lojban words:</para>
     <orderedlist>
       <listitem>
         <para> <indexterm type="general-imported"><primary>pause</primary><secondary>between words</secondary></indexterm>  <indexterm type="general-imported"><primary>pause</primary><secondary>proscribed within words</secondary></indexterm> Any two words may have a pause between them; it is always illegal to pause in the middle of a word, because that breaks up the word into two words.</para>
       </listitem>
       <listitem>
         <para> <indexterm type="general-imported"><primary>pause</primary><secondary>and consonant-final words</secondary></indexterm>  <indexterm type="general-imported"><primary>consonant-final words</primary><secondary>necessity for pause after</secondary></indexterm> Every word ending in a consonant must be followed by a pause. Necessarily, all such words are cmene.</para>
@@ -1967,21 +1967,21 @@
           </variablelist></para>
         </listitem>
       </varlistentry>
       <varlistentry>
         <term>5)</term>
         <listitem>
           <para>Test all forms with one or more initial CVC-form rafsi - with the pattern 
           <quote>CVC ... CVC + X</quote>- for 
           <jbophrase>tosmabru failure</jbophrase>. X must either be a CVCCV long rafsi that happens to have a permissible initial pair as the consonant cluster, or is something which has caused a 
           <jbophrase>y</jbophrase>-hyphen to be installed between the previous CVC and itself by one of the above rules.</para>
-        <para>The test is as follows:</para>
+          <para>The test is as follows:</para>
           <variablelist>
             <varlistentry>
               <term>5a)</term>
               <listitem>
                 <para>Examine all the C/C consonant pairs up to the first <jbophrase>y</jbophrase>-hyphen, or up to the end of the word in case there are no <jbophrase>y</jbophrase>-hyphens.</para>
                 <para>These consonant pairs are called "joints”.</para>
               </listitem>
             </varlistentry>
             <varlistentry>
               <term>5b)</term>
@@ -2090,21 +2090,21 @@
         <listitem>
           <para>Count the number of vowels, not including 
           <jbophrase>y</jbophrase>; call it 
           <quote>V</quote>.</para>
         </listitem>
       </varlistentry>
     </variablelist>
     <para> <indexterm type="general-imported"><primary>lujvo form</primary><secondary>hierarchy of priorities for selection of</secondary></indexterm>  <indexterm type="general-imported"><primary>hierarchy of priorities for selecting lujvo form</primary></indexterm> The score is then:</para>
     <programlisting xml:space="preserve">
       (1000 * L) - (500 * A) + (100 * H) - (10 * R) - V
-</programlisting>
+    </programlisting>
     <para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>scored examples of</secondary></indexterm> In case of ties, there is no preference. This should be rare. Note that the algorithm essentially encodes a hierarchy of priorities: short words are preferred (counting apostrophes as half a letter), then words with fewer hyphens, words with more pleasing rafsi (this judgment is subjective), and finally words with more vowels are chosen. Each decision principle is applied in turn if the ones before it have failed to choose; it is possible that a lower-ranked principle might dominate a higher-ranked one if it is ten times better than the alternative.</para>
     
     <para> <indexterm type="example-imported"><primary>doghouse</primary><secondary>example</secondary></indexterm>  <indexterm type="general-imported"><primary>lujvo</primary><secondary>examples of making</secondary></indexterm> Here are some lujvo with their scores (not necessarily the lowest scoring forms for these lujvo, nor even necessarily sensible lujvo):</para>
     <example xml:id="example-random-id-qJKu" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c4e12d1"/>
       </title>
       <interlinear-gloss>
         <jbo>zbasai</jbo>
         <gloss>zba + sai</gloss>
@@ -2155,43 +2155,43 @@
     <para>This section contains examples of making and scoring lujvo. First, we will start with the tanru 
     <jbophrase>gerku zdani</jbophrase> ( 
     <quote>dog house</quote>) and construct a lujvo meaning 
     
     
     <quote>doghouse</quote>, that is, a house where a dog lives. We will use a brute-force application of the algorithm in 
     <xref linkend="chapter-morphology-section12"/>, using every possible rafsi.</para>
     <para>The rafsi for 
     <jbophrase>gerku</jbophrase> are:</para>
     <programlisting xml:space="preserve">
-          -ger-, -ge'u-, -gerk-, -gerku
-</programlisting>
+      -ger-, -ge'u-, -gerk-, -gerku
+    </programlisting>
     <para>The rafsi for 
     <jbophrase>zdani</jbophrase> are:</para>
     <programlisting xml:space="preserve">
-          -zda-, -zdan-, -zdani.
-</programlisting>
+      -zda-, -zdan-, -zdani.
+    </programlisting>
     <para>Step 1 of the algorithm directs us to use 
     <quote>-ger-</quote>, 
     <quote>-ge'u-</quote> and 
     <quote>-gerk-</quote> as possible rafsi for 
     <jbophrase>gerku</jbophrase>; Step 2 directs us to use 
     <quote>-zda-</quote> and 
     <quote>-zdani</quote> as possible rafsi for 
     <jbophrase>zdani</jbophrase>. The six possible forms of the lujvo are then:</para>
     <programlisting xml:space="preserve">
-          ger-zda
-          ger-zdani
-          ge'u-zda
-          ge'u-zdani
-          gerk-zda
-          gerk-zdani
-</programlisting>
+      ger-zda
+      ger-zdani
+      ge'u-zda
+      ge'u-zdani
+      gerk-zda
+      gerk-zdani
+    </programlisting>
     <para>We must then insert appropriate hyphens in each case. The first two forms need no hyphenation: 
     
     <quote>ge</quote> cannot fall off the front, because the following word would begin with 
     <quote>rz</quote>, which is not a permissible initial consonant pair. So the lujvo forms are 
     <jbophrase>gerzda</jbophrase> and 
     <jbophrase>gerzdani</jbophrase>.</para>
     <para>The third form, 
     <quote>ge'u-zda</quote>, needs no hyphen, because even though the first rafsi is CVV, the second one is CCV, so there is a consonant cluster in the first five letters. So 
     <jbophrase>ge'uzda</jbophrase> is this form of the lujvo.</para>
     <para>The fourth form, 
@@ -2215,102 +2215,102 @@
     <para>The rafsi for 
     <jbophrase>bloti</jbophrase> are 
     <quote>-lot-</quote>, 
     <quote>-blo-</quote>, and 
     <quote>-lo'i-</quote>; for 
     <jbophrase>klesi</jbophrase> they are 
     <quote>-kle-</quote> and 
     <quote>-lei-</quote>. Both these gismu are among the handful which have both CVV-form and CCV-form rafsi, so there is an unusual number of possibilities available for a two-part tanru:</para>
     <programlisting xml:space="preserve">
       lotkle      blokle      lo'ikle 
-<!-- not a cmavo list -->
-          lotlei      blolei      lo'irlei
-</programlisting>
+      <!-- not a cmavo list -->
+      lotlei      blolei      lo'irlei
+    </programlisting>
     <para>Only 
     <jbophrase>lo'irlei</jbophrase> requires hyphenation (to avoid confusion with the cmavo sequence 
     <quote>lo'i lei</quote>). All six forms are valid versions of the lujvo, as are the six further forms using long rafsi; however, the scoring algorithm produces the following results:</para>
     
     <programlisting xml:space="preserve">
-          lotkle  5878      blokle  5858      lo'ikle  6367 
-<!-- not a cmavo list -->
-          lotlei  5867      blolei  5847      lo'irlei 7456
-</programlisting>
+      lotkle  5878      blokle  5858      lo'ikle  6367 
+      <!-- not a cmavo list -->
+      lotlei  5867      blolei  5847      lo'irlei 7456
+    </programlisting>
     <para> <indexterm type="example-imported"><primary>Logical Language Group</primary><secondary>example</secondary></indexterm> So the form 
     <jbophrase>blolei</jbophrase> is preferred, but only by a tiny margin over 
     <jbophrase>blokle</jbophrase>; "lotlei" and "lotkle" are only slightly worse; 
     <jbophrase>lo'ikle</jbophrase> suffers because of its apostrophe, and 
     <jbophrase>lo'irlei</jbophrase> because of having both apostrophe and hyphen.</para>
     <para>Our third example will result in forming both a lujvo and a name from the tanru 
     <jbophrase>logji bangu girzu</jbophrase>, or 
     <quote>logical-language group</quote> in English. ( 
     <quote>The Logical Language Group</quote> is the name of the publisher of this book and the organization for the promotion of Lojban.)</para>
     <para>The available rafsi are 
     <quote>-loj-</quote> and 
     <quote>-logj-</quote>; 
     <quote>-ban-</quote>, 
     <quote>-bau-</quote>, and 
     <quote>-bang-</quote>; and 
     <quote>-gri-</quote> and 
     <quote>-girzu</quote>, and (for name purposes only) 
     <quote>-gir-</quote> and 
     <quote>-girz-</quote>. The resulting 12 lujvo possibilities are:</para>
     <programlisting xml:space="preserve">
-          loj-ban-gri      loj-bau-gri      loj-bang-gri 
-<!-- not a cmavo list -->
-          logj-ban-gri     logj-bau-gri     logj-bang-gri
-          loj-ban-girzu    loj-bau-girzu    loj-bang-girzu
-          logj-ban-girzu   logj-bau-girzu   logj-bang-girzu
-</programlisting>
+      loj-ban-gri      loj-bau-gri      loj-bang-gri 
+      <!-- not a cmavo list -->
+      logj-ban-gri     logj-bau-gri     logj-bang-gri
+      loj-ban-girzu    loj-bau-girzu    loj-bang-girzu
+      logj-ban-girzu   logj-bau-girzu   logj-bang-girzu
+    </programlisting>
     <para>and the 12 name possibilities are:</para>
     <programlisting xml:space="preserve">
-          loj-ban-gir.     loj-bau-gir.     loj-bang-gir. 
-<!-- not a cmavo list -->
-          logj-ban-gir.    logj-bau-gir.    logj-bang-gir.
-          loj-ban-girz.    loj-bau-girz.    loj-bang-girz.
-          logj-ban-girz.   logj-bau-girz.   logj-bang-girz.
-</programlisting>
+      loj-ban-gir.     loj-bau-gir.     loj-bang-gir. 
+      <!-- not a cmavo list -->
+      logj-ban-gir.    logj-bau-gir.    logj-bang-gir.
+      loj-ban-girz.    loj-bau-girz.    loj-bang-girz.
+      logj-ban-girz.   logj-bau-girz.   logj-bang-girz.
+    </programlisting>
     <para>After hyphenation, we have:</para>
     <programlisting xml:space="preserve">
-          lojbangri        lojbaugri        lojbangygri 
-<!-- not a cmavo list -->
-          logjybangri      logjybaugri      logjybangygri
-          lojbangirzu      lojbaugirzu      lojbangygirzu
-          logjybangirzu    logjybaugirzu    logjybangygirzu
+      lojbangri        lojbaugri        lojbangygri 
+      <!-- not a cmavo list -->
+      logjybangri      logjybaugri      logjybangygri
+      lojbangirzu      lojbaugirzu      lojbangygirzu
+      logjybangirzu    logjybaugirzu    logjybangygirzu
 
-          lojbangir.       lojbaugir.       lojbangygir.
-          logjybangir.     logjybaugir.     logjybangygir.
-          lojbangirz.      lojbaugirz.      lojbangygirz.
-          logjybangirz.    logjybaugirz.    logjybangygirz.
-</programlisting>
+      lojbangir.       lojbaugir.       lojbangygir.
+      logjybangir.     logjybaugir.     logjybangygir.
+      lojbangirz.      lojbaugirz.      lojbangygirz.
+      logjybangirz.    logjybaugirz.    logjybangygirz.
+    </programlisting>
     <para> <indexterm type="example-imported"><primary>sexual teacher</primary><secondary>male</secondary><tertiary>example</tertiary></indexterm>  <indexterm type="example-imported"><primary>male sexual teacher</primary><secondary>example</secondary></indexterm> The only fully reduced lujvo forms are 
     
     <jbophrase>lojbangri</jbophrase> and 
     <jbophrase>lojbaugri</jbophrase>, of which the latter has a slightly lower score: 8827 versus 8796, respectively. However, for the name of the organization, we chose to make sure the name of the language was embedded in it, and to use the clearer long-form rafsi for 
     <jbophrase>girzu</jbophrase>, producing 
     <jbophrase>lojbangirz.</jbophrase></para>
     <para>Finally, here is a four-part lujvo with a cmavo in it, based on the tanru 
     <jbophrase>nakni ke cinse ctuca</jbophrase> or 
     <quote>male (sexual teacher)</quote>. The 
     
     <quote>ke</quote> cmavo ensures the interpretation 
     <quote>teacher of sexuality who is male</quote>, rather than 
     <quote>teacher of male sexuality</quote>. Here are the possible forms of the lujvo, both before and after hyphenation:</para>
     <programlisting xml:space="preserve">
-          nak-kem-cin-ctu          nakykemcinctu
-          nak-kem-cin-ctuca        nakykemcinctuca
-          nak-kem-cins-ctu         nakykemcinsyctu
-          nak-kem-cins-ctuca       nakykemcinsyctuca
-          nakn-kem-cin-ctu         naknykemcinctu
-          nakn-kem-cin-ctuca       naknykemcinctuca
-          nakn-kem-cins-ctu        naknykemcinsyctu
-          nakn-kem-cins-ctuca      naknykemcinsyctuca
-</programlisting>
+      nak-kem-cin-ctu          nakykemcinctu
+      nak-kem-cin-ctuca        nakykemcinctuca
+      nak-kem-cins-ctu         nakykemcinsyctu
+      nak-kem-cins-ctuca       nakykemcinsyctuca
+      nakn-kem-cin-ctu         naknykemcinctu
+      nakn-kem-cin-ctuca       naknykemcinctuca
+      nakn-kem-cins-ctu        naknykemcinsyctu
+      nakn-kem-cins-ctuca      naknykemcinsyctuca
+    </programlisting>
     <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>algorithm for</secondary></indexterm> Of these forms, 
     <jbophrase>nakykemcinctu</jbophrase> is the shortest and is preferred by the scoring algorithm. On the whole, however, it might be better to just make a lujvo for 
     <jbophrase>cinse ctuca</jbophrase> (which would be 
     <jbophrase>cinctu</jbophrase>) since the sex of the teacher is rarely important. If there was a reason to specify 
     <quote>male</quote>, then the simpler tanru 
     <jbophrase>nakni cinctu</jbophrase> ( 
     <quote>male sexual-teacher</quote>) would be appropriate. This tanru is actually shorter than the four-part lujvo, since the 
     <quote>ke</quote> required for grouping need not be expressed.</para>
   </section>
   <section xml:id="chapter-morphology-section14">
@@ -2361,256 +2361,256 @@
         <listitem>
           <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>creation</secondary><tertiary>proscribed gismu pairs</tertiary></indexterm>  <indexterm type="general-imported"><primary>gismu</primary><secondary>too-similar</secondary></indexterm> The scores were divided by the length of the source-language word in its Lojbanized form, and then multiplied by a weighting value specific to each language, reflecting the proportional number of first-language and second-language speakers of the language. (Second-language speakers were reckoned at half their actual numbers.) The weights were chosen to sum to 1.00. The sum of the weighted scores was the total score for the proposed gismu form.</para>
         </listitem>
       </varlistentry>
       <varlistentry>
         <term>4)</term>
         <listitem>
           <para>Any gismu forms that conflicted with existing gismu were removed. Obviously, being identical with an existing gismu constitutes a conflict. In addition, a proposed gismu that was identical to an existing gismu except for the final vowel was considered a conflict, since two such gismu would have identical 4-letter rafsi.</para>
           <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>creation</secondary><tertiary>and transcription blunders</tertiary></indexterm> More subtly: If the proposed gismu was identical to an existing gismu except for a single consonant, and the consonant was "too similar” based on the following table, then the proposed gismu was rejected.</para>
           <programlisting>
-       proposed gismu		   existing gismu
-                b			p, v
-		c			j, s
-		d			t
-		f			p, v
-		g			k, x
-		j			c, z
-		k			g, x
-		l			r
-		m			n
-		n			m
-		p			b, f
-		r			l
-		s			c, z
-		t			d
-		v			b, f
-		x			g, k
-		z			j, s
-              </programlisting>
-              <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>source-language weights for</secondary></indexterm> See <xref linkend="chapter-morphology-section4"/> for an example.</para>
+            proposed gismu		   existing gismu
+            b			p, v
+            c			j, s
+            d			t
+            f			p, v
+            g			k, x
+            j			c, z
+            k			g, x
+            l			r
+            m			n
+            n			m
+            p			b, f
+            r			l
+            s			c, z
+            t			d
+            v			b, f
+            x			g, k
+            z			j, s
+          </programlisting>
+          <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>source-language weights for</secondary></indexterm> See <xref linkend="chapter-morphology-section4"/> for an example.</para>
         </listitem>
       </varlistentry>
       <varlistentry>
         <term>5)</term>
         <listitem>
           <para>The gismu form with the highest score usually became the actual gismu. Sometimes a lower-scoring form was used to provide a better rafsi. A few gismu were changed in error as a result of transcription blunders (for example, the gismu 
           <jbophrase>gismu</jbophrase> should have been 
           <jbophrase>gicmu</jbophrase>, but it's too late to fix it now).</para>
           <para>The language weights used to make most of the gismu were as follows:</para>
-<programlisting>
-        Chinese	0.36
-	English	0.21
-	Hindi		0.16
-	Spanish	0.11
-	Russian	0.09
-	Arabic		0.07
-		</programlisting>
-<para>reflecting 1985 number-of-speakers data. A few gismu were made much later using updated weights:</para>
-<programlisting>
-        Chinese	0.347
-	Hindi		0.196
-	English	0.160
-	Spanish	0.123
-	Russian	0.089
-	Arabic		0.085
-</programlisting>
-<para> <indexterm type="general-imported"><primary>gismu</primary><secondary>coined</secondary></indexterm>  <indexterm type="general-imported"><primary>gismu</primary><secondary>exceptions to gismu creation by algorithm</secondary></indexterm> (English and Hindi switched places due to demographic changes.)</para>
+          <programlisting>
+            Chinese	0.36
+            English	0.21
+            Hindi		0.16
+            Spanish	0.11
+            Russian	0.09
+            Arabic		0.07
+          </programlisting>
+          <para>reflecting 1985 number-of-speakers data. A few gismu were made much later using updated weights:</para>
+          <programlisting>
+            Chinese	0.347
+            Hindi		0.196
+            English	0.160
+            Spanish	0.123
+            Russian	0.089
+            Arabic		0.085
+          </programlisting>
+          <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>coined</secondary></indexterm>  <indexterm type="general-imported"><primary>gismu</primary><secondary>exceptions to gismu creation by algorithm</secondary></indexterm> (English and Hindi switched places due to demographic changes.)</para>
         </listitem>
       </varlistentry>
     </variablelist>
     <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>Lojban-specific</secondary></indexterm> Note that the stressed vowel of the gismu was considered sufficiently distinctive that two or more gismu may differ only in this vowel; as an extreme example, 
     
     <jbophrase>bradi</jbophrase>, 
     <jbophrase>bredi</jbophrase>, 
     <jbophrase>bridi</jbophrase>, and 
     <jbophrase>brodi</jbophrase> (but fortunately not 
     <jbophrase>brudi</jbophrase>) are all existing gismu.</para>
   </section>
   <section xml:id="chapter-morphology-section15">
     <title>Cultural and other non-algorithmic gismu</title>
     <para>The following gismu were not made by the gismu creation algorithm. They are, in effect, coined words similar to fu'ivla. They are exceptions to the otherwise mandatory gismu creation algorithm where there was sufficient justification for such exceptions. Except for the small metric prefixes and the assignable predicates beginning with 
     <quote>brod-</quote>, they all end in the letter 
     <quote>o</quote>, which is otherwise a rare letter in Lojban gismu.</para>
     <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>scientific-mathematical</secondary></indexterm> The following gismu represent concepts that are sufficiently unique to Lojban that they were either coined from combining forms of other gismu, or else made up out of whole cloth. These gismu are thus conceptually similar to lujvo even though they are only five letters long; however, unlike lujvo, they have rafsi assigned to them for use in building more complex lujvo. Assigning gismu to these concepts helps to keep the resulting lujvo reasonably short.</para>
     <programlisting xml:space="preserve">
-    broda       1st assignable predicate
-    brode       2nd assignable predicate
-    brodi       3rd assignable predicate
-    brodo       4th assignable predicate
-    brodu       5th assignable predicate
-    cmavo       structure word (from 
-<jbophrase>cmalu valsi</jbophrase>)
-    lojbo       Lojbanic (from 
-<jbophrase>logji bangu</jbophrase>)
-    lujvo       compound word (from 
-<jbophrase>pluja valsi</jbophrase>)
-    mekso       Mathematical EXpression
-</programlisting>
+      broda       1st assignable predicate
+      brode       2nd assignable predicate
+      brodi       3rd assignable predicate
+      brodo       4th assignable predicate
+      brodu       5th assignable predicate
+      cmavo       structure word (from 
+      <jbophrase>cmalu valsi</jbophrase>)
+      lojbo       Lojbanic (from 
+      <jbophrase>logji bangu</jbophrase>)
+      lujvo       compound word (from 
+      <jbophrase>pluja valsi</jbophrase>)
+      mekso       Mathematical EXpression
+    </programlisting>
     <para>It is important to understand that even though 
     <jbophrase>cmavo</jbophrase>, 
     <jbophrase>lojbo</jbophrase>, and 
     <jbophrase>lujvo</jbophrase> were made up from parts of other gismu, they are now full-fledged gismu used in exactly the same way as all other gismu, both in grammar and in word formation.</para>
     <para>The following three groups of gismu represent concepts drawn from the international language of science and mathematics. They are used for concepts that are represented in most languages by a root which is recognized internationally.</para>
     <para>Small metric prefixes (values less than 1):</para>
     <programlisting xml:space="preserve">
-    decti       .1/deci
-    centi       .01/centi
-    milti       .001/milli
-    mikri       1E-6/micro
-    nanvi       1E-9/nano
-    picti       1E-12/pico
-    femti       1E-15/femto
-    xatsi       1E-18/atto
-    zepti       1E-21/zepto
-    gocti       1E-24/yocto
-</programlisting>
+      decti       .1/deci
+      centi       .01/centi
+      milti       .001/milli
+      mikri       1E-6/micro
+      nanvi       1E-9/nano
+      picti       1E-12/pico
+      femti       1E-15/femto
+      xatsi       1E-18/atto
+      zepti       1E-21/zepto
+      gocti       1E-24/yocto
+    </programlisting>
     <para>Large metric prefixes (values greater than 1):</para>
     <programlisting xml:space="preserve">
-    dekto       10/deka
-    xecto       100/hecto
-    kilto       1000/kilo
-    megdo       1E6/mega
-    gigdo       1E9/giga
-    terto       1E12/tera
-    petso       1E15/peta
-    xexso       1E18/exa
-    zetro       1E21/zetta
-    gotro       1E24/yotta
-</programlisting>
+      dekto       10/deka
+      xecto       100/hecto
+      kilto       1000/kilo
+      megdo       1E6/mega
+      gigdo       1E9/giga
+      terto       1E12/tera
+      petso       1E15/peta
+      xexso       1E18/exa
+      zetro       1E21/zetta
+      gotro       1E24/yotta
+    </programlisting>
     <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>cultural</secondary></indexterm> Other scientific or mathematical terms:</para>
     <programlisting xml:space="preserve">
-    delno       candela
-    kelvo       kelvin
-    molro       mole
-    radno       radian
-    sinso       sine
-    stero       steradian
-    tanjo       tangent
-    xampo       ampere
-</programlisting>
+      delno       candela
+      kelvo       kelvin
+      molro       mole
+      radno       radian
+      sinso       sine
+      stero       steradian
+      tanjo       tangent
+      xampo       ampere
+    </programlisting>
     <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>for Lojban source languages</secondary></indexterm>  <indexterm type="general-imported"><primary>gismu</primary><secondary>for languages</secondary></indexterm> The gismu 
     <jbophrase>sinso</jbophrase> and 
     <jbophrase>tanjo</jbophrase> were only made non-algorithmically because they were identical (having been borrowed from a common source) in all the dictionaries that had translations. The other terms in this group are units in the international metric system; some metric units, however, were made by the ordinary process (usually because they are different in Chinese).</para>
     <para>Finally, there are the cultural gismu, which are also borrowed, but by modifying a word from one particular language, instead of using the multi-lingual gismu creation algorithm. Cultural gismu are used for words that have local importance to a particular culture; other cultures or languages may have no word for the concept at all, or may borrow the word from its home culture, just as Lojban does. In such a case, the gismu algorithm, which uses weighted averages, doesn't accurately represent the frequency of usage of the individual concept. Cultural gismu are not even required to be based on the six major languages.</para>
     <para>The six Lojban source languages:</para>
     
     <programlisting xml:space="preserve">
-    jungo       Chinese (from 
-<quote>Zhong
-<superscript>1</superscript> guo
-<superscript>2</superscript></quote>)
-    glico       English
-    xindo       Hindi
-    spano       Spanish
-    rusko       Russian
-    xrabo       Arabic
-</programlisting>
+      jungo       Chinese (from 
+      <quote>Zhong
+      <superscript>1</superscript> guo
+      <superscript>2</superscript></quote>)
+      glico       English
+      xindo       Hindi
+      spano       Spanish
+      rusko       Russian
+      xrabo       Arabic
+    </programlisting>
     <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>for countries</secondary></indexterm> Seven other widely spoken languages that were on the list of candidates for gismu-making, but weren't used:</para>
     <programlisting xml:space="preserve">
-    bengo       Bengali
-    porto       Portuguese
-    baxso       Bahasa Melayu/Bahasa Indonesia
-    ponjo       Japanese (from 
-<quote>Nippon</quote>)
-    dotco       German (from 
-<quote>Deutsch</quote>)
-    fraso       French (from 
-<quote>Français</quote>)
-    xurdo       Urdu
-</programlisting>
+      bengo       Bengali
+      porto       Portuguese
+      baxso       Bahasa Melayu/Bahasa Indonesia
+      ponjo       Japanese (from 
+      <quote>Nippon</quote>)
+      dotco       German (from 
+      <quote>Deutsch</quote>)
+      fraso       French (from 
+      <quote>Français</quote>)
+      xurdo       Urdu
+    </programlisting>
     <para> <indexterm type="general-imported"><primary>continents</primary><secondary>gismu for</secondary></indexterm>  <indexterm type="general-imported"><primary>gismu</primary><secondary>geographical</secondary></indexterm> (Urdu and Hindi began as the same language with different writing systems, but have now become somewhat different, principally in borrowed vocabulary. Urdu-speakers were counted along with Hindi-speakers when weights were assigned for gismu-making purposes.)</para>
     <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>ethnic</secondary></indexterm> Countries with a large number of speakers of any of the above languages (where the meaning of 
     <jbophrase>large</jbophrase> is dependent on the specific language):</para>
     <programlisting xml:space="preserve">
-         English:
+      English:
 
-    merko       American
-    brito       British
-    skoto       Scottish
-    sralo       Australian
-    kadno       Canadian
+      merko       American
+      brito       British
+      skoto       Scottish
+      sralo       Australian
+      kadno       Canadian
 
-         Spanish:
+      Spanish:
 
-    gento       Argentinian
-    mexno       Mexican
+      gento       Argentinian
+      mexno       Mexican
 
-         Russian:
+      Russian:
 
-    softo       Soviet/USSR
-    vukro       Ukrainian
+      softo       Soviet/USSR
+      vukro       Ukrainian
 
-         Arabic:
+      Arabic:
 
-    filso       Palestinian
-    jerxo       Algerian
-    jordo       Jordanian
-    libjo       Libyan
-    lubno       Lebanese
-    misro       Egyptian (from 
-<quote>Mizraim</quote>)
-    morko       Moroccan
-    rakso       Iraqi
-    sadjo       Saudi
-    sirxo       Syrian
+      filso       Palestinian
+      jerxo       Algerian
+      jordo       Jordanian
+      libjo       Libyan
+      lubno       Lebanese
+      misro       Egyptian (from 
+      <quote>Mizraim</quote>)
+      morko       Moroccan
+      rakso       Iraqi
+      sadjo       Saudi
+      sirxo       Syrian
 
-         Bahasa Melayu/Bahasa Indonesia:
+      Bahasa Melayu/Bahasa Indonesia:
 
-    bindo       Indonesian
-    meljo       Malaysian
+      bindo       Indonesian
+      meljo       Malaysian
 
-         Portuguese:
+      Portuguese:
 
-    brazo       Brazilian
+      brazo       Brazilian
 
-         Urdu:
+      Urdu:
 
-    kisto       Pakistani
-    
-</programlisting>
+      kisto       Pakistani
+      
+    </programlisting>
     <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>religious</secondary></indexterm> The continents (and oceanic regions) of the Earth:</para>
     
     <programlisting xml:space="preserve">
-    bemro       North American (from 
-<jbophrase>berti merko</jbophrase>)
-    dzipo       Antarctican (from 
-<jbophrase>cadzu cipni</jbophrase>)
-    ketco       South American (from 
-<quote>Quechua</quote>)
-    friko       African
-    polno       Polynesian/Oceanic
-    ropno       European
-    xazdo       Asiatic
-</programlisting>
+      bemro       North American (from 
+      <jbophrase>berti merko</jbophrase>)
+      dzipo       Antarctican (from 
+      <jbophrase>cadzu cipni</jbophrase>)
+      ketco       South American (from 
+      <quote>Quechua</quote>)
+      friko       African
+      polno       Polynesian/Oceanic
+      ropno       European
+      xazdo       Asiatic
+    </programlisting>
     <para>A few smaller but historically important cultures:</para>
     <programlisting xml:space="preserve">
-    latmo       Latin/Roman
-    srito       Sanskrit
-    xebro       Hebrew/Israeli/Jewish
-    xelso       Greek (from 
-<quote>Hellas</quote>)
-</programlisting>
+      latmo       Latin/Roman
+      srito       Sanskrit
+      xebro       Hebrew/Israeli/Jewish
+      xelso       Greek (from 
+      <quote>Hellas</quote>)
+    </programlisting>
     <para> <indexterm type="general-imported"><primary>cultural words</primary><secondary>rafsi fu'ivla proposal for</secondary></indexterm>  <indexterm type="general-imported"><primary>rafsi fu'ivla</primary></indexterm> Major world religions:</para>
     <programlisting xml:space="preserve">
-    budjo       Buddhist
-    dadjo       Taoist
-    muslo       Islamic/Moslem
-    xriso       Christian
-</programlisting>
+      budjo       Buddhist
+      dadjo       Taoist
+      muslo       Islamic/Moslem
+      xriso       Christian
+    </programlisting>
     <para> <indexterm type="general-imported"><primary>fu'ivla</primary><secondary>form for rafsi fu'ivla proposal</secondary></indexterm>  <indexterm type="general-imported"><primary>CCVVCV fu'ivla</primary><secondary>and rafsi fu'ivla proposal</secondary></indexterm> A few terms that cover multiple groups of the above:</para>
     <programlisting xml:space="preserve">
-    jegvo       Jehovist (Judeo-Christian-Moslem)
-    semto       Semitic
-    slovo       Slavic
-    xispo       Hispanic (New World Spanish)
-</programlisting>
+      jegvo       Jehovist (Judeo-Christian-Moslem)
+      semto       Semitic
+      slovo       Slavic
+      xispo       Hispanic (New World Spanish)
+    </programlisting>
   </section>
   <section xml:id="chapter-morphology-section16">
     <title>rafsi fu'ivla: a proposal</title>
     <para>The list of cultures represented by gismu, given in 
     <xref linkend="chapter-morphology-section15"/>, is unavoidably controversial. Much time has been spent debating whether this or that culture 
     <quote>deserves a gismu</quote> or 
     <quote>must languish in fu'ivla space</quote>. To help defuse this argument, a last-minute proposal was made when this book was already substantially complete. I have added it here with experimental status: it is not yet a standard part of Lojban, since all its implications have not been tested in open debate, and it affects a part of the language (lujvo-making) that has long been stable, but is known to be fragile in the face of small changes. (Many attempts were made to add general mechanisms for making lujvo that contained fu'ivla, but all failed on obvious or obscure counterexamples; finally the general 
     <quote>zei</quote> mechanism was devised instead.)</para>
     <para>The first part of the proposal is uncontroversial and involves no change to the language mechanisms. All valid Type 4 fu'ivla of the form CCVVCV would be reserved for cultural brivla analogous to those described in 
     <xref linkend="chapter-morphology-section15"/>. For example,</para>

commit ddc1332254c74ec6707af35828eb347ea68609c8
Author: Eitan Postavsky <eitanp32@gmail.com>
Date:   Sun Jan 2 16:41:35 2011 -0500

    Fixed chapter 5 examples and example links.
    
    * Some <gloss>s were actually <jbo>, some <en>s were actually
      <gloss>s.
    * One very long example had gotten broken up into many small <jbo>s,
      <gloss>s, and <en>s.
    * One place refered to examples by number; the numbers were replaced
      with <xref>s (hopefully I made no mistakes with the random IDs,
      but...).
    * Some examples had <en>s which were actually commentary about the
      example.

diff --git a/todocbook/5.xml b/todocbook/5.xml
index 30b9d7f..7fb00f2 100644
--- a/todocbook/5.xml
+++ b/todocbook/5.xml
@@ -453,21 +453,21 @@
     <jbophrase>bo</jbophrase> is present at all: the last two are grouped together. Not surprisingly, this is called the 
     <quote>right-grouping rule</quote>, and it is associated with every use of 
     
     <jbophrase>bo</jbophrase> in the language. Therefore,</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-snKn">
       <title>
         <anchor xml:id="c5e4d6"/>
       </title>
       <interlinear-gloss>
         <jbo>ta cmalu bo nixli bo ckule</jbo>
-        <en>That is-a-little type-of (girl type-of school).</en>
+        <gloss>That is-a-little type-of (girl type-of school).</gloss>
       </interlinear-gloss>
     </example>
     <para>means the same as 
     <xref linkend="example-random-id-nwuU"/>, not 
     <xref linkend="example-random-id-jquh"/>. This rule may seem peculiar at first, but one of its consequences is that 
     <jbophrase>bo</jbophrase> is never necessary between the first two elements of any of the complex tanru presented so far: all of 
     <xref linkend="example-random-id-qjmr"/> through 
     <xref linkend="example-random-id-qjop"/> could have 
     <jbophrase>bo</jbophrase> inserted between 
     <jbophrase>melbi</jbophrase> and 
@@ -498,65 +498,65 @@
     
     <jbophrase>ke</jbophrase> and 
     <jbophrase>ke'e</jbophrase> (belonging to selma'o KE and KEhE respectively). Any portion of a selbri sandwiched between these two cmavo is taken to be a single tanru component, independently of what is adjacent to it. Thus, 
     <xref linkend="example-random-id-qjmr"/> can be rewritten in any of the following ways:</para>
     <example xml:id="example-random-id-qjqu" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c5e5d1"/>
       </title>
       <interlinear-gloss>
         <jbo>ta ke melbi cmalu ke'e nixli ckule</jbo>
-        <en>That is-a-( pretty little ) girl school.</en>
+        <gloss>That is-a-( pretty little ) girl school.</gloss>
       </interlinear-gloss>
     </example>
     <example xml:id="example-random-id-qJQz" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c5e5d2"/>
       </title>
       <interlinear-gloss>
         <jbo>ta ke ke melbi cmalu ke'e nixli ke'e ckule</jbo>
-        <en>That is-a-( ( pretty little ) girl ) school.</en>
+        <gloss>That is-a-( ( pretty little ) girl ) school.</gloss>
       </interlinear-gloss>
     </example>
     <example xml:id="example-random-id-qjSA" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c5e5d3"/>
       </title>
       <interlinear-gloss>
         <jbo>ta ke ke ke melbi cmalu ke'e nixli ke'e ckule ke'e</jbo>
-        <en>That is-a-( ( ( pretty little ) girl ) school ).</en>
+        <gloss>That is-a-( ( ( pretty little ) girl ) school ).</gloss>
       </interlinear-gloss>
     </example>
     <para>Even more versions could be created simply by placing any number of 
     <jbophrase>ke</jbophrase> cmavo at the beginning of the selbri, and a like number of 
     <jbophrase>ke'e</jbophrase> cmavo at its end. Obviously, all of these are a waste of breath once the left-grouping rule has been grasped. However, the following is equivalent to 
     <xref linkend="example-random-id-qjog"/> and may be easier to understand:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-zV26">
       <title>
         <anchor xml:id="c5e5d4"/>
       </title>
       <interlinear-gloss>
         <jbo>ta melbi ke cmalu nixli ke'e ckule</jbo>
-        <en>That is-a-( pretty type-of ( little type-of girl ) ) type-of school.</en>
+        <gloss>That is-a-( pretty type-of ( little type-of girl ) ) type-of school.</gloss>
       </interlinear-gloss>
     </example>
     <para>Likewise, a 
     <jbophrase>ke</jbophrase> and 
     <jbophrase>ke'e</jbophrase> version of 
     <xref linkend="example-random-id-qjNi"/> would be:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-AUdM">
       <title>
         <anchor xml:id="c5e5d5"/>
       </title>
       <interlinear-gloss>
         <jbo>ta melbi cmalu ke nixli ckule [ke'e]</jbo>
-        <en>That is-a-(pretty type-of little) ( girl type-of school ).</en>
+        <gloss>That is-a-(pretty type-of little) ( girl type-of school ).</gloss>
       </interlinear-gloss>
     </example>
     <para>The final 
     <jbophrase>ke'e</jbophrase> is given in square brackets here to indicate that it can be elided. It is always possible to elide 
     
     <jbophrase>ke'e</jbophrase> at the end of the selbri, making 
     <xref linkend="example-random-id-AUdM"/> as terse as 
     <xref linkend="example-random-id-qjNi"/>.</para>
     <para>Now how about that fifth grouping? It is</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-tz0L">
@@ -578,31 +578,31 @@
     <jbophrase>bo</jbophrase> and 
     <jbophrase>ke ... ke'e</jbophrase> in a single selbri. For instance, 
     <xref linkend="example-random-id-qjop"/>, which in pure 
     <jbophrase>ke ... ke'e</jbophrase> form is</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-uBS4">
       <title>
         <anchor xml:id="c5e5d7"/>
       </title>
       <interlinear-gloss>
         <jbo>ta melbi ke cmalu ke nixli ckule [ke'e] [ke'e]</jbo>
-        <en>That is-a-pretty type-of ( little type-of ( girl type-of school ) ).</en>
+        <gloss>That is-a-pretty type-of ( little type-of ( girl type-of school ) ).</gloss>
       </interlinear-gloss>
     </example>
     <para>can equivalently be expressed as:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-Ei5U">
       <title>
         <anchor xml:id="c5e5d8"/>
       </title>
       <interlinear-gloss>
         <jbo>ta melbi ke cmalu nixli bo ckule [ke'e]</jbo>
-        <en>That is-a-pretty type-of ( little type-of ( girl type-of school ) ).</en>
+        <gloss>That is-a-pretty type-of ( little type-of ( girl type-of school ) ).</gloss>
       </interlinear-gloss>
     </example>
     <para>and in many other different forms as well.</para>
   </section>
 
   <section xml:id="section-logical-connection">
     <title>Logical connection within tanru</title>
     <para>The following cmavo are discussed in this section:</para>
     <cmavo-list>
       <cmavo-entry>
@@ -634,194 +634,194 @@
     <para>  Consider the English phrase 
     <quote>big red dog</quote>. How shall this be rendered as a Lojban tanru? The naive attempt:</para>
     
     <example role="interlinear-gloss-example" xml:id="example-random-id-riAq">
       <title>
         <indexterm type="example-imported"><primary>big red dog</primary><secondary>example</secondary></indexterm>
         <anchor xml:id="c5e6d1"/>
       </title>
       <interlinear-gloss>
         <jbo>barda xunre gerku</jbo>
-        <en>(big type-of red) type-of dog</en>
+        <gloss>(big type-of red) type-of dog</gloss>
       </interlinear-gloss>
     </example>
     <para>will not do, as it means a dog whose redness is big, in whatever way redness might be described as 
     <quote>big</quote>. Nor is</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-6MqF">
       <title>
         <anchor xml:id="c5e6d2"/>
       </title>
       <interlinear-gloss>
         <jbo>barda xunre bo gerku</jbo>
-        <en>big type-of (red type-of dog)</en>
+        <gloss>big type-of (red type-of dog)</gloss>
       </interlinear-gloss>
     </example>
     <para> <indexterm type="general-imported"><primary>adjective ordering</primary></indexterm> much better. After all, the straightforward understanding of the English phrase is that the dog is big as compared with other dogs, not merely as compared with other red dogs. In fact, the bigness and redness are independent properties of the dog, and only obscure rules of English adjective ordering prevent us from saying 
     
     <quote>red big dog</quote>.</para>
     <para> <indexterm type="lojban-word-imported"><primary>je</primary></indexterm>  <indexterm type="general-imported"><primary>logical connectives</primary><secondary>in tanru</secondary></indexterm> The Lojban approach to this problem is to introduce the cmavo 
     <jbophrase>je</jbophrase>, which is one of the many equivalents of English 
     <quote>and</quote>. A big red dog is one that is both big and red, and we can say:</para>
     
     <example role="interlinear-gloss-example" xml:id="example-random-id-0UrF">
       <title>
         <anchor xml:id="c5e6d3"/>
       </title>
       <interlinear-gloss>
         <jbo>barda je xunre gerku</jbo>
-        <en>(big and red) type-of dog</en>
+        <gloss>(big and red) type-of dog</gloss>
       </interlinear-gloss>
     </example>
     <para>Of course,</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-DzeP">
       <title>
         <anchor xml:id="c5e6d4"/>
       </title>
       <interlinear-gloss>
         <jbo>xunre je barda gerku</jbo>
-        <en>(red and big) type-of dog</en>
+        <gloss>(red and big) type-of dog</gloss>
       </interlinear-gloss>
     </example>
     <para> <indexterm type="general-imported"><primary>logical connectives in tanru</primary><secondary>effect on tanru grouping</secondary></indexterm> is equally satisfactory and means the same thing. As these examples indicate, joining two brivla with 
     <jbophrase>je</jbophrase> makes them a unit for tanru purposes. However, explicit grouping with 
     <jbophrase>bo</jbophrase> or 
     <jbophrase>ke ... ke'e</jbophrase> associates brivla more closely than 
     <jbophrase>je</jbophrase> does:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-LES9">
       <title>
         <anchor xml:id="c5e6d5"/>
       </title>
       <interlinear-gloss>
         <jbo>barda je pelxu bo xunre gerku</jbo>
-        <gloss>barda je ke pelxu xunre ke'e gerku</gloss>
+        <jbo>barda je ke pelxu xunre ke'e gerku</jbo>
         <gloss>(big and (yellow type-of red)) dog</gloss>
-        <en>big yellowish-red dog</en>
+        <gloss>big yellowish-red dog</gloss>
       </interlinear-gloss>
     </example>
     <para>With no grouping indicators, we get:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-fuhg">
       <title>
         <anchor xml:id="c5e6d6"/>
       </title>
       <interlinear-gloss>
         <jbo>barda je pelxu xunre gerku</jbo>
         <gloss>((big and yellow) type-of red) type-of dog</gloss>
-        <en>biggish- and yellowish-red dog</en>
+        <gloss>biggish- and yellowish-red dog</gloss>
       </interlinear-gloss>
     </example>
     <para>which again raises the question of 
     <xref linkend="example-random-id-riAq"/>: what does 
     <quote>biggish-red</quote> mean?</para>
     <para> <indexterm type="general-imported"><primary>logical connectives in tanru</primary><secondary>usefulness of</secondary></indexterm> Unlike 
     <jbophrase>bo</jbophrase> and 
     <jbophrase>ke ... ke'e</jbophrase>, 
     <jbophrase>je</jbophrase> is useful as well as merely legal within simple tanru. It may be used to partly resolve the ambiguity of simple tanru:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-W56H">
       <title>
         <anchor xml:id="c5e6d7"/>
       </title>
       <interlinear-gloss>
         <jbo>ta blanu je zdani</jbo>
-        <en>that is-blue and is-a-house</en>
+        <gloss>that is-blue and is-a-house</gloss>
       </interlinear-gloss>
     </example>
     <para>definitely refers to something which is both blue and is a house, and not to any of the other possible interpretations of simple 
     <jbophrase>blanu zdani</jbophrase>. Furthermore, 
     <jbophrase>blanu zdani</jbophrase> refers to something which is blue in the way that houses are blue; 
     <jbophrase>blanu je zdani</jbophrase> has no such implication - the blueness of a 
     <jbophrase>blanu je zdani</jbophrase> is independent of its houseness.</para>
     <para>With the addition of 
     <jbophrase>je</jbophrase>, many more versions of 
     <quote>pretty little girls' school</quote> are made possible: see 
     
     <xref linkend="section-pretty-school-groupings"/> for a complete list.</para>
     <para>A subtle point in the semantics of tanru like 
     <xref linkend="example-random-id-0UrF"/> needs special elucidation. There are at least two possible interpretations of:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-N5Bt">
       <title>
         <anchor xml:id="c5e6d8"/>
       </title>
       <interlinear-gloss>
         <jbo>ta melbi je nixli ckule</jbo>
-        <en>That is-a-(beautiful and girl) type-of school.</en>
+        <gloss>That is-a-(beautiful and girl) type-of school.</gloss>
       </interlinear-gloss>
     </example>
     <para>It can be understood as:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-FCDa">
       <title>
         <anchor xml:id="c5e6d9"/>
       </title>
       <interlinear-gloss>
-        <jbo>That is a girls' school and a beautiful school.</jbo>
+        <gloss>That is a girls' school and a beautiful school.</gloss>
       </interlinear-gloss>
     </example>
     <para>or as:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-aFxm">
       <title>
         <anchor xml:id="c5e6d10"/>
       </title>
       <interlinear-gloss>
-        <jbo>That is a school for things which are both girls and beautiful.</jbo>
+        <en>That is a school for things which are both girls and beautiful.</en>
       </interlinear-gloss>
     </example>
     <para> <indexterm type="general-imported"><primary>logical connectives in tanru</primary><secondary>ambiguity of</secondary></indexterm> The interpretation specified by 
     <xref linkend="example-random-id-FCDa"/> treats the tanru as a sort of abbreviation for:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-pHHw">
       <title>
         <anchor xml:id="c5e6d11"/>
       </title>
       <interlinear-gloss>
         <jbo>ta ke melbi ckule ke'e je ke nixli ckule [ke'e]</jbo>
-        <en>That is-a-( beautiful type-of school ) and ( girl type-of school )</en>
+        <gloss>That is-a-( beautiful type-of school ) and ( girl type-of school )</gloss>
       </interlinear-gloss>
     </example>
     <para>whereas the interpretation specified by 
     <xref linkend="example-random-id-aFxm"/> does not. This is a kind of semantic ambiguity for which Lojban does not compel a firm resolution. The way in which the school is said to be of type 
     <quote>beautiful and girl</quote> may entail that it is separately a beautiful school and a girls' school; but the alternative interpretation, that the members of the school are beautiful and girls, is also possible. Still another interpretation is:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-2cjH">
       <title>
         <anchor xml:id="c5e6d12"/>
       </title>
       <interlinear-gloss>
-        <jbo>That is a school for beautiful things and also for girls.</jbo>
+        <en>That is a school for beautiful things and also for girls.</en>
       </interlinear-gloss>
     </example>
     <para>so while the logical connectives help to resolve the meaning of tanru, they by no means compel a single meaning in and of themselves.</para>
     <para> <indexterm type="general-imported"><primary>logical connectives in tanru</primary><secondary>effect on formal logical manipulations</secondary></indexterm> In general, logical connectives within tanru cannot undergo the formal manipulations that are possible with the related logical connectives that exist outside tanru; see 
     <xref linkend="chapter-connectives"/> for further details.</para>
     <para> <indexterm type="lojban-word-imported"><primary>JA selma'o</primary></indexterm> The logical connective 
     <jbophrase>je</jbophrase> is only one of the fourteen logical connectives that Lojban provides. Here are a few examples of some of the others:</para>
     <example xml:id="example-random-id-qJse" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c5e6d13"/>
       </title>
       <interlinear-gloss>
         <jbo>le bajra cu jinga ja te jinga</jbo>
-        <en>the runner(s) is/are winner(s) or loser(s).</en>
+        <gloss>the runner(s) is/are winner(s) or loser(s).</gloss>
       </interlinear-gloss>
     </example>
     <example xml:id="example-random-id-qJsg" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c5e6d14"/>
       </title>
       <interlinear-gloss>
         <jbo>blanu naja lenku skapi</jbo>
         <gloss>(blue only-if cold) skin</gloss>
         <en>skin which is blue only if it is cold</en>
       </interlinear-gloss>
     </example>
     <example xml:id="example-random-id-qjsy" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c5e6d15"/>
       </title>
       <interlinear-gloss>
-        <jbo>xamgu jo cortu nuntavla</jbo>
+        <jbo>xamgu jo tordu nuntavla</jbo>
         <gloss>(good if-and-only-if short) speech</gloss>
         <en>speech which is good if (and only if) it is short</en>
       </interlinear-gloss>
     </example>
     <example xml:id="example-random-id-qjtD" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c5e6d16"/>
       </title>
       <interlinear-gloss>
         <jbo>vajni ju pluka nuntavla</jbo>
@@ -844,68 +844,66 @@
     <jbophrase>ju</jbophrase> means 
     <quote>whether or not</quote> in 
     <xref linkend="example-random-id-qjtD"/>.</para>
     <para> <indexterm type="general-imported"><primary>multiple logical connectives</primary><secondary>within tanru</secondary></indexterm> Now consider the following example:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-NuWM">
       <title>
         <anchor xml:id="c5e6d17"/>
       </title>
       <interlinear-gloss>
         <jbo>ricfu je blanu jabo crino</jbo>
-        
-        <en>rich and (blue or green)</en>
+        <gloss>rich and (blue or green)</gloss>
       </interlinear-gloss>
     </example>
     <para> <indexterm type="lojban-word-imported"><primary>jabo</primary></indexterm>  <indexterm type="general-imported"><primary>tanru grouping with JA+BO</primary><secondary>effect on tanru grouping</secondary></indexterm> which illustrates a new grammatical feature: the use of both 
     <jbophrase>ja</jbophrase> and 
     <jbophrase>bo</jbophrase> between tanru components. The two cmavo combine to form a compound whose meaning is that of 
     <jbophrase>ja</jbophrase> but which groups more closely; 
     <jbophrase glossary="false">jabo</jbophrase> is to 
     
     <jbophrase>ja</jbophrase> as plain 
     <jbophrase>bo</jbophrase> is to no cmavo at all. However, both 
     <jbophrase>ja</jbophrase> and 
     <jbophrase glossary="false">jabo</jbophrase> group less closely than 
     
     <jbophrase>bo</jbophrase> does:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-KxqX">
       <title>
         <anchor xml:id="c5e6d18"/>
       </title>
       <interlinear-gloss>
         <jbo>ricfu je blanu jabo crino bo blanu</jbo>
-        
         <gloss>rich and (blue or green – blue)</gloss>
-        <en>rich and (blue or greenish-blue)</en>
+        <gloss>rich and (blue or greenish-blue)</gloss>
       </interlinear-gloss>
     </example>
     <para>An alternative form of 
     <xref linkend="example-random-id-NuWM"/> is:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-2WtT">
       <title>
         <anchor xml:id="c5e6d19"/>
       </title>
       <interlinear-gloss>
         <jbo>ricfu je ke blanu ja crino [ke'e]</jbo>
-        <en>rich and (blue or green)</en>
+        <gloss>rich and (blue or green)</gloss>
       </interlinear-gloss>
     </example>
     <para> <indexterm type="general-imported"><primary>non-logical connectives</primary><secondary>within tanru</secondary></indexterm> In addition to the logical connectives, there are also a variety of non-logical connectives, grammatically equivalent to the logical ones. The only one with a well-understood meaning in tanru contexts is 
     <jbophrase>joi</jbophrase>, which is the kind of 
     <quote>and</quote> that denotes a mixture:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-Hr1L">
       <title>
         <anchor xml:id="c5e6d20"/>
       </title>
       <interlinear-gloss>
         <jbo>ti blanu joi xunre bolci</jbo>
-        <en>This is-a-(blue and red) ball.</en>
+        <gloss>This is-a-(blue and red) ball.</gloss>
         
       </interlinear-gloss>
     </example>
     <para>The ball described is neither solely red nor solely blue, but probably striped or in some other way exhibiting a combination of the two colors. 
     <xref linkend="example-random-id-Hr1L"/> is distinct from:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-NAhT">
       <title>
         <anchor xml:id="c5e6d21"/>
       </title>
       <interlinear-gloss>
@@ -914,40 +912,40 @@
       </interlinear-gloss>
     </example>
     <para>which would be a ball whose color is some sort of purple tending toward red, since 
     <jbophrase>xunre</jbophrase> is the more important of the two components. On the other hand,</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-78C3">
       <title>
         <anchor xml:id="c5e6d22"/>
       </title>
       <interlinear-gloss>
         <jbo>ti blanu je xunre bolci</jbo>
-        <en>This is a (blue and red) ball</en>
+        <gloss>This is a (blue and red) ball</gloss>
         
       </interlinear-gloss>
     </example>
     <para>is probably self-contradictory, seeming to claim that the ball is independently both blue and red at the same time, although some sensible interpretation may exist.</para>
     
     <para> <indexterm type="lojban-word-imported"><primary>gi</primary></indexterm>  <indexterm type="lojban-word-imported"><primary>gu'e</primary></indexterm>  <indexterm type="general-imported"><primary>forethought logical connectives</primary><secondary>within tanru</secondary></indexterm> Finally, just as English 
     <quote>and</quote> has the variant form 
     <quote>both ... and</quote>, so 
     <jbophrase>je</jbophrase> between tanru components has the variant form 
     <jbophrase>gu'e ... gi</jbophrase>, where 
     <jbophrase>gu'e</jbophrase> is placed before the components and 
     <jbophrase>gi</jbophrase> between them:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-gLbh">
       <title>
         <anchor xml:id="c5e6d23"/>
       </title>
       <interlinear-gloss>
         <jbo>gu'e barda gi xunre gerku</jbo>
-        <en>(both big and red) type-of dog</en>
+        <gloss>(both big and red) type-of dog</gloss>
       </interlinear-gloss>
     </example>
     <para>is equivalent in meaning to 
     <xref linkend="example-random-id-0UrF"/>. For each logical connective related to 
     <jbophrase>je</jbophrase>, there is a corresponding connective related to 
     <jbophrase>gu'e ... gi</jbophrase> in a systematic way.</para>
     <para> <indexterm type="general-imported"><primary>forethought logical connectives in tanru</primary><secondary>effect on tanru grouping</secondary></indexterm> The portion of a 
     <jbophrase>gu'e ... gi</jbophrase> construction before the 
     <jbophrase>gi</jbophrase> is a full selbri, and may use any of the selbri resources including 
     <jbophrase>je</jbophrase> logical connections. After the 
@@ -1040,63 +1038,48 @@
     <jbophrase>bei</jbophrase> (of selma'o BEI), and the list of sumti is terminated by the elidable terminator 
     <jbophrase>be'o</jbophrase> (of selma'o BEhO).</para>
     <para> <indexterm type="general-imported"><primary>linked sumti</primary><secondary>definition</secondary></indexterm> Grammatically, a brivla with sumti linked to it in this fashion plays the same role in tanru as a simple brivla. To illustrate, here is a fully fleshed-out version of 
     <xref linkend="example-random-id-nwuU"/>, with all places filled in:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-7vxB">
       <title>
         <indexterm type="example-imported"><primary>Brooklyn</primary><secondary>example</secondary></indexterm>
         <anchor xml:id="c5e7d3"/>
       </title>
       <interlinear-gloss>
-        <jbo>ti cmalu be le ka canlu</jbo>
-        <gloss>bei lo'e ckule be'o</gloss>
-        <gloss>nixli be li mu bei lo merko be'o bo</gloss>
-        <gloss>ckule la bryklyn. loi pemci</gloss>
-        <gloss>le mela nu,IORK. prenu</gloss>
-        <gloss>le jecta</gloss>
-        <gloss>This is a small (in-dimension the property-of volume</gloss>
-        
-        <gloss>by-standard the-typical school)</gloss>
-        <gloss>(girl (of-years the-number five by-standard some American-thing)</gloss>
-        <gloss>school) in-Brooklyn with-subject poems</gloss>
-        
-        <gloss>for-audience New-York persons</gloss>
-        <gloss>with-operator the state.</gloss>
-        <gloss>This is a school, small in volume compared to the typical school, pertaining</gloss>
-        <gloss>to five-year-old girls (by American standards), in Brooklyn, teaching poetry</gloss>
-        
-        <en>to the New York community and operated by the state.</en>
+        <jbo>ti cmalu be le ka canlu bei lo'e ckule be'o nixli be li mu bei lo merko be'o bo ckule la bryklyn. loi pemci le mela nu,IORK. prenu le jecta</jbo>
+        <gloss>This is a small (in-dimension the property-of volume by-standard the-typical school) (girl (of-years the-number five by-standard some American-thing) school) in-Brooklyn with-subject poems for-audience New-York persons with-operator the state.</gloss>
+        <en>This is a school, small in volume compared to the typical school, pertaining to five-year-old girls (by American standards), in Brooklyn, teaching poetry to the New York community and operated by the state.</en>
       </interlinear-gloss>
     </example>
     <para>Here the three places of 
     <jbophrase>cmalu</jbophrase>, the three of 
     <jbophrase>nixli</jbophrase>, and the four of 
     <jbophrase>ckule</jbophrase> are fully specified. Since the places of 
     <jbophrase>ckule</jbophrase> are the places of the bridi as a whole, it was not necessary to link the sumti which follow 
     <jbophrase>ckule</jbophrase>. It would have been legal to do so, however:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-YIty">
       <title>
         <anchor xml:id="c5e7d4"/>
       </title>
       <interlinear-gloss>
         <jbo>mi klama be le zarci bei le zdani [be'o]</jbo>
-        <en>I go (to-the market from-the house).</en>
+        <gloss>I go (to-the market from-the house).</gloss>
       </interlinear-gloss>
     </example>
     <para>means the same as</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-UtBR">
       <title>
         <anchor xml:id="c5e7d5"/>
       </title>
       <interlinear-gloss>
         <jbo>mi klama le zarci le zdani</jbo>
-        <en>I go to-the market from-the house.</en>
+        <gloss>I go to-the market from-the house.</gloss>
       </interlinear-gloss>
     </example>
     <para> <indexterm type="general-imported"><primary>tanru</primary><secondary>place structures of</secondary></indexterm> No matter how complex a tanru gets, the last brivla always dictates the place structure: the place structure of</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-Twmx">
       <title>
         <anchor xml:id="c5e7d6"/>
       </title>
       <interlinear-gloss>
         <jbo>melbi je cmalu nixli bo ckule</jbo>
         <gloss>a (pretty and little) (girl school)</gloss>
@@ -1113,21 +1096,21 @@
     <jbophrase>fo</jbophrase>, and 
     <jbophrase>fu</jbophrase> (of selma'o FA, discussed further in 
     <xref linkend="chapter-sumti-tcita"/>), which serve to explicitly specify the x2, x3, x4, and x5 places respectively. Normally, the place following the 
     <jbophrase>be</jbophrase> is the x2 place and the other places follow in order. If it seems convenient to change the order, however, it can be accomplished as follows:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-mhS7">
       <title>
         <anchor xml:id="c5e7d7"/>
       </title>
       <interlinear-gloss>
         <jbo>ti xamgu be fi mi bei fe do [be'o] zdani</jbo>
-        <en>This is-a-good ( by-standard me for you ) house.</en>
+        <gloss>This is-a-good ( by-standard me for you ) house.</gloss>
       </interlinear-gloss>
     </example>
     <para>which is equivalent in meaning to 
     <xref linkend="example-random-id-Uuio"/>. Note that the order of 
     <jbophrase>be</jbophrase>, 
     <jbophrase>bei</jbophrase>, and 
     <jbophrase>be'o</jbophrase> does not change; only the inserted 
     <jbophrase>fi</jbophrase> tells us that 
     <jbophrase>mi</jbophrase> is the x3 place (and correspondingly, the inserted 
     <jbophrase>fe</jbophrase> tells us that 
@@ -1174,44 +1157,44 @@
     <para> <indexterm type="general-imported"><primary>be'o</primary><secondary>effect of relative clauses on elidability of</secondary></indexterm>  <indexterm type="general-imported"><primary>relative clauses</primary><secondary>effect on elidability of be'o</secondary></indexterm>  <indexterm type="general-imported"><primary>be'o</primary><secondary>elidability of</secondary></indexterm>  <indexterm type="general-imported"><primary>elidability of be'o</primary></indexterm> The terminator 
     <jbophrase>be'o</jbophrase> is almost always elidable: however, if the selbri belongs to a description, then a relative clause following it will attach to the last linked sumti unless 
     
     <jbophrase>be'o</jbophrase> is used, in which case it will attach to the outer description:</para>
     <example xml:id="example-random-id-qJTI" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c5e7d11"/>
       </title>
       <interlinear-gloss>
         <jbo>le xamgu be do noi barda cu zdani</jbo>
-        <en>The good-thing for you (who are-large) is-a-house.</en>
+        <gloss>The good-thing for you (who are-large) is-a-house.</gloss>
       </interlinear-gloss>
     </example>
     <example xml:id="example-random-id-qjTj" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c5e7d12"/>
       </title>
       <interlinear-gloss>
         <jbo>le xamgu be do be'o noi barda cu zdani</jbo>
-        <en>The (good-thing for you) (which is-large) is-a-house</en>
+        <gloss>The (good-thing for you) (which is-large) is-a-house</gloss>
       </interlinear-gloss>
     </example>
     <para>(Relative clauses are explained in 
     <xref linkend="chapter-relative-clauses"/>.)</para>
     <para> <indexterm type="general-imported"><primary>be'o</primary><secondary>effect of ku on elidability of</secondary></indexterm>  <indexterm type="general-imported"><primary>ku</primary><secondary>effect on elidability of be'o</secondary></indexterm> In other cases, however, 
     <jbophrase>be'o</jbophrase> cannot be elided if 
     <jbophrase>ku</jbophrase> has also been elided:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-zb4A">
       <title>
         <anchor xml:id="c5e7d13"/>
       </title>
       <interlinear-gloss>
         <jbo>le xamgu be le ctuca [ku] be'o zdani</jbo>
-        <en>the good (for the teacher) house</en>
+        <gloss>the good (for the teacher) house</gloss>
       </interlinear-gloss>
     </example>
     <para>requires either 
     <jbophrase>ku</jbophrase> or 
     <jbophrase>be'o</jbophrase>, and since there is only one occurrence of 
     <jbophrase>be</jbophrase>, the 
     <jbophrase>be'o</jbophrase> must match it, whereas it may be confusing which occurrence of 
     <jbophrase>le</jbophrase> the 
     <jbophrase>ku</jbophrase> terminates (in fact the second one is correct).</para>
   </section>
@@ -1361,45 +1344,45 @@
         <en>school for beautiful girls</en>
       </interlinear-gloss>
     </example>
     <para>means the same as:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-w5cI">
       <title>
         <anchor xml:id="c5e8d8"/>
       </title>
       <interlinear-gloss>
         <jbo>ke melbi nixli ke'e ckule</jbo>
-        <en>(pretty girl) school</en>
+        <gloss>(pretty girl) school</gloss>
       </interlinear-gloss>
     </example>
     <para> <indexterm type="general-imported"><primary>multiple tanru inversion</primary><secondary>effect on grouping</secondary></indexterm>  <indexterm type="general-imported"><primary>tanru inversion</primary><secondary>multiple</secondary></indexterm> Multiple 
     <jbophrase>co</jbophrase> cmavo can appear within a selbri, indicating multiple inversions: a right-grouping rule is employed, as for 
     
     <jbophrase>bo</jbophrase>. The above rule can be applied to interpret such selbri, but all 
     <jbophrase>co</jbophrase> cmavo must be removed simultaneously:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-yLn5">
       <title>
         <anchor xml:id="c5e8d9"/>
       </title>
       <interlinear-gloss>
         <jbo>ckule co nixli co cmalu</jbo>
-        <en>school of-type (girl of-type little)</en>
+        <gloss>school of-type (girl of-type little)</gloss>
       </interlinear-gloss>
     </example>
     <para>becomes formally</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-mM3Q">
       <title>
         <anchor xml:id="c5e8d10"/>
       </title>
       <interlinear-gloss>
         <jbo>ke ke cmalu ke'e nixli ke'e ckule</jbo>
-        <en>( (little) girl ) school</en>
+        <gloss>( (little) girl ) school</gloss>
       </interlinear-gloss>
     </example>
     <para>which by the left-grouping rule is simply</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-LGRz">
       <title>
         <anchor xml:id="c5e8d11"/>
       </title>
       <interlinear-gloss>
         <jbo>cmalu nixli ckule</jbo>
         <gloss>little girl school</gloss>
@@ -1480,21 +1463,21 @@
     <xref linkend="chapter-abstractions"/>, and 
     <xref linkend="chapter-mekso"/>; but for completeness these types are mentioned here with a brief explanation and an example of their use in selbri.</para>
     <para> <indexterm type="lojban-word-imported"><primary>GOhA selma'o</primary></indexterm>  <indexterm type="general-imported"><primary>tanru</primary><secondary>with GOhA</secondary></indexterm>  <indexterm type="general-imported"><primary>selbri</primary><secondary>with GOhA</secondary></indexterm>  <indexterm type="general-imported"><primary>GOhA selma'o</primary><secondary>as component in tanru</secondary></indexterm>  <indexterm type="general-imported"><primary>GOhA selma'o</primary><secondary>as selbri</secondary></indexterm> The cmavo of selma'o GOhA (with one exception) serve as pro-bridi, providing a reference to the content of other bridi; none of them has a fixed meaning. The most commonly used member of GOhA is probably 
     <jbophrase>go'i</jbophrase>, which amounts to a repetition of the previous bridi, or part of it. If I say:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-2UvG">
       <title>
         <anchor xml:id="c5e9d1"/>
       </title>
       <interlinear-gloss>
         <jbo>la djan. klama le zarci</jbo>
-        <en>John goes-to the market.</en>
+        <gloss>John goes-to the market.</gloss>
       </interlinear-gloss>
     </example>
     <para> <indexterm type="lojban-word-imported"><primary>go'i</primary></indexterm> you may retort:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-EvoD">
       <title>
         <anchor xml:id="c5e9d2"/>
       </title>
       <interlinear-gloss>
         <jbo>la djan. go'i troci</jbo>
         <gloss>John [repeat last] are-a-tryer</gloss>
@@ -1502,21 +1485,21 @@
       </interlinear-gloss>
     </example>
     <para>
     <xref linkend="example-random-id-EvoD"/> is short for:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-nKQ3">
       <title>
         <anchor xml:id="c5e9d3"/>
       </title>
       <interlinear-gloss>
         <jbo>la djan. klama be le zarci be'o troci</jbo>
-        <en>John is-a-goer (to the market) type-of trier.</en>
+        <gloss>John is-a-goer (to the market) type-of trier.</gloss>
       </interlinear-gloss>
     </example>
     <para>because the whole bridi of 
     <xref linkend="example-random-id-2UvG"/> has been packaged up into the single word 
     <jbophrase>go'i</jbophrase> and inserted into 
     <xref linkend="example-random-id-EvoD"/>.</para>
     <para> <indexterm type="general-imported"><primary>du</primary><secondary>as an exception within GOhA selma'o</secondary></indexterm> The exceptional member of GOhA is 
     <jbophrase>du</jbophrase>, which represents the relation of identity. Its place structure is:</para>
     <!-- FIXME: This definition is supposed to be set out from the rest of the text, but which Docbook tag to use? -->
     <para>x1 is identical with x2, x3, ...</para>
@@ -1529,21 +1512,21 @@
     <jbophrase>nu'a</jbophrase> (of selma'o NUhA). The resulting place structure is:</para>
     <!-- FIXME: This definition is supposed to be set out from the rest of the text, but which Docbook tag to use? -->
     <para>x1 is the result of applying (the operator) to arguments x2, x3, etc.</para>
     <para>for as many arguments as are required. (The result goes in the x1 place because the number of following places may be indefinite.) For example:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-pp6j">
       <title>
         <anchor xml:id="c5e9d4"/>
       </title>
       <interlinear-gloss>
         <jbo>li vo nu'a su'i li re li re</jbo>
-        <en>The-number 4 is-the-sum-of the-number 2 and-the-number 2.</en>
+        <gloss>The-number 4 is-the-sum-of the-number 2 and-the-number 2.</gloss>
       </interlinear-gloss>
     </example>
     <para>A possible tanru example might be:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-K7yz">
       <title>
         <indexterm type="example-imported"><primary>addition problems</primary><secondary>example</secondary></indexterm>
         <anchor xml:id="c5e9d5"/>
       </title>
       <interlinear-gloss>
         <jbo>mi jimpe tu'a loi nu'a su'i nabmi</jbo>
@@ -1594,21 +1577,21 @@
       </interlinear-gloss>
     </example>
     <para> <indexterm type="general-imported"><primary>abstraction bridi</primary><secondary>contrasted with component non-abstraction bridi in meaning</secondary></indexterm> 
     <xref linkend="example-random-id-5szz"/> is quite distinct in meaning from:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-yNSI">
       <title>
         <anchor xml:id="c5e9d9"/>
       </title>
       <interlinear-gloss>
         <jbo>ti zdile kumfa</jbo>
-        <en>This is-an-amuser room.</en>
+        <gloss>This is-an-amuser room.</gloss>
       </interlinear-gloss>
     </example>
     <para>which suggests the meaning 
     <quote>a room that amuses someone</quote>.</para>
   </section>
 
   <section xml:id="section-me-selbri">
     <title>selbri based on sumti: <jbophrase>me</jbophrase></title>
     <para>The following cmavo are discussed in this section:</para>
     <cmavo-list>
@@ -1675,22 +1658,21 @@
     </example>
     <para> <indexterm type="general-imported"><primary>du</primary><secondary>compared with me in effect</secondary></indexterm>  <indexterm type="general-imported"><primary>me</primary><secondary>compared with du in effect</secondary></indexterm>  <indexterm type="general-imported"><primary>me/du equivalence</primary></indexterm> If the sumti refers to a single object, then the effect of 
     <jbophrase>me</jbophrase> is much like that of 
     <jbophrase>du</jbophrase>:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-HMHc">
       <title>
         <anchor xml:id="c5e10d5"/>
       </title>
       <interlinear-gloss>
         <jbo>do du la djan.</jbo>
-        <gloss>You are-identical-with the-one-called 
-        <quote>John</quote>.</gloss>
+        <gloss>You are-identical-with the-one-called <quote>John</quote>.</gloss>
         <en>You are John.</en>
       </interlinear-gloss>
     </example>
     <para>means the same as</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-GMCc">
       <title>
         <anchor xml:id="c5e10d6"/>
       </title>
       <interlinear-gloss>
         <jbo>do me la djan.</jbo>
@@ -1829,60 +1811,60 @@
     </example>
     <para>To convert this sentence so that 
     <jbophrase>le zarci</jbophrase> is in the x1 place, one correct way is:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-4mbn">
       <title>
         <anchor xml:id="c5e11d4"/>
       </title>
       <interlinear-gloss>
         <jbo>le zarci cu se ke cadzu klama [ke'e] la .alis.</jbo>
         <gloss>The market is-a-[swap x1/x2] (walker type-of goer) Alice.</gloss>
-        <en>The market is-walkingly gone-to by-Alice.</en>
+        <gloss>The market is-walkingly gone-to by-Alice.</gloss>
       </interlinear-gloss>
     </example>
     <para> <indexterm type="general-imported"><primary>ke</primary><secondary>for conversion of tanru</secondary></indexterm>  <indexterm type="general-imported"><primary>conversion with `ke'</primary></indexterm> The 
     <jbophrase>ke ... ke'e</jbophrase> brackets cause the entire tanru to be converted by the 
     <jbophrase>se</jbophrase>, which would otherwise convert only 
     <jbophrase>cadzu</jbophrase>, leading to:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-UNt0">
       <title>
         <anchor xml:id="c5e11d5"/>
       </title>
       <interlinear-gloss>
         <jbo>le zarci cu se cadzu klama la .alis.</jbo>
         <gloss>The market (is-a-[swap x1/x2] walker) type-of goer to Alice.</gloss>
-        <en>The market is-a-walking-surface type-of goer to Alice.</en>
+        <gloss>The market is-a-walking-surface type-of goer to Alice.</gloss>
       </interlinear-gloss>
     </example>
     <para>whatever that might mean. An alternative approach, since the place structure of 
     <jbophrase>cadzu klama</jbophrase> is that of 
     <jbophrase>klama</jbophrase> alone, is to convert only the latter:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-U0fo">
       <title>
         <anchor xml:id="c5e11d6"/>
       </title>
       <interlinear-gloss>
         <jbo>le zarci cu cadzu se klama la .alis.</jbo>
-        <en>The market walkingly is-gone-to by-Alice.</en>
+        <gloss>The market walkingly is-gone-to by-Alice.</gloss>
       </interlinear-gloss>
     </example>
     <para>But the tanru in 
     <xref linkend="example-random-id-U0fo"/> may or may not have the same meaning as that in 
     <xref linkend="example-random-id-mPX8"/>; in particular, because 
     <jbophrase>cadzu</jbophrase> is not converted, there is a suggestion that although Alice is the goer, the market is the walker. With a different sumti as x1, this seemingly odd interpretation might make considerable sense:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-XEnd">
       <title>
         <anchor xml:id="c5e11d7"/>
       </title>
       <interlinear-gloss>
         <jbo>la djan. cu cadzu se klama la .alis</jbo>
-        <en>John walkingly is-gone-to by Alice</en>
+        <gloss>John walkingly is-gone-to by Alice</gloss>
       </interlinear-gloss>
     </example>
     <para>suggests that Alice is going to John, who is a moving target.</para>
     <para> <indexterm type="general-imported"><primary>tense conversion</primary><secondary>with jai</secondary></indexterm>  <indexterm type="general-imported"><primary>jai</primary><secondary>for modal conversion</secondary></indexterm> There is an alternative type of conversion, using the cmavo 
     <jbophrase>jai</jbophrase> of selma'o JAI optionally followed by a modal or tense construction. Grammatically, such a combination behaves exactly like conversion using SE. More details can be found in 
     <xref linkend="chapter-sumti-tcita"/>.</para>
   </section>
 
   <section xml:id="section-scalar-negation">
     <title>Scalar negation of selbri</title>
@@ -2037,22 +2019,21 @@
     <para>And if both 
     <jbophrase>ke'e</jbophrase> and 
     <jbophrase>be'o</jbophrase> are omitted, the results are even sillier:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-0WLq">
       <title>
         <anchor xml:id="c5e12d11"/>
       </title>
       <interlinear-gloss>
         <jbo>mi na'e ke sutra cadzu be fi le birka je masno klama [be'o] [ke'e] le zarci</jbo>
         <gloss>I non-(quickly walk on my (arm-type and slow) goers) on the market.</gloss>
-        <gloss>I do something other than quickly walking using the goers, both arm-type</gloss>
-        <en>and slow, relative-to the market.</en>
+        <en>I do something other than quickly walking using the goers, both arm-type and slow, relative-to the market.</en>
       </interlinear-gloss>
     </example>
     <para>In 
     <xref linkend="example-random-id-0WLq"/>, everything after 
     <jbophrase>be</jbophrase> is a linked sumti, so the place structure is that of 
     
     <jbophrase>cadzu</jbophrase>, whose x2 place is the surface walked upon. It is less than clear what an 
     <quote>arm-type goer</quote> might be. Furthermore, since the x3 place has been occupied by the linked sumti, the 
     
     <jbophrase>le zarci</jbophrase> following the selbri falls into the nonexistent x4 place of 
@@ -2129,22 +2110,21 @@
     
     
     <xref linkend="chapter-tenses"/>.</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-hw6g">
       <title>
         <anchor xml:id="c5e13d5"/>
       </title>
       <interlinear-gloss>
         <jbo>mi na pu na ca klama le zarci</jbo>
         <gloss>I [not] [past] [not] [present] go to-the market</gloss>
-        <gloss>It is not the case that in the past it was not the case that in the present I</gloss>
-        <gloss>went to the market.</gloss>
+        <gloss>It is not the case that in the past it was not the case that in the present I went to the market.</gloss>
         <gloss>I didn't not go to the market.</gloss>
         <en>I went to the market.</en>
       </interlinear-gloss>
     </example>
     <para> <indexterm type="general-imported"><primary>negation cmavo</primary><secondary>position relative to selbri</secondary></indexterm>  <indexterm type="general-imported"><primary>modal cmavo</primary><secondary>position relative to selbri</secondary></indexterm>  <indexterm type="general-imported"><primary>tense cmavo</primary><secondary>position relative to selbri</secondary></indexterm> Tense, modal, and negation cmavo can appear only at the beginning of the selbri. They cannot be embedded within it.</para>
     
   </section>
 
   <section xml:id="section-asymmetric-tanru">
     <title>Some types of asymmetrical tanru</title>
@@ -3736,27 +3716,30 @@
   <section xml:id="section-pretty-school-groupings">
     <title>
     <quote>Pretty little girls' school</quote>: forty ways to say it</title>
     <para> <indexterm type="general-imported"><primary>pretty little girls' school</primary><secondary>forty ways</secondary></indexterm> The following examples show every possible grouping arrangement of 
     <jbophrase>melbi cmalu nixli ckule</jbophrase> using 
     <jbophrase>bo</jbophrase> or 
     <jbophrase>ke ... ke'e</jbophrase> for grouping and 
     <jbophrase>je</jbophrase> or 
     <jbophrase glossary="false">jebo</jbophrase> for logical connection. Most of these are definitely not plausible interpretations of the English phrase 
     <quote>pretty little girls' school</quote>, especially those which describe something which is both a girl and a school.</para>
-    
-    <para>Examples 4.2, 4.3, 4.4, 4.5, and 5.6 are repeated here as Examples 16.1, 16.9, 16.17, 16.25, and 16.33 respectively. The seven examples following each of these share the same grouping pattern, but differ in the presence or absence of 
+    <para>Examples <xref linkend="example-random-id-qjmr"/>, <xref linkend="example-random-id-qjNi"/>, <xref linkend="example-random-id-qjog"/>, <xref linkend="example-random-id-qjop"/>, and <xref linkend="example-random-id-tz0L"/> are repeated here as Examples <xref linkend="example-random-id-qjzw"/>, <xref linkend="example-random-id-qKaM"/>, <xref linkend="example-random-id-qKfX"/>, <xref linkend="example-random-id-qKmg"/>, and <xref linkend="example-random-id-qKPQ"/> respectively.
+        <!-- was: Examples 4.2, 4.3, 4.4, 4.5, and 5.6 are repeated here as Examples 16.1, 16.9, 16.17, 16.25, and 16.33 respectively. -->
+        The seven examples following each of these share the same grouping pattern, but differ in the presence or absence of 
     <jbophrase>je</jbophrase> at each possible site. Some of the examples have more than one Lojban version. In that case, they differ only in grouping mechanism, and are always equivalent in meaning.</para>
     <para>The logical connective 
     <jbophrase>je</jbophrase> is associative: that is, 
     <quote>A and (B and C)</quote> is the same as 
-    <quote>(A and B) and C</quote>. Therefore, some of the examples have the same meaning as others. In particular, 16.8, 16.16, 16.24, 16.32, and 16.40 all have the same meaning because all four brivla are logically connected and the grouping is simply irrelevant. Other equivalent forms are noted in the examples themselves. However, if 
+    <quote>(A and B) and C</quote>. Therefore, some of the examples have the same meaning as others. In particular, <xref linkend="example-random-id-qKAG"/>, <xref linkend="example-random-id-qKFA"/>, <xref linkend="example-random-id-qKLN"/>, <xref linkend="example-random-id-qKpo"/>, and <xref linkend="example-random-id-qKU6"/> all have the same meaning because all four brivla are logically connected and the grouping is simply irrelevant.
+    <!-- was: In particular, 16.8, 16.16, 16.24, 16.32, and 16.40 all have the same meaning -->
+    Other equivalent forms are noted in the examples themselves. However, if 
     
     <jbophrase>je</jbophrase> were replaced by 
     <jbophrase>naja</jbophrase> or 
     <jbophrase>jo</jbophrase> or most of the other logical connectives, the meanings would become distinct.</para>
     <para>It must be emphasized that, because of the ambiguity of all tanru, the English translations are by no means definitive - they represent only one possible interpretation of the corresponding Lojban sentence.</para>
     <example xml:id="example-random-id-qjzw" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c5e16d1"/>
       </title>
       <interlinear-gloss>
@@ -3887,35 +3870,35 @@
         <en>a pretty and little type of thing which is both a girl and a school</en>
       </interlinear-gloss>
     </example>
     <example xml:id="example-random-id-qKdY" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c5e16d14"/>
       </title>
       <interlinear-gloss>
         <jbo>melbi bo cmalu je nixli jebo ckule</jbo>
         <gloss>(pretty type-of little) and (girl and school)</gloss>
-        <gloss>thing which is beautifully small, a school, and a girl</gloss>
-        <en>Note: same as 16.6</en>
+        <en>thing which is beautifully small, a school, and a girl</en>
       </interlinear-gloss>
     </example>
+    <para>Note: same as 16.6</para>
     <example xml:id="example-random-id-qKEI" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c5e16d15"/>
       </title>
       <interlinear-gloss>
         <jbo>melbi jebo cmalu je nixli bo ckule</jbo>
         <gloss>(pretty and little) and (girl type-of school)</gloss>
-        <gloss>thing which is beautiful and small and a girl's school</gloss>
-        <en>Note: same as 16.30</en>
+        <en>thing which is beautiful and small and a girl's school</en>
       </interlinear-gloss>
     </example>
+    <para>Note: same as 16.30</para>
     <example xml:id="example-random-id-qKFA" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c5e16d16"/>
       </title>
       <interlinear-gloss>
         <jbo>melbi jebo cmalu je nixli jebo ckule</jbo>
         <gloss>(pretty and little) and (girl and school)</gloss>
         <en>thing which is beautiful, small, a girl, and a school</en>
       </interlinear-gloss>
     </example>
@@ -3948,47 +3931,47 @@
         <gloss>(pretty and (little type-of girl)) type-of school</gloss>
         <en>school for things which are beautiful and are small girls</en>
       </interlinear-gloss>
     </example>
     <example xml:id="example-random-id-qKjJ" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c5e16d20"/>
       </title>
       <interlinear-gloss>
         <jbo>ke melbi cmalu bo nixli ke'e je ckule</jbo>
-        <gloss>melbi bo cmalu bo nixli je ckule</gloss>
+        <jbo>melbi bo cmalu bo nixli je ckule</jbo>
         <gloss>(pretty type-of (little type-of girl)) and school</gloss>
         <en>thing which is a school and a small girl who is beautiful</en>
       </interlinear-gloss>
     </example>
     <example xml:id="example-random-id-qKjr" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c5e16d21"/>
       </title>
       <interlinear-gloss>
         <jbo>melbi je cmalu jebo nixli ckule</jbo>
         <gloss>(pretty and (little and girl)) type-of school</gloss>
-        <gloss>school for things which are beautiful, small, and girls</gloss>
-        <en>Note: same as 16.5</en>
+        <en>school for things which are beautiful, small, and girls</en>
       </interlinear-gloss>
     </example>
+    <para>Note: same as 16.5</para>
     <example xml:id="example-random-id-qKKM" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c5e16d22"/>
       </title>
       <interlinear-gloss>
         <jbo>melbi je cmalu bo nixli je ckule</jbo>
         <gloss>(pretty and (little type-of girl)) and school</gloss>
-        <gloss>thing which is beautiful, a small girl, and a school</gloss>
-        <en>Note: same as 16.38</en>
+        <en>thing which is beautiful, a small girl, and a school</en>
       </interlinear-gloss>
     </example>
+    <para>Note: same as 16.38</para>
     <example xml:id="example-random-id-qKLi" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c5e16d23"/>
       </title>
       <interlinear-gloss>
         <jbo>ke melbi cmalu je nixli ke'e je ckule</jbo>
         <gloss>(pretty type-of (little and girl)) and school</gloss>
         <en>thing which is beautifully small, a beautiful girl, and a school</en>
       </interlinear-gloss>
     </example>
@@ -4001,21 +3984,21 @@
         <gloss>(pretty and (little and girl)) and school</gloss>
         <en>thing which is beautiful, small, a girl, and a school</en>
       </interlinear-gloss>
     </example>
     <example xml:id="example-random-id-qKmg" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c5e16d25"/>
       </title>
       <interlinear-gloss>
         <jbo>melbi cmalu bo nixli bo ckule</jbo>
-        <gloss>melbi ke cmalu ke nixli ckule [ke'e] [ke'e]</gloss>
+        <jbo>melbi ke cmalu ke nixli ckule [ke'e] [ke'e]</jbo>
         <gloss>pretty type-of (little type-of (girl type-of school))</gloss>
         <en>small school for girls which is beautiful</en>
       </interlinear-gloss>
     </example>
     <example xml:id="example-random-id-qKn8" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c5e16d26"/>
       </title>
       <interlinear-gloss>
         <jbo>melbi ke cmalu nixli je ckule [ke'e]</jbo>
@@ -4032,50 +4015,50 @@
         <gloss>pretty type-of (little and (girl type-of school))</gloss>
         <en>thing which is beautifully small and a girls' school that is beautiful</en>
       </interlinear-gloss>
     </example>
     <example xml:id="example-random-id-qKp6" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c5e16d28"/>
       </title>
       <interlinear-gloss>
         <jbo>melbi je cmalu bo nixli bo ckule</jbo>
-        <gloss>melbi je ke cmalu nixli bo ckule [ke'e]</gloss>
-        <gloss>melbi je ke cmalu ke nixli ckule [ke'e] [ke'e]</gloss>
+        <jbo>melbi je ke cmalu nixli bo ckule [ke'e]</jbo>
+        <jbo>melbi je ke cmalu ke nixli ckule [ke'e] [ke'e]</jbo>
         <gloss>pretty and (little type-of (girl type-of school))</gloss>
         <en>thing which is beautiful and a small type of girls' school</en>
       </interlinear-gloss>
     </example>
     <example xml:id="example-random-id-qKp9" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c5e16d29"/>
       </title>
       <interlinear-gloss>
         <jbo>melbi cmalu je nixli jebo ckule</jbo>
         <gloss>melbi cmalu je ke nixli je ckule [ke'e]</gloss>
         <gloss>pretty type-of (little and (girl and school))</gloss>
-        <gloss>thing which is beautifully small, a beautiful girl, and a beautiful school</gloss>
-        <en>Note: same as 16.37</en>
+        <en>thing which is beautifully small, a beautiful girl, and a beautiful school</en>
       </interlinear-gloss>
     </example>
+    <para>Note: same as 16.37</para>
     <example xml:id="example-random-id-qKpm" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c5e16d30"/>
       </title>
       <interlinear-gloss>
         <jbo>melbi je cmalu jebo nixli bo ckule</jbo>
-        <gloss>melbi je ke cmalu je nixli bo ckule [ke'e]</gloss>
+        <jbo>melbi je ke cmalu je nixli bo ckule [ke'e]</jbo>
         <gloss>pretty and (little and (girl type-of school))</gloss>
-        <gloss>thing which is beautiful, small and a girls' school</gloss>
-        <en>Note: same as 16.15</en>
+        <en>thing which is beautiful, small and a girls' school</en>
       </interlinear-gloss>
     </example>
+    <para>Note: same as 16.15</para>
     <example xml:id="example-random-id-qKPn" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c5e16d31"/>
       </title>
       <interlinear-gloss>
         <jbo>melbi je ke cmalu nixli je ckule [ke'e]</jbo>
         <gloss>pretty and (little type-of (girl and school))</gloss>
         <en>beautiful thing which is a small girl and a small school</en>
       </interlinear-gloss>
     </example>
@@ -4129,35 +4112,35 @@
         <en>thing which is beautiful and a school for small girls</en>
       </interlinear-gloss>
     </example>
     <example xml:id="example-random-id-qKR5" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c5e16d37"/>
       </title>
       <interlinear-gloss>
         <jbo>melbi cmalu je nixli je ckule</jbo>
         <gloss>pretty type-of ((little and girl) and school)</gloss>
-        <gloss>thing which is beautifully small, a beautiful girl, and a beautiful school</gloss>
-        <en>Note: same as 16.29</en>
+        <en>thing which is beautifully small, a beautiful girl, and a beautiful school</en>
       </interlinear-gloss>
     </example>
+    <para>Note: same as 16.29</para>
     <example xml:id="example-random-id-qKsA" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c5e16d38"/>
       </title>
       <interlinear-gloss>
         <jbo>melbi je ke cmalu bo nixli je ckule [ke'e]</jbo>
         <gloss>pretty and ((little type-of girl) and school)</gloss>
-        <gloss>thing which is beautiful, a small girl and a school</gloss>
-        <en>Note: same as 16.22</en>
+        <en>thing which is beautiful, a small girl and a school</en>
       </interlinear-gloss>
     </example>
+    <para>Note: same as 16.22</para>
     <example xml:id="example-random-id-qKSK" role="interlinear-gloss-example">
       <title>
         <anchor xml:id="c5e16d39"/>
       </title>
       <interlinear-gloss>
         <jbo>melbi je ke cmalu je nixli ckule [ke'e]</jbo>
         <gloss>pretty and ((little and girl) type-of school)</gloss>
         <en>thing which is beautiful and is a small school and a girls' school</en>
       </interlinear-gloss>
     </example>

-- 
You received this message because you are subscribed to the Google Groups "BPFK" group.
To post to this group, send email to bpfk-list@googlegroups.com.
To unsubscribe from this group, send email to bpfk-list+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/bpfk-list?hl=en.
Prev by Date: [bpfk] [dag/cll] 712517: Merge commit '81c3b6e12f8b6ebb43e1c1314e6224716979...
Next by Date: [bpfk] [dag/cll] 714302: Merge commit 'e65387de7dbe64d1aa64fbc461b99cf456fd...
Previous by thread: [bpfk] [dag/cll] 712517: Merge commit '81c3b6e12f8b6ebb43e1c1314e6224716979...
Next by thread: [bpfk] [dag/cll] 714302: Merge commit 'e65387de7dbe64d1aa64fbc461b99cf456fd...
Index(es):
- Date
- Thread