[bpfk] dag-cll git updates for Thu Dec 16 15:21:02 EST 2010

[www-data <www-data@oh-www1.lojban.org>]

commit 3afe0e4432e77073d8033a248d36435e5cc2a75e
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date:   Thu Dec 16 11:40:46 2010 -0800

    CHanging chapter 5 tag.

diff --git a/todocbook/1.xml b/todocbook/1.xml
index 4d49335..1aaec9a 100644
--- a/todocbook/1.xml
+++ b/todocbook/1.xml
@@ -134,21 +134,21 @@
     <xref linkend="cll_chapter4" />were originally written by Bob LeChevalier with contributions by Chuck Barton; 
     <xref linkend="cll_chapter12" />was originally written (in much longer form) by Nick Nicholas; the dialogue near the end of 
     <xref linkend="cll_chapter13" />was contributed by Nora Tansky LeChevalier; 
     <xref linkend="cll_chapter15" />and parts of 
     <xref linkend="cll_chapter16" />were originally by Bob LeChevalier; and the YACC grammar in 
 <!-- ^^   YACC grammar, 511 -->
 <indexterm><primary>YACC grammar</primary></indexterm>
     <xref linkend="cll_chapter21" />is the work of several hands, but is primarily by Bob LeChevalier and Jeff Taylor. The BNF grammar, which is also in 
     <xref linkend="cll_chapter21" />, was originally written by me, then rewritten by Clark Nelson, and finally touched up by me again.</para>
     <para>The research into natural languages from which parts of 
-    <xref linkend="cll_chapter5" />draw their material was performed by Ivan Derzhanski. LLG acknowledges his kind permission to use the fruits of his research.</para>
+    <xref linkend="selbri" />draw their material was performed by Ivan Derzhanski. LLG acknowledges his kind permission to use the fruits of his research.</para>
 <!-- ^^   LLG, 5 -->
 <indexterm><primary>LLG</primary></indexterm>
     <para>The pictures in this book were drawn by Nora Tansky LeChevalier, except for the picture appearing in 
 <!-- ^^   pictures: captions to, 7; credits for, 6 -->
 <indexterm><primary>pictures</primary></indexterm>
     <xref linkend="cll_chapter4" />, which is by Sylvia Rutiser Rissell.</para>
     <para>The index was made by Nora Tansky LeChevalier.</para>
     <para>I would like to thank the following people for their detailed reviews, suggestions, comments, and early detection of my embarrassing errors in Lojban, logic, English, and cross-references: Nick Nicholas, Mark Shoulson, Veijo Vilva, Colin Fine, And Rosta, Jorge Llambias, Iain Alexander, Paulo S. L. M. Barreto, Robert J. Chassell, Gale Cowan, Karen Stein, Ivan Derzhanski, Jim Carter, Irene Gates, Bob LeChevalier, John Parks-Clifford (also known as 
     <quote>pc</quote>), and Nora Tansky LeChevalier.</para>
     <para>Nick Nicholas (NSN) would like to thank the following Lojbanists: Mark Shoulson, Veijo Vilva, Colin Fine, And Rosta, and Iain Alexander for their suggestions and comments; John Cowan, for his extensive comments, his exemplary trailblazing of Lojban grammar, and for solving the 
diff --git a/todocbook/12.xml b/todocbook/12.xml
index 9935cf3..cf6a373 100644
--- a/todocbook/12.xml
+++ b/todocbook/12.xml
@@ -43,21 +43,21 @@
       </interlinear-gloss>
     </example>
     <para>Although the lujvo 
     <quote>fagyfesti</quote>is derived from the tanru 
     <quote>fagri festi</quote>, it is not equivalent in meaning to it. In particular, 
     <quote>fagyfesti</quote>has a distinct place structure of its own, not the same as that of 
     <quote>festi</quote>. (In contrast, the tanru does have the same place structure as 
     <quote>festi</quote>.) The lujvo needs to take account of the places of 
     <quote>fagri</quote>as well. When a tanru is made into a lujvo, there is no equivalent of 
     <quote>be ... bei ... be'o</quote>(described in 
-    <xref linkend="cll_chapter5" />) to incorporate sumti into the middle of the lujvo.</para>
+    <xref linkend="selbri" />) to incorporate sumti into the middle of the lujvo.</para>
     <para>So why have lujvo? Primarily to reduce semantic ambiguity. On hearing a tanru, there is a burden on the listener to figure out what the tanru might mean. Adding further terms to the tanru reduces ambiguity in one sense, by providing more information; but it increases ambiguity in another sense, because there are more and more tanru joints, each with an ambiguous significance. Since lujvo, like other brivla, have a fixed place structure and a single meaning, encapsulating a commonly-used tanru into a lujvo relieves the listener of the burden of creative understanding. In addition, lujvo are typically shorter than the corresponding tanru.</para>
 <!-- ^^   creative understanding, 273 -->
 <indexterm><primary>creative understanding</primary></indexterm>
     <para>There are no absolute laws fixing the place structure of a newly created lujvo. The maker must consider the place structures of all the components of the tanru and then decide which are still relevant and which can be removed. What is said in this chapter represents guidelines, presented as one possible standard, not necessarily complete, and not the only possible standard. There may well be lujvo that are built without regard for these guidelines, or in accordance with entirely different guidelines, should such alternative guidelines someday be developed. The reason for presenting any guidelines at all is so that Lojbanists have a starting point for deciding on a likely place structure - one that others seeing the same word can also arrive at by similar consideration.</para>
 <!-- ^^   alternative guidelines, 273 -->
 <indexterm><primary>alternative guidelines</primary></indexterm>
 <!-- ^^   absolute laws, 273 -->
 <indexterm><primary>absolute laws</primary></indexterm>
     <para>If the tanru includes connective cmavo such as 
     <quote>bo</quote>, 
@@ -70,21 +70,21 @@
     <xref linkend="cll_chapter4" />.</para>
   </section>
   <section xml:id="cll_chapter12-section2">
     <title>The meaning of tanru: a necessary detour</title>
 <!-- ^^   necessary detour, 274 -->
 <indexterm><primary>necessary detour</primary></indexterm>
     <para>The meaning of a lujvo is controlled by - but is not the same as - the meaning of the tanru from which the lujvo was constructed. The tanru corresponding to a lujvo is called its 
     <quote>veljvo</quote>in Lojban, and since there is no concise English equivalent, that term will be used in this chapter. Furthermore, the left (modifier) part of a tanru will be called the 
     <quote>seltau</quote>, and the right (modified) part the 
     <quote>tertau</quote>, following the usage of 
-    <xref linkend="cll_chapter5" />. For brevity, we will speak of the seltau or tertau of a lujvo, meaning of course the seltau or tertau of the veljvo of that lujvo. (If this terminology is confusing, substituting 
+    <xref linkend="selbri" />. For brevity, we will speak of the seltau or tertau of a lujvo, meaning of course the seltau or tertau of the veljvo of that lujvo. (If this terminology is confusing, substituting 
     <quote>modifier</quote>for 
     <quote>seltau</quote>and 
     <quote>modified</quote>for 
     <quote>tertau</quote>may help.)</para>
     <para>The place structure of a tanru is always the same as the place structure of its tertau. As a result, the meaning of the tanru is a modified version of the meaning of the tertau; the tanru will typically, but not always, refer to a subset of the things referred to by the tertau.</para>
     <para>The purpose of a tanru is to join concepts together without necessarily focusing on the exact meaning of the seltau. For example, in the 
     <citation>Iliad</citation>, the poet talks about 
     <quote>the wine-dark sea</quote>, in which 
 <!-- ^^   wine-dark sea, 274 -->
 <indexterm><primary>wine-dark sea</primary></indexterm>
@@ -367,21 +367,21 @@
     <para>Why so? Because not only is the j1 place (the one who pays attention) equivalent to the t1 place (the hearer), but the j2 place (the thing paid attention to) is equivalent to the t2 place (the thing heard).</para>
     <para>A substantial minority of lujvo have the property that the first place of the seltau ( 
     <quote>gerku</quote>in this case) is equivalent to a place other than the first place of the tertau; such lujvo are said to be 
     <quote>asymmetrical</quote>. (There is a deliberate parallel here with the terms 
     <quote>asymmetrical tanru</quote>and 
 <!-- ^^   asymmetrical tanru, 104; definition, 104 -->
 <indexterm><primary>asymmetrical tanru</primary></indexterm>
     <quote>symmetrical tanru</quote>used in 
 <!-- ^^   symmetrical tanru, 111 -->
 <indexterm><primary>symmetrical tanru</primary></indexterm>
-    <xref linkend="cll_chapter5" />.)</para>
+    <xref linkend="selbri" />.)</para>
     <para>In principle any asymmetrical lujvo could be expressed as a symmetrical lujvo. Consider 
     <quote>gerzda</quote>, discussed in 
     <xref linkend="cll_chapter12-section3" />, where we learned that the g1 place was equivalent to the z2 place. In order to get the places aligned, we could convert 
     <quote>zdani</quote>to 
     <quote>se zdani</quote>(or 
     <quote>selzda</quote>when expressed as a lujvo). The place structure of 
     <quote>selzda</quote>is</para>
     <example role="interlinear-gloss-example" xml:id="random-id-IXoj">
       <title>
         <anchor xml:id="c12e5d5" />
@@ -1666,21 +1666,21 @@
     <quote>jdaselsku</quote>, not resolvable by using 
     <quote>seljdasku</quote>. No veljvo involving just the two gismu 
     <quote>lijda</quote>and 
     <quote>cusku</quote>can fully express the relationship implicit in prayer. A prayer is not just anything said by the adherents of a religion; nor is it even anything said by them acting as adherents of that religion. Rather, it is what they say under the authority of that religion, or using the religion as a medium, or following the rules associated with the religion, or something of the kind. So the veljvo is somewhat elliptical.</para>
     <para>As a result, both 
     <quote>seljdasku</quote>and 
     <quote>jdaselsku</quote>belong to the second class of anomalous lujvo: the veljvo doesn't really supply all that the lujvo requires.</para>
     <para>Another example of this kind of anomalous lujvo, drawn from the tanru lists in 
 <!-- ^^   lists: use of tu'e/tu'u in, 358 -->
 <indexterm><primary>lists</primary></indexterm>
-    <xref linkend="cll_chapter5" />, is 
+    <xref linkend="selbri" />, is 
     <quote>lange'u</quote>, meaning 
     <quote>sheepdog</quote>. Clearly a sheepdog is not a dog which is a sheep (the symmetrical interpretation is wrong), nor a dog of the sheep breed (the asymmetrical interpretation is wrong). Indeed, there is simply no overlap in the places of 
 <!-- ^^   sheepdog, 290; example, 290 -->
 <indexterm><primary>sheepdog</primary></indexterm>
 <!-- ^^   sheep breed, 290 -->
 <indexterm><primary>sheep breed</primary></indexterm>
     <quote>lanme</quote>and 
     <quote>gerku</quote>at all. Rather, the lujvo refers to a dog which controls sheep flocks, a 
     <quote>terlanme jitro gerku</quote>, the lujvo from which is 
     <quote>terlantroge'u</quote>with place structure:</para>
diff --git a/todocbook/14.xml b/todocbook/14.xml
index f476149..4dba34d 100644
--- a/todocbook/14.xml
+++ b/todocbook/14.xml
@@ -403,21 +403,21 @@
       <interlinear-gloss>
         <jbo>la djan. nanmu .inaja la djeimyz. ninmu</jbo>
         <gloss>John is-not-a-man or James is-a-woman.</gloss>
         <gloss>John is a man only if James is a woman.</gloss>
         <en>If John is a man, then James is a woman.</en>
       </interlinear-gloss>
     </example>
     <para>The following example illustrates the use of 
     <quote>se</quote>to, in effect, exchange the two sentences. The normal use of 
     <quote>se</quote>is to (in effect) transpose places of a bridi, as explained in 
-    <xref linkend="cll_chapter5" />.</para>
+    <xref linkend="selbri" />.</para>
     <example role="interlinear-gloss-example" xml:id="random-id-z43X">
       <title>
         <anchor xml:id="c14e4d11" />
         <anchor xml:id="cll_chapter14-section4-example11" />
       </title>
       <interlinear-gloss>
         <jbo>la djan. nanmu .iseju la djeimyz. ninmu</jbo>
         <en>Whether or not John is a man, James is a woman.</en>
       </interlinear-gloss>
     </example>
diff --git a/todocbook/15.xml b/todocbook/15.xml
index 931bbbe..7567917 100644
--- a/todocbook/15.xml
+++ b/todocbook/15.xml
@@ -666,21 +666,21 @@
         <en>I (other-than-walkingly)-go-to the market.</en>
         <jbo>mi cadzu na'e klama le zarci</jbo>
         <en>I walkingly-(other-than-go-to) the market.</en>
       </interlinear-gloss>
     </example>
     <para>These negations show the default scope of 
     <quote>na'e</quote>is close-binding on an individual brivla in a tanru. 
 <!-- ^^   close-binding, 490 -->
 <indexterm><primary>close-binding</primary></indexterm>
     <xref linkend="cll_chapter15-section4-example5" />says that I am going to the market, but in some kind of a non-walking manner. (As with most tanru, there are a few other possible interpretations, but we'll assume this one - see 
-    <xref linkend="cll_chapter5" />for a discussion of tanru meaning).</para>
+    <xref linkend="selbri" />for a discussion of tanru meaning).</para>
     <para>In neither 
     <xref linkend="cll_chapter15-section4-example5" />nor 
     <xref linkend="cll_chapter15-section4-example6" />does the 
     <quote>na'e</quote>negate the entire selbri. While both sentences contain negations that deny a particular relationship between the sumti, they also have a component which makes a positive claim about such a relationship. This is clearer in 
     <xref linkend="cll_chapter15-section4-example5" />, which says that I am going, but in a non-walking manner. In 
     <xref linkend="cll_chapter15-section4-example6" />, we have claimed that the relationship between me and the market in some way involves walking, but is not one of 
     <quote>going to</quote>(perhaps we are walking around the market, or walking-in-place while at the market).</para>
     <para>The 
     <quote>scale</quote>, or actually the 
     <quote>set</quote>, implied in Lojban tanru negations is anything which plausibly can be substituted into the tanru. (Plausibility here is interpreted in the same way that answers to a 
diff --git a/todocbook/16.xml b/todocbook/16.xml
index d22bcad..4de7c00 100644
--- a/todocbook/16.xml
+++ b/todocbook/16.xml
@@ -549,21 +549,21 @@
         <anchor xml:id="c16e5d6" />
         <anchor xml:id="cll_chapter16-section5-example6" />
       </title>
       <interlinear-gloss>
         <jbo>ro da poi prenu cu se batci de poi gerku</jbo>
         <en>Every-X which is-a-person is-bitten-by some-Y which is-a-dog.</en>
       </interlinear-gloss>
     </example>
     <para>using the conversion operator 
     <quote>se</quote>(explained in 
-    <xref linkend="cll_chapter5" />) to change the selbri 
+    <xref linkend="selbri" />) to change the selbri 
     <quote>batci</quote>( 
     <quote>bites</quote>) into 
     <quote>se batci</quote>( 
     <quote>is bitten by</quote>). The translation given in 
     <xref linkend="cll_chapter16-section5-example4" />uses the corresponding strategy in English, since English does not have prenexes (except in strained 
     <quote>logician's English</quote>). This implies that a sentence with both a universal and an existential variable can't be freely converted with 
 <!-- ^^   existential variable: in abstraction contrasted with in main bridi, 400; in main bridi contrasted with in abstraction, 400 -->
 <indexterm><primary>existential variable</primary></indexterm>
 <!-- ^^   existential: mixed claim with universal, 394 -->
 <indexterm><primary>existential</primary></indexterm>
diff --git a/todocbook/19.xml b/todocbook/19.xml
index 9986c91..7c8fa1a 100644
--- a/todocbook/19.xml
+++ b/todocbook/19.xml
@@ -645,21 +645,21 @@
       <listitem>
         <para>a prenex/topic (to modify some previously expressed bridi, see 
         <xref linkend="cll_chapter16" />)</para>
       </listitem>
       <listitem>
         <para>linked arguments (beginning with 
 <!-- ^^   linked arguments, 471 -->
 <indexterm><primary>linked arguments</primary></indexterm>
         <quote>be</quote>or 
         <quote>bei</quote>and attached to some previously expressed selbri, often in a description,see 
-        <xref linkend="cll_chapter5" />)</para>
+        <xref linkend="selbri" />)</para>
       </listitem>
     </itemizedlist>
     <para>At the beginning of a text, the following non-bridi are also permitted:</para>
     <itemizedlist>
       <listitem>
         <para>one or more names (to indicate direct address without 
 <!-- ^^   direct address, 323 -->
 <indexterm><primary>direct address</primary></indexterm>
         <quote>doi</quote>, see 
         <xref linkend="cll_chapter6" />)</para>
diff --git a/todocbook/2.xml b/todocbook/2.xml
index 0d034cc..c095b4b 100644
--- a/todocbook/2.xml
+++ b/todocbook/2.xml
@@ -504,21 +504,21 @@
     <para>Note that only the first and third sumti have switched places; the second sumti has remained in the second place.</para>
     <para>The cmavo 
     <quote>ve</quote>and 
     <quote>xe</quote>switch the first and fourth sumti places, and the first and fifth sumti places, respectively. These changes in the order of places are known as 
     <quote>conversions</quote>, and the 
     <quote>se</quote>, 
     <quote>te</quote>, 
     <quote>ve</quote>, and 
     <quote>xe</quote>cmavo are said to convert the selbri.</para>
     <para>More than one of these operators may be used on a given selbri at one time, and in such a case they are evaluated from left to right. However, in practice they are used one at a time, as there are better tools for complex manipulation of the sumti places. See 
-    <xref linkend="cll_chapter5" />for details.</para>
+    <xref linkend="selbri" />for details.</para>
     <para>The effect is similar to what in English is called the 
     <quote>passive voice</quote>. In Lojban, the converted selbri has a new place structure that is renumbered to reflect the place reversal, thus having effects when such a conversion is used in combination with other constructs such as 
 <!-- ^^   passive voice, 16 -->
 <indexterm><primary>passive voice</primary></indexterm>
 <!-- ^^   converted selbri: as different selbri from unconverted, 192; as resetting standard order, 193; compared with selbri with FA in meaning, 193; contrasted with other similar selbri, 193; contrasted with selbri with FA in structure, 193; definition, 192; forming with SE, 192; in descriptions, 193; place structure of, 192; retention of basic meaning in, 193; to access non-first place in description, 193 -->
 <indexterm><primary>converted selbri</primary></indexterm>
     <quote>le selbri [ku]</quote>(see 
     <xref linkend="cll_chapter2-section10" />).</para>
   </section>
   <section xml:id="cll_chapter2-section8">
@@ -1487,21 +1487,21 @@
         <term>sumti:</term>
         <listitem>
           <para>argument; words identifying something which stands in a specified relationship to something else, or which has a specified property. See 
           <xref linkend="cll_chapter6" />.</para>
         </listitem>
       </varlistentry>
       <varlistentry>
         <term>selbri:</term>
         <listitem>
           <para>logical predicate; the core of a bridi; the word or words specifying the relationship between the objects referred to by the sumti. See 
-          <xref linkend="cll_chapter5" />.</para>
+          <xref linkend="selbri" />.</para>
         </listitem>
       </varlistentry>
       <varlistentry>
         <term>cmavo:</term>
         <listitem>
           <para>one of the Lojban parts of speech; a short word; a structural word; a word used for its grammatical function.</para>
 <!-- ^^   parts of speech, 50 -->
 <indexterm><primary>parts of speech</primary></indexterm>
         </listitem>
       </varlistentry>
@@ -1542,21 +1542,21 @@
         <term>rafsi:</term>
         <listitem>
           <para>a word fragment; one or more is associated with each gismu; can be assembled according to rules in order to make lujvo; not a valid word by itself. See 
           <xref linkend="cll_chapter4" />.</para>
         </listitem>
       </varlistentry>
       <varlistentry>
         <term>tanru:</term>
         <listitem>
           <para>a group of two or more brivla, possibly with associated cmavo, that form a selbri; always divisible into two parts, with the first part modifying the meaning of the second part (which is taken to be basic). See 
-          <xref linkend="cll_chapter5" />.</para>
+          <xref linkend="selbri" />.</para>
         </listitem>
       </varlistentry>
       <varlistentry>
         <term>selma'o:</term>
         <listitem>
           <para>a group of cmavo that have the same grammatical use (can appear interchangeably in sentences, as far as the grammar is concerned) but differ in meaning or other usage. See 
           <xref linkend="cll_chapter20" />.</para>
         </listitem>
       </varlistentry>
     </variablelist>
diff --git a/todocbook/4.xml b/todocbook/4.xml
index bf34490..e84566d 100644
--- a/todocbook/4.xml
+++ b/todocbook/4.xml
@@ -188,21 +188,21 @@
 <indexterm><primary>punctuation marks</primary></indexterm>
 <!-- ^^   prepositions: cmavo as Lojban equivalents, 50 -->
 <indexterm><primary>prepositions</primary></indexterm>
 <!-- ^^   hundred: expressing as number, 432 -->
 <indexterm><primary>hundred</primary></indexterm>
 <!-- ^^   conjunctions: cmavo as Lojban equivalents, 50 -->
 <indexterm><primary>conjunctions</primary></indexterm>
 <!-- ^^   articles: cmavo as Lojban equivalents, 50 -->
 <indexterm><primary>articles</primary></indexterm>
     <quote>selma'o</quote>, each having a specifically defined grammatical usage. The various selma'o are discussed throughout 
-    <xref linkend="cll_chapter5" />to 
+    <xref linkend="selbri" />to 
     <xref linkend="cll_chapter19" />and summarized in 
     <xref linkend="cll_chapter20" />.</para>
     <para>Standard cmavo occur in four forms defined by their word structure. Here are some examples of the various forms:</para>
     <cmavo-list>
       <cmavo-entry>
         <cmavo>V-form .a .e .i</cmavo>
         <selmaho>.o</selmaho>
         <description>.u</description>
       </cmavo-entry>
       <cmavo-entry>
@@ -572,21 +572,21 @@
       <interlinear-gloss>
         <jbo>skami pilno</jbo>
       </interlinear-gloss>
     </example>
     <para>is the tanru which expresses the concept of 
     <quote>computer user</quote>.</para>
     <para>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>The meaning of a tanru is usually at least partly ambiguous: 
     <quote>skami pilno</quote>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>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="cll_chapter5" />.</para>
+    <xref linkend="selbri" />.</para>
     <para>To express a simple tanru, simply say the component gismu together. Thus the binary metaphor 
     <quote>big boat</quote>becomes the tanru</para>
 <!-- ^^   big boat: example, 55 -->
 <indexterm><primary>big boat</primary></indexterm>
     <example role="interlinear-gloss-example" xml:id="random-id-oLE3">
       <title>
         <anchor xml:id="c4e5d2" />
         <anchor xml:id="cll_chapter4-section5-example2" />
       </title>
       <interlinear-gloss>
@@ -1943,21 +1943,21 @@
 <!-- ^^   Zipf's Law, 69 -->
 <indexterm><primary>Zipf's Law</primary></indexterm>
 <!-- ^^   basis: example, 317 -->
 <indexterm><primary>basis</primary></indexterm>
     <para>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>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>
 <!-- ^^   anticipated: example, 316 -->
 <indexterm><primary>anticipated</primary></indexterm>
     <para>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="cll_chapter5" />; abstraction is explained in 
+    <xref linkend="selbri" />; abstraction is explained in 
     <xref linkend="cll_chapter11" />.) Plausibility is the key to learning new ideas and to evaluating unfamiliar lujvo.</para>
   </section>
   <section xml:id="cll_chapter4-section11">
     <title>The lujvo-making algorithm</title>
     <para>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 
 <!-- ^^   Brown: James Cooke, 6; James Cooke, and "letteral", 413 -->
 <indexterm><primary>Brown</primary></indexterm>
     <quote>tosmabru test</quote>.</para>
 <!-- ^^   tosmabru test, 71 -->
 <indexterm><primary>tosmabru test</primary></indexterm>
diff --git a/todocbook/5.xml b/todocbook/5.xml
index b423caa..7a1b964 100644
--- a/todocbook/5.xml
+++ b/todocbook/5.xml
@@ -1,13 +1,12 @@
-<chapter xml:id="cll_chapter5">
-  <title>Chapter 5 
-  <quote>Pretty Little Girls' School</quote>: The Structure Of Lojban selbri</title>
+<chapter xml:id="selbri">
+  <title><quote>Pretty Little Girls' School</quote>: The Structure Of Lojban selbri</title>
   <section xml:id="cll_chapter5-section1">
     <title>Lojban content words: brivla</title>
     <para>At the center, logically and often physically, of every Lojban bridi is one or more words which constitute the selbri. A bridi expresses a relationship between things: the selbri specifies which relationship is referred to. The difference between:</para>
     <example role="interlinear-gloss-example" xml:id="random-id-dNXY">
       <title>
         <anchor xml:id="c5e1d1" />
         <anchor xml:id="cll_chapter5-section1-example1" />
       </title>
       <interlinear-gloss>
         <jbo>do mamta mi</jbo>
diff --git a/todocbook/6.xml b/todocbook/6.xml
index 3e723f9..86fd6b7 100644
--- a/todocbook/6.xml
+++ b/todocbook/6.xml
@@ -1204,21 +1204,21 @@
         <jbo>mi ponse su'o ci lo cutci</jbo>
         <gloss>I possess at-least three things-which-really-are shoes</gloss>
         <en>I own three (or more) shoes.</en>
       </interlinear-gloss>
     </example>
   </section>
   <section xml:id="cll_chapter6-section9">
     <title>sumti-based descriptions</title>
     <para>As stated in 
     <xref linkend="cll_chapter6-section2" />, most descriptions consist of just a descriptor and a selbri. (In this chapter, the selbri have always been single gismu, but of course any selbri, however complex, can be employed in a description. The syntax and semantics of selbri are explained in 
-    <xref linkend="cll_chapter5" />.) In the intervening sections, inner and outer quantifiers have been added to the syntax. Now it is time to discuss a description of a radically different kind: the sumti-based description.</para>
+    <xref linkend="selbri" />.) In the intervening sections, inner and outer quantifiers have been added to the syntax. Now it is time to discuss a description of a radically different kind: the sumti-based description.</para>
 <!-- ^^   sumti-based description: definition, 132; inner quantifier on, 132; outer quantifier on, 132 -->
 <indexterm><primary>sumti-based description</primary></indexterm>
     <para>A sumti-based description has a sumti where the selbri would normally be, and the inner quantifier is required - it cannot be implicit. An outer quantifier is permitted but not required.</para>
 <!-- ^^   sumti-based description: definition, 132; inner quantifier on, 132; outer quantifier on, 132 -->
 <indexterm><primary>sumti-based description</primary></indexterm>
     <para>A full theory of sumti-based descriptions has yet to be worked out. One common case, however, is well understood. Compare the following:</para>
     <example role="interlinear-gloss-example" xml:id="random-id-aJEh">
       <title>
         <anchor xml:id="c6e9d1" />
         <anchor xml:id="cll_chapter6-section9-example1" />
diff --git a/todocbook/9.xml b/todocbook/9.xml
index be4802b..00a2644 100644
--- a/todocbook/9.xml
+++ b/todocbook/9.xml
@@ -616,21 +616,21 @@
     <quote>se ke blanu zdani [ke'e]</quote>is therefore:</para>
     <programlisting xml:space="preserve">
        x1 is the inhabitant of the blue house (etc.) x2
 </programlisting>
     <para>Consequently, 
     <xref linkend="cll_chapter9-section4-example8" />means:</para>
     <programlisting xml:space="preserve">
        I am the inhabitant of the blue house which is this thing.
 </programlisting>
     <para>Conversion applied to only part of a tanru has subtler effects which are explained in 
-    <xref linkend="cll_chapter5" />.</para>
+    <xref linkend="selbri" />.</para>
     <para>It is grammatical to convert a selbri more than once with SE; later (inner) conversions are applied before earlier (outer) ones. For example, the place structure of 
     <quote>se te klama</quote>is achieved by exchanging the x1 and x2 place of 
 <!-- ^^   se te, 194 -->
 <indexterm><primary>se te</primary></indexterm>
     <quote>te klama</quote>, producing:</para>
     <programlisting xml:space="preserve">
        x1 is the destination and x2 is the origin of x3 going via x4 using x5
 <!-- ^^   the destination: example, 193 -->
 <indexterm><primary>the destination</primary></indexterm>
 </programlisting>
@@ -904,21 +904,21 @@
         <en>A man of the north came to the city.</en>
       </interlinear-gloss>
     </example>
     <para>Here 
     <quote>le berti</quote>is provided as a modal place of the selbri 
     <quote>nanmu</quote>, but its exact significance is vague, and is paralleled in the colloquial translation by the vague English preposition 
     <quote>of</quote>. 
     <xref linkend="cll_chapter9-section6-example7" />also illustrates a modal place bound into a selbri with 
     <quote>be</quote>. This construction is useful when the selbri of a description requires a modal place; this and other uses of 
     <quote>be</quote>are more fully explained in 
-    <xref linkend="cll_chapter5" />.</para>
+    <xref linkend="selbri" />.</para>
   </section>
   <section xml:id="cll_chapter9-section7">
     <title>Modal sentence connection: the causals</title>
 <!-- ^^   causals: claiming the relation contrasted with claiming cause and/or effect and/or relation, 198; gismu, 197; modal, 197 -->
 <indexterm><primary>causals</primary></indexterm>
     <para>The following cmavo are discussed in this section:</para>
     <cmavo-list>
       <cmavo-entry>
         <cmavo>ri'a</cmavo>
         <selmaho>BAI</selmaho>
diff --git a/todocbook/TODO b/todocbook/TODO
index 5fee21e..b14b77c 100644
--- a/todocbook/TODO
+++ b/todocbook/TODO
@@ -1,35 +1,69 @@
 
 ==================
   Instructions For Helpers
 ==================
+
 Fix the chapter name so it's just the second part, i.e.
 
     <title>Chapter 5
       <quote>Pretty Little Girls' School</quote>: The Structure Of Lojban selbri</title>
 
 becomes:
 
     <title><quote>Pretty Little Girls' School</quote>: The Structure Of Lojban selbri</title>
 
 Make sure the <interlinear-gloss> bits look right (which is why the
 columns are so spaced out).
 
+ ------
+
+Fix IDs/tags.  A command like the following should do the trick:
+
+  sed -i 's/"cll_chapter5"/"selbri"/g' [0-9]*.xml
+
+Please run "git diff" afterwards to make sure it did what you
+expected.  Check in as often as you like (to make the diffs
+manageable).
+
+We want short and meaningful; these are used to make file names and
+so on.  If multi-word, please make a slug (see
+http://en.wikipedia.org/wiki/Slug_%28web_publishing%29 ); we are
+using - based slugs rather than _ based, so drop all special
+characters, lowercase, replace space with -.
+
+Do this for all sections.  Feel free to do it for examples too if an
+example has an obvious title.  The important thing here is that
+*NOTHING* mentions a fixed number!  *NOWHERE* in the docbook should
+*ANYTHING* be aware that it is in chapter 20 or section 7 or
+anything like that.  This is to give us the freedom to move things
+around later.
+
+Numeric-based stuff will all be autogenerated during processing,
+based on the current state of the docs.
+
+
 ==================
   Data
 ==================
 - lojban words, lojban phrases, terms of art ("abstraction"),
   others?... should each have their own index
+- cll_chapter5-section1 should be content-words-brivla or so ; those
+  IDs should not change when things are moved around
 
 ==================
   Display
 ==================
 - links to examples should *say* "example N"; easy to test from the
   index
 - links to sections should say the number of section and chapter
 - examples should be 5.2.1 rather than 5.6 for the first example in
   section 2 of chatpre 5
 
 ==================
   Both/Other
 ==================
 - make sure backwards-compatible anchors exist
+  - Ideally, make sure they are autogenerated as part of the HTML
+    production.
+- Similarily, generate more-readable anchors based on current
+  section number and such

-- 
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.