[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bpfk] dag-cll git updates for Thu Feb 3 02:21:05 EST 2011
commit 32a1f4ba4b7c03f04f47f62f14d26c25f0fb05e0
Merge: 6a2f417 60341f5
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date: Wed Feb 2 23:09:52 2011 -0800
Merge commit '60341f53adb7cbced3b4476b69a6aa0efa8aee05' into gh-pages
commit 6a2f417d88b118de5d82d7c0add6392f7401a13d
Merge: e63c405 97365f0
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date: Wed Feb 2 22:58:28 2011 -0800
Merge commit '97365f0bd2cc805b4d549fc5bfaa539c7d06c98f' into gh-pages
commit e63c405b116858a8402ffd508952d9ee5caa4c33
Merge: 9b639c4 2883395
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date: Wed Feb 2 22:39:56 2011 -0800
Merge commit '28833950b5bd99b745accaab728a194f2f7eb0ae' into gh-pages
commit 9b639c4929339059f84f72bb238d2bc8b81e6ee6
Merge: 4dcf042 8efd40d
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date: Wed Feb 2 22:36:48 2011 -0800
Merge commit '8efd40db4c231f470a1c962c4c3808e2f0a75071' into gh-pages
commit 4dcf0421fd89005565f0820ba57e717ba2cd5111
Merge: 11bbc04 bcacdb6
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date: Wed Feb 2 22:31:04 2011 -0800
Merge commit 'bcacdb645be573910870fb23a531c9ccd9e11077' into gh-pages
commit 11bbc043434508334a3b16ef5447bdb8122d53b2
Merge: 2a38527 93899e5
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date: Wed Feb 2 22:24:15 2011 -0800
Merge commit '93899e5b79dbe5bfcad00fc7e0cdaf16d83eaee9' into gh-pages
commit 2a385279cb0bcc7704021ebdb1ae8587b9851c8e
Merge: 962f040 a2cbb0a
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date: Wed Feb 2 22:18:54 2011 -0800
Merge commit 'a2cbb0a4f260557e1e422861caced687899adebc' into gh-pages
commit 60341f53adb7cbced3b4476b69a6aa0efa8aee05
Author: Eitan Postavsky <eitanp32@gmail.com>
Date: Wed Jan 26 23:30:55 2011 -0500
<link>ized jek/joik/guhek table at the end of chapter 14, and small TODO update.
diff --git a/todocbook/14.xml b/todocbook/14.xml
index df53f1d..d4e80ba 100644
--- a/todocbook/14.xml
+++ b/todocbook/14.xml
@@ -3015,79 +3015,79 @@
<entry>construct</entry>
<entry>afterthought logical</entry>
<entry>forethought logical</entry>
<entry>afterthought non-logical</entry>
<entry>forethought non-logical</entry>
</row>
</thead>
<tbody>
<row>
<entry>bridi</entry>
- <entry>ijek*</entry>
- <entry>gek</entry>
- <entry>ijoik*</entry>
- <entry>joigik</entry>
+ <entry><link linkend="section-bridi-connection">ijek*</link></entry>
+ <entry><link linkend="section-forethought-bridi-connection">gek</link></entry>
+ <entry><link linkend="section-non-logical-continued">ijoik*</link></entry>
+ <entry><link linkend="section-non-logical-continued-continued">joigik</link></entry>
</row>
<row>
<entry>sumti</entry>
- <entry>ek*</entry>
- <entry>gek</entry>
- <entry>joik*</entry>
- <entry>joigik</entry>
+ <entry><link linkend="section-sumti-connection">ek*</link></entry>
+ <entry><link linkend="section-sumti-connection">gek</link></entry>
+ <entry><link linkend="section-non-logical-connectives">joik*</link></entry>
+ <entry><link linkend="section-non-logical-continued-continued">joigik</link></entry>
</row>
<row>
<entry>bridi-tails</entry>
- <entry>gihek*</entry>
- <entry>gek</entry>
+ <entry><link linkend="section-compound-bridi">gihek*</link></entry>
+ <entry><link linkend="section-compound-bridi">gek</link></entry>
<entry>-</entry>
- <entry>joigik</entry>
+ <entry><link linkend="section-non-logical-continued-continued">joigik</link></entry>
</row>
<row>
<entry>termsets</entry>
- <entry>ek*</entry>
- <entry>gek</entry>
- <entry>joik*</entry>
- <entry>joigik</entry>
+ <entry><link linkend="section-termsets">ek*</link></entry>
+ <entry><link linkend="section-termsets">gek</link></entry>
+ <entry><link linkend="section-termsets">joik*</link></entry>
+ <entry><link linkend="section-termsets">joigik</link></entry>
</row>
<row>
<entry>tanru parts</entry>
- <entry>jek</entry>
- <entry>guhek</entry>
- <entry>joik*</entry>
+ <entry><link linkend="section-tanru">jek</link></entry>
+ <entry><link linkend="section-tanru">guhek</link></entry>
+ <entry><link linkend="section-tanru">joik*</link></entry>
<entry>-</entry>
</row>
<row>
<entry>operands</entry>
- <entry>ek*</entry>
- <entry>gek</entry>
- <entry>joik*</entry>
- <entry>joigik</entry>
+ <entry><link linkend="section-mekso-connections">ek*</link></entry>
+ <entry><link linkend="section-mekso-connections">gek</link></entry>
+ <entry><link linkend="section-mekso-connections">joik*</link></entry>
+ <entry><link linkend="section-mekso-connections">joigik</link></entry>
</row>
<row>
<entry>operators</entry>
- <entry>jek</entry>
- <entry>guhek</entry>
- <entry>joik</entry>
+ <entry><link linkend="section-mekso-connections">jek</link></entry>
+ <entry><link linkend="section-mekso-connections">guhek</link></entry>
+ <entry><link linkend="section-mekso-connections">joik</link></entry>
<entry>-</entry>
</row>
<row>
<entry>tenses/modals</entry>
- <entry>jek</entry>
+ <entry><link linkend="section-sumtcita">jek</link></entry>
<entry>-</entry>
- <entry>joik</entry>
+ <entry><link linkend="section-sumtcita">joik</link></entry>
<entry>-</entry>
</row>
<row>
<entry>abstractors</entry>
- <entry>jek</entry>
+ <entry><link linkend="section-abstractors">jek</link></entry>
<entry>-</entry>
- <entry>joik</entry>
+ <entry><link linkend="section-abstractors">joik</link></entry>
<entry>-</entry>
</row>
</tbody>
</tgroup>
</informaltable>
</section>
<section xml:id="section-truth-functions-summary">
<title>Truth functions and corresponding logical connectives</title>
<para> <indexterm type="general-imported"><primary>logical connectives</primary><secondary>table by truth function value</secondary></indexterm> <indexterm type="general-imported"><primary>truth functions</primary><secondary>table of logical connectives</secondary></indexterm> The following table specifies, for each truth function, the most-often used cmavo or compound cmavo which expresses it for each of the six types of logical connective. (Other compound cmavo are often possible: for example,
<jbophrase>se.a</jbophrase> means the same as
@@ -3099,141 +3099,141 @@
<colspec colnum="3" colname="col3"/>
<colspec colnum="4" colname="col4"/>
<colspec colnum="5" colname="col5"/>
<colspec colnum="6" colname="col6"/>
<thead>
<row>
<entry>truth</entry>
<entry>ek</entry>
<entry>jek</entry>
<entry>gihek</entry>
- <entry>gek–gik</entry>
- <entry>guhek–gik</entry>
+ <entry>gek-gik</entry>
+ <entry>guhek-gik</entry>
</row>
</thead>
<tbody>
<row>
<entry>TTTF</entry>
- <entry>.a</entry>
- <entry>ja</entry>
- <entry>gi'a</entry>
- <entry>ga–gi</entry>
- <entry>gu'a–gi</entry>
+ <entry><jbophrase>.a</jbophrase></entry>
+ <entry><jbophrase>ja</jbophrase></entry>
+ <entry><jbophrase>gi'a</jbophrase></entry>
+ <entry><jbophrase>ga-gi</jbophrase></entry>
+ <entry><jbophrase>gu'a-gi</jbophrase></entry>
</row>
<row>
<entry>TTFT</entry>
- <entry>.anai</entry>
- <entry>janai</entry>
- <entry>gi'anai</entry>
- <entry>ga–ginai</entry>
- <entry>gu'a–ginai</entry>
+ <entry><jbophrase>.anai</jbophrase></entry>
+ <entry><jbophrase>janai</jbophrase></entry>
+ <entry><jbophrase>gi'anai</jbophrase></entry>
+ <entry><jbophrase>ga-ginai</jbophrase></entry>
+ <entry><jbophrase>gu'a-ginai</jbophrase></entry>
</row>
<row>
<entry>TTFF</entry>
- <entry>.u</entry>
- <entry>ju</entry>
- <entry>gi'u</entry>
- <entry>gu–gi</entry>
- <entry>gu'u–gi</entry>
+ <entry><jbophrase>.u</jbophrase></entry>
+ <entry><jbophrase>ju</jbophrase></entry>
+ <entry><jbophrase>gi'u</jbophrase></entry>
+ <entry><jbophrase>gu-gi</jbophrase></entry>
+ <entry><jbophrase>gu'u-gi</jbophrase></entry>
</row>
<row>
<entry>TFTT</entry>
- <entry>na.a</entry>
- <entry>naja</entry>
- <entry>nagi'a</entry>
- <entry>ganai–gi</entry>
- <entry>gu'anai–gi</entry>
+ <entry><jbophrase>na.a</jbophrase></entry>
+ <entry><jbophrase>naja</jbophrase></entry>
+ <entry><jbophrase>nagi'a</jbophrase></entry>
+ <entry><jbophrase>ganai-gi</jbophrase></entry>
+ <entry><jbophrase>gu'anai-gi</jbophrase></entry>
</row>
<row>
<entry>TFTF</entry>
- <entry>se.u</entry>
- <entry>seju</entry>
- <entry>segi'u</entry>
- <entry>segu–gi</entry>
- <entry>segu'u–gi</entry>
+ <entry><jbophrase>se.u</jbophrase></entry>
+ <entry><jbophrase>seju</jbophrase></entry>
+ <entry><jbophrase>segi'u</jbophrase></entry>
+ <entry><jbophrase>segu-gi</jbophrase></entry>
+ <entry><jbophrase>segu'u-gi</jbophrase></entry>
</row>
<row>
<entry>TFFT</entry>
- <entry>.o</entry>
- <entry>jo</entry>
- <entry>gi'o</entry>
- <entry>go–gi</entry>
- <entry>gu'o–gi</entry>
+ <entry><jbophrase>.o</jbophrase></entry>
+ <entry><jbophrase>jo</jbophrase></entry>
+ <entry><jbophrase>gi'o</jbophrase></entry>
+ <entry><jbophrase>go-gi</jbophrase></entry>
+ <entry><jbophrase>gu'o-gi</jbophrase></entry>
</row>
<row>
<entry>TFFF</entry>
- <entry>.e</entry>
- <entry>je</entry>
- <entry>gi'e</entry>
- <entry>ge–gi</entry>
- <entry>gu'e–gi</entry>
+ <entry><jbophrase>.e</jbophrase></entry>
+ <entry><jbophrase>je</jbophrase></entry>
+ <entry><jbophrase>gi'e</jbophrase></entry>
+ <entry><jbophrase>ge-gi</jbophrase></entry>
+ <entry><jbophrase>gu'e-gi</jbophrase></entry>
</row>
<row>
<entry>FTTT</entry>
- <entry>na.anai</entry>
- <entry>najanai</entry>
- <entry>nagi'anai</entry>
- <entry>ganai–ginai</entry>
- <entry>gu'anai–ginai</entry>
+ <entry><jbophrase>na.anai</jbophrase></entry>
+ <entry><jbophrase>najanai</jbophrase></entry>
+ <entry><jbophrase>nagi'anai</jbophrase></entry>
+ <entry><jbophrase>ganai-ginai</jbophrase></entry>
+ <entry><jbophrase>gu'anai-ginai</jbophrase></entry>
</row>
<row>
<entry>FTTF</entry>
- <entry>.onai</entry>
- <entry>jonai</entry>
- <entry>gi'onai</entry>
- <entry>go–ginai</entry>
- <entry>gu'o–ginai</entry>
+ <entry><jbophrase>.onai</jbophrase></entry>
+ <entry><jbophrase>jonai</jbophrase></entry>
+ <entry><jbophrase>gi'onai</jbophrase></entry>
+ <entry><jbophrase>go-ginai</jbophrase></entry>
+ <entry><jbophrase>gu'o-ginai</jbophrase></entry>
</row>
<row>
<entry>FTFT</entry>
- <entry>se.unai</entry>
- <entry>sejunai</entry>
- <entry>segi'unai</entry>
- <entry>segu–ginai</entry>
- <entry>segu'u–ginai</entry>
+ <entry><jbophrase>se.unai</jbophrase></entry>
+ <entry><jbophrase>sejunai</jbophrase></entry>
+ <entry><jbophrase>segi'unai</jbophrase></entry>
+ <entry><jbophrase>segu-ginai</jbophrase></entry>
+ <entry><jbophrase>segu'u-ginai</jbophrase></entry>
</row>
<row>
<entry>FTFF</entry>
- <entry>.enai</entry>
- <entry>jenai</entry>
- <entry>gi'enai</entry>
- <entry>ge–ginai</entry>
- <entry>gu'e–ginai</entry>
+ <entry><jbophrase>.enai</jbophrase></entry>
+ <entry><jbophrase>jenai</jbophrase></entry>
+ <entry><jbophrase>gi'enai</jbophrase></entry>
+ <entry><jbophrase>ge-ginai</jbophrase></entry>
+ <entry><jbophrase>gu'e-ginai</jbophrase></entry>
</row>
<row>
<entry>FFTT</entry>
- <entry>na.u</entry>
- <entry>naju</entry>
- <entry>nagi'u</entry>
- <entry>gunai–gi</entry>
- <entry>gu'unai–gi</entry>
+ <entry><jbophrase>na.u</jbophrase></entry>
+ <entry><jbophrase>naju</jbophrase></entry>
+ <entry><jbophrase>nagi'u</jbophrase></entry>
+ <entry><jbophrase>gunai-gi</jbophrase></entry>
+ <entry><jbophrase>gu'unai-gi</jbophrase></entry>
</row>
<row>
<entry>FFTF</entry>
- <entry>na.e</entry>
- <entry>naje</entry>
- <entry>nagi'e</entry>
- <entry>genai–gi</entry>
- <entry>gu'enai–gi</entry>
+ <entry><jbophrase>na.e</jbophrase></entry>
+ <entry><jbophrase>naje</jbophrase></entry>
+ <entry><jbophrase>nagi'e</jbophrase></entry>
+ <entry><jbophrase>genai-gi</jbophrase></entry>
+ <entry><jbophrase>gu'enai-gi</jbophrase></entry>
</row>
<row>
<entry>FFFT</entry>
- <entry>na.enai</entry>
- <entry>najenai</entry>
- <entry>nagi'enai</entry>
- <entry>genai–ginai</entry>
- <entry>gu'enai–ginai</entry>
+ <entry><jbophrase>na.enai</jbophrase></entry>
+ <entry><jbophrase>najenai</jbophrase></entry>
+ <entry><jbophrase>nagi'enai</jbophrase></entry>
+ <entry><jbophrase>genai-ginai</jbophrase></entry>
+ <entry><jbophrase>gu'enai-ginai</jbophrase></entry>
</row>
</tbody>
</tgroup>
</informaltable>
- <para>Note: Ijeks are exactly the same as the corresponding jeks, except for the prefixed <!-- FIXME: "ijeks", not "Ijeks"? -->
+ <para>Note: ijeks are exactly the same as the corresponding jeks, except for the prefixed
<jbophrase>.i</jbophrase>.</para>
</section>
<section xml:id="section-construction-summary">
<title>Rules for making logical and non-logical connectives</title>
<para> <indexterm type="general-imported"><primary>non-logical connectives</primary><secondary>syntax rules summary</secondary></indexterm> <indexterm type="general-imported"><primary>logical connectives</primary><secondary>syntax rules summary</secondary></indexterm> The full set of rules for inserting
<jbophrase>na</jbophrase>,
<jbophrase>se</jbophrase>, and
<jbophrase>nai</jbophrase> into any connective is:</para>
<para>Afterthought logical connectives (eks, jeks, giheks, ijeks):</para>
diff --git a/todocbook/TODO b/todocbook/TODO
index c7a8458..76c7222 100644
--- a/todocbook/TODO
+++ b/todocbook/TODO
@@ -24,48 +24,20 @@ If you have any trouble, add a FIXME comment, like so:
<!-- FIXME: detailed explanation here -->
------
Make sure the <interlinear-gloss> bits look right in the output (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_chapter8-section1"/"chapter-relative-clauses-section-poi"/g' [0-9]*.xml
-
-BUT FIRST: check that it doesn't already exist:
-
- grep '"chapter-relative-clauses-section-poi"' [0-9]*.xml
-
-because duplicates would really suck.
-
-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 -.
-
-Make sure that the ids for chapters have "chapter-" at the start,
-"section-" for the sections, and "example-" for the examples; we
-might need them for auto-processing.
-
-Do this for all sections. Feel free to do it for examples too if an
-example has an obvious title, but it's much less important there, so
-not worth spending time on for the first pass.
-
References to examples in the text should be changed to <xref>s, using
the random id of the example in question, e.g. <xref linkend="example-random-id-qjmr"/>
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.
@@ -107,29 +79,30 @@ change it, or think it's actually correct in some particular place,
post to the BPFK list.
------
If an example/interlinear-gloss consists solely of English, replace
the <interlinear-gloss>...</interlinear-gloss> with <para>...</para>
------
Make sure all the components of <example>s are appropriately wrapped in
-<jbo>, <gloss>, <en>, <ipa>, or <foreign> (if it doesn't fit one of
-those, make up a tag and report it).
+<jbo>, <gloss>, <en>, <ipa>, <math>, or <foreign> (if it doesn't fit
+one of those, make up a tag).
------
Entries like <indexterm type="lojban-word-imported"> (NOTE the type)
probably need to be destroyed; there should be a bit of Lojban near
them that can be wrapped in <jbophrase>, to exactly the same effect
-as the <indexterm> entry. If you can't find such a correspondance,
+as the <indexterm> entry, UNLESS said Lojban text is part of a bigger
+Lojban phrase; leave those for now. If you can't find such a correspondance,
add a FIXME comment.
------
Entries like <indexterm type="example-imported"> (NOTE the type)
need to be moved into examples.
Especially things like this:
<para> <indexterm type="example-imported"><primary>lemon tree</primary><secondary>example</secondary></indexterm> FIXME: TAG SPOT</para>
commit 97365f0bd2cc805b4d549fc5bfaa539c7d06c98f
Author: Eitan Postavsky <eitanp32@gmail.com>
Date: Wed Jan 26 19:19:54 2011 -0500
Hyphens to en dashes where appropriate.
diff --git a/todocbook/1.xml b/todocbook/1.xml
index 73b2cd5..ba516c0 100644
--- a/todocbook/1.xml
+++ b/todocbook/1.xml
@@ -53,22 +53,22 @@
<title>What is this book?</title>
<para> <indexterm type="general-imported"><primary>goal of this book</primary></indexterm> <indexterm type="general-imported"><primary>this book</primary><secondary>goal of</secondary></indexterm> <indexterm type="general-imported"><primary>reference grammar</primary></indexterm> This book is what is called a
<quote>reference grammar</quote>. It attempts to expound the whole Lojban language, or at least as much of it as is understood at present. Lojban is a rich language with many features, and an attempt has been made to discover the functions of those features. The word
<quote>discover</quote> is used advisedly; Lojban was not
<quote>invented</quote> by any one person or committee. Often, grammatical features were introduced into the language long before their usage was fully understood. Sometimes they were introduced for one reason, only to prove more useful for other reasons not recognized at the time.</para>
<para>By intention, this book is complete in description but not in explanation. For every rule in the formal Lojban grammar (given in
<xref linkend="chapter-grammars"/>), there is a bit of explanation and an example somewhere in the book, and often a great deal more than a bit. In essence,
<xref linkend="chapter-tour"/> gives a brief overview of the language,
<xref linkend="chapter-grammars"/> gives the formal structure of the language, and the chapters in between put semantic flesh on those formal bones. I hope that eventually more grammatical material founded on (or even correcting) the explanations in this book will become available.</para>
- <para> <indexterm type="general-imported"><primary>linguistic drift</primary></indexterm> <indexterm type="general-imported"><primary>Lojban</primary><secondary>stability of</secondary></indexterm> Nevertheless, the publication of this book is, in one sense, the completion of a long period of language evolution. With the exception of a possible revision of the language that will not even be considered until five years from publication date, and any revisions of this book needed to correct outright errors, the language described in this book will not be changing by deliberate act of its creators any more. Instead, language change will take place in the form of new vocabulary - Lojban does not yet have nearly the vocabulary it needs to be a fully usable language of the modern world, as
- <xref linkend="chapter-lujvo"/> explains - and through the irregular natural processes of drift and (who knows?) native-speaker evolution. (Teach your children Lojban!) You can learn the language described here with assurance that (unlike previous versions of Lojban and Loglan, as well as most other artificial languages) it will not be subject to further fiddling by language-meisters.</para>
+ <para> <indexterm type="general-imported"><primary>linguistic drift</primary></indexterm> <indexterm type="general-imported"><primary>Lojban</primary><secondary>stability of</secondary></indexterm> Nevertheless, the publication of this book is, in one sense, the completion of a long period of language evolution. With the exception of a possible revision of the language that will not even be considered until five years from publication date, and any revisions of this book needed to correct outright errors, the language described in this book will not be changing by deliberate act of its creators any more. Instead, language change will take place in the form of new vocabulary – Lojban does not yet have nearly the vocabulary it needs to be a fully usable language of the modern world, as
+ <xref linkend="chapter-lujvo"/> explains – and through the irregular natural processes of drift and (who knows?) native-speaker evolution. (Teach your children Lojban!) You can learn the language described here with assurance that (unlike previous versions of Lojban and Loglan, as well as most other artificial languages) it will not be subject to further fiddling by language-meisters.</para>
<para> <indexterm type="general-imported"><primary>this book</primary><secondary>structure of</secondary></indexterm> <indexterm type="general-imported"><primary>structure of this book</primary></indexterm> It is probably worth mentioning that this book was written somewhat piecemeal. Each chapter began life as an explication of a specific Lojban topic; only later did these begin to clump together into a larger structure of words and ideas. Therefore, there are perhaps not as many cross-references as there should be. However, I have attempted to make the index as comprehensive as possible.</para>
<para> <indexterm type="general-imported"><primary>chapter titles</primary><secondary>intent of</secondary></indexterm> <indexterm type="general-imported"><primary>jokes</primary></indexterm> <indexterm type="general-imported"><primary>Lojbanistan</primary></indexterm> Each chapter has a descriptive title, often involving some play on words; this is an attempt to make the chapters more memorable. The title of
<xref linkend="chapter-about"/> (which you are now reading), for example, is an allusion to the book
<citation>English As We Speak It In Ireland</citation>, by P. W. Joyce, which is a sort of informal reference grammar of Hiberno-English.
<quote>Lojbanistan</quote> is both an imaginary country where Lojban is the native language, and a term for the actual community of Lojban-speakers, scattered over the world. Why
<quote>mangle</quote>? As yet, nobody in the real Lojbanistan speaks the language at all well, by the standards of the imaginary Lojbanistan; that is one of the circumstances this book is meant to help remedy.</para>
</section>
diff --git a/todocbook/10.xml b/todocbook/10.xml
index d3e0765..67191e2 100644
--- a/todocbook/10.xml
+++ b/todocbook/10.xml
@@ -228,21 +228,21 @@
<interlinear-gloss>
<jbo>zu'aviku le nanmu cu batci le gerku</jbo>
<gloss>[Left] [short distance] the man bites the dog.</gloss>
<en>Slightly to my left, the man bites the dog.</en>
</interlinear-gloss>
</example>
</section>
<section xml:id="section-compound-spatial-tenses">
<title>Compound spatial tenses</title>
<para> <indexterm type="general-imported"><primary>compound tense</primary><secondary>definition</secondary></indexterm> Humph, says the reader: this talk of
- <quote>imaginary journeys</quote> is all very well, but what's the point of it? -
+ <quote>imaginary journeys</quote> is all very well, but what's the point of it? –
<jbophrase>zu'a</jbophrase> means
<quote>on the left</quote> and
<jbophrase>vi</jbophrase> means
<quote>nearby</quote>, and there's no more to be said. The imaginary-journey model becomes more useful when so-called compound tenses are involved. A compound tense is exactly like a simple tense, but has several FAhAs run together:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-rWtP">
<title>
<anchor xml:id="c10e3d1"/>
@@ -587,42 +587,42 @@
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>imaginary journey</primary><secondary>with interval direction</secondary></indexterm> <indexterm type="general-imported"><primary>pu</primary><secondary>meaning when following interval specification</secondary></indexterm> means that for a short time interval extending from the past to the present I have been expressing
<xref linkend="example-random-id-imdX"/>. Here the imaginary journey starts at the present, lays down one end point of the interval, moves into the past, and lays down the other endpoint. Another example:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-AqvW">
<title>
<anchor xml:id="c10e5d6"/>
</title>
<interlinear-gloss>
<jbo>mi pu ze'aba citka le mi sanmi</jbo>
- <gloss>I [past] [medium time interval - future] eat my meal.</gloss>
+ <gloss>I [past] [medium time interval – future] eat my meal.</gloss>
<gloss>For a medium time afterward, I ate my meal.</gloss>
<en>I ate my meal for a while.</en>
</interlinear-gloss>
</example>
<para>With
<jbophrase>ca</jbophrase> instead of
<jbophrase>ba</jbophrase>,
<xref linkend="example-random-id-AqvW"/> becomes
<xref linkend="example-random-id-a5dp"/>,</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-a5dp">
<title>
<anchor xml:id="c10e5d7"/>
</title>
<interlinear-gloss>
<jbo>mi pu ze'aca citka le mi sanmi</jbo>
<gloss>I [past] [medium time interval – present] eat my meal.</gloss>
<gloss>For a medium time before and afterward, I ate my meal.</gloss>
<en>I ate my meal for a while.</en>
</interlinear-gloss>
</example>
- <para>because the interval would then be centered on the past moment rather than oriented toward the future of that moment. The colloquial English translations are the same - English is not well-suited to representing this distinction.</para>
+ <para>because the interval would then be centered on the past moment rather than oriented toward the future of that moment. The colloquial English translations are the same – English is not well-suited to representing this distinction.</para>
<para>Here are some examples of the use of space intervals with and without specified directions:</para>
<para> <indexterm type="example-imported"><primary>fish on right</primary><secondary>example</secondary></indexterm> FIXME: TAG SPOT</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-Mrzt">
<title>
<anchor xml:id="c10e5d8"/>
</title>
<interlinear-gloss>
<jbo>ta ri'u ve'i finpe</jbo>
<gloss>That-there [right] [short space interval] is-a-fish.</gloss>
<en>That thing on my right is a fish.</en>
@@ -746,21 +746,21 @@
<jbophrase>vi'u</jbophrase>. So the cognitive, rather than the physical, dimensionality controls the choice of VIhA cmavo.</para>
<para> <indexterm type="lojban-word-imported"><primary>vi'e</primary></indexterm> <indexterm type="general-imported"><primary>spatial tense</primary><secondary>4-dimensional interaction with temporal tense</secondary></indexterm> <indexterm type="general-imported"><primary>temporal tense</primary><secondary>interaction with 4-dimensional spatial tense</secondary></indexterm> <indexterm type="general-imported"><primary>futureward</primary><secondary>as a spatial tense</secondary></indexterm> <indexterm type="general-imported"><primary>pastward</primary><secondary>as a spatial tense</secondary></indexterm> <indexterm type="general-imported"><primary>tense</primary><secondary>space-time dimension for intervals</secondary></indexterm> <indexterm type="general-imported"><primary>spatial tense</primary><secondary>four-dimensional</secondary></indexterm> <indexterm type="general-imported"><primary>Einsteinian</primary><secondary>space-time intervals with 4 dimensions</secondary></indexterm> VIhA has a member
<jbophrase>vi'e</jbophrase> which indicates a 4-dimensional interval, one that involves both space and time. This allows the spatial tenses to invade, to some degree, the temporal tenses; it is possible to make statements about space-time considered as an Einsteinian whole. (There are presently no cmavo of FAhA assigned to
<quote>pastward</quote> and
- <quote>futureward</quote> considered as space rather than time directions - they could be added, though, if Lojbanists find space-time expression useful.) If a temporal tense cmavo is used in the same tense construct with a
+ <quote>futureward</quote> considered as space rather than time directions – they could be added, though, if Lojbanists find space-time expression useful.) If a temporal tense cmavo is used in the same tense construct with a
<jbophrase>vi'e</jbophrase> interval, the resulting tense may be self-contradictory.</para>
</section>
<section xml:id="section-movement">
<title>Movement in space: MOhI</title>
<para>The following cmavo is discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
@@ -842,21 +842,21 @@
<title>
<anchor xml:id="c10e8d5"/>
</title>
<interlinear-gloss>
<jbo>mi mo'i ca'uvu citka le mi sanmi</jbo>
<gloss>I [movement] [front] [long] eat my meal.</gloss>
<en>While moving a long way forward, I eat my meal.</en>
</interlinear-gloss>
</example>
<para> <indexterm type="example-imported"><primary>eat in airplane</primary><secondary>example</secondary></indexterm> (Perhaps I am eating in an airplane.)</para>
- <para> <indexterm type="general-imported"><primary>time travel</primary></indexterm> <indexterm type="general-imported"><primary>movement</primary><secondary>time</secondary></indexterm> There is no parallel facility in Lojban at present for expressing movement in time - time travel - but one could be added easily if it ever becomes useful.</para>
+ <para> <indexterm type="general-imported"><primary>time travel</primary></indexterm> <indexterm type="general-imported"><primary>movement</primary><secondary>time</secondary></indexterm> There is no parallel facility in Lojban at present for expressing movement in time – time travel – but one could be added easily if it ever becomes useful.</para>
</section>
<section xml:id="section-interval-properties">
<title>Interval properties: TAhE and
<jbophrase>roi</jbophrase></title>
<para>The following cmavo are discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>di'i</cmavo>
@@ -1087,21 +1087,21 @@
<anchor xml:id="c10e9d10"/>
</title>
<interlinear-gloss>
<jbo>mi ze'e paroi klama le zarci</jbo>
<gloss>I [whole interval] [once] go-to the market.</gloss>
</interlinear-gloss>
</example>
<para>Since specifying no ZEhA leaves the interval vague,
<xref linkend="example-random-id-TYve"/> might in appropriate context mean the same as
- <xref linkend="example-random-id-8WJS"/> after all - but
+ <xref linkend="example-random-id-8WJS"/> after all – but
<xref linkend="example-random-id-8WJS"/> allows us to be specific when specificity is necessary.</para>
<para> <indexterm type="lojban-word-imported"><primary>ze'eca</primary></indexterm> <indexterm type="lojban-word-imported"><primary>ze'eba</primary></indexterm> <indexterm type="lojban-word-imported"><primary>ze'epu</primary></indexterm> <indexterm type="lojban-word-imported"><primary>PU selma'o</primary></indexterm> <indexterm type="example-imported"><primary>have never</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>ze'eca</primary><secondary>meaning of</secondary></indexterm> <indexterm type="general-imported"><primary>ze'eba</primary><secondary>meaning of</secondary></indexterm> <indexterm type="general-imported"><primary>ze'epu</primary><secondary>meaning of</secondary></indexterm> <indexterm type="general-imported"><primary>ze'e</primary><secondary>effect on following PU direction</secondary></indexterm> <indexterm type="general-imported"><primary>temporal direction</primary><secondary>exception in meaning when following ze'e</secondary></indexterm> A PU cmavo following
<jbophrase>ze'e</jbophrase> has a slightly different meaning from one that follows another ZEhA cmavo. The compound cmavo
<jbophrase>ze'epu</jbophrase> signifies the interval stretching from the infinite past to the reference point (wherever the imaginary journey has taken you);
<jbophrase>ze'eba</jbophrase> is the interval stretching from the reference point to the infinite future. The remaining form,
<jbophrase>ze'eca</jbophrase>, makes specific the
@@ -1650,21 +1650,21 @@
<anchor xml:id="c10e12d10"/>
</title>
<interlinear-gloss>
<jbo>le bloti pu za'o xelklama fe'e ba'o le lalxu</jbo>
<gloss>The boat [past] [superfective] is-a-transport-mechanism [space] [perfective] the lake.</gloss>
<en>The boat sailed for too long and beyond the lake.</en>
</interlinear-gloss>
</example>
<para>Probably it sailed up onto the dock. One point of clarification: although
<jbophrase>xelklama</jbophrase> appears to mean simply
- <quote>is-a-mode-of-transport</quote>, it does not - the bridi of
+ <quote>is-a-mode-of-transport</quote>, it does not – the bridi of
<xref linkend="example-random-id-PABV"/> has four omitted arguments, and thus has the (physical) journey which goes on too long as part of its meaning.</para>
<para> <indexterm type="general-imported"><primary>sumti tcita based on quantified tenses</primary></indexterm> <indexterm type="general-imported"><primary>quantified tenses</primary><secondary>as sumti tcita</secondary></indexterm> <indexterm type="general-imported"><primary>sumti tcita based on interval properties</primary></indexterm> <indexterm type="general-imported"><primary>interval properties</primary><secondary>meaning as sumti tcita</secondary></indexterm> <indexterm type="general-imported"><primary>sumti tcita based on interval continuousness</primary></indexterm> <indexterm type="general-imported"><primary>interval continuousness</primary><secondary>meaning as sumti tcita</secondary></indexterm> <indexterm type="general-imported"><primary>sumti tcita based on dimension</primary></indexterm> <indexterm type="general-imported"><primary>dimension</primary><secondary>meaning as sumti tcita</secondary></indexterm> <indexterm type="general-imported"><primary>sumti tcita based on interval size</primary></indexterm> <indexterm type="general-imported"><primary>interval size</primary><secondary>meaning as sumti tcita</secondary></indexterm> The remaining tense cmavo, which have to do with interval size, dimension, and continuousness (or lack thereof) are interpreted to let the sumti specify the particular interval over which the main bridi operates:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-bLaQ">
<title>
<anchor xml:id="c10e12d11"/>
</title>
<interlinear-gloss>
@@ -1810,21 +1810,21 @@
<example xml:id="example-random-id-qE4m" role="interlinear-gloss-example">
<title>
<anchor xml:id="c10e13d8"/>
</title>
<interlinear-gloss>
<jbo>mi bapu klama le zarci</jbo>
<gloss>I [future] [past] go-to the market.</gloss>
<en>I will have gone to the market.</en>
</interlinear-gloss>
</example>
- <para>So when multiple tense constructs in a single bridi are involved, order counts - the tenses cannot be shifted around as freely as if there were only one tense to worry about.</para>
+ <para>So when multiple tense constructs in a single bridi are involved, order counts – the tenses cannot be shifted around as freely as if there were only one tense to worry about.</para>
<para> <indexterm type="general-imported"><primary>sticky tenses</primary><secondary>from part of a multiple tense</secondary></indexterm> But why bother to allow multiple tense constructs at all? They specify separate portions of the imaginary journey, and can be useful in order to make part of a tense sticky. Consider
<xref linkend="example-random-id-gg9C"/>, which adds a second bridi and a
<jbophrase>ki</jbophrase> to
<xref linkend="example-random-id-t7YR"/>:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-gg9C">
<title>
<anchor xml:id="c10e13d9"/>
</title>
<interlinear-gloss>
<jbo>pukiku mi ba klama le zarci .i le nanmu cu batci le gerku</jbo>
@@ -2227,21 +2227,21 @@
</title>
<interlinear-gloss>
<jbo>mi klama pugi le zarci gi le zdani</jbo>
<gloss>I go-to [past] the market [,] the house.</gloss>
</interlinear-gloss>
</example>
<para>Because English does not have any direct way of expressing a tense-like relationship between nouns,
<xref linkend="example-random-id-o3Yg"/> cannot be expressed in English without paraphrasing it either into
<xref linkend="example-random-id-9cXU"/> or else into
- <quote>I go to the house before the market</quote>, which is ambiguous - is the market going?</para>
+ <quote>I go to the house before the market</quote>, which is ambiguous – is the market going?</para>
<para> <indexterm type="lojban-word-imported"><primary>gi</primary></indexterm> <indexterm type="general-imported"><primary>bridi-tails</primary><secondary>forethought tense connection of</secondary></indexterm> <indexterm type="general-imported"><primary>imaginary journey</primary><secondary>origin in tense forethought bridi-tail connection</secondary></indexterm> <indexterm type="general-imported"><primary>forethought tense connection of bridi-tails</primary><secondary>order of</secondary></indexterm> Finally, a third forethought construction expresses a tense relationship between bridi-tails rather than whole bridi. (The construct known as a
<quote>bridi-tail</quote> is explained fully in
<xref linkend="chapter-connectives-section-compound-bridi"/>; roughly speaking, it is a selbri, possibly with following sumti.)
<xref linkend="example-random-id-vSCv"/> is equivalent in meaning to
<xref linkend="example-random-id-9cXU"/> and
<xref linkend="example-random-id-o3Yg"/>:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-vSCv">
<title>
<anchor xml:id="c10e16d8"/>
</title>
@@ -2601,21 +2601,21 @@
<jbo>ro datka ca ca'a flulimna</jbo>
<gloss>All ducks [present] [actual] are-float-swimmers.</gloss>
<en>All ducks are now actually swimming by floating.</en>
</interlinear-gloss>
</example>
<para> <indexterm type="lojban-word-imported"><primary>ki</primary></indexterm> <indexterm type="lojban-word-imported"><primary>CAhA selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>ca'a</primary></indexterm> <indexterm type="general-imported"><primary>sticky tenses</primary><secondary>and CAhA</secondary></indexterm> <indexterm type="general-imported"><primary>CAhA selma'o</primary><secondary>making sticky</secondary></indexterm> <indexterm type="general-imported"><primary>CAhA selma'o</primary><secondary>order in tense construct</secondary></indexterm> <indexterm type="general-imported"><primary>actual events</primary><secondary>explicitly expressing</secondary></indexterm> A CAhA cmavo is always placed after any other tense cmavo, whether for time or for space. However, a CAhA cmavo comes before
<jbophrase>ki</jbophrase>, so that a CAhA condition can be made sticky.</para>
<para>
<xref linkend="example-random-id-hXpB"/> is false in both Lojban and English, since it claims that the swimming is an actual, present fact, true of every duck that exists, whereas in fact there is at least one duck that is not swimming now.</para>
- <para> <indexterm type="lojban-word-imported"><primary>ka'e</primary></indexterm> <indexterm type="general-imported"><primary>innate capability</primary><secondary>expressing explicitly</secondary></indexterm> Furthermore, some ducks are dead (and therefore sink); some ducks have just hatched (and do not know how to swim yet), and some ducks have been eaten by predators (and have ceased to exist as separate objects at all). Nevertheless, all these ducks have the innate capability of swimming - it is part of the nature of duckhood. The cmavo
+ <para> <indexterm type="lojban-word-imported"><primary>ka'e</primary></indexterm> <indexterm type="general-imported"><primary>innate capability</primary><secondary>expressing explicitly</secondary></indexterm> Furthermore, some ducks are dead (and therefore sink); some ducks have just hatched (and do not know how to swim yet), and some ducks have been eaten by predators (and have ceased to exist as separate objects at all). Nevertheless, all these ducks have the innate capability of swimming – it is part of the nature of duckhood. The cmavo
<jbophrase>ka'e</jbophrase> expresses this notion of innate capability:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-ApiH">
<title>
<anchor xml:id="c10e19d4"/>
</title>
<interlinear-gloss>
<jbo>ro datka ka'e flulimna</jbo>
diff --git a/todocbook/11.xml b/todocbook/11.xml
index 26f0264..d4d337d 100644
--- a/todocbook/11.xml
+++ b/todocbook/11.xml
@@ -1289,21 +1289,21 @@
<title>
<anchor xml:id="c11e10d6"/>
</title>
<interlinear-gloss>
<jbo>tu'a la djan. cu cafne</jbo>
<gloss>something-to-do-with John frequently-occurs</gloss>
</interlinear-gloss>
</example>
<para>This must mean that something which John does, or which happens to John, occurs frequently: but without more context there is no way to figure out what. Note that without the
<jbophrase>tu'a</jbophrase>,
- <xref linkend="example-random-id-9S5B"/> would mean that John considered as an event frequently occurs - in other words, that John has some sort of on-and-off existence! Normally we do not think of people as events in English, but the x1 place of
+ <xref linkend="example-random-id-9S5B"/> would mean that John considered as an event frequently occurs – in other words, that John has some sort of on-and-off existence! Normally we do not think of people as events in English, but the x1 place of
<jbophrase>cafne</jbophrase> is an event, and if something that does not seem to be an event is put there, the Lojbanic listener will attempt to construe it as one. (Of course, this analysis assumes that
<jbophrase>djan.</jbophrase> is the name of a person, and not the name of some event.)</para>
<para> <indexterm type="lojban-word-imported"><primary>JAI selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>jai</primary></indexterm> <indexterm type="general-imported"><primary>abstractions</primary><secondary>simplification to sumti with jai</secondary></indexterm> <indexterm type="general-imported"><primary>abstractions</primary><secondary>making concrete</secondary></indexterm> Logically, a counterpart of some sort is needed to
<jbophrase>tu'a</jbophrase> which transposes an abstract sumti into a concrete one. This is achieved at the selbri level by the cmavo
<jbophrase>jai</jbophrase> (of selma'o JAI). This cmavo has more than one function, discussed in
<xref linkend="chapter-sumti-tcita-section-jai"/> and
<xref linkend="chapter-tenses-section-jai"/>; for the purposes of this chapter, it operates as a conversion of selbri, similarly to the cmavo of selma'o SE. This conversion changes</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-jAdY">
<title>
<anchor xml:id="c11e10d7"/>
@@ -1335,21 +1335,21 @@
<title>
<anchor xml:id="c11e10d9"/>
</title>
<interlinear-gloss>
<jbo>le jai rinka be le nu do morsi</jbo>
<gloss>that-which-is associated-with causing (the event-of your death)</gloss>
<en>the one who caused your death</en>
</interlinear-gloss>
</example>
<para>because
- <jbophrase>jai</jbophrase> modifies the selbri and can be incorporated into the description - not so for
+ <jbophrase>jai</jbophrase> modifies the selbri and can be incorporated into the description – not so for
<jbophrase>tu'a</jbophrase>.</para>
<para>The weakness of
<jbophrase>jai</jbophrase> used in descriptions in this way is that it does not specify which argument of the implicit abstraction is being raised into the x1 place of the description selbri. One can be more specific by using the modal form of
<jbophrase>jai</jbophrase> explained in
<xref linkend="chapter-sumti-tcita-section-jai"/>:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-LPbo">
<title>
<anchor xml:id="c11e10d10"/>
</title>
<interlinear-gloss>
diff --git a/todocbook/12.xml b/todocbook/12.xml
index 9d202cd..37ba1e1 100644
--- a/todocbook/12.xml
+++ b/todocbook/12.xml
@@ -36,37 +36,37 @@
<jbophrase>fagyfesti</jbophrase> is derived from the tanru
<jbophrase>fagri festi</jbophrase>, it is not equivalent in meaning to it. In particular,
<jbophrase>fagyfesti</jbophrase> has a distinct place structure of its own, not the same as that of
<jbophrase>festi</jbophrase>. (In contrast, the tanru does have the same place structure as
<jbophrase>festi</jbophrase>.) The lujvo needs to take account of the places of
<jbophrase>fagri</jbophrase> as well. When a tanru is made into a lujvo, there is no equivalent of
<jbophrase>be ... bei ... be'o</jbophrase> (described in
<xref linkend="chapter-selbri-section-be-sumti"/>) to incorporate sumti into the middle of the lujvo.</para>
<para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>rationale for</secondary></indexterm> <indexterm type="general-imported"><primary>creative understanding</primary></indexterm> 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>
- <para> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>guidelines</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>guidelines for place structure</secondary></indexterm> <indexterm type="general-imported"><primary>absolute laws</primary></indexterm> <indexterm type="general-imported"><primary>alternative guidelines</primary></indexterm> 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>
+ <para> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>guidelines</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>guidelines for place structure</secondary></indexterm> <indexterm type="general-imported"><primary>absolute laws</primary></indexterm> <indexterm type="general-imported"><primary>alternative guidelines</primary></indexterm> 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>
<para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>cmavo incorporation</secondary></indexterm> If the tanru includes connective cmavo such as
<jbophrase>bo</jbophrase>,
<jbophrase>ke</jbophrase>,
<jbophrase>ke'e</jbophrase>, or
<jbophrase>je</jbophrase>, or conversion or abstraction cmavo such as
<jbophrase>se</jbophrase> or
<jbophrase>nu</jbophrase>, there are ways of incorporating them into the lujvo as well. Sometimes this makes the lujvo excessively long; if so, the cmavo may be dropped. This leads to the possibility that more than one tanru could produce the same lujvo. Typically, however, only one of the possible tanru is useful enough to justify making a lujvo for it.</para>
<para>The exact workings of the lujvo-making algorithm, which takes a tanru built from gismu (and possibly cmavo) and produces a lujvo from it, are described in
<xref linkend="chapter-morphology-section-lujvo-making"/>.</para>
</section>
<section xml:id="section-tanru-meanings">
<title>The meaning of tanru: a necessary detour</title>
- <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
+ <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
<jbophrase>veljvo</jbophrase> 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
<jbophrase>seltau</jbophrase>, and the right (modified) part the
<jbophrase>tertau</jbophrase>, following the usage of
<xref linkend="chapter-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
<jbophrase>seltau</jbophrase> and
<quote>modified</quote> for
<jbophrase>tertau</jbophrase> may help.)</para>
<para> <indexterm type="general-imported"><primary>tanru</primary><secondary>place structure of</secondary></indexterm> 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> <indexterm type="general-imported"><primary>tanru</primary><secondary>purpose</secondary></indexterm> <indexterm type="general-imported"><primary>wine-dark sea</primary></indexterm> The purpose of a tanru is to join concepts together without necessarily focusing on the exact meaning of the seltau. For example, in the
@@ -94,55 +94,55 @@
<example xml:id="example-random-id-zUVg">
<title>
<anchor xml:id="c12e2d2"/>
</title>
<para>x1 goes to destination x2 from origin point x3 via route x4 using means x5</para>
</example>
<para>The tanru
<jbophrase>klama zdani</jbophrase> will also have two places, namely those of
<jbophrase>zdani</jbophrase>. Since a
<jbophrase>klama zdani</jbophrase> is a type of
- <jbophrase>zdani</jbophrase>, we can assume that all goer-houses - whatever they may be - are also houses.</para>
+ <jbophrase>zdani</jbophrase>, we can assume that all goer-houses – whatever they may be – are also houses.</para>
<para> <indexterm type="example-imported"><primary>dog house</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>tanru</primary><secondary>possible meanings of</secondary></indexterm> <indexterm type="general-imported"><primary>fleas</primary></indexterm> But is knowing the places of the tertau everything that is needed to understand the meaning of a tanru? No. To see why, let us switch to a less unlikely tanru:
<jbophrase>gerku zdani</jbophrase>, literally
<quote>dog house</quote>. A tanru expresses a very loose relation: a
<jbophrase>gerku zdani</jbophrase> is a house that has something to do with some dog or dogs. What the precise relation might be is left unstated. Thus, the meaning of
<jbophrase>lo gerku zdani</jbophrase> can include all of the following: houses occupied by dogs, houses shaped by dogs, dogs which are also houses (e.g. houses for fleas), houses named after dogs, and so on. All that is essential is that the place structure of
<jbophrase>zdani</jbophrase> continues to apply.</para>
<para>For something (call it z1) to qualify as a
<jbophrase>gerku zdani</jbophrase> in Lojban, it's got to be a house, first of all. For it to be a house, it's got to house someone (call that z2). Furthermore, there's got to be a dog somewhere (called g1). For g1 to count as a dog in Lojban, it's got to belong to some breed as well (called g2). And finally, for z1 to be in the first place of
<jbophrase>gerku zdani</jbophrase>, as opposed to just
<jbophrase>zdani</jbophrase>, there's got to be some relationship (called r) between some place of
<jbophrase>zdani</jbophrase> and some place of
<jbophrase>gerku</jbophrase>. It doesn't matter which places, because if there's a relationship between some place of
<jbophrase>zdani</jbophrase> and any place of
<jbophrase>gerku</jbophrase>, then that relationship can be compounded with the relationship between the places of
<jbophrase>gerku</jbophrase>- namely,
- <jbophrase>gerku</jbophrase> itself - to reach any of the other
+ <jbophrase>gerku</jbophrase> itself – to reach any of the other
<jbophrase>gerku</jbophrase> places. Thus, if the relationship turns out to be between z2 and g2, we can still state r in terms of z1 and g1:
<quote>the relationship involves the dog g1, whose breed has to do with the occupant of the house z1</quote>.</para>
<para> <indexterm type="example-imported"><primary>Bill Clinton</primary><secondary>example</secondary></indexterm> Doubtless to the relief of the reader, here's an illustration. We want to find out whether the White House (the one in which the U. S. President lives, that is) counts as a
<jbophrase>gerku zdani</jbophrase>. We go through the five variables. The White House is the z1. It houses Bill Clinton as z2, as of this writing, so it counts as a
- <jbophrase>zdani</jbophrase>. Let's take a dog - say, Spot (g1). Spot has to have a breed; let's say it's a Saint Bernard (g2). Now, the White House counts as a
+ <jbophrase>zdani</jbophrase>. Let's take a dog – say, Spot (g1). Spot has to have a breed; let's say it's a Saint Bernard (g2). Now, the White House counts as a
<jbophrase>gerku zdani</jbophrase> if there is any relationship (r) at all between the White House and Spot. (We'll choose the g1 and z1 places to relate by r; we could have chosen any other pair of places, and simply gotten a different relationship.)</para>
<para> <indexterm type="general-imported"><primary>Chelsea Clinton</primary></indexterm> The sky is the limit for r; it can be as complicated as
<quote>The other day, g1 (Spot) chased Socks, who is owned by Chelsea Clinton, who is the daughter of Bill Clinton, who lives in z1 (the White House)</quote> or even worse. If no such r can be found, well, you take another dog, and keep going until no more dogs can be found. Only then can we say that the White House cannot fit into the first place of
<jbophrase>gerku zdani</jbophrase>.</para>
<para>As we have seen, no less than five elements are involved in the definition of
- <jbophrase>gerku zdani</jbophrase>: the house, the house dweller, the dog, the dog breed (everywhere a dog goes in Lojban, a dog breed follows), and the relationship between the house and the dog. Since tanru are explicitly ambiguous in Lojban, the relationship r cannot be expressed within a tanru (if it could, it wouldn't be a tanru any more!) All the other places, however, can be expressed - thus:</para>
+ <jbophrase>gerku zdani</jbophrase>: the house, the house dweller, the dog, the dog breed (everywhere a dog goes in Lojban, a dog breed follows), and the relationship between the house and the dog. Since tanru are explicitly ambiguous in Lojban, the relationship r cannot be expressed within a tanru (if it could, it wouldn't be a tanru any more!) All the other places, however, can be expressed – thus:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-tUDa">
<title>
<anchor xml:id="c12e2d3"/>
</title>
<interlinear-gloss>
<jbo>la blabi zdani cu gerku be fa la spot. bei la sankt. berNARD. be'o zdani la bil. klinton.</jbo>
<gloss>The White House is-a-dog (namely Spot of-breed Saint Bernard) type-of-house-for Bill Clinton.</gloss>
</interlinear-gloss>
</example>
@@ -151,21 +151,21 @@
<jbophrase>gerku zdani</jbophrase>, then the meaning of
<jbophrase>gerku zdani</jbophrase> changes. So if we understand
<jbophrase>gerku zdani</jbophrase> as having the same meaning as the English word
<quote>doghouse</quote>, the White House would no longer be a
<jbophrase>gerku zdani</jbophrase> with respect to Spot, because as far as we know Spot does not actually live in the White House, and the White House is not a doghouse (derogatory terms for incumbents notwithstanding).</para>
</section>
<section xml:id="section-lujvo-meanings">
<title>The meaning of lujvo</title>
<para>This is a fairly long way to go to try and work out how to say
- <quote>doghouse</quote>! The reader can take heart; we're nearly there. Recall that one of the components involved in fixing the meaning of a tanru - the one left deliberately vague - is the precise relation between the tertau and the seltau. Indeed, fixing this relation is tantamount to giving an interpretation to the ambiguous tanru.</para>
+ <quote>doghouse</quote>! The reader can take heart; we're nearly there. Recall that one of the components involved in fixing the meaning of a tanru – the one left deliberately vague – is the precise relation between the tertau and the seltau. Indeed, fixing this relation is tantamount to giving an interpretation to the ambiguous tanru.</para>
<para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>and seltau/tertau relationship</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>interpreting</secondary></indexterm> <indexterm type="general-imported"><primary>disambiguated instance</primary></indexterm> A lujvo is defined by a single disambiguated instance of a tanru. That is to say, when we try to design the place structure of a lujvo, we don't need to try to discover the relation between the tertau and the seltau. We already know what kind of relation we're looking for; it's given by the specific need we wish to express, and it determines the place structure of the lujvo itself.</para>
<para>Therefore, it is generally not appropriate to simply devise lujvo and decide on place structures for them without considering one or more specific usages for the coinage. If one does not consider specifics, one will be likely to make erroneous generalizations on the relationship r.</para>
<para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>design consideration for relationship</secondary></indexterm> The insight driving the rest of this chapter is this: while the relation expressed by a tanru can be very distant (e.g. Spot chasing Socks, above), the relationship singled out for disambiguation in a lujvo should be quite close. This is because lujvo-making, paralleling natural language compounding, picks out the most salient relationship r between a tertau place and a seltau place to be expressed in a single word. The relationship
<quote>dog chases cat owned by daughter of person living in house</quote> is too distant, and too incidental, to be likely to need expression as a single short word; the relationship
<quote>dog lives in house</quote> is not. From all the various interpretations of
<jbophrase>gerku zdani</jbophrase>, the person creating
<jbophrase>gerzda</jbophrase> should pick the most useful value of r. The most useful one is usually going to be the most obvious one, and the most obvious one is usually the closest one.</para>
<para>In fact, the relationship will almost always be so close that the predicate expressing r will be either the seltau or the tertau predicate itself. This should come as no surprise, given that a word like
<jbophrase>zdani</jbophrase> in Lojban is a predicate. Predicates express relations; so when you're looking for a relation to tie together
@@ -228,21 +228,21 @@
<para>Despite the apparently conclusive nature of
<xref linkend="example-random-id-Wx42"/>, our task is not yet done: we still need to decide whether any of the remaining places should also be eliminated, and what order the lujvo places should appear in. These concerns will be addressed in the remainder of the chapter; but we are now equipped with the terminology needed for those discussions.</para>
</section>
<section xml:id="section-selecting-places">
<title>Selecting places</title>
<para> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>basis of</secondary></indexterm> The set of places of an ordinary lujvo are selected from the places of its component gismu. More precisely, the places of such a lujvo are derived from the set of places of the component gismu by eliminating unnecessary places, until just enough places remain to give an appropriate meaning to the lujvo. In general, including a place makes the concept expressed by a lujvo more general; excluding a place makes the concept more specific, because omitting the place requires assuming a standard value or range of values for it.</para>
<para> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>rationale for standardization</secondary></indexterm> It would be possible to design the place structure of a lujvo from scratch, treating it as if it were a gismu, and working out what arguments contribute to the notion to be expressed by the lujvo. There are two reasons arguing against doing so and in favor of the procedure detailed in this chapter.</para>
<para>The first is that it might be very difficult for a hearer or reader, who has no preconceived idea of what concept the lujvo is intended to convey, to work out what the place structure actually is. Instead, he or she would have to make use of a lujvo dictionary every time a lujvo is encountered in order to work out what a
<jbophrase>se jbopli</jbophrase> or a
<jbophrase>te klagau</jbophrase> is. But this would mean that, rather than having to learn just the 1300-odd gismu place structures, a Lojbanist would also have to learn myriads of lujvo place structures with little or no apparent pattern or regularity to them. The purpose of the guidelines documented in this chapter is to apply regularity and to make it conventional wherever possible.</para>
- <para>The second reason is related to the first: if the veljvo of the lujvo has not been properly selected, and the places for the lujvo are formulated from scratch, then there is a risk that some of the places formulated may not correspond to any of the places of the gismu used in the veljvo of the lujvo. If that is the case - that is to say, if the lujvo places are not a subset of the veljvo gismu places - then it will be very difficult for the hearer or reader to understand what a particular place means, and what it is doing in that particular lujvo. This is a topic that will be further discussed in
+ <para>The second reason is related to the first: if the veljvo of the lujvo has not been properly selected, and the places for the lujvo are formulated from scratch, then there is a risk that some of the places formulated may not correspond to any of the places of the gismu used in the veljvo of the lujvo. If that is the case – that is to say, if the lujvo places are not a subset of the veljvo gismu places – then it will be very difficult for the hearer or reader to understand what a particular place means, and what it is doing in that particular lujvo. This is a topic that will be further discussed in
<xref linkend="section-anomalous-lujvo"/>.</para>
<para>However, second-guessing the place structure of the lujvo is useful in guiding the process of subsequently eliminating places from the veljvo. If the Lojbanist has an idea of what the final place structure should look like, he or she should be able to pick an appropriate veljvo to begin with, in order to express the idea, and then to decide which places are relevant or not relevant to expressing that idea.</para>
</section>
<section xml:id="section-symmetrical-asymmetrical">
<title>Symmetrical and asymmetrical lujvo</title>
<para> <indexterm type="example-imported"><primary>great soldier</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>when first places redundant</secondary></indexterm> <indexterm type="general-imported"><primary>veljvo</primary><secondary>symmetrical</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>symmetrical</secondary></indexterm> A common pattern, perhaps the most common pattern, of lujvo-making creates what is called a
<quote>symmetrical lujvo</quote>. A symmetrical lujvo is one based on a tanru interpretation such that the first place of the seltau is equivalent to the first place of the tertau: each component of the tanru characterizes the same object. As an illustration of this, consider the lujvo
<jbophrase>balsoi</jbophrase>: it is intended to mean
<quote>both great and a soldier</quote>- that is,
<quote>great soldier</quote>, which is the interpretation we would tend to give its veljvo,
@@ -375,21 +375,21 @@
<jbophrase>zdani</jbophrase>, on the other hand, there is no dependency between the places. When we know the identity of a house-dweller, we have not determined the house, because a dweller may dwell in more than one house. By the same token, when we know the identity of a house, we do not know the identity of its dweller, for a house may contain more than one dweller.</para>
<para> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>dropping dependent seltau places</secondary></indexterm> The rule for eliminating places from a lujvo is that dependent places provided by the seltau are eliminated. Therefore, in
<jbophrase>gerzda</jbophrase> the dependent g2 place is removed from the tentative place structure given in
<xref linkend="example-random-id-Wx42"/>, leaving the place structure:</para>
<example xml:id="example-random-id-zMyY">
<title>
<anchor xml:id="c12e6d1"/>
</title>
<para>z1 is the house dwelt in by dog z2=g1</para>
</example>
- <para>Informally put, the reason this has happened - and it happens a lot with seltau places - is that the third place was describing not the doghouse, but the dog who lives in it. The sentence</para>
+ <para>Informally put, the reason this has happened – and it happens a lot with seltau places – is that the third place was describing not the doghouse, but the dog who lives in it. The sentence</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-PI6B">
<title>
<anchor xml:id="c12e6d2"/>
</title>
<interlinear-gloss>
<jbo>la mon. rePOS. gerzda la spat.</jbo>
<en>Mon Repos is a doghouse of Spot.</en>
</interlinear-gloss>
</example>
@@ -855,21 +855,21 @@
<para>because the alternative,</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-xAYJ">
<title>
<anchor xml:id="c12e11d4"/>
</title>
<interlinear-gloss>
<jbo>[ke] zekri nenri [ke'e] klama</jbo>
<en>(crime inside) go</en>
</interlinear-gloss>
</example>
- <para>doesn't make much sense. (To go to the inside of a crime? To go into a place where it is criminal to be inside - an interpretation almost identical with
+ <para>doesn't make much sense. (To go to the inside of a crime? To go into a place where it is criminal to be inside – an interpretation almost identical with
<xref linkend="example-random-id-aXrm"/> anyway?)</para>
<para> <indexterm type="example-imported"><primary>shellfish</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>shellfish</primary></indexterm> There are cases, however, where omitting a KE or KEhE rafsi can produce another lujvo, equally useful. For example,
<jbophrase>xaskemcakcurnu</jbophrase> means
<quote>oceanic shellfish</quote>, and has the veljvo</para>
<para> <indexterm type="example-imported"><primary>shell worm</primary><secondary>example</secondary></indexterm> FIXME: TAG SPOT</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-0W5t">
<title>
<anchor xml:id="c12e11d5"/>
</title>
@@ -915,27 +915,23 @@
<jbophrase>selkla</jbophrase>, and the places of
<jbophrase>selkla</jbophrase> are exactly those of
<jbophrase>se klama</jbophrase>. But consider the related lujvo
<jbophrase>dzukla</jbophrase>, meaning
<quote>to walk to somewhere</quote>. It is a symmmetrical lujvo, derived from the veljvo
<jbophrase>cadzu klama</jbophrase> as follows:</para>
<example xml:id="example-random-id-4yG0">
<title>
<anchor xml:id="c12e11d7"/>
</title>
- <para>
- <jbophrase>cadzu</jbophrase>: c1 walks on surface c2 using limbs c3</para>
- <gloss>
- <jbophrase>klama</jbophrase>: k1 goes to k2 from k3 via route k4 using k5</gloss>
- <gloss>
- <jbophrase>dzukla</jbophrase>: c1=k1 walks to k2 from k3 via route k4 using limbs k5=c3</gloss>
- <para>on surface c2</para>
+ <para><jbophrase>cadzu</jbophrase>: c1 walks on surface c2 using limbs c3</para>
+ <para><jbophrase>klama</jbophrase>: k1 goes to k2 from k3 via route k4 using k5</para>
+ <para><jbophrase>dzukla</jbophrase>: c1=k1 walks to k2 from k3 via route k4 using limbs k5=c3 on surface c2</para>
</example>
<para>We can swap the k1 and k2 places using
<jbophrase>se dzukla</jbophrase>, but we cannot directly make
<jbophrase>se dzukla</jbophrase> into
<jbophrase>seldzukla</jbophrase>, which would represent the veljvo
<jbophrase>selcadzu klama</jbophrase> and plausibly mean something like
<quote>to go to a walking surface</quote>. Instead, we would need
<jbophrase>selkemdzukla</jbophrase>, with an explicit rafsi for
<jbophrase>ke</jbophrase>. Similarly,
<jbophrase>nalbrablo</jbophrase> (from
@@ -1132,42 +1128,42 @@
</example>
<para>Now we can transform the veljvo of
<jbophrase>nunctikezgau</jbophrase> into
<jbophrase>nuncti gasnu</jbophrase>. The g2 place (what is brought about by the actor g1) obviously denotes the same thing as n1 (the event of eating). So we can eliminate g2 as redundant, leaving us with a tentative place structure of</para>
<example xml:id="example-random-id-izvp">
<title>
<anchor xml:id="c12e13d3"/>
</title>
<para>g1 is the actor in the event n1=g2 of c1 eating c2</para>
</example>
- <para>But it is also possible to omit the n1 place itself! The n1 place describes the event brought about; an event in Lojban is described as a bridi, by a selbri and its sumti; the selbri is already known (it's the seltau), and the sumti are also already known (they're in the lujvo place structure). So n1 would not give us any information we didn't already know. In fact, the n1=g2 place is dependent on c1 and c2 jointly - it does not depend on either c1 or c2 by itself. Being dependent and derived from the seltau, it is omissible. So the final place structure of
+ <para>But it is also possible to omit the n1 place itself! The n1 place describes the event brought about; an event in Lojban is described as a bridi, by a selbri and its sumti; the selbri is already known (it's the seltau), and the sumti are also already known (they're in the lujvo place structure). So n1 would not give us any information we didn't already know. In fact, the n1=g2 place is dependent on c1 and c2 jointly – it does not depend on either c1 or c2 by itself. Being dependent and derived from the seltau, it is omissible. So the final place structure of
<jbophrase>nunctikezgau</jbophrase> is:</para>
<example xml:id="example-random-id-9oTP">
<title>
<anchor xml:id="c12e13d4"/>
</title>
<para>g1 is the actor in the event of c1 eating c2</para>
</example>
<para>There is one further step that can be taken. As we have already seen with
<jbophrase>balsoi</jbophrase> in
<xref linkend="section-symmetrical-asymmetrical"/>, the interpretation of lujvo is constrained by the semantics of gismu and of their sumti places. Now, any asymmetrical lujvo with
<jbophrase>gasnu</jbophrase> as its tertau will involve an event abstraction either implicitly or explicitly, since that is how the g2 place of
<jbophrase>gasnu</jbophrase> is defined.</para>
<para>Therefore, if we assume that
<jbophrase>nu</jbophrase> is the type of abstraction one would expect to be a
<jbophrase>se gasnu</jbophrase>, then the rafsi
<jbophrase role="rafsi">nun</jbophrase> and
<jbophrase role="rafsi">kez</jbophrase> in
- <jbophrase>nunctikezgau</jbophrase> are only telling us what we would already have guessed - that the seltau of a
+ <jbophrase>nunctikezgau</jbophrase> are only telling us what we would already have guessed – that the seltau of a
<jbophrase>gasnu</jbophrase> lujvo is an event. If we drop these rafsi out, and use instead the shorter lujvo
<jbophrase>ctigau</jbophrase>, rejecting its symmetrical interpretation (
<quote>someone who both does and eats</quote>;
<quote>an eating doer</quote>), we can still deduce that the seltau refers to an event.</para>
<para>(You can't
<quote>do an eater</quote>/
<jbophrase>gasnu lo citka</jbophrase>, with the meaning of
<jbophrase>do</jbophrase> as
<quote>bring about an event</quote>; so the seltau must refer to an event,
<jbophrase>nu citka</jbophrase>. The English slang meanings of
@@ -1429,21 +1425,21 @@
<jbophrase>xanplimi'e</jbophrase>,
<jbophrase>mi'erxanpli</jbophrase>, and
<jbophrase>minkemxanpli</jbophrase> respectively.</para>
<para> <indexterm type="general-imported"><primary>latent component</primary></indexterm> Does this make
<jbophrase>xanmi'e</jbophrase> wrong? By no means. But it does mean that there is a latent component to the meaning of
<jbophrase>xanmi'e</jbophrase>, the gismu
<jbophrase>pilno</jbophrase>, which is not explicit in the veljvo. And it also means that, for a place structure derivation that actually makes sense, rather than being ad-hoc, the Lojbanist should probably go through a derivation for
<jbophrase>xancypliminde</jbophrase> or one of the other possibilities that is analogous to the analysis of
<jbophrase>terlantroge'u</jbophrase> above, even if he or she decides to stick with a shorter, more convenient form like
- <jbophrase>xanmi'e</jbophrase>. In addition, of course, the possibilities of elliptical lujvo increase their potential ambiguity enormously - an unavoidable fact which should be borne in mind.</para>
+ <jbophrase>xanmi'e</jbophrase>. In addition, of course, the possibilities of elliptical lujvo increase their potential ambiguity enormously – an unavoidable fact which should be borne in mind.</para>
</section>
<section xml:id="section-comparatives">
<title>Comparatives and superlatives</title>
<para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>superlatives</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>comparatives</secondary></indexterm> English has the concepts of
<quote>comparative adjectives</quote> and
<quote>superlative adjectives</quote> which can be formed from other adjectives, either by adding the suffixes
<quote>-er</quote> and
<quote>-est</quote> or by using the words
diff --git a/todocbook/13.xml b/todocbook/13.xml
index a9f632a..f526842 100644
--- a/todocbook/13.xml
+++ b/todocbook/13.xml
@@ -291,21 +291,21 @@
<interlinear-gloss>
<jbo>.uenai la djan. klama</jbo>
<gloss>[Expected!] John comes.</gloss>
</interlinear-gloss>
</example>
<para>In
<xref linkend="example-random-id-qfin"/>, John's coming has been anticipated by the speaker. In
<xref linkend="example-random-id-qFiE"/> and
<xref linkend="example-random-id-qfiI"/>, no such anticipation has been made, but in
- <xref linkend="example-random-id-qfiI"/> the lack-of-anticipation goes no further - in
+ <xref linkend="example-random-id-qfiI"/> the lack-of-anticipation goes no further – in
<xref linkend="example-random-id-qFiE"/>, it amounts to actual surprise.</para>
<para>It is not possible to firmly distinguish the pure emotion words beginning with
<jbophrase role="letteral">o</jbophrase> or
<jbophrase role="letteral">i</jbophrase> from those beginning with
<jbophrase role="letteral">u</jbophrase>, but in general they represent more complex, more ambivalent, or more difficult emotions.</para>
<cmavo-list>
<cmavo-entry>
<cmavo>.o'a</cmavo>
<attitudinal-scale point="sai">pride</attitudinal-scale>
<attitudinal-scale point="cu'i">modesty</attitudinal-scale>
@@ -935,21 +935,21 @@
</interlinear-gloss>
</example>
<example xml:id="example-random-id-qfvL" role="interlinear-gloss-example">
<title>
<anchor xml:id="c13e4d4"/>
</title>
<interlinear-gloss>
<jbo>.eiru'e</jbo>
- <en>I might (a weak obligation - in English often mixed with permission and desire)</en>
+ <en>I might (a weak obligation – in English often mixed with permission and desire)</en>
</interlinear-gloss>
</example>
<example xml:id="example-random-id-qfvn" role="interlinear-gloss-example">
<title>
<anchor xml:id="c13e4d5"/>
</title>
<interlinear-gloss>
<jbo>.eicu'i</jbo>
@@ -969,35 +969,35 @@
<para> <indexterm type="lojban-word-imported"><primary>.einai</primary></indexterm> <indexterm type="lojban-word-imported"><primary>.eicu'i</primary></indexterm> <indexterm type="lojban-word-imported"><primary>.eiru'e</primary></indexterm> <indexterm type="lojban-word-imported"><primary>.eisai</primary></indexterm> <indexterm type="lojban-word-imported"><primary>.eicai</primary></indexterm> <indexterm type="lojban-word-imported"><primary>.ei</primary></indexterm> <indexterm type="example-imported"><primary>formal requirement</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>attitudinal scale</primary><secondary>stand-alone usage</secondary></indexterm> You can also utter a scale indicator without a specific emotion. This is often used in the language: in order to emphasize a point about which you feel strongly, you mark what you are saying with the scale indicator
<jbophrase>cai</jbophrase>. You could also indicate that you don't care using
<jbophrase>cu'i</jbophrase> by itself.</para>
</section>
<section xml:id="section-attitudinal-space">
<title>The space of emotions</title>
<para> <indexterm type="general-imported"><primary>attitudinal scale</primary><secondary>as axis in emotion-space</secondary></indexterm> Each of the attitude scales constitutes an axis in a multi-dimensional space. In effect, given our total so far of 39 scales, we have a 39-dimensional space. At any given time, our emotions and attitudes are represented by a point in this 39-dimensional space, with the intensity indicators serving as coordinates along each dimension. A complete attitudinal inventory, should one decide to express it, would consist of reading off each of the scale values for each of the emotions, with the vector sum serving as a distinct single point, which is our attitude.</para>
- <para> <indexterm type="general-imported"><primary>emotions</primary><secondary>when expressed</secondary></indexterm> <indexterm type="general-imported"><primary>emotions</primary><secondary>insights</secondary></indexterm> <indexterm type="general-imported"><primary>emotions</primary><secondary>compound</secondary></indexterm> <indexterm type="general-imported"><primary>compound emotions</primary></indexterm> Now no one is going to ever utter a string of 100-odd attitudinals to express their emotions. If asked, we normally do not recognize more than one or two emotions at a time - usually the ones that are strongest or which most recently changed in some significant way. But the scale system provides some useful insights into a possible theory of emotion (which might be testable using Lojban), and incidentally explains how Lojbanists express compound emotions when they do recognize them.</para>
+ <para> <indexterm type="general-imported"><primary>emotions</primary><secondary>when expressed</secondary></indexterm> <indexterm type="general-imported"><primary>emotions</primary><secondary>insights</secondary></indexterm> <indexterm type="general-imported"><primary>emotions</primary><secondary>compound</secondary></indexterm> <indexterm type="general-imported"><primary>compound emotions</primary></indexterm> Now no one is going to ever utter a string of 100-odd attitudinals to express their emotions. If asked, we normally do not recognize more than one or two emotions at a time – usually the ones that are strongest or which most recently changed in some significant way. But the scale system provides some useful insights into a possible theory of emotion (which might be testable using Lojban), and incidentally explains how Lojbanists express compound emotions when they do recognize them.</para>
<para> <indexterm type="general-imported"><primary>attitudinal scale</primary><secondary>neutral compared with positive + negative</secondary></indexterm> The existence of 39 scales highlights the complexity of emotion. We also aren't bound to the 39. There are modifiers described in
<xref linkend="section-categories"/> that multiply the set of scales by an order of magnitude. You can also have mixed feelings on a scale, which might be expressed by
<jbophrase>cu'i</jbophrase>, but could also be expressed by using both the
<quote>positive</quote> and
<quote>negative</quote> scale emotions at once. One expression of
<quote>fortitude</quote> might be
<jbophrase>.ii.iinai</jbophrase>- fear coupled with security.</para>
- <para> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>contrasted with rationalizations of emotion</secondary></indexterm> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>order of</secondary></indexterm> Uttering one or more attitudinals to express an emotion reflects several things. We will tend to utter emotions in their immediate order of importance to us. We feel several emotions at once, and our expression reflects these emotions simultaneously, although their order of importance to us is also revealing - of our attitude towards our attitude, so to speak. There is little analysis necessary; for those emotions you feel, you express them; the
- <quote>vector sum</quote> naturally expresses the result. This is vital to their nature as attitudinals - if you had to stop and think about them, or to worry about grammar, they wouldn't be emotions but rationalizations.</para>
- <para> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>contrasted with bridi</secondary></indexterm> People have proposed that attitudinals be expressed as bridi just like everything else; but emotions aren't logical or analytical - saying
+ <para> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>contrasted with rationalizations of emotion</secondary></indexterm> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>order of</secondary></indexterm> Uttering one or more attitudinals to express an emotion reflects several things. We will tend to utter emotions in their immediate order of importance to us. We feel several emotions at once, and our expression reflects these emotions simultaneously, although their order of importance to us is also revealing – of our attitude towards our attitude, so to speak. There is little analysis necessary; for those emotions you feel, you express them; the
+ <quote>vector sum</quote> naturally expresses the result. This is vital to their nature as attitudinals – if you had to stop and think about them, or to worry about grammar, they wouldn't be emotions but rationalizations.</para>
+ <para> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>contrasted with bridi</secondary></indexterm> People have proposed that attitudinals be expressed as bridi just like everything else; but emotions aren't logical or analytical – saying
<quote>I'm awed</quote> is not the same as saying
<quote>Wow!!!</quote>. The Lojban system is intended to give the effects of an analytical system without the thought involved. Thus, you can simply feel in Lojban.</para>
<para> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>design benefit</secondary></indexterm> A nice feature of this design is that you can be simple or complex, and the system works the same way. The most immediate benefit is in learning. You only need to learn a couple of the scale words and a couple of attitude words, and you're ready to express your emotions Lojbanically. As you learn more, you can express your emotions more thoroughly and more precisely, but even a limited vocabulary offers a broad range of expression.</para>
</section>
<section xml:id="section-categories">
<title>Emotional categories</title>
<para> <indexterm type="general-imported"><primary>attitudinal categories</primary><secondary>rationale</secondary></indexterm> <indexterm type="general-imported"><primary>attitudinal categories</primary></indexterm> <indexterm type="general-imported"><primary>emotional categories</primary></indexterm> The Lojban attitudinal system was designed by starting with a long list of English emotion words, far too many to fit into the 39 available VV-form cmavo. To keep the number of cmavo limited, the emotion words in the list were grouped together by common features: each group was then assigned a separate cmavo. This was like making tanru in reverse, and the result is a collection of indicators that can be combined, like tanru, to express very complex emotions. Some examples in a moment.</para>
<para>The most significant
<quote>common feature</quote> we identified was that the emotional words on the list could easily be broken down into six major groups, each of which was assigned its own cmavo:</para>
<cmavo-list>
@@ -1053,21 +1053,21 @@
<jbophrase>.o'unairo'a</jbophrase>. Some emotions that we label
<quote>stress</quote> in English are expressed in Lojban with
<jbophrase>.o'unairo'i</jbophrase>. Physical distress can be expressed with
<jbophrase>.o'unairo'o</jbophrase>, which makes a nice groan if you say it with feeling. Mental discomfort might be what you feel when you don't know the answer to the test question, but feel that you should. Most adults can recall some instance where we felt sexual discomfort,
<jbophrase>o'unairo'u</jbophrase>. Spiritual discomfort,
<jbophrase>o'unaire'e</jbophrase>, might be felt by a church-goer who has wandered into the wrong kind of religious building.</para>
<para>Most of the time when expressing an emotion, you won't categorize it with these words. Emotional expressions should be quickly expressible without having to think about them. However, we sometimes have mixed emotions within this set, as for example emotional discomfort coupled with physical comfort or vice versa.</para>
<para> <indexterm type="lojban-word-imported"><primary>.eiro'u</primary></indexterm> Coupling these six words with our 39 attitude scales, each of which has a positive and negative side, already gives you far more emotional expression words than we have emotional labels in English. Thus, you'll never see a Lojban-English emotional dictionary that covers all the Lojban possibilities. Some may be useless, but others convey emotions that probably never had a word for them before, though many have felt them (
- <jbophrase>.eiro'u</jbophrase>, for example - look it up).</para>
+ <jbophrase>.eiro'u</jbophrase>, for example – look it up).</para>
<para> <indexterm type="example-imported"><primary>ro'anai</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>stand-alone categories</secondary></indexterm> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>categories with nai</secondary></indexterm> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>categories with scale markers</secondary></indexterm> You can use scale markers and
<jbophrase>nai</jbophrase> on these six category words, and you can also use category words without specifying the emotion. Thus,
<quote>I'm trying to concentrate</quote> could be expressed simply as
<jbophrase>ro'e</jbophrase>, and if you are feeling anti-social in some non-specific way,
<jbophrase>ro'anai</jbophrase> will express it.</para>
<para> <indexterm type="general-imported"><primary>attitudinal categories</primary><secondary>mnemonic for</secondary></indexterm> There is a mnemonic device for the six emotion categories, based on moving your arms about. In the following table, your hands begin above your head and move down your body in sequence.</para>
<cmavo-list>
@@ -1261,21 +1261,21 @@
<jbophrase>ro'ole'o</jbophrase>.
<jbophrase>le'o</jbophrase> is also useful in threats as an alternative to
<jbophrase>o'onai</jbophrase>, which expresses anger.</para>
<para> <indexterm type="lojban-word-imported"><primary>vu'e</primary></indexterm> <indexterm type="example-imported"><primary>sinful</primary><secondary>example</secondary></indexterm> <indexterm type="example-imported"><primary>virtue</primary><secondary>example</secondary></indexterm> <indexterm type="example-imported"><primary>righteous indignation</primary><secondary>example</secondary></indexterm> The cmavo
<jbophrase>vu'e</jbophrase> represents ethical virtue or its absence. An excess of almost any emotion is usually somewhat
- <quote>sinful</quote> in the eyes of most ethical systems. On the other hand, we often feel virtuous about our feelings - what we call righteous indignation might be
+ <quote>sinful</quote> in the eyes of most ethical systems. On the other hand, we often feel virtuous about our feelings – what we call righteous indignation might be
<jbophrase>o'onaivu'e</jbophrase>. Note that this is distinct from lack of guilt:
<jbophrase>.u'unai</jbophrase>.</para>
<para> <indexterm type="lojban-word-imported"><primary>se'i</primary></indexterm> The cmavo
<jbophrase>se'i</jbophrase> expresses the difference between selfishness and generosity, for example (in combination with
<jbophrase role="diphthong">.au</jbophrase>):</para>
<example xml:id="example-random-id-qFxm" role="interlinear-gloss-example">
@@ -1353,21 +1353,21 @@
<jbophrase>be'u</jbophrase> can be used alone:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-U3zm">
<title>
<anchor xml:id="c13e7d9"/>
</title>
<interlinear-gloss>
<jbo>le cukta be'u cu zvati ma</jbo>
<gloss>The book [Needed!] is at-location [what sumti?]</gloss>
- <gloss>Where's the book? - I need it!</gloss>
+ <gloss>Where's the book? – I need it!</gloss>
</interlinear-gloss>
</example>
<para> <indexterm type="lojban-word-imported"><primary>se'a</primary></indexterm> Lastly, the modifier
<jbophrase>se'a</jbophrase> shows whether the feeling is associated with self-sufficiency or with dependence on others.</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-4S14">
<title>
<anchor xml:id="c13e7d10"/>
</title>
<interlinear-gloss>
@@ -1431,21 +1431,21 @@
<jbophrase>.ie ge'eru'e</jbophrase> might be
<quote>I agree, but ...</quote> where the
<quote>but</quote> is left hanging. (Again, attitudes aren't always expressed in English by English attitudinals.)</para>
<para> <indexterm type="general-imported"><primary>attitudinal indicators</primary><secondary>placement of scale in</secondary></indexterm> A scale variable similarly modifies the previous emotion word. You put the scale word for a root emotion word before a modifier, since the latter can have its own scale word. This merely maximizes the amount of information expressible. For example,
<jbophrase>.oinaicu'i ro'ucai</jbophrase> expresses a feeling midway between pain (
<jbophrase role="diphthong">.oi</jbophrase>) and pleasure (
<jbophrase>.oinai</jbophrase>) which is intensely sexual (
<jbophrase>ro'u</jbophrase>) in nature.</para>
<para> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>placement in sentences with "nai"</secondary></indexterm> <indexterm type="general-imported"><primary>attitudinal indicators</primary><secondary>placement of "nai" in</secondary></indexterm> The cmavo
- <jbophrase>nai</jbophrase> is the most tightly bound modifier in the language: it always negates exactly one word - the preceding one. Of all the words used in indicator constructs,
+ <jbophrase>nai</jbophrase> is the most tightly bound modifier in the language: it always negates exactly one word – the preceding one. Of all the words used in indicator constructs,
<jbophrase>nai</jbophrase> is the only one with any meaning outside the indicator system. If you try to put an indicator between a non-indicator cmavo and its
<jbophrase>nai</jbophrase> negator, the
<jbophrase>nai</jbophrase> will end up negating the last word of the indicator. The result, though unambiguous, is not what you want. For example,</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-9BBA">
<title>
<anchor xml:id="c13e8d1"/>
</title>
<interlinear-gloss>
<jbo>mi .e .ui nai do</jbo>
<gloss>I and [Yay!] [Not!] you</gloss>
@@ -1511,21 +1511,21 @@
</title>
<interlinear-gloss>
<jbo>mi pu tavla do .o'onai .oi</jbo>
<gloss>I [past] talk-to you [Grrr!] [Oy!]</gloss>
</interlinear-gloss>
</example>
<para>can be interpreted as expressing complaint about the anger, in which case it means
<quote>Damn, I snapped at you</quote>; or as expressing both anger and complaint about the listener, in which case it means
<quote>I told you, you pest!</quote></para>
- <para>Similarly, an indicator after the final brivla of a tanru may be taken to express an attitude about the particular brivla placed there - as the rules have it - or about the entire bridi which hinges on that brivla. Remembering that indicators are supposedly direct expressions of emotion, this ambiguity is acceptable.</para>
+ <para>Similarly, an indicator after the final brivla of a tanru may be taken to express an attitude about the particular brivla placed there – as the rules have it – or about the entire bridi which hinges on that brivla. Remembering that indicators are supposedly direct expressions of emotion, this ambiguity is acceptable.</para>
<para> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>benefit in written expression</secondary></indexterm> Even if the scope rules given for indicators turn out to be impractical or unintuitive for use in conversation, they are still useful in written expression. There, where you can go back and put in markers or move words around, the scope rules can be used in lieu of elaborate nuances of body language and intonation to convey the writer's intent.</para>
</section>
<section xml:id="section-questions-empathy-contours">
<title>Attitude questions; empathy; attitude contours</title>
<para>The following cmavo are discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>pei</cmavo>
<attitudinal-scale point="sai">attitude question</attitudinal-scale>
@@ -1543,25 +1543,25 @@
<attitudinal-scale point="nai">end emotion</attitudinal-scale>
</cmavo-entry>
</cmavo-list>
<para>You can ask someone how they are feeling with a normal bridi sentence, but you will get a normal bridi answer in response, one which may be true or false. Since the response to a question about emotions is no more logical than the emotion itself, this isn't appropriate.</para>
<para> <indexterm type="lojban-word-imported"><primary>pei</primary></indexterm> <indexterm type="general-imported"><primary>attitudinal questions</primary></indexterm> The word
<jbophrase>pei</jbophrase> is therefore reserved for attitude questions. Asked by itself, it captures all of the denotation of English
<quote>How are you?</quote> coupled with
<quote>How do you feel?</quote> (which has a slightly different range of usage).</para>
<para> <indexterm type="general-imported"><primary>attitudinal answers</primary><secondary>plausibility</secondary></indexterm> When asked in the context of discourse,
- <jbophrase>pei</jbophrase> acts like other Lojban question words - it requests the respondent to
+ <jbophrase>pei</jbophrase> acts like other Lojban question words – it requests the respondent to
<quote>fill in the blank</quote>, in this case with an appropriate attitudinal describing the respondent's feeling about the referent expression. As with other questions, plausibility is polite; if you answer with an irrelevant UI cmavo, such as a discursive, you are probably making fun of the questioner. (A
- <jbophrase>ge'e</jbophrase>, however, is always in order - you are not required to answer emotionally. This is not the same as
+ <jbophrase>ge'e</jbophrase>, however, is always in order – you are not required to answer emotionally. This is not the same as
<jbophrase>.i'inai</jbophrase>, which is privacy as the reverse of conviviality.)</para>
<para> <indexterm type="general-imported"><primary>attitudinal questions</primary><secondary>asking intensity</secondary></indexterm> Most often, however, the asker will use
<jbophrase>pei</jbophrase> as a place holder for an intensity marker. (As a result,
<jbophrase>pei</jbophrase> is placed in selma'o CAI, although selma'o UI would have been almost as appropriate. Grammatically, there is no difference between UI and CAI.) Such usage corresponds to a whole range of idiomatic usages in natural languages:</para>
<example xml:id="example-random-id-qfXT" role="interlinear-gloss-example">
<title>
<anchor xml:id="c13e10d1"/>
</title>
<interlinear-gloss>
@@ -1647,21 +1647,21 @@
</interlinear-gloss>
</example>
<para> <indexterm type="lojban-word-imported"><primary>.uuse'inai</primary></indexterm> <indexterm type="lojban-word-imported"><primary>dai</primary></indexterm> <indexterm type="example-imported"><primary>sympathy</primary><secondary>example</secondary></indexterm> <indexterm type="example-imported"><primary>empathy</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>attitudes</primary><secondary>empathy contrasted with sympathy</secondary></indexterm> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>attributing emotion to others</secondary></indexterm> Empathy, which is not really an emotion, is expressed by the indicator
<jbophrase>dai</jbophrase>. (Don't confuse empathy with sympathy, which is
<jbophrase>.uuse'inai</jbophrase>.) Sometimes, as when telling a story, you want to attribute emotion to someone else. You can of course make a bridi claim that so-and-so felt such-and-such an emotion, but you can also make use of the attitudinal system by adding the indicator
- <jbophrase>dai</jbophrase>, which attributes the preceding attitudinal to someone else - exactly whom, must be determined from context. You can also use
+ <jbophrase>dai</jbophrase>, which attributes the preceding attitudinal to someone else – exactly whom, must be determined from context. You can also use
<jbophrase>dai</jbophrase> conversationally when you empathize, or feel someone else's emotion as if it were your own:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-Ny8w">
<title>
<anchor xml:id="c13e10d9"/>
</title>
<interlinear-gloss>
<jbo>.oiro'odai</jbo>
<gloss>[Pain!] [physical] [empathy]</gloss>
@@ -1904,21 +1904,21 @@
<anchor xml:id="c13e11d3"/>
</title>
<interlinear-gloss>
<jbo>ti'e la .uengas cu zergau</jbo>
<gloss>[I hear!] Wenga is-a-criminal-doer.</gloss>
<en>I hear that Wenga is a crook.</en>
</interlinear-gloss>
</example>
<para> <indexterm type="lojban-word-imported"><primary>ka'u</primary></indexterm> <indexterm type="example-imported"><primary>cultural knowledge</primary><secondary>example</secondary></indexterm> <indexterm type="example-imported"><primary>myth</primary><secondary>example</secondary></indexterm> A bridi marked by
- <jbophrase>ka'u</jbophrase> is one held to be true in the speaker's cultural context, as a matter of myth or custom, for example. Such statements should be agreed on by a community of people - you cannot just make up your own cultural context - although
+ <jbophrase>ka'u</jbophrase> is one held to be true in the speaker's cultural context, as a matter of myth or custom, for example. Such statements should be agreed on by a community of people – you cannot just make up your own cultural context – although
<quote>objectivity</quote> in the sense of actual correspondence with the facts is certainly not required.</para>
<para> <indexterm type="lojban-word-imported"><primary>ka'u</primary></indexterm> <indexterm type="lojban-word-imported"><primary>se'o</primary></indexterm> <indexterm type="example-imported"><primary>dream</primary><secondary>example</secondary></indexterm> <indexterm type="example-imported"><primary>revelation</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>evidentials</primary><secondary>ka'u contrasted with se'o</secondary></indexterm> <indexterm type="general-imported"><primary>evidentials</primary><secondary>se'o contrasted with ka'u</secondary></indexterm> On the other hand,
<jbophrase>se'o</jbophrase> marks a bridi whose truth is asserted by the speaker as a result of an internal experience not directly available to others, such as a dream, vision, or personal revelation. In some cultures, the line between
<jbophrase>ka'u</jbophrase> and
<jbophrase>se'o</jbophrase> is fuzzy or even nonexistent.</para>
<para> <indexterm type="lojban-word-imported"><primary>za'a</primary></indexterm> <indexterm type="example-imported"><primary>observation</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>observation evidential</primary><secondary>contrasted with observative </secondary></indexterm> <indexterm type="general-imported"><primary>observative</primary><secondary>contrasted with observation evidential</secondary></indexterm> A bridi marked by
<jbophrase>za'a</jbophrase> is based on perception or direct observation by the speaker. This use of
@@ -2229,21 +2229,21 @@
<quote>broadly construed</quote>; for
<jbophrase>do'anai</jbophrase> (as you might expect),
<quote>narrowly construed</quote>.</para>
<para> <indexterm type="lojban-word-imported"><primary>pa'enai</primary></indexterm> <indexterm type="lojban-word-imported"><primary>pa'e</primary></indexterm> The cmavo
<jbophrase>pa'e</jbophrase> is used to claim (truly or falsely) that one is being fair or just to all parties mentioned, whereas
<jbophrase>pa'enai</jbophrase> admits (or proclaims) a bias in favor of one party.</para>
<para> <indexterm type="lojban-word-imported"><primary>.ianai</primary></indexterm> <indexterm type="lojban-word-imported"><primary>zo'o</primary></indexterm> <indexterm type="example-imported"><primary>irony</primary><secondary>example</secondary></indexterm> <indexterm type="example-imported"><primary>sarcasm</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>irony</primary><secondary>expressing</secondary></indexterm> <indexterm type="general-imported"><primary>sarcasm</primary><secondary>expressing</secondary></indexterm> The scale of
<jbophrase>je'u</jbophrase> and
- <jbophrase>je'unai</jbophrase> is a little different from the others in the group. By default, we assume that people speak the truth - or at least, that if they are lying, they will do their best to conceal it from us. So under what circumstances would
+ <jbophrase>je'unai</jbophrase> is a little different from the others in the group. By default, we assume that people speak the truth – or at least, that if they are lying, they will do their best to conceal it from us. So under what circumstances would
<jbophrase>je'unai</jbophrase> be used, or
<jbophrase>je'u</jbophrase> be useful? For one thing,
<jbophrase>je'u</jbophrase> can be used to mark a tautology: a sentence that is a truth of logic, like
<quote>All cats are cats.</quote> Its counterpart
<jbophrase>je'unai</jbophrase> then serves to mark a logical contradiction. In addition,
<jbophrase>je'unai</jbophrase> can be used to express one kind of sarcasm or irony, where the speaker pretends to believe what he/she says, but actually wishes the listener to infer a contrary opinion. Other forms of irony can be marked with
<jbophrase>zo'o</jbophrase> (humor) or
@@ -2641,37 +2641,37 @@
<en>I know who goes to the store.</en>
</interlinear-gloss>
</example>
</section>
<section xml:id="section-vocatives">
<title>Vocative scales</title>
<para> <indexterm type="lojban-word-imported"><primary>COI selma'o</primary></indexterm> <indexterm type="general-imported"><primary>direct address</primary></indexterm> <indexterm type="general-imported"><primary>"la"</primary><secondary>contrasted with vocatives</secondary></indexterm> <indexterm type="general-imported"><primary>vocatives</primary><secondary>contrasted with "la"</secondary></indexterm> <indexterm type="general-imported"><primary>vocatives</primary><secondary>definition</secondary></indexterm>
<quote>Vocatives</quote> are words used to address someone directly; they precede and mark a name used in direct address, just as
- <jbophrase>la</jbophrase> (and the other members of selma'o LA) mark a name used to refer to someone. The vocatives actually are indicators - in fact, discursives - but the need to tie them to names and other descriptions of listeners requires them to be separated from selma'o UI. But like the cmavo of UI, the members of selma'o COI can be
+ <jbophrase>la</jbophrase> (and the other members of selma'o LA) mark a name used to refer to someone. The vocatives actually are indicators – in fact, discursives – but the need to tie them to names and other descriptions of listeners requires them to be separated from selma'o UI. But like the cmavo of UI, the members of selma'o COI can be
<quote>negated</quote> with
<jbophrase>nai</jbophrase> to get the opposite part of the scale.</para>
<para> <indexterm type="general-imported"><primary>vocatives</primary><secondary>rationale for redundancy</secondary></indexterm> <indexterm type="general-imported"><primary>redundancy</primary><secondary>effect on vocative design</secondary></indexterm> Because of the need for redundancy in noisy environments, the Lojban design does not compress the vocatives into a minimum number of scales. Doing so would make a non-redundant
<jbophrase>nai</jbophrase> too often vital to interpretation of a protocol signal, as explained later in this section.</para>
<para> <indexterm type="lojban-word-imported"><primary>do'u</primary></indexterm> <indexterm type="lojban-word-imported"><primary>DOhU selma'o</primary></indexterm> <indexterm type="general-imported"><primary>vocatives</primary><secondary>grammar overview</secondary></indexterm> The grammar of vocatives is explained in
<xref linkend="chapter-sumti-section-vocatives"/>; but in brief, a vocative may be followed by a name (without
<jbophrase>la</jbophrase>), a description (without
<jbophrase>le</jbophrase> or its relatives), a complete sumti, or nothing at all (if the addressee is obvious from the context). There is an elidable terminator,
<jbophrase>do'u</jbophrase> (of selma'o DOhU) which is almost never required unless no name (or other indication of the addressee) follows the vocative.</para>
<para> <indexterm type="general-imported"><primary>vocatives</primary><secondary>and definition of "you"</secondary></indexterm> <indexterm type="general-imported"><primary>you</primary><secondary>defining</secondary></indexterm> Using any vocative except
<jbophrase>mi'e</jbophrase> (explained below) implicitly defines the meaning of the pro-sumti
- <jbophrase>do</jbophrase>, as the whole point of vocatives is to specify the listener, or at any rate the desired listener - even if the desired listener isn't listening! We will use the terms
+ <jbophrase>do</jbophrase>, as the whole point of vocatives is to specify the listener, or at any rate the desired listener – even if the desired listener isn't listening! We will use the terms
<quote>speaker</quote> and
<quote>listener</quote> for clarity, although in written Lojban the appropriate terms would be
<quote>writer</quote> and
<quote>reader</quote>.</para>
<para> <indexterm type="general-imported"><primary>vocatives</primary><secondary>notation convention symbol "X"</secondary></indexterm> In the following list of vocatives, the translations include the symbol X. This represents the name (or identifying description, or whatever) of the listener.</para>
<para> <indexterm type="lojban-word-imported"><primary>DOI selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>doi</primary></indexterm> <indexterm type="general-imported"><primary>doi</primary><secondary>effect on pause before name</secondary></indexterm> <indexterm type="general-imported"><primary>pause before name</primary><secondary>effect of doi</secondary></indexterm> The cmavo
<jbophrase>doi</jbophrase> is the general-purpose vocative. Unlike the cmavo of selma'o COI, explained below,
<jbophrase>doi</jbophrase> can precede a name directly without an intervening pause. It is not considered a scale, and
<jbophrase>doinai</jbophrase> is not grammatical. In general,
<jbophrase>doi</jbophrase> needs no translation in English (we just use names by themselves without any preceding word, although in poetic styles we sometimes say
@@ -3240,21 +3240,21 @@
<para> <indexterm type="general-imported"><primary>indicators</primary><secondary>rationale for selection</secondary></indexterm> We have tried to err on the side of overkill. There are distinctions possible in this system that no one may care to make in any culture. But it was deemed more neutral to overspecify and let usage decide, than to choose a limited set and constrain emotional expression. For circumstances in which even the current indicator set is not enough, it is possible using the cmavo
<jbophrase>sei</jbophrase>, explained in
<xref linkend="chapter-structure-section-parentheses"/>, to create metalinguistic comments that act like indicators.</para>
<para> <indexterm type="general-imported"><primary>indicators</primary><secondary>evolutionary development of</secondary></indexterm> We envision an evolutionary development. At this point, the system is little more than a mental toy. Many of you who read this will try playing around with various combinations of indicators, trying to figure out what emotions they express and when the expressions might be useful. You may even find an expression for which there currently is no good English word and start using it. Why not, if it helps you express your feelings?</para>
<para>There will be a couple dozen of these used pretty much universally – mostly just simple attitudinals with, at most, intensity markers. These are the ones that will quickly be expressed at the subconscious level. But every Lojbanist who plays with the list will bring in a couple of new words. Poets will paint emotional pictures, and people who identify with those pictures will use the words so created for their own experiences.</para>
- <para>Just as a library of tanru is built up, so will a library of attitudes be built. Unlike the tanru, though, the emotional expressions are built on some fairly nebulous root emotions - words that cannot be defined with the precision of the gismu. The emotion words of Lojban will very quickly take on a life of their own, and the outline given here will evolve into a true system of emotions.</para>
+ <para>Just as a library of tanru is built up, so will a library of attitudes be built. Unlike the tanru, though, the emotional expressions are built on some fairly nebulous root emotions – words that cannot be defined with the precision of the gismu. The emotion words of Lojban will very quickly take on a life of their own, and the outline given here will evolve into a true system of emotions.</para>
<para> <indexterm type="general-imported"><primary>emotions</primary><secondary>research using indicators</secondary></indexterm> <indexterm type="general-imported"><primary>emotions</primary><secondary>recording using indicators</secondary></indexterm> There are several theories as to the nature of emotion, and they change from year to year as we learn more about ourselves. Whether or not Lojban's additive/scalar emotional model is an accurate model for human emotions, it does support the linguistic needs for expressing those emotions. Researchers may learn more about the nature of human emotions by exploring the use of the system by Lojban speakers. They also may be able to use the Lojban system as a means for more clearly recording emotions.</para>
- <para> <indexterm type="general-imported"><primary>emotions</primary><secondary>cultural bias of expression</secondary></indexterm> The full list of scales and attitudes will probably not be used until someone speaks the language from birth. Until then, people will use the attitudes that are important to them. In this way, we counter cultural bias - if a culture is prone to recognizing and/or expressing certain emotions more than others, its members will use only those out of the enormous set available. If a culture hides certain emotions, its members simply won't express them.</para>
+ <para> <indexterm type="general-imported"><primary>emotions</primary><secondary>cultural bias of expression</secondary></indexterm> The full list of scales and attitudes will probably not be used until someone speaks the language from birth. Until then, people will use the attitudes that are important to them. In this way, we counter cultural bias – if a culture is prone to recognizing and/or expressing certain emotions more than others, its members will use only those out of the enormous set available. If a culture hides certain emotions, its members simply won't express them.</para>
<para> <indexterm type="general-imported"><primary>Sapir-Whorf effects</primary><secondary>and emotional indicators</secondary></indexterm> Perhaps native Lojban speakers will be more expressively clear about their emotions than others. Perhaps they will feel some emotions more strongly than others in ways that can be correlated with the word choices; any difference from the norms of other cultures could be significant. Psychologists have devised elaborate tests for measuring attitudes and personality; this may be the easiest area in which to detect any systematic cultural effect of the type sought to confirm Sapir-Whorf, simply because we already have tools in existence to test it. Because Lojban is unique among languages in having such extensive and expressive indicators, it is likely that a Sapir-Whorf effect will occur and will be recognized.</para>
<para>It is unlikely that we will know the true potential of a system like this one until and unless we have children raised entirely in a multi-cultural Lojban-speaking environment. We learn too many cultural habits in the realm of emotional communication
<quote>at our mother's knee</quote>. Such children will have a Lojban system that has stronger reinforcement than any typical culture system. The second generation of such children, then, could be said to be the start of a true Lojbanic culture.</para>
<para> <indexterm type="general-imported"><primary>emotional indicators</primary><secondary>noticeable effects of</secondary></indexterm> We shouldn't need to wait that long to detect significant effects. Emotion is so basic to our lives that even a small change or improvement in emotional communication would have immediately noticeable effects. Perhaps it will be the case that the most important contribution of our
<quote>logical language</quote> will be in the non-logical realm of emotion!</para>
</section>
</chapter>
diff --git a/todocbook/14.xml b/todocbook/14.xml
index 5ff8c5b..df53f1d 100644
--- a/todocbook/14.xml
+++ b/todocbook/14.xml
@@ -794,21 +794,21 @@
<anchor xml:id="c14e7d3"/>
</title>
<interlinear-gloss>
<jbo>mi dotco .ijo mi ricfu .ijo mi nanmu</jbo>
<gloss>I am-German. If-and-only-if I am-rich. If-and-only-if I am-a-man.</gloss>
</interlinear-gloss>
</example>
<para>shows that
<xref linkend="example-random-id-3zE1"/> does not mean that either I am all three of these things or none of them; instead, an accurate translation would be:</para>
<place-structure>
- Of the three properties - German-ness, wealth, and manhood - I possess either exactly one or else all three.
+ Of the three properties – German-ness, wealth, and manhood – I possess either exactly one or else all three.
</place-structure>
<para> <indexterm type="general-imported"><primary>logical connection</primary><secondary>negation in connecting more than 2 sentences</secondary></indexterm> <indexterm type="general-imported"><primary>logical connection</primary><secondary>of more than 2 sentences</secondary><tertiary>things to avoid</tertiary></indexterm> Because of the counterintuitiveness of this outcome, it is safest to avoid
<phrase role="logical-vowel">O</phrase> with more than two sentences. Likewise, the connectives which involve negation also have unexpected truth values when used with more than two sentences.</para>
<para> <indexterm type="general-imported"><primary>logical connection</primary><secondary>of more than 2 sentences</secondary><tertiary>all or none</tertiary></indexterm> In fact, no combination of logical connectives can produce the
<quote>all or none</quote> interpretation intended (but not achieved) by
<xref linkend="example-random-id-3zE1"/> without repeating one of the bridi. See
<xref linkend="example-random-id-KyHw"/>.</para>
<para>There is an additional difficulty with the use of more than two sentences. What is the meaning of:</para>
<para> <indexterm type="general-imported"><primary>logical connection of more than 2 sentences</primary><secondary>mixed "and" and "or"</secondary></indexterm> FIXME: TAG SPOT</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-mLo1">
@@ -1002,21 +1002,21 @@
<gloss>I walk-to the market and the house or ( the school and the office ).</gloss>
</interlinear-gloss>
</example>
<para> <indexterm type="lojban-word-imported"><primary>KE selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>ke</primary></indexterm> <indexterm type="general-imported"><primary>ke in sumti grouping</primary><secondary>where allowed</secondary></indexterm> If sumti were allowed to begin with
<jbophrase>ke</jbophrase>, unavoidable ambiguities would result, so
<jbophrase>ke</jbophrase> grouping of sumti is allowed only just after a logical connective. This rule does not apply to
<jbophrase>tu'e</jbophrase> grouping of bridi, as
<xref linkend="example-random-id-erTb"/> shows.</para>
<para> <indexterm type="example-imported"><primary>German rich man</primary><secondary>example</secondary></indexterm> Now we have enough facilities to handle the problem of
<xref linkend="example-random-id-3zE1"/>:
- <quote>I am German, rich, and a man - or else none of these.</quote> The following paraphrase has the correct meaning:</para>
+ <quote>I am German, rich, and a man – or else none of these.</quote> The following paraphrase has the correct meaning:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-KyHw">
<title>
<anchor xml:id="c14e8d10"/>
</title>
<interlinear-gloss>
<jbo>[tu'e] mi dotco .ijo mi ricfu [tu'u] .ije tu'e mi dotco .ijo mi nanmu [tu'u]</jbo>
<gloss>( I am-German if-and-only-if I am-rich ) and (I am-German if-and-only-if I am-a-man ).</gloss>
</interlinear-gloss>
</example>
<para>The truth table, when worked out, produces T if and only if all three component sentences are true or all three are false.</para>
@@ -1836,21 +1836,21 @@
<gloss>You desire something-about a-mass-of coffee [truth function?] a-mass-of tea?</gloss>
<en>Do you want coffee or tea?</en>
</interlinear-gloss>
</example>
<para> <indexterm type="example-imported"><primary>coffee or tea</primary><secondary>example</secondary></indexterm> the answer
<jbophrase>.e</jbophrase>, meaning that I want both, is perfectly plausible, if not necessarily polite.</para>
<para> <indexterm type="general-imported"><primary>afterthought connection</primary><secondary>contrasted with forethought for grammatical utterances</secondary></indexterm> <indexterm type="general-imported"><primary>forethought connection</primary><secondary>contrasted with afterthought for grammatical utterances</secondary></indexterm> <indexterm type="general-imported"><primary>forethought connectives</primary><secondary>as ungrammatical utterance</secondary></indexterm> <indexterm type="general-imported"><primary>connectives</primary><secondary>as ungrammatical utterance</secondary></indexterm> The forethought questions
<jbophrase>ge'i</jbophrase> and
- <jbophrase>gu'i</jbophrase> are used like the others, but ambiguity forbids the use of isolated forethought connectives as answers - they sound like the start of forethought-connected bridi. So although
+ <jbophrase>gu'i</jbophrase> are used like the others, but ambiguity forbids the use of isolated forethought connectives as answers – they sound like the start of forethought-connected bridi. So although
<xref linkend="example-random-id-286J"/> is the forethought version of
<xref linkend="example-random-id-xtIf"/>:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-286J">
<title>
<anchor xml:id="c14e13d14"/>
</title>
<interlinear-gloss>
<jbo>do djica tu'a ge'i loi ckafi gi loi tcati</jbo>
@@ -2068,21 +2068,21 @@
<jbophrase>liste</jbophrase> is a sequence of the things which are mentioned in the list. (It is worth pointing out that
<jbophrase>lo liste</jbophrase> means a physical object such as a grocery list: a purely abstract list is
<jbophrase>lo porsi</jbophrase>, a sequence.) Here the three sumti connected by
<jbophrase>ce'o</jbophrase> are in a definite order, not just lumped together in a set or a mass.</para>
<para> <indexterm type="lojban-word-imported"><primary>jo'u</primary></indexterm> <indexterm type="general-imported"><primary>jo'u</primary><secondary>result of connection with</secondary></indexterm> <indexterm type="general-imported"><primary>jo'u</primary><secondary>contrasted with ce'o</secondary></indexterm> <indexterm type="general-imported"><primary>jo'u</primary><secondary>contrasted with ce</secondary></indexterm> <indexterm type="general-imported"><primary>jo'u</primary><secondary>contrasted with joi</secondary></indexterm> <indexterm type="general-imported"><primary>individuals into set</primary><secondary>by non-logical connection</secondary></indexterm> <indexterm type="general-imported"><primary>individuals into mass</primary><secondary>by non-logical connection</secondary></indexterm> <indexterm type="general-imported"><primary>non-logical connection</primary><secondary>of individuals into set</secondary></indexterm> <indexterm type="general-imported"><primary>non-logical connection</primary><secondary>of individuals into mass</secondary></indexterm> So
<jbophrase>joi</jbophrase>,
<jbophrase>ce</jbophrase>, and
<jbophrase>ce'o</jbophrase> are parallel, in that the sumti connected are taken to be individuals, and the result is something else: a mass, a set, or a sequence respectively. The cmavo
- <jbophrase>jo'u</jbophrase> serves as a fourth element in this pattern: the sumti connected are individuals, and the result is still individuals - but inseparably so. The normal Lojban way of saying that James and George are brothers is:</para>
+ <jbophrase>jo'u</jbophrase> serves as a fourth element in this pattern: the sumti connected are individuals, and the result is still individuals – but inseparably so. The normal Lojban way of saying that James and George are brothers is:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-sy2V">
<title>
<anchor xml:id="c14e14d8"/>
</title>
<interlinear-gloss>
<jbo>la djeimyz. bruna la djordj.</jbo>
<gloss>James is-the-brother-of George.</gloss>
</interlinear-gloss>
@@ -2783,21 +2783,21 @@
<example role="interlinear-gloss-example" xml:id="example-random-id-PMTu">
<title>
<anchor xml:id="c14e18d5"/>
</title>
<interlinear-gloss>
<jbo>mi pu klama le zarci .ije mi pu tervecnu lo cidja</jbo>
<gloss>I [past] go-to the market. And I [past] buy items-of food.</gloss>
</interlinear-gloss>
</example>
<para>fails to fully represent a feature of the English, namely that the buying came after the going. (It also fails to represent that the buying was a consequence of the going, which can be expressed by a modal that is discussed in
- <xref linkend="chapter-sumti-tcita"/>.) However, the tense information - that the event of my going to the market preceded the event of my buying food - can be added to the logical connective as follows. The
+ <xref linkend="chapter-sumti-tcita"/>.) However, the tense information – that the event of my going to the market preceded the event of my buying food – can be added to the logical connective as follows. The
<jbophrase>.ije</jbophrase> is replaced by
<jbophrase>.ijebo</jbophrase>, and the tense cmavo
<jbophrase>ba</jbophrase> is inserted between
<jbophrase>.ije</jbophrase> and
<jbophrase>bo</jbophrase>:</para>
<para> <indexterm type="lojban-word-imported"><primary>ba</primary></indexterm> <indexterm type="lojban-word-imported"><primary>.ijebabo</primary></indexterm> FIXME: TAG SPOT</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-BPG1">
<title>
<anchor xml:id="c14e18d6"/>
</title>
diff --git a/todocbook/15.xml b/todocbook/15.xml
index f4d3383..5549a90 100644
--- a/todocbook/15.xml
+++ b/todocbook/15.xml
@@ -339,21 +339,21 @@
</section>
<section xml:id="section-scalar-negation">
<title>Scalar Negation</title>
<para>Let us now consider some other types of negation. For example, when we say:</para>
<example xml:id="example-random-id-GJga">
<title>
<anchor xml:id="c15e3d1"/>
</title>
<para>The chair is not brown.</para>
</example>
- <para>we make a positive inference - that the chair is some other color. Thus, it is legitimate to respond:</para>
+ <para>we make a positive inference – that the chair is some other color. Thus, it is legitimate to respond:</para>
<example xml:id="example-random-id-DDN8">
<title>
<anchor xml:id="c15e3d2"/>
</title>
<para>It is green.</para>
</example>
<para>Whether we agree that the chair is brown or not, the fact that the statement refers to color has significant effect on how we interpret some responses. If we hear the following exchange:</para>
<example xml:id="example-random-id-muQB">
<title>
<anchor xml:id="c15e3d3"/>
@@ -480,21 +480,21 @@
<quote>not necessary</quote> or
<quote>unnecessary</quote> being the polar opposite of necessary. Another scale, especially relevant to Lojban, is interpreted based on situations modified by one's philosophy:
<quote>not true</quote> may be equated with
<quote>false</quote> in a bi-valued truth-functional logic, while in tri-valued logic an intermediate between
<quote>true</quote> and
<quote>false</quote> is permitted, and in fuzzy logic a continuous scale exists from true to false. The meaning of
<quote>not true</quote> requires a knowledge of which variety of truth scale is being considered.</para>
<para>We will define the most general form of scalar negation as indicating only that the particular point or value in the scale or range is not valid and that some other (unspecified) point on the scale is correct. This is the intent expressed in most contexts by
<quote>not mild</quote>, for example.</para>
- <para>Using this paradigm, contradictory negation is less restrictive than scalar negation - it says that the point or value stated is incorrect (false), and makes no statement about the truth of any other point or value, whether or not on the scale.</para>
+ <para>Using this paradigm, contradictory negation is less restrictive than scalar negation – it says that the point or value stated is incorrect (false), and makes no statement about the truth of any other point or value, whether or not on the scale.</para>
<para>In English, scalar negation semantically includes phrases such as
<quote>other than</quote>,
<quote>reverse of</quote>, or
<quote>opposite from</quote> expressions and their equivalents. More commonly, scalar negation is expressed in English by the prefixes
<quote>non-</quote>,
<quote>un-</quote>,
<quote>il-</quote>, and
<quote>im-</quote>. Just which form and permissible values are implied by a scalar negation is dependent on the semantics of the word or concept which is being negated, and on the context. Much confusion in English results from the uncontrolled variations in meaning of these phrases and prefixes.</para>
<para>In the examples of
<xref linkend="section-nahe"/>, we will translate the general case of scalar negation using the general formula
@@ -579,33 +579,33 @@
<anchor xml:id="c15e4d6"/>
</title>
<interlinear-gloss>
<jbo>mi cadzu na'e klama le zarci</jbo>
<gloss>I walkingly-(other-than-go-to) the market.</gloss>
</interlinear-gloss>
</example>
<para>These negations show the default scope of
<jbophrase>na'e</jbophrase> is close-binding on an individual brivla in a tanru.
- <xref linkend="example-random-id-qh4w"/> 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="example-random-id-qh4w"/> 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="chapter-selbri"/> for a discussion of tanru meaning).</para>
<para>In neither
<xref linkend="example-random-id-qh4w"/> nor
<xref linkend="example-random-id-qH6w"/> does the
<jbophrase>na'e</jbophrase> 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="example-random-id-qh4w"/>, which says that I am going, but in a non-walking manner. In
<xref linkend="example-random-id-qH6w"/>, 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
- <jbophrase>mo</jbophrase> question must be plausible - the result must not only have the right number of places and have sumti values appropriate to the place structure, it must also be appropriate or relevant to the context.) This minimal condition allows a speaker to be intentionally vague, while still communicating meaningful information. The speaker who uses selbri negation is denying one relationship, while minimally asserting a different relationship.</para>
+ <jbophrase>mo</jbophrase> question must be plausible – the result must not only have the right number of places and have sumti values appropriate to the place structure, it must also be appropriate or relevant to the context.) This minimal condition allows a speaker to be intentionally vague, while still communicating meaningful information. The speaker who uses selbri negation is denying one relationship, while minimally asserting a different relationship.</para>
<para>We also need a scalar negation form that has a scope longer than a single brivla. There exists such a longer-scope selbri negation form, as exemplified by (each Lojban sentence in the next several examples is given twice, with parentheses in the second copy showing the scope of the
<jbophrase>na'e</jbophrase>):</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-t20b">
<title>
<anchor xml:id="c15e4d7"/>
</title>
<interlinear-gloss>
<jbo>mi na'eke cadzu klama [ke'e] le zarci</jbo>
<jbo>mi na'e (ke cadzu klama [ke'e]) le zarci</jbo>
<gloss>I other-than-(walkingly-go-to) the market.</gloss>
@@ -694,21 +694,21 @@
</title>
<interlinear-gloss>
<jbo>na'e klama becomes nalkla</jbo>
<jbo>na'e cadzu klama becomes naldzukla</jbo>
<jbo>na'e sutra cadzu klama becomes nalsu'adzukla</jbo>
<jbo>nake sutra cadzu ke'e klama becomes nalsu'adzuke'ekla</jbo>
</interlinear-gloss>
</example>
<para>Note:
<jbophrase role="rafsi">-kem-</jbophrase> is the rafsi for
- <jbophrase>ke</jbophrase>, but it is omitted in the final lujvo as superfluous -
+ <jbophrase>ke</jbophrase>, but it is omitted in the final lujvo as superfluous –
<jbophrase>ke'e</jbophrase> is its own rafsi, and its inclusion in the lujvo implies a
<jbophrase>ke</jbophrase> after the
<jbophrase role="rafsi">-nal-</jbophrase>, since it needs to close something; only a
<jbophrase>ke</jbophrase> immediately after the negation would make the
<jbophrase>ke'e</jbophrase> meaningful in the tanru expressed in this lujvo.</para>
<para>In a lujvo, it is probably clearest to translate
<jbophrase role="rafsi">-nal-</jbophrase> as
<quote>non-</quote>, to match the English combining forms, except when the
<jbophrase>na'e</jbophrase> has single word scope and English uses
@@ -967,21 +967,21 @@
<xref linkend="example-random-id-qh9U"/> through
<xref linkend="example-random-id-qHAV"/> could be replaced by the lujvo
<jbophrase>nalmle</jbophrase>,
<jbophrase>normle</jbophrase>, and
<jbophrase>tolmle</jbophrase> respectively.</para>
<para>This large variety of scalar negations is provided because different scales have different properties. Some scales are open-ended in both directions: there is no
<quote>ultimately ugly</quote> or
<quote>ultimately beautiful</quote>. Other scales, like temperature, are open at one end and closed at the other: there is a minimum temperature (so-called
<quote>absolute zero</quote>) but no maximum temperature. Still other scales are closed at both ends.</para>
<para>Correspondingly, some selbri have no obvious
- <jbophrase>to'e</jbophrase>- what is the opposite of a dog? - while others have more than one, and need
+ <jbophrase>to'e</jbophrase>- what is the opposite of a dog? – while others have more than one, and need
<jbophrase>ci'u</jbophrase> to specify which opposite is meant.</para>
</section>
<section xml:id="section-sumti-negation">
<title>sumti negation</title>
<para>There are two ways of negating sumti in Lojban. We have the choice of quantifying the sumti with zero, or of applying the sumti-negator
<jbophrase>na'ebo</jbophrase> before the sumti. It turns out that a zero quantification serves for contradictory negation. As the cmavo we use implies,
<jbophrase>na'ebo</jbophrase> forms a scalar negation.</para>
@@ -1283,21 +1283,21 @@
<interlinear-gloss>
<jbo>na go'i</jbo>
<gloss>[false] [repeat previous]</gloss>
</interlinear-gloss>
</example>
<para>as a response to a negative question like
<xref linkend="example-random-id-8VCt"/>, Lojban designers had to choose between two equally plausible interpretations with opposite effects. Does
<xref linkend="example-random-id-Pgrw"/> create a double negative in the sentence by adding a new
<jbophrase>na</jbophrase> to the one already there (forming a double negative and hence a positive statement), or does the
<jbophrase>na</jbophrase> replace the previous one, leaving the sentence unchanged?</para>
- <para>It was decided that substitution, the latter alternative, is the preferable choice, since it is then clear whether we intend a positive or a negative sentence without performing any manipulations. This is the way English usually works, but not all languages work this way - Russian, Japanese, and Navajo all interpret a negative reply to a negative question as positive.</para>
+ <para>It was decided that substitution, the latter alternative, is the preferable choice, since it is then clear whether we intend a positive or a negative sentence without performing any manipulations. This is the way English usually works, but not all languages work this way – Russian, Japanese, and Navajo all interpret a negative reply to a negative question as positive.</para>
<para>The positive assertion cmavo of selma'o NA, which is "ja'a", can also replace the
<jbophrase>na</jbophrase> in the context, giving:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-iUfV">
<title>
<anchor xml:id="c15e9d5"/>
</title>
<interlinear-gloss>
<jbo>ja'a go'i</jbo>
<gloss>(John truly-(previously went-to) [both] Paris and Rome.)</gloss>
@@ -1345,43 +1345,43 @@
<para>Negations of every sort must be expressible in Lojban; errors are inherent to human thought, and are not excluded from the language. When such negations are metalinguistic, we must separate them from logical claims about the truth or falsity of the statement, as well as from scalar negations which may not easily express (or imply) the preferred claim. Because Lojban allows concepts to be so freely combined in tanru, limits on what is plausible or not plausible tend to be harder to determine.</para>
<para>Mimicking the muddled nature of natural language negation would destroy this separation. Since Lojban does not use tone of voice, we need other means to metalinguistically indicate what is wrong with a statement. When the statement is entirely inappropriate, we need to be able to express metalinguistic negation in a more non-specific fashion.</para>
<para>Here is a list of some different kinds of metalinguistic negation with English-language examples:</para>
<example xml:id="example-random-id-qhbg">
<title>
<anchor xml:id="c15e10d2"/>
</title>
<para>I have not
<emphasis>stopped</emphasis> beating my wife</para>
- <para>(I never started - failure of presupposition).</para>
+ <para>(I never started – failure of presupposition).</para>
</example>
<example xml:id="example-random-id-qHcI">
<title>
<anchor xml:id="c15e10d3"/>
</title>
<para>5 is not blue</para>
- <para>(color does not apply to abstract concepts - failure of category).</para>
+ <para>(color does not apply to abstract concepts – failure of category).</para>
</example>
<example xml:id="example-random-id-qHEQ">
<title>
<anchor xml:id="c15e10d4"/>
</title>
<para>The current King of France is not bald.</para>
- <para>(there is no current King of France - existential failure)</para>
+ <para>(there is no current King of France – existential failure)</para>
</example>
<example xml:id="example-random-id-qhet">
<title>
<anchor xml:id="c15e10d5"/>
</title>
<para>I do not have THREE children.</para>
- <para>(I have two - simple undue quantity)</para>
+ <para>(I have two – simple undue quantity)</para>
</example>
<example xml:id="example-random-id-qhEU">
<title>
<anchor xml:id="c15e10d6"/>
</title>
<para>I have not held THREE jobs previously, but four.</para>
<para>(inaccurate quantity; the difference from the previous example is that</para>
<para>someone who has held four jobs has also held three jobs)</para>
</example>
<example xml:id="example-random-id-qhf5">
@@ -1459,21 +1459,21 @@
<jbophrase>na'i</jbophrase> anywhere in a sentence makes it a non-assertion, and suggests one or more pitfalls in assigning a truth value.</para>
<para>Let us briefly indicate how the above-mentioned metalinguistic errors can be identified. Other metalinguistic problems can then be marked by devising analogies to these examples:</para>
<para>Existential failure can be marked by attaching
<jbophrase>na'i</jbophrase> to the descriptor
<jbophrase>lo</jbophrase> or the
<jbophrase>poi</jbophrase> in a
<jbophrase>da poi</jbophrase>-form sumti. (See
<xref linkend="chapter-sumti-section-basic-descriptors"/> and
<xref linkend="chapter-quantifiers-section-restricted-claims"/> for details on these constructions.) Remember that if a
- <jbophrase>le</jbophrase> sumti seems to refer to a non-existent referent, you may not understand what the speaker has in mind - the appropriate response is then
+ <jbophrase>le</jbophrase> sumti seems to refer to a non-existent referent, you may not understand what the speaker has in mind – the appropriate response is then
<jbophrase>ki'a</jbophrase>, asking for clarification.</para>
<para>Presupposition failure can be marked directly if the presupposition is overt; if not, one can insert a
<quote>mock presupposition</quote> to question with the sumti tcita (selma'o BAI) word
<jbophrase>ji'u</jbophrase>;
<jbophrase>ji'uku</jbophrase> thus explicitly refers to an unexpressed assumption, and
<jbophrase>ji'una'iku</jbophrase> metalinguistically says that something is wrong with that assumption. (See
<xref linkend="chapter-sumti-tcita"/>.)</para>
<para>Scale errors and category errors can be similarly expressed with selma'o BAI.
<jbophrase>le'a</jbophrase> has meaning
<quote>of category/class/type X</quote>,
@@ -1548,25 +1548,25 @@
<anchor xml:id="c15e10d18"/>
</title>
<interlinear-gloss>
<jbo>go'i ji'una'iku</jbo>
<en>Some presupposition is wrong with the previous bridi.</en>
</interlinear-gloss>
</example>
<para>Finally, one may metalinguistically affirm a bridi with
<jbophrase>jo'a</jbophrase>, another cmavo of selma'o UI. A common use for
- <jbophrase>jo'a</jbophrase> might be to affirm that a particular construction, though unusual or counterintuitive, is in fact correct; another usage would be to disagree with - by overriding - a respondent's metalinguistic negation.</para>
+ <jbophrase>jo'a</jbophrase> might be to affirm that a particular construction, though unusual or counterintuitive, is in fact correct; another usage would be to disagree with – by overriding – a respondent's metalinguistic negation.</para>
</section>
<section xml:id="section-are-all-questions-answered">
- <title>Summary - Are All Possible Questions About Negation Now Answered?</title>
+ <title>Summary – Are All Possible Questions About Negation Now Answered?</title>
<example role="interlinear-gloss-example" xml:id="example-random-id-MdRP">
<title>
<anchor xml:id="c15e11d1"/>
</title>
<interlinear-gloss>
<jbo>na go'i .ije na'e go'i .ije na'i go'i</jbo>
</interlinear-gloss>
</example>
</section>
</chapter>
diff --git a/todocbook/16.xml b/todocbook/16.xml
index b217d85..53effd9 100644
--- a/todocbook/16.xml
+++ b/todocbook/16.xml
@@ -117,21 +117,21 @@
<title>
<anchor xml:id="c16e2d3"/>
</title>
<interlinear-gloss>
<jbo>da zo'u da viska mi</jbo>
<gloss>There-is-an-X such-that X sees me.</gloss>
</interlinear-gloss>
</example>
<para> <indexterm type="lojban-word-imported"><primary>da</primary></indexterm> <indexterm type="general-imported"><primary>zo'e</primary><secondary>contrasted with da</secondary></indexterm> <indexterm type="general-imported"><primary>da</primary><secondary>contrasted with zo'e</secondary></indexterm> <indexterm type="general-imported"><primary>existential claims</primary><secondary>definition</secondary></indexterm> <indexterm type="general-imported"><primary>da</primary><secondary>as a translation for "something"</secondary></indexterm>
<xref linkend="example-random-id-jjLd"/> does not presuppose that the listener knows who sees the speaker, but simply tells the listener that there is someone who sees the speaker. Statements of this kind are called
- <quote>existential claims</quote>. (Formally, the one doing the seeing is not restricted to being a person; it could be an animal or - in principle - an inanimate object. We will see in
+ <quote>existential claims</quote>. (Formally, the one doing the seeing is not restricted to being a person; it could be an animal or – in principle – an inanimate object. We will see in
<xref linkend="section-restricted-claims"/> how to represent such restrictions.)</para>
<para> <indexterm type="lojban-word-imported"><primary>ZOhU selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>zo'u</primary></indexterm> <indexterm type="general-imported"><primary>logical variables</primary><secondary>notation convention</secondary></indexterm> <indexterm type="general-imported"><primary>variables</primary><secondary>logical</secondary></indexterm> <indexterm type="general-imported"><primary>prenex</primary><secondary>syntax of</secondary></indexterm> <indexterm type="general-imported"><primary>prenex</primary><secondary>explanation</secondary></indexterm>
<xref linkend="example-random-id-jjLd"/> has a two-part structure: there is the part
<jbophrase>da zo'u</jbophrase>, called the prenex, and the part
<jbophrase>da viska mi</jbophrase>, the main bridi. Almost any Lojban bridi can be preceded by a prenex, which syntactically is any number of sumti followed by the cmavo
<jbophrase>zo'u</jbophrase> (of selma'o ZOhU). For the moment, the sumti will consist of one or more of the cmavo
<jbophrase>da</jbophrase>,
<jbophrase>de</jbophrase>, and
@@ -920,21 +920,21 @@
<gloss>I [false] go-to the store.</gloss>
<gloss>It is false that I go to the store.</gloss>
<en>I don't go to the store.</en>
</interlinear-gloss>
</example>
<para> <indexterm type="lojban-word-imported"><primary>naku</primary></indexterm> <indexterm type="lojban-word-imported"><primary>na</primary></indexterm> The other form of bridi negation is expressed by using the compound cmavo
<jbophrase>naku</jbophrase> in the prenex, which is identified and compounded by the lexer before looking at the sentence grammar. In Lojban grammar,
<jbophrase>naku</jbophrase> is then treated like a sumti. In a prenex,
<jbophrase>naku</jbophrase> means precisely the same thing as the logician's
<quote>it is not the case that</quote> in a similar English context. (Outside of a prenex,
- <jbophrase>naku</jbophrase> is also grammatically treated as a single entity - the equivalent of a sumti - but does not have this exact meaning; we'll discuss these other situations in
+ <jbophrase>naku</jbophrase> is also grammatically treated as a single entity – the equivalent of a sumti – but does not have this exact meaning; we'll discuss these other situations in
<xref linkend="section-na-outside-prenex"/>.)</para>
<para> <indexterm type="general-imported"><primary>external bridi negation</primary><secondary>compared to internal bridi negation</secondary></indexterm> <indexterm type="general-imported"><primary>internal bridi negation</primary><secondary>compared to external bridi negation</secondary></indexterm> <indexterm type="general-imported"><primary>internal bridi negation</primary><secondary>definition</secondary></indexterm> <indexterm type="general-imported"><primary>external bridi negation</primary><secondary>definition</secondary></indexterm> <indexterm type="general-imported"><primary>bridi negation</primary><secondary>na before selbri compared to naku in prenex</secondary></indexterm> <indexterm type="general-imported"><primary>bridi negation</primary><secondary>naku in prenex compared to na before selbri</secondary></indexterm> To represent a bridi negation using a prenex, remove the
<jbophrase>na</jbophrase> from before the selbri and place
<jbophrase>naku</jbophrase> at the left end of the prenex. This form is called
<quote>external bridi negation</quote>, as opposed to
<quote>internal bridi negation</quote> using
<jbophrase>na</jbophrase>. The prenex version of
@@ -1522,21 +1522,21 @@
<jbophrase>nai</jbophrase>,
<jbophrase>na</jbophrase> and
<jbophrase>se</jbophrase> can be derived directly from these rules; modify the basic connective for DeMorgan's Law by substituting from the above identities, and then, apply each
<jbophrase>nai</jbophrase>,
<jbophrase>na</jbophrase> and
<jbophrase>se</jbophrase> modifier of the original connectives. Cancel any double negatives that result.</para>
<para> <indexterm type="general-imported"><primary>DeMorgan's Law</primary><secondary>and moving a logical connective relative to "naku"</secondary></indexterm> <indexterm type="general-imported"><primary>DeMorgan's Law</primary><secondary>and distributing a negation</secondary></indexterm> <indexterm type="general-imported"><primary>distributing a negation</primary></indexterm> When do we apply DeMorgan's Law? Whenever we wish to
<quote>distribute</quote> a negation over a logical connective; and, for internal
- <jbophrase>naku</jbophrase> negation, whenever a logical connective moves in to, or out of, the scope of a negation - when it crosses a negation boundary.</para>
+ <jbophrase>naku</jbophrase> negation, whenever a logical connective moves in to, or out of, the scope of a negation – when it crosses a negation boundary.</para>
<para> <indexterm type="lojban-word-imported"><primary>nai</primary></indexterm> <indexterm type="lojban-word-imported"><primary>gi</primary></indexterm> <indexterm type="lojban-word-imported"><primary>ge</primary></indexterm> <indexterm type="lojban-word-imported"><primary>ga</primary></indexterm> <indexterm type="general-imported"><primary>DeMorgan's Law</primary><secondary>sample applications</secondary></indexterm> Let us apply DeMorgan's Law to some sample sentences. These sentences make use of forethought logical connectives, which are explained in
<xref linkend="chapter-connectives-section-forethought-bridi-connection"/>. It suffices to know that
<jbophrase>ga</jbophrase> and
<jbophrase>gi</jbophrase>, used before each of a pair of sumti or bridi, mean
<quote>either</quote> and
<quote>or</quote> respectively, and that
<jbophrase>ge</jbophrase> and
<jbophrase>gi</jbophrase> used similarly mean
<quote>both</quote> and
@@ -1717,21 +1717,21 @@
<en>There's some relationship between Jim and John.</en>
</interlinear-gloss>
</example>
<para> <indexterm type="example-imported"><primary>some relationship</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>selbri variables</primary><secondary>prenex form as indefinite description</secondary></indexterm> The translations of
<xref linkend="example-random-id-gEWB"/> show how unidiomatic selbri variables are in English; Lojban sentences like
<xref linkend="example-random-id-gEWB"/> need to be totally reworded in English. Furthermore, when a selbri variable appears in the prenex, it is necessary to precede it with a quantifier such as
<jbophrase>su'o</jbophrase>; it is ungrammatical to just say
<jbophrase>bu'a zo'u</jbophrase>. This rule is necessary because only sumti can appear in the prenex, and
- <jbophrase>su'o bu'a</jbophrase> is technically a sumti - in fact, it is an indefinite description like
+ <jbophrase>su'o bu'a</jbophrase> is technically a sumti – in fact, it is an indefinite description like
<jbophrase>re nanmu</jbophrase>, since
<jbophrase>bu'a</jbophrase> is grammatically equivalent to a brivla like
<jbophrase>nanmu</jbophrase>. However, indefinite descriptions involving the bu'a-series cannot be imported from the prenex.</para>
<para> <indexterm type="general-imported"><primary>selbri variables</primary><secondary>form when not in prenex</secondary></indexterm> When the prenex is omitted, the preceding number has to be omitted too:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-XxgT">
<title>
<anchor xml:id="c16e13d2"/>
</title>
@@ -1769,21 +1769,21 @@
</title>
<interlinear-gloss>
<jbo>ci da poi mlatu cu blabi .ije re da cu barda</jbo>
<gloss>Three Xs which-are cats are white, and two Xs are big.</gloss>
</interlinear-gloss>
</example>
<para>What does
<xref linkend="example-random-id-x0FP"/> mean? The appearance of
<jbophrase>ci da</jbophrase> quantifies
<jbophrase>da</jbophrase> as referring to three things, which are restricted by the relative clause to be cats. When
- <jbophrase>re da</jbophrase> appears later, it refers to two of those three things - there is no saying which ones. Further uses of
+ <jbophrase>re da</jbophrase> appears later, it refers to two of those three things – there is no saying which ones. Further uses of
<jbophrase>da</jbophrase> alone, if there were any, would refer once more to the three cats, so the requantification of
<jbophrase>da</jbophrase> is purely local.</para>
<para> <indexterm type="general-imported"><primary>prenex scope</primary><secondary>in abstractions</secondary></indexterm> <indexterm type="general-imported"><primary>prenex scope</primary><secondary>in relative clauses</secondary></indexterm> <indexterm type="general-imported"><primary>prenex scope</primary><secondary>in embedded bridi</secondary></indexterm> <indexterm type="general-imported"><primary>prenex scope</primary><secondary>informal</secondary></indexterm> <indexterm type="general-imported"><primary>prenex scope</primary><secondary>for sentences joined by .i</secondary></indexterm> <indexterm type="general-imported"><primary>prenex scope</primary><secondary>for sentences joined by ijeks</secondary></indexterm> In general, the scope of a prenex that precedes a sentence extends to following sentences that are joined by ijeks (explained in
<xref linkend="chapter-connectives-section-bridi-connection"/>) such as the
<jbophrase>.ije</jbophrase> in
<xref linkend="example-random-id-x0FP"/>. Theoretically, a bare
<jbophrase>.i</jbophrase> terminates the scope of the prenex. Informally, however, variables may persist for a while even after an
<jbophrase>.i</jbophrase>, as if it were an
<jbophrase>.ije</jbophrase>. Prenexes that precede embedded bridi such as relative clauses and abstractions extend only to the end of the clause, as explained in
<xref linkend="section-any"/>. A prenex preceding
diff --git a/todocbook/17.xml b/todocbook/17.xml
index 8cde5c5..5532cda 100644
--- a/todocbook/17.xml
+++ b/todocbook/17.xml
@@ -22,21 +22,21 @@
<jbophrase>lerfu</jbophrase>, and this word will be used in the rest of this chapter.</para>
<para> <indexterm type="general-imported"><primary>alphabet</primary><secondary>Latin used for Lojban</secondary></indexterm> <indexterm type="general-imported"><primary>Latin</primary><secondary>alphabet of Lojban</secondary></indexterm> Lojban uses the Latin alphabet, just as English does, right? Then why is there a need for a chapter like this? After all, everyone who can read it already knows the alphabet. The answer is twofold:</para>
<para> <indexterm type="general-imported"><primary>alphabet</primary><secondary>words for letters in</secondary><tertiary>rationale</tertiary></indexterm> First, in English there are a set of words that correspond to and represent the English lerfu. These words are rarely written down in English and have no standard spellings, but if you pronounce the English alphabet to yourself you will hear them: ay, bee, cee, dee ... . They are used in spelling out words and in pronouncing most acronyms. The Lojban equivalents of these words are standardized and must be documented somehow.</para>
<para> <indexterm type="general-imported"><primary>alphabets</primary><secondary>words for non-Lojban letters</secondary><tertiary>rationale</tertiary></indexterm> Second, English has names only for the lerfu used in writing English. (There are also English names for Greek and Hebrew lerfu: English-speakers usually refer to the Greek lerfu conventionally spelled
<quote>phi</quote> as
<quote>fye</quote>, whereas
<quote>fee</quote> would more nearly represent the name used by Greek-speakers. Still, not all English-speakers know these English names.) Lojban, in order to be culturally neutral, needs a more comprehensive system that can handle, at least potentially, all of the world's alphabets and other writing systems.</para>
- <para>Letterals have several uses in Lojban: in forming acronyms and abbreviations, as mathematical symbols, and as pro-sumti - the equivalent of English pronouns.</para>
+ <para>Letterals have several uses in Lojban: in forming acronyms and abbreviations, as mathematical symbols, and as pro-sumti – the equivalent of English pronouns.</para>
<para> <indexterm type="general-imported"><primary>letter</primary><secondary>contrasted with word for the letter</secondary></indexterm> <indexterm type="general-imported"><primary>lerfu word</primary><secondary>contrasted with lerfu</secondary></indexterm> <indexterm type="general-imported"><primary>lerfu</primary><secondary>contrasted with lerfu word</secondary></indexterm> In earlier writings about Lojban, there has been a tendency to use the word
<jbophrase>lerfu</jbophrase> for both the letterals themselves and for the Lojban words which represent them. In this chapter, that tendency will be ruthlessly suppressed, and the term
<quote>lerfu word</quote> will invariably be used for the latter. The Lojban equivalent would be
<jbophrase>lerfu valsi</jbophrase> or
<jbophrase>lervla</jbophrase>.</para>
</section>
<section xml:id="section-lerfu-liste">
<title>A to Z in Lojban, plus one</title>
<para> <indexterm type="general-imported"><primary>lerfu words</primary><secondary>Lojban coverage requirement</secondary></indexterm> The first requirement of a system of lerfu words for any language is that they must represent the lerfu used to write the language. The lerfu words for English are a motley crew: the relationship between
@@ -184,21 +184,21 @@ ty. .ubu vy. xy. .ybu zy.
<quote>o</quote>
<quote>'</quote>
<quote>a</quote>
</en>
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>lerfu words</primary><secondary>effect of systematic formulation</secondary></indexterm> <indexterm type="general-imported"><primary>spelling out words</primary><secondary>Lojban contrasted with English in usefulness</secondary></indexterm> Spelling out words is less useful in Lojban than in English, for two reasons: Lojban spelling is phonemic, so there can be no real dispute about how a word is spelled; and the Lojban lerfu words sound more alike than the English ones do, since they are made up systematically. The English words
<quote>fail</quote> and
<quote>vale</quote> sound similar, but just hearing the first lerfu word of either, namely
<quote>eff</quote> or
- <quote>vee</quote>, is enough to discriminate easily between them - and even if the first lerfu word were somehow confused, neither
+ <quote>vee</quote>, is enough to discriminate easily between them – and even if the first lerfu word were somehow confused, neither
<quote>vail</quote> nor
<quote>fale</quote> is a word of ordinary English, so the rest of the spelling determines which word is meant. Still, the capability of spelling out words does exist in Lojban.</para>
<para> <indexterm type="general-imported"><primary>lerfu words ending with "y"</primary><secondary>pause after</secondary><tertiary>rationale</tertiary></indexterm> Note that the lerfu words ending in
<jbophrase role="letteral">y</jbophrase> were written (in
<xref linkend="example-random-id-qHRb"/> and
<xref linkend="example-random-id-qhrx"/>) with pauses after them. It is not strictly necessary to pause after such lerfu words, but failure to do so can in some cases lead to ambiguities:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-6dMS">
<title>
<anchor xml:id="c17e2d3"/>
@@ -831,21 +831,21 @@ ty. .ubu vy. xy. .ybu zy.
<interlinear-gloss>
<jbo>.abu dunda by. cy.</jbo>
<en>A gives B C</en>
</interlinear-gloss>
</example>
<para> <indexterm type="lojban-word-imported"><primary>BOI selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>boi</primary></indexterm> <indexterm type="general-imported"><primary>boi</primary><secondary>eliding from lerfu strings</secondary></indexterm> Does this mean that A gives B to C? No.
<jbophrase>by. cy.</jbophrase> is a single lerfu string, although written as two words, and represents a single pro-sumti. The true interpretation is that A gives BC to someone unspecified. To solve this problem, we need to introduce the elidable terminator
<jbophrase>boi</jbophrase> (of selma'o BOI). This cmavo is used to terminate lerfu strings and also strings of numerals; it is required when two of these appear in a row, as here. (The other reason to use
- <jbophrase>boi</jbophrase> is to attach a free modifier - subscript, parenthesis, or what have you - to a lerfu string.) The correct version is:</para>
+ <jbophrase>boi</jbophrase> is to attach a free modifier – subscript, parenthesis, or what have you – to a lerfu string.) The correct version is:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-Hdwz">
<title>
<anchor xml:id="c17e9d6"/>
</title>
<interlinear-gloss>
<jbo>.abu [boi] dunda by. boi cy. [boi]</jbo>
<en>A gives B to C</en>
</interlinear-gloss>
</example>
@@ -904,21 +904,21 @@ ty. .ubu vy. xy. .ybu zy.
<anchor xml:id="c17e10d3"/>
</title>
<interlinear-gloss>
<jbo>dei vasru vo lerfu po'u me'o .ebu</jbo>
<gloss>this-sentence contains four letterals which-are the-expression <quote>e</quote>.</gloss>
<en>This sentence contains four
<quote>e</quote> s.</en>
</interlinear-gloss>
</example>
<para>Since the Lojban sentence has only four
- <jbophrase role="letteral">e</jbophrase> lerfu rather than fourteen, the translation is not a literal one - but
+ <jbophrase role="letteral">e</jbophrase> lerfu rather than fourteen, the translation is not a literal one – but
<xref linkend="example-random-id-pbDf"/> is a Lojban truth just as
<xref linkend="example-random-id-tvHm"/> is an English truth. Coincidentally, the colloquial English translation of
<xref linkend="example-random-id-pbDf"/> is also true!</para>
<para> <indexterm type="lojban-word-imported"><primary>la'e</primary></indexterm> <indexterm type="lojban-word-imported"><primary>lu</primary></indexterm> <indexterm type="lojban-word-imported"><primary>me'o</primary></indexterm> <indexterm type="general-imported"><primary>la'e lu</primary><secondary>compared with me'o</secondary></indexterm> <indexterm type="general-imported"><primary>me'o</primary><secondary>compared with la'e lu</secondary></indexterm> <indexterm type="general-imported"><primary>representing lerfu</primary><secondary>lu contrasted with me'o</secondary></indexterm> <indexterm type="general-imported"><primary>lu</primary><secondary>contrasted with me'o for representing lerfu</secondary></indexterm> <indexterm type="general-imported"><primary>me'o</primary><secondary>contrasted with lu…li'u for representing lerfu</secondary></indexterm> <indexterm type="general-imported"><primary>me'o</primary><secondary>contrasted with quotation for representing lerfu</secondary></indexterm> <indexterm type="general-imported"><primary>quotation</primary><secondary>contrasted with me'o for representing lerfu</secondary></indexterm> The reader might be tempted to use quotation with
<jbophrase>lu ... li'u</jbophrase> instead of
<jbophrase>me'o</jbophrase>, producing:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-pbDf">
<title>
<anchor xml:id="c17e10d4"/>
</title>
@@ -1329,21 +1329,21 @@ ty. .ubu vy. xy. .ybu zy.
<selmaho>FOI</selmaho>
<description>end compound lerfu word</description>
</cmavo-entry>
</cmavo-list>
<para> <indexterm type="general-imported"><primary>LAU selma'o</primary><secondary>grammar of following BY cmavo</secondary></indexterm> <indexterm type="general-imported"><primary>lerfu word cmavo</primary><secondary>list of auxiliary</secondary></indexterm> Note that LAU cmavo must be followed by a BY cmavo or the equivalent, where
<quote>equivalent</quote> means: either any Lojban word followed by
<jbophrase>bu</jbophrase>, another LAU cmavo (and its required sequel), or a
<jbophrase>tei ... foi</jbophrase> compound cmavo.</para>
</section>
<section xml:id="section-proposed-lerfu-words">
- <title>Proposed lerfu words - introduction</title>
+ <title>Proposed lerfu words – introduction</title>
<para> <indexterm type="general-imported"><primary>lerfu words</primary><secondary>list of proposed</secondary><tertiary>notation convention</tertiary></indexterm> The following sections contain tables of proposed lerfu words for some of the standard alphabets supported by the Lojban lerfu system. The first column of each list is the lerfu (actually, a Latin-alphabet name sufficient to identify it). The second column is the proposed name-based lerfu word, and the third column is the proposed lerfu word in the system based on using the cmavo of selma'o BY with a shift word.</para>
<para> <indexterm type="general-imported"><primary>proposed lerfu words</primary><secondary>as working basis</secondary></indexterm> These tables are not meant to be authoritative (several authorities within the Lojban community have niggled over them extensively, disagreeing with each other and sometimes with themselves). They provide a working basis until actual usage is available, rather than a final resolution of lerfu word problems. Probably the system presented here will evolve somewhat before settling down into a final, conventional form.</para>
<para>For Latin-alphabet lerfu words, see
<xref linkend="section-lerfu-liste"/> (for Lojban) and
<xref linkend="section-alien-alphabets"/> (for non-Lojban Latin-alphabet lerfu).</para>
</section>
<section xml:id="section-greek">
<title>Proposed lerfu words for the Greek alphabet</title>
diff --git a/todocbook/18.xml b/todocbook/18.xml
index 1bf5b72..6e266cf 100644
--- a/todocbook/18.xml
+++ b/todocbook/18.xml
@@ -30,21 +30,21 @@
</title>
<math>3x + 2y</math>
</example>
<para> <indexterm type="general-imported"><primary>mathematical notation</primary><secondary>and omitted operators</secondary></indexterm> contains omitted multiplication operators, but there are other possible interpretations for the strings
<quote>3x</quote> and
<quote>2y</quote> than as mathematical multiplication. Therefore, the Lojban verbal (spoken and written) form of
<xref linkend="example-random-id-dGcT"/> must not omit the multiplication operators.</para>
- <para> <indexterm type="general-imported"><primary>mekso chapter</primary><secondary>completeness</secondary></indexterm> <indexterm type="general-imported"><primary>mekso chapter</primary><secondary>table notation convention</secondary></indexterm> The remainder of this chapter explains (in as much detail as is currently possible) the mekso system. This chapter is by intention complete as regards mekso components, but only suggestive about uses of those components - as of now, there has been no really comprehensive use made of mekso facilities, and many matters must await the test of usage to be fully clarified.</para>
+ <para> <indexterm type="general-imported"><primary>mekso chapter</primary><secondary>completeness</secondary></indexterm> <indexterm type="general-imported"><primary>mekso chapter</primary><secondary>table notation convention</secondary></indexterm> The remainder of this chapter explains (in as much detail as is currently possible) the mekso system. This chapter is by intention complete as regards mekso components, but only suggestive about uses of those components – as of now, there has been no really comprehensive use made of mekso facilities, and many matters must await the test of usage to be fully clarified.</para>
</section>
<section xml:id="section-numbers">
<title>Lojban numbers</title>
<para>The following cmavo are discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>pa</cmavo>
<selmaho>PA</selmaho>
<description>1</description>
</cmavo-entry>
@@ -1629,21 +1629,21 @@
<anchor xml:id="c18e10d3"/>
</title>
<interlinear-gloss>
<jbo>li jaureivai ju'u paxa du li cimuxaze</jbo>
<gloss>The-number DEF base 16 equals the-number 3567.</gloss>
</interlinear-gloss>
</example>
<para> <indexterm type="example-imported"><primary>ABC base 16</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>digits beyond 9</primary><secondary>word pattern</secondary></indexterm> Note the pattern in the cmavo: the diphthongs
<jbophrase>au</jbophrase>,
<jbophrase>ei</jbophrase>,
- <jbophrase>ai</jbophrase> are used twice in the same order. The digits for A to D use consonants different from those used in the decimal digit cmavo; E and F unfortunately overlap 2 and 4 - there was simply not enough available cmavo space to make a full differentiation possible. The cmavo are also in alphabetical order.</para>
+ <jbophrase>ai</jbophrase> are used twice in the same order. The digits for A to D use consonants different from those used in the decimal digit cmavo; E and F unfortunately overlap 2 and 4 – there was simply not enough available cmavo space to make a full differentiation possible. The cmavo are also in alphabetical order.</para>
<para> <indexterm type="general-imported"><primary>decimal point</primary><secondary>in bases other than 10</secondary></indexterm> <indexterm type="general-imported"><primary>base point</primary><secondary>in bases other than 10</secondary></indexterm> The base point
<jbophrase>pi</jbophrase> is used in non-decimal bases just as in base 10:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-gCo4">
<title>
<anchor xml:id="c18e10d4"/>
</title>
<interlinear-gloss>
<jbo>li vai pi bi ju'u paxa du li pamu pi mu</jbo>
<gloss>The-number F.8 base 16 equals the-number 15.5.</gloss>
diff --git a/todocbook/2.xml b/todocbook/2.xml
index 4d0ea5b..bb10196 100644
--- a/todocbook/2.xml
+++ b/todocbook/2.xml
@@ -598,21 +598,21 @@
<para>The cmavo
<jbophrase>ni'o</jbophrase> separates paragraphs (covering different topics of discussion). In a long text or utterance, the topical structure of the text may be indicated by multiple
<jbophrase>ni'o</jbophrase> s, with perhaps
<jbophrase>ni'oni'oni'o</jbophrase> used to indicate a chapter,
<jbophrase>ni'oni'o</jbophrase> to indicate a section, and a single
<jbophrase>ni'o</jbophrase> to indicate a subtopic corresponding to a single English paragraph.</para>
<para>The cmavo
<jbophrase>.i</jbophrase> separates sentences. It is sometimes compounded with words that modify the exact meaning (the semantics) of the sentence in the context of the utterance. (The cmavo
<jbophrase>xu</jbophrase>, discussed in
- <xref linkend="cll_chapter2-section15"/>, is one such word - it turns the sentence from a statement to a question about truth.) When more than one person is talking, a new speaker will usually omit the
+ <xref linkend="cll_chapter2-section15"/>, is one such word – it turns the sentence from a statement to a question about truth.) When more than one person is talking, a new speaker will usually omit the
<jbophrase>.i</jbophrase> even though she/he may be continuing on the same topic.</para>
<para>It is still O.K. for a new speaker to say the
<jbophrase>.i</jbophrase> before continuing; indeed, it is encouraged for maximum clarity (since it is possible that the second speaker might merely be adding words onto the end of the first speaker's sentence). A good translation for
<jbophrase>.i</jbophrase> is the
<quote>and</quote> used in run-on sentences when people are talking informally:
<quote>I did this, and then I did that, and ..., and ...</quote>.</para>
</section>
<section xml:id="cll_chapter2-section9">
<title>tanru</title>
<para> <indexterm type="general-imported"><primary>tanru</primary><secondary>quick-tour version</secondary></indexterm> When two gismu are adjacent, the first one modifies the second, and the selbri takes its place structure from the rightmost word. Such combinations of gismu are called
diff --git a/todocbook/20.xml b/todocbook/20.xml
index 091c66a..73d8192 100644
--- a/todocbook/20.xml
+++ b/todocbook/20.xml
@@ -1271,21 +1271,21 @@
I [inchoative] fight.
I’m on the verge of fighting.
</programlisting>
<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.
That is an X-ray camera.
</programlisting>
<bridgehead>
<anchor xml:id="ZEhA"/> selma'o ZEhA (<xref linkend="chapter-tenses-section-interval-sizes"/>)
</bridgehead>
<para>A tense indicating the size of an interval in time (long, medium, or short).</para>
<programlisting xml:space="preserve">
mi puze'a citka
I [past] [short interval] eat.
diff --git a/todocbook/21.xml b/todocbook/21.xml
index 7b95525..e274759 100644
--- a/todocbook/21.xml
+++ b/todocbook/21.xml
@@ -1,25 +1,25 @@
<chapter xml:id="chapter-grammars">
<title>Formal Grammars</title>
<section xml:id="section-YACC">
<title>YACC Grammar of Lojban</title>
<para>The following two listings constitute the formal grammar of Lojban. The first version is written in the YACC language, which is used to describe parsers, and has been used to create a parser for Lojban texts. This parser is available from the Logical Language Group. The second listing is in Extended Backus-Naur Form (EBNF) and represents the same grammar in a more human-readable form. (In case of discrepancies, the YACC version is official.) There is a cross-reference listing for each format that shows, for each selma'o and rule, which rules refer to it.</para>
<para>/* /*Lojban Machine Grammar, Final Baseline The Lojban Machine Grammardocument is explicitly dedicated to the public domain by its author,The Logical Language Group, Inc.</para>
<para>grammar.300 */</para>
<para>/* The Lojban machine parsing algorithm is a multi-step process. The YACC machine grammar presented here is an amalgam of those steps, concatenated so as to allow YACC to verify the syntactic ambiguity of the grammar. YACC is used to generate a parser for a portion of the grammar, which is LALR1 (the type of grammar that YACC is designed to identify and process successfully), but most of the rest of the grammar must be parsed using some language-coded processing.</para>
- <bridgehead>Step 1 - Lexing</bridgehead>
+ <bridgehead>Step 1 – Lexing</bridgehead>
<para>From phonemes, stress, and pause, it is possible to resolve Lojban unambiguously into a stream of words. Any machine processing of speech will have to have some way to deal with ’non-Lojban’ failures of fluent speech, of course. The resolved words can be expressed as a text file using Lojban’s phonetic spelling rules.</para>
<para>The following steps assume that there is the possibility of non-Lojban text within the Lojban text (delimited appropriately). Such non-Lojban text may not be reducible from speech phonetically. However, step 2 allows the filtering of a phonetically transcribed text stream, to recognize such portions of non-Lojban text where properly delimited, without interference with the parsing algorithm.</para>
- <bridgehead>Step 2 - Filtering</bridgehead>
+ <bridgehead>Step 2 – Filtering</bridgehead>
<para>From start to end, performing the following filtering and lexing tasks using the given order of precedence in case of conflict:</para>
<orderedlist numeration="lowerroman">
<listitem>
<para>If the Lojban word <jbophrase>zoi</jbophrase> (selma'o ZOI) is identified, take the following Lojban word (which should be end delimited with a pause for separation from the following non-Lojban text) as an opening delimiter. Treat all text following that delimiter, until that delimiter recurs
<emphasis>after a pause</emphasis>, as grammatically a single token (labelled ’
<xref linkend="cll_yacc-699"/>’ in this grammar). There is no need for processing within this text except as necessary to find the closing delimiter.</para>
</listitem>
<listitem>
<para>If the Lojban word <jbophrase>zo</jbophrase> (selma'o ZO) is identified, treat the following Lojban word as a token labelled ’
<xref linkend="cll_yacc-698"/>’, instead of lexing it by its normal grammatical function.</para>
@@ -34,42 +34,42 @@
<listitem>
<para>If the word <jbophrase>si</jbophrase> (selma'o SI) is identified, erase it and the previous word (or token, if the previous text has been condensed into a single token by one of the above rules).</para>
</listitem>
<listitem>
<para>If the word <jbophrase>sa</jbophrase> (selma'o SA) is identified, erase it and all preceding text as far back as necessary to make what follows attach to what precedes. (This rule is hard to formalize and may receive further definition later.)</para>
</listitem>
<listitem>
<para>If the word <jbophrase>su</jbophrase> (selma'o SU) is identified, erase it and all preceding text back to and including the first preceding token word which is in one of the selma'o: NIhO, LU, TUhE, and TO. However, if speaker identification is available, a SU shall only erase to the beginning of a speaker’s discourse, unless it occurs at the beginning of a speaker’s discourse. (Thus, if the speaker has said something, two adjacent uses of <jbophrase>su</jbophrase> are required to erase the entire conversation.</para>
</listitem>
</orderedlist>
- <bridgehead>Step 3 - Termination</bridgehead>
+ <bridgehead>Step 3 – Termination</bridgehead>
<para>If the text contains a FAhO, treat that as the end-of-text and ignore everything that follows it.</para>
- <bridgehead>Step 4 - Absorption of Grammar-Free Tokens</bridgehead>
+ <bridgehead>Step 4 – Absorption of Grammar-Free Tokens</bridgehead>
<para>In a new pass, perform the following absorptions (absorption means that the token is removed from the grammar for processing in following steps, and optionally reinserted, grouped with the absorbing token after parsing is completed).</para>
<orderedlist numeration="lowerroman">
<listitem>
- <para>Token sequences of the form any - (ZEI - any) ..., where there may be any number of ZEIs, are merged into a single token of selma'o BRIVLA.</para>
+ <para>Token sequences of the form any – (ZEI – any) ..., where there may be any number of ZEIs, are merged into a single token of selma'o BRIVLA.</para>
</listitem>
<listitem>
<para>Absorb all selma'o BAhE tokens into the following token. If they occur at the end of text, leave them alone (they are errors).</para>
</listitem>
<listitem>
<para>Absorb all selma'o BU tokens into the previous token. Relabel the previous token as selma'o BY.</para>
</listitem>
<listitem>
<para>If selma'o NAI occurs immediately following any of tokens UI or CAI, absorb the NAI into the previous token.</para>
</listitem>
<listitem>
<para>Absorb all members of selma'o DAhO, FUhO, FUhE, UI, Y, and CAI into the previous token. All of these null grammar tokens are permitted following any word of the grammar, without interfering with that word’s grammatical function, or causing any effect on the grammatical interpretation of any other token in the text. Indicators at the beginning of text are explicitly handled by the grammar.</para>
</listitem>
</orderedlist>
- <bridgehead>Step 5 - Insertion of Lexer Lexemes</bridgehead>
+ <bridgehead>Step 5 – Insertion of Lexer Lexemes</bridgehead>
<para>Lojban is not in itself LALR1. There are words whose grammatical function is determined by following tokens. As a result, parsing of the YACC grammar must take place in two steps. In the first step, certain strings of tokens with defined grammars are identified, and either</para>
<orderedlist numeration="lowerroman">
<listitem>
<para>are replaced by a single specified ’lexer token’ for step 6, or</para>
</listitem>
<listitem>
<para>the lexer token is inserted in front of the token string to identify it uniquely.</para>
</listitem>
</orderedlist>
<para>The YACC grammar included herein is written to make YACC generation of a step 6 parser easy regardless of whether a. or b. is used. The strings of tokens to be labelled with lexer tokens are found in rule terminals labelled with numbers between 900 and 1099. These rules are defined with the lexer tokens inserted, with the result that it can be verified that the language is LALR1 under option b. after steps 1 through 4 have been performed. Alternatively, if option a. is to be used, these rules are commented out, and the rule terminals labelled from 800 to 900 refer to the lexer tokens
@@ -98,21 +98,21 @@
<member>F</member>
<member>P</member>
<member>R</member>
<member>T</member>
<member>S</member>
<member>Y</member>
<member>L</member>
<member>Q</member>
</simplelist>
. This ensures that the longest rules will be processed first; a PA+MAI will not be seen as a PA with a dangling MAI at the end, for example. </para>
- <bridgehead>Step 6 - YACC Parsing</bridgehead>
+ <bridgehead>Step 6 – YACC Parsing</bridgehead>
<para>YACC should now be able to parse the Lojban text in accordance with the rule terminals labelled from 1 to 899 under option 5a, or 1 to 1099 under option 5b. Comment out the rules beyond 900 if option 5a is used, and comment out the 700-series of lexer-tokens, while restoring the series of lexer tokens numbered from 900 up.</para>
<para>*/</para>
<programlisting xml:space="preserve">
%token
<anchor xml:id="y501"/>
<anchor xreflabel="YACC rule #501" xml:id="cll_yacc-501"/> A_501 /* eks; basic afterthought logical connectives */
%token
<anchor xml:id="y502"/>
<anchor xreflabel="YACC rule #502" xml:id="cll_yacc-502"/> BAI_502 /* modal operators */
%token
@@ -416,21 +416,21 @@
and relative clauses */
%token
<anchor xml:id="y618"/>
<anchor xreflabel="YACC rule #618" xml:id="cll_yacc-618"/> XI_618 /* subscripting operator */
%token
<anchor xml:id="y619"/>
<anchor xreflabel="YACC rule #619" xml:id="cll_yacc-619"/> Y_619 /* hesitation */
%token
<anchor xml:id="y621"/>
-<anchor xreflabel="YACC rule #621" xml:id="cll_yacc-621"/> ZAhO_621 /* event properties - inchoative, etc. */
+<anchor xreflabel="YACC rule #621" xml:id="cll_yacc-621"/> ZAhO_621 /* event properties – inchoative, etc. */
%token
<anchor xml:id="y622"/>
<anchor xreflabel="YACC rule #622" xml:id="cll_yacc-622"/> ZEhA_622 /* time interval size tense */
%token
<anchor xml:id="y623"/>
<anchor xreflabel="YACC rule #623" xml:id="cll_yacc-623"/> ZEI_623 /* lujvo glue */
%token
<anchor xml:id="y624"/>
<anchor xreflabel="YACC rule #624" xml:id="cll_yacc-624"/> ZI_624 /* time distance tense */
@@ -1630,31 +1630,31 @@ the 900 series rules are found in the lexer. */
<xref linkend="cll_yacc-822"/>
<xref linkend="cll_yacc-383"/>
;
<anchor xml:id="y385"/>
<anchor xreflabel="YACC rule #385" xml:id="cll_yacc-385"/> operand_C_385 :
<xref linkend="cll_yacc-300"/>
|
<xref linkend="cll_yacc-817"/>
<xref linkend="cll_yacc-461"/>
- /* lerfu string as operand - classic math variable */
+ /* lerfu string as operand – classic math variable */
|
<xref linkend="cll_yacc-428"/>
<xref linkend="cll_yacc-130"/>
<xref linkend="cll_yacc-473"/>
- /* quantifies a bridi - inverse of -MOI */
+ /* quantifies a bridi – inverse of -MOI */
|
<xref linkend="cll_yacc-427"/>
<xref linkend="cll_yacc-90"/>
<xref linkend="cll_yacc-473"/>
- /* quantifies a sumti - inverse of LI */
+ /* quantifies a sumti – inverse of LI */
|
<xref linkend="cll_yacc-431"/>
<xref linkend="cll_yacc-313"/>
<xref linkend="cll_yacc-473"/>
|
<xref linkend="cll_yacc-807"/>
<xref linkend="cll_yacc-381"/>
<xref linkend="cll_yacc-816"/>
<xref linkend="cll_yacc-385"/>
|
@@ -1946,21 +1946,21 @@ the 900 series rules are found in the lexer. */
<xref linkend="cll_yacc-697"/>
<xref linkend="cll_yacc-565"/>
;
/* ’words’ may be any Lojban words, with no claim of grammaticality; the
preparser will not lex the individual words per their normal selma'o;
used to quote ungrammatical Lojban, equivalent to the * or ? writing
convention for such text. */
/* The preparser needs one bit of sophistication for this rule. A
- quoted string should be able to contain other quoted strings - this is
+ quoted string should be able to contain other quoted strings – this is
only a problem for a LOhU quote itself, since the LEhU clossing this
quote would otherwise close the outer quotes, which is incorrect. For
this purpose, we will cheat on the use of ZO in such a quote (since this
is ungrammatical text, it is a sign ignored by the parser). Use ZO to
mark any nested quotation LOhU. The preparser then will absorb it by
the ZO rule, before testing for LOhU. This is obviously not the
standard usage for ZO, which would otherwise cause the result to be a
sumti. But, since the result will be part of an unparsed string anyway,
it doesn’t matter. */
@@ -3090,21 +3090,21 @@ the 900 series rules are found in the lexer. */
/* space defaults to time-space reference space */
|
<xref linkend="cll_yacc-1040"/>
/* can include time if specified with VIhA; otherwise time defaults to the
time-space reference time */
|
<xref linkend="cll_yacc-1030"/>
<xref linkend="cll_yacc-1040"/>
- /* time and space - If
+ /* time and space – If
<xref linkend="cll_yacc-1040"/> is marked with
VIhA for space-time the tense may be self-contradictory */
/* interval prop before space_time is for time distribution */
|
<xref linkend="cll_yacc-1040"/>
<xref linkend="cll_yacc-1030"/>
;
<anchor xml:id="y980"/>
<anchor xreflabel="YACC rule #980" xml:id="cll_yacc-980"/> lexer_P_980 :
diff --git a/todocbook/3.xml b/todocbook/3.xml
index b6168e6..bb9baf5 100644
--- a/todocbook/3.xml
+++ b/todocbook/3.xml
@@ -616,21 +616,21 @@
<member><jbophrase>y'a</jbophrase></member>
<member><jbophrase>y'e</jbophrase></member>
<member><jbophrase>y'i</jbophrase></member>
<member><jbophrase>y'o</jbophrase></member>
<member><jbophrase>y'u</jbophrase></member>
<member><jbophrase>y'y</jbophrase></member>
</simplelist>
<para> <indexterm type="general-imported"><primary>vowel pairs</primary><secondary>involving y</secondary></indexterm> Vowel pairs involving
<jbophrase role="letteral">y</jbophrase> appear only in Lojbanized names. They could appear in cmavo (structure words), but only
- <jbophrase>.y'y.</jbophrase> is so used - it is the Lojban name of the apostrophe letter (see
+ <jbophrase>.y'y.</jbophrase> is so used – it is the Lojban name of the apostrophe letter (see
<xref linkend="chapter-letterals-section-lerfu-liste"/>).</para>
<para> <indexterm type="general-imported"><primary>vowel pairs</primary><secondary>grouping of</secondary></indexterm> When more than two vowels occur together in Lojban, the normal pronunciation pairs vowels from the left into syllables, as in the Lojbanized name:</para>
<example role="pronunciation-example" xml:id="example-random-id-RxtI">
<title>
<anchor xml:id="c3e5d1"/>
</title>
<pronunciation>
<jbo>meiin.</jbo>
<jbo role="pronunciation">mei,in.</jbo>
</pronunciation>
@@ -1208,21 +1208,21 @@
<quote>stressed vowel</quote> are largely interchangeable concepts.</para>
<para> <indexterm type="general-imported"><primary>stress</primary><secondary>rules for</secondary></indexterm> Most Lojban words are stressed on the next-to-the-last, or penultimate, syllable. In counting syllables, however, syllables whose vowel is
<jbophrase role="letteral">y</jbophrase> or which contain a syllabic consonant (
<jbophrase role="letteral">l</jbophrase>,
<jbophrase role="letteral">m</jbophrase>,
<jbophrase role="letteral">n</jbophrase>, or
<jbophrase role="letteral">r</jbophrase>) are never counted. (The Lojban term for penultimate stress is
<jbophrase>da'amoi terbasna</jbophrase>.) Similarly, syllables created solely by adding a buffer vowel, such as
<phrase role="IPA">[ɪ]</phrase>, are not counted.</para>
- <para> <indexterm type="general-imported"><primary>stress</primary><secondary>levels of</secondary></indexterm> There are actually three levels of stress - primary, secondary, and weak. Weak stress is the lowest level, so it really means no stress at all. Weak stress is required for syllables containing
+ <para> <indexterm type="general-imported"><primary>stress</primary><secondary>levels of</secondary></indexterm> There are actually three levels of stress – primary, secondary, and weak. Weak stress is the lowest level, so it really means no stress at all. Weak stress is required for syllables containing
<jbophrase role="letteral">y</jbophrase>, a syllabic consonant, or a buffer vowel.</para>
<para> <indexterm type="general-imported"><primary>names</primary><secondary>stress on</secondary></indexterm> <indexterm type="general-imported"><primary>brivla</primary><secondary>stress on</secondary></indexterm> <indexterm type="general-imported"><primary>cmavo</primary><secondary>stress on</secondary></indexterm> <indexterm type="general-imported"><primary>stress</primary><secondary>primary</secondary></indexterm> Primary stress is required on the penultimate syllable of Lojban content words (called
<jbophrase>brivla</jbophrase>). Lojbanized names may be stressed on any syllable, but if a syllable other than the penultimate is stressed, the syllable (or at least its vowel) must be capitalized in writing. Lojban structural words (called
<jbophrase>cmavo</jbophrase>) may be stressed on any syllable or none at all. However, primary stress may not be used in a syllable just preceding a brivla, unless a pause divides them; otherwise, the two words may run together.</para>
<para> <indexterm type="general-imported"><primary>stress</primary><secondary>secondary</secondary></indexterm> Secondary stress is the optional and non-distinctive emphasis used for other syllables besides those required to have either weak or primary stress. There are few rules governing secondary stress, which typically will follow a speaker's native language habits or preferences. Secondary stress can be used for contrast, or for emphasis of a point. Secondary stress can be emphasized at any level up to primary stress, although the speaker must not allow a false primary stress in brivla, since errors in word resolution could result.</para>
<para> The following are Lojban words with stress explicitly shown:</para>
<example role="pronunciation-example" xml:id="example-random-id-cxzt">
<title>
<anchor xml:id="c3e9d6"/>
</title>
@@ -1315,38 +1315,38 @@
<example role="pronunciation-example" xml:id="example-random-id-5g4j">
<title>
<anchor xml:id="c3e9d12"/>
</title>
<pronunciation>
<jbo>da'udja</jbo>
<jbo role="pronunciation">da'UD,ja</jbo>
<jbo role="pronunciation">da'U,dja</jbo>
</pronunciation>
</example>
- <para> These two syllabications sound the same to a Lojban listener - the association of unbuffered consonants in syllables is of no import in recognizing the word.</para>
+ <para> These two syllabications sound the same to a Lojban listener – the association of unbuffered consonants in syllables is of no import in recognizing the word.</para>
<example role="pronunciation-example" xml:id="example-random-id-Ki4a">
<title>
<indexterm type="example-imported"><primary>syllabication</primary><secondary>variants of</secondary><tertiary>example</tertiary></indexterm>
<anchor xml:id="c3e9d13"/>
</title>
<pronunciation>
<jbo>e'u bridi</jbo>
<jbo role="pronunciation">e'u BRI,di</jbo>
<jbo role="pronunciation">E'u BRI,di</jbo>
<jbo role="pronunciation">e'U.BRI,di</jbo>
</pronunciation>
</example>
<para>In
<xref linkend="example-random-id-Ki4a"/>,
<jbophrase>e'u</jbophrase> is a cmavo and
<jbophrase>bridi</jbophrase> is a brivla. Either of the first two pronunciations is permitted: no primary stress on either syllable of
- <jbophrase>e'u</jbophrase>, or primary stress on the first syllable. The third pronunciation, which places primary stress on the second syllable of the cmavo, requires that - since the following word is a brivla - the two words must be separated by a pause. Consider the following two cases:</para>
+ <jbophrase>e'u</jbophrase>, or primary stress on the first syllable. The third pronunciation, which places primary stress on the second syllable of the cmavo, requires that – since the following word is a brivla – the two words must be separated by a pause. Consider the following two cases:</para>
<example xml:id="example-random-id-qIXo" role="pronunciation-example">
<title>
<anchor xml:id="c3e9d14"/>
</title>
<pronunciation>
<jbo>le re nobli prenu</jbo>
<jbo role="pronunciation">le re NObli PREnu</jbo>
</pronunciation>
</example>
<example xml:id="example-random-id-qiXR" role="pronunciation-example">
diff --git a/todocbook/4.xml b/todocbook/4.xml
index d4b6789..9e54728 100644
--- a/todocbook/4.xml
+++ b/todocbook/4.xml
@@ -112,21 +112,21 @@
</programlisting></para>
</listitem>
<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-section-clusters"/>. In brief, any consonant pair is permissible unless it: contains two identical letters, contains both a voiced (excluding <jbophrase role="letteral">r</jbophrase>, <jbophrase role="letteral">l</jbophrase>, <jbophrase role="letteral">m</jbophrase>, <jbophrase role="letteral">n</jbophrase>) and an unvoiced consonant, or is one of certain specified forbidden pairs.
</para>
</listitem>
<listitem>
<para> <indexterm type="general-imported"><primary>C/CC string</primary><secondary>as a symbol for a consonant triple</secondary></indexterm> C/CC represents a consonant triple. The first two consonants must constitute a permissible consonant pair; the last two consonants must constitute a permissible initial consonant pair.</para>
</listitem>
</orderedlist>
- <para> <indexterm type="general-imported"><primary>brivla</primary><secondary>as one of the 3 basic word classes</secondary></indexterm> <indexterm type="general-imported"><primary>cmene</primary><secondary>as one of the 3 basic word classes</secondary></indexterm> <indexterm type="general-imported"><primary>cmavo</primary><secondary>as one of the 3 basic word classes</secondary></indexterm> <indexterm type="general-imported"><primary>parts of speech</primary></indexterm> <indexterm type="general-imported"><primary>word classes</primary></indexterm> Lojban has three basic word classes - parts of speech - in contrast to the eight that are traditional in English. These three classes are called cmavo, brivla, and cmene. Each of these classes has uniquely identifying properties - an arrangement of letters that allows the word to be uniquely and unambiguously recognized as a separate word in a string of Lojban, upon either reading or hearing, and as belonging to a specific word-class.</para>
+ <para> <indexterm type="general-imported"><primary>brivla</primary><secondary>as one of the 3 basic word classes</secondary></indexterm> <indexterm type="general-imported"><primary>cmene</primary><secondary>as one of the 3 basic word classes</secondary></indexterm> <indexterm type="general-imported"><primary>cmavo</primary><secondary>as one of the 3 basic word classes</secondary></indexterm> <indexterm type="general-imported"><primary>parts of speech</primary></indexterm> <indexterm type="general-imported"><primary>word classes</primary></indexterm> Lojban has three basic word classes – parts of speech – in contrast to the eight that are traditional in English. These three classes are called cmavo, brivla, and cmene. Each of these classes has uniquely identifying properties – an arrangement of letters that allows the word to be uniquely and unambiguously recognized as a separate word in a string of Lojban, upon either reading or hearing, and as belonging to a specific word-class.</para>
<para>They are also functionally different: cmavo are the structure words, corresponding to English words like
<quote>and</quote>,
<quote>if</quote>,
<quote>the</quote> and
<quote>to</quote>; brivla are the content words, corresponding to English words like
<quote>come</quote>,
<quote>red</quote>,
@@ -346,21 +346,21 @@
<para>This would probably be the most common usage.</para>
</section>
<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>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>
@@ -514,21 +514,21 @@
<jbo>ninmu</jbo>
<en>woman</en>
</interlinear-gloss>
</example>
<para>A small number of gismu were formed differently; see
<xref linkend="section-cultural-gismu"/> for a list.</para>
</section>
<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>
+ <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>
@@ -670,21 +670,21 @@
<jbophrase role="letteral">r</jbophrase> making up the
<jbophrase role="morphology">rs</jbophrase> consonant pair needed to make the word a brivla. Without the
<jbophrase role="letteral">r</jbophrase>, the word would break up into
<jbophrase>soi sai</jbophrase>, 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="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
+ <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="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>
@@ -758,21 +758,21 @@
<jbophrase>zmadu</jbophrase>, corresponding in general to English comparative adjectives ending in
<quote>-er</quote> such as
<quote>whiter</quote> (Lojban
<jbophrase>labmau</jbophrase>). On the other hand,
<jbophrase>bakri</jbophrase> (
<quote>chalk</quote>) has no short rafsi and few lujvo.</para>
<para>There are at most one CVC-form, one CCV-form, and one CVV-form rafsi per gismu. In fact, only a tiny handful of gismu have both a CCV-form and a CVV-form rafsi assigned, and still fewer have all three forms of short rafsi. However, gismu with both a CVC-form and another short rafsi are fairly common, partly because more possible CVC-form rafsi exist. Yet CVC-form rafsi, even though they are fairly easy to remember, cannot be used at the end of a lujvo (because lujvo must end in vowels), so justifying the assignment of an additional short rafsi to many gismu.</para>
<para> <indexterm type="general-imported"><primary>rafsi</primary><secondary>rationale for assignments of</secondary></indexterm> <indexterm type="general-imported"><primary>rafsi space</primary></indexterm> The intention was to use the available
- <quote>rafsi space</quote>- the set of all possible short rafsi forms - in the most efficient way possible; the goal is to make the most-used lujvo as short as possible (thus maximizing the use of short rafsi), while keeping the rafsi very recognizable to anyone who knows the source gismu. For this reason, the letters in a rafsi have always been chosen from among the five letters of the corresponding gismu. As a result, there are a limited set of short rafsi available for assignment to each gismu. At most seven possible short rafsi are available for consideration (of which at most three can be used, as explained above).</para>
+ <quote>rafsi space</quote>- the set of all possible short rafsi forms – in the most efficient way possible; the goal is to make the most-used lujvo as short as possible (thus maximizing the use of short rafsi), while keeping the rafsi very recognizable to anyone who knows the source gismu. For this reason, the letters in a rafsi have always been chosen from among the five letters of the corresponding gismu. As a result, there are a limited set of short rafsi available for assignment to each gismu. At most seven possible short rafsi are available for consideration (of which at most three can be used, as explained above).</para>
<para> <indexterm type="general-imported"><primary>rafsi</primary><secondary>possible forms for construction of</secondary></indexterm> Here are the only short rafsi forms that can possibly exist for gismu of the form CVC/CV, like <jbophrase>sakli</jbophrase>. The digits in the second column represent the gismu letters used to form the rafsi.</para>
<informaltable>
<tgroup cols="3">
<colspec colnum="1" colname="col1"/>
<colspec colnum="2" colname="col2"/>
<colspec colnum="3" colname="col3"/>
<tbody>
@@ -935,21 +935,21 @@
<example xml:id="example-random-id-qJDg" role="lujvo-example">
<title>
<anchor xml:id="c4e6d11"/>
</title>
<lujvo>
<jbo>lerste</jbo>
<veljvo>from <jbophrase>lerfu liste</jbophrase></veljvo>
<gloss><quote>letter list</quote> or a <quote>list of letters</quote></gloss>
</lujvo>
</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</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 role="letteral">y</jbophrase> or one of the consonants
<jbophrase role="letteral">r</jbophrase> and
<jbophrase role="letteral">n</jbophrase>. (The letter
<jbophrase role="letteral">l</jbophrase> can also be a hyphen, but is not used as one in lujvo.)</para>
<para> <indexterm type="general-imported"><primary>lujvo form</primary><secondary>requirements for y-hyphen insertion in</secondary></indexterm> The
<jbophrase role="letteral">y-</jbophrase>hyphen is used after a CVC-form rafsi when joining it with the following rafsi could result in an impermissible consonant pair, or when the resulting lujvo could fall apart into two or more words (either cmavo or gismu).</para>
<para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>and consonant pairs</secondary></indexterm> Thus, the tanru
@@ -1118,21 +1118,21 @@
<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="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>
+ <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:
<jbophrase>spraile</jbophrase> is acceptable, but not
<jbophrase valid="false">ktraile</jbophrase> or
<jbophrase valid="false">trkaile</jbophrase>;</para>
</listitem>
<listitem>
<para>must end in one or more vowels;</para>
</listitem>
@@ -1304,21 +1304,21 @@
<quote>letter</quote>). Note the l-hyphen in "lerldjamo", since "lerndjamo" contains the forbidden cluster "ndj".</para>
<para> <indexterm type="general-imported"><primary>fu'ivla categorizer</primary><secondary>for distinguishing fu'ivla form</secondary></indexterm> <indexterm type="general-imported"><primary>fu'ivla</primary><secondary>disambiguation of</secondary></indexterm> The use of the prefix helps distinguish among the many possible meanings of the borrowed word, depending on the field. As it happens,
<jbophrase>spageti</jbophrase> and
<jbophrase>kuarka</jbophrase> are valid Stage 4 fu'ivla, but
<jbophrase valid="false">xaceru</jbophrase> looks like a compound cmavo, and
<jbophrase valid="false">kobra</jbophrase> like a gismu.</para>
<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
- <jbophrase>integrale</jbophrase>, 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
+ <jbophrase>integrale</jbophrase>, 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,
<jbophrase>integrale</jbophrase> 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> <!-- 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 role="letteral">i</jbophrase> of
<jbophrase>integrale</jbophrase> is removed, or something like
@@ -1926,22 +1926,22 @@
</listitem>
</orderedlist>
</section>
<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="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="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>
+ <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="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
<jbophrase>za'e</jbophrase> (explained in
<xref linkend="chapter-structure-section-bahe"/>) 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>
@@ -1994,22 +1994,22 @@
<para>Put a
<jbophrase role="letteral">y-</jbophrase>hyphen between the consonants of any impermissible consonant pair. This will always appear between rafsi.</para>
</listitem>
<listitem>
<para> <indexterm type="general-imported"><primary>tosmabru test</primary></indexterm> Put a
<jbophrase role="letteral">y-</jbophrase>hyphen after any 4-letter rafsi form.</para>
</listitem>
</orderedlist>
</listitem>
<listitem>
- <para>Test all forms with one or more initial CVC-form rafsi - with the pattern
- <quote>CVC ... CVC + X</quote> - for
+ <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 role="letteral">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>
<orderedlist>
<listitem>
<para>Examine all the C/C consonant pairs up to the first <jbophrase role="letteral">y-</jbophrase>hyphen, or up to the end of the word in case there are no <jbophrase role="letteral">y-</jbophrase>hyphens.</para>
<para>These consonant pairs are called "joints”.</para>
</listitem>
<listitem>
<para>If all of those joints are permissible initials, then the trial word will break up into a cmavo and a shorter brivla. If not, the word will not break up, and no further hyphens are needed.</para>
diff --git a/todocbook/5.xml b/todocbook/5.xml
index d19c8ea..69c9bb2 100644
--- a/todocbook/5.xml
+++ b/todocbook/5.xml
@@ -327,21 +327,21 @@
</title>
<interlinear-gloss>
<jbo>ta cmalu nixli ckule</jbo>
<gloss>That is-a-small girl school.</gloss>
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>tanru</primary><secondary>default left-grouping of</secondary></indexterm> <indexterm type="general-imported"><primary>left-grouping rule</primary><secondary>definition of</secondary></indexterm> The rules of Lojban do not leave this sentence ambiguous, as the rules of English do with
<xref linkend="example-random-id-gCLr"/>. The choice made by the language designers is to say that
<xref linkend="example-random-id-9FPm"/> means the same as
<xref linkend="example-random-id-jquh"/>. This is true no matter what three brivla are used: the leftmost two are always grouped together. This rule is called the
- <quote>left-grouping rule</quote>. Left-grouping in seemingly ambiguous structures is quite common - though not universal - in other contexts in Lojban.</para>
+ <quote>left-grouping rule</quote>. Left-grouping in seemingly ambiguous structures is quite common – though not universal – in other contexts in Lojban.</para>
<para>Another way to express the English meaning of
<xref linkend="example-random-id-nwuU"/> and
<xref linkend="example-random-id-jquh"/>, using parentheses to mark grouping, is:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-ERBx">
<title>
<anchor xml:id="c5e3d7"/>
</title>
<interlinear-gloss>
<jbo>ta cmalu [] nixli bo ckule</jbo>
<gloss>That is-a-small type-of (girl type-of school).</gloss>
@@ -390,22 +390,22 @@
</example>
<para>In
<xref linkend="example-random-id-m5SD"/>, the selbri is a tanru with seltau
<jbophrase>mutce bo barda</jbophrase> and tertau
<jbophrase>gerku bo kavbu</jbophrase>. It is worth emphasizing once again that this tanru has the same fundamental ambiguity as all other Lojban tanru: the sense in which the
<quote>dog type-of capturer</quote> is said to be
<quote>very type-of large</quote> is not precisely specified. Presumably it is his body which is large, but theoretically it could be one of his other properties.</para>
<para> <indexterm type="general-imported"><primary>pretty</primary><secondary>English ambiguity of</secondary></indexterm> We will now justify the title of this chapter by exploring the ramifications of the phrase
<quote>pretty little girls' school</quote>, an expansion of the tanru used in
- <xref linkend="section-three-part-tanru"/> to four brivla. (Although this example has been used in the Loglan Project almost since the beginning - it first appeared in Quine's book
- <citation>Word and Object</citation> (1960) - it is actually a mediocre example because of the ambiguity of English
+ <xref linkend="section-three-part-tanru"/> to four brivla. (Although this example has been used in the Loglan Project almost since the beginning – it first appeared in Quine's book
+ <citation>Word and Object</citation> (1960) – it is actually a mediocre example because of the ambiguity of English
<quote>pretty</quote>; it can mean
<quote>beautiful</quote>, the sense intended here, or it can mean
<quote>very</quote>. Lojban
<jbophrase>melbi</jbophrase> is not subject to this ambiguity: it means only
<quote>beautiful</quote>.)</para>
<para>Here are four ways to group this phrase:</para>
<example xml:id="example-random-id-qjmr" role="interlinear-gloss-example">
<title>
<anchor xml:id="c5e4d2"/>
</title>
@@ -720,21 +720,21 @@
<anchor xml:id="c5e6d7"/>
</title>
<interlinear-gloss>
<jbo>ta blanu je zdani</jbo>
<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> 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>
@@ -1271,21 +1271,21 @@
</interlinear-gloss>
</example>
<para>
<xref linkend="example-random-id-qjVx"/> is a less deeply nested construction, requiring fewer cmavo. As a result it is probably easier to understand.</para>
<para> Note that in Lojban
<quote>trying to go</quote> is expressed using
<jbophrase>troci</jbophrase> as the tertau. The reason is that
<quote>trying to go</quote> is a
<quote>going type of trying</quote>, not a
- <quote>trying type of going</quote>. The trying is more fundamental than the going - if the trying fails, we may not have a going at all.</para>
+ <quote>trying type of going</quote>. The trying is more fundamental than the going – if the trying fails, we may not have a going at all.</para>
<para> <indexterm type="general-imported"><primary>inverted tanru</primary><secondary>effect on sumti after the selbri</secondary></indexterm> <indexterm type="general-imported"><primary>inverted tanru</primary><secondary>effect on sumti before the selbri</secondary></indexterm> <indexterm type="general-imported"><primary>unfilled places of inverted tanru</primary></indexterm> Any sumti which precede a selbri with an inverted tanru fill the places of the selbri (i.e., the places of the tertau) in the ordinary way. In
<xref linkend="example-random-id-qjVx"/>,
<jbophrase>mi</jbophrase> fills the x1 place of
<jbophrase>troci co klama</jbophrase>, which is the x1 place of
<jbophrase>troci</jbophrase>. The other places of the selbri remain unfilled. The trailing sumti
<jbophrase>le zarci</jbophrase> and
<jbophrase>le zdani</jbophrase> do not occupy selbri places, despite appearances.</para>
<para>As a result, the regular mechanisms (involving selma'o VOhA and GOhI, explained in
<xref linkend="chapter-anaphoric-cmavo"/>) for referring to individual sumti of a bridi cannot refer to any of the trailing places of
@@ -1965,21 +1965,21 @@
<para>However, if we place a
<jbophrase>na'e</jbophrase> at the beginning of the selbri in both
<xref linkend="example-random-id-qjyW"/> and
<xref linkend="example-random-id-qjyy"/>, we get different results:</para>
<example xml:id="example-random-id-qjyz" role="interlinear-gloss-example">
<title>
<anchor xml:id="c5e12d8"/>
</title>
<interlinear-gloss>
<jbo>mi na'e sutra cadzu be fi le birka be'o je masno klama le zarci</jbo>
- <gloss>I ( (non- quickly) – (walking using the arms) and slowly) go-to the market.</gloss>
+ <gloss>I ( (non- quickly) - (walking using the arms) and slowly) go-to the market.</gloss>
<en>I go to the market, both walking using my arms other than quickly, and also slowly.</en>
</interlinear-gloss>
</example>
<example xml:id="example-random-id-qJzr" role="interlinear-gloss-example">
<title>
<anchor xml:id="c5e12d9"/>
</title>
<interlinear-gloss>
<jbo>mi na'e ke sutra cadzu be fi le birka [be'o] ke'e je masno klama le zarci</jbo>
<gloss>I (non-(quickly (walking using the arms) ) and slowly) go-to the market.</gloss>
@@ -3722,21 +3722,21 @@
<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, <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>
+ <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>
<jbo>melbi cmalu nixli ckule</jbo>
<gloss>((pretty type-of little) type-of girl) type-of school</gloss>
<en>school for girls who are beautifully small</en>
</interlinear-gloss>
</example>
diff --git a/todocbook/6.xml b/todocbook/6.xml
index caef939..ffce490 100644
--- a/todocbook/6.xml
+++ b/todocbook/6.xml
@@ -424,21 +424,21 @@
<en>The lion dwells in Africa.</en>
<en>Lions dwell in Africa.</en>
</interlinear-gloss>
</example>
<para><indexterm type="general-imported"><primary>loi</primary><secondary>contrasted with lei in specificity</secondary></indexterm> <indexterm type="general-imported"><primary>lei</primary><secondary>contrasted with loi in specificity</secondary></indexterm> The difference between
<jbophrase>lei</jbophrase> and
<jbophrase>loi</jbophrase> is that
<jbophrase>lei cinfo</jbophrase> refers to a mass of specific individuals which the speaker calls lions, whereas
<jbophrase>loi cinfo</jbophrase> refers to some part of the mass of all those individuals which actually are lions. The restriction to
<quote>some part of the mass</quote> allows statements like
- <xref linkend="example-random-id-T1pF"/> to be true even though some lions do not dwell in Africa - they live in various zoos around the world. On the other hand,
+ <xref linkend="example-random-id-T1pF"/> to be true even though some lions do not dwell in Africa – they live in various zoos around the world. On the other hand,
<xref linkend="example-random-id-T1pF"/> doesn't actually say that most lions live in Africa: equally true is</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-JzXc">
<title>
<indexterm type="example-imported"><primary>Englishman in Africa</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c6e3d4"/>
</title>
<interlinear-gloss>
<jbo>loi glipre cu xabju le fi'ortu'a</jbo>
<gloss>Part-of-the-mass-of-those-which-really are-English-persons dwell in-the African-land.</gloss>
<en>The English dwell in Africa.</en>
@@ -509,21 +509,21 @@
<selmaho>LE</selmaho>
<description>the set of those which really are</description>
</cmavo-entry>
<cmavo-entry>
<cmavo>la'i</cmavo>
<selmaho>LA</selmaho>
<description>the set of those named</description>
</cmavo-entry>
</cmavo-list>
<para> <indexterm type="general-imported"><primary>mass</primary><secondary>compared with set as abstract of multiple individuals</secondary></indexterm> <indexterm type="general-imported"><primary>set</primary><secondary>compared with mass as abstract of multiple individuals</secondary></indexterm> <indexterm type="general-imported"><primary>mass</primary><secondary>contrasted with set in attribution of component properties</secondary></indexterm> <indexterm type="general-imported"><primary>set</primary><secondary>contrasted with mass in attribution of component properties</secondary></indexterm> Having said so much about masses, let us turn to sets. Sets are easier to understand than masses, but are more rarely used. Like a mass, a set is an abstract object formed from a number of individuals; however, the properties of a set are not derived from any of the properties of the individuals that compose it.</para>
- <para><indexterm type="general-imported"><primary>la'i</primary><secondary>as set counterpart of lai</secondary></indexterm> <indexterm type="general-imported"><primary>lo'i</primary><secondary>as set counterpart of loi</secondary></indexterm> <indexterm type="general-imported"><primary>le'i</primary><secondary>as set counterpart of lei</secondary></indexterm> <indexterm type="general-imported"><primary>sets</primary><secondary>properties of</secondary></indexterm> <indexterm type="general-imported"><primary>cardinality</primary><secondary>definition</secondary></indexterm> <indexterm type="general-imported"><primary>cardinality</primary><secondary>property of sets</secondary></indexterm> <indexterm type="general-imported"><primary>membership</primary><secondary>property of sets</secondary></indexterm> <indexterm type="general-imported"><primary>inclusion</primary><secondary>property of sets</secondary></indexterm> Sets have properties like cardinality (how many elements in the set), membership (the relationship between a set and its elements), and set inclusion (the relationship between two sets, one of which - the superset – contains all the elements of the other - the subset). The set descriptors
+ <para><indexterm type="general-imported"><primary>la'i</primary><secondary>as set counterpart of lai</secondary></indexterm> <indexterm type="general-imported"><primary>lo'i</primary><secondary>as set counterpart of loi</secondary></indexterm> <indexterm type="general-imported"><primary>le'i</primary><secondary>as set counterpart of lei</secondary></indexterm> <indexterm type="general-imported"><primary>sets</primary><secondary>properties of</secondary></indexterm> <indexterm type="general-imported"><primary>cardinality</primary><secondary>definition</secondary></indexterm> <indexterm type="general-imported"><primary>cardinality</primary><secondary>property of sets</secondary></indexterm> <indexterm type="general-imported"><primary>membership</primary><secondary>property of sets</secondary></indexterm> <indexterm type="general-imported"><primary>inclusion</primary><secondary>property of sets</secondary></indexterm> Sets have properties like cardinality (how many elements in the set), membership (the relationship between a set and its elements), and set inclusion (the relationship between two sets, one of which – the superset – contains all the elements of the other – the subset). The set descriptors
<jbophrase>le'i</jbophrase>,
<jbophrase>lo'i</jbophrase> and
<jbophrase>la'i</jbophrase> correspond exactly to the mass descriptors
<jbophrase>lei</jbophrase>,
<jbophrase>loi</jbophrase>, and
<jbophrase>lai</jbophrase> except that normally we talk of the whole of a set, not just part of it. Here are some examples contrasting
<jbophrase>lo</jbophrase>,
@@ -555,41 +555,41 @@
<example xml:id="example-random-id-qL3V" role="interlinear-gloss-example">
<title>
<anchor xml:id="c6e4d3"/>
</title>
<interlinear-gloss>
<jbo>lo'i ratcu cu barda</jbo>
<gloss>The-set-of rats is-large.</gloss>
<en>There are a lot of rats.</en>
</interlinear-gloss>
</example>
- <para>The mass of rats is small because at least one rat is small; the mass of rats is also large; the set of rats, though, is unquestionably large - it has billions of members. The mass of rats is also brown, since some of its components are; but it would be incorrect to call the set of rats brown - brown-ness is not the sort of property that sets possess.</para>
+ <para>The mass of rats is small because at least one rat is small; the mass of rats is also large; the set of rats, though, is unquestionably large – it has billions of members. The mass of rats is also brown, since some of its components are; but it would be incorrect to call the set of rats brown – brown-ness is not the sort of property that sets possess.</para>
<para> <indexterm type="general-imported"><primary>sets</primary><secondary>use in Lojban place structure</secondary></indexterm> Lojban speakers should generally think twice before employing the set descriptors. However, certain predicates have places that require set sumti to fill them. For example, the place structure of
<jbophrase>fadni</jbophrase> is:</para>
<place-structure>x1 is ordinary/common/typical/usual in property x2 among the members of set x3</place-structure>
<para>Why is it necessary for the x3 place of
<jbophrase>fadni</jbophrase> to be a set? Because it makes no sense for an individual to be typical of another individual: an individual is typical of a group. In order to make sure that the bridi containing
<jbophrase>fadni</jbophrase> is about an entire group, its x3 place must be filled with a set:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-xIXo">
<title>
<indexterm type="example-imported"><primary>typical Lojban user</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c6e4d4"/>
</title>
<interlinear-gloss>
<jbo>mi fadni zo'e lo'i lobypli</jbo>
<gloss>I am-ordinary among the-set-of Lojban-users.</gloss>
<en>I am a typical Lojban user.</en>
</interlinear-gloss>
</example>
- <para>Note that the x2 place has been omitted; I am not specifying in exactly which way I am typical - whether in language knowledge, or age, or interests, or something else. If
+ <para>Note that the x2 place has been omitted; I am not specifying in exactly which way I am typical – whether in language knowledge, or age, or interests, or something else. If
<jbophrase>lo'i</jbophrase> were changed to
<jbophrase>lo</jbophrase> in
<xref linkend="example-random-id-xIXo"/>, the meaning would be something like
<quote>I am typical of some Lojban user</quote>, which is nonsense.</para>
</section>
<section xml:id="section-typicals">
<title>Descriptors for typical objects</title>
<para>The following cmavo are discussed in this section:</para>
<cmavo-list>
@@ -701,21 +701,21 @@
<xref linkend="chapter-mekso"/>. For the purposes of this chapter, a simplified treatment will suffice. Our examples will employ either the simple Lojban numbers
<jbophrase>pa</jbophrase>,
<jbophrase>re</jbophrase>,
<jbophrase>ci</jbophrase>,
<jbophrase>vo</jbophrase>, and
<jbophrase>mu</jbophrase>, meaning
<quote>one</quote>,
<quote>two</quote>,
<quote>three</quote>,
<quote>four</quote>,
- <quote>five</quote> respectively, or else one of four special quantifiers, two of which are discussed in this section and listed above. These four quantifiers are important because every Lojban sumti has either one or two of them implicitly present in it - which one or two depends on the particular kind of sumti. There is more explanation of implicit quantifiers later in this section. (The other two quantifiers,
+ <quote>five</quote> respectively, or else one of four special quantifiers, two of which are discussed in this section and listed above. These four quantifiers are important because every Lojban sumti has either one or two of them implicitly present in it – which one or two depends on the particular kind of sumti. There is more explanation of implicit quantifiers later in this section. (The other two quantifiers,
<jbophrase>piro</jbophrase> and
<jbophrase>pisu'o</jbophrase>, are explained in
<xref linkend="section-quantified-descriptions"/>.)</para>
<para>Every Lojban sumti may optionally be preceded by an explicit quantifier. The purpose of this quantifier is to specify how many of the things referred to by the sumti are being talked about. Here are some simple examples contrasting sumti with and without explicit quantifiers:</para>
<example xml:id="example-random-id-qL61" role="interlinear-gloss-example">
<title>
<anchor xml:id="c6e6d1"/>
</title>
<interlinear-gloss>
@@ -890,21 +890,21 @@
<anchor xml:id="c6e7d3"/>
</title>
<interlinear-gloss>
<jbo>le ci gerku cu blabi</jbo>
<gloss>The three dogs are-white.</gloss>
<en>The three dogs are white.</en>
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>outer quantifier</primary><secondary>implicit on descriptors</secondary></indexterm> <indexterm type="general-imported"><primary>inner quantifier</primary><secondary>implicit on descriptors</secondary></indexterm> <indexterm type="general-imported"><primary>descriptors</primary><secondary>implicit quantifiers for</secondary></indexterm> There are rules for each of the 11 descriptors specifying what the implicit values for the inner and outer quantifiers are. They are meant to provide sensible default values when context is absent, not necessarily to prescribe hard and fast rules. The following table lists the implicit values:</para>
- <!--This stuff was here before, not sure what it means - zort-->
+ <!--This stuff was here before, not sure what it means – zort-->
<!--<lx "le"> XE "le" -->
<!--<lx "ro"> XE "ro" -->
<!--<lx "su'o"> XE "su'o" -->
<!--<lx "lo"> XE "lo" <dl compact><p>-->
<!--<lx "la"> XE "la" <dl compact><p>-->
<!--<lx "lei"> XE "lei" <dl compact><p>-->
<!--<lx "loi"> XE "loi" <dl compact><p>-->
<!--<lx "lai"> XE "lai" <dl compact><p>-->
<!--<lx "le'i"> XE "le'i" <dl compact><p>-->
<!--<lx "lo'i"> XE "lo'i" <dl compact><p>-->
@@ -988,31 +988,31 @@
<para> <indexterm type="general-imported"><primary>le-series cmavo</primary><secondary>rule for implicit inner quantifier</secondary></indexterm> <indexterm type="general-imported"><primary>lo-series cmavo</primary><secondary>rule for implicit inner quantifier</secondary></indexterm> The rule for the inner quantifier is very simple: the lo-series cmavo (namely,
<jbophrase>lo</jbophrase>,
<jbophrase>loi</jbophrase>,
<jbophrase>lo'i</jbophrase>, and
<jbophrase>lo'e</jbophrase>) all have an implicit inner quantifier of
<jbophrase>ro</jbophrase>, whereas the le-series cmavo all have an implicit inner quantifier of
<jbophrase>su'o</jbophrase>.</para>
- <para> <indexterm type="general-imported"><primary>le-series cmavo</primary><secondary>rationale for implicit inner quantifier</secondary></indexterm> <indexterm type="general-imported"><primary>lo-series cmavo</primary><secondary>rationale for implicit inner quantifier</secondary></indexterm> Why? Because lo-series descriptors always refer to all of the things which really fit into the x1 place of the selbri. They are not restricted by the speaker's intention. Descriptors of the le-series, however, are so restricted, and therefore talk about some number, definite or indefinite, of objects the speaker has in mind - but never less than one.</para>
+ <para> <indexterm type="general-imported"><primary>le-series cmavo</primary><secondary>rationale for implicit inner quantifier</secondary></indexterm> <indexterm type="general-imported"><primary>lo-series cmavo</primary><secondary>rationale for implicit inner quantifier</secondary></indexterm> Why? Because lo-series descriptors always refer to all of the things which really fit into the x1 place of the selbri. They are not restricted by the speaker's intention. Descriptors of the le-series, however, are so restricted, and therefore talk about some number, definite or indefinite, of objects the speaker has in mind – but never less than one.</para>
<para><indexterm type="general-imported"><primary>masses</primary><secondary>rule for implicit outer quantifier</secondary></indexterm> <indexterm type="general-imported"><primary>sets</primary><secondary>rule for implicit outer quantifier</secondary></indexterm> Understanding the implicit outer quantifier requires rules of greater subtlety. In the case of mass and set descriptors, a single rule suffices for each: reference to a mass is implicitly a reference to some part of the mass; reference to a set is implicitly a reference to the whole set. Masses and sets are inherently singular objects: it makes no sense to talk about two distinct masses with the same components, or two distinct sets with the same members. Therefore, the largest possible outer quantifier for either a set description or a mass description is
<jbophrase>piro</jbophrase>, the whole of it.</para>
<para> <indexterm type="general-imported"><primary>plural masses</primary><secondary>possible use for</secondary></indexterm> (Pedantically, it is possible that the mass of water molecules composing an ice cube might be thought of as different from the same mass of water molecules in liquid form, in which case we might talk about
<jbophrase>re lei djacu</jbophrase>, two masses of the water-bits I have in mind.)</para>
<para><indexterm type="general-imported"><primary>pisu'o</primary><secondary>explanation of meaning</secondary></indexterm> <indexterm type="general-imported"><primary>piro</primary><secondary>explanation of meaning</secondary></indexterm> Why
<jbophrase>pi</jbophrase>? It is the Lojban cmavo for the decimal point. Just as
<jbophrase>pimu</jbophrase> means
<quote><inlineequation><mathphrase>.5</mathphrase></inlineequation></quote>, and when used as a quantifier specifies a portion consisting of five tenths of a thing,
- <jbophrase>piro</jbophrase> means a portion consisting of the all-ness – the entirety - of a thing. Similarly,
+ <jbophrase>piro</jbophrase> means a portion consisting of the all-ness – the entirety – of a thing. Similarly,
<jbophrase>pisu'o</jbophrase> specifies a portion consisting of at least one part of a thing, i.e. some of it.</para>
<para> <indexterm type="general-imported"><primary>portion</primary><secondary>on set contrasted with on individual</secondary></indexterm> <indexterm type="general-imported"><primary>outer quantifiers</primary><secondary>for expressing subsets</secondary></indexterm> <indexterm type="general-imported"><primary>subsets</primary><secondary>expressing with outer quantifiers</secondary></indexterm> Smaller quantifiers are possible for sets, and refer to subsets. Thus
<jbophrase>pimu le'i nanmu</jbophrase> is a subset of the set of men I have in mind; we don't know precisely which elements make up this subset, but it must have half the size of the full set. This is the best way to say
<quote>half of the men</quote>; saying
<jbophrase>pimu le nanmu</jbophrase> would give us a half-portion of one of them instead! Of course, the result of
<jbophrase>pimu le'i nanmu</jbophrase> is still a set; if you need to refer to the individuals of the subset, you must say so (see
<jbophrase>lu'a</jbophrase> in
@@ -1101,21 +1101,21 @@
</example>
<para> <indexterm type="general-imported"><primary>indefinite description</primary><secondary>definition</secondary></indexterm> <indexterm type="general-imported"><primary>omission of descriptor</primary><secondary>effect on ku</secondary></indexterm> <indexterm type="general-imported"><primary>ku</primary><secondary>effect on of omitting descriptor</secondary></indexterm> is equivalent in meaning to
<xref linkend="example-random-id-gr7Y"/>. Even though the descriptor is not present, the elidable terminator
<jbophrase>ku</jbophrase> may still be used. The name
<quote>indefinite description</quote> for this syntactic form is historically based: of course, it is no more and no less indefinite than its counterpart with an explicit
<jbophrase>lo</jbophrase>. Indefinite descriptions were introduced into the language in order to imitate the syntax of English and other natural languages.</para>
<para> <indexterm type="general-imported"><primary>inner quantifier</primary><secondary>in indefinite description</secondary></indexterm> <indexterm type="general-imported"><primary>outer quantifier</primary><secondary>in indefinite description</secondary></indexterm> <indexterm type="general-imported"><primary>indefinite description</primary><secondary>as prohibiting explicit inner quantifier</secondary></indexterm> <indexterm type="general-imported"><primary>indefinite description</primary><secondary>as needing explicit outer quantifier</secondary></indexterm> Indefinite descriptions must fit this mold exactly: there is no way to make one which does not have an explicit outer quantifier (thus
<jbophrase valid="false">*gerku cu blabi</jbophrase> is ungrammatical), or which has an explicit inner quantifier (thus
- <jbophrase valid="false">*reboi ci gerku cu blabi</jbophrase> is also ungrammatical -
+ <jbophrase valid="false">*reboi ci gerku cu blabi</jbophrase> is also ungrammatical –
<jbophrase>re ci gerku cu blabi</jbophrase> is fine, but means
<quote>23 dogs are white</quote>).</para>
<para>Note:
<xref linkend="example-random-id-gLpy"/> also contains an indefinite description, namely
<jbophrase>su'o ci cutci</jbophrase>; another version of that example using an explicit
<jbophrase>lo</jbophrase> would be:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-SMvA">
<title>
@@ -1127,21 +1127,21 @@
<en>I own three (or more) shoes.</en>
</interlinear-gloss>
</example>
</section>
<section xml:id="section-sumti-based-descriptions">
<title>sumti-based descriptions</title>
<para>As stated in
<xref linkend="section-basic-descriptors"/>, 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="chapter-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>
- <para> <indexterm type="general-imported"><primary>sumti-based description</primary><secondary>outer quantifier on</secondary></indexterm> <indexterm type="general-imported"><primary>sumti-based description</primary><secondary>inner quantifier on</secondary></indexterm> <indexterm type="general-imported"><primary>sumti-based description</primary><secondary>definition</secondary></indexterm> 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>
+ <para> <indexterm type="general-imported"><primary>sumti-based description</primary><secondary>outer quantifier on</secondary></indexterm> <indexterm type="general-imported"><primary>sumti-based description</primary><secondary>inner quantifier on</secondary></indexterm> <indexterm type="general-imported"><primary>sumti-based description</primary><secondary>definition</secondary></indexterm> 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>
<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 xml:id="example-random-id-qLaQ" role="interlinear-gloss-example">
<title> <!-- FIXME: this indexterm matches two examples -->
<indexterm type="example-imported"><primary>the two of you</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c6e9d1"/>
</title>
<interlinear-gloss>
<jbo>re do cu nanmu</jbo>
<gloss>Two-of you are-men.</gloss>
diff --git a/todocbook/7.xml b/todocbook/7.xml
index b197d62..ee488ac 100644
--- a/todocbook/7.xml
+++ b/todocbook/7.xml
@@ -1041,21 +1041,21 @@
<xref linkend="example-random-id-qdCR"/> and eliminates any possibility of
<jbophrase>ko'a</jbophrase> being interpreted by the listener as referring to Alice.</para>
<para> <indexterm type="lojban-word-imported"><primary>go'u</primary></indexterm> <indexterm type="lojban-word-imported"><primary>go'a</primary></indexterm> <indexterm type="general-imported"><primary>answers</primary><secondary>go'i for yes/no questions</secondary></indexterm> <indexterm type="general-imported"><primary>questions</primary><secondary>answering with go'i</secondary></indexterm> <indexterm type="general-imported"><primary>go'i</primary><secondary>as affirmative answer to yes/no question</secondary></indexterm> <indexterm type="general-imported"><primary>go'i-series pro-bridi</primary><secondary>effect of sumti of referent bridi on</secondary></indexterm> <indexterm type="general-imported"><primary>go'i-series pro-bridi</primary><secondary>as main-bridi anaphora only</secondary></indexterm> <indexterm type="general-imported"><primary>go'i-series pro-bridi</primary><secondary>effect of sub-clauses on</secondary></indexterm> <indexterm type="general-imported"><primary>go'i-series pro-bridi</primary><secondary>referent of</secondary></indexterm> <indexterm type="general-imported"><primary>go'i-series pro-bridi</primary><secondary>compared with ri-series pro-sumti in rules of reference</secondary></indexterm> <indexterm type="general-imported"><primary>go'i-series pro-bridi</primary></indexterm> <indexterm type="general-imported"><primary>ri-series pro-sumti</primary></indexterm> <indexterm type="general-imported"><primary>anaphora</primary><secondary>pro-bridi go'i-series as</secondary></indexterm> <indexterm type="general-imported"><primary>anaphora</primary><secondary>pro-sumti ri-series as</secondary></indexterm> <indexterm type="general-imported"><primary>pronouns</primary><secondary>as anaphora</secondary></indexterm> <indexterm type="general-imported"><primary>anaphora</primary><secondary>definition</secondary></indexterm> The cmavo
<jbophrase>go'i</jbophrase>,
<jbophrase>go'a</jbophrase>, and
<jbophrase>go'u</jbophrase> follow exactly the same rules as
<jbophrase>ri</jbophrase>,
<jbophrase>ra</jbophrase>, and
- <jbophrase>ru</jbophrase>, except that they are pro-bridi, and therefore repeat bridi, not sumti - specifically, main sentence bridi. Any bridi that are embedded within other bridi, such as relative clauses or abstractions, are not counted. Like the cmavo of the broda-series, the cmavo of the go'i-series copy all sumti with them. This makes
+ <jbophrase>ru</jbophrase>, except that they are pro-bridi, and therefore repeat bridi, not sumti – specifically, main sentence bridi. Any bridi that are embedded within other bridi, such as relative clauses or abstractions, are not counted. Like the cmavo of the broda-series, the cmavo of the go'i-series copy all sumti with them. This makes
<jbophrase>go'i</jbophrase> by itself convenient for answering a question affirmatively, or for repeating the last bridi, possibly with new sumti:</para>
<example xml:id="example-random-id-qLN4" role="interlinear-gloss-example">
<title>
<anchor xml:id="c7e6d8"/>
</title>
<interlinear-gloss>
<jbo>xu zo djan. cmene do .i go'i</jbo>
<gloss>[True-false?] The-word
<quote>John</quote> is-the-name of you? [repeat last bridi].</gloss>
<en>Is John your name? Yes.</en>
diff --git a/todocbook/8.xml b/todocbook/8.xml
index 9cbb32a..1c01632 100644
--- a/todocbook/8.xml
+++ b/todocbook/8.xml
@@ -556,22 +556,22 @@
<interlinear-gloss>
<jbo>le mi pendo pe le kabri cu cmalu</jbo>
<gloss>My friend associated-with the cup is small.</gloss>
<en>My friend, the one with the cup, is small.</en>
</interlinear-gloss>
</example>
<para> <indexterm type="example-imported"><primary>cup's friend</primary><secondary>example</secondary></indexterm> <indexterm type="example-imported"><primary>friend's cup</primary><secondary>example</secondary></indexterm>
<xref linkend="example-random-id-qMb2"/> is useful in a context which is about my friend, and states that his or her cup is small, whereas
<xref linkend="example-random-id-qmbn"/> is useful in a context that is primarily about a certain cup, and makes a claim about
<quote>my friend of the cup</quote>, as opposed to some other friend of mine. Here the cup appears to
- <quote>possess</quote> the person! English can't even express this relationship with a possessive -
- <quote>the cup's friend of mine</quote> looks like nonsense - but Lojban has no trouble doing so.</para>
+ <quote>possess</quote> the person! English can't even express this relationship with a possessive –
+ <quote>the cup's friend of mine</quote> looks like nonsense – but Lojban has no trouble doing so.</para>
<para><indexterm type="general-imported"><primary>incidental identification</primary><secondary>expressing with no'u</secondary></indexterm> <indexterm type="general-imported"><primary>incidental association</primary><secondary>expressing with ne</secondary></indexterm> <indexterm type="general-imported"><primary>po'u</primary><secondary>compared with no'u</secondary></indexterm> <indexterm type="general-imported"><primary>pe</primary><secondary>compared with ne</secondary></indexterm> <indexterm type="general-imported"><primary>no'u</primary><secondary>compared with po'u</secondary></indexterm> <indexterm type="general-imported"><primary>ne</primary><secondary>compared with pe</secondary></indexterm> Finally, the cmavo
<jbophrase>ne</jbophrase> and
<jbophrase>no'u</jbophrase> stand to
<jbophrase>pe</jbophrase> and
<jbophrase>po'u</jbophrase>, respectively, as
<jbophrase>noi</jbophrase> does to
<jbophrase>poi-</jbophrase> they provide incidental information:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-Arj8">
@@ -949,21 +949,21 @@
<xref linkend="example-random-id-qmdX"/> tell us that one or more persons are going to the market. However, they make very different incidental claims. Now, what does
<jbophrase>lo prenu noi blabi</jbophrase> mean? Well, the default inner quantifier is
<jbophrase>ro</jbophrase> (meaning
<quote>all</quote>), and the default outer quantifier is
<jbophrase>su'o</jbophrase> (meaning
<quote>at least one</quote>). Therefore, we must first take all persons, then choose at least one of them. That one or more people will be going.</para>
<para>In
<xref linkend="example-random-id-qmDS"/>, the relative clause described the sumti once the outer quantifier was applied: one or more people, who are white, are going. But in
<xref linkend="example-random-id-qmdX"/>, the relative clause actually describes the sumti before the outer quantification is applied, so that it ends up meaning
- <quote>First take all persons - by the way, they're all white</quote>. But not all people are white, so the incidental claim being made here is false.</para>
+ <quote>First take all persons – by the way, they're all white</quote>. But not all people are white, so the incidental claim being made here is false.</para>
<para> <indexterm type="general-imported"><primary>relative clauses on lo</primary><secondary>syntax suggestion</secondary></indexterm> The safe strategy, therefore, is to always use
<jbophrase>ku</jbophrase> when attaching a
<jbophrase>noi</jbophrase> relative clause to a
<jbophrase>lo</jbophrase> descriptor. Otherwise we may end up claiming far too much.</para>
<para> <indexterm type="general-imported"><primary>relative clauses and names</primary><secondary>placement considerations</secondary></indexterm> <indexterm type="general-imported"><primary>relative clauses</primary><secondary>on names</secondary></indexterm> <indexterm type="general-imported"><primary>relative clauses</primary><secondary>as part of name</secondary></indexterm> <indexterm type="general-imported"><primary>relative clauses</primary><secondary>impact of la on placement</secondary></indexterm> When the descriptor is
<jbophrase>la</jbophrase>, indicating that what follows is a selbri used for naming, then the positioning of relative clauses has a different significance. A relative clause inside the
<jbophrase>ku</jbophrase>, whether before or after the selbri, is reckoned part of the name; a relative clause outside the
<jbophrase>ku</jbophrase> is not. Therefore,</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-JYj4">
diff --git a/todocbook/9.xml b/todocbook/9.xml
index 74953d9..1f3f14b 100644
--- a/todocbook/9.xml
+++ b/todocbook/9.xml
@@ -765,21 +765,21 @@
<para><indexterm type="general-imported"><primary>BAI modal tags</primary><secondary>rationale for</secondary></indexterm> and almost any selbri which represents an action may need to specify a tool. Having to say
<jbophrase>fi'o se pilno</jbophrase> frequently would make many Lojban sentences unnecessarily verbose and clunky, so an abbreviation is provided in the language design: the compound cmavo
<jbophrase>sepi'o</jbophrase>.</para>
<para> <indexterm type="lojban-word-imported"><primary>SE selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>BAI selma'o</primary></indexterm> <indexterm type="general-imported"><primary>conversion</primary><secondary>of BAI cmavo</secondary></indexterm> <indexterm type="general-imported"><primary>modal tags</primary><secondary>short forms as BAI cmavo</secondary></indexterm> <indexterm type="general-imported"><primary>fi'o constructs</primary><secondary>short forms as BAI cmavo</secondary></indexterm> <indexterm type="general-imported"><primary>BAI selma'o</primary><secondary>as short forms for fi'o constructs</secondary></indexterm> Here
<jbophrase>se</jbophrase> is used before a cmavo, namely
<jbophrase>pi'o</jbophrase>, rather than before a brivla. The meaning of this cmavo, which belongs to selma'o BAI, is exactly the same as that of
<jbophrase>fi'o pilno fe'u</jbophrase>. Since what we want is a tag based on
<jbophrase>se pilno</jbophrase> rather than
- <jbophrase>pilno-</jbophrase> the tool, not the tool user - the grammar allows a BAI cmavo to be converted using a SE cmavo.
+ <jbophrase>pilno-</jbophrase> the tool, not the tool user – the grammar allows a BAI cmavo to be converted using a SE cmavo.
<xref linkend="example-random-id-Lu15"/> may therefore be rewritten as:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-N32m">
<title>
<anchor xml:id="c9e6d1"/>
</title>
<interlinear-gloss>
<jbo>mi viska do sepi'o le zunle kanla</jbo>
<gloss>I see you with-tool: the left eye</gloss>
<en>I see you using my left eye.</en>
@@ -1208,22 +1208,22 @@
<en>I gave the book to John, because John gave money to me.</en>
</interlinear-gloss>
</example>
<para>means the same as:</para>
<para> <indexterm type="lojban-word-imported"><primary>nu'u</primary></indexterm> <indexterm type="lojban-word-imported"><primary>nu'i</primary></indexterm> FIXME: TAG SPOT</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-tFSC">
<title>
<anchor xml:id="c9e8d6"/>
</title>
<interlinear-gloss>
- <jbo>nu'i mu'igi mi le cukta la djan. gi la djan. lei jdini mi nu'u dunda</jbo>
- <gloss>[start] because I, the book, John; John, the-mass-of money, me [end] gives.</gloss>
+ <jbo>nu'i mu'igi la djan. lei jdini mi gi mi le cukta la djan. nu'u dunda</jbo>
+ <gloss>[start] because John, the-mass-of money, me; I, the book, John [end] gives.</gloss>
</interlinear-gloss>
</example>
<para>Here there are three sumti in each half of the termset, because the two bridi share only their selbri.</para>
<para> <indexterm type="general-imported"><primary>bridi-tail modal connection</primary></indexterm> <indexterm type="general-imported"><primary>modal bridi-tail connection</primary></indexterm> <indexterm type="general-imported"><primary>modal connection of selbri</primary><secondary>using bridi-tail modal connection</secondary></indexterm> There is no modal connection between selbri as such: bridi which differ only in the selbri can be modally connected using bridi-tail modal connection. The bridi-tail construct is more fully explained in
<xref linkend="chapter-connectives-section-compound-bridi"/>, but essentially it consists of a selbri with optional sumti following it.
<xref linkend="example-random-id-qMN7"/> is suitable for bridi-tail connection, and could be shortened to:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-Do9b">
<title>
<anchor xml:id="c9e8d7"/>
@@ -1239,21 +1239,21 @@
<title>
<anchor xml:id="c9e8d8"/>
</title>
<interlinear-gloss>
<jbo>mi mu'igi viska gi lebna vau le cukta</jbo>
<gloss>I because saw, therefore took, the book.</gloss>
</interlinear-gloss>
</example>
<para>where
<jbophrase>le cukta</jbophrase> is set off by the non-elidable
- <jbophrase>vau</jbophrase> and is made to belong to both bridi-tails - see
+ <jbophrase>vau</jbophrase> and is made to belong to both bridi-tails – see
<xref linkend="chapter-connectives-section-compound-bridi"/> for more explanations.</para>
<para> <indexterm type="general-imported"><primary>shared bridi-tail sumti</primary><secondary>avoiding</secondary></indexterm> <indexterm type="general-imported"><primary>vau for shared bridi-tail sumti</primary><secondary>avoiding</secondary></indexterm> Since this is a chapter on rearranging sumti, it is worth pointing out that
<xref linkend="example-random-id-YXps"/> can be further rearranged to:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-Pxca">
<title>
<anchor xml:id="c9e8d9"/>
</title>
<interlinear-gloss>
<jbo>mi le cukta mu'igi viska gi lebna</jbo>
<gloss>I, the book, because saw, therefore took.</gloss>
@@ -1456,31 +1456,31 @@
<description>mleca modal</description>
</cmavo-entry>
</cmavo-list>
<para>Relative phrases and clauses are explained in much more detail in
<xref linkend="chapter-relative-clauses"/>. However, there is a construction which combines a modal with a relative phrase which is relevant to this chapter. Consider the following examples of relative clauses:</para>
<example xml:id="example-random-id-qmPP" role="interlinear-gloss-example">
<title>
<anchor xml:id="c9e10d1"/>
</title>
<interlinear-gloss>
- <jbo>la .apasionatas. poi se cusku la .artr. rubnstain. cu se nelci mi</jbo>
+ <jbo>la .apasionatas. ku poi se cusku la .artr. rubnstain. cu se nelci mi</jbo>
<gloss>The Appassionata which is-expressed-by Arthur Rubinstein is-liked-by me.</gloss>
</interlinear-gloss>
</example>
<example xml:id="example-random-id-qmPr" role="interlinear-gloss-example">
<title>
<anchor xml:id="c9e10d2"/>
</title>
<interlinear-gloss>
- <jbo>la .apasionatas. noi se finti la betovn. cu se nelci mi</jbo>
+ <jbo>la .apasionatas. ku noi se finti la betovn. cu se nelci mi</jbo>
<gloss>The Appassionata, which is-created-by Beethoven, is-liked-by me.</gloss>
</interlinear-gloss>
</example>
<para><indexterm type="example-imported"><primary>Beethoven</primary><secondary>example</secondary></indexterm> <indexterm type="example-imported"><primary>Artur Rubenstein</primary><secondary>example</secondary></indexterm> <indexterm type="example-imported"><primary>Appassionata</primary><secondary>example</secondary></indexterm> In
<xref linkend="example-random-id-qmPP"/>,
<jbophrase>la .apasionatas.</jbophrase> refers to a particular performance of the sonata, namely the one performed by Rubinstein. Therefore, the relative clause
<jbophrase>poi se cusku</jbophrase> uses the cmavo
<jbophrase>poi</jbophrase> (of selma'o NOI) to restrict the meaning of
@@ -1495,31 +1495,31 @@
<jbophrase>ne</jbophrase> (of selma'o GOI) are roughly equivalent to
<jbophrase>poi</jbophrase> and
<jbophrase>noi</jbophrase> respectively, but are followed by sumti rather than full bridi. We can abbreviate
<xref linkend="example-random-id-qmPP"/> and
<xref linkend="example-random-id-qmPr"/> to:</para>
<example xml:id="example-random-id-qMq1" role="interlinear-gloss-example">
<title>
<anchor xml:id="c9e10d3"/>
</title>
<interlinear-gloss>
- <jbo>la .apasionatas pe la .artr. rubnstain. se nelci mi</jbo>
+ <jbo>la .apasionatas. ku pe la .artr. rubnstain. se nelci mi</jbo>
<gloss>The Appassionata of Arthur Rubinstein is-liked-by me.</gloss>
</interlinear-gloss>
</example>
<example xml:id="example-random-id-qMQ1" role="interlinear-gloss-example">
<title>
<anchor xml:id="c9e10d4"/>
</title>
<interlinear-gloss>
- <jbo>la .apasionatas ne la betovn. se nelci mi</jbo>
+ <jbo>la .apasionatas. ku ne la betovn. se nelci mi</jbo>
<gloss>The Appassionata, which is of Beethoven, is-liked-by me.</gloss>
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>relative phrases</primary><secondary>contrasted with relative clauses in preciseness</secondary></indexterm> Here the precise selbri of the relative clauses is lost: all we can tell is that the Appassionata is connected in some way with Rubinstein (in
<xref linkend="example-random-id-qMq1"/>) and Beethoven (in
<xref linkend="example-random-id-qMQ1"/>), and that the relationships are respectively restrictive and incidental.</para>
commit 28833950b5bd99b745accaab728a194f2f7eb0ae
Author: Eitan Postavsky <eitanp32@gmail.com>
Date: Wed Jan 26 18:37:41 2011 -0500
Chapter xrefs to chapter-section xrefs where possible.
diff --git a/todocbook/10.xml b/todocbook/10.xml
index 3eead2c..d3e0765 100644
--- a/todocbook/10.xml
+++ b/todocbook/10.xml
@@ -810,21 +810,21 @@
<gloss>The child [movement] [right] walks on the ice in-reference-frame the-x1-place.</gloss>
<en>The child walks toward her right on the ice.</en>
</interlinear-gloss>
</example>
<para> <indexterm type="example-imported"><primary>toward her right</primary><secondary>example</secondary></indexterm>
<xref linkend="example-random-id-mfgA"/> is analogous to
<xref linkend="example-random-id-d8yP"/>. The cmavo
<jbophrase>ma'i</jbophrase> belongs to selma'o BAI (explained in
- <xref linkend="chapter-sumti-tcita"/>), and allows specifying a reference frame.</para>
+ <xref linkend="chapter-sumti-tcita-section-BAI"/>), and allows specifying a reference frame.</para>
<para> <indexterm type="general-imported"><primary>tense</primary><secondary>order of movement specification in</secondary></indexterm> <indexterm type="general-imported"><primary>movement</primary><secondary>order in tense constructs</secondary></indexterm> Both a regular and a
<jbophrase>mo'i</jbophrase>-flagged spatial tense can be combined, with the
<jbophrase>mo'i</jbophrase> construct coming last:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-fusc">
<title>
<anchor xml:id="c10e8d4"/>
</title>
<interlinear-gloss>
<jbo>le verba zu'avu mo'i ri'uvi cadzu le bisli</jbo>
@@ -2230,21 +2230,21 @@
<gloss>I go-to [past] the market [,] the house.</gloss>
</interlinear-gloss>
</example>
<para>Because English does not have any direct way of expressing a tense-like relationship between nouns,
<xref linkend="example-random-id-o3Yg"/> cannot be expressed in English without paraphrasing it either into
<xref linkend="example-random-id-9cXU"/> or else into
<quote>I go to the house before the market</quote>, which is ambiguous - is the market going?</para>
<para> <indexterm type="lojban-word-imported"><primary>gi</primary></indexterm> <indexterm type="general-imported"><primary>bridi-tails</primary><secondary>forethought tense connection of</secondary></indexterm> <indexterm type="general-imported"><primary>imaginary journey</primary><secondary>origin in tense forethought bridi-tail connection</secondary></indexterm> <indexterm type="general-imported"><primary>forethought tense connection of bridi-tails</primary><secondary>order of</secondary></indexterm> Finally, a third forethought construction expresses a tense relationship between bridi-tails rather than whole bridi. (The construct known as a
<quote>bridi-tail</quote> is explained fully in
- <xref linkend="chapter-connectives"/>; roughly speaking, it is a selbri, possibly with following sumti.)
+ <xref linkend="chapter-connectives-section-compound-bridi"/>; roughly speaking, it is a selbri, possibly with following sumti.)
<xref linkend="example-random-id-vSCv"/> is equivalent in meaning to
<xref linkend="example-random-id-9cXU"/> and
<xref linkend="example-random-id-o3Yg"/>:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-vSCv">
<title>
<anchor xml:id="c10e16d8"/>
</title>
<interlinear-gloss>
<jbo>mi pugi klama le zarci gi klama le zdani</jbo>
<gloss>I [past] go-to the market [,] go-to the house.</gloss>
@@ -3259,21 +3259,21 @@
<title>
<anchor xml:id="c10e24d7"/>
</title>
<interlinear-gloss>
<jbo>pu'o</jbo>
<gloss>[inchoative]</gloss>
<en>He hasn't yet done so.</en>
</interlinear-gloss>
</example>
<para>or even the modal reply (from selma'o BAI; see
- <xref linkend="chapter-sumti-tcita"/>):</para>
+ <xref linkend="chapter-sumti-tcita-section-BAI"/>):</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-Vqgy">
<title>
<anchor xml:id="c10e24d8"/>
</title>
<interlinear-gloss>
<jbo>seka'a le briju</jbo>
<gloss>With-destination the office.</gloss>
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>modal-or-tense questions</primary><secondary>pre-specifying some information</secondary></indexterm> <indexterm type="general-imported"><primary>tense-or-modal questions</primary><secondary>pre-specifying some information</secondary></indexterm> <indexterm type="general-imported"><primary>cu'e</primary><secondary>combining with other tense cmavo</secondary></indexterm> The only way to combine
@@ -3309,40 +3309,40 @@
<quote>both</quote>,
<jbophrase>naje</jbophrase> meaning
<quote>the latter</quote>, or
<jbophrase>jenai</jbophrase> meaning
<quote>the former</quote>.</para>
</section>
<section xml:id="section-explicit-magnitudes">
<title>Explicit magnitudes</title>
<para>It is a limitation of the VA and ZI system of specifying magnitudes that they can only prescribe vague magnitudes: small, medium, or large. In order to express both an origin point and an exact distance, the Lojban construction called a
<quote>termset</quote> is employed. (Termsets are explained further in
- <xref linkend="chapter-connectives"/> and
- <xref linkend="chapter-quantifiers"/>.) It is grammatical for a termset to be placed after a tense or modal tag rather than a sumti, which allows both the origin of the imaginary journey and its distance to be specified. Here is an example:</para>
+ <xref linkend="chapter-connectives-section-termsets"/> and
+ <xref linkend="chapter-quantifiers-section-grouping"/>.) It is grammatical for a termset to be placed after a tense or modal tag rather than a sumti, which allows both the origin of the imaginary journey and its distance to be specified. Here is an example:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-7Lys">
<title>
<anchor xml:id="c10e25d1"/>
</title>
<interlinear-gloss>
<jbo>la frank. sanli zu'a nu'i la djordj. la'u lo mitre be li mu [nu'u]</jbo>
<gloss>Frank stands [left] [start termset] George [quantity] a thing-measuring-in-meters the-number 5 [end termset].</gloss>
<en>Frank is standing five meters to the left of George.</en>
</interlinear-gloss>
</example>
<para>Here the termset extends from the
<jbophrase>nu'i</jbophrase> to the implicit
<jbophrase>nu'u</jbophrase> at the end of the sentence, and includes the terms
<jbophrase>la djordj.</jbophrase>, which is the unmarked origin point, and the tagged sumti
<jbophrase>lo mitre be li mu</jbophrase>, which the cmavo
<jbophrase>la'u</jbophrase> (of selma'o BAI, and meaning
<quote>with quantity</quote>; see
- <xref linkend="chapter-sumti-tcita"/>) marks as a quantity. Both terms are governed by the tag
+ <xref linkend="chapter-sumti-tcita-section-BAI"/>) marks as a quantity. Both terms are governed by the tag
<jbophrase>zu'a</jbophrase></para>
<para>It is not necessary to have both an origin point and an explicit magnitude: a termset may have only a single term in it. A less precise version of
<xref linkend="example-random-id-7Lys"/> is:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-RWEE">
<title>
<anchor xml:id="c10e25d2"/>
diff --git a/todocbook/11.xml b/todocbook/11.xml
index e7d6a38..26f0264 100644
--- a/todocbook/11.xml
+++ b/todocbook/11.xml
@@ -928,21 +928,21 @@
</interlinear-gloss>
</example>
<para>because
<xref linkend="example-random-id-AX2I"/> claims that John actually said the quoted words, whereas
<xref linkend="example-random-id-hzd8"/> claims only that he said some words or other which were to the same purpose.</para>
<para> <indexterm type="lojban-word-imported"><primary>lu'e</primary></indexterm>
<jbophrase>le se du'u</jbophrase> is much the same as
<jbophrase>lu'e le du'u</jbophrase>, a symbol for the predication, but
<jbophrase>se du'u</jbophrase> can be used as a selbri, whereas
<jbophrase>lu'e</jbophrase> is ungrammatical in a selbri. (See
- <xref linkend="chapter-sumti"/> for a discussion of
+ <xref linkend="chapter-sumti-section-sumti-qualifiers"/> for a discussion of
<jbophrase>lu'e</jbophrase>.)</para>
</section>
<section xml:id="section-indirect-questions">
<title>Indirect questions</title>
<para>The following cmavo is discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>kau</cmavo>
<selmaho>UI</selmaho>
@@ -1295,22 +1295,22 @@
</interlinear-gloss>
</example>
<para>This must mean that something which John does, or which happens to John, occurs frequently: but without more context there is no way to figure out what. Note that without the
<jbophrase>tu'a</jbophrase>,
<xref linkend="example-random-id-9S5B"/> would mean that John considered as an event frequently occurs - in other words, that John has some sort of on-and-off existence! Normally we do not think of people as events in English, but the x1 place of
<jbophrase>cafne</jbophrase> is an event, and if something that does not seem to be an event is put there, the Lojbanic listener will attempt to construe it as one. (Of course, this analysis assumes that
<jbophrase>djan.</jbophrase> is the name of a person, and not the name of some event.)</para>
<para> <indexterm type="lojban-word-imported"><primary>JAI selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>jai</primary></indexterm> <indexterm type="general-imported"><primary>abstractions</primary><secondary>simplification to sumti with jai</secondary></indexterm> <indexterm type="general-imported"><primary>abstractions</primary><secondary>making concrete</secondary></indexterm> Logically, a counterpart of some sort is needed to
<jbophrase>tu'a</jbophrase> which transposes an abstract sumti into a concrete one. This is achieved at the selbri level by the cmavo
<jbophrase>jai</jbophrase> (of selma'o JAI). This cmavo has more than one function, discussed in
- <xref linkend="chapter-sumti-tcita"/> and
- <xref linkend="chapter-tenses"/>; for the purposes of this chapter, it operates as a conversion of selbri, similarly to the cmavo of selma'o SE. This conversion changes</para>
+ <xref linkend="chapter-sumti-tcita-section-jai"/> and
+ <xref linkend="chapter-tenses-section-jai"/>; for the purposes of this chapter, it operates as a conversion of selbri, similarly to the cmavo of selma'o SE. This conversion changes</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-jAdY">
<title>
<anchor xml:id="c11e10d7"/>
</title>
<interlinear-gloss>
<jbo>tu'a mi rinka le nu do morsi</jbo>
<gloss>something-to-do-with me causes the event-of you are-dead</gloss>
<en>My action causes your death.</en>
</interlinear-gloss>
</example>
@@ -1340,39 +1340,39 @@
<gloss>that-which-is associated-with causing (the event-of your death)</gloss>
<en>the one who caused your death</en>
</interlinear-gloss>
</example>
<para>because
<jbophrase>jai</jbophrase> modifies the selbri and can be incorporated into the description - not so for
<jbophrase>tu'a</jbophrase>.</para>
<para>The weakness of
<jbophrase>jai</jbophrase> used in descriptions in this way is that it does not specify which argument of the implicit abstraction is being raised into the x1 place of the description selbri. One can be more specific by using the modal form of
<jbophrase>jai</jbophrase> explained in
- <xref linkend="chapter-sumti-tcita"/>:</para>
+ <xref linkend="chapter-sumti-tcita-section-jai"/>:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-LPbo">
<title>
<anchor xml:id="c11e10d10"/>
</title>
<interlinear-gloss>
<jbo>le jai gau rinka be le nu do morsi</jbo>
<gloss>that-which-is agent-in causing (the event-of your death)</gloss>
</interlinear-gloss>
</example>
</section>
<section xml:id="section-events-and-contours">
<title>Event-type abstractors and event contour tenses</title>
<para>This section is a logical continuation of
<xref linkend="section-event-types"/>.</para>
<para> <indexterm type="lojban-word-imported"><primary>ZAhO selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>NU selma'o</primary></indexterm> There exists a relationship between the four types of events explained in
<xref linkend="section-event-types"/> and the event contour tense cmavo of selma'o ZAhO. The specific cmavo of NU and of ZAhO are mutually interdefining; the ZAhO contours were chosen to fit the needs of the NU event types and vice versa. Event contours are explained in full in
- <xref linkend="chapter-tenses"/>, and only summarized here.</para>
+ <xref linkend="chapter-tenses-section-event-contours"/>, and only summarized here.</para>
<para>The purpose of ZAhO cmavo is to represent the natural portions of an event, such as the beginning, the middle, and the end. They fall into several groups:</para>
<itemizedlist>
<listitem>
<para> <indexterm type="general-imported"><primary>process abstractions</primary><secondary>related tense contours</secondary></indexterm> The cmavo
<jbophrase>pu'o</jbophrase>,
<jbophrase>ca'o</jbophrase>, and
<jbophrase>ba'o</jbophrase> represent spans of time: before an event begins, while it is going on, and after it is over, respectively.</para>
</listitem>
<listitem>
<para>The cmavo
diff --git a/todocbook/12.xml b/todocbook/12.xml
index 649f6c5..9d202cd 100644
--- a/todocbook/12.xml
+++ b/todocbook/12.xml
@@ -33,35 +33,35 @@
</interlinear-gloss>
</example>
<para>Although the lujvo
<jbophrase>fagyfesti</jbophrase> is derived from the tanru
<jbophrase>fagri festi</jbophrase>, it is not equivalent in meaning to it. In particular,
<jbophrase>fagyfesti</jbophrase> has a distinct place structure of its own, not the same as that of
<jbophrase>festi</jbophrase>. (In contrast, the tanru does have the same place structure as
<jbophrase>festi</jbophrase>.) The lujvo needs to take account of the places of
<jbophrase>fagri</jbophrase> as well. When a tanru is made into a lujvo, there is no equivalent of
<jbophrase>be ... bei ... be'o</jbophrase> (described in
- <xref linkend="chapter-selbri"/>) to incorporate sumti into the middle of the lujvo.</para>
+ <xref linkend="chapter-selbri-section-be-sumti"/>) to incorporate sumti into the middle of the lujvo.</para>
<para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>rationale for</secondary></indexterm> <indexterm type="general-imported"><primary>creative understanding</primary></indexterm> 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>
<para> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>guidelines</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>guidelines for place structure</secondary></indexterm> <indexterm type="general-imported"><primary>absolute laws</primary></indexterm> <indexterm type="general-imported"><primary>alternative guidelines</primary></indexterm> 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>
<para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>cmavo incorporation</secondary></indexterm> If the tanru includes connective cmavo such as
<jbophrase>bo</jbophrase>,
<jbophrase>ke</jbophrase>,
<jbophrase>ke'e</jbophrase>, or
<jbophrase>je</jbophrase>, or conversion or abstraction cmavo such as
<jbophrase>se</jbophrase> or
<jbophrase>nu</jbophrase>, there are ways of incorporating them into the lujvo as well. Sometimes this makes the lujvo excessively long; if so, the cmavo may be dropped. This leads to the possibility that more than one tanru could produce the same lujvo. Typically, however, only one of the possible tanru is useful enough to justify making a lujvo for it.</para>
<para>The exact workings of the lujvo-making algorithm, which takes a tanru built from gismu (and possibly cmavo) and produces a lujvo from it, are described in
- <xref linkend="chapter-morphology"/>.</para>
+ <xref linkend="chapter-morphology-section-lujvo-making"/>.</para>
</section>
<section xml:id="section-tanru-meanings">
<title>The meaning of tanru: a necessary detour</title>
<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
<jbophrase>veljvo</jbophrase> 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
<jbophrase>seltau</jbophrase>, and the right (modified) part the
<jbophrase>tertau</jbophrase>, following the usage of
<xref linkend="chapter-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
@@ -582,21 +582,21 @@
<anchor xml:id="c12e7d6"/>
</title>
<interlinear-gloss>
<jbo>b1 sonci s2 gi'e banli b2 b3</jbo>
<gloss>b1 is-a-soldier of-army-s2 and is-great in-property-b2 by-standard-b3</gloss>
</interlinear-gloss>
</example>
<para>where
<jbophrase>gi'e</jbophrase> is the Lojban word for
<quote>and</quote> when placed between two partial bridi, as explained in
- <xref linkend="chapter-connectives"/>.</para>
+ <xref linkend="chapter-connectives-section-compound-bridi"/>.</para>
<para> <indexterm type="example-imported"><primary>veterinarian</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo place order</primary><secondary>asymmetrical lujvo</secondary></indexterm> <indexterm type="general-imported"><primary>animal doctor</primary><secondary>example</secondary></indexterm> Asymmetrical lujvo like
<jbophrase>gerzda</jbophrase>, on the other hand, employ a different rule. The seltau places are inserted not at the end of the place structure, but rather immediately after the tertau place which is equivalent to the first place of the seltau. Consider
<jbophrase>dalmikce</jbophrase>, meaning
<quote>veterinarian</quote>: its veljvo is
<jbophrase>danlu mikce</jbophrase>, or
<quote>animal doctor</quote>. The place structures for those gismu are:</para>
<example xml:id="example-random-id-BqPj">
<title>
@@ -962,21 +962,21 @@
<jbophrase>terter-</jbophrase>,
<jbophrase>velvel-</jbophrase> and
<jbophrase>xelxel-</jbophrase> work in the same way.</para>
<para>Other SE combinations like
<jbophrase>selter-</jbophrase>, although they might conceivably mean
<jbophrase>se te</jbophrase>, more than likely should be interpreted in the same way, namely as
<jbophrase>se ke te</jbophrase>, since there is no need to re-order places in the way that
<jbophrase>se te</jbophrase> provides. (See
- <xref linkend="chapter-sumti-tcita"/>.)</para>
+ <xref linkend="chapter-sumti-tcita-section-SE"/>.)</para>
</section>
<section xml:id="section-abstraction-lujvo">
<title>Abstract lujvo</title>
<para> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>"nu" lujvo</secondary></indexterm> <indexterm type="general-imported"><primary>abstract lujvo</primary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>abstract</secondary></indexterm> The cmavo of NU can participate in the construction of lujvo of a particularly simple and well-patterned kind. Consider that old standard example,
<jbophrase>klama</jbophrase>:</para>
<example xml:id="example-random-id-KEao">
<title>
<anchor xml:id="c12e12d1"/>
</title>
<para>k1 comes/goes to k2 from k3 via route k4 by means k5.</para>
@@ -1065,39 +1065,37 @@
<title>
<anchor xml:id="c12e12d7"/>
</title>
<interlinear-gloss>
<jbo>mi jai rinka le nu do morsi</jbo>
<gloss>I am-associated-with causing the event-of your death.</gloss>
<en>I cause your death.</en>
</interlinear-gloss>
</example>
<para>explained in
- <xref linkend="chapter-abstractions"/>, to be rendered with lujvo:</para>
+ <xref linkend="chapter-abstractions-section-jai"/>, to be rendered with lujvo:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-Wrpr">
<title>
<anchor xml:id="c12e12d8"/>
</title>
<interlinear-gloss>
<jbo>mi jaxri'a le nu do morsi</jbo>
<gloss>I am-part-of-the-cause-of the event-of your dying.</gloss>
</interlinear-gloss>
</example>
<para>In making a lujvo that contains
<jbophrase role="rafsi">jax-</jbophrase> for a selbri that contains
<jbophrase>jai</jbophrase>, the rule is to leave the
<jbophrase>fai</jbophrase> place as a
<jbophrase>fai</jbophrase> place of the lujvo; it does not participate in the regular lujvo place structure. (The use of
-
-
- <jbophrase>fai</jbophrase> is also explained in
- <xref linkend="chapter-abstractions"/>.)</para>
+ <jbophrase>fai</jbophrase> is explained in
+ <xref linkend="chapter-sumti-tcita-section-jai"/> and <xref linkend="chapter-tenses-section-jai"/>.)</para>
</section>
<section xml:id="section-implicit-abstraction">
<title>Implicit-abstraction lujvo</title>
<para>Eliding NU rafsi involves the same restrictions as eliding SE rafsi, plus additional ones. In general, NU rafsi should not be elided from the tertau, since that changes the kind of thing the lujvo is talking about from an abstraction to a concrete sumti. However, they may be elided from the seltau if no reasonable ambiguity would result.</para>
<para>A major difference, however, between SE elision and NU elision is that the former is a rather sparse process, providing a few convenient shortenings. Eliding
<jbophrase>nu</jbophrase>, however, is extremely important in producing a class of lujvo called
<quote>implicit-abstraction lujvo</quote>.</para>
@@ -1327,21 +1325,21 @@
<para>However, there is a further problem with
<jbophrase>jdaselsku</jbophrase>, not resolvable by using
<jbophrase>seljdasku</jbophrase>. No veljvo involving just the two gismu
<jbophrase>lijda</jbophrase> and
<jbophrase>cusku</jbophrase> 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
<jbophrase>seljdasku</jbophrase> and
<jbophrase>jdaselsku</jbophrase> 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
- <xref linkend="chapter-selbri"/>, is
+ <xref linkend="chapter-selbri-section-asymmetric-tanru"/>, is
<jbophrase>lange'u</jbophrase>, 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
<jbophrase>lanme</jbophrase> and
<jbophrase>gerku</jbophrase> at all. Rather, the lujvo refers to a dog which controls sheep flocks, a
<jbophrase>terlanme jitro gerku</jbophrase>, the lujvo from which is
<jbophrase>terlantroge'u</jbophrase> with place structure:</para>
<example xml:id="example-random-id-TW5Q">
<title>
@@ -1703,21 +1701,21 @@
<para>
<jbophrase>xekri</jbophrase>: xe1 is black</para>
</example>
<para> <indexterm type="general-imported"><primary>color standards</primary></indexterm> Brevity was the most important goal here, reinforced by one interpretation of metaphysical necessity. There is no mention of color standards here, as many people have pointed out; like all color gismu,
<jbophrase>xekri</jbophrase> is explicitly subjective. Objective color standards can be brought in by an appropriate BAI tag such as
<jbophrase>ci'u</jbophrase> (
<quote>in system</quote>; see
- <xref linkend="chapter-sumti-tcita"/>) or by making a lujvo.</para>
+ <xref linkend="chapter-sumti-tcita-section-BAI"/>) or by making a lujvo.</para>
<example xml:id="example-random-id-cuYP">
<title>
<anchor xml:id="c12e16d2"/>
</title>
<para>
<jbophrase>jbena</jbophrase>: j1 is born to j2 at time j3 and location j4</para>
</example>
<para>The gismu
<jbophrase>jbena</jbophrase> contains places for time and location, which few other gismu have: normally, the time and place at which something is done is supplied by a tense tag (see
<xref linkend="chapter-tenses"/>). However, providing these places makes
diff --git a/todocbook/13.xml b/todocbook/13.xml
index 765031d..a9f632a 100644
--- a/todocbook/13.xml
+++ b/todocbook/13.xml
@@ -1330,21 +1330,21 @@
<jbophrase>.o'ufu'i</jbophrase> to show appreciation for the assistance in your comfort.</para>
<para> <indexterm type="lojban-word-imported"><primary>be'u</primary></indexterm> The cmavo
<jbophrase>be'u</jbophrase> expresses, roughly speaking, whether the emotion it modifies is in response to something you don't have enough of, something you have enough of, or something you have too much of. It is more or less the attitudinal equivalent of the subjective quantifier cmavo
<jbophrase>mo'a</jbophrase>,
<jbophrase>rau</jbophrase>, and
<jbophrase>du'e</jbophrase> (these belong to selma'o PA, and are discussed in
- <xref linkend="chapter-mekso"/>). For example,</para>
+ <xref linkend="chapter-mekso-section-indefinite-numbers"/>). For example,</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-K4aV">
<title>
<anchor xml:id="c13e7d8"/>
</title>
<interlinear-gloss>
<jbo>.uiro'obe'unai</jbo>
<gloss>[Yay!] [physical] [Enough!]</gloss>
</interlinear-gloss>
</example>
<para> <indexterm type="example-imported"><primary>large meal</primary><secondary>example</secondary></indexterm> might be something you say after a large meal which you enjoyed.</para>
@@ -1459,21 +1459,21 @@
</title>
<interlinear-gloss>
<jbo>mi .e nai .ui do</jbo>
<gloss>I and [Not!] [Yay!] you</gloss>
</interlinear-gloss>
</example>
<para>means
<quote>I but (fortunately) not you</quote>. Attitudinal
<jbophrase>nai</jbophrase> expresses a
<quote>scalar negation</quote>, a concept explained in
- <xref linkend="chapter-negation"/>; since every attitudinal word implies exactly one scale, the effect of
+ <xref linkend="chapter-negation-section-scalar-negation"/>; since every attitudinal word implies exactly one scale, the effect of
<jbophrase>nai</jbophrase> on each should be obvious.</para>
<para> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>grammar of internal compounding</secondary></indexterm> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>internal grammar</secondary><tertiary>complete</tertiary></indexterm> Thus, the complete internal grammar of UI is as follows, with each listed part optionally present or absent without affecting grammaticality, though it obviously would affect meaning.</para>
<simplelist type="horiz" columns="9">
<member>attitudinal</member>
<member><jbophrase>nai</jbophrase></member>
<member>intensity-word</member>
<member><jbophrase>nai</jbophrase></member>
<member>modifier</member>
<member><jbophrase>nai</jbophrase></member>
<member>intensity-word</member>
@@ -1487,27 +1487,27 @@
</section>
<section xml:id="section-scope">
<title>The uses of indicators</title>
<para> <indexterm type="lojban-word-imported"><primary>su</primary></indexterm> <indexterm type="lojban-word-imported"><primary>sa</primary></indexterm> <indexterm type="lojban-word-imported"><primary>si</primary></indexterm> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>external grammar</secondary></indexterm> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>grammar of placement in bridi</secondary></indexterm> The behavior of indicators in the
<quote>outside grammar</quote> is nearly as simple as their internal structure. Indicator groupings are identified immediately after the metalinguistic erasers
<jbophrase>si</jbophrase>,
<jbophrase>sa</jbophrase>, and
<jbophrase>su</jbophrase> and some, though not all, kinds of quotations. The details of such interactions are discussed in
- <xref linkend="chapter-structure"/>.</para>
+ <xref linkend="chapter-structure-section-cmavo-interactions"/>.</para>
<para> <indexterm type="lojban-word-imported"><primary>zo</primary></indexterm> A group of indicators may appear anywhere that a single indicator may, except in those few situations (as in
<jbophrase>zo</jbophrase> quotation, explained in
- <xref linkend="chapter-structure"/>) where compound cmavo may not be used.</para>
+ <xref linkend="chapter-structure-section-more-quotations"/>) where compound cmavo may not be used.</para>
<para> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>at beginning of text</secondary></indexterm> At the beginning of a text, indicators modify everything following them indefinitely: such a usage is taken as a raw emotional expression, and we normally don't turn off our emotions when we start and stop sentences. In every other place in an utterance, the indicator (or group) attaches to the word immediately to its left, and indicates that the attitude is being expressed concerning the object or concept to which the word refers.</para>
<para> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>affecting whole grammatical structures</secondary></indexterm> If the word that an indicator (or group) attaches to is itself a cmavo which governs a grammatical structure, then the indicator construct pertains to the referent of the entire structure. There is also a mechanism, discussed in
- <xref linkend="chapter-structure"/>, for explicitly marking the range of words to which an indicator applies.</para>
+ <xref linkend="chapter-structure-section-attitudinal-scope"/>, for explicitly marking the range of words to which an indicator applies.</para>
<para> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>referent uncertainty</secondary></indexterm> More details about the uses of indicators, and the way they interact with other specialized cmavo, are given in
<xref linkend="chapter-structure"/>. It is worth mentioning that real-world interpretation is not necessarily consistent with the formal scope rules. People generally express emotions when they feel them, with only a minimum of grammatical constraint on that expression; complexities of emotional expression are seldom logically analyzable. Lojban attempts to provide a systematic reference that could possibly be ingrained to an instinctive level. However, it should always be assumed that the referent of an indicator has some uncertainty.</para>
<para> <indexterm type="general-imported"><primary>multiple indicators</primary></indexterm> For example, in cases of multiple indicators expressed together, the combined form has some ambiguity of interpretation. It is possible to interpret the second indicator as expressing an attitude about the first, or to interpret both as expressing attitudes about the common referent. For example, in</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-Rs6P">
<title>
<anchor xml:id="c13e9d1"/>
</title>
<interlinear-gloss>
<jbo>mi pu tavla do .o'onai .oi</jbo>
@@ -2042,21 +2042,21 @@
<para> <indexterm type="lojban-word-imported"><primary>go'i</primary></indexterm> <indexterm type="lojban-word-imported"><primary>po'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>mi'u</primary></indexterm> <indexterm type="lojban-word-imported"><primary>si'a</primary></indexterm> <indexterm type="lojban-word-imported"><primary>ji'a</primary></indexterm> <indexterm type="lojban-word-imported"><primary>ku'i</primary></indexterm> <indexterm type="example-imported"><primary>too</primary><secondary>example</secondary></indexterm> <indexterm type="example-imported"><primary>but</primary><secondary>example</secondary></indexterm> <indexterm type="example-imported"><primary>ditto</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>go'i</primary><secondary>contrasted with mi'u</secondary></indexterm> <indexterm type="general-imported"><primary>mi'u</primary><secondary>contrasted with go'i</secondary></indexterm> <indexterm type="general-imported"><primary>discursives for consecutive discourse</primary><secondary>contrasted</secondary></indexterm> These five discursives are mutually exclusive, and therefore they are not usually considered as scales. The first four are used in consecutive discourse. The first,
<jbophrase>ku'i</jbophrase>, makes an exception to the previous argument. The second,
<jbophrase>ji'a</jbophrase>, adds weight to the previous argument. The third,
<jbophrase>si'a</jbophrase>, adds quantity to the previous argument, enumerating an additional example. The fourth,
<jbophrase>mi'u</jbophrase>, adds a parallel case to the previous argument, and can also be used in tables or the like to show that something is being repeated from the previous column. It is distinct from
<jbophrase>go'i</jbophrase> (of selma'o GOhA, discussed in
- <xref linkend="chapter-anaphoric-cmavo"/>), which is a non-discursive version of
+ <xref linkend="chapter-anaphoric-cmavo-section-ri-gohi-series"/>), which is a non-discursive version of
<quote>ditto</quote> that explicitly repeats the claim of the previous bridi.</para>
<para> <indexterm type="example-imported"><primary>only</primary><secondary>example</secondary></indexterm> Lastly,
<jbophrase>po'o</jbophrase> is used when there is no other comparable case, and thus corresponds to some of the uses of
<quote>only</quote>, a word difficult to express in pure bridi form:</para>
<example xml:id="example-random-id-qG0v" role="interlinear-gloss-example">
<title>
<anchor xml:id="c13e12d1"/>
</title>
@@ -2521,21 +2521,21 @@
<jbophrase>li'o</jbophrase> was not part of the original quotation. In practice, this and other forms which are already associated with metalinguistic expressions, such as
<jbophrase>sei</jbophrase> (of selma'o SEI) or
<jbophrase>to'i</jbophrase> (of selma'o TO) need not be marked except where confusion might result.</para>
<para> <indexterm type="general-imported"><primary>sa'a</primary><secondary>editorial insertion of text already containing sa'a</secondary></indexterm> <indexterm type="general-imported"><primary>editorial insertion</primary><secondary>of text already containing sa'a</secondary></indexterm> In the rare case that the quoted material already contains one or more instances of
<jbophrase>sa'a</jbophrase>, they can be changed to
<jbophrase>sa'asa'a</jbophrase>.</para>
<para> <indexterm type="lojban-word-imported"><primary>xu</primary></indexterm> <indexterm type="general-imported"><primary>questions</primary><secondary>with "xu"</secondary></indexterm> <indexterm type="general-imported"><primary>truth questions</primary></indexterm> <indexterm type="general-imported"><primary>yes/no questions</primary></indexterm> The cmavo
<jbophrase>xu</jbophrase> marks truth questions, which are discussed in detail in
- <xref linkend="chapter-negation"/>. In general,
+ <xref linkend="chapter-negation-section-questions"/>. In general,
<jbophrase>xu</jbophrase> may be translated
<quote>Is it true that ... ?</quote> and questions whether the attached bridi is true. When
<jbophrase>xu</jbophrase> is attached to a specific word or construct, it directs the focus of the question to that word or construct.</para>
<para> <indexterm type="lojban-word-imported"><primary>pau</primary></indexterm> <indexterm type="general-imported"><primary>questions</primary><secondary>marking in advance</secondary></indexterm> Lojban question words, unlike those of English, frequently do not stand at the beginning of the question. Placing the cmavo
<jbophrase>pau</jbophrase> at the beginning of a bridi helps the listener realize that the bridi is a question, like the symbol at the beginning of written Spanish questions that looks like an upside-down question mark. The listener is then warned to watch for the actual question word.</para>
<para> <indexterm type="lojban-word-imported"><primary>paunai</primary></indexterm> <indexterm type="general-imported"><primary>questions</primary><secondary>rhetorical</secondary></indexterm> <indexterm type="general-imported"><primary>rhetorical question</primary></indexterm> <indexterm type="general-imported"><primary>pau</primary><secondary>placement in sentence</secondary></indexterm> Although
<jbophrase>pau</jbophrase> is grammatical in any location (like all indicators), it is not really useful except at or near the beginning of a bridi. Its scalar opposite,
<jbophrase>paunai</jbophrase>, signals that a bridi is not really a question despite its form. This is what we call in English a rhetorical question: an example appears in the English text near the beginning of
@@ -2622,21 +2622,21 @@
<para> <indexterm type="lojban-word-imported"><primary>kau</primary></indexterm> <indexterm type="general-imported"><primary>indirect question</primary></indexterm> FIXME: TAG SPOT</para>
<cmavo-list>
<cmavo-entry>
<cmavo>kau</cmavo>
<attitudinal-scale point="sai">indirect question</attitudinal-scale>
</cmavo-entry>
</cmavo-list>
<para>This cmavo is explained in detail in
- <xref linkend="chapter-abstractions"/>. It marks the word it is attached to as the focus of an indirect question:</para>
+ <xref linkend="chapter-abstractions-section-indirect-questions"/>. It marks the word it is attached to as the focus of an indirect question:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-umCQ">
<title>
<anchor xml:id="c13e13d3"/>
</title>
<interlinear-gloss>
<jbo>mi djuno le du'u dakau klama le zarci</jbo>
<gloss>I know the statement-that somebody [indirect ?] goes to-the store.</gloss>
<en>I know who goes to the store.</en>
@@ -2650,21 +2650,21 @@
<jbophrase>la</jbophrase> (and the other members of selma'o LA) mark a name used to refer to someone. The vocatives actually are indicators - in fact, discursives - but the need to tie them to names and other descriptions of listeners requires them to be separated from selma'o UI. But like the cmavo of UI, the members of selma'o COI can be
<quote>negated</quote> with
<jbophrase>nai</jbophrase> to get the opposite part of the scale.</para>
<para> <indexterm type="general-imported"><primary>vocatives</primary><secondary>rationale for redundancy</secondary></indexterm> <indexterm type="general-imported"><primary>redundancy</primary><secondary>effect on vocative design</secondary></indexterm> Because of the need for redundancy in noisy environments, the Lojban design does not compress the vocatives into a minimum number of scales. Doing so would make a non-redundant
<jbophrase>nai</jbophrase> too often vital to interpretation of a protocol signal, as explained later in this section.</para>
<para> <indexterm type="lojban-word-imported"><primary>do'u</primary></indexterm> <indexterm type="lojban-word-imported"><primary>DOhU selma'o</primary></indexterm> <indexterm type="general-imported"><primary>vocatives</primary><secondary>grammar overview</secondary></indexterm> The grammar of vocatives is explained in
- <xref linkend="chapter-sumti"/>; but in brief, a vocative may be followed by a name (without
+ <xref linkend="chapter-sumti-section-vocatives"/>; but in brief, a vocative may be followed by a name (without
<jbophrase>la</jbophrase>), a description (without
<jbophrase>le</jbophrase> or its relatives), a complete sumti, or nothing at all (if the addressee is obvious from the context). There is an elidable terminator,
<jbophrase>do'u</jbophrase> (of selma'o DOhU) which is almost never required unless no name (or other indication of the addressee) follows the vocative.</para>
<para> <indexterm type="general-imported"><primary>vocatives</primary><secondary>and definition of "you"</secondary></indexterm> <indexterm type="general-imported"><primary>you</primary><secondary>defining</secondary></indexterm> Using any vocative except
<jbophrase>mi'e</jbophrase> (explained below) implicitly defines the meaning of the pro-sumti
<jbophrase>do</jbophrase>, as the whole point of vocatives is to specify the listener, or at any rate the desired listener - even if the desired listener isn't listening! We will use the terms
<quote>speaker</quote> and
<quote>listener</quote> for clarity, although in written Lojban the appropriate terms would be
<quote>writer</quote> and
@@ -3234,21 +3234,21 @@
</example>
</section>
<section xml:id="section-conclusion">
<title>Tentative conclusion</title>
<para> <indexterm type="general-imported"><primary>indicators</primary><secondary>ramifications</secondary></indexterm> <indexterm type="general-imported"><primary>aliens</primary><secondary>communication with</secondary></indexterm> <indexterm type="general-imported"><primary>Kzinti</primary><secondary>communication with</secondary></indexterm> The exact ramifications of the indicator system in actual usage are unknown. There has never been anything like it in natural language before. The system provides great potential for emotional expression and transcription, from which significant Sapir-Whorf effects can be anticipated. When communicating across cultural boundaries, where different indicators are often used for the same emotion, accidental offense can be avoided. If we ever ran into an alien race, a culturally neutral language of emotion could be vital. (A classic example, taken from the science fiction of Larry Niven, is to imagine speaking Lojban to the carnivorous warriors called Kzinti, noting that a human smile bares the teeth, and could be seen as an intent to attack.) And for communicating emotions to computers, when we cannot identify all of the signals involved in subliminal human communication (things like body language are also cultural), a system like this is needed.</para>
<para> <indexterm type="general-imported"><primary>indicators</primary><secondary>rationale for selection</secondary></indexterm> We have tried to err on the side of overkill. There are distinctions possible in this system that no one may care to make in any culture. But it was deemed more neutral to overspecify and let usage decide, than to choose a limited set and constrain emotional expression. For circumstances in which even the current indicator set is not enough, it is possible using the cmavo
<jbophrase>sei</jbophrase>, explained in
- <xref linkend="chapter-structure"/>, to create metalinguistic comments that act like indicators.</para>
+ <xref linkend="chapter-structure-section-parentheses"/>, to create metalinguistic comments that act like indicators.</para>
<para> <indexterm type="general-imported"><primary>indicators</primary><secondary>evolutionary development of</secondary></indexterm> We envision an evolutionary development. At this point, the system is little more than a mental toy. Many of you who read this will try playing around with various combinations of indicators, trying to figure out what emotions they express and when the expressions might be useful. You may even find an expression for which there currently is no good English word and start using it. Why not, if it helps you express your feelings?</para>
<para>There will be a couple dozen of these used pretty much universally – mostly just simple attitudinals with, at most, intensity markers. These are the ones that will quickly be expressed at the subconscious level. But every Lojbanist who plays with the list will bring in a couple of new words. Poets will paint emotional pictures, and people who identify with those pictures will use the words so created for their own experiences.</para>
<para>Just as a library of tanru is built up, so will a library of attitudes be built. Unlike the tanru, though, the emotional expressions are built on some fairly nebulous root emotions - words that cannot be defined with the precision of the gismu. The emotion words of Lojban will very quickly take on a life of their own, and the outline given here will evolve into a true system of emotions.</para>
<para> <indexterm type="general-imported"><primary>emotions</primary><secondary>research using indicators</secondary></indexterm> <indexterm type="general-imported"><primary>emotions</primary><secondary>recording using indicators</secondary></indexterm> There are several theories as to the nature of emotion, and they change from year to year as we learn more about ourselves. Whether or not Lojban's additive/scalar emotional model is an accurate model for human emotions, it does support the linguistic needs for expressing those emotions. Researchers may learn more about the nature of human emotions by exploring the use of the system by Lojban speakers. They also may be able to use the Lojban system as a means for more clearly recording emotions.</para>
<para> <indexterm type="general-imported"><primary>emotions</primary><secondary>cultural bias of expression</secondary></indexterm> The full list of scales and attitudes will probably not be used until someone speaks the language from birth. Until then, people will use the attitudes that are important to them. In this way, we counter cultural bias - if a culture is prone to recognizing and/or expressing certain emotions more than others, its members will use only those out of the enormous set available. If a culture hides certain emotions, its members simply won't express them.</para>
<para> <indexterm type="general-imported"><primary>Sapir-Whorf effects</primary><secondary>and emotional indicators</secondary></indexterm> Perhaps native Lojban speakers will be more expressively clear about their emotions than others. Perhaps they will feel some emotions more strongly than others in ways that can be correlated with the word choices; any difference from the norms of other cultures could be significant. Psychologists have devised elaborate tests for measuring attitudes and personality; this may be the easiest area in which to detect any systematic cultural effect of the type sought to confirm Sapir-Whorf, simply because we already have tools in existence to test it. Because Lojban is unique among languages in having such extensive and expressive indicators, it is likely that a Sapir-Whorf effect will occur and will be recognized.</para>
<para>It is unlikely that we will know the true potential of a system like this one until and unless we have children raised entirely in a multi-cultural Lojban-speaking environment. We learn too many cultural habits in the realm of emotional communication
diff --git a/todocbook/14.xml b/todocbook/14.xml
index b5da6b6..5ff8c5b 100644
--- a/todocbook/14.xml
+++ b/todocbook/14.xml
@@ -462,21 +462,21 @@
<interlinear-gloss>
<jbo>la djan. nanmu .inaja la djeimyz. ninmu</jbo>
<gloss>John is-not-a-man or James is-a-woman.</gloss>
<en>John is a man only if James is a woman.</en>
<en>If John is a man, then James is a woman.</en>
</interlinear-gloss>
</example>
<para> <indexterm type="lojban-word-imported"><primary>se</primary></indexterm> <indexterm type="general-imported"><primary>se</primary><secondary>in logical connective to exchange sentences</secondary></indexterm> The following example illustrates the use of
<jbophrase>se</jbophrase> to, in effect, exchange the two sentences. The normal use of
<jbophrase>se</jbophrase> is to (in effect) transpose places of a bridi, as explained in
- <xref linkend="chapter-selbri"/>.</para>
+ <xref linkend="chapter-selbri-section-place-conversion"/>.</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-z43X">
<title>
<anchor xml:id="c14e4d11"/>
</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>
<para> <indexterm type="lojban-word-imported"><primary>se</primary></indexterm> <indexterm type="lojban-word-imported"><primary>nai</primary></indexterm> <indexterm type="lojban-word-imported"><primary>na</primary></indexterm> <indexterm type="general-imported"><primary>na</primary><secondary>order in logical connectives with se</secondary></indexterm> <indexterm type="general-imported"><primary>se</primary><secondary>order in logical connectives with na</secondary></indexterm> If both
@@ -603,21 +603,21 @@
<example role="interlinear-gloss-example" xml:id="example-random-id-TQP9">
<title>
<anchor xml:id="c14e5d7"/>
</title>
<interlinear-gloss>
<jbo>le nu do cidja dunda fi le xarju cu rinka le nu ri ba banro</jbo>
<gloss>The event-of (you food-give to the pig) causes the event-of (it will grow).</gloss>
</interlinear-gloss>
</example>
<para>Causality is discussed in far more detail in
- <xref linkend="chapter-sumti-tcita"/>.</para>
+ <xref linkend="chapter-sumti-tcita-section-causals"/>.</para>
<para>
<xref linkend="example-random-id-I2jU"/> and
<xref linkend="example-random-id-Tiz6"/> illustrates a truth function, FTTF, which needs to negate either the first or the second bridi. We already understand how to negate the first bridi:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-I2jU">
<title>
<anchor xml:id="c14e5d8"/>
</title>
<interlinear-gloss>
<jbo>gonai la djan. nanmu gi la djeimyz. ninmu</jbo>
<gloss>John is-not-a-man if-and-only-if James is-a-woman,</gloss>
@@ -1431,22 +1431,23 @@
<anchor xml:id="c14e11d7"/>
</title>
<interlinear-gloss>
<jbo>mi klama nu'i ge le zarci le briju nu'u gi le zdani le ckule [nu'u]</jbo>
<gloss>I go [start termset] both to-the market from-the office [joint] and to-the house from-the school [end termset].</gloss>
</interlinear-gloss>
</example>
<para>Note that even though two termsets are being connected, only one
<jbophrase>nu'i</jbophrase> is used.</para>
<para>The grammatical uses of termsets that do not contain logical connectives are explained in
- <xref linkend="chapter-lujvo"/> and
- <xref linkend="chapter-quantifiers"/>.</para>
+ <xref linkend="chapter-sumti-tcita-section-modal-connectives"/>,
+ <xref linkend="chapter-tenses-section-explicit-magnitudes"/>, and
+ <xref linkend="chapter-quantifiers-section-grouping"/>.</para>
</section>
<section xml:id="section-tanru">
<title>Logical connection within tanru</title>
<para> <indexterm type="general-imported"><primary>logical connectives in tanru</primary></indexterm> As noted at the beginning of
<xref linkend="section-compound-bridi"/>, there is no logical connective in Lojban that joins selbri and nothing but selbri. However, it is possible to have logical connectives within a selbri, forming a kind of tanru that involves a logical connection. Consider the simple tanru
<jbophrase>blanu zdani</jbophrase>, blue house. Now anything that is a blue ball, in the most ordinary understanding of the phrase at least, is both blue and a ball. And indeed, instead of
<jbophrase>blanu bolci</jbophrase>, Lojbanists can say
<jbophrase>blanu je bolci</jbophrase>, using a jek connective within the tanru. (We saw jeks used in
<xref linkend="section-termsets"/> also, but there they were always prefixed by
<jbophrase>pe'e</jbophrase>; in this section they are used alone.) Here is a pair of examples:</para>
@@ -1662,27 +1663,27 @@
<interlinear-gloss>
<jbo>xu la faidon. gerku</jbo>
<gloss>Is-it-true-that Fido is-a-dog?</gloss>
</interlinear-gloss>
</example>
<para>
<xref linkend="example-random-id-bMjE"/> and
<xref linkend="example-random-id-gKaM"/> are equivalent in meaning.</para>
<para> <indexterm type="general-imported"><primary>truth questions</primary><secondary>answering "no"</secondary></indexterm> <indexterm type="general-imported"><primary>truth questions</primary><secondary>answering "yes"</secondary></indexterm> <indexterm type="general-imported"><primary>truth questions</primary><secondary>as yes-or-no questions</secondary></indexterm> A truth question can be answered
<quote>yes</quote> or
- <jbophrase>no</jbophrase>, depending on the truth or falsity, respectively, of the underlying statement. The standard way of saying
+ <quote>no</quote>, depending on the truth or falsity, respectively, of the underlying statement. The standard way of saying
<quote>yes</quote> in Lojban is
<jbophrase>go'i</jbophrase> and of saying
- <jbophrase>no</jbophrase> is
+ <quote>no</quote> is
<jbophrase>nago'i</jbophrase>. (The reasons for this rule are explained in
- <xref linkend="chapter-anaphoric-cmavo"/>.) In answer to
+ <xref linkend="chapter-anaphoric-cmavo-section-ri-gohi-series"/>.) In answer to
<xref linkend="example-random-id-gKaM"/>, the possible answers are:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-XSmq">
<title>
<anchor xml:id="c14e13d3"/>
</title>
<interlinear-gloss>
<jbo>go'i</jbo>
<en>Fido is a dog.</en>
</interlinear-gloss>
</example>
@@ -1896,21 +1897,21 @@
<gloss>If this is-coffee then [you!] bring a-mass-of tea to-me, and if this is-tea then [you!] bring a-mass-of coffee to-me.</gloss>
<en>If this is coffee, bring me tea; but if this is tea, bring me coffee.</en>
</interlinear-gloss>
</example>
<para> <indexterm type="lojban-word-imported"><primary>UI selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>ku'i</primary></indexterm> <indexterm type="general-imported"><primary>and</primary><secondary>compared with but</secondary></indexterm> <indexterm type="general-imported"><primary>but</primary><secondary>compared with and</secondary></indexterm> In logical terms, however,
<quote>but</quote> is the same as
<quote>and</quote>; the difference is that the sentence after a
<quote>but</quote> is felt to be in tension or opposition to the sentence before it. Lojban represents this distinction by adding the discursive cmavo
<jbophrase>ku'i</jbophrase> (of selma'o UI), which is explained in
- <xref linkend="chapter-attitudinals"/>, to the logical
+ <xref linkend="chapter-attitudinals-section-discursives"/>, to the logical
<jbophrase>.ije</jbophrase>.)</para>
</section>
<section xml:id="section-non-logical-connectives">
<title>Non-logical connectives</title>
<para> <indexterm type="general-imported"><primary>and</primary><secondary>as non-logical connective</secondary></indexterm> Way back in
<xref linkend="section-introduction"/>, the point was made that not every use of English
<quote>and</quote>,
<quote>if ... then</quote>, and so on represents a Lojban logical connective. In particular, consider the
<quote>and</quote> of:</para>
@@ -1936,21 +1937,21 @@
</title>
<interlinear-gloss>
<jbo>la djan. joi la .alis. cu bevri le pipno</jbo>
<gloss>John massed-with Alice carry the piano.</gloss>
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>components contrasted with mass</primary><secondary>in properties of</secondary></indexterm> <indexterm type="general-imported"><primary>mass contrasted with components</primary><secondary>in properties of</secondary></indexterm> <indexterm type="general-imported"><primary>supervising</primary><secondary>as a contribution to mass action</secondary></indexterm>
<xref linkend="example-random-id-pC5x"/> covers the case mentioned, where John and Alice divide the labor; it also could mean that John did all the hauling and Alice did the supervising. This possibility arises because the properties of a mass are the properties of its components, which can lead to apparent contradictions: if John is small and Alice is large, then John-and-Alice is both small and large. Masses are also discussed in
- <xref linkend="chapter-sumti"/>.</para>
+ <xref linkend="chapter-sumti-section-masses"/>.</para>
<para> <indexterm type="lojban-word-imported"><primary>JA selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>A selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>JOI selma'o</primary></indexterm> <indexterm type="general-imported"><primary>non-logical connection</primary><secondary>in tanru</secondary><tertiary>distinguishing from connection of sumti</tertiary></indexterm> <indexterm type="general-imported"><primary>non-logical connection</primary><secondary>of sumti</secondary><tertiary>distinguishing from connection in tanru</tertiary></indexterm> <indexterm type="general-imported"><primary>joi grammar</primary><secondary>contrasted with jeks</secondary></indexterm> <indexterm type="general-imported"><primary>joi grammar</primary><secondary>contrasted with eks</secondary></indexterm> <indexterm type="general-imported"><primary>non-logical connection</primary><secondary>and elidability of terminators</secondary></indexterm> Grammatically,
<jbophrase>joi</jbophrase> can appear between two sumti (like an ek) or between two tanru components (like a jek). This flexibility must be paid for in the form of occasional terminators that cannot be elided:</para>
<para> <indexterm type="lojban-word-imported"><primary>LE selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>KU selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>le</primary></indexterm> <indexterm type="lojban-word-imported"><primary>ku</primary></indexterm> <indexterm type="general-imported"><primary>terminators</primary><secondary>eliding ku in non-logical connections</secondary></indexterm> FIXME: TAG SPOT</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-NN93">
<title>
<anchor xml:id="c14e14d4"/>
</title>
<interlinear-gloss>
<jbo>le nanmu ku joi le ninmu [ku] cu klama le zarci</jbo>
<gloss>The man massed-with the woman go-to the market.</gloss>
@@ -2615,21 +2616,21 @@
<quote>2</quote>, and operators, like
<quote>+</quote>. Both of these may be either logically or non-logically connected.</para>
<para> <indexterm type="lojban-word-imported"><primary>JOI selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>GUhA selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>JA selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>GA selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>A selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>BO selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>bo</primary></indexterm> <indexterm type="general-imported"><primary>connecting operators</primary><secondary>with bo in connective</secondary></indexterm> <indexterm type="general-imported"><primary>bo</primary><secondary>in joiks for operators</secondary></indexterm> <indexterm type="general-imported"><primary>bo</primary><secondary>in jeks for operators</secondary></indexterm> <indexterm type="general-imported"><primary>guheks</primary><secondary>connecting operators</secondary></indexterm> <indexterm type="general-imported"><primary>jeks</primary><secondary>connecting operators</secondary></indexterm> <indexterm type="general-imported"><primary>operators</primary><secondary>connecting</secondary></indexterm> <indexterm type="general-imported"><primary>operands</primary><secondary>connecting</secondary></indexterm> <indexterm type="general-imported"><primary>geks</primary><secondary>connecting operands</secondary></indexterm> <indexterm type="general-imported"><primary>eks</primary><secondary>connecting operands</secondary></indexterm> Operands are connected in afterthought with eks and in forethought with geks, just like sumti. Operators, on the other hand, are connected in afterthought with jeks and in forethought with guheks, just like tanru components. (However, jeks and joiks with
<jbophrase>bo</jbophrase> are not allowed for operators.) This parallelism is no accident.</para>
<para> <indexterm type="lojban-word-imported"><primary>ke'e</primary></indexterm> <indexterm type="lojban-word-imported"><primary>ke</primary></indexterm> <indexterm type="lojban-word-imported"><primary>bo</primary></indexterm> <indexterm type="lojban-word-imported"><primary>BO selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>KE selma'o</primary></indexterm> <indexterm type="general-imported"><primary>operators</primary><secondary>analogue of tanru in</secondary></indexterm> <indexterm type="general-imported"><primary>connecting operators</primary><secondary>with ke in connective</secondary></indexterm> <indexterm type="general-imported"><primary>connecting operands</primary><secondary>with ke in connective</secondary></indexterm> <indexterm type="general-imported"><primary>connecting operands</primary><secondary>with bo in connective</secondary></indexterm> In addition, eks with
<jbophrase>bo</jbophrase> and with
<jbophrase>ke ... ke'e</jbophrase> are allowed for grouping logically connected operands, and
<jbophrase>ke ... ke'e</jbophrase> is allowed for grouping logically connected operators, although there is no analogue of tanru among the operators.</para>
<para>Only a few examples of each kind of mekso connection will be given. Despite the large number of rules required to support this feature, it is of relatively minor importance in either the mekso or the logical-connective scheme of things. These examples are drawn from
- <xref linkend="chapter-mekso"/>, and contain many mekso features not explained in this chapter.</para>
+ <xref linkend="chapter-mekso-section-connectives-within-mekso"/>, and contain many mekso features not explained in this chapter.</para>
<para>
<xref linkend="example-random-id-gMU4"/> exhibits afterthought logical connection between operands:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-gMU4">
<title>
<anchor xml:id="c14e17d1"/>
</title>
<interlinear-gloss>
<jbo>vei ci .a vo [ve'o] prenu cu klama le zarci</jbo>
<gloss>( Three or four ) people go-to the market.</gloss>
</interlinear-gloss>
@@ -2715,21 +2716,21 @@
<xref linkend="example-random-id-8rEL"/> is not elidable, because the
<jbophrase>xi</jbophrase> subscript needs something to attach to.</para>
</section>
<section xml:id="section-sumtcita">
<title>Tenses, modals, and logical connection</title>
<para> <indexterm type="lojban-word-imported"><primary>PU selma'o</primary></indexterm> The tense and modal systems of Lojban interact with the logical connective system. No one chapter can explain all of these simultaneously, so each chapter must present its own view of the area of interaction with emphasis on its own concepts and terminology. In the examples of this chapter, the many tenses of various selma'o as well as the modals of selma'o BAI are represented by the simple time cmavo
<jbophrase>pu</jbophrase>,
<jbophrase>ca</jbophrase>, and
<jbophrase>ba</jbophrase> (of selma'o PU) representing the past, the present, and the future respectively. Preceding a selbri, these cmavo state the time when the bridi was, is, or will be true (analogous to English verb tenses); preceding a sumti, they state that the event of the main bridi is before, simultaneous with, or after the event given by the sumti (which is generally a
<jbophrase>le nu</jbophrase> abstraction; see
- <xref linkend="chapter-abstractions"/>).</para>
+ <xref linkend="chapter-abstractions-section-events"/>).</para>
<para> <indexterm type="general-imported"><primary>logically connected tenses</primary><secondary>definition</secondary></indexterm> <indexterm type="general-imported"><primary>logical connection</primary><secondary>interaction with tenses</secondary></indexterm> The two types of interaction between tenses and logical connectives are logically connected tenses and tensed logical connections. The former are fairly simple. Jeks may be used between tense cmavo to specify two connected bridi that differ only in tense:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-g6iT">
<title>
<anchor xml:id="c14e18d1"/>
</title>
<interlinear-gloss>
<jbo>la .artr. pu nolraitru .ije la .artr. ba nolraitru</jbo>
<gloss>Arthur [past] is-a-noblest-governor. And Arthur [future] is-a-noblest-governor.</gloss>
diff --git a/todocbook/15.xml b/todocbook/15.xml
index b724d07..f4d3383 100644
--- a/todocbook/15.xml
+++ b/todocbook/15.xml
@@ -795,21 +795,21 @@
<jbo>lo ca nolraitru be le fasygu'e cu na krecau</jbo>
<gloss>An-actual current noblest-governor of the French Country [false] is-hair-without.</gloss>
<en>It is false that the current King of France is bald.</en>
</interlinear-gloss>
</example>
<para>Note:
<jbophrase>lo</jbophrase> is used in these sentences because negation relates to truth conditions. To meaningfully talk about truth conditions in sentences carrying a description, it must be clear that the description actually applies to the referent. A sentence using
<jbophrase>le</jbophrase> instead of
<jbophrase>lo</jbophrase> can be true even if there is no current king of France, as long as the speaker and the listener agree to describe something as the current king of France. (See the explanations of
<jbophrase>le</jbophrase> in
- <xref linkend="chapter-sumti"/>.)</para>
+ <xref linkend="chapter-sumti-section-basic-descriptors"/>.)</para>
</section>
<section xml:id="section-scales-negation">
<title>Expressing scales in selbri negation</title>
<para>In expressing a scalar negation, we can provide some indication of the scale, range, frame-of-reference, or universe of discourse that is being dealt with in an assertion. As stated in
<xref linkend="section-nahe"/>, the default is the set of plausible alternatives. Thus if we say:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-mw3B">
<title>
<anchor xml:id="c15e5d1"/>
</title>
<interlinear-gloss>
@@ -1038,21 +1038,21 @@
</section>
<section xml:id="section-other-negation">
<title>Negation of minor grammatical constructs</title>
<para>We have a few other constructs that can be negated, all of them based on negating individual words. For such negation, we use the suffix-combining negator, which is
<jbophrase>nai</jbophrase>.
<jbophrase>nai</jbophrase>, by the way, is almost always written as a compound into the previous word that it is negating, although it is a regular separate-word cmavo and the sole member of selma'o NAI.</para>
<para>Most of these negation forms are straightforward, and should be discussed and interpreted in connection with an analysis of the particular construct being negated. Thus, we will not go into much detail here.</para>
<para>The following are places where
<jbophrase>nai</jbophrase> is used:</para>
<para>When attached to tenses and modals (see
- <xref linkend="chapter-tenses"/>), the
+ <xref linkend="chapter-tenses"/>), the <!-- also see chapter-modals? -->
<jbophrase>nai</jbophrase> suffix usually indicates a contradictory negation of the tagged bridi. Thus
<jbophrase>punai</jbophrase> as a tense inflection means
<quote>not-in-the-past</quote>, or
<quote>not-previously</quote>, without making any implication about any other time period unless explicitly stated. As a result,</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-PprX">
<title>
<anchor xml:id="c15e7d1"/>
</title>
<interlinear-gloss>
<jbo>mi na pu klama le zarci</jbo>
@@ -1083,52 +1083,52 @@
<anchor xml:id="c15e7d3"/>
</title>
<interlinear-gloss>
<jbo>mi paroinai dansu le bisli</jbo>
<gloss>I [once] [not] dance-on the ice</gloss>
</interlinear-gloss>
</example>
<para>means that I dance on the ice either zero or else two or more times within the relevant time interval described by the bridi.
<xref linkend="example-random-id-4YYQ"/> is very different from the English use of
<quote>not once</quote>, which is an emphatic way of saying
- <quote>never</quote>- that is, exactly zero times.</para>
+ <quote>never</quote> – that is, exactly zero times.</para>
<para>In indicators and attitudinals of selma'o UI or CAI,
<jbophrase>nai</jbophrase> denotes a polar negation. As discussed in
- <xref linkend="chapter-attitudinals"/>, most indicators have an implicit scale, and
+ <xref linkend="chapter-attitudinals-section-intensity-scale"/>, most indicators have an implicit scale, and
<jbophrase>nai</jbophrase> changes the indicator to refer to the opposite end of the scale. Thus
<jbophrase>.uinai</jbophrase> expresses unhappiness, and
<jbophrase>.ienai</jbophrase> expresses disagreement (not ambivalence, which is expressed with the neutral or undecided intensity as
<jbophrase>.iecu'i</jbophrase>).</para>
<para>Vocative cmavo of selma'o COI are considered a kind of indicator, but one which identifies the listener. Semantically, we could dispense with about half of the COI selma'o words based on the scalar paradigm. For example,
<jbophrase>co'o</jbophrase> could be expressed as
<jbophrase>coinai</jbophrase>. However, this is not generally done.</para>
<para>Most of the COI cmavo are used in what are commonly called protocol situations. These protocols are used, for example, in radio conversations, which often take place in a noisy environment. The negatives of protocol words tend to convey diametrically opposite communications situations (as might be expected). Therefore, only one protocol vocative is dependent on
<jbophrase>nai</jbophrase>: negative acknowledgement, which is
<jbophrase>je'enai</jbophrase> (
<quote>I didn't get that</quote>).</para>
<para>Unlike the attitudinal indicators, which tend to be unimportant in noisy situations, the protocol vocatives become more important. So if, in a noisy environment, a protocol listener makes out only
<jbophrase>nai</jbophrase>, he or she can presume it is a negative acknowledgement and repeat transmission or otherwise respond accordingly.
- <xref linkend="chapter-attitudinals"/> provides more detail on this topic.</para>
+ <xref linkend="chapter-attitudinals-section-vocatives"/> provides more detail on this topic.</para>
<para>The abstractors of selma'o NU follow the pattern of the tenses and modals. NU allows negative abstractions, especially in compound abstractions connected by logical connectives:
<jbophrase>su'ujeninai</jbophrase>, which corresponds to
<jbophrase>su'u jenai ni</jbophrase> just as
<jbophrase>punai je ca</jbophrase> corresponds to
<jbophrase>pu naje ca</jbophrase>. It is not clear how much use logically connected abstractors will be: see
- <xref linkend="chapter-attitudinals"/>.</para>
+ <xref linkend="chapter-abstractions-section-abstractor-connection"/>.</para>
<para>A
<jbophrase>nai</jbophrase> attached to a non-logical connective (of selma'o JOI or BIhI) is a scalar negation, and says that the bridi is false under the specified mixture, but that another connective is applicable. Non-logical connectives are discussed in
- <xref linkend="chapter-connectives"/>.</para>
+ <xref linkend="chapter-connectives-section-non-logical-connectives"/>.</para>
</section>
<section xml:id="section-questions">
<title>Truth questions</title>
<para>One application of negation is in answer to truth questions (those which expect the answers
<quote>Yes</quote> or
<quote>No</quote>). The truth question cmavo
<jbophrase>xu</jbophrase> is in selma'o UI; placed at the beginning of a sentence, it asks whether the sentence as a whole is true or false.</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-5y84">
<title>
<anchor xml:id="c15e8d1"/>
@@ -1456,30 +1456,31 @@
<jbophrase>na'i</jbophrase> need not be assumed to cancel each other. Indeed, we can use the position of
<jbophrase>na'i</jbophrase> to indicate metalinguistically what is incorrect, preparatory to correcting it in a later sentence; for this reason, we give
<jbophrase>na'i</jbophrase> the grammar of UI. The inclusion of
<jbophrase>na'i</jbophrase> anywhere in a sentence makes it a non-assertion, and suggests one or more pitfalls in assigning a truth value.</para>
<para>Let us briefly indicate how the above-mentioned metalinguistic errors can be identified. Other metalinguistic problems can then be marked by devising analogies to these examples:</para>
<para>Existential failure can be marked by attaching
<jbophrase>na'i</jbophrase> to the descriptor
<jbophrase>lo</jbophrase> or the
<jbophrase>poi</jbophrase> in a
- <jbophrase>da poi</jbophrase>-form sumti. (See Chapter 6 and
- <xref linkend="chapter-quantifiers"/> for details on these constructions.) Remember that if a
+ <jbophrase>da poi</jbophrase>-form sumti. (See
+ <xref linkend="chapter-sumti-section-basic-descriptors"/> and
+ <xref linkend="chapter-quantifiers-section-restricted-claims"/> for details on these constructions.) Remember that if a
<jbophrase>le</jbophrase> sumti seems to refer to a non-existent referent, you may not understand what the speaker has in mind - the appropriate response is then
<jbophrase>ki'a</jbophrase>, asking for clarification.</para>
<para>Presupposition failure can be marked directly if the presupposition is overt; if not, one can insert a
<quote>mock presupposition</quote> to question with the sumti tcita (selma'o BAI) word
<jbophrase>ji'u</jbophrase>;
<jbophrase>ji'uku</jbophrase> thus explicitly refers to an unexpressed assumption, and
<jbophrase>ji'una'iku</jbophrase> metalinguistically says that something is wrong with that assumption. (See
- <xref linkend="chapter-tenses"/>.)</para>
+ <xref linkend="chapter-sumti-tcita"/>.)</para>
<para>Scale errors and category errors can be similarly expressed with selma'o BAI.
<jbophrase>le'a</jbophrase> has meaning
<quote>of category/class/type X</quote>,
<jbophrase>ci'u</jbophrase> has meaning
<quote>on scale X</quote>, and
<jbophrase>ci'e</jbophrase>, based on
<jbophrase>ciste</jbophrase>, can be used to talk about universes of discourse defined either as systems or sets of components, as shown in
<xref linkend="section-questions"/>.
<jbophrase>kai</jbophrase> and
@@ -1493,21 +1494,21 @@
<quote>good</quote> is
<quote>bad</quote>.</para>
<para>This mutual independence of gismu is only an ideal. Pragmatically, people will categorize things based on their world-views. We will write dictionary definitions that will relate gismu, unfortunately including some of these world-view assumptions. Lojbanists should try to minimize these assumptions, but this seems a likely area where logical rules will break down (or where Sapir-Whorf effects will be made evident). In terms of negation, however, it is vital that we clearly preserve the capability of denying a presumably obvious scale or category assumption.</para>
<para>Solecisms, grammatical and spelling errors will be marked by marking the offending word or phrase with
<jbophrase>na'i</jbophrase> (in the manner of any selma'o UI cmavo). In this sense,
<jbophrase>na'i</jbophrase> becomes equivalent to the English metalinguistic marker
<quote>[sic]</quote>. Purists may choose to use ZOI or LOhU/LEhU quotes or
<jbophrase>sa'a</jbophrase>-marked corrections to avoid repeating a truly unparsable passage, especially if a computer is to analyze the speech/text. See
- <xref linkend="chapter-structure"/> for explanations of these usages.</para>
+ <xref linkend="chapter-structure-section-parentheses"/> for explanations of these usages.</para>
<para>In summary, metalinguistic negation will typically take the form of referring to a previous statement and marking it with one or more
<jbophrase>na'i</jbophrase> to indicate what metalinguistic errors have been made, and then repeating the statement with corrections. References to previous statements may be full repetitions, or may use members of selma'o GOhA.
<jbophrase>na'i</jbophrase> at the beginning of a statement merely says that something is inappropriate about the statement, without specificity.</para>
<para>In normal use, metalinguistic negation requires that a corrected statement follow the negated statement. In Lojban, however, it is possible to completely and unambiguously specify metalinguistic errors without correcting them. It will eventually be seen whether an uncorrected metalinguistic negation remains an acceptable form in Lojban. In such a statement, metalinguistic expression would involve an ellipsis not unlike that of tenseless expression.</para>
<para>Note that metalinguistic negation gives us another kind of legitimate negative answer to a
<jbophrase>xu</jbophrase> question (see
<xref linkend="section-questions"/>).
diff --git a/todocbook/16.xml b/todocbook/16.xml
index 783b2cf..b217d85 100644
--- a/todocbook/16.xml
+++ b/todocbook/16.xml
@@ -1,17 +1,16 @@
<chapter xml:id="chapter-quantifiers">
<title>
<quote>Who Did You Pass On The Road? Nobody</quote>: Lojban And Logic</title>
<section xml:id="section-introduction">
<title>What's wrong with this picture?</title>
- <para> <indexterm type="general-imported"><primary>nobody</primary><secondary>interpretation of</secondary></indexterm> The following brief dialogue is from
- <xref linkend="chapter-anaphoric-cmavo"/> of
+ <para> <indexterm type="general-imported"><primary>nobody</primary><secondary>interpretation of</secondary></indexterm> The following brief dialogue is from Chapter 7 of
<citation>Through The Looking Glass</citation> by Lewis Carroll.</para>
<example xml:id="example-random-id-KB90">
<title>
<anchor xml:id="c16e1d1"/>
</title>
<para>
<quote>Who did you pass on the road?</quote> the King went on, holding out his hand to the Messenger for some more hay.</para>
</example>
<example xml:id="example-random-id-1UVT">
<title>
@@ -102,21 +101,21 @@
<anchor xml:id="c16e2d2"/>
</title>
<interlinear-gloss>
<jbo>[zo'e] viska mi</jbo>
<gloss>Something-unspecified sees me.</gloss>
</interlinear-gloss>
</example>
<para> <indexterm type="lojban-word-imported"><primary>zo'e</primary></indexterm> <indexterm type="general-imported"><primary>something</primary><secondary>unspecified definite with "zo'e"</secondary></indexterm> <indexterm type="general-imported"><primary>zo'e</primary><secondary>as a translation for "something"</secondary></indexterm> The cmavo
<jbophrase>zo'e</jbophrase> indicates that a sumti has been omitted (indeed, even
<jbophrase>zo'e</jbophrase> itself can be omitted in this case, as explained in
- <xref linkend="chapter-anaphoric-cmavo"/>) and the listener must fill in the correct value from context. In other words,
+ <xref linkend="chapter-anaphoric-cmavo-section-zohe-cohe-series"/>) and the listener must fill in the correct value from context. In other words,
<xref linkend="example-random-id-b9pV"/> means
<quote>‘You-know-what' sees me.</quote></para>
<para>However,
<xref linkend="example-random-id-Mxj3"/> is just as likely to assert simply that there is someone who sees me, in which case a correct translation is:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-jjLd">
<title>
<anchor xml:id="c16e2d3"/>
</title>
<interlinear-gloss>
<jbo>da zo'u da viska mi</jbo>
@@ -197,21 +196,21 @@
<anchor xml:id="c16e2d7"/>
</title>
<interlinear-gloss>
<jbo>da zo'u le da gerku cu viska mi</jbo>
<gloss>There-is-an-X such-that the of-X dog sees me</gloss>
<en>Somebody's dog sees me</en>
</interlinear-gloss>
</example>
<para> <indexterm type="example-imported"><primary>somebody's dog</primary><secondary>example</secondary></indexterm> is perfectly correct even though the
<jbophrase>da</jbophrase> is used only in a possessive construction. (Possessives are explained in
- <xref linkend="chapter-relative-clauses"/>.)</para>
+ <xref linkend="chapter-relative-clauses-section-possessive-sumti"/>.)</para>
<para> <indexterm type="general-imported"><primary>logical variables</primary><secondary>when not in main bridi</secondary></indexterm> It is very peculiar, however, even if technically grammatical, for the variable not to appear in the main bridi at all:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-mE4m">
<title>
<anchor xml:id="c16e2d8"/>
</title>
<interlinear-gloss>
<jbo>da zo'u la ralf. gerku</jbo>
<en>There is something such that Ralph is a dog.</en>
</interlinear-gloss>
@@ -382,21 +381,21 @@
<gloss>Each dog breathes.</gloss>
<en>All dogs breathe.</en>
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>dog breathes</primary></indexterm>
<xref linkend="example-random-id-DFen"/> is a silly falsehood, but
<xref linkend="example-random-id-njh0"/> is an important truth (at least if applied in a timeless or potential sense: see
- <xref linkend="chapter-tenses"/>). Note the various colloquial translations
+ <xref linkend="chapter-tenses-section-caha"/>). Note the various colloquial translations
<quote>every dog</quote>,
<quote>each dog</quote>, and
<quote>all dogs</quote>. They all come to the same thing in Lojban, since what is true of every dog is true of all dogs.
<quote>All dogs</quote> is treated as an English plural and the others as singular, but Lojban makes no distinction.</para>
<para>If we make an existential claim about dogs rather than a universal one, we get:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-4BTd">
<title>
<anchor xml:id="c16e4d5"/>
@@ -490,21 +489,21 @@
<title>
<anchor xml:id="c16e5d6"/>
</title>
<interlinear-gloss>
<jbo>ro da poi prenu cu se batci de poi gerku</jbo>
<gloss>Every-X which is-a-person is-bitten-by some-Y which is-a-dog.</gloss>
</interlinear-gloss>
</example>
<para>using the conversion operator
<jbophrase>se</jbophrase> (explained in
- <xref linkend="chapter-selbri"/>) to change the selbri
+ <xref linkend="chapter-selbri-section-place-conversion"/>) to change the selbri
<jbophrase>batci</jbophrase> (
<quote>bites</quote>) into
<jbophrase>se batci</jbophrase> (
<quote>is bitten by</quote>). The translation given in
<xref linkend="example-random-id-KLAr"/> 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
<jbophrase>se</jbophrase>; one must be careful to preserve the order of the variables.</para>
<para> <indexterm type="lojban-word-imported"><primary>poi</primary></indexterm> <indexterm type="lojban-word-imported"><primary>ro</primary></indexterm> <indexterm type="general-imported"><primary>poi</primary><secondary>dropping from multiple appearances on logical variables</secondary></indexterm> <indexterm type="general-imported"><primary>ro</primary><secondary>dropping from multiple appearances on logical variables</secondary></indexterm> <indexterm type="general-imported"><primary>logical variables</primary><secondary>with poi</secondary><tertiary>in multiple appearances</tertiary></indexterm> <indexterm type="general-imported"><primary>logical variables</primary><secondary>with ro</secondary><tertiary>in multiple appearances</tertiary></indexterm> If a variable occurs more than once, then any
@@ -590,21 +589,21 @@
<gloss>For-at-least-two Xes : X sees me.</gloss>
</interlinear-gloss>
</example>
<para>which would be false if nothing, or only one thing, saw the speaker, but not otherwise. We note the
<jbophrase>su'o</jbophrase> here meaning
<quote>at least</quote>;
<jbophrase>su'o</jbophrase> by itself is short for
<jbophrase>su'opa</jbophrase> where
<jbophrase>pa</jbophrase> means
<quote>one</quote>, as is explained in
- <xref linkend="chapter-mekso"/>.</para>
+ <xref linkend="chapter-mekso-section-approximation"/>.</para>
<para> <indexterm type="general-imported"><primary>prenex</primary><secondary>removing when numeric quantifiers present</secondary></indexterm> The prenex may be removed from
<xref linkend="example-random-id-3C69"/> and
<xref linkend="example-random-id-mSzo"/> as from the others, leading to:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-2r5v">
<title>
<anchor xml:id="c16e6d4"/>
</title>
<interlinear-gloss>
<jbo>re da viska mi</jbo>
<en>Two Xes see me.</en>
@@ -747,21 +746,21 @@
</example>
<para>which picks out two groups, one of three dogs and the other of two men, and says that every one of the dogs bites each of the men. The second Lojban version uses forethought; note that
<jbophrase>nu'u</jbophrase> is an elidable terminator, and in this case can be freely elided.</para>
<para> <indexterm type="general-imported"><primary>ro</primary><secondary>effect of order when multiple in sentence</secondary></indexterm> <indexterm type="general-imported"><primary>indefinite sumti</primary><secondary>compared to sumti with lo</secondary></indexterm> <indexterm type="general-imported"><primary>sumti with lo</primary><secondary>compared to indefinite sumti</secondary></indexterm> <indexterm type="general-imported"><primary>quantified sumti</primary><secondary>different types contrasted for scope for distribution</secondary></indexterm> What about descriptors, like
<jbophrase>ci lo gerku</jbophrase>,
<jbophrase>le nanmu</jbophrase> or
<jbophrase>re le ci mlatu</jbophrase>? They too can be grouped in termsets, but usually need not be, except for the
<jbophrase>lo</jbophrase> case which functions like the case without a descriptor. Unless an actual quantifier precedes it,
<jbophrase>le nanmu</jbophrase> means
<jbophrase>ro le nanmu</jbophrase>, as is explained in
- <xref linkend="chapter-sumti"/>. Two sumti with
+ <xref linkend="chapter-sumti-section-quantified-descriptions"/>. Two sumti with
<jbophrase>ro</jbophrase> quantifiers are independent of order, so:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-MADY">
<title>
<anchor xml:id="c16e7d6"/>
</title>
<interlinear-gloss>
<jbo>[ro] le ci gerku cu batci [ro] le re nanmu</jbo>
<gloss>[All of] the three dogs bite [all of] the two men.</gloss>
</interlinear-gloss>
</example>
@@ -903,21 +902,21 @@
<section xml:id="section-negation-boundaries">
<title>Negation boundaries</title>
<para> <indexterm type="general-imported"><primary>"there is a Y"</primary><secondary>expression</secondary><tertiary>notation convention</tertiary></indexterm> This section, as well as
<xref linkend="section-connectives"/> through
<xref linkend="section-demorgans-law"/>, are in effect a continuation of
<xref linkend="chapter-negation"/>, introducing features of Lojban negation that require an understanding of prenexes and variables. In the examples below,
<quote>there is a Y</quote> and the like must be understood as
<quote>there is at least one Y, possibly more</quote>.</para>
<para> <indexterm type="general-imported"><primary>bridi negation</primary><secondary>two forms of</secondary></indexterm> As explained in
- <xref linkend="chapter-negation"/>, the negation of a bridi is usually accomplished by inserting
+ <xref linkend="chapter-negation-section-bridi-negation"/>, the negation of a bridi is usually accomplished by inserting
<jbophrase>na</jbophrase> at the beginning of the selbri:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-hBRH">
<title>
<anchor xml:id="c16e9d1"/>
</title>
<interlinear-gloss>
<jbo>mi na klama le zarci</jbo>
<gloss>I [false] go-to the store.</gloss>
<gloss>It is false that I go to the store.</gloss>
<en>I don't go to the store.</en>
@@ -1481,22 +1480,22 @@
<jbophrase>naku</jbophrase> negation, then quantified variables that cross the negation boundary must be inverted.</para>
<para> <indexterm type="general-imported"><primary>negation manipulation</primary><secondary>"na" contrasted with "naku" in difficulty of</secondary></indexterm> <indexterm type="general-imported"><primary>negation manipulation</primary><secondary>"naku" contrasted with "na" in difficulty of</secondary></indexterm> Clearly, if all of Lojban negation was built on
<jbophrase>naku</jbophrase> negation instead of
<jbophrase>na</jbophrase> negation, logical manipulation in Lojban would be as difficult as in natural languages. In
<xref linkend="section-demorgans-law"/>, for example, we'll discuss DeMorgan's Law, which must be used whenever a sumti with a logical connection is moved across a negation boundary.</para>
<para> <indexterm type="general-imported"><primary>naku</primary><secondary>in linked sumti places</secondary></indexterm> Since
<jbophrase>naku</jbophrase> has the grammar of a sumti, it can be placed almost anywhere a sumti can go, including
<jbophrase>be</jbophrase> and
<jbophrase>bei</jbophrase> clauses; it isn't clear what these mean, and we recommend avoiding such constructs.</para>
<para> <indexterm type="general-imported"><primary>double negation</primary><secondary>and naku</secondary></indexterm> <indexterm type="general-imported"><primary>naku</primary><secondary>multiple in sentence</secondary></indexterm> You can put multiple
- <jbophrase>naku</jbophrase> s in a sentence, each forming a separate negation boundary. Two adjacent
- <jbophrase>naku</jbophrase> s in a bridi are a double negative and cancel out:</para>
+ <jbophrase>naku</jbophrase>s in a sentence, each forming a separate negation boundary. Two adjacent
+ <jbophrase>naku</jbophrase>s in a bridi are a double negative and cancel out:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-u784">
<title>
<anchor xml:id="c16e11d15"/>
</title>
<interlinear-gloss>
<jbo>mi naku naku le zarci cu klama</jbo>
</interlinear-gloss>
</example>
<para>Other expressions using two
<jbophrase>naku</jbophrase> s may or may not cancel out. If there is no quantified variable between them, then the
@@ -1526,21 +1525,21 @@
<jbophrase>nai</jbophrase>,
<jbophrase>na</jbophrase> and
<jbophrase>se</jbophrase> modifier of the original connectives. Cancel any double negatives that result.</para>
<para> <indexterm type="general-imported"><primary>DeMorgan's Law</primary><secondary>and moving a logical connective relative to "naku"</secondary></indexterm> <indexterm type="general-imported"><primary>DeMorgan's Law</primary><secondary>and distributing a negation</secondary></indexterm> <indexterm type="general-imported"><primary>distributing a negation</primary></indexterm> When do we apply DeMorgan's Law? Whenever we wish to
<quote>distribute</quote> a negation over a logical connective; and, for internal
<jbophrase>naku</jbophrase> negation, whenever a logical connective moves in to, or out of, the scope of a negation - when it crosses a negation boundary.</para>
<para> <indexterm type="lojban-word-imported"><primary>nai</primary></indexterm> <indexterm type="lojban-word-imported"><primary>gi</primary></indexterm> <indexterm type="lojban-word-imported"><primary>ge</primary></indexterm> <indexterm type="lojban-word-imported"><primary>ga</primary></indexterm> <indexterm type="general-imported"><primary>DeMorgan's Law</primary><secondary>sample applications</secondary></indexterm> Let us apply DeMorgan's Law to some sample sentences. These sentences make use of forethought logical connectives, which are explained in
- <xref linkend="chapter-connectives"/>. It suffices to know that
+ <xref linkend="chapter-connectives-section-forethought-bridi-connection"/>. It suffices to know that
<jbophrase>ga</jbophrase> and
<jbophrase>gi</jbophrase>, used before each of a pair of sumti or bridi, mean
<quote>either</quote> and
<quote>or</quote> respectively, and that
<jbophrase>ge</jbophrase> and
<jbophrase>gi</jbophrase> used similarly mean
<quote>both</quote> and
<quote>and</quote>. Furthermore,
<jbophrase>ga</jbophrase>,
<jbophrase>ge</jbophrase>, and
@@ -1587,21 +1586,21 @@
</example>
<para>The
<jbophrase>ga</jbophrase> and
<jbophrase>gi</jbophrase>, meaning
<quote>either-or</quote>, have become
<jbophrase>ge</jbophrase> and
<jbophrase>gi</jbophrase>, meaning
<quote>both-and</quote>, as a consequence of moving the negators into the individual bridi.</para>
<para> <indexterm type="general-imported"><primary>DeMorgan's Law</primary><secondary>and bridi-tail logical connection</secondary></indexterm> <indexterm type="general-imported"><primary>bridi-tail logical connection</primary><secondary>and DeMorgan's Law</secondary></indexterm> Here is another example of DeMorgan's Law in action, involving bridi-tail logical connection (explained in
- <xref linkend="chapter-connectives"/>):</para>
+ <xref linkend="chapter-connectives-section-compound-bridi"/>):</para>
<example xml:id="example-random-id-qHpR" role="interlinear-gloss-example">
<title>
<anchor xml:id="c16e12d4"/>
</title>
<interlinear-gloss>
<jbo>la djein. le zarci na ge dzukla gi bajrykla</jbo>
<gloss>Jane to-the market [false] both walks and runs.</gloss>
</interlinear-gloss>
</example>
<example xml:id="example-random-id-qHQ2" role="interlinear-gloss-example">
@@ -1774,40 +1773,40 @@
</interlinear-gloss>
</example>
<para>What does
<xref linkend="example-random-id-x0FP"/> mean? The appearance of
<jbophrase>ci da</jbophrase> quantifies
<jbophrase>da</jbophrase> as referring to three things, which are restricted by the relative clause to be cats. When
<jbophrase>re da</jbophrase> appears later, it refers to two of those three things - there is no saying which ones. Further uses of
<jbophrase>da</jbophrase> alone, if there were any, would refer once more to the three cats, so the requantification of
<jbophrase>da</jbophrase> is purely local.</para>
<para> <indexterm type="general-imported"><primary>prenex scope</primary><secondary>in abstractions</secondary></indexterm> <indexterm type="general-imported"><primary>prenex scope</primary><secondary>in relative clauses</secondary></indexterm> <indexterm type="general-imported"><primary>prenex scope</primary><secondary>in embedded bridi</secondary></indexterm> <indexterm type="general-imported"><primary>prenex scope</primary><secondary>informal</secondary></indexterm> <indexterm type="general-imported"><primary>prenex scope</primary><secondary>for sentences joined by .i</secondary></indexterm> <indexterm type="general-imported"><primary>prenex scope</primary><secondary>for sentences joined by ijeks</secondary></indexterm> In general, the scope of a prenex that precedes a sentence extends to following sentences that are joined by ijeks (explained in
- <xref linkend="chapter-connectives"/>) such as the
+ <xref linkend="chapter-connectives-section-bridi-connection"/>) such as the
<jbophrase>.ije</jbophrase> in
<xref linkend="example-random-id-x0FP"/>. Theoretically, a bare
<jbophrase>.i</jbophrase> terminates the scope of the prenex. Informally, however, variables may persist for a while even after an
<jbophrase>.i</jbophrase>, as if it were an
<jbophrase>.ije</jbophrase>. Prenexes that precede embedded bridi such as relative clauses and abstractions extend only to the end of the clause, as explained in
<xref linkend="section-any"/>. A prenex preceding
<jbophrase>tu'e ... tu'u</jbophrase> long-scope brackets persists until the
<jbophrase>tu'u</jbophrase>, which may be many sentences or even paragraphs later.</para>
<para> <indexterm type="general-imported"><primary>subscripts</primary><secondary>use with logical variables</secondary></indexterm> <indexterm type="general-imported"><primary>logical variables</primary><secondary>creating more by subscripting</secondary></indexterm> If the variables
<jbophrase>da</jbophrase>,
<jbophrase>de</jbophrase>, and
<jbophrase>di</jbophrase> (or the selbri variables
<jbophrase>bu'a</jbophrase>,
<jbophrase>bu'e</jbophrase>, and
<jbophrase>bu'i</jbophrase>) are insufficient in number for handling a particular problem, the Lojban approach is to add a subscript to any of them. Each possible different combination of a subscript and a variable cmavo counts as a distinct variable in Lojban. Subscripts are explained in full in
- <xref linkend="chapter-structure"/>, but in general consist of the cmavo
+ <xref linkend="chapter-structure-section-subscripts"/>, but in general consist of the cmavo
<jbophrase>xi</jbophrase> (of selma'o XI) followed by a number, one or more lerfu words forming a single string, or a general mathematical expression enclosed in parentheses.</para>
<para>A quantifier can be prefixed to a variable that has already been bound either in a prenex or earlier in the bridi, thus:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-6gyb">
<title>
<anchor xml:id="c16e14d2"/>
</title>
<interlinear-gloss>
<jbo>ci da poi prenu cu se ralju pa da</jbo>
<gloss>Three Xs which are-persons are-led-by one-of X</gloss>
<en>Three people are led by one of them.</en>
diff --git a/todocbook/18.xml b/todocbook/18.xml
index 28823c0..1bf5b72 100644
--- a/todocbook/18.xml
+++ b/todocbook/18.xml
@@ -1543,21 +1543,21 @@
<xref linkend="section-indefinite-numbers"/>, all of these cmavo may be preceded by
<jbophrase>pi</jbophrase> to make the corresponding quantifiers for part of a whole. For example,
<jbophrase>pisu'o</jbophrase> means
<quote>at least some part of</quote>. The quantifiers
<jbophrase>ro</jbophrase>,
<jbophrase>su'o</jbophrase>,
<jbophrase>piro</jbophrase>, and
<jbophrase>pisu'o</jbophrase> are particularly important in Lojban, as they are implicitly used in the descriptions introduced by the cmavo of selma'o LA and LE, as explained in
- <xref linkend="chapter-sumti"/>. Descriptions in general are outside the scope of this chapter.</para>
+ <xref linkend="chapter-sumti-section-quantified-descriptions"/>. Descriptions in general are outside the scope of this chapter.</para>
</section>
<section xml:id="section-radixen">
<title>Non-decimal and compound bases</title>
<para>The following cmavo are discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>ju'u</cmavo>
<selmaho>VUhU</selmaho>
<description>to the base</description>
</cmavo-entry>
@@ -1871,21 +1871,21 @@
<en>There are many rats in the park.</en>
</interlinear-gloss>
</example>
<para>In
<xref linkend="example-random-id-n52D"/>, the conversion cmavo
<jbophrase>se</jbophrase> swaps the x1 and the x2 places, so that the new x1 is the set. The x4 set is unspecified, so the implication is that the rats are
<quote>many</quote> with respect to some unspecified comparison set.</para>
<para>More explanations about the interrelationship of sets, masses, and individuals can be found in
- <xref linkend="chapter-sumti"/>.</para>
+ <xref linkend="chapter-sumti-section-masses"/>.</para>
<para> <indexterm type="lojban-word-imported"><primary>moi</primary></indexterm> <indexterm type="general-imported"><primary>ordinal selbri</primary><secondary>definition</secondary></indexterm> <indexterm type="general-imported"><primary>ordinal selbri</primary><secondary>place structure</secondary></indexterm> The cmavo
<jbophrase>moi</jbophrase> creates ordinal selbri. The place structure is:</para>
<place-structure>
x1 is the (n)th member of set x2 when ordered by rule x3
</place-structure>
<para>Some examples:</para>
<example xml:id="example-random-id-qiHw" role="interlinear-gloss-example">
<title>
<anchor xml:id="c18e11d5"/>
@@ -2074,21 +2074,21 @@
<cmavo-entry>
<cmavo>xo</cmavo>
<selmaho>PA</selmaho>
<description>number question</description>
</cmavo-entry>
</cmavo-list>
<para> <indexterm type="lojban-word-imported"><primary>xo</primary></indexterm> <indexterm type="general-imported"><primary>number questions</primary></indexterm> <indexterm type="general-imported"><primary>questions</primary><secondary>number</secondary></indexterm> The cmavo
<jbophrase>xo</jbophrase>, a member of selma'o PA, is used to ask questions whose answers are numbers. Like most Lojban question words, it fills the blank where the answer should go. (See
- <xref linkend="chapter-structure"/> for more on Lojban questions.)</para>
+ <xref linkend="chapter-structure-section-questions"/> for more on Lojban questions.)</para>
<example xml:id="example-random-id-qIiE" role="interlinear-gloss-example">
<title>
<anchor xml:id="c18e12d1"/>
</title>
<interlinear-gloss>
<jbo>li re su'i re du li xo</jbo>
<gloss>The-number 2 plus 2 equals the-number what?</gloss>
<en>What is 2 + 2?</en>
</interlinear-gloss>
@@ -2184,21 +2184,21 @@
<anchor xml:id="c18e13d5"/>
</title>
<interlinear-gloss>
<jbo>xy.boi xi by.boi xi vo</jbo>
<math>x<subscript>b<subscript>4</subscript></subscript></math>
</interlinear-gloss>
</example>
<para>See
<xref linkend="example-random-id-eMsd"/> for the standard method of specifying multiple subscripts on a single object.</para>
<para>More information on the uses of subscripts may be found in
- <xref linkend="chapter-structure"/>.</para>
+ <xref linkend="chapter-structure-section-subscripts"/>.</para>
</section>
<section xml:id="section-infix-again">
<title>Infix operators revisited</title>
<para>The following cmavo are discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>tu'o</cmavo>
<selmaho>PA</selmaho>
<description>null operand</description>
@@ -2333,26 +2333,38 @@
<jbophrase>pi'a</jbophrase>, the matrix row operator, or
<jbophrase>sa'i</jbophrase>, the matrix column operator. The first combines vectors representing rows of the matrix, and the second combines vectors representing columns of the matrix. Both of them allow any number of arguments: additional arguments are tacked on with the null operator
<jbophrase>ge'a</jbophrase>.</para>
<para> <indexterm type="example-imported"><primary>magic square</primary><secondary>example</secondary></indexterm> Therefore, the
<quote>magic square</quote> matrix</para>
-
- <programlisting xml:space="preserve">
- 8 1 6
- 3 5 7
- 4 9 2
- </programlisting>
+ <informaltable>
+ <tgroup cols="3">
+ <colspec colnum="1" colname="col1"/>
+ <colspec colnum="2" colname="col2"/>
+ <colspec colnum="3" colname="col3"/>
+ <tbody>
+ <row>
+ <entry>8</entry><entry>1</entry><entry>6</entry>
+ </row>
+ <row>
+ <entry>3</entry><entry>5</entry><entry>7</entry>
+ </row>
+ <row>
+ <entry>4</entry><entry>9</entry><entry>2</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
<para>can be represented either as:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-zbJP">
<title>
<anchor xml:id="c18e15d2"/>
</title>
<interlinear-gloss>
<jbo>jo'i biboi paboi xa pi'a jo'i ciboi muboi ze ge'a jo'i voboi soboi re</jbo>
<gloss>the-vector (8 1 6) matrix-row the-vector (3 5 7), the-vector (4 9 2)</gloss>
</interlinear-gloss>
@@ -2983,28 +2995,28 @@
<en>nineteenthly (higher order)</en>
</interlinear-gloss>
</example>
<para> <indexterm type="lojban-word-imported"><primary>MAI selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>mo'o</primary></indexterm> <indexterm type="example-imported"><primary>firstly</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>chapter numbering</primary></indexterm> <indexterm type="general-imported"><primary>mo'o</primary><secondary>contrasted with mai</secondary></indexterm> <indexterm type="general-imported"><primary>mai</primary><secondary>contrasted with mo'o</secondary></indexterm> <indexterm type="general-imported"><primary>text</primary><secondary>division numbering with -mai</secondary></indexterm> The difference between
<jbophrase>mai</jbophrase> and
<jbophrase>mo'o</jbophrase> is that
<jbophrase>mo'o</jbophrase> enumerates larger subdivisions of a text. Each
<jbophrase>mo'o</jbophrase> subdivision can then be divided into pieces and internally numbered with
<jbophrase>mai</jbophrase>. If this chapter were translated into Lojban, each section would be numbered with
<jbophrase>mo'o</jbophrase>. (See
- <xref linkend="chapter-structure"/> for more on these words.)</para>
+ <xref linkend="chapter-structure-section-utterance-ordinals"/> for more on these words.)</para>
<para> <indexterm type="lojban-word-imported"><primary>roi</primary></indexterm> <indexterm type="example-imported"><primary>once</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>tense</primary><secondary>numerical</secondary></indexterm> A numerical tense can be created by suffixing a digit string with
<jbophrase>roi</jbophrase>. This usage generates tenses corresponding to English
<quote>once</quote>,
<quote>twice</quote>, and so on. This topic belongs to a detailed discussion of Lojban tenses, and is explained further in
- <xref linkend="chapter-tenses"/>.</para>
+ <xref linkend="chapter-tenses-section-interval-properties"/>.</para>
<para> <indexterm type="lojban-word-imported"><primary>boi</primary></indexterm> <indexterm type="general-imported"><primary>numerical tenses</primary><secondary>effect on use of boi</secondary></indexterm> <indexterm type="general-imported"><primary>boi</primary><secondary>exception before ROI</secondary></indexterm> <indexterm type="general-imported"><primary>boi</primary><secondary>exception before MAI</secondary></indexterm> <indexterm type="general-imported"><primary>MAI selma'o</primary><secondary>exception on use of boi before</secondary></indexterm> <indexterm type="general-imported"><primary>ROI selma'o</primary><secondary>exception on use of boi before</secondary></indexterm> Note: the elidable terminator
<jbophrase>boi</jbophrase> is not used between a number and a member of MAI or ROI.</para>
</section>
<section xml:id="section-explicit-operator-precedence">
<title>Explicit operator precedence</title>
<para>As mentioned earlier, Lojban does provide a way for the precedences of operators to be explicitly declared, although current parsers do not understand these declarations.</para>
<para> <indexterm type="lojban-word-imported"><primary>SEI selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>ti'o</primary></indexterm> The declaration is made in the form of a metalinguistic comment using
<jbophrase>ti'o</jbophrase>, a member of selma'o SEI.
@@ -3231,21 +3243,21 @@
<section xml:id="section-selmaho-summary">
<title>mekso selma'o summary</title>
<para>Except as noted, each selma'o has only one cmavo.</para>
<place-structure>
<cmavo-entry>
<selmaho>BOI</selmaho>
<description>elidable terminator for numerals and lerfu strings</description>
</cmavo-entry>
<cmavo-entry>
<selmaho>BY</selmaho>
- <description>lerfu for variables and functions (see <xref linkend="chapter-letterals"/>)</description>
+ <description>lerfu for variables and functions (see <xref linkend="chapter-letterals-section-math"/>)</description>
</cmavo-entry>
<cmavo-entry>
<selmaho>FUhA</selmaho>
<description>reverse-Polish flag</description>
</cmavo-entry>
<cmavo-entry>
<selmaho>GOhA</selmaho>
<description>includes <jbophrase>du</jbophrase> (mathematical equality) and other non-mekso cmavo</description>
</cmavo-entry>
diff --git a/todocbook/19.xml b/todocbook/19.xml
index a2f5bca..7a6f2ef 100644
--- a/todocbook/19.xml
+++ b/todocbook/19.xml
@@ -34,42 +34,42 @@
<jbophrase>.i</jbophrase> signals a new sentence on the same topic, not necessarily by the same speaker. The relationship between the sentences is left vague, except in stories, where the relationship usually is temporal, and the following sentence states something that happened after the previous sentence.</para>
<para>Note that although the first letter of an English sentence is capitalized, the cmavo
<jbophrase>.i</jbophrase> is never capitalized. In writing, it is appropriate to place extra space before
<jbophrase>.i</jbophrase> to make it stand out better for the reader. In some styles of Lojban writing, every
<jbophrase>.i</jbophrase> is placed at the beginning of a line, possibly leaving space at the end of the previous line.</para>
<para>An
<jbophrase>.i</jbophrase> cmavo may or may not be used when the speaker of the following sentence is different from the speaker of the preceding sentence, depending on whether the sentences are felt to be connected or not.</para>
<para>An
<jbophrase>.i</jbophrase> cmavo can be compounded with a logical or non-logical connective (a jek or joik), a modal or tense connective, or both: these constructs are explained in
- <xref linkend="chapter-sumti-tcita"/>,
- <xref linkend="chapter-tenses"/>, and
- <xref linkend="chapter-connectives"/>. In all cases, the
+ <xref linkend="chapter-sumti-tcita-section-modal-connectives"/>,
+ <xref linkend="chapter-tenses-section-tense-connection"/>, and
+ <xref linkend="chapter-connectives-section-bridi-connection"/>. In all cases, the
<jbophrase>.i</jbophrase> comes first in the compound. Attitudinals can also be attached to an
<jbophrase>.i</jbophrase> if they are meant to apply to the whole sentence: see
- <xref linkend="chapter-attitudinals"/>.</para>
+ <xref linkend="chapter-attitudinals-section-scope"/>.</para>
<para> <indexterm type="lojban-word-imported"><primary>BO selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>bo</primary></indexterm> <indexterm type="general-imported"><primary>sentences</primary><secondary>close grouping</secondary></indexterm> There exist a pair of mechanisms for binding a sequence of sentences closely together. If the
<jbophrase>.i</jbophrase> (with or without connectives) is followed by
<jbophrase>bo</jbophrase> (of selma'o BO), then the two sentences being separated are understood to be more closely grouped than sentences connected by
<jbophrase>.i</jbophrase> alone.</para>
<para> <indexterm type="lojban-word-imported"><primary>TUhU selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>TUhE selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>tu'u</primary></indexterm> <indexterm type="lojban-word-imported"><primary>tu'e</primary></indexterm> <indexterm type="general-imported"><primary>title</primary><secondary>specifying with tu'e…tu'u</secondary></indexterm> Similarly, a group of sentences can be preceded by
<jbophrase>tu'e</jbophrase> (of selma'o TUhE) and followed by
<jbophrase>tu'u</jbophrase> (of selma'o TUhU) to fuse them into a single unit. A common use of
<jbophrase>tu'e ... tu'u</jbophrase> is to group the sentences which compose a poem: the title sentence would precede the group, separated from it by
<jbophrase>.i</jbophrase>. Another use might be a set of directions, where each numbered direction might be surrounded by
<jbophrase>tu'e ... tu'u</jbophrase> and contain one or more sentences separated by
<jbophrase>.i</jbophrase>. Grouping with
<jbophrase>tu'e</jbophrase> and
<jbophrase>tu'u</jbophrase> is analogous to grouping with
<jbophrase>ke</jbophrase> and
<jbophrase>ke'e</jbophrase> to establish the scope of logical or non-logical connectives (see
- <xref linkend="chapter-connectives"/>).</para>
+ <xref linkend="chapter-connectives-section-grouping"/>).</para>
</section>
<section xml:id="section-niho">
<title>Paragraphs: NIhO</title>
<para>The following cmavo are discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>ni'o</cmavo>
<selmaho>NIhO</selmaho>
<description>new topic</description>
</cmavo-entry>
@@ -205,58 +205,54 @@
<title>
<anchor xml:id="c19e4d5"/>
</title>
<interlinear-gloss>
<jbo>le finpe zo'u citka</jbo>
<gloss>the fish : eat</gloss>
</interlinear-gloss>
</example>
<para>Is the fish eating or being eaten? The sentence doesn't say. The Chinese equivalent of
<xref linkend="example-random-id-tpcK"/> is:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-N6H3">
+ <example xml:id="example-random-id-N6H3">
<title>
<anchor xml:id="c19e4d6"/>
</title>
- <interlinear-gloss>
- <jbo>yu</jbo>
- </interlinear-gloss>
+ <foreign xml:lang="zh">yu</foreign>
</example>
<para>which is vague in exactly the same way.</para>
<para>Grammatically, it is possible to have more than one sumti before
<jbophrase>zo'u</jbophrase>. This is not normally useful in topic-comment sentences, but is necessary in the other use of
<jbophrase>zo'u</jbophrase>: to separate a quantifying section from a bridi containing quantified variables. This usage belongs to a discussion of quantifier logic in Lojban (see
- <xref linkend="chapter-quantifiers"/>), but an example would be:</para>
+ <xref linkend="chapter-quantifiers-section-da-and-zohu"/>), but an example would be:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-6yRx">
<title>
<anchor xml:id="c19e4d7"/>
</title>
<interlinear-gloss>
<jbo>roda poi prenu ku'o su'ode zo'u de patfu da</jbo>
<gloss>For-all X which-are-persons, there-exists-a-Y such-that Y is the father of X.</gloss>
<en>Every person has a father.</en>
</interlinear-gloss>
</example>
<para>The string of sumti before
<jbophrase>zo'u</jbophrase> (called the
<quote>prenex</quote>: see
- <xref linkend="chapter-quantifiers"/>) may contain both a topic and bound variables:</para>
+ <xref linkend="chapter-quantifiers-section-da-and-zohu"/>) may contain both a topic and bound variables:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-ggMy">
<title>
<anchor xml:id="c19e4d8"/>
</title>
<interlinear-gloss>
- <jbo>loi patfu roda poi prenu ku'o</jbo>
- <gloss>su'ode zo'u de patfu da</gloss>
- <gloss>For-the-mass-of fathers for-all X which-are-persons,</gloss>
- <gloss>there-exists-a-Y such-that Y is the father of X.</gloss>
+ <jbo>loi patfu roda poi prenu ku'o su'ode zo'u de patfu da</jbo>
+ <gloss>For-the-mass-of fathers for-all X which-are-persons, there-exists-a-Y such-that Y is the father of X.</gloss>
<en>As for fathers, every person has one.</en>
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>topic/comment</primary><secondary>multiple sentence</secondary></indexterm> To specify a topic which affects more than one sentence, wrap the sentences in
<jbophrase>tu'e ... tu'u</jbophrase> brackets and place the topic and the
<jbophrase>zo'u</jbophrase> directly in front. This is the exception to the rule that a topic attaches directly to a sentence:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-mK5Y">
<title>
<anchor xml:id="c19e4d9"/>
</title>
@@ -389,21 +385,21 @@
<title>
<anchor xml:id="c19e5d1"/>
</title>
<interlinear-gloss>
<jbo>xu do klama le zarci</jbo>
<gloss>[True or false?] You go to the store</gloss>
<en>Are you going to the store/Did you go to the store?</en>
</interlinear-gloss>
</example>
<para>(Since the Lojban is tenseless, either colloquial translation might be correct.) Truth questions are further discussed in
- <xref linkend="chapter-negation"/>.</para>
+ <xref linkend="chapter-negation-section-questions"/>.</para>
<para> <indexterm type="general-imported"><primary>questions</primary><secondary>fill-in-the-blank</secondary></indexterm> Fill-in-the-blank questions have a cmavo representing some Lojban word or phrase which is not known to the questioner, and which the answerer is to supply. There are a variety of cmavo belonging to different selma'o which provide different kinds of blanks.</para>
<para> <indexterm type="lojban-word-imported"><primary>KOhA selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>ma</primary></indexterm> <indexterm type="general-imported"><primary>questions</primary><secondary>sumti</secondary></indexterm> Where a sumti is not known, a question may be formed with
<jbophrase>ma</jbophrase> (of selma'o KOhA), which is a kind of pro-sumti:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-Pqzy">
<title>
<anchor xml:id="c19e5d2"/>
</title>
<interlinear-gloss>
<jbo>ma klama le zarci</jbo>
<gloss>[What sumti?] goes-to the store</gloss>
@@ -477,24 +473,24 @@
<jbo>la djan. la marcas. le zarci le briju</jbo>
<gloss>John, Marsha, the store, the office.</gloss>
<en>John and Marsha go to the store and the office, respectively.</en>
</interlinear-gloss>
</example>
<para>(Note: A mechanical substitution of
<xref linkend="example-random-id-yGYX"/> into
<xref linkend="example-random-id-nDeV"/> produces an ungrammatical result, because
- <jbophrase>* ... le zarci fa'u le briju</jbophrase> is ungrammatical Lojban: the first
+ <jbophrase valid="false">* ... le zarci fa'u le briju</jbophrase> is ungrammatical Lojban: the first
<jbophrase>le zarci</jbophrase> has to be closed with its proper terminator
<jbophrase>ku</jbophrase>, for reasons explained in
- <xref linkend="chapter-connectives"/>. This effect is not important: Lojban behaves as if all elided terminators have been supplied in both question and answer before inserting the latter into the former. The exchange is grammatical if question and answer are each separately grammatical.)</para>
+ <xref linkend="chapter-connectives-section-non-logical-connectives"/>. This effect is not important: Lojban behaves as if all elided terminators have been supplied in both question and answer before inserting the latter into the former. The exchange is grammatical if question and answer are each separately grammatical.)</para>
<para> <indexterm type="lojban-word-imported"><primary>GOhA selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>mo</primary></indexterm> <indexterm type="general-imported"><primary>questions</primary><secondary>selbri</secondary></indexterm> Questions to be answered with a selbri are expressed with
<jbophrase>mo</jbophrase> of selma'o GOhA, which is a kind of pro-bridi:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-uVCW">
<title>
<anchor xml:id="c19e5d9"/>
</title>
<interlinear-gloss>
<jbo>la lojban. mo</jbo>
<gloss>Lojban [what selbri?]</gloss>
<en>What is Lojban?</en>
@@ -528,36 +524,36 @@
</interlinear-gloss>
</example>
<para>Fill-in-the-blank questions may also be asked about: logical connectives (using cmavo
<jbophrase>ji</jbophrase> of A,
<jbophrase>ge'i</jbophrase> of GA,
<jbophrase>gi'i</jbophrase> of GIhA,
<jbophrase>gu'i</jbophrase> of GUhA, or
- <jbophrase>je'i</jbophrase> of JA, and receiving an ek, gihek, ijek, or ijoik as an answer) - see
+ <jbophrase>je'i</jbophrase> of JA, and receiving an ek, gihek, ijek, or ijoik as an answer) – see
- <xref linkend="chapter-connectives"/>; attitudes (using
- <jbophrase>pei</jbophrase> of UI, and receiving an attitudinal as an answer) - see
- <xref linkend="chapter-attitudinals"/>; place structures (using
- <jbophrase>fi'a</jbophrase> of FA, and receiving a cmavo of FA as an answer) - see
+ <xref linkend="chapter-connectives-section-questions"/>; attitudes (using
+ <jbophrase>pei</jbophrase> of UI, and receiving an attitudinal as an answer) – see
+ <xref linkend="chapter-attitudinals-section-questions-empathy-contours"/>; place structures (using
+ <jbophrase>fi'a</jbophrase> of FA, and receiving a cmavo of FA as an answer) – see
- <xref linkend="chapter-sumti-tcita"/>; tenses and modals (using
- <jbophrase>cu'e</jbophrase> of CUhE, and receiving any tense or BAI cmavo as an answer) - see
- <xref linkend="chapter-sumti-tcita"/> and
+ <xref linkend="chapter-sumti-tcita-section-FA"/>; tenses and modals (using
+ <jbophrase>cu'e</jbophrase> of CUhE, and receiving any tense or BAI cmavo as an answer) – see
+ <xref linkend="chapter-sumti-tcita-section-BAI"/> and
<xref linkend="chapter-tenses"/>.</para>
<para>Questions can be marked by placing
<jbophrase>pau</jbophrase> (of selma'o UI) before the question bridi. See
- <xref linkend="chapter-attitudinals"/> for details.</para>
+ <xref linkend="chapter-attitudinals-section-miscellanious"/> for details.</para>
<para>The full list of non-bridi utterances suitable as answers to questions is:</para>
<itemizedlist>
<listitem>
<para> <indexterm type="general-imported"><primary>linked arguments</primary></indexterm> <indexterm type="general-imported"><primary>utterances</primary><secondary>non-bridi</secondary></indexterm> any number of sumti (with elidable terminator
<jbophrase>vau</jbophrase>, see
<xref linkend="chapter-sumti"/>)</para>
</listitem>
<listitem>
<para>an ek or gihek (logical connectives, see
<xref linkend="chapter-connectives"/>)</para>
@@ -577,40 +573,40 @@
<xref linkend="chapter-relative-clauses"/>)</para>
</listitem>
<listitem>
<para>a prenex/topic (to modify some previously expressed bridi, see
<xref linkend="chapter-quantifiers"/>)</para>
</listitem>
<listitem>
<para>linked arguments (beginning with
<jbophrase>be</jbophrase> or
- <jbophrase>bei</jbophrase> and attached to some previously expressed selbri, often in a description,see
- <xref linkend="chapter-selbri"/>)</para>
+ <jbophrase>bei</jbophrase> and attached to some previously expressed selbri, often in a description, see
+ <xref linkend="chapter-selbri-section-be-sumti"/>)</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
<jbophrase>doi</jbophrase>, see
<xref linkend="chapter-sumti"/>)</para>
</listitem>
<listitem>
<para>indicators (to express a prevailing attitude, see
<xref linkend="chapter-attitudinals"/>)</para>
</listitem>
<listitem>
<para>
<jbophrase>nai</jbophrase> (to vaguely negate something or other, see
- <xref linkend="chapter-negation"/>)</para>
+ <xref linkend="chapter-negation-section-other-negation"/>)</para>
</listitem>
</itemizedlist>
<para>Where not needed for the expression of answers, most of these are made grammatical for pragmatic reasons: people will say them in conversation, and there is no reason to rule them out as ungrammatical merely because most of them are vague.</para>
</section>
<section xml:id="section-subscripts">
<title>Subscripts: XI</title>
<para>The following cmavo is discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>xi</cmavo>
@@ -666,21 +662,21 @@
</title>
<interlinear-gloss>
<jbo>la'edi'u cu nunkla mi le zarci le zdani le dargu le karce</jbo>
<gloss>The-referent-of-the-previous-sentence is-an-event-of-going by-me to-the market from-the house via-the road using-the car.</gloss>
</interlinear-gloss>
</example>
<para> <indexterm type="lojban-word-imported"><primary>SE selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>se</primary></indexterm> <indexterm type="general-imported"><primary>FA selma'o</primary><secondary>after 5th place</secondary></indexterm> <indexterm type="general-imported"><primary>SE selma'o</primary><secondary>after 5th place</secondary></indexterm> <indexterm type="general-imported"><primary>subscripts</primary><secondary>and sumti re-ordering</secondary></indexterm>
<xref linkend="example-random-id-sMPn"/> shows that
<jbophrase>nunkla</jbophrase> has six places: the five places of
<jbophrase>klama</jbophrase> plus a new one (placed first) for the event itself. Performing transformations similar to that of
- <xref linkend="example-random-id-QPGC"/> requires an additional conversion cmavo that exchanges the x1 and x6 places. The solution is to use any cmavo of SE with a subscript "6" (<xref linkend="chapter-structure"/>):</para>
+ <xref linkend="example-random-id-QPGC"/> requires an additional conversion cmavo that exchanges the x1 and x6 places. The solution is to use any cmavo of SE with a subscript "6" (<xref linkend="section-subscripts"/>):</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-zGhw">
<title>
<anchor xml:id="c19e6d5"/>
</title>
<interlinear-gloss>
<jbo>le karce cu sexixa nunkla mi le zarci le zdani le dargu la'edi'u</jbo>
<gloss>The car is-a-transportation-means-in-the-event-of-going by-me to-the market via-the road which-is-referred-to-by-the-last-sentence.</gloss>
</interlinear-gloss>
</example>
@@ -1406,21 +1402,21 @@
</title>
<interlinear-gloss>
<jbo>mi klama la za'e. .albeinias</jbo>
<gloss>I go-to so-called Albania</gloss>
</interlinear-gloss>
</example>
<para>marks a Lojbanization of an English name, where a more appropriate standard form might be something like
- <jbophrase>la ctiipyris.</jbophrase>, reflecting the country's name in Albanian.</para>
+ <jbophrase>la ckiipyris.</jbophrase>, reflecting the country's name in Albanian.</para>
<para> <indexterm type="general-imported"><primary>unabridged dictionary</primary></indexterm> Before a lujvo or fu'ivla,
<jbophrase>za'e</jbophrase> indicates that the word has been made up on the spot and may be used in a sense that is not found in the unabridged dictionary (when we have an unabridged dictionary!).</para>
</section>
<section xml:id="section-parentheses">
<title>Parenthesis and metalinguistic commentary: TO, TOI, SEI</title>
<para>The following cmavo are discussed in this section:</para>
<cmavo-list>
diff --git a/todocbook/20.xml b/todocbook/20.xml
index 0e66406..091c66a 100644
--- a/todocbook/20.xml
+++ b/todocbook/20.xml
@@ -1212,21 +1212,21 @@
</bridgehead>
<para>A tense indicating dimensionality in space (line, plane, volume, or space-time interval).</para>
<programlisting xml:space="preserve">
le verba ve'a vi'a cadzu le bisli
The child [medium space interval] [2-dimensional] walks-on the ice.
In a medium-sized area, the child walks on the ice.
</programlisting>
<bridgehead>
<anchor xml:id="VUhO"/> selma'o VUhO (
- <xref linkend="cll_chapter8-section8"/>)
+ <xref linkend="chapter-vuho"/>)
</bridgehead>
<para>Attaches relative clauses or phrases to a whole (possibly connected) sumti, rather than simply to the leftmost portion of the sumti.</para>
<programlisting xml:space="preserve">
la frank. ce la djordj. vu'o noi gidva cu zvati le kumfa
Frank [in-set-with] George, which are-guides, are-in the room.
Frank and George, who are guides, are in the room.
</programlisting>
<bridgehead>
<anchor xml:id="VUhU"/> selma'o VUhU (
diff --git a/todocbook/3.xml b/todocbook/3.xml
index 6bbe930..b6168e6 100644
--- a/todocbook/3.xml
+++ b/todocbook/3.xml
@@ -322,23 +322,23 @@
<phrase role="IPA">[h]</phrase>). The letter
<quote>h</quote> is not used to represent this sound for two reasons: primarily in order to simplify explanations of the morphology, but also because the sound is very common, and the apostrophe is a visually lightweight representation of it. The apostrophe sound is a consonant in nature, but is not treated as either a consonant or a vowel for purposes of Lojban morphology (word-formation), which is explained in
<xref linkend="chapter-morphology"/>. In addition, the apostrophe visually parallels the comma and the period, which are also used (in different ways) to separate syllables.</para>
<para> <indexterm type="general-imported"><primary>unvoiced vowel glide</primary><secondary>apostrophe as</secondary></indexterm> <indexterm type="general-imported"><primary>apostrophe</primary><secondary>purpose of</secondary></indexterm> The apostrophe is included in Lojban only to enable a smooth transition between vowels, while joining the vowels within a single word. In fact, one way to think of the apostrophe is as representing an unvoiced vowel glide.</para>
<para> <indexterm type="general-imported"><primary>apostrophe</primary><secondary>variant of</secondary></indexterm> As a permitted variant, any unvoiced fricative other than those already used in Lojban may be used to render the apostrophe: IPA
<phrase role="IPA">[θ]</phrase> is one possibility. The convenience of the listener should be regarded as paramount in deciding to use a substitute for
<phrase role="IPA">[h]</phrase>.</para>
<para> <indexterm type="general-imported"><primary>pause</primary><secondary>representation of in Lojban</secondary></indexterm> <indexterm type="general-imported"><primary>glottal stop</primary><secondary>as pause in Lojban</secondary></indexterm> <indexterm type="general-imported"><primary>period</primary><secondary>definition of</secondary></indexterm> The period represents a mandatory pause, with no specified length; a glottal stop (IPA
- <phrase role="IPA">[ʔ]</phrase>) is considered a pause of shortest length. A pause (or glottal stop) may appear between any two words, and in certain cases - explained in detail in
+ <phrase role="IPA">[ʔ]</phrase>) is considered a pause of shortest length. A pause (or glottal stop) may appear between any two words, and in certain cases – explained in detail in
- <xref linkend="chapter-morphology"/>- must occur. In particular, a word beginning with a vowel is always preceded by a pause, and a word ending in a consonant is always followed by a pause.</para>
+ <xref linkend="chapter-morphology-section-pauses"/> – must occur. In particular, a word beginning with a vowel is always preceded by a pause, and a word ending in a consonant is always followed by a pause.</para>
<para> <indexterm type="general-imported"><primary>period</primary><secondary>optional</secondary></indexterm> Technically, the period is an optional reminder to the reader of a mandatory pause that is dictated by the rules of the language; because these rules are unambiguous, a missing period can be inferred from otherwise correct text. Periods are included only as an aid to the reader.</para>
<para> <indexterm type="general-imported"><primary>period</primary><secondary>within a word</secondary></indexterm> A period also may be found apparently embedded in a word. When this occurs, such a written string is not one word but two, written together to indicate that the writer intends a unitary meaning for the compound. It is not really necessary to use a space between words if a period appears.</para>
<para> <indexterm type="general-imported"><primary>pause</primary><secondary>contrasted with syllable break</secondary></indexterm> <indexterm type="general-imported"><primary>syllable break</primary><secondary>contrasted with pause</secondary></indexterm> <indexterm type="general-imported"><primary>syllable break</primary><secondary>representation in Lojban</secondary></indexterm> <indexterm type="general-imported"><primary>comma</primary><secondary>definition of</secondary></indexterm> The comma is used to indicate a syllable break within a word, generally one that is not obvious to the reader. Such a comma is written to separate syllables, but indicates that there must be no pause between them, in contrast to the period. Between two vowels, a comma indicates that some type of glide may be necessary to avoid a pause that would split the two syllables into separate words. It is always legal to use the apostrophe (IPA
<phrase role="IPA">[h]</phrase>) sound in pronouncing a comma. However, a comma cannot be pronounced as a pause or glottal stop between the two letters separated by the comma, because that pronunciation would split the word into two words.</para>
<para> <indexterm type="general-imported"><primary>comma</primary><secondary>optional</secondary></indexterm> <indexterm type="general-imported"><primary>comma</primary><secondary>main use of</secondary></indexterm> Otherwise, a comma is usually only used to clarify the presence of syllabic
<jbophrase role="letteral">l</jbophrase>,
<jbophrase role="letteral">m</jbophrase>,
<jbophrase role="letteral">n</jbophrase>, or
@@ -617,21 +617,21 @@
<member><jbophrase>y'e</jbophrase></member>
<member><jbophrase>y'i</jbophrase></member>
<member><jbophrase>y'o</jbophrase></member>
<member><jbophrase>y'u</jbophrase></member>
<member><jbophrase>y'y</jbophrase></member>
</simplelist>
<para> <indexterm type="general-imported"><primary>vowel pairs</primary><secondary>involving y</secondary></indexterm> Vowel pairs involving
<jbophrase role="letteral">y</jbophrase> appear only in Lojbanized names. They could appear in cmavo (structure words), but only
<jbophrase>.y'y.</jbophrase> is so used - it is the Lojban name of the apostrophe letter (see
- <xref linkend="chapter-letterals"/>).</para>
+ <xref linkend="chapter-letterals-section-lerfu-liste"/>).</para>
<para> <indexterm type="general-imported"><primary>vowel pairs</primary><secondary>grouping of</secondary></indexterm> When more than two vowels occur together in Lojban, the normal pronunciation pairs vowels from the left into syllables, as in the Lojbanized name:</para>
<example role="pronunciation-example" xml:id="example-random-id-RxtI">
<title>
<anchor xml:id="c3e5d1"/>
</title>
<pronunciation>
<jbo>meiin.</jbo>
<jbo role="pronunciation">mei,in.</jbo>
</pronunciation>
</example>
@@ -1056,21 +1056,21 @@
</title>
<pronunciation>
<jbo>xapcke</jbo>
<ipa>[ˈxap ʃkɛ]</ipa>
<ipa>[ˈxa pɪ ʃkɛ]</ipa>
<ipa>[ˈxa pɪ ʃɪ kɛ]</ipa>
</pronunciation>
</example>
<para>In
<xref linkend="example-random-id-k2Gg"/>, we see that buffering vowels can be used in just some, rather than all, of the possible places: the second pronunciation buffers the
- <jbophrase role="morphology" valid="false">pc</jbophrase> consonant pair but not the
+ <jbophrase role="morphology">pc</jbophrase> consonant pair but not the
<jbophrase role="morphology">ck</jbophrase>. The third pronunciation buffers both.</para>
<example role="pronunciation-example" xml:id="example-random-id-k2hN">
<title>
<anchor xml:id="c3e8d5"/>
</title>
<pronunciation>
<jbo>ponyni'u</jbo>
<ipa>[po nə 'ni hu]</ipa>
</pronunciation>
</example>
@@ -1302,21 +1302,21 @@
<pronunciation>
<jbo>bisydja</jbo>
<jbo role="pronunciation">BI,sy,dja</jbo>
<jbo role="pronunciation">BI,syd,ja</jbo>
</pronunciation>
</example>
<para>This word is a compound word, or lujvo, built from the two affixes
<jbophrase role="rafsi">bis</jbophrase> and
<jbophrase role="rafsi">dja</jbophrase>. When they are joined, an impermissible consonant pair results:
<jbophrase role="morphology" valid="false">sd</jbophrase>. In accordance with the algorithm for making lujvo, explained in
- <xref linkend="chapter-morphology"/>, a
+ <xref linkend="chapter-morphology-section-lujvo-making"/>, a
<jbophrase role="letteral">y</jbophrase> is inserted to separate the impermissible consonant pair; the
<jbophrase role="letteral">y</jbophrase> is not counted as a syllable for purposes of stress determination.</para>
<example role="pronunciation-example" xml:id="example-random-id-5g4j">
<title>
<anchor xml:id="c3e9d12"/>
</title>
<pronunciation>
<jbo>da'udja</jbo>
<jbo role="pronunciation">da'UD,ja</jbo>
<jbo role="pronunciation">da'U,dja</jbo>
diff --git a/todocbook/4.xml b/todocbook/4.xml
index 041cb43..d4b6789 100644
--- a/todocbook/4.xml
+++ b/todocbook/4.xml
@@ -105,21 +105,21 @@
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>
<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 <jbophrase role="letteral">r</jbophrase>, <jbophrase role="letteral">l</jbophrase>, <jbophrase role="letteral">m</jbophrase>, <jbophrase role="letteral">n</jbophrase>) and an unvoiced consonant, or is one of certain specified forbidden pairs.
+ <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-section-clusters"/>. In brief, any consonant pair is permissible unless it: contains two identical letters, contains both a voiced (excluding <jbophrase role="letteral">r</jbophrase>, <jbophrase role="letteral">l</jbophrase>, <jbophrase role="letteral">m</jbophrase>, <jbophrase role="letteral">n</jbophrase>) and an unvoiced consonant, or is one of certain specified forbidden pairs.
</para>
</listitem>
<listitem>
<para> <indexterm type="general-imported"><primary>C/CC string</primary><secondary>as a symbol for a consonant triple</secondary></indexterm> C/CC represents a consonant triple. The first two consonants must constitute a permissible consonant pair; the last two consonants must constitute a permissible initial consonant pair.</para>
</listitem>
</orderedlist>
<para> <indexterm type="general-imported"><primary>brivla</primary><secondary>as one of the 3 basic word classes</secondary></indexterm> <indexterm type="general-imported"><primary>cmene</primary><secondary>as one of the 3 basic word classes</secondary></indexterm> <indexterm type="general-imported"><primary>cmavo</primary><secondary>as one of the 3 basic word classes</secondary></indexterm> <indexterm type="general-imported"><primary>parts of speech</primary></indexterm> <indexterm type="general-imported"><primary>word classes</primary></indexterm> Lojban has three basic word classes - parts of speech - in contrast to the eight that are traditional in English. These three classes are called cmavo, brivla, and cmene. Each of these classes has uniquely identifying properties - an arrangement of letters that allows the word to be uniquely and unambiguously recognized as a separate word in a string of Lojban, upon either reading or hearing, and as belonging to a specific word-class.</para>
<para>They are also functionally different: cmavo are the structure words, corresponding to English words like
@@ -869,32 +869,32 @@
<jbophrase role="diphthong">au</jbophrase>; and a CCV-form rafsi is possible only if the two consonants form a permissible initial consonant pair (see
<xref linkend="section-introduction"/>). Thus
<jbophrase>mamta</jbophrase>, which has the same form as
<jbophrase>salci</jbophrase>, can only have
<jbophrase role="rafsi">mam</jbophrase>,
<jbophrase role="rafsi" valid="false">mat</jbophrase>, and
<jbophrase role="rafsi" valid="false">ma'a</jbophrase> as possible rafsi: in fact, only
<jbophrase role="rafsi">mam</jbophrase> 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>
+ <xref linkend="chapter-lujvo"/>).</para> <!-- erratum: no such list anywhere -->
<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
<quote>fully reduced lujvo</quote>. Here are some examples of fully reduced lujvo:</para>
<example xml:id="example-random-id-qJc2" role="lujvo-example">
<title>
<anchor xml:id="c4e6d6"/>
</title>
<lujvo>
<jbo>cumfri</jbo>
<veljvo>from <jbophrase>cumki lifri</jbophrase></veljvo>
- <gloss><quote>possible experiglossce</quote></gloss>
+ <gloss><quote>possible experience</quote></gloss>
</lujvo>
</example>
<example xml:id="example-random-id-qjcA" role="lujvo-example">
<title>
<anchor xml:id="c4e6d7"/>
</title>
<lujvo>
<jbo>klezba</jbo>
<veljvo>from <jbophrase>klesi zbasu</jbophrase></veljvo>
<gloss><quote>category make</quote></gloss>
@@ -1084,21 +1084,21 @@
<quote>quark</quote>,
<quote>integral</quote>, or
<quote>iambic pentameter</quote>). These words are in effect names for concepts, and the names were invented by speakers of another language. The vast majority of words referring to plants, animals, foods, and scientific terminology cannot be easily expressed as tanru. They thus must be borrowed (actually
<quote>copied</quote>) into Lojban from the original language.</para>
<para><indexterm type="general-imported"><primary>borrowings</primary><secondary>Stage 1</secondary></indexterm> <indexterm type="general-imported"><primary>borrowings</primary><secondary>using foreign-language name</secondary></indexterm> <indexterm type="general-imported"><primary>borrowing</primary><secondary>four stages of</secondary></indexterm> There are four stages of borrowing in Lojban, as words become more and more modified (but shorter and easier to use). Stage 1 is the use of a foreign name quoted with the cmavo
<jbophrase>la'o</jbophrase> (explained in full in
- <xref linkend="chapter-structure"/>):</para>
+ <xref linkend="chapter-structure-section-more-quotations"/>):</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-QpNm">
<title>
<anchor xml:id="c4e7d1"/>
</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
@@ -1646,21 +1646,21 @@
<jbophrase>do'i</jbophrase>, respectively.</para>
</listitem>
</orderedlist>
<para> <indexterm type="general-imported"><primary>scientific names</primary><secondary>rules for</secondary></indexterm> <indexterm type="general-imported"><primary>Linnaean names</primary><secondary>rules for</secondary></indexterm> There are some additional rules for Lojbanizing the scientific names (technically known as
<quote>Linnaean binomials</quote> after their inventor) which are internationally applied to each species of animal or plant. Where precision is essential, these names need not be Lojbanized, but can be directly inserted into Lojban text using the cmavo
<jbophrase>la'o</jbophrase>, explained in
- <xref linkend="chapter-structure"/>. Using this cmavo makes the already lengthy Latinized names at least four syllables longer, however, and leaves the pronunciation in doubt. The following suggestions, though incomplete, will assist in converting Linnaean binomals to valid Lojban names. They can also help to create fu'ivla based on Linnaean binomials or other words of the international scientific vocabulary. The term
+ <xref linkend="chapter-structure-section-more-quotations"/>. Using this cmavo makes the already lengthy Latinized names at least four syllables longer, however, and leaves the pronunciation in doubt. The following suggestions, though incomplete, will assist in converting Linnaean binomals to valid Lojban names. They can also help to create fu'ivla based on Linnaean binomials or other words of the international scientific vocabulary. The term
<quote>back vowel</quote> in the following list refers to any of the letters
<jbophrase role="letteral">a</jbophrase>,
<jbophrase role="letteral">o</jbophrase>, or
<jbophrase role="letteral">u</jbophrase>; the term
<quote>front vowel</quote> correspondingly refers to any of the letters
<jbophrase role="letteral">e</jbophrase>,
<jbophrase role="letteral">i</jbophrase>, or
@@ -1915,40 +1915,40 @@
<para> <indexterm type="general-imported"><primary>pause</primary><secondary>and final-syllable stress</secondary></indexterm> <indexterm type="general-imported"><primary>final syllable stress</primary><secondary>rules for pause after</secondary></indexterm> <indexterm type="general-imported"><primary>stress</primary><secondary>final syllable</secondary><tertiary>rules for pause after</tertiary></indexterm> If the last syllable of a word bears the stress, and a brivla follows, the two must be separated by a pause, to prevent confusion with the primary stress of the brivla. In this case, the first word must be either a cmavo or a cmene with unusual stress (which already ends with a pause, of course).</para>
</listitem>
<listitem>
<para> <indexterm type="general-imported"><primary>pause</primary><secondary>and Cy-form cmavo</secondary></indexterm> <indexterm type="general-imported"><primary>cmavo</primary><secondary>rules for pause after Cy-form</secondary></indexterm> <indexterm type="general-imported"><primary>Cy-form cmavo</primary><secondary>rules for pause after</secondary></indexterm> A cmavo of the form
<quote>Cy</quote> must be followed by a pause unless another
<quote>Cy</quote>-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>
+ <xref linkend="chapter-structure-section-more-quotations"/>.)</para>
</listitem>
</orderedlist>
</section>
<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="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="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="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
<jbophrase>za'e</jbophrase> (explained in
- <xref linkend="chapter-structure"/>) before a newly coined lujvo to indicate that it may have a non-dictionary meaning.</para>
+ <xref linkend="chapter-structure-section-bahe"/>) 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>
<para>Therefore, given a complicated tanru with grouping markers, abstraction markers, and other cmavo in it to make it syntactically unambiguous, the psychological basis of Zipf's Law may compel the lujvo-maker to drop some of the cmavo to make a shorter (technically incorrect) tanru, and then use that tanru to make the lujvo.</para>
<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>
diff --git a/todocbook/5.xml b/todocbook/5.xml
index 2c03987..d19c8ea 100644
--- a/todocbook/5.xml
+++ b/todocbook/5.xml
@@ -774,21 +774,21 @@
<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 xml:id="example-random-id-2cjH">
<title>
<anchor xml:id="c5e6d12"/>
</title>
<para>That is a school for beautiful things and also for girls.</para>
</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>
+ <xref linkend="chapter-connectives-section-tanru"/> 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>
<gloss>the runner(s) is/are winner(s) or loser(s).</gloss>
</interlinear-gloss>
@@ -958,21 +958,21 @@
</example>
<para>leaves
<jbophrase>mlatu</jbophrase> outside the
<jbophrase>gu'e ... gi</jbophrase> construction. The scope of the
<jbophrase>gi</jbophrase> arm extends only to a single brivla or to two or more brivla connected with
<jbophrase>bo</jbophrase> or
<jbophrase>ke ... ke'e</jbophrase>.</para>
</section>
<section xml:id="section-be-sumti">
- <title>Linked sumti: <jbophrase glossary="false">be–bei–be'o</jbophrase></title>
+ <title>Linked sumti: <jbophrase glossary="false">be-bei-be'o</jbophrase></title>
<para>The following cmavo are discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>be</cmavo>
<selmaho>BE</selmaho>
<description>linked sumti marker</description>
</cmavo-entry>
<cmavo-entry>
<cmavo>bei</cmavo>
@@ -982,21 +982,21 @@
</cmavo-entry>
<cmavo-entry>
<cmavo>be'o</cmavo>
<selmaho>BEhO</selmaho>
<description>linked sumti terminator</description>
</cmavo-entry>
</cmavo-list>
<para>The question of the place structures of selbri has been glossed over so far. This chapter does not attempt to treat place structure issues in detail; they are discussed in
<xref linkend="chapter-sumti-tcita"/>. One grammatical structure related to places belongs here, however. In simple sentences such as
- <xref linkend="example-do-mamta-mi"/>, the place structure of the selbri is simply the defined place structure of the gismu
+ <xref linkend="example-do-mamta-mi"/>, the place structure of the selbri is simply the defined place structure of the gismu
<jbophrase>mamta</jbophrase>. What about more complex selbri?</para>
<para> <indexterm type="general-imported"><primary>tanru</primary><secondary>place structures of</secondary></indexterm> For tanru, the place structure rule is simple: the place structure of a tanru is always the place structure of its tertau. Thus, the place structure of
<jbophrase>blanu zdani</jbophrase> is that of
<jbophrase>zdani</jbophrase>: the x1 place is a house or nest, and the x2 place is its occupants.</para>
<para>What about the places of
<jbophrase>blanu</jbophrase>? Is there any way to get them into the act? In fact,
<jbophrase>blanu</jbophrase> has only one place, and this is merged, as it were, with the x1 place of
<jbophrase>zdani</jbophrase>. It is whatever is in the x1 place that is being characterized as blue-for-a-house. But if we replace
<jbophrase>blanu</jbophrase> with
<jbophrase>xamgu</jbophrase>, we get:</para>
@@ -1031,20 +1031,21 @@
<jbophrase>be</jbophrase> (of selma'o BE), which signals that one or more sumti follows. These sumti are not part of the overall bridi place structure, but fill the places of the brivla they are attached to, starting with x2. If there is more than one sumti, they are separated by the cmavo
<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>
+ <!-- these sentences should be broken up to make them easier to read, or at least less intimidating -->
<interlinear-gloss>
<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
@@ -1082,21 +1083,21 @@
</example>
<para>is simply that of
<jbophrase>ckule</jbophrase>. (The sole exception to this rule is discussed in
<xref linkend="section-co-inversion"/>.)</para>
<para> <indexterm type="lojban-word-imported"><primary>FA selma'o</primary></indexterm> <indexterm type="general-imported"><primary>FA tags and linked sumti</primary></indexterm> <indexterm type="general-imported"><primary>linked sumti and FA tags</primary></indexterm> It is possible to precede linked sumti by the place structure ordering tags
<jbophrase>fe</jbophrase>,
<jbophrase>fi</jbophrase>,
<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
+ <xref linkend="chapter-sumti-tcita-section-FA"/>), 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>
<gloss>This is-a-good ( by-standard me for you ) house.</gloss>
</interlinear-gloss>
</example>
@@ -1522,21 +1523,21 @@
</title>
<interlinear-gloss>
<jbo>mi jimpe tu'a loi nu'a su'i nabmi</jbo>
<gloss>I understand something-about the-mass-of is-the-sum-of problems.</gloss>
<en>I understand addition problems.</en>
</interlinear-gloss>
</example>
<para> <indexterm type="lojban-word-imported"><primary>MOI selma'o</primary></indexterm> More usefully, it is possible to combine a mathematical expression with a cmavo of selma'o MOI to create one of various numerical selbri. Details are available in
- <xref linkend="chapter-mekso"/>. Here are a few tanru:</para>
+ <xref linkend="chapter-mekso-section-mekso-selbri"/>. Here are a few tanru:</para>
<example xml:id="example-random-id-qjWh" role="interlinear-gloss-example">
<title>
<anchor xml:id="c5e9d6"/>
</title>
<interlinear-gloss>
<jbo>la prim. palvr. pamoi cusku</jbo>
<gloss>Preem Palver is-the-1-th speaker.</gloss>
<en>Preem Palver is the first speaker.</en>
@@ -1687,25 +1688,25 @@
<en>That is a Chrysler car.</en>
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>logical connectives</primary><secondary>relative precedence with me'u</secondary></indexterm> <indexterm type="general-imported"><primary>me'u</primary><secondary>relative precedence with logical connectives</secondary></indexterm> <indexterm type="general-imported"><primary>elidability of me'u</primary></indexterm> The elidable terminator
<jbophrase>me'u</jbophrase> can usually be omitted. It is absolutely required only if the
<jbophrase>me</jbophrase> selbri is being used in an indefinite description (a type of sumti explained in
- <xref linkend="chapter-sumti"/>), and if the indefinite description is followed by a relative clause (explained in
+ <xref linkend="chapter-sumti-section-indefinite-descriptions"/>), and if the indefinite description is followed by a relative clause (explained in
<xref linkend="chapter-relative-clauses"/>) or a sumti logical connective (explained in
- <xref linkend="chapter-connectives"/>). Without a
+ <xref linkend="chapter-connectives-section-sumti-connection"/>). Without a
<jbophrase>me'u</jbophrase>, the relative clause or logical connective would appear to belong to the sumti embedded in the
<jbophrase>me</jbophrase> expression. Here is a contrasting pair of sentences:</para>
<example xml:id="example-random-id-qJyi" role="interlinear-gloss-example">
<title>
<anchor xml:id="c5e10d8"/>
</title>
<interlinear-gloss>
<jbo>re me le ci nolraitru .e la djan. [me'u] cu blabi</jbo>
<en>Two of the group
<quote>the three kings and John</quote> are white.</en>
@@ -1779,21 +1780,21 @@
<title>
<anchor xml:id="c5e11d2"/>
</title>
<interlinear-gloss>
<jbo>do se prami mi</jbo>
<gloss>You [swap x1 and x2] love me.</gloss>
<en>You are loved by me.</en>
</interlinear-gloss>
</example>
<para>Conversion is fully explained in
- <xref linkend="chapter-sumti-tcita"/>. For the purposes of this chapter, the important point about conversion is that it applies only to the following simple selbri. When trying to convert a tanru, therefore, it is necessary to be careful! Consider
+ <xref linkend="chapter-sumti-tcita-section-SE"/>. For the purposes of this chapter, the important point about conversion is that it applies only to the following simple selbri. When trying to convert a tanru, therefore, it is necessary to be careful! Consider
<xref linkend="example-random-id-mPX8"/>:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-mPX8">
<title>
<indexterm type="example-imported"><primary>walk to market</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c5e11d3"/>
</title>
<interlinear-gloss>
<jbo>la .alis. cu cadzu klama le zarci</jbo>
<gloss>Alice is-a-walker type-of goer to-the market.</gloss>
<gloss>Alice walkingly goes to the market.</gloss>
@@ -1847,21 +1848,21 @@
<anchor xml:id="c5e11d7"/>
</title>
<interlinear-gloss>
<jbo>la djan. cu cadzu se klama la .alis</jbo>
<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>
+ <xref linkend="chapter-sumti-tcita-section-jai"/>.</para>
</section>
<section xml:id="section-scalar-negation">
<title>Scalar negation of selbri</title>
<para> <indexterm type="lojban-word-imported"><primary>NAhE selma'o</primary></indexterm> <indexterm type="general-imported"><primary>selbri</primary><secondary>scalar negation of</secondary></indexterm> <indexterm type="general-imported"><primary>scalar negation</primary><secondary>effect on selbri</secondary></indexterm> Negation is too large and complex a topic to explain fully in this chapter; see
<xref linkend="chapter-negation"/>. In brief, there are two main types of negation in Lojban. This section is concerned with so-called
<quote>scalar negation</quote>, which is used to state that a true relation between the sumti is something other than what the selbri specifies. Scalar negation is expressed by cmavo of selma'o NAhE:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-4oxH">
<title>
<anchor xml:id="c5e12d1"/>
diff --git a/todocbook/6.xml b/todocbook/6.xml
index 1a3460c..caef939 100644
--- a/todocbook/6.xml
+++ b/todocbook/6.xml
@@ -326,26 +326,26 @@
<en>Some human beings wrote the story.</en>
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>lo</primary><secondary>contrasted with le in implications</secondary></indexterm> <indexterm type="general-imported"><primary>le</primary><secondary>contrasted with lo in implications</secondary></indexterm>
<xref linkend="example-random-id-qKw7"/> says who the author of the story is: one or more particular human beings that the speaker has in mind. If the topic of conversation is the story, then
<xref linkend="example-random-id-qKw7"/> identifies the author as someone who can be pointed out or who has been previously mentioned; whereas if the topic is a person, then
<jbophrase>le remna</jbophrase> is in effect a shorthand reference to that person.
<xref linkend="example-random-id-qKYf"/> merely says that the author is human.</para>
<para><indexterm type="general-imported"><primary>ku</primary><secondary>uses of</secondary></indexterm> <indexterm type="general-imported"><primary>cu</primary><secondary>effect on elidability of ku</secondary></indexterm> <indexterm type="general-imported"><primary>ku</primary><secondary>effect of following selbri on elidability of</secondary></indexterm> <indexterm type="general-imported"><primary>ku</primary><secondary>as elidable terminator for descriptions</secondary></indexterm> The elidable terminator for all descriptions is
<jbophrase>ku</jbophrase>. It can almost always be omitted with no danger of ambiguity. The main exceptions are in certain uses of relative clauses, which are discussed in
- <xref linkend="chapter-relative-clauses"/>, and in the case of a description immediately preceding the selbri. In this latter case, using an explicit
+ <xref linkend="chapter-relative-clauses-section-descriptors"/>, and in the case of a description immediately preceding the selbri. In this latter case, using an explicit
<jbophrase>cu</jbophrase> before the selbri makes the
<jbophrase>ku</jbophrase> unnecessary. There are also a few other uses of
<jbophrase>ku</jbophrase>: in the compound negator
<jbophrase>naku</jbophrase> (discussed in
- <xref linkend="chapter-negation"/>) and to terminate place-structure, tense, and modal tags that do not have associated sumti (discussed in
+ <xref linkend="chapter-quantifiers"/>) and to terminate place-structure, tense, and modal tags that do not have associated sumti (discussed in
<xref linkend="chapter-sumti-tcita"/> and
<xref linkend="chapter-tenses"/>).</para>
</section>
<section xml:id="section-masses">
<title>Individuals and masses</title>
<para>The following cmavo are discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>lei</cmavo>
<selmaho>LE</selmaho>
@@ -1356,21 +1356,21 @@
</title>
<interlinear-gloss>
<jbo>mi pu cusku le sinxa be le vi cukta</jbo>
<gloss>I [past] express the symbol-for the nearby book.</gloss>
</interlinear-gloss>
</example>
<para>which is equivalent to
<xref linkend="example-random-id-7ytm"/>, but longer.</para>
<para><indexterm type="general-imported"><primary>sequence</primary><secondary>contrasted with set</secondary></indexterm> <indexterm type="general-imported"><primary>vu'i</primary><secondary>use for creating sequence</secondary></indexterm> <indexterm type="general-imported"><primary>tu'a</primary><secondary>use for forming abstractions</secondary></indexterm> <indexterm type="general-imported"><primary>vu'i</primary><secondary>effect of on meaning</secondary></indexterm> <indexterm type="general-imported"><primary>lu'o</primary><secondary>effect of on meaning</secondary></indexterm> <indexterm type="general-imported"><primary>lu'i</primary><secondary>effect of on meaning</secondary></indexterm> <indexterm type="general-imported"><primary>lu'a</primary><secondary>effect of on meaning</secondary></indexterm> <indexterm type="general-imported"><primary>tu'a</primary><secondary>effect of on meaning</secondary></indexterm> The other sumti qualifiers follow the same rules. The cmavo
<jbophrase>tu'a</jbophrase> is used in forming abstractions, and is explained more fully in
- <xref linkend="chapter-abstractions"/>. The triplet
+ <xref linkend="chapter-abstractions-section-events-and-contours"/>. The triplet
<jbophrase>lu'a</jbophrase>,
<jbophrase>lu'i</jbophrase>, and
<jbophrase>lu'o</jbophrase> convert between individuals, sets, and masses;
<jbophrase>vu'i</jbophrase> belongs to this group as well, but creates a sequence, which is similar to a set but has a definite order. (The set of John and Charles is the same as the set of Charles and John, but the sequences are different.) Here are some examples:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-ioCu">
<title>
@@ -1380,21 +1380,21 @@
<jbo>mi troci tu'a le vorme</jbo>
<gloss>I try some-abstraction-about the door.</gloss>
<en>I try (to open) the door.</en>
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>tu'a</primary><secondary>as being deliberately vague</secondary></indexterm>
<xref linkend="example-random-id-ioCu"/> might mean that I try to do something else involving the door; the form is deliberately vague.</para>
<para>Most of the following examples make use of the cmavo
<jbophrase>ri</jbophrase>, belonging to selma'o KOhA. This cmavo means
<quote>the thing last mentioned</quote>; it is equivalent to repeating the immediately previous sumti (but in its original context). It is explained in more detail in
- <xref linkend="chapter-anaphoric-cmavo"/>.</para>
+ <xref linkend="chapter-anaphoric-cmavo-section-ri-gohi-series"/>.</para>
<example xml:id="example-random-id-qLbv" role="interlinear-gloss-example">
<title> <!-- FIXME: this indexterm matches three examples -->
<indexterm type="example-imported"><primary>set of rats</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c6e10d7"/>
</title>
<interlinear-gloss>
<jbo>lo'i ratcu cu barda .iku'i lu'a ri cmalu</jbo>
<gloss>The-set-of rats is-large. But some-members-of it-last-mentioned is-small.</gloss>
<en>The set of rats is large, but some of its members are small.</en>
@@ -1455,32 +1455,32 @@
</interlinear-gloss>
</example>
<para>(In
<xref linkend="example-random-id-JwCb"/>, the sumti
<jbophrase>ra</jbophrase> refers to some previously mentioned sumti other than that referred to by
<jbophrase>ri</jbophrase>. We cannot use
<jbophrase>ri</jbophrase> here, because it would signify
<jbophrase>la djein.</jbophrase>, that being the most recent sumti available to
<jbophrase>ri</jbophrase>. See more detailed explanations in
- <xref linkend="chapter-anaphoric-cmavo"/>.)</para>
+ <xref linkend="chapter-anaphoric-cmavo-section-ri-gohi-series"/>.)</para>
</section>
<section xml:id="section-vocatives">
<title>The syntax of vocative phrases</title>
<para> <indexterm type="general-imported"><primary>vocative phrases</primary><secondary>as a <quote>free modifier</quote></secondary></indexterm> Vocative phrases are not sumti, but are explained in this chapter because their syntax is very similar to that of sumti. Grammatically, a vocative phrase is one of the so-called
<quote>free modifiers</quote> of Lojban, along with subscripts, parentheses, and various other constructs explained in
<xref linkend="chapter-structure"/>. They can be placed after many, but not all, constructions of the grammar: in general, after any elidable terminator (which, however, must not then be elided!), at the beginnings and ends of sentences, and in many other places.</para>
<para> <indexterm type="lojban-word-imported"><primary>DOI selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>COI selma'o</primary></indexterm> <indexterm type="general-imported"><primary>vocative phrase</primary><secondary>purpose of</secondary></indexterm> The purpose of a vocative phrase is to indicate who is being addressed, or to indicate to that person that he or she ought to be listening. A vocative phrase begins with a cmavo of selma'o COI or DOI, all of which are explained in more detail in
- <xref linkend="chapter-attitudinals"/>. Sometimes that is all there is to the phrase:</para>
+ <xref linkend="chapter-attitudinals-section-vocatives"/>. Sometimes that is all there is to the phrase:</para>
<example xml:id="example-random-id-qLE3" role="interlinear-gloss-example">
<title>
<anchor xml:id="c6e11d1"/>
</title>
<interlinear-gloss>
<jbo>coi</jbo>
<gloss>[greetings]</gloss>
<en>Hello.</en>
</interlinear-gloss>
</example>
@@ -1574,25 +1574,23 @@
<anchor xml:id="c6e11d9"/>
</title>
<interlinear-gloss>
<jbo>doi la djan.</jbo>
<gloss>The-one-named John!</gloss>
</interlinear-gloss>
</example>
<para> <indexterm type="lojban-word-imported"><primary>DOhU selma'o</primary></indexterm> <indexterm type="general-imported"><primary>vocative phrase terminator</primary><secondary>elidability of</secondary></indexterm> <indexterm type="general-imported"><primary>vocative phrase</primary><secondary>elidable terminator for</secondary></indexterm> Finally, the elidable terminator for vocative phrases is
<jbophrase>do'u</jbophrase> (of selma'o DOhU), which is rarely needed except when a simple vocative word is being placed somewhere within a bridi. It may also be required when a vocative is placed between a sumti and its relative clause, or when there are a sequence of so-called
- <quote>free modifiers</quote> (vocatives, subscripts, utterance ordinals - see
-
-
- <xref linkend="chapter-mekso"/>- metalinguistic comments - see
- <xref linkend="chapter-structure"/>- or reciprocals - see
+ <quote>free modifiers</quote> (vocatives, subscripts, utterance ordinals – see
+ <xref linkend="chapter-mekso"/> – metalinguistic comments – see
+ <xref linkend="chapter-structure-section-parentheses"/> – or reciprocals – see
<xref linkend="chapter-structure"/>) which must be properly separated.</para>
<para> <indexterm type="general-imported"><primary>vocative phrase</primary><secondary>effect of position on meaning</secondary></indexterm> The meaning of a vocative phrase that is within a sentence is not affected by its position in the sentence: thus
<xref linkend="example-random-id-bx2C"/> and
<xref linkend="example-random-id-qLFi"/> mean the same thing:</para>
<example xml:id="example-random-id-qLFi" role="interlinear-gloss-example">
<title>
<anchor xml:id="c6e11d10"/>
</title>
<interlinear-gloss>
@@ -1714,21 +1712,21 @@
<jbo>doi djan. pol. djonz. le bloti cu klama fi la niuport. niuz.</jbo>
<en>John Paul Jones, the boat comes (to somewhere) from Newport News.</en>
</interlinear-gloss>
</example>
<para><indexterm type="general-imported"><primary>name-words</primary><secondary>permissible consonant combinations</secondary></indexterm> A name may not contain any consonant combination that is illegal in Lojban words generally: the
<quote>impermissible consonant clusters</quote> of Lojban morphology (explained in
- <xref linkend="chapter-phonology"/>). Thus
+ <xref linkend="chapter-phonology-section-clusters"/>). Thus
<jbophrase valid="false">djeimz.</jbophrase> is not a valid version of
<quote>James</quote> (because
<jbophrase role="morphology" valid="false">mz</jbophrase> is invalid):
<jbophrase>djeimyz</jbophrase> will suffice. Similarly,
<jbophrase>la</jbophrase> may be replaced by
<jbophrase>ly</jbophrase>,
<jbophrase>lai</jbophrase> by
<jbophrase>ly'i</jbophrase>,
<jbophrase>doi</jbophrase> by
<jbophrase>do'i</jbophrase> or
diff --git a/todocbook/7.xml b/todocbook/7.xml
index d99de1a..b197d62 100644
--- a/todocbook/7.xml
+++ b/todocbook/7.xml
@@ -102,21 +102,21 @@
<para><!-- FIXME: this indexterm applies to a <cmavo>'d (not <jbophrase>'d) word --><indexterm type="lojban-word-imported"><primary>do</primary></indexterm><!-- FIXME: this indexterm applies to a <cmavo>'d (not <jbophrase>'d) word --> <indexterm type="lojban-word-imported"><primary>mi</primary></indexterm> <!-- FIXME: this indexterm has nowhere to go --><indexterm type="example-imported"><primary>foreman of a jury</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>personal pronouns</primary><secondary>with mi-series for I/you</secondary></indexterm> <indexterm type="general-imported"><primary>pro-sumti</primary><secondary>for listener(s)</secondary></indexterm> <indexterm type="general-imported"><primary>pro-sumti</primary><secondary>for speaker(s)</secondary></indexterm> <indexterm type="general-imported"><primary>pro-sumti</primary><secondary>mi-series</secondary></indexterm> <indexterm type="general-imported"><primary>mi-series</primary><secondary>of pro-sumti</secondary></indexterm> The mi-series of pro-sumti refer to the speaker, the listener, and others in various combinations.
<jbophrase>mi</jbophrase> refers to the speaker and perhaps others for whom the speaker speaks; it may be a Lojbanic mass.
<jbophrase>do</jbophrase> refers to the listener or listeners. Neither
<jbophrase>mi</jbophrase> nor
<jbophrase>do</jbophrase> is specific about the number of persons referred to; for example, the foreman of a jury may refer to the members of the jury as
<jbophrase>mi</jbophrase>, since in speaking officially he represents all of them.</para>
<para> <indexterm type="lojban-word-imported"><primary>COI selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>mi'e</primary></indexterm> <indexterm type="general-imported"><primary>COI selma'o</primary><secondary>effect on referent of "do"<!-- FIXME: what should these "s become? --></secondary></indexterm> <indexterm type="general-imported"><primary>COI selma'o</primary><secondary>effect on referent of "mi"</secondary></indexterm> The referents of
<jbophrase>mi</jbophrase> and
<jbophrase>do</jbophrase> are usually obvious from the context, but may be assigned by the vocative words of selma'o COI, explained in
- <xref linkend="chapter-attitudinals"/>. The vocative
+ <xref linkend="chapter-attitudinals-section-vocatives"/>. The vocative
<jbophrase>mi'e</jbophrase> assigns
<jbophrase>mi</jbophrase>, whereas all of the other vocatives assign
<jbophrase>do</jbophrase>.</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-4dna">
<title>
<anchor xml:id="c7e2d1"/>
</title>
<interlinear-gloss>
<jbo>mi'e djan. doi frank. mi cusku lu mi bajra li'u do</jbo>
<gloss>I-am John, O Frank, I express [quote] I run [unquote] to-you</gloss>
@@ -296,35 +296,35 @@
<jbo>le ti bloti</jbo>
<gloss>the this boat</gloss>
</interlinear-gloss>
</example>
<para><indexterm type="general-imported"><primary>this</primary><secondary>adjective expression with vi</secondary></indexterm> <indexterm type="general-imported"><primary>vi</primary><secondary>as adjective expression for English this</secondary></indexterm> does not mean
<quote>this boat</quote> but rather
<quote>this one's boat</quote>,
<quote>the boat associated with this thing</quote>, as explained in
- <xref linkend="chapter-relative-clauses"/>. A correct Lojban translation of
+ <xref linkend="chapter-relative-clauses-section-possessive-sumti"/>. A correct Lojban translation of
<xref linkend="example-random-id-IWi7"/> is</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-rfUc">
<title>
<anchor xml:id="c7e3d2"/>
</title>
<interlinear-gloss>
<jbo>le vi bloti</jbo>
<gloss>the here boat</gloss>
<en>the nearby boat</en>
</interlinear-gloss>
</example>
<para>using a spatial tense before the selbri
<jbophrase>bloti</jbophrase> to express that the boat is near the speaker. (Tenses are explained in full in
- <xref linkend="chapter-abstractions"/>.) Another correct translation would be:</para>
+ <xref linkend="chapter-tenses"/>.) Another correct translation would be:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-pRLq">
<title>
<anchor xml:id="c7e3d3"/>
</title>
<interlinear-gloss>
<jbo>ti noi bloti</jbo>
<gloss>this-thing which-incidentally is-a-boat</gloss>
</interlinear-gloss>
</example>
@@ -476,21 +476,21 @@
</interlinear-gloss>
</example>
<para>The cmavo of the di'u-series have a meaning that is relative to the context. The referent of
<jbophrase>dei</jbophrase> in the current utterance is the same as the referent of
<jbophrase>di'u</jbophrase> in the next utterance. The term
<quote>utterance</quote> is used rather than
<quote>sentence</quote> because the amount of speech or written text referred to by any of these words is vague. Often, a single bridi is intended, but longer utterances may be thus referred to.</para>
<para> <indexterm type="lojban-word-imported"><primary>la'edi'u</primary></indexterm> <indexterm type="lojban-word-imported"><primary>LAhE selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>la'e</primary></indexterm> Note one very common construction with
<jbophrase>di'u</jbophrase> and the cmavo
<jbophrase>la'e</jbophrase> (of selma'o LAhE; see
- <xref linkend="chapter-sumti"/>) which precedes a sumti and means
+ <xref linkend="chapter-sumti-section-sumti-qualifiers"/>) which precedes a sumti and means
<quote>the thing referred to by (the sumti)</quote>:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-MsUd">
<title>
<anchor xml:id="c7e4d6"/>
</title>
<interlinear-gloss>
<jbo>mi prami la djein. .i mi nelci la'e di'u</jbo>
<gloss>I love Jane. And I like the-referent-of the-last-utterance.</gloss>
<en>I love Jane, and I like that.</en>
</interlinear-gloss>
@@ -678,21 +678,21 @@
<anchor xml:id="c7e5d3"/>
</title>
<interlinear-gloss>
<jbo>la .alis. klama le zarci .i la .alis. goi ko'a cu blanu</jbo>
<gloss>Alice goes-to the store. Alice, also-known-as it-1, is-blue.</gloss>
</interlinear-gloss>
</example>
<para> <indexterm type="lojban-word-imported"><primary>ge'u</primary></indexterm> in other words,
<jbophrase>goi</jbophrase> is symmetrical. There is a terminator,
<jbophrase>ge'u</jbophrase> (of selma'o GEhU), which is almost always elidable. The details are in
- <xref linkend="chapter-relative-clauses"/>.</para>
+ <xref linkend="chapter-relative-clauses-section-relative-phrases"/>.</para>
<para> <indexterm type="general-imported"><primary>goi assignment of ko'a-series pro-sumti</primary><secondary>use in speech contrasted with writing</secondary></indexterm> The afterthought form of
<jbophrase>goi</jbophrase> shown in
<xref linkend="example-random-id-duGR"/> and
<xref linkend="example-random-id-oKaM"/> is probably most common in speech, where we do not know until part way through our utterance that we will want to refer to Alice again. In writing, though,
<jbophrase>ko'a</jbophrase> may be assigned at the point where Alice is first mentioned. An example of this forethought form of
<jbophrase>goi</jbophrase> is:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-1FJV">
<title>
<anchor xml:id="c7e5d4"/>
</title>
@@ -755,21 +755,21 @@
<title>
<anchor xml:id="c7e5d7"/>
</title>
<interlinear-gloss>
<jbo>broda ke brode brodi</jbo>
<gloss>a thing-1 type of (thing-2 type-of thing-3)</gloss>
</interlinear-gloss>
</example>
<para>represents an abstract pattern, a certain kind of tanru. (Historically, this use was the original one.)</para>
<para> <indexterm type="general-imported"><primary>lerfu as pro-sumti</primary><secondary>implicit assignment of antecedent</secondary></indexterm> <indexterm type="general-imported"><primary>ko'a-series pro-sumti</primary><secondary>contrasted with lerfu as pro-sumti in explicit assignment of</secondary></indexterm> <indexterm type="general-imported"><primary>lerfu as pro-sumti</primary><secondary>contrasted with ko'a-series in explicit assignment of</secondary></indexterm> <indexterm type="general-imported"><primary>pro-sumti</primary><secondary>lerfu as</secondary></indexterm> <indexterm type="general-imported"><primary>lerfu</primary><secondary>as assignable pro-sumti</secondary></indexterm> As is explained in
- <xref linkend="chapter-letterals"/>, the words for Lojban letters, belonging to selma'o BY and certain related selma'o, are also usable as assignable pro-sumti. The main difference between letter pro-sumti and ko'a-series pro-sumti is that, in the absence of an explicit assignment, letters are taken to refer to the most recent name or description sumti beginning with the same letter:</para>
+ <xref linkend="chapter-letterals-section-lerfu-pro-sumti"/>, the words for Lojban letters, belonging to selma'o BY and certain related selma'o, are also usable as assignable pro-sumti. The main difference between letter pro-sumti and ko'a-series pro-sumti is that, in the absence of an explicit assignment, letters are taken to refer to the most recent name or description sumti beginning with the same letter:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-x1gh">
<title>
<anchor xml:id="c7e5d8"/>
</title>
<interlinear-gloss>
@@ -957,21 +957,21 @@
<gloss>John sees the tree. [repeat last] is-adorned-by the of-[repeat last] branch.</gloss>
<en>John sees the tree. It is adorned by its branches.</en>
</interlinear-gloss>
</example>
<para>Here the second
<jbophrase>ri</jbophrase> has as antecedent the first
<jbophrase>ri</jbophrase>, which has as antecedent
<jbophrase>le tricu</jbophrase>. All three refer to the same thing: a tree.</para>
<para>To refer to the next-to-last sumti, the third-from-last sumti, and so on,
<jbophrase>ri</jbophrase> may be subscripted (subscripts are explained in
- <xref linkend="chapter-structure"/>):</para>
+ <xref linkend="chapter-structure-section-subscripts"/>):</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-Lc2y">
<title>
<anchor xml:id="c7e6d5"/>
</title>
<interlinear-gloss>
<jbo>lo smuci .i lo forca .i la rik. pilno rixire .i la .alis. pilno riximu</jbo>
<gloss>A spoon. A fork. Rick uses [repeat next-to-last]. Alice uses [repeat fifth-from-last].</gloss>
</interlinear-gloss>
</example>
<para>Here
@@ -1087,39 +1087,39 @@
<title>
<anchor xml:id="c7e6d10"/>
</title>
<interlinear-gloss>
<jbo>A: mi ba klama le zarci B: mi nelci le si'o mi go'i A: do go'e</jbo>
<gloss>A: I [future] go-to the store. B: I like the concept-of I [repeat last bridi]. A: You [repeat last bridi but one].</gloss>
<en>A: I am going to the store. B: I like the idea of my going. A: You'll go, too.</en>
</interlinear-gloss>
</example>
- <para>Here B's sentence repeats A's within an abstraction (explained in Chapter 11):
+ <para>Here B's sentence repeats A's within an abstraction (explained in <xref linkend="chapter-abstractions-"/>):
<jbophrase>le si'o mi go'i</jbophrase> means
<jbophrase>le si'o mi klama le zarci</jbophrase>. Why must B use the word
<jbophrase>mi</jbophrase> explicitly to replace the x1 of
<jbophrase>mi klama le zarci</jbophrase>, even though it looks like
<jbophrase>mi</jbophrase> is replacing
<jbophrase>mi</jbophrase>? Because B's
<jbophrase>mi</jbophrase> refers to B, whereas A's
<jbophrase>mi</jbophrase> refers to A. If B said:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-2uS7">
<title>
<anchor xml:id="c7e6d11"/>
</title>
<interlinear-gloss>
<jbo>mi nelci le si'o go'i</jbo>
</interlinear-gloss>
</example>
<para>that would mean:</para>
- <place-structure> I like the idea of your going to the store. </place-structure> <!-- not actually a place structure, but needs to be set out from text... egh... -->
+ <place-structure> I like the idea of your going to the store. </place-structure> <!-- not actually a place structure, but should be set out from the text -->
<para>The repetition signalled by
<jbophrase>go'i</jbophrase> is not literally of words, but of concepts. Finally, A repeats her own sentence, but with the x1 changed to
<jbophrase>do</jbophrase>, meaning B. Note that in
<xref linkend="example-random-id-9hf5"/>, the tense
<jbophrase>ba</jbophrase> (future time) is carried along by both
<jbophrase>go'i</jbophrase> and
<jbophrase>go'e</jbophrase>.</para>
<para>Descriptions based on go'i-series cmavo can be very useful for repeating specific sumti of previous bridi:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-hwau">
@@ -1422,21 +1422,21 @@
</interlinear-gloss>
</example>
<para>The English version means, and the Lojban version probably means, that I try to open the door, but the relationship of opening is not actually specified; the Lojbanic listener must guess it from context. Lojban, unlike English, makes it clear that there is an implicit action that is not being expressed.</para>
<para> <indexterm type="general-imported"><primary>co'e</primary><secondary>rationale for word form</secondary></indexterm> The form of
<jbophrase>co'e</jbophrase> was chosen to resemble
<jbophrase>zo'e</jbophrase>; the cmavo
<jbophrase>do'e</jbophrase> of selma'o BAI (see
- <xref linkend="chapter-sumti-tcita"/>) also belongs to the same group of cmavo.</para>
+ <xref linkend="chapter-sumti-tcita-section-BAI"/>) also belongs to the same group of cmavo.</para>
<para> <indexterm type="general-imported"><primary>zo'e-series</primary><secondary>compared with do'i as indefinite pro-sumti</secondary></indexterm> <indexterm type="general-imported"><primary>do'i</primary><secondary>compared with zo'e-series as indefinite pro-sumti</secondary></indexterm> Note that
<jbophrase>do'i</jbophrase>, of the di'u-series, is also a kind of indefinite pro-sumti: it is indefinite in referent, but is restricted to referring only to an utterance.</para>
</section>
<section xml:id="section-voha-series">
<title>Reflexive and reciprocal pro-sumti: the vo'a-series</title>
<para>The following cmavo are discussed in this section:</para>
<cmavo-list>
@@ -1588,21 +1588,21 @@
<selmaho>KOhA</selmaho>
<description>sumti question</description>
</cmavo-entry>
<cmavo-entry>
<cmavo>mo</cmavo>
<selmaho>GOhA</selmaho>
<description>bridi question</description>
</cmavo-entry>
</cmavo-list>
<para> <indexterm type="lojban-word-imported"><primary>ma</primary></indexterm> <indexterm type="general-imported"><primary>questions</primary><secondary>sumti</secondary></indexterm> <indexterm type="general-imported"><primary>ma</primary><secondary>as sumti question</secondary></indexterm> Lojban questions are more fully explained in
- <xref linkend="chapter-structure"/>, but
+ <xref linkend="chapter-structure-section-questions"/>, but
<jbophrase>ma</jbophrase> and
<jbophrase>mo</jbophrase> are listed in this chapter for completeness. The cmavo
<jbophrase>ma</jbophrase> asks for a sumti to make the bridi true:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-Csod">
<title>
<anchor xml:id="c7e9d1"/>
</title>
<interlinear-gloss>
<jbo>do klama ma</jbo>
<gloss>You go to-what-destination?</gloss>
@@ -1720,21 +1720,21 @@
<jbophrase>ri</jbophrase> cannot be used in place of
<jbophrase>ke'a</jbophrase> in
<xref linkend="example-random-id-UNBb"/> and
<xref linkend="example-random-id-0EWp"/>, because the relativized sumti is not yet complete when the
<jbophrase>ke'a</jbophrase> appears.</para>
<para> <indexterm type="general-imported"><primary>subscripts</primary><secondary>on ke'a for nested relative clauses</secondary></indexterm> <indexterm type="general-imported"><primary>ke'a</primary><secondary>subscripting for nested relative clauses</secondary></indexterm> <indexterm type="general-imported"><primary>ke'a</primary><secondary>and abstract descriptions</secondary></indexterm> Note that
<jbophrase>ke'a</jbophrase> is used only with relative clauses, and not with other embedded bridi such as abstract descriptions. In the case of relative clauses within relative clauses,
<jbophrase>ke'a</jbophrase> may be subscripted to make the difference clear (see
- <xref linkend="chapter-relative-clauses"/>).</para>
+ <xref linkend="chapter-relative-clauses-section-nesting"/>).</para>
</section>
<section xml:id="section-cehu">
<title>Abstraction focus pro-sumti:
<jbophrase>ce'u</jbophrase></title>
<para>The following cmavo are discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>ce'u</cmavo>
<selmaho>KOhA</selmaho>
<description>abstraction focus</description>
@@ -1842,37 +1842,37 @@
<selmaho>DAhO</selmaho>
<description>cancel all pro-sumti/pro-bridi</description>
</cmavo-entry>
</cmavo-list>
<para> <indexterm type="general-imported"><primary>pro-bridi assignment</primary><secondary>stability of</secondary></indexterm> <indexterm type="general-imported"><primary>pro-sumti assignment</primary><secondary>stability of</secondary></indexterm> How long does a pro-sumti or pro-bridi remain stable? In other words, once we know the referent of a pro-sumti or pro-bridi, how long can we be sure that future uses of the same cmavo have the same referent? The answer to this question depends on which series the cmavo belongs to.</para>
<para> <indexterm type="lojban-word-imported"><primary>cei</primary></indexterm> <indexterm type="lojban-word-imported"><primary>goi</primary></indexterm> <indexterm type="general-imported"><primary>bound variable pro-sumti</primary><secondary>stability of</secondary></indexterm> <indexterm type="general-imported"><primary>assignable pro-sumti</primary><secondary>explicit cancellation of by rebinding</secondary></indexterm> <indexterm type="general-imported"><primary>assignable pro-sumti</primary><secondary>stability of</secondary></indexterm> <indexterm type="general-imported"><primary>personal pro-sumti</primary><secondary>stability of</secondary></indexterm> <indexterm type="general-imported"><primary>personal pro-sumti</primary><secondary>implicit cancellation of by change of speaker/listener</secondary></indexterm> Personal pro-sumti are stable until there is a change of speaker or listener, possibly signaled by a vocative. Assignable pro-sumti and pro-bridi last indefinitely or until rebound with
<jbophrase>goi</jbophrase> or
<jbophrase>cei</jbophrase>. Bound variable pro-sumti and pro-bridi also generally last until re-bound; details are available in
- <xref linkend="chapter-quantifiers"/>.</para>
+ <xref linkend="chapter-quantifiers-section-notes-on-variables"/>.</para>
<para> <indexterm type="general-imported"><primary>anaphoric pro-bridi</primary><secondary>stability of</secondary></indexterm> <indexterm type="general-imported"><primary>anaphoric pro-sumti</primary><secondary>stability of</secondary></indexterm> <indexterm type="general-imported"><primary>ke'a</primary><secondary>stability of</secondary></indexterm> <indexterm type="general-imported"><primary>reflexive pro-sumti</primary><secondary>stability of</secondary></indexterm> <indexterm type="general-imported"><primary>utterance pro-sumti</primary><secondary>stability of</secondary></indexterm> Utterance pro-sumti are stable only within the utterance in which they appear; similarly, reflexive pro-sumti are stable only within the bridi in which they appear; and
<jbophrase>ke'a</jbophrase> is stable only within its relative clause. Anaphoric pro-sumti and pro-bridi are stable only within narrow limits depending on the rules for the particular cmavo.</para>
<para> <indexterm type="general-imported"><primary>indefinite pro-bridi</primary><secondary>stability of</secondary></indexterm> <indexterm type="general-imported"><primary>indefinite pro-sumti</primary><secondary>stability of</secondary></indexterm> <indexterm type="general-imported"><primary>demonstrative pro-sumti</primary><secondary>stability of</secondary></indexterm> Demonstrative pro-sumti, indefinite pro-sumti and pro-bridi, and sumti and bridi questions potentially change referents every time they are used.</para>
<para> <indexterm type="lojban-word-imported"><primary>DAhO selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>da'o</primary></indexterm> <indexterm type="general-imported"><primary>da'o</primary><secondary>syntax of</secondary></indexterm> <indexterm type="general-imported"><primary>da'o</primary><secondary>for cancellation of pro-sumti/pro-bridi assignment</secondary></indexterm> <indexterm type="general-imported"><primary>cancellation of pro-sumti/pro-bridi assignment</primary><secondary>with da'o</secondary></indexterm> <indexterm type="general-imported"><primary>pro-bridi assignment</primary><secondary>explicit cancellation of with da'o</secondary></indexterm> <indexterm type="general-imported"><primary>pro-sumti assignment</primary><secondary>explicit cancellation of with da'o</secondary></indexterm> However, there are ways to cancel all pro-sumti and pro-bridi, so that none of them have known referents. (Some, such as
<jbophrase>mi</jbophrase>, will acquire the same referent as soon as they are used again after the cancellation.) The simplest way to cancel everything is with the cmavo
<jbophrase>da'o</jbophrase> of selma'o DAhO, which is used solely for this purpose; it may appear anywhere, and has no effect on the grammar of texts containing it. One use of
<jbophrase>da'o</jbophrase> is when entering a conversation, to indicate that one's pro-sumti assignments have nothing to do with any assignments already made by other participants in the conversation.</para>
<para> <indexterm type="general-imported"><primary>pro-bridi assignment</primary><secondary>no'i effect on</secondary></indexterm> <indexterm type="general-imported"><primary>pro-sumti assignment</primary><secondary>no'i effect on</secondary></indexterm> <indexterm type="general-imported"><primary>no'i</primary><secondary>effect on pro-sumti/pro-bridi assignments</secondary></indexterm> <indexterm type="general-imported"><primary>ni'o</primary><secondary>effect on pro-sumti/pro-bridi assignments</secondary></indexterm> In addition, the cmavo
<jbophrase>ni'o</jbophrase> and
<jbophrase>no'i</jbophrase> of selma'o NIhO, which are used primarily to indicate shifts in topic, may also have the effect of canceling pro-sumti and pro-bridi assignments, or of reinstating ones formerly in effect. More explanations of NIhO can be found in
- <xref linkend="chapter-structure"/>.</para>
+ <xref linkend="chapter-structure-section-niho"/>.</para>
</section>
<section xml:id="section-du">
<title>The identity predicate: du</title>
<para>The following cmavo is discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>du</cmavo>
<selmaho>GOhA</selmaho>
<description>identity</description>
@@ -1954,21 +1954,21 @@
<title>
<anchor xml:id="c7e15d3"/>
</title>
<interlinear-gloss>
<jbo>fo'a goi le kulnrsu,omi .i lo fo'arselsanga</jbo>
<gloss>x6 stands for Finnish-culture. An x6-song.</gloss>
</interlinear-gloss>
</example>
<para> <indexterm type="lojban-word-imported"><primary>zi'o</primary></indexterm> <!-- FIXME: this indexterm has nowhere to go --><indexterm type="example-imported"><primary>beverage</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>zi'o rafsi</primary><secondary>effect of on place structure of lujvo</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>zi'o rafsi effect on place structure of</secondary></indexterm> Finally, lujvo involving
<jbophrase>zi'o</jbophrase> are also possible, and are fully discussed in
- <xref linkend="chapter-lujvo"/>. In brief, the convention is to use the rafsi for
+ <xref linkend="chapter-lujvo"/>. In brief, the convention is to use the rafsi for <!-- FIXME: chapter 12 does not talk about zi'o, it's probably supposed to -->
<jbophrase>zi'o</jbophrase> as a prefix immediately followed by the rafsi for the number of the place to be deleted. Thus, if we consider a beverage (something drunk without considering who, if anyone, drinks it) as a
<jbophrase>se pinxe be zi'o</jbophrase>, the lujvo corresponding to this is
<jbophrase>zilrelselpinxe</jbophrase> (deleting the second place of
<jbophrase>se pinxe</jbophrase>). Deleting the x1 place in this fashion would move all remaining places up by one. This would mean that
<jbophrase>zilpavypinxe</jbophrase> has the same place structure as
<jbophrase>zilrelselpinxe</jbophrase>, and
<jbophrase>lo zilpavypinxe</jbophrase>, like
<jbophrase>lo zilrelselpinxe</jbophrase>, refers to a beverage, and not to a non-existent drinker.</para>
diff --git a/todocbook/8.xml b/todocbook/8.xml
index ec4c7de..9cbb32a 100644
--- a/todocbook/8.xml
+++ b/todocbook/8.xml
@@ -628,21 +628,21 @@
<interlinear-gloss>
<jbo>le nanmu cu punji le xance le daski</jbo>
<gloss>The man puts the hand at-locus-the pocket.</gloss>
</interlinear-gloss>
</example>
<para> <indexterm type="example-imported"><primary>hands in pockets</primary><secondary>example</secondary></indexterm> is very natural. Of course, if the man is in fact putting his hands into another's pockets, or another's hands into his pockets, the fact can be specified.</para>
<para> <indexterm type="lojban-word-imported"><primary>GEhU selma'o</primary></indexterm> <indexterm type="general-imported"><primary>goi</primary><secondary>rationale for non-inclusion in relative clause chapter</secondary></indexterm> <indexterm type="general-imported"><primary>ge'u</primary><secondary>effect of following logical connective on elidability</secondary></indexterm> <indexterm type="general-imported"><primary>logical connectives</primary><secondary>effect on elidability of ge'u from preceding relative phrase</secondary></indexterm> <indexterm type="general-imported"><primary>ge'u</primary><secondary>elidability of from relative phrases</secondary></indexterm> Finally, the elidable terminator for GOI cmavo is
<jbophrase>ge'u</jbophrase> of selma'o GEhU; it is almost never required. However, if a logical connective immediately follows a sumti modified by a relative phrase, then an explicit
<jbophrase>ge'u</jbophrase> is needed to allow the connective to affect the relativized sumti rather than the sumti of the relative phrase. (What about the cmavo after which selma'o GOI is named? It is discussed in
- <xref linkend="chapter-anaphoric-cmavo"/>, as it is not semantically akin to the other kinds of relative phrases, although the syntax is the same.)</para>
+ <xref linkend="chapter-anaphoric-cmavo-section-koha-broda-series"/>, as it is not semantically akin to the other kinds of relative phrases, although the syntax is the same.)</para>
</section>
<section xml:id="section-zihe">
<title>Multiple relative clauses:
<jbophrase>zi'e</jbophrase></title>
<cmavo-list>
<cmavo-entry>
<cmavo>zi'e</cmavo>
<selmaho>ZIhE</selmaho>
<description>relative clause joiner</description>
</cmavo-entry>
@@ -845,21 +845,21 @@
</example>
<para>
<xref linkend="example-random-id-UmLX"/> will seem most natural to speakers of languages like English, which always puts relative clauses after the noun phrases they are attached to;
<xref linkend="example-random-id-qmCQ"/>, on the other hand, may seem more natural to Finnish or Chinese speakers, who put the relative clause first. Note that in
<xref linkend="example-random-id-qmCQ"/>, the elidable terminator
<jbophrase>ku'o</jbophrase> must appear, or the selbri of the relative clause (
<jbophrase>blabi</jbophrase>) will merge with the selbri of the description (
<jbophrase>gerku</jbophrase>), resulting in an ungrammatical sentence. The purpose of the form appearing in
<xref linkend="example-random-id-qMct"/> will be apparent shortly.</para>
<para>As is explained in detail in
- <xref linkend="chapter-sumti"/>, two different numbers (known as the
+ <xref linkend="chapter-sumti-section-quantified-descriptions"/>, two different numbers (known as the
<quote>inner quantifier</quote> and the
<quote>outer quantifier</quote>) can be attached to a description. The inner quantifier specifies how many things the descriptor refers to: it appears between the descriptor and the description selbri. The outer quantifier appears before the descriptor, and specifies how many of the things referred to by the descriptor are involved in this particular bridi. In the following example,</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-3nJN">
<title>
<anchor xml:id="c8e6d4"/>
</title>
<interlinear-gloss>
<jbo>re le mu prenu cu klama le zarci</jbo>
<gloss>Two-of the five persons go to-the market.</gloss>
<en>Two of the five people [that I have in mind] are going to the market.</en>
@@ -912,21 +912,21 @@
<jbophrase>ku</jbophrase>, then the relative clause is understood to apply to everything which the underlying selbri applies to.</para>
<para>What about
<xref linkend="example-random-id-qMdb"/>? By convention, it means the same as
<xref linkend="example-random-id-qMDQ"/>, and it requires no
<jbophrase>ku</jbophrase>, but it does typically require a
<jbophrase>ku'o</jbophrase> instead. Note that the relative clause comes before the inner quantifier.</para>
<para>When
<jbophrase>le</jbophrase> is the descriptor being used, and the sumti has no explicit outer quantifier, then the outer quantifier is understood to be
<jbophrase>ro</jbophrase> (meaning
<quote>all</quote>), as is explained in
- <xref linkend="chapter-sumti"/>. Thus
+ <xref linkend="chapter-sumti-section-quantified-descriptions"/>. Thus
<jbophrase>le gerku</jbophrase> is taken to mean
<quote>all of the things I refer to as dogs</quote>, possibly all one of them. In that case, there is no difference between a relative clause after the
<jbophrase>ku</jbophrase> or before it. However, if the descriptor is
<jbophrase>lo</jbophrase>, the difference is quite important:</para>
<example xml:id="example-random-id-qmDS" role="interlinear-gloss-example">
<title>
<anchor xml:id="c8e6d8"/>
</title>
<interlinear-gloss>
<jbo>lo prenu ku noi blabi cu klama le zarci</jbo>
@@ -1125,21 +1125,21 @@
<gloss>The of-me car which sleeps isn't going.</gloss>
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>ku'o</primary><secondary>effect of vau on elidability</secondary></indexterm> <indexterm type="general-imported"><primary>vau</primary><secondary>effect on elidability ku'o</secondary></indexterm> Note that
<xref linkend="example-random-id-cVjs"/> uses
<jbophrase>vau</jbophrase> rather than
<jbophrase>ku'o</jbophrase> at the end of the relative clause: this terminator ends every simple bridi and is almost always elidable; in this case, though, it is a syllable shorter than the equally valid alternative,
<jbophrase>ku'o</jbophrase>.</para>
</section>
- <section xml:id="cll_chapter8-section8">
+ <section xml:id="section-vuho">
<title>Relative clauses and complex sumti:
<jbophrase>vu'o</jbophrase></title>
<para>The following cmavo is discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>vu'o</cmavo>
<selmaho>VUhO</selmaho>
<description>relative clause attacher</description>
</cmavo-entry>
</cmavo-list>
@@ -1166,21 +1166,21 @@
<jbo>lu mi klama le zarci li'u noi mi cusku ke'a cu jufra</jbo>
<gloss>[quote] I go to-the market [unquote] incidentally-which-(I express IT) is-a-sentence.</gloss>
<en>
<quote>I'm going to the market</quote>, which I'd said, is a sentence.</en>
</interlinear-gloss>
</example>
<para>which may serve to identify the author of the quotation or some other relevant, but subsidiary, fact about it. All such relative clauses appear only after the simple sumti, never before it.</para>
<para> <indexterm type="lojban-word-imported"><primary>NAhE selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>LAhE selma'o</primary></indexterm> <indexterm type="general-imported"><primary>NAhE selma'o</primary><secondary>effect of relative clause placement with</secondary></indexterm> <indexterm type="general-imported"><primary>LAhE selma'o</primary><secondary>effect of relative clause placement with</secondary></indexterm> <indexterm type="general-imported"><primary>relative clauses and NAhE</primary><secondary>placement considerations</secondary></indexterm> <indexterm type="general-imported"><primary>relative clauses</primary><secondary>impact of NAhE on placement</secondary></indexterm> <indexterm type="general-imported"><primary>relative clauses and LAhE</primary><secondary>placement considerations</secondary></indexterm> <indexterm type="general-imported"><primary>relative clauses</primary><secondary>impact of LAhE on placement</secondary></indexterm> In addition, sumti with attached sumti qualifiers of selma'o LAhE or NAhE+BO (which are explained in detail in
- <xref linkend="chapter-sumti"/>) can have a relative clause appearing after the qualifier and before the qualified sumti, as in:</para>
+ <xref linkend="chapter-sumti-section-sumti-qualifiers"/>) can have a relative clause appearing after the qualifier and before the qualified sumti, as in:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-4sqi">
<title>
<anchor xml:id="c8e8d3"/>
</title>
<interlinear-gloss>
<jbo>la'e poi tolcitno vau lu le xunre cmaxirma li'u cu zvati le vu kumfa</gloss>
<gloss>A-referent-of (which is-old) [quote] The Red Small-horse [unquote] is-at the [far distance] room.</gloss>
<en>An old
<quote>The Red Pony</quote> is in the far room.</en>
@@ -1278,21 +1278,21 @@
<gloss>(Frank and George) who [past] run go to-the house.</gloss>
<en>Frank and George, who ran, go to the house.</en>
</interlinear-gloss>
</example>
<para>In spoken English, tone of voice would serve; in written English, one or both sentences would need rewriting.</para>
</section>
<section xml:id="section-vocatives">
<title>Relative clauses in vocative phrases</title>
<para> <indexterm type="lojban-word-imported"><primary>DOI selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>COI selma'o</primary></indexterm> Vocative phrases are explained in more detail in
- <xref linkend="chapter-sumti"/>. Briefly, they are a method of indicating who a sentence or discourse is addressed to: of identifying the intended listener. They take three general forms, all beginning with cmavo from selma'o COI or DOI (called
+ <xref linkend="chapter-sumti-section-vocatives"/>. Briefly, they are a method of indicating who a sentence or discourse is addressed to: of identifying the intended listener. They take three general forms, all beginning with cmavo from selma'o COI or DOI (called
<quote>vocative words</quote>; there can be one or many), followed by either a name, a selbri, or a sumti. Here are three examples:</para>
<example xml:id="example-random-id-qMG8" role="interlinear-gloss-example">
<title>
<anchor xml:id="c8e9d1"/>
</title>
<interlinear-gloss>
<jbo>coi. frank.</jbo>
<en>Hello, Frank.</en>
</interlinear-gloss>
</example>
@@ -1418,21 +1418,21 @@
<jbo>le prenu poi ke'a goi ko'a zo'u ko'a zvati le kumfa poi ke'a goi ko'e zo'u ko'a zbasu ke'a cu masno</jbo>
<gloss>The man who (IT = it1 : it1 is-in the room which (IT = it2 : it1 built it2) is-slow.</gloss>
</interlinear-gloss>
</example>
<para>
<xref linkend="example-random-id-5TuF"/> is more verbose than
<xref linkend="example-random-id-8RdM"/>, but may be clearer, since it explicitly spells out the two
<jbophrase>ke'a</jbophrase> cmavo, each on its own level, and assigns them to the assignable cmavo
<jbophrase>ko'a</jbophrase> and
<jbophrase>ko'e</jbophrase> (explained in Chapter
- <xref linkend="chapter-sumti"/>).</para>
+ <xref linkend="chapter-anaphoric-cmavo-section-koha-broda-series"/>).</para>
</section>
<section xml:id="section-summary">
<title>Index of relative clause cmavo</title>
<para> <indexterm type="general-imported"><primary>relative clauses</primary><secondary>list of cmavo for</secondary></indexterm> Relative clause introducers (selma'o NOI):</para>
<cmavo-list>
<cmavo-entry>
<cmavo>noi</cmavo>
<description>incidental clauses</description>
</cmavo-entry>
<cmavo-entry>
diff --git a/todocbook/9.xml b/todocbook/9.xml
index b531aa1..74953d9 100644
--- a/todocbook/9.xml
+++ b/todocbook/9.xml
@@ -626,21 +626,21 @@
<jbophrase>se ke blanu zdani [ke'e]</jbophrase> is therefore:</para>
<place-structure>
x1 is the inhabitant of the blue house (etc.) x2
</place-structure>
<para>Consequently,
<xref linkend="example-random-id-wQbB"/> means:</para>
<place-structure>
I am the inhabitant of the blue house which is this thing.
</place-structure>
<para>Conversion applied to only part of a tanru has subtler effects which are explained in
- <xref linkend="chapter-selbri"/>.</para>
+ <xref linkend="chapter-selbri-section-place-conversion"/>.</para>
<para> <indexterm type="general-imported"><primary>multiple conversion</primary><secondary>effect of ordering</secondary></indexterm> <indexterm type="general-imported"><primary>conversion</primary><secondary>effect of multiple on a selbri</secondary></indexterm> <indexterm type="general-imported"><primary>multiple SE</primary><secondary>effect of ordering</secondary></indexterm> <indexterm type="general-imported"><primary>SE selma'o</primary><secondary>effect of multiple on a selbri</secondary></indexterm> 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
<jbophrase>se te klama</jbophrase> is achieved by exchanging the x1 and x2 place of
<jbophrase>te klama</jbophrase>, producing:</para>
<para> <indexterm type="lojban-word-imported"><primary>se te</primary></indexterm> FIXME: TAG SPOT</para>
<place-structure>
x1 is the destination and x2 is the origin of x3 going via x4 using x5
</place-structure>
<para>On the other hand,
@@ -900,21 +900,21 @@
<en>A man of the north came to the city.</en>
</interlinear-gloss>
</example>
<para><!-- FIXME: what to do with these "s? --><indexterm type="general-imported"><primary>modal place</primary><secondary>on description selbri</secondary></indexterm> <indexterm type="general-imported"><primary>"of"</primary><secondary>in English</secondary><tertiary>compared with do'e</tertiary></indexterm> <indexterm type="general-imported"><primary>do'e</primary><secondary>compared with English "of"</secondary></indexterm> Here
<jbophrase>le berti</jbophrase> is provided as a modal place of the selbri
<jbophrase>nanmu</jbophrase>, but its exact significance is vague, and is paralleled in the colloquial translation by the vague English preposition
<quote>of</quote>.
<xref linkend="example-random-id-2vMd"/> also illustrates a modal place bound into a selbri with
<jbophrase>be</jbophrase>. This construction is useful when the selbri of a description requires a modal place; this and other uses of
<jbophrase>be</jbophrase> are more fully explained in
- <xref linkend="chapter-selbri"/>.</para>
+ <xref linkend="chapter-selbri-section-be-sumti"/>.</para>
</section>
<section xml:id="section-causals">
<title>Modal sentence connection: the causals</title>
<para>The following cmavo are discussed in this section:</para>
<para> <indexterm type="lojban-word-imported"><primary>ni'i</primary></indexterm> <indexterm type="lojban-word-imported"><primary>mu'i</primary></indexterm> <indexterm type="lojban-word-imported"><primary>ki'u</primary></indexterm> <indexterm type="lojban-word-imported"><primary>ri'a</primary></indexterm> FIXME: TAG SPOT</para>
<cmavo-list>
<cmavo-entry>
<cmavo>ri'a</cmavo>
<selmaho>BAI</selmaho>
@@ -1190,21 +1190,21 @@
<interlinear-gloss>
<jbo>mi jgari ri'agi le kabri gi lei djacu</jbo>
<gloss>I grasp because the cup, the-mass-of water.</gloss>
</interlinear-gloss>
</example>
<para>
<xref linkend="example-random-id-o7FG"/> means exactly the same as
<xref linkend="example-random-id-2D4c"/> through
<xref linkend="example-random-id-rQ77"/>, but there is no idiomatic English translation that will distinguish it from them.</para>
<para> <indexterm type="general-imported"><primary>termset modal connection</primary></indexterm> <indexterm type="general-imported"><primary>modals</primary><secondary>termset connection</secondary></indexterm> If the two connected bridi are different in more than one sumti, then a termset may be employed. Termsets are explained more fully in
- <xref linkend="chapter-connectives"/>, but are essentially a mechanism for creating connections between multiple sumti simultaneously.</para>
+ <xref linkend="chapter-connectives-section-termsets"/>, but are essentially a mechanism for creating connections between multiple sumti simultaneously.</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-LetE">
<title>
<anchor xml:id="c9e8d5"/>
</title>
<interlinear-gloss>
<jbo>mi dunda le cukta la djan. .imu'ibo la djan. dunda lei jdini mi</jbo>
<gloss>I gave the book to John. Motivated-by John gave the-mass-of money to-me.</gloss>
<en>I gave the book to John, because John gave money to me.</en>
</interlinear-gloss>
</example>
@@ -1215,21 +1215,21 @@
<anchor xml:id="c9e8d6"/>
</title>
<interlinear-gloss>
<jbo>nu'i mu'igi mi le cukta la djan. gi la djan. lei jdini mi nu'u dunda</jbo>
<gloss>[start] because I, the book, John; John, the-mass-of money, me [end] gives.</gloss>
</interlinear-gloss>
</example>
<para>Here there are three sumti in each half of the termset, because the two bridi share only their selbri.</para>
<para> <indexterm type="general-imported"><primary>bridi-tail modal connection</primary></indexterm> <indexterm type="general-imported"><primary>modal bridi-tail connection</primary></indexterm> <indexterm type="general-imported"><primary>modal connection of selbri</primary><secondary>using bridi-tail modal connection</secondary></indexterm> There is no modal connection between selbri as such: bridi which differ only in the selbri can be modally connected using bridi-tail modal connection. The bridi-tail construct is more fully explained in
- <xref linkend="chapter-connectives"/>, but essentially it consists of a selbri with optional sumti following it.
+ <xref linkend="chapter-connectives-section-compound-bridi"/>, but essentially it consists of a selbri with optional sumti following it.
<xref linkend="example-random-id-qMN7"/> is suitable for bridi-tail connection, and could be shortened to:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-Do9b">
<title>
<anchor xml:id="c9e8d7"/>
</title>
<interlinear-gloss>
<jbo>mi mu'igi viska le cukta gi lebna le cukta</jbo>
<gloss>I, because saw the book, took the book.</gloss>
</interlinear-gloss>
</example>
@@ -1240,21 +1240,21 @@
<anchor xml:id="c9e8d8"/>
</title>
<interlinear-gloss>
<jbo>mi mu'igi viska gi lebna vau le cukta</jbo>
<gloss>I because saw, therefore took, the book.</gloss>
</interlinear-gloss>
</example>
<para>where
<jbophrase>le cukta</jbophrase> is set off by the non-elidable
<jbophrase>vau</jbophrase> and is made to belong to both bridi-tails - see
- <xref linkend="chapter-connectives"/> for more explanations.</para>
+ <xref linkend="chapter-connectives-section-compound-bridi"/> for more explanations.</para>
<para> <indexterm type="general-imported"><primary>shared bridi-tail sumti</primary><secondary>avoiding</secondary></indexterm> <indexterm type="general-imported"><primary>vau for shared bridi-tail sumti</primary><secondary>avoiding</secondary></indexterm> Since this is a chapter on rearranging sumti, it is worth pointing out that
<xref linkend="example-random-id-YXps"/> can be further rearranged to:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-Pxca">
<title>
<anchor xml:id="c9e8d9"/>
</title>
<interlinear-gloss>
<jbo>mi le cukta mu'igi viska gi lebna</jbo>
<gloss>I, the book, because saw, therefore took.</gloss>
</interlinear-gloss>
@@ -1407,21 +1407,21 @@
</example>
<para>Here the
<jbophrase>bai</jbophrase> is spread over both
<jbophrase>klama le zarci</jbophrase> and
<jbophrase>cadzu le bisli</jbophrase>, and the
<jbophrase>ge ... gi</jbophrase> represents the logical connection
<quote>both-and</quote> between the two.</para>
<para><indexterm type="general-imported"><primary>modals</primary><secondary>expanding scope over multiple sentences with tu'e…tu'u</secondary></indexterm> Similarly, a modal can be attached to multiple sentences that have been combined with
<jbophrase>tu'e</jbophrase> and
<jbophrase>tu'u</jbophrase>, which are explained in more detail in
- <xref linkend="chapter-structure"/>:</para>
+ <xref linkend="chapter-structure-section-i"/>:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-boYr">
<title>
<anchor xml:id="c9e9d9"/>
</title>
<interlinear-gloss>
<jbo>bai tu'e mi klama le zarci .i mi cadzu le bisli [tu'u]</jbo>
<gloss>Under-compulsion [start] I go to-the market. I walk on-the ice [end].</gloss>
</interlinear-gloss>
</example>
<para>means the same thing as
@@ -1837,21 +1837,21 @@
<jbophrase>fai</jbophrase> behaves like
<jbophrase>fi'a</jbophrase>; it does not affect the numbering of the other places around it.</para>
<para> <indexterm type="general-imported"><primary>modal conversions</primary><secondary>in descriptions</secondary></indexterm> Like SE conversions, JAI conversions are especially convenient in descriptions. We may refer to
<quote>the language of an expression</quote> as
<jbophrase>le jai bau cusku</jbophrase>, for example.</para>
<para> <indexterm type="general-imported"><primary>modal conversion</primary><secondary>with no modal specified</secondary></indexterm> <indexterm type="general-imported"><primary>jai without modal</primary><secondary>meaning</secondary></indexterm> In addition, it is grammatical to use
<jbophrase>jai</jbophrase> without a following modal. This usage is not related to modals, but is explained here for completeness. The effect of
<jbophrase>jai</jbophrase> by itself is to send the x1 place, which should be an abstraction, into the
<jbophrase>fai</jbophrase> position, and to raise one of the sumti from the abstract sub-bridi into the x1 place of the main bridi. This feature is discussed in more detail in
- <xref linkend="chapter-abstractions"/>. The following two examples mean the same thing:</para>
+ <xref linkend="chapter-abstractions-section-jai"/>. The following two examples mean the same thing:</para>
<example xml:id="example-random-id-qMsd" role="interlinear-gloss-example">
<title>
<anchor xml:id="c9e12d3"/>
</title>
<interlinear-gloss>
<jbo>le nu mi lebna le cukta cu se krinu le nu mi viska le cukta</jbo>
<gloss>The event-of (I take the book) is-justified-by the event-of (I see the book).</gloss>
<en>My taking the book is justified by my seeing it.</en>
</interlinear-gloss>
</example>
diff --git a/todocbook/TODO b/todocbook/TODO
index 58c91be..c7a8458 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: 3 to 19 (they contain FIXMEs, though)
+Zort: All chapters except 2 excepting index stuff (plenty of FIXMEs, though)
Matthew Walton: 3
------
Ignore Chapter 2 for now.
------
If you have any trouble, add a FIXME comment, like so:
commit 8efd40db4c231f470a1c962c4c3808e2f0a75071
Author: Eitan Postavsky <eitanp32@gmail.com>
Date: Tue Jan 25 15:47:05 2011 -0500
Chapter 21: lists.
diff --git a/todocbook/21.xml b/todocbook/21.xml
index a8cf4a6..7b95525 100644
--- a/todocbook/21.xml
+++ b/todocbook/21.xml
@@ -7,52 +7,111 @@
<para>/* /*Lojban Machine Grammar, Final Baseline The Lojban Machine Grammardocument is explicitly dedicated to the public domain by its author,The Logical Language Group, Inc.</para>
<para>grammar.300 */</para>
<para>/* The Lojban machine parsing algorithm is a multi-step process. The YACC machine grammar presented here is an amalgam of those steps, concatenated so as to allow YACC to verify the syntactic ambiguity of the grammar. YACC is used to generate a parser for a portion of the grammar, which is LALR1 (the type of grammar that YACC is designed to identify and process successfully), but most of the rest of the grammar must be parsed using some language-coded processing.</para>
<bridgehead>Step 1 - Lexing</bridgehead>
<para>From phonemes, stress, and pause, it is possible to resolve Lojban unambiguously into a stream of words. Any machine processing of speech will have to have some way to deal with ’non-Lojban’ failures of fluent speech, of course. The resolved words can be expressed as a text file using Lojban’s phonetic spelling rules.</para>
<para>The following steps assume that there is the possibility of non-Lojban text within the Lojban text (delimited appropriately). Such non-Lojban text may not be reducible from speech phonetically. However, step 2 allows the filtering of a phonetically transcribed text stream, to recognize such portions of non-Lojban text where properly delimited, without interference with the parsing algorithm.</para>
<bridgehead>Step 2 - Filtering</bridgehead>
<para>From start to end, performing the following filtering and lexing tasks using the given order of precedence in case of conflict:</para>
- <para>a. If the Lojban word <jbophrase>zoi</jbophrase> (selma'o ZOI) is identified, take the following Lojban word (which should be end delimited with a pause for separation from the following non-Lojban text) as an opening delimiter. Treat all text following that delimiter, until that delimiter recurs
-
- <emphasis>after a pause</emphasis>, as grammatically a single token (labelled ’
- <xref linkend="cll_yacc-699"/>’ in this grammar). There is no need for processing within this text except as necessary to find the closing delimiter.</para>
- <para>b. If the Lojban word <jbophrase>zo</jbophrase> (selma'o ZO) is identified, treat the following Lojban word as a token labelled ’
- <xref linkend="cll_yacc-698"/>’, instead of lexing it by its normal grammatical function.</para>
- <para>c. If the Lojban word <jbophrase>lo'u</jbophrase> (selma'o LOhU) is identified, search for the closing delimiter <jbophrase>le'u</jbophrase> (selma'o LEhU), ignoring any such closing delimiters absorbed by the previous two steps. The text between the delimiters should be treated as the single token ’
- <xref linkend="cll_yacc-697"/>’.</para>
- <para>d. Categorize all remaining words into their Lojban selma'o category, including the various delimiters mentioned in the previous steps. In all steps after step 2, only the selma'o token type is significant for each word.</para>
- <para>e. If the word <jbophrase>si</jbophrase> (selma'o SI) is identified, erase it and the previous word (or token, if the previous text has been condensed into a single token by one of the above rules).</para>
- <para>f. If the word <jbophrase>sa</jbophrase> (selma'o SA) is identified, erase it and all preceding text as far back as necessary to make what follows attach to what precedes. (This rule is hard to formalize and may receive further definition later.)</para>
- <para>g. If the word ’su’ (selma'o SU) is identified, erase it and all preceding text back to and including the first preceding token word which is in one of the selma'o: NIhO, LU, TUhE, and TO. However, if speaker identification is available, a SU shall only erase to the beginning of a speaker’s discourse, unless it occurs at the beginning of a speaker’s discourse. (Thus, if the speaker has said something, two adjacent uses of <jbophrase>su</jbophrase> are required to erase the entire conversation.</para>
+ <orderedlist numeration="lowerroman">
+ <listitem>
+ <para>If the Lojban word <jbophrase>zoi</jbophrase> (selma'o ZOI) is identified, take the following Lojban word (which should be end delimited with a pause for separation from the following non-Lojban text) as an opening delimiter. Treat all text following that delimiter, until that delimiter recurs
+ <emphasis>after a pause</emphasis>, as grammatically a single token (labelled ’
+ <xref linkend="cll_yacc-699"/>’ in this grammar). There is no need for processing within this text except as necessary to find the closing delimiter.</para>
+ </listitem>
+ <listitem>
+ <para>If the Lojban word <jbophrase>zo</jbophrase> (selma'o ZO) is identified, treat the following Lojban word as a token labelled ’
+ <xref linkend="cll_yacc-698"/>’, instead of lexing it by its normal grammatical function.</para>
+ </listitem>
+ <listitem>
+ <para>If the Lojban word <jbophrase>lo'u</jbophrase> (selma'o LOhU) is identified, search for the closing delimiter <jbophrase>le'u</jbophrase> (selma'o LEhU), ignoring any such closing delimiters absorbed by the previous two steps. The text between the delimiters should be treated as the single token ’
+ <xref linkend="cll_yacc-697"/>’.</para>
+ </listitem>
+ <listitem>
+ <para>Categorize all remaining words into their Lojban selma'o category, including the various delimiters mentioned in the previous steps. In all steps after step 2, only the selma'o token type is significant for each word.</para>
+ </listitem>
+ <listitem>
+ <para>If the word <jbophrase>si</jbophrase> (selma'o SI) is identified, erase it and the previous word (or token, if the previous text has been condensed into a single token by one of the above rules).</para>
+ </listitem>
+ <listitem>
+ <para>If the word <jbophrase>sa</jbophrase> (selma'o SA) is identified, erase it and all preceding text as far back as necessary to make what follows attach to what precedes. (This rule is hard to formalize and may receive further definition later.)</para>
+ </listitem>
+ <listitem>
+ <para>If the word <jbophrase>su</jbophrase> (selma'o SU) is identified, erase it and all preceding text back to and including the first preceding token word which is in one of the selma'o: NIhO, LU, TUhE, and TO. However, if speaker identification is available, a SU shall only erase to the beginning of a speaker’s discourse, unless it occurs at the beginning of a speaker’s discourse. (Thus, if the speaker has said something, two adjacent uses of <jbophrase>su</jbophrase> are required to erase the entire conversation.</para>
+ </listitem>
+ </orderedlist>
<bridgehead>Step 3 - Termination</bridgehead>
<para>If the text contains a FAhO, treat that as the end-of-text and ignore everything that follows it.</para>
<bridgehead>Step 4 - Absorption of Grammar-Free Tokens</bridgehead>
<para>In a new pass, perform the following absorptions (absorption means that the token is removed from the grammar for processing in following steps, and optionally reinserted, grouped with the absorbing token after parsing is completed).</para>
- <para>a. Token sequences of the form any - (ZEI - any) ..., where there may be any number of ZEIs, are merged into a single token of selma'o BRIVLA.</para>
- <para>b. Absorb all selma'o BAhE tokens into the following token. If they occur at the end of text, leave them alone (they are errors).</para>
- <para>c. Absorb all selma'o BU tokens into the previous token. Relabel the previous token as selma'o BY.</para>
- <para>d. If selma'o NAI occurs immediately following any of tokens UI or CAI, absorb the NAI into the previous token.</para>
- <para>e. Absorb all members of selma'o DAhO, FUhO, FUhE, UI, Y, and CAI into the previous token. All of these null grammar tokens are permitted following any word of the grammar, without interfering with that word’s grammatical function, or causing any effect on the grammatical interpretation of any other token in the text. Indicators at the beginning of text are explicitly handled by the grammar.</para>
+ <orderedlist numeration="lowerroman">
+ <listitem>
+ <para>Token sequences of the form any - (ZEI - any) ..., where there may be any number of ZEIs, are merged into a single token of selma'o BRIVLA.</para>
+ </listitem>
+ <listitem>
+ <para>Absorb all selma'o BAhE tokens into the following token. If they occur at the end of text, leave them alone (they are errors).</para>
+ </listitem>
+ <listitem>
+ <para>Absorb all selma'o BU tokens into the previous token. Relabel the previous token as selma'o BY.</para>
+ </listitem>
+ <listitem>
+ <para>If selma'o NAI occurs immediately following any of tokens UI or CAI, absorb the NAI into the previous token.</para>
+ </listitem>
+ <listitem>
+ <para>Absorb all members of selma'o DAhO, FUhO, FUhE, UI, Y, and CAI into the previous token. All of these null grammar tokens are permitted following any word of the grammar, without interfering with that word’s grammatical function, or causing any effect on the grammatical interpretation of any other token in the text. Indicators at the beginning of text are explicitly handled by the grammar.</para>
+ </listitem>
+ </orderedlist>
<bridgehead>Step 5 - Insertion of Lexer Lexemes</bridgehead>
<para>Lojban is not in itself LALR1. There are words whose grammatical function is determined by following tokens. As a result, parsing of the YACC grammar must take place in two steps. In the first step, certain strings of tokens with defined grammars are identified, and either</para>
-
- <para>a. are replaced by a single specified ’lexer token’ for step 6, or</para>
- <para>b. the lexer token is inserted in front of the token string to identify it uniquely.</para>
+ <orderedlist numeration="lowerroman">
+ <listitem>
+ <para>are replaced by a single specified ’lexer token’ for step 6, or</para>
+ </listitem>
+ <listitem>
+ <para>the lexer token is inserted in front of the token string to identify it uniquely.</para>
+ </listitem>
+ </orderedlist>
<para>The YACC grammar included herein is written to make YACC generation of a step 6 parser easy regardless of whether a. or b. is used. The strings of tokens to be labelled with lexer tokens are found in rule terminals labelled with numbers between 900 and 1099. These rules are defined with the lexer tokens inserted, with the result that it can be verified that the language is LALR1 under option b. after steps 1 through 4 have been performed. Alternatively, if option a. is to be used, these rules are commented out, and the rule terminals labelled from 800 to 900 refer to the lexer tokens
<emphasis>without</emphasis> the strings of defining tokens. Two sets of lexer tokens are defined in the token set so as to be compatible with either option.</para>
<para>In this step, the strings must be labelled with the appropriate lexer tokens. Order of inserting lexer tokens
<emphasis>IS</emphasis> significant, since some shorter strings that would be marked with a lexer token may be found inside longer strings. If the tokens are inserted before or in place of the shorter strings, the longer strings cannot be identified.</para>
- <para>If option a. is chosen, the following order of insertion works correctly (it is not the only possible order): A, C, D, B, U, E, H, I, J, K, M, N, G, O, V, W, F, P, R, T, S, Y, L, Q. This ensures that the longest rules will be processed first; a PA+MAI will not be seen as a PA with a dangling MAI at the end, for example.</para>
+ <para>If option a. is chosen, the following order of insertion works correctly (it is not the only possible order): <!-- xref instead of "option a."? -->
+ <simplelist type="inline">
+ <member>A</member>
+ <member>C</member>
+ <member>D</member>
+ <member>B</member>
+ <member>U</member>
+ <member>E</member>
+ <member>H</member>
+ <member>I</member>
+ <member>J</member>
+ <member>K</member>
+ <member>M</member>
+ <member>N</member>
+ <member>G</member>
+ <member>O</member>
+ <member>V</member>
+ <member>W</member>
+ <member>F</member>
+ <member>P</member>
+ <member>R</member>
+ <member>T</member>
+ <member>S</member>
+ <member>Y</member>
+ <member>L</member>
+ <member>Q</member>
+ </simplelist>
+ . This ensures that the longest rules will be processed first; a PA+MAI will not be seen as a PA with a dangling MAI at the end, for example. </para>
<bridgehead>Step 6 - YACC Parsing</bridgehead>
<para>YACC should now be able to parse the Lojban text in accordance with the rule terminals labelled from 1 to 899 under option 5a, or 1 to 1099 under option 5b. Comment out the rules beyond 900 if option 5a is used, and comment out the 700-series of lexer-tokens, while restoring the series of lexer tokens numbered from 900 up.</para>
<para>*/</para>
<programlisting xml:space="preserve">
%token
<anchor xml:id="y501"/>
<anchor xreflabel="YACC rule #501" xml:id="cll_yacc-501"/> A_501 /* eks; basic afterthought logical connectives */
%token
<anchor xml:id="y502"/>
<anchor xreflabel="YACC rule #502" xml:id="cll_yacc-502"/> BAI_502 /* modal operators */
@@ -1861,21 +1920,21 @@ the 900 series rules are found in the lexer. */
<anchor xml:id="y434"/>
<anchor xreflabel="YACC rule #434" xml:id="cll_yacc-434"/> ZOI_quote_434 :
<xref linkend="cll_yacc-627"/>
<xref linkend="cll_yacc-698"/>
/*pause*/
<xref linkend="cll_yacc-699"/> /*pause*/
<xref linkend="cll_yacc-698"/>
;
-/* ’pause’ is morphemic, represented by ’.’ The lexer assembles
+/* ’pause’ is morphemic, represented by <jbophrase role="letteral">.</jbophrase> The lexer assembles
<xref linkend="cll_yacc-699"/> */
<anchor xml:id="y435"/>
<anchor xreflabel="YACC rule #435" xml:id="cll_yacc-435"/> ZO_quote_435 :
<xref linkend="cll_yacc-626"/>
<xref linkend="cll_yacc-698"/>
;
/* ’word’ may not be a compound; but it can be any valid Lojban selma'o value,
including ZO, ZOI, SI, SA, SU. The preparser will not lex the word per its
diff --git a/todocbook/3.xml b/todocbook/3.xml
index 6e20e63..6bbe930 100644
--- a/todocbook/3.xml
+++ b/todocbook/3.xml
@@ -39,21 +39,21 @@
<quote>w</quote>.</para>
<para> <indexterm type="general-imported"><primary>alphabetic order</primary></indexterm> The alphabetic order given above is that of the ASCII coded character set, widely used in computers. By making Lojban alphabetical order the same as ASCII, computerized sorting and searching of Lojban text is facilitated.</para>
<para> <indexterm type="general-imported"><primary>stress</primary><secondary>showing non-standard</secondary></indexterm> <indexterm type="general-imported"><primary>capital letters</primary><secondary>use of</secondary></indexterm> Capital letters are used only to represent non-standard stress, which can appear only in the representation of Lojbanized names. Thus the English name
<quote>Josephine</quote>, as normally pronounced, is Lojbanized as
<jbophrase>DJOsefin.</jbophrase>, pronounced
<phrase role="IPA">['dʒosɛfinʔ]</phrase>. (See
<xref linkend="section-basic-phonetics"/> for an explanation of the symbols within square brackets.) Technically, it is sufficient to capitalize the vowel letter, in this case
- <quote>O</quote>, but it is easier on the reader to capitalize the whole syllable.</para>
+ <jbophrase role="letteral">O</jbophrase>, but it is easier on the reader to capitalize the whole syllable.</para>
<para>Without the capitalization, the ordinary rules of Lojban stress would cause the
<jbophrase>se</jbophrase> syllable to be stressed. Lojbanized names are meant to represent the pronunciation of names from other languages with as little distortion as may be; as such, they are exempt from many of the regular rules of Lojban phonology, as will appear in the rest of this chapter.</para>
</section>
<section xml:id="section-basic-phonetics">
<title>Basic Phonetics</title>
<para> <indexterm type="general-imported"><primary>brackets</primary><secondary>use in IPA notation</secondary></indexterm> <indexterm type="general-imported"><primary>phonetic alphabet</primary></indexterm> <indexterm type="general-imported"><primary>IPA</primary></indexterm> <indexterm type="general-imported"><primary>International Phonetic Alphabet (see also IPA)</primary></indexterm> Lojban pronunciations are defined using the International Phonetic Alphabet, or IPA, a standard method of transcribing pronunciations. By convention, IPA transcriptions are always within square brackets: for example, the word
<quote>cat</quote> is pronounced (in General American pronunciation)
commit bcacdb645be573910870fb23a531c9ccd9e11077
Author: Eitan Postavsky <eitanp32@gmail.com>
Date: Tue Jan 25 15:23:17 2011 -0500
Chapter 19: example tags. Chapter 21: quotes and section IDs.
diff --git a/todocbook/19.xml b/todocbook/19.xml
index fba392a..a2f5bca 100644
--- a/todocbook/19.xml
+++ b/todocbook/19.xml
@@ -200,21 +200,21 @@
<para>
<xref linkend="example-random-id-V2B4"/> means the same as
<xref linkend="example-random-id-p4ww"/>, and it is simpler. However, often the position of the topic in the place structure of the selbri within the comment is vague:</para>
<para> <indexterm type="example-imported"><primary>fish eat</primary><secondary>example</secondary></indexterm> FIXME: TAG SPOT</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-tpcK">
<title>
<anchor xml:id="c19e4d5"/>
</title>
<interlinear-gloss>
<jbo>le finpe zo'u citka</jbo>
- <en>the fish : eat</en>
+ <gloss>the fish : eat</gloss>
</interlinear-gloss>
</example>
<para>Is the fish eating or being eaten? The sentence doesn't say. The Chinese equivalent of
<xref linkend="example-random-id-tpcK"/> is:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-N6H3">
<title>
<anchor xml:id="c19e4d6"/>
</title>
<interlinear-gloss>
<jbo>yu</jbo>
@@ -658,75 +658,67 @@
<xref linkend="example-random-id-GuYz"/> to
<xref linkend="example-random-id-PaKo"/> all mean the same thing. But consider the lujvo
<jbophrase>nunkla</jbophrase>, formed by applying the abstraction operator
<jbophrase>nu</jbophrase> to
<jbophrase>klama</jbophrase>:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-sMPn">
<title>
<anchor xml:id="c19e6d4"/>
</title>
<interlinear-gloss>
- <jbo>la'edi'u cu nunkla</jbo>
-
- <gloss>mi le zarci le zdani le dargu le karce</gloss>
- <gloss>The-referent-of-the-previous-sentence is-an-event-of-going</gloss>
- <gloss>by-me to-the market from-the house via-the road using-the car.</gloss>
+ <jbo>la'edi'u cu nunkla mi le zarci le zdani le dargu le karce</jbo>
+ <gloss>The-referent-of-the-previous-sentence is-an-event-of-going by-me to-the market from-the house via-the road using-the car.</gloss>
</interlinear-gloss>
</example>
<para> <indexterm type="lojban-word-imported"><primary>SE selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>se</primary></indexterm> <indexterm type="general-imported"><primary>FA selma'o</primary><secondary>after 5th place</secondary></indexterm> <indexterm type="general-imported"><primary>SE selma'o</primary><secondary>after 5th place</secondary></indexterm> <indexterm type="general-imported"><primary>subscripts</primary><secondary>and sumti re-ordering</secondary></indexterm>
<xref linkend="example-random-id-sMPn"/> shows that
<jbophrase>nunkla</jbophrase> has six places: the five places of
<jbophrase>klama</jbophrase> plus a new one (placed first) for the event itself. Performing transformations similar to that of
<xref linkend="example-random-id-QPGC"/> requires an additional conversion cmavo that exchanges the x1 and x6 places. The solution is to use any cmavo of SE with a subscript "6" (<xref linkend="chapter-structure"/>):</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-zGhw">
<title>
<anchor xml:id="c19e6d5"/>
</title>
<interlinear-gloss>
- <jbo>le karce cu sexixa nunkla mi</jbo>
- <gloss>le zarci le zdani le dargu la'edi'u</gloss>
+ <jbo>le karce cu sexixa nunkla mi le zarci le zdani le dargu la'edi'u</jbo>
- <gloss>The car is-a-transportation-means-in-the-event-of-going by-me</gloss>
- <gloss>to-the market via-the road which-is-referred-to-by-the-last-sentence.</gloss>
+ <gloss>The car is-a-transportation-means-in-the-event-of-going by-me to-the market via-the road which-is-referred-to-by-the-last-sentence.</gloss>
</interlinear-gloss>
</example>
<para>Likewise, a sixth place tag can be created by using any cmavo of FA with a subscript:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-EW1n">
<title>
<anchor xml:id="c19e6d6"/>
</title>
<interlinear-gloss>
- <jbo>fu le dargu fo le zdani fe mi fa la'edi'u</jbo>
-
- <gloss>fi le zarci faxixa le karce cu nunkla</gloss>
- <gloss>Via the road, from the house, by me, the-referent-of-the-last-sentence,</gloss>
- <gloss>to the market, using the car, is-an-event-of-going.</gloss>
+ <jbo>fu le dargu fo le zdani fe mi fa la'edi'u fi le zarci faxixa le karce cu nunkla</jbo>
+ <gloss>Via the road, from the house, by me, the-referent-of-the-last-sentence, to the market, using the car, is-an-event-of-going.</gloss>
</interlinear-gloss>
</example>
<para>
<xref linkend="example-random-id-sMPn"/> to
<xref linkend="example-random-id-EW1n"/> also all mean the same thing, and each is derived straightforwardly from any of the others, despite the tortured nature of the English glosses. In addition, any other member of SE or FA could be substituted into
<jbophrase>sexixa</jbophrase> and
<jbophrase>faxixa</jbophrase> without change of meaning:
<jbophrase>vexixa</jbophrase> means the same thing as
<jbophrase>sexixa</jbophrase>.</para>
<para> <indexterm type="general-imported"><primary>ko'a-series</primary><secondary>after tenth</secondary></indexterm> <indexterm type="general-imported"><primary>da-series</primary><secondary>after third</secondary></indexterm> <indexterm type="general-imported"><primary>subscripts</primary><secondary>and pro-sumti</secondary></indexterm> Lojban provides two groups of pro-sumti, both belonging to selma'o KOhA. The ko'a-series cmavo are used to refer to explicitly specified sumti to which they have been bound using
<jbophrase>goi</jbophrase>. The da-series, on the other hand, are existentially or universally quantified variables. (These concepts are explained more fully in
<xref linkend="chapter-quantifiers"/>.) There are ten ko'a-series cmavo and 3 da-series cmavo available.</para>
<para> <indexterm type="lojban-word-imported"><primary>da</primary></indexterm> <indexterm type="lojban-word-imported"><primary>DA selma'o</primary></indexterm> If more are required, any cmavo of the ko'a-series or the da-series can be subscripted:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-Bday">
<title>
<anchor xml:id="c19e6d7"/>
</title>
<interlinear-gloss>
<jbo>daxivo</jbo>
- <en>X sub 4</en>
+ <gloss>X sub 4</gloss>
</interlinear-gloss>
</example>
<para>is the 4th bound variable of the 1st sequence of the da-series, and</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-gfXT">
<title>
<anchor xml:id="c19e6d8"/>
</title>
<interlinear-gloss>
<jbo>ko'ixipaso</jbo>
<gloss>something-3 sub 18</gloss>
@@ -759,21 +751,21 @@
<jbophrase>boi</jbophrase> after each
<jbophrase>xy.</jbophrase> cmavo; this terminator allows the subscript to be attached without ambiguity.)</para>
<para> <indexterm type="general-imported"><primary>subscripts</primary><secondary>and names</secondary></indexterm> Names, which are similar to pro-sumti, can also be subscripted to distinguish two individuals with the same name:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-tW4J">
<title>
<anchor xml:id="c19e6d10"/>
</title>
<interlinear-gloss>
<jbo>la djan. xipa cusku lu mi'enai do li'u la djan. xire</jbo>
- <en>John</en>
+ <gloss>John<subscript>1</subscript> expresses ``I-am-not you'' to John<subscript>2</subscript>.</gloss>
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>subscripts</primary><secondary>and tense</secondary></indexterm> Subscripts on tenses allow talking about more than one time or place that is described by the same general cmavo. For example,
<jbophrase>puxipa</jbophrase> could refer to one point in the past, and
<jbophrase>puxire</jbophrase> a second point (earlier or later).</para>
<para> <indexterm type="general-imported"><primary>subscripts</primary><secondary>and fuzzy truths</secondary></indexterm> You can place a subscript on the word
<jbophrase>ja'a</jbophrase>, the bridi affirmative of selma'o NA, to express so-called fuzzy truths. The usual machinery for fuzzy logic (statements whose truth value is not merely
<quote>true</quote> or
<quote>false</quote>, but is expressed by a number in the range 0 to 1) in Lojban is the abstractor
<jbophrase>jei</jbophrase>:</para>
@@ -1034,24 +1026,22 @@
</example>
<para>
<xref linkend="example-random-id-IUz8"/> is grammatical even though the embedded quotation is not. Similarly,
<jbophrase>lo'u</jbophrase> quotation can quote fragments of a text which themselves do not constitute grammatical utterances:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-EXeq">
<title>
<anchor xml:id="c19e9d3"/>
</title>
<interlinear-gloss>
- <jbo>lu le mlatu cu viska le finpe li'u zo'u lo'u viska le le'u</jbo>
- <gloss>cu selbasti .ei lo'u viska lo le'u</gloss>
- <gloss>[quote] le mlatu cu viska le finpe [unquote] : [quote] viska le [unquote]</gloss>
- <gloss>is-replaced-by [obligation!] [quote] viska lo [unquote].</gloss>
+ <jbo>lu le mlatu cu viska le finpe li'u zo'u lo'u viska le le'u cu selbasti .ei lo'u viska lo le'u</jbo>
+ <gloss>[quote] <jbophrase>le mlatu cu viska le finpe</jbophrase> [unquote] : [quote] <jbophrase>viska le</jbophrase> [unquote] is-replaced-by [obligation!] [quote] <jbophrase>viska lo</jbophrase> [unquote].</gloss>
<en>In the sentence
<jbophrase>le mlatu viska le finpe</jbophrase>,
<jbophrase>viska le</jbophrase> should be replaced by
<jbophrase>viska lo</jbophrase>.</en>
</interlinear-gloss>
</example>
<para>Note the topic-comment formulation (
<xref linkend="section-topic-comments"/>) and the indicator applying to the selbri only (
<xref linkend="section-attitudinal-scope"/>). Neither
@@ -1059,43 +1049,37 @@
<jbophrase>viska lo</jbophrase> is a valid Lojban utterance, and both require
<jbophrase>lo'u</jbophrase> quotation.</para>
<para>Additionally, pro-sumti or pro-bridi in the quoting sentence can refer to words appearing in the quoted sentence when
<jbophrase>lu ... li'u</jbophrase> is used, but not when
<jbophrase>lo'u ... le'u</jbophrase> is used:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-x8XL">
<title>
<anchor xml:id="c19e9d4"/>
</title>
<interlinear-gloss>
- <jbo>la tcarlis. cusku lu le ninmu cu morsi li'u</jbo>
- <gloss>.iku'i ri jmive</gloss>
- <gloss>Charlie says [quote] the woman is-dead [unquote].</gloss>
- <gloss>However, the-last-mentioned is-alive.</gloss>
- <en>Charlie says
- <quote>The woman is dead</quote>, but she is alive.</en>
+ <jbo>la tcarlis. cusku lu le ninmu cu morsi li'u .iku'i ri jmive</jbo>
+ <gloss>Charlie says [quote] the woman is-dead [unquote]. However, the-last-mentioned is-alive.</gloss>
+ <en>Charlie says <quote>The woman is dead</quote>, but she is alive.</en>
</interlinear-gloss>
</example>
<para>In
<xref linkend="example-random-id-x8XL"/>,
<jbophrase>ri</jbophrase> is a pro-sumti which refers to the most recent previous sumti, namely
<jbophrase>le ninmu</jbophrase>. Compare:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-hvhb">
<title>
<anchor xml:id="c19e9d5"/>
</title>
<interlinear-gloss>
- <jbo>la tcarlis. cusku lo'u le ninmu cu morsi le'u</jbo>
- <gloss>.iku'i ri jmive</gloss>
- <gloss>Charlie says [quote] le ninmu cu morsi [unquote].</gloss>
- <gloss>However, the-last-mentioned is-alive.</gloss>
- <en>Charlie says
- <jbophrase>le ninmu cu morsi</jbophrase>, but he is alive.</en>
+ <jbo>la tcarlis. cusku lo'u le ninmu cu morsi le'u .iku'i ri jmive</jbo>
+ <gloss>Charlie says [quote] le ninmu cu morsi [unquote]. However, the-last-mentioned is-alive.</gloss>
+ <en>Charlie says <jbophrase>le ninmu cu morsi</jbophrase>, but he is alive.</en>
</interlinear-gloss>
</example>
<para>In
<xref linkend="example-random-id-hvhb"/>,
<jbophrase>ri</jbophrase> cannot refer to the referent of the alleged sumti
<jbophrase>le ninmu</jbophrase>, because
<jbophrase>le ninmu cu morsi</jbophrase> is a mere uninterpreted sequence of Lojban words. Instead,
<jbophrase>ri</jbophrase> ends up referring to the referent of the sumti
<jbophrase>la tcarlis.</jbophrase>, and so it is Charlie who is alive.</para>
diff --git a/todocbook/21.xml b/todocbook/21.xml
index fa6e496..a8cf4a6 100644
--- a/todocbook/21.xml
+++ b/todocbook/21.xml
@@ -1,38 +1,38 @@
<chapter xml:id="chapter-grammars">
<title>Formal Grammars</title>
- <section xml:id="cll_chapter21-section1">
+ <section xml:id="section-YACC">
<title>YACC Grammar of Lojban</title>
<para>The following two listings constitute the formal grammar of Lojban. The first version is written in the YACC language, which is used to describe parsers, and has been used to create a parser for Lojban texts. This parser is available from the Logical Language Group. The second listing is in Extended Backus-Naur Form (EBNF) and represents the same grammar in a more human-readable form. (In case of discrepancies, the YACC version is official.) There is a cross-reference listing for each format that shows, for each selma'o and rule, which rules refer to it.</para>
<para>/* /*Lojban Machine Grammar, Final Baseline The Lojban Machine Grammardocument is explicitly dedicated to the public domain by its author,The Logical Language Group, Inc.</para>
<para>grammar.300 */</para>
<para>/* The Lojban machine parsing algorithm is a multi-step process. The YACC machine grammar presented here is an amalgam of those steps, concatenated so as to allow YACC to verify the syntactic ambiguity of the grammar. YACC is used to generate a parser for a portion of the grammar, which is LALR1 (the type of grammar that YACC is designed to identify and process successfully), but most of the rest of the grammar must be parsed using some language-coded processing.</para>
<bridgehead>Step 1 - Lexing</bridgehead>
<para>From phonemes, stress, and pause, it is possible to resolve Lojban unambiguously into a stream of words. Any machine processing of speech will have to have some way to deal with ’non-Lojban’ failures of fluent speech, of course. The resolved words can be expressed as a text file using Lojban’s phonetic spelling rules.</para>
<para>The following steps assume that there is the possibility of non-Lojban text within the Lojban text (delimited appropriately). Such non-Lojban text may not be reducible from speech phonetically. However, step 2 allows the filtering of a phonetically transcribed text stream, to recognize such portions of non-Lojban text where properly delimited, without interference with the parsing algorithm.</para>
<bridgehead>Step 2 - Filtering</bridgehead>
<para>From start to end, performing the following filtering and lexing tasks using the given order of precedence in case of conflict:</para>
- <para>a. If the Lojban word “zoi” (selma'o ZOI) is identified, take the following Lojban word (which should be end delimited with a pause for separation from the following non-Lojban text) as an opening delimiter. Treat all text following that delimiter, until that delimiter recurs
+ <para>a. If the Lojban word <jbophrase>zoi</jbophrase> (selma'o ZOI) is identified, take the following Lojban word (which should be end delimited with a pause for separation from the following non-Lojban text) as an opening delimiter. Treat all text following that delimiter, until that delimiter recurs
<emphasis>after a pause</emphasis>, as grammatically a single token (labelled ’
<xref linkend="cll_yacc-699"/>’ in this grammar). There is no need for processing within this text except as necessary to find the closing delimiter.</para>
- <para>b. If the Lojban word “zo” (selma'o ZO) is identified, treat the following Lojban word as a token labelled ’
+ <para>b. If the Lojban word <jbophrase>zo</jbophrase> (selma'o ZO) is identified, treat the following Lojban word as a token labelled ’
<xref linkend="cll_yacc-698"/>’, instead of lexing it by its normal grammatical function.</para>
- <para>c. If the Lojban word “lo'u” (selma'o LOhU) is identified, search for the closing delimiter “le'u” (selma'o LEhU), ignoring any such closing delimiters absorbed by the previous two steps. The text between the delimiters should be treated as the single token ’
+ <para>c. If the Lojban word <jbophrase>lo'u</jbophrase> (selma'o LOhU) is identified, search for the closing delimiter <jbophrase>le'u</jbophrase> (selma'o LEhU), ignoring any such closing delimiters absorbed by the previous two steps. The text between the delimiters should be treated as the single token ’
<xref linkend="cll_yacc-697"/>’.</para>
<para>d. Categorize all remaining words into their Lojban selma'o category, including the various delimiters mentioned in the previous steps. In all steps after step 2, only the selma'o token type is significant for each word.</para>
- <para>e. If the word “si” (selma'o SI) is identified, erase it and the previous word (or token, if the previous text has been condensed into a single token by one of the above rules).</para>
- <para>f. If the word “sa” (selma'o SA) is identified, erase it and all preceding text as far back as necessary to make what follows attach to what precedes. (This rule is hard to formalize and may receive further definition later.)</para>
- <para>g. If the word ’su’ (selma'o SU) is identified, erase it and all preceding text back to and including the first preceding token word which is in one of the selma'o: NIhO, LU, TUhE, and TO. However, if speaker identification is available, a SU shall only erase to the beginning of a speaker’s discourse, unless it occurs at the beginning of a speaker’s discourse. (Thus, if the speaker has said something, two adjacent uses of “su” are required to erase the entire conversation.</para>
+ <para>e. If the word <jbophrase>si</jbophrase> (selma'o SI) is identified, erase it and the previous word (or token, if the previous text has been condensed into a single token by one of the above rules).</para>
+ <para>f. If the word <jbophrase>sa</jbophrase> (selma'o SA) is identified, erase it and all preceding text as far back as necessary to make what follows attach to what precedes. (This rule is hard to formalize and may receive further definition later.)</para>
+ <para>g. If the word ’su’ (selma'o SU) is identified, erase it and all preceding text back to and including the first preceding token word which is in one of the selma'o: NIhO, LU, TUhE, and TO. However, if speaker identification is available, a SU shall only erase to the beginning of a speaker’s discourse, unless it occurs at the beginning of a speaker’s discourse. (Thus, if the speaker has said something, two adjacent uses of <jbophrase>su</jbophrase> are required to erase the entire conversation.</para>
<bridgehead>Step 3 - Termination</bridgehead>
<para>If the text contains a FAhO, treat that as the end-of-text and ignore everything that follows it.</para>
<bridgehead>Step 4 - Absorption of Grammar-Free Tokens</bridgehead>
<para>In a new pass, perform the following absorptions (absorption means that the token is removed from the grammar for processing in following steps, and optionally reinserted, grouped with the absorbing token after parsing is completed).</para>
<para>a. Token sequences of the form any - (ZEI - any) ..., where there may be any number of ZEIs, are merged into a single token of selma'o BRIVLA.</para>
<para>b. Absorb all selma'o BAhE tokens into the following token. If they occur at the end of text, leave them alone (they are errors).</para>
<para>c. Absorb all selma'o BU tokens into the previous token. Relabel the previous token as selma'o BY.</para>
<para>d. If selma'o NAI occurs immediately following any of tokens UI or CAI, absorb the NAI into the previous token.</para>
<para>e. Absorb all members of selma'o DAhO, FUhO, FUhE, UI, Y, and CAI into the previous token. All of these null grammar tokens are permitted following any word of the grammar, without interfering with that word’s grammatical function, or causing any effect on the grammatical interpretation of any other token in the text. Indicators at the beginning of text are explicitly handled by the grammar.</para>
<bridgehead>Step 5 - Insertion of Lexer Lexemes</bridgehead>
@@ -1378,21 +1378,21 @@ the 900 series rules are found in the lexer. */
|
<xref linkend="cll_yacc-470"/>
<xref linkend="cll_yacc-310"/>
<xref linkend="cll_yacc-471"/>
;
/* Entry point for MEX used after LI; no parens needed, but LI now has an
elidable terminator. (This allows us to express the difference between
- “the expression a + b” and “the expression (a + b)” ) */
+ <quote>the expression a + b</quote> and <quote>the expression (a + b)</quote> ) */
/* This rule supports left-grouping infix expressions and reverse Polish
expressions. To handle infix monadic, use a null operand; to handle
infix with more than two operands (whatever that means) use an extra
operator or an array operand. */
<anchor xml:id="y310"/>
<anchor xreflabel="YACC rule #310" xml:id="cll_yacc-310"/> MEX_310 :
@@ -3412,21 +3412,21 @@ the 900 series rules are found in the lexer. */
/* roroi = always and everywhere */
/* roroiku'avi = always here (ku'a = intersection) */
/* puroroi = always in the past
/* paroi = once upon a time (somewhere) */
/* paroiku'avi = once upon a time here */
-/* The following are “Lexer-only rules”, covered by steps 1-4 described
+/* The following are <quote>Lexer-only rules</quote>, covered by steps 1-4 described
at the beginning. The grammar of these constructs is nonexistent,
except possibly in cases where they interact with each other. Even
there, however, the effects are semantic rather than grammatical. Where
it is believed possible that conflicts could exist, the grammar of these
constructs has been put in the above grammar, even though the
lexer/Preparser will actually prevent these from being passed thru to
the parse routine. (Otherwise we have to put unacceptably fancy code in
the PreParser to determine just when these can be passed thru, and when
they can’t.) Constructs in this category include quotes and indicators
as defined above. (The above grammar handles utterance scope
@@ -6947,56 +6947,56 @@ the 900 series rules are found in the lexer. */
<varlistentry>
<term>ZO_quote_435</term>
<listitem>
<para>
<xref linkend="cll_yacc-433"/>
</para>
</listitem>
</varlistentry>
</variablelist>
</section>
- <section xml:id="cll_chapter21-section2">
+ <section xml:id="section-EBNF">
<title>EBNF Grammar of Lojban</title>
<para>Lojban Machine Grammar, EBNF Version, Final Baseline</para>
<para>This EBNF document is explicitly dedicated to the public domain by its author, The Logical Language Group, Inc. Contact that organization at: 2904 Beau Lane, Fairfax VA 22031 USA 703-385-0273 (intl: +1 703 385 0273)</para>
<para>Explanation of notation: All rules have the form:</para>
<para>name
<subscript>number</subscript>= bnf-expression</para>
- <para>which means that the grammatical construct “name” is defined by “bnf-expression”. The number cross-references this grammar with the rule numbers in the YACC grammar. The names are the same as those in the YACC grammar, except that subrules are labeled with A, B, C, ... in the YACC grammar and with 1, 2, 3, ... in this grammar. In addition, rule 971 is “simple_tag” in the YACC grammar but “stag” in this grammar, because of its frequent appearance.</para>
+ <para>which means that the grammatical construct <quote>name</quote> is defined by <quote>bnf-expression</quote>. The number cross-references this grammar with the rule numbers in the YACC grammar. The names are the same as those in the YACC grammar, except that subrules are labeled with A, B, C, ... in the YACC grammar and with 1, 2, 3, ... in this grammar. In addition, rule 971 is <quote>simple_tag</quote> in the YACC grammar but <quote>stag</quote> in this grammar, because of its frequent appearance.</para>
<orderedlist>
<listitem>
<para>Names in lower case are grammatical constructs.</para>
</listitem>
<listitem>
<para>Names in UPPER CASE are selma'o (lexeme) names, and are terminals.</para>
</listitem>
<listitem>
<para>Concatenation is expressed by juxtaposition with no operator symbol.</para>
</listitem>
<listitem>
<para>| represents alternation (choice).</para>
</listitem>
<listitem>
<para>[] represents an optional element.</para>
</listitem>
<listitem>
- <para>& represents and/or (“A & B” is the same as “A | B | A B”).</para>
+ <para>& represents and/or (<quote>A & B</quote> is the same as <quote>A | B | A B</quote>).</para>
</listitem>
<listitem>
- <para>... represents optional repetition of the construct to the left. Left-grouping is implied; right-grouping is shown by explicit self-referential recursion with no “...”</para>
+ <para>... represents optional repetition of the construct to the left. Left-grouping is implied; right-grouping is shown by explicit self-referential recursion with no <quote>...</quote></para>
</listitem>
<listitem>
- <para>() serves to indicate the grouping of the other operators. Otherwise, “...” binds closer than &, which binds closer than |.</para>
+ <para>() serves to indicate the grouping of the other operators. Otherwise, <quote>...</quote> binds closer than &, which binds closer than |.</para>
</listitem>
<listitem>
- <para># is shorthand for “[free ...]”, a construct which appears in many places.</para>
+ <para># is shorthand for <quote>[free ...]</quote>, a construct which appears in many places.</para>
</listitem>
<listitem>
<para>// encloses an elidable terminator, which may be omitted (without change of meaning) if no grammatical ambiguity results.</para>
</listitem>
</orderedlist>
<variablelist>
<varlistentry>
<term>
<anchor xml:id="b0"/>
<anchor xreflabel="BNF rule #0" xml:id="cll_bnf-0"/>
@@ -7888,43 +7888,43 @@ the 900 series rules are found in the lexer. */
<anchor xreflabel="BNF rule #1100" xml:id="cll_bnf-1100"/>
<xref linkend="cll_yacc-1100"/> word
<subscript>1100</subscript>=</term>
<listitem>
<para>[BAhE] any-word [indicators]</para>
</listitem>
</varlistentry>
<varlistentry>
<term>any-word =</term>
<listitem>
- <para>“any single word (no compound cmavo)”</para>
+ <para><quote>any single word (no compound cmavo)</quote></para>
</listitem>
</varlistentry>
<varlistentry>
<term>anything =</term>
<listitem>
- <para>“any text at all, whether Lojban or not”
+ <para><quote>any text at all, whether Lojban or not</quote>
<anchor xml:id="b1101"/>
<anchor xreflabel="BNF rule #1101" xml:id="cll_bnf-1101"/>
<xref linkend="cll_yacc-1101"/></para>
</listitem>
</varlistentry>
<varlistentry>
<term>null
<subscript>1101</subscript>=</term>
<listitem>
<para>any-word SI | utterance SA | text SU</para>
</listitem>
</varlistentry>
</variablelist>
<para>FAhO is a universal terminator and signals the end of parsable input.</para>
</section>
- <section xml:id="cll_chapter21-section3">
+ <section xml:id="section-cross-reference">
<title>EBNF Cross-Reference</title>
<variablelist>
<varlistentry>
<term>A</term>
<listitem>
<para>
<xref linkend="cll_bnf-802"/>
<subscript>802</subscript>
</para>
</listitem>
commit 93899e5b79dbe5bfcad00fc7e0cdaf16d83eaee9
Author: Eitan Postavsky <eitanp32@gmail.com>
Date: Mon Jan 24 19:12:36 2011 -0500
Chapter 18: <cmavo-list>s and section IDs (titles). Invented <rafsi> for <cmavo-list>s.
diff --git a/todocbook/13.xml b/todocbook/13.xml
index 569b2da..765031d 100644
--- a/todocbook/13.xml
+++ b/todocbook/13.xml
@@ -857,21 +857,21 @@
<quote>virtuous</quote> in most cases than their negative counterparts. But these two were felt to be instinctive, distinct, and very powerful emotions that needed to be expressible in a monosyllable when necessary, while their counterparts are less commonly expressed.</para>
<para> <indexterm type="general-imported"><primary>attitudinal scales</primary><secondary>rationale for assignment</secondary></indexterm> (Why the overt bias? Because there are a lot of attitudinals and they will be difficult to learn as an entire set. By aligning our scales arbitrarily, we give the monosyllable
<jbophrase>nai</jbophrase> a useful meaning and make it easier for a novice to recognize at least the positive or negative alignment of an indicator, if not the specific word. Other choices considered were
<quote>random</quote> orientation, which would have unknown biases and be difficult to learn, and orientation based on our guesses as to which scale orientations made the most frequent usages shorter, which would be biased in favor of American perceptions of
<quote>usefulness</quote>. If bias must exist in our indicator set, it might as well be a known bias that eases learning, and in addition might as well favor a harmonious and positive world-view.)</para>
<para> <indexterm type="lojban-word-imported"><primary>CAI selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>naicai</primary></indexterm> <indexterm type="lojban-word-imported"><primary>naisai</primary></indexterm> <indexterm type="lojban-word-imported"><primary>nairu'e</primary></indexterm> <indexterm type="lojban-word-imported"><primary>cu'i</primary></indexterm> <indexterm type="lojban-word-imported"><primary>ru'e</primary></indexterm> <indexterm type="lojban-word-imported"><primary>sai</primary></indexterm> <indexterm type="lojban-word-imported"><primary>cai</primary></indexterm> <indexterm type="general-imported"><primary>attitudinal scale</primary><secondary>seven-position</secondary></indexterm> <indexterm type="general-imported"><primary>emotional scale</primary></indexterm> In fact, though, each emotional scale has seven positions defined, three
<quote>positive</quote> ones (shown below on the left), three
<quote>negative</quote> ones (shown below on the right), and a neutral one indicating that no particular attitude on this scale is felt. The following chart indicates the seven positions of the scale and the associated cmavo. All of these cmavo, except
<jbophrase>nai</jbophrase>, are in selma'o CAI.</para>
- <cmavo-list orient="land">
+ <cmavo-list> <!--orient="land"-->
<cmavo-entry>
<cmavo>cai</cmavo>
<source-gismu>carmi</source-gismu>
</cmavo-entry>
<cmavo-entry>
<cmavo>sai</cmavo>
<source-gismu>tsali</source-gismu>
</cmavo-entry>
<cmavo-entry>
<cmavo>ru'e</cmavo>
diff --git a/todocbook/18.xml b/todocbook/18.xml
index 5da4f58..28823c0 100644
--- a/todocbook/18.xml
+++ b/todocbook/18.xml
@@ -1,13 +1,13 @@
<chapter xml:id="chapter-mekso">
<title>lojbau mekso: Mathematical Expressions in Lojban</title>
- <section xml:id="cll_chapter18-section1">
+ <section xml:id="section-introduction">
<title>Introductory</title>
<para>lojbau mekso (
<quote>Lojbanic mathematical-expression</quote>) is the part of the Lojban language that is tailored for expressing statements of a mathematical character, or for adding numerical information to non-mathematical statements. Its formal design goals include:</para>
<orderedlist>
<listitem>
<para> <indexterm type="general-imported"><primary>mekso goal</primary><secondary>for mathematical writing</secondary></indexterm> <indexterm type="general-imported"><primary>mekso</primary><secondary>design goals</secondary></indexterm> representing all the different forms of expression used by mathematicians in their normal modes of writing, so that a reader can unambiguously read off mathematical text as written with minimal effort and expect a listener to understand it;</para>
</listitem>
<listitem>
<para> <indexterm type="general-imported"><primary>mekso goal</primary><secondary>for common use</secondary></indexterm> <indexterm type="general-imported"><primary>mekso goal</primary><secondary>expandable</secondary></indexterm> providing a vocabulary of commonly used mathematical terms which can readily be expanded to include newly coined words using the full resources of Lojban;</para>
</listitem>
@@ -32,21 +32,21 @@
</example>
<para> <indexterm type="general-imported"><primary>mathematical notation</primary><secondary>and omitted operators</secondary></indexterm> contains omitted multiplication operators, but there are other possible interpretations for the strings
<quote>3x</quote> and
<quote>2y</quote> than as mathematical multiplication. Therefore, the Lojban verbal (spoken and written) form of
<xref linkend="example-random-id-dGcT"/> must not omit the multiplication operators.</para>
<para> <indexterm type="general-imported"><primary>mekso chapter</primary><secondary>completeness</secondary></indexterm> <indexterm type="general-imported"><primary>mekso chapter</primary><secondary>table notation convention</secondary></indexterm> The remainder of this chapter explains (in as much detail as is currently possible) the mekso system. This chapter is by intention complete as regards mekso components, but only suggestive about uses of those components - as of now, there has been no really comprehensive use made of mekso facilities, and many matters must await the test of usage to be fully clarified.</para>
</section>
- <section xml:id="cll_chapter18-section2">
+ <section xml:id="section-numbers">
<title>Lojban numbers</title>
<para>The following cmavo are discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>pa</cmavo>
<selmaho>PA</selmaho>
<description>1</description>
</cmavo-entry>
<cmavo-entry>
<cmavo>re</cmavo>
@@ -95,21 +95,21 @@
</cmavo-entry>
</cmavo-list>
<para> <indexterm type="lojban-word-imported"><primary>PA selma'o</primary></indexterm> <indexterm type="general-imported"><primary>hundred</primary><secondary>expressing as number</secondary></indexterm> <indexterm type="general-imported"><primary>ten</primary><secondary>expressing as number</secondary></indexterm> <indexterm type="general-imported"><primary>numbers</primary><secondary>as compound cmavo</secondary></indexterm> <indexterm type="general-imported"><primary>digits</primary><secondary>cmavo for</secondary></indexterm> <indexterm type="general-imported"><primary>numbers</primary><secondary>expressing simple</secondary></indexterm> The simplest kind of mekso are numbers, which are cmavo or compound cmavo. There are cmavo for each of the 10 decimal digits, and numbers greater than 9 are made by stringing together the cmavo. Some examples:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-LmPr">
<title>
<anchor xml:id="c18e2d1"/>
</title>
<interlinear-gloss>
<jbo>pa re ci</jbo>
<gloss>one two three</gloss>
- <math>123 ignore</math> <!-- okely dokely -->
+ <math>123 ignore</math> <!-- ok -->
<en>one hundred and twenty three</en>
</interlinear-gloss>
</example>
<example role="interlinear-gloss-example" xml:id="example-random-id-TNjj">
<title>
<anchor xml:id="c18e2d2"/>
</title>
<interlinear-gloss>
<jbo>pa no</jbo>
@@ -140,21 +140,21 @@
<jbophrase role="letteral">e</jbophrase>,
<jbophrase role="letteral">i</jbophrase>,
<jbophrase role="letteral">o</jbophrase>,
<jbophrase role="letteral">u</jbophrase> respectively; and the cmavo from 6 to 9 likewise end in the vowels
<jbophrase role="letteral">a</jbophrase>,
<jbophrase role="letteral">e</jbophrase>,
<jbophrase role="letteral">i</jbophrase>, and
<jbophrase role="letteral">o</jbophrase> respectively. None of the digit cmavo begin with the same consonant, to make them easy to tell apart in noisy environments.</para>
</section>
- <section xml:id="cll_chapter18-section3">
+ <section xml:id="section-signs-punctuation">
<title>Signs and numerical punctuation</title>
<para> <indexterm type="lojban-word-imported"><primary>PA selma'o</primary></indexterm> The following cmavo are discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>ma'u</cmavo>
<selmaho>PA</selmaho>
<description>positive sign</description>
</cmavo-entry>
<cmavo-entry>
@@ -205,21 +205,21 @@
</title>
<interlinear-gloss>
<jbo>ni'u pa</jbo>
<gloss>negative-sign 1</gloss>
<math>-1</math>
</interlinear-gloss>
</example>
<para> <indexterm type="lojban-word-imported"><primary>pa</primary></indexterm> <indexterm type="example-imported"><primary>-1</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>signs on numbers</primary><secondary>grammar</secondary></indexterm> Grammatically, the signs are part of the number to which they are attached. It is also possible to use
<jbophrase>ma'u</jbophrase> and
<jbophrase>ni'u</jbophrase> by themselves as numbers; the meaning of these numbers is explained in
- <xref linkend="cll_chapter18-section8"/>.</para>
+ <xref linkend="section-indefinite-numbers"/>.</para>
<para> <indexterm type="general-imported"><primary>decimal point</primary><secondary>as numerical punctuation</secondary></indexterm> <indexterm type="general-imported"><primary>punctuation</primary><secondary>in numbers</secondary></indexterm> <indexterm type="general-imported"><primary>numerical punctuation</primary></indexterm> Various numerical punctuation marks are likewise expressed by cmavo, as illustrated in the following examples:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-Ust4">
<title>
<anchor xml:id="c18e3d2"/>
</title>
<interlinear-gloss>
<jbo>ci pi pa vo pa mu</jbo>
<gloss>three point one four one five</gloss>
<math>3.1415</math>
@@ -332,21 +332,21 @@
<anchor xml:id="c18e3d10"/>
</title>
<interlinear-gloss>
<jbo>pi pa ki'o pa re ki'o pa</jbo>
<gloss>point one comma one two comma one</gloss>
<math>.001012001</math>
</interlinear-gloss>
</example>
</section>
- <section xml:id="cll_chapter18-section4">
+ <section xml:id="section-constants">
<title>Special numbers</title>
<para>The following cmavo are discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>ci'i</cmavo>
<selmaho>PA</selmaho>
<description>infinity</description>
</cmavo-entry>
@@ -449,24 +449,24 @@
<jbo>pa ni'u re</jbo>
<gloss>1 negative-sign 2</gloss>
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>subtraction operator</primary><secondary>contrasted with negative sign</secondary></indexterm> <indexterm type="general-imported"><primary>negative sign</primary><secondary>contrasted with subtraction operator</secondary></indexterm>
<xref linkend="example-random-id-qHya"/> is not
<quote>1 minus 2</quote>, which is represented by a different cmavo sequence altogether. It is a single number which has not been assigned a meaning. There are many such numbers which have no well-defined meaning; they may be used for experimental purposes or for future expansion of the Lojban number system.</para>
<para>It is possible, of course, that some of these
<quote>oddities</quote> do have a meaningful use in some restricted area of mathematics. A mathematician appropriating these structures for specialized use needs to consider whether some other branch of mathematics would use the structure differently.</para>
<para>More information on numbers may be found in
- <xref linkend="cll_chapter18-section8"/> to
- <xref linkend="cll_chapter18-section12"/>.</para>
+ <xref linkend="section-indefinite-numbers"/> to
+ <xref linkend="section-number-questions"/>.</para>
</section>
- <section xml:id="cll_chapter18-section5">
+ <section xml:id="section-simple-infix">
<title>Simple infix expressions and equations</title>
<para>The following cmavo are discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>du</cmavo>
<selmaho>GOhA</selmaho>
<description>equals</description>
</cmavo-entry>
<cmavo-entry>
@@ -639,21 +639,21 @@
<gloss>The-number three plus four times five equals the-number three-five.</gloss>
<math>3 + 4 × 5 = 35</math>
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>default operator precedence</primary><secondary>contrasted with mekso goal</secondary></indexterm> Here we calculate 3 + 4 first, giving 7, and then calculate 7 × 5 second, leading to the result 35. While possessing the advantage of simplicity, this result violates the design goal of matching the standards of mathematics. What can be done?</para>
<para> <indexterm type="general-imported"><primary>operator precedence</primary><secondary>effect of pragmatic convention</secondary></indexterm> <indexterm type="general-imported"><primary>operator precedence</primary><secondary>and mathematical notation</secondary></indexterm> <indexterm type="general-imported"><primary>mathematical notation</primary><secondary>and operator precedence</secondary></indexterm> There are three solutions, all of which will probably be used to some degree. The first solution is to ignore the problem. People will say
<jbophrase>li ci su'i vo pi'i mu</jbophrase> and mean 23 by it, because the notion that multiplication takes precedence over addition is too deeply ingrained to be eradicated by Lojban parsing, which totally ignores semantics. This convention essentially allows semantics to dominate syntax in this one area.</para>
<para> <indexterm type="general-imported"><primary>operator precedence in other languages</primary></indexterm> <indexterm type="general-imported"><primary>operator precedence</primary><secondary>rationale for default left-grouping</secondary></indexterm> (Why not hard-wire the precedences into the grammar, as is done in computer programming languages? Essentially because there are too many operators, known and unknown, with levels of precedence that vary according to usage. The programming language 'C' has 13 levels of precedence, and its list of operators is not even extensible. For Lojban this approach is just not practical. In addition, hard-wired precedence could not be overridden in mathematical systems such as spreadsheets where the conventions are different.)</para>
<para> <indexterm type="general-imported"><primary>operator precedence</primary><secondary>generalized explicit specification</secondary></indexterm> The second solution is to use explicit means to specify the precedence of operators. This approach is fully general, but clumsy, and will be explained in
- <xref linkend="cll_chapter18-section20"/>.</para>
+ <xref linkend="section-explicit-operator-precedence"/>.</para>
<para> <indexterm type="lojban-word-imported"><primary>BIhE selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>bi'e</primary></indexterm> <indexterm type="general-imported"><primary>bi'e</primary><secondary>effect on following operator</secondary></indexterm> <indexterm type="general-imported"><primary>operator precedence</primary><secondary>scope modification with bi'e</secondary></indexterm> The third solution is simple but not very general. When an operator is prefixed with the cmavo
<jbophrase>bi'e</jbophrase> (of selma'o BIhE), it becomes automatically of higher precedence than other operators not so prefixed. Thus,</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-LIUa">
<title>
<anchor xml:id="c18e5d9"/>
</title>
<interlinear-gloss>
<jbo>li ci su'i vo bi'e pi'i mu du li reci</jbo>
@@ -700,21 +700,21 @@
<para>The explicit operator
<jbophrase>pi'i</jbophrase> is required in the Lojban verbal form whereas multiplication is implicit in the symbolic form. Note that
<jbophrase>ve'o</jbophrase> (the right parenthesis) is an elidable terminator: the first use of it in
<xref linkend="example-random-id-wfFV"/> is required, but the second use (marked by square brackets) could be elided. Additionally, the first
<jbophrase>bi'e</jbophrase> (also marked by square brackets) is not necessary to get the proper grouping, but it is included here for symmetry with the other one.</para>
</section>
- <section xml:id="cll_chapter18-section6">
+ <section xml:id="section-forethought">
<title>Forethought operators (Polish notation, functions)</title>
<para>The following cmavo are discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>boi</cmavo>
<selmaho>BOI</selmaho>
<description>numeral/lerfu string terminator</description>
</cmavo-entry>
<cmavo-entry>
<cmavo>va'a</cmavo>
@@ -837,21 +837,21 @@
<para>Again, no parentheses are used. The construct
<jbophrase>ma'o fy.boi</jbophrase> is the equivalent of an operator, and appears in forethought here (although it could also be used as a regular infix operator). In mathematics, letters sometimes mean functions and sometimes mean variables, with only the context to tell which. Lojban chooses to accept the variable interpretation as the default, and uses the special flag
<jbophrase>ma'o</jbophrase> to mark a lerfu string as an operator. The cmavo
<jbophrase>xy.</jbophrase> and
<jbophrase>zy.</jbophrase> are variables, but
<jbophrase>fy.</jbophrase> is an operator (a function) because
<jbophrase>ma'o</jbophrase> marks it as such. The
<jbophrase>boi</jbophrase> is required because otherwise the
<jbophrase>xy.</jbophrase> would look like part of the operator name. (The use of
<jbophrase>ma'o</jbophrase> can be generalized from lerfu strings to any mekso operand: see
- <xref linkend="cll_chapter18-section21"/>.)</para>
+ <xref linkend="section-miscellany"/>.)</para>
<para>When using forethought mekso, the optional marker
<jbophrase>pe'o</jbophrase> may be placed in front of the operator. This usage can help avoid confusion by providing clearly marked
<jbophrase>pe'o</jbophrase> and
<jbophrase>ku'e</jbophrase> pairs to delimit the operand list.
<xref linkend="example-random-id-I0Bm"/> to
<xref linkend="example-random-id-VybU"/>, respectively, with explicit
<jbophrase>pe'o</jbophrase> and
@@ -882,21 +882,21 @@
<jbo>li zy du li pe'o ma'o fy.boi xy. ku'e</jbo>
</interlinear-gloss>
</example>
<para>Note: When using forethought mekso, be sure that the operands really are operands: they cannot contain regular infix expressions unless parenthesized with
<jbophrase>vei</jbophrase> and
<jbophrase>ve'o</jbophrase>. An earlier version of the complex
<xref linkend="example-random-id-k36J"/> came to grief because I forgot this rule.</para>
</section>
- <section xml:id="cll_chapter18-section7">
+ <section xml:id="section-useful-selbri">
<title>Other useful selbri for mekso bridi</title>
<para>So far our examples have been isolated mekso (it is legal to have a bare mekso as a sentence in Lojban) and equation bridi involving
<jbophrase>du</jbophrase>. What about inequalities such as
<quote>x < 5</quote>? The answer is to use a bridi with an appropriate selbri, thus:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-s4TW">
<title>
<anchor xml:id="c18e7d1"/>
</title>
<interlinear-gloss>
<jbo>li xy. mleca li mu</jbo>
@@ -989,21 +989,21 @@
<anchor xml:id="c18e7d3"/>
</title>
<interlinear-gloss>
<jbo>li re su'i re na du li mu</jbo>
<gloss>the-number 2 + 2 is-not equal-to the-number 5.</gloss>
<math>2 + 2 ≠ 5</math>
</interlinear-gloss>
</example>
<para>As usual in Lojban, negated bridi say what is false, and do not say anything about what might be true.</para>
</section>
- <section xml:id="cll_chapter18-section8">
+ <section xml:id="section-indefinite-numbers">
<title>Indefinite numbers</title>
<para>The following cmavo are discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>ro</cmavo>
<selmaho>PA</selmaho>
<description>all</description>
</cmavo-entry>
<cmavo-entry>
<cmavo>so'a</cmavo>
@@ -1262,21 +1262,21 @@
<en>All rats can eat all other rats.</en>
</interlinear-gloss>
</example>
<para> <indexterm type="example-imported"><primary>eat themselves</primary><secondary>example</secondary></indexterm> (The use of
<jbophrase>da'a</jbophrase> means that
<xref linkend="example-random-id-3z2U"/> does not require that all rats can eat themselves, but does allow it. Each rat has one rat it cannot eat, but that one might be some rat other than itself. Context often dictates that
<quote>itself</quote> is, indeed, the
<quote>other</quote> rat.)</para>
<para> <indexterm type="lojban-word-imported"><primary>ni'u</primary></indexterm> <indexterm type="lojban-word-imported"><primary>ma'u</primary></indexterm> <indexterm type="general-imported"><primary>ni'u</primary><secondary>with elided number</secondary></indexterm> <indexterm type="general-imported"><primary>ma'u</primary><secondary>with elided number</secondary></indexterm> As mentioned in
- <xref linkend="cll_chapter18-section3"/>,
+ <xref linkend="section-signs-punctuation"/>,
<jbophrase>ma'u</jbophrase> and
<jbophrase>ni'u</jbophrase> are also legal numbers, and they mean
<quote>some positive number</quote> and
<quote>some negative number</quote> respectively.</para>
<example xml:id="example-random-id-qiaK" role="interlinear-gloss-example">
<title>
<anchor xml:id="c18e8d14"/>
</title>
<interlinear-gloss>
<jbo>li ci vu'u re du li ma'u</jbo>
@@ -1357,21 +1357,21 @@
<jbo>mi speni so'ici prenu</jbo>
<gloss>I am-married-to many/three persons.</gloss>
<en>I am married to three persons (which is
<quote>many</quote> in the circumstances).</en>
</interlinear-gloss>
</example>
<para> <indexterm type="example-imported"><primary>both dogs</primary><secondary>example</secondary></indexterm>
<xref linkend="example-random-id-qIBi"/> assumes a mostly monogamous culture by stating that three is
<quote>many</quote>.</para>
</section>
- <section xml:id="cll_chapter18-section9">
+ <section xml:id="section-approximation">
<title>Approximation and inexact numbers</title>
<para>The following cmavo are discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>ji'i</cmavo>
<selmaho>PA</selmaho>
<description>approximately</description>
</cmavo-entry>
<cmavo-entry>
<cmavo>su'e</cmavo>
@@ -1533,33 +1533,33 @@
<title>
<anchor xml:id="c18e9d10"/>
</title>
<interlinear-gloss>
<jbo>mi catlu su'o prenu</jbo>
<gloss>I look-at at-least [one] person</gloss>
</interlinear-gloss>
</example>
<para>is a meaningful claim.</para>
<para> <indexterm type="lojban-word-imported"><primary>pi</primary></indexterm> <indexterm type="general-imported"><primary>inexact portions with bounds</primary></indexterm> Like the numbers in
- <xref linkend="cll_chapter18-section8"/>, all of these cmavo may be preceded by
+ <xref linkend="section-indefinite-numbers"/>, all of these cmavo may be preceded by
<jbophrase>pi</jbophrase> to make the corresponding quantifiers for part of a whole. For example,
<jbophrase>pisu'o</jbophrase> means
<quote>at least some part of</quote>. The quantifiers
<jbophrase>ro</jbophrase>,
<jbophrase>su'o</jbophrase>,
<jbophrase>piro</jbophrase>, and
<jbophrase>pisu'o</jbophrase> are particularly important in Lojban, as they are implicitly used in the descriptions introduced by the cmavo of selma'o LA and LE, as explained in
<xref linkend="chapter-sumti"/>. Descriptions in general are outside the scope of this chapter.</para>
</section>
- <section xml:id="cll_chapter18-section10">
+ <section xml:id="section-radixen">
<title>Non-decimal and compound bases</title>
<para>The following cmavo are discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>ju'u</cmavo>
<selmaho>VUhU</selmaho>
<description>to the base</description>
</cmavo-entry>
<cmavo-entry>
<cmavo>dau</cmavo>
@@ -1739,21 +1739,21 @@
<title>
<anchor xml:id="c18e10d11"/>
</title>
<interlinear-gloss>
<jbo>dei jufra panopi'epapamoi</jbo>
<gloss>This-utterance is-a-sentence-type-of 10;11th-thing.</gloss>
<en>This is Sentence 10.11.</en>
</interlinear-gloss>
</example>
</section>
- <section xml:id="cll_chapter18-section11">
+ <section xml:id="section-mekso-selbri">
<title>Special mekso selbri</title>
<para>The following cmavo are discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>mei</cmavo>
<selmaho>MOI</selmaho>
<description>cardinal selbri</description>
</cmavo-entry>
<cmavo-entry>
@@ -1830,21 +1830,21 @@
<jbo>mi poi pamei cu cusku dei</jbo>
<gloss>I who am-an-individual express this-sentence.</gloss>
</interlinear-gloss>
</example>
<para>In
<xref linkend="example-random-id-1Pen"/>,
<jbophrase>mi</jbophrase> refers to a mass,
<quote>the mass consisting of me</quote>. Personal pronouns are vague between masses, sets, and individuals.</para>
<para>However, when the number expressed before
<jbophrase role="rafsi">-mei</jbophrase> is an objective indefinite number of the kind explained in
- <xref linkend="cll_chapter18-section8"/>, a slightly different place structure is required:</para>
+ <xref linkend="section-indefinite-numbers"/>, a slightly different place structure is required:</para>
<para> <indexterm type="general-imported"><primary>individuals of set</primary><secondary>expressing measurement standard for indefinites</secondary></indexterm> <indexterm type="general-imported"><primary>set</primary><secondary>expressing measurement standard for indefinites</secondary></indexterm> <indexterm type="general-imported"><primary>mass</primary><secondary>expressing measurement standard for indefinites</secondary></indexterm> <indexterm type="general-imported"><primary>mei</primary><secondary>place structure formed for objective indefinites</secondary></indexterm> FIXME: TAG SPOT</para>
<place-structure>
x1 is a mass formed from a set x2 of n members, one or more of which is/are x3, measured relative to the set x4.
</place-structure>
<para>An example:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-GJsg">
<title>
<anchor xml:id="c18e11d3"/>
</title>
<interlinear-gloss>
@@ -2060,21 +2060,21 @@
</interlinear-gloss>
</example>
<para> <indexterm type="lojban-word-imported"><primary>PA selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>MOI selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>boi</primary></indexterm> <indexterm type="lojban-word-imported"><primary>me'u</primary></indexterm> <indexterm type="example-imported"><primary>snowball's chance</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>boi</primary><secondary>effect on elidability of me'u</secondary></indexterm> <indexterm type="general-imported"><primary>MOI selma'o</primary><secondary>use of boi before</secondary></indexterm> <indexterm type="general-imported"><primary>PA selma'o</primary><secondary>exception on use of boi with MOI</secondary></indexterm> <indexterm type="general-imported"><primary>boi</primary><secondary>exception before MOI</secondary></indexterm> Note: the elidable terminator
<jbophrase>boi</jbophrase> is not used between a number and a member of MOI. As a result, the
<jbophrase>me'u</jbophrase> in
<xref linkend="example-random-id-xaYd"/> could also be replaced by a
<jbophrase>boi</jbophrase>, which would serve the same function of preventing the
<jbophrase>pa</jbophrase> and
<jbophrase>moi</jbophrase> from joining into a compound.</para>
</section>
- <section xml:id="cll_chapter18-section12">
+ <section xml:id="section-number-questions">
<title>Number questions</title>
<para>The following cmavo is discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>xo</cmavo>
<selmaho>PA</selmaho>
<description>number question</description>
</cmavo-entry>
</cmavo-list>
@@ -2114,21 +2114,21 @@
<interlinear-gloss>
<jbo>li remu pi'i xa du li paxono</jbo>
<gloss>The-number 25 times 6 equals the-number 1?0</gloss>
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>number questions</primary><secondary>answers to</secondary></indexterm> <indexterm type="general-imported"><primary>numbers</primary><secondary>as grammatically complete utterances</secondary></indexterm> to which the correct reply would be
<jbophrase>mu</jbophrase>, or 5. The ability to utter bare numbers as grammatical Lojban sentences is primarily intended for giving answers to
<jbophrase>xo</jbophrase> questions. (Another use, obviously, is for counting off physical objects one by one.)</para>
</section>
- <section xml:id="cll_chapter18-section13">
+ <section xml:id="section-subscripts">
<title>Subscripts</title>
<para>The following cmavo is discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>xi</cmavo>
<selmaho>XI</selmaho>
<description>subscript</description>
</cmavo-entry>
</cmavo-list>
<para> <indexterm type="general-imported"><primary>subscripts</primary><secondary>external grammar of</secondary></indexterm> Subscripting is a general Lojban feature, not used only in mekso; there are many things that can logically be subscripted, and grammatically a subscript is a free modifier, usable almost anywhere. In particular, of course, mekso variables (lerfu strings) can be subscripted:</para>
@@ -2186,21 +2186,21 @@
<interlinear-gloss>
<jbo>xy.boi xi by.boi xi vo</jbo>
<math>x<subscript>b<subscript>4</subscript></subscript></math>
</interlinear-gloss>
</example>
<para>See
<xref linkend="example-random-id-eMsd"/> for the standard method of specifying multiple subscripts on a single object.</para>
<para>More information on the uses of subscripts may be found in
<xref linkend="chapter-structure"/>.</para>
</section>
- <section xml:id="cll_chapter18-section14">
+ <section xml:id="section-infix-again">
<title>Infix operators revisited</title>
<para>The following cmavo are discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>tu'o</cmavo>
<selmaho>PA</selmaho>
<description>null operand</description>
</cmavo-entry>
@@ -2280,21 +2280,21 @@
<title>
<anchor xml:id="c18e14d4"/>
</title>
<interlinear-gloss>
<jbo>papano bi'eju'u re gei pipanopano bi'eju'u re ge'a re</jbo>
<gloss>(one-one-zero base 2) scientific (point-one-zero-one-zero base 2) with-base 2</gloss>
<math>.1010</math>
</interlinear-gloss>
</example>
</section>
- <section xml:id="cll_chapter18-section15">
+ <section xml:id="section-vectors-matrices">
<title>Vectors and matrices</title>
<para>The following cmavo are discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>jo'i</cmavo>
<selmaho>JOhI</selmaho>
<description>start vector</description>
</cmavo-entry>
<cmavo-entry>
<cmavo>te'u</cmavo>
@@ -2374,37 +2374,37 @@
<jbophrase>pi'a</jbophrase> or
<jbophrase>sa'i</jbophrase> with an appropriate subscript numbering the dimension. When subscripted, there is no difference between
<jbophrase>pi'a</jbophrase> and
<jbophrase>sa'i</jbophrase>.</para>
</section>
- <section xml:id="cll_chapter18-section16">
+ <section xml:id="section-reverse-polish-notation">
<title>Reverse Polish notation</title>
<para>The following cmavo is discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>fu'a</cmavo>
<selmaho>FUhA</selmaho>
<description>reverse Polish flag</description>
</cmavo-entry>
</cmavo-list>
<para> <indexterm type="general-imported"><primary>RP</primary><secondary>as abbreviation for reverse Polish notation</secondary></indexterm> So far, the Lojban notational conventions have mapped fairly familiar kinds of mathematical discourse. The use of forethought operators may have seemed odd when applied to
<quote>+</quote>, but when applied to
<quote>f</quote> they appear as the usual functional notation. Now comes a sharp break. Reverse Polish (RP) notation represents something completely different; even mathematicians don't use it much. (The only common uses of RP, in fact, are in some kinds of calculators and in the implementation of some programming languages.)</para>
<para> <indexterm type="lojban-word-imported"><primary>fu'a</primary></indexterm> <indexterm type="general-imported"><primary>reverse Polish notation</primary><secondary>terminator</secondary></indexterm> <indexterm type="general-imported"><primary>reverse Polish notation</primary><secondary>marker</secondary></indexterm> <indexterm type="general-imported"><primary>reverse Polish notation</primary><secondary>use of parentheses in</secondary></indexterm> <indexterm type="general-imported"><primary>reverse Polish notation</primary><secondary>definition</secondary></indexterm> In RP notation, the operator follows the operands. (Polish notation, where the operator precedes its operands, is another name for forethought mekso of the kind explained in
- <xref linkend="cll_chapter18-section6"/>.) The number of operands per operator is always fixed. No parentheses are required or permitted. In Lojban, RP notation is always explicitly marked by a
+ <xref linkend="section-forethought"/>.) The number of operands per operator is always fixed. No parentheses are required or permitted. In Lojban, RP notation is always explicitly marked by a
<jbophrase>fu'a</jbophrase> at the beginning of the expression; there is no terminator. Here is a simple example:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-V4xe">
<title>
<anchor xml:id="c18e16d1"/>
</title>
<interlinear-gloss>
<jbo>li fu'a reboi ci su'i du li mu</jbo>
<gloss>the-number (RP!) two, three, plus equals the-number five.</gloss>
@@ -2469,21 +2469,21 @@
<title>
<anchor xml:id="c18e16d4"/>
</title>
<interlinear-gloss>
<jbo>li cinoki'oki'o du li fu'a biboi ciboi panoboi ge'a gei</jbo>
<gloss>The-number 30-comma-comma equals the-number (RP!) 8, (3, 10, null-op), exponential-notation.</gloss>
<math>30,000,000 = 3 × 10</math>
</interlinear-gloss>
</example>
</section>
- <section xml:id="cll_chapter18-section17">
+ <section xml:id="section-connectives-within-mekso">
<title>Logical and non-logical connectives within mekso</title>
<para>The following cmavo are discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>.abu</cmavo>
<selmaho>BY</selmaho>
<description>letter <quote>a</quote></description>
</cmavo-entry>
<cmavo-entry>
<cmavo>by</cmavo>
@@ -2684,21 +2684,21 @@
<jbo>xy. xi vei by. ce'o dy. [ve'o]</jbo>
<gloss>
<quote>x</quote> sub (
<quote>b</quote> sequence
<quote>d</quote>)</gloss>
<math>x<subscript>b,d</subscript></math>
</interlinear-gloss>
</example>
</section>
- <section xml:id="cll_chapter18-section18">
+ <section xml:id="section-lojban-within-mekso">
<title>Using Lojban resources within mekso</title>
<para>The following cmavo are discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>na'u</cmavo>
<selmaho>NAhU</selmaho>
<description>selbri to operator</description>
</cmavo-entry>
<cmavo-entry>
<cmavo>ni'e</cmavo>
@@ -2788,21 +2788,21 @@
</title>
<interlinear-gloss>
<jbo>mi viska vei mo'e lo'e lanzu ve'o cinfo</jbo>
<gloss>I see ( the-typical family )-number-of lions.</gloss>
<en>I see a pride of lions.</en>
</interlinear-gloss>
</example>
</section>
- <section xml:id="cll_chapter18-section19">
+ <section xml:id="section-other-mekso-uses">
<title>Other uses of mekso</title>
<para>The following cmavo are discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>me'o</cmavo>
<selmaho>LI</selmaho>
<description>the mekso</description>
</cmavo-entry>
<cmavo-entry>
<cmavo>nu'a</cmavo>
@@ -2994,41 +2994,41 @@
<para> <indexterm type="lojban-word-imported"><primary>roi</primary></indexterm> <indexterm type="example-imported"><primary>once</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>tense</primary><secondary>numerical</secondary></indexterm> A numerical tense can be created by suffixing a digit string with
<jbophrase>roi</jbophrase>. This usage generates tenses corresponding to English
<quote>once</quote>,
<quote>twice</quote>, and so on. This topic belongs to a detailed discussion of Lojban tenses, and is explained further in
<xref linkend="chapter-tenses"/>.</para>
<para> <indexterm type="lojban-word-imported"><primary>boi</primary></indexterm> <indexterm type="general-imported"><primary>numerical tenses</primary><secondary>effect on use of boi</secondary></indexterm> <indexterm type="general-imported"><primary>boi</primary><secondary>exception before ROI</secondary></indexterm> <indexterm type="general-imported"><primary>boi</primary><secondary>exception before MAI</secondary></indexterm> <indexterm type="general-imported"><primary>MAI selma'o</primary><secondary>exception on use of boi before</secondary></indexterm> <indexterm type="general-imported"><primary>ROI selma'o</primary><secondary>exception on use of boi before</secondary></indexterm> Note: the elidable terminator
<jbophrase>boi</jbophrase> is not used between a number and a member of MAI or ROI.</para>
</section>
- <section xml:id="cll_chapter18-section20">
+ <section xml:id="section-explicit-operator-precedence">
<title>Explicit operator precedence</title>
<para>As mentioned earlier, Lojban does provide a way for the precedences of operators to be explicitly declared, although current parsers do not understand these declarations.</para>
<para> <indexterm type="lojban-word-imported"><primary>SEI selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>ti'o</primary></indexterm> The declaration is made in the form of a metalinguistic comment using
<jbophrase>ti'o</jbophrase>, a member of selma'o SEI.
<jbophrase>sei</jbophrase>, the other member of SEI, is used to insert metalinguistic comments on a bridi which give information about the discourse which the bridi comprises. The format of a
<jbophrase>ti'o</jbophrase> declaration has not been formally established, but presumably would take the form of mentioning a mekso operator and then giving it either an absolute numerical precedence on some pre-established scale, or else specifying relative precedences between new operators and existing operators.</para>
<para> <indexterm type="general-imported"><primary>operator precedence</primary><secondary>plans for future</secondary></indexterm> In future, we hope to create an improved machine parser that can understand declarations of the precedences of simple operators belonging to selma'o VUhU. Originally, all operators would have the same precedence. Declarations would have the effect of raising the specified cmavo of VUhU to higher precedence levels. Complex operators formed with
<jbophrase>na'u</jbophrase>,
<jbophrase>ni'e</jbophrase>, or
<jbophrase>ma'o</jbophrase> would remain at the standard low precedence; declarations with respect to them are for future implementation efforts. It is probable that such a parser would have a set of
<quote>commonly assumed precedences</quote> built into it (selectable by a special
<jbophrase>ti'o</jbophrase> declaration) that would match mathematical intuition: times higher than plus, and so on.</para>
</section>
- <section xml:id="cll_chapter18-section21">
+ <section xml:id="section-miscellany">
<title>Miscellany</title>
<para>A few other points:</para>
<para> <indexterm type="lojban-word-imported"><primary>se</primary></indexterm> <indexterm type="general-imported"><primary>se</primary><secondary>use with operators</secondary></indexterm> <indexterm type="general-imported"><primary>conversion</primary><secondary>of operator places</secondary></indexterm>
<jbophrase>se</jbophrase> can be used to convert an operator as if it were a selbri, so that its arguments are exchanged. For example:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-NwYJ">
<title>
<anchor xml:id="c18e21d1"/>
</title>
<interlinear-gloss>
<jbo>li ci se vu'u vo du li pa</jbo>
@@ -3143,21 +3143,21 @@
<para> <indexterm type="lojban-word-imported"><primary>te'u</primary></indexterm> <indexterm type="lojban-word-imported"><primary>ma'o</primary></indexterm> <indexterm type="general-imported"><primary>operator</primary><secondary>converting from operand</secondary></indexterm> <indexterm type="general-imported"><primary>operand</primary><secondary>converting into operator</secondary></indexterm> <indexterm type="general-imported"><primary>conversion of operand into operator</primary></indexterm> To change an operand into an operator, we use the cmavo
<jbophrase>ma'o</jbophrase>, already introduced as a means of changing a lerfu string such as
<jbophrase>fy.</jbophrase> into an operator. In fact,
<jbophrase>ma'o</jbophrase> can be followed by any mekso operand, using the elidable terminator
<jbophrase>te'u</jbophrase> if necessary.</para>
<para> <indexterm type="general-imported"><primary>ma'o</primary><secondary>potential ambiguity caveat</secondary></indexterm> There is a potential semantic ambiguity in
<jbophrase>ma'o fy. [te'u]</jbophrase> if
<jbophrase>fy.</jbophrase> is already in use as a variable: it comes to mean
<quote>the function whose value is always ‘f'</quote>. However, mathematicians do not normally use the same lerfu words or strings as both functions and variables, so this case should not arise in practice.</para>
</section>
- <section xml:id="cll_chapter18-section22">
+ <section xml:id="section-four-score-and-seven">
<title>Four score and seven: a mekso problem</title>
<para> <indexterm type="example-imported"><primary>Four score and seven</primary><secondary>example</secondary></indexterm> <indexterm type="example-imported"><primary>Gettysburg Address</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>mekso</primary><secondary>and literary translation</secondary></indexterm> Abraham Lincoln's Gettysburg Address begins with the words
<quote>Four score and seven years ago</quote>. This section exhibits several different ways of saying the number
<quote>four score and seven</quote>. (A
<quote>score</quote>, for those not familiar with the term, is 20; it is analogous to a
<quote>dozen</quote> for 12.) The trivial way:</para>
@@ -3221,21 +3221,21 @@
<gloss>four ; seven base 20</gloss>
<math>47</math>
</interlinear-gloss>
</example>
<para>Overall,
<xref linkend="example-random-id-iwba"/> probably captures the flavor of the English best.
<xref linkend="example-random-id-DzMH"/> and
<xref linkend="example-random-id-HNyL"/> are too simple, and
<xref linkend="example-random-id-2C3I"/> is too tricky. Nevertheless, all four examples are good Lojban. Pedagogically, these examples illustrate the richness of lojbau mekso: anything that can be said at all, can probably be said in more than one way.</para>
</section>
- <section xml:id="cll_chapter18-section23">
+ <section xml:id="section-selmaho-summary">
<title>mekso selma'o summary</title>
<para>Except as noted, each selma'o has only one cmavo.</para>
<place-structure>
<cmavo-entry>
<selmaho>BOI</selmaho>
<description>elidable terminator for numerals and lerfu strings</description>
</cmavo-entry>
<cmavo-entry>
<selmaho>BY</selmaho>
<description>lerfu for variables and functions (see <xref linkend="chapter-letterals"/>)</description>
@@ -3252,420 +3252,443 @@
<cmavo-entry>
<selmaho>JOhI</selmaho>
<description>array flag</description>
</cmavo-entry>
<cmavo-entry>
<selmaho>KUhE</selmaho>
<description>elidable terminator for forethought mekso</description>
</cmavo-entry>
<cmavo-entry>
<selmaho>LI</selmaho>
- <description>mekso articles (li and me'o)</description>
+ <description>mekso articles (<jbophrase>li</jbophrase> and <jbophrase>me'o</jbophrase>)</description>
</cmavo-entry>
<cmavo-entry>
<selmaho>MAhO</selmaho>
<description>make operand into operator</description>
</cmavo-entry>
<cmavo-entry>
<selmaho>MOI</selmaho>
- <description>creates mekso selbri (moi, mei, si'e, and cu'o, see <xref linkend="cll_chapter18-section11"/>)</description>
+ <description>creates mekso selbri (<jbophrase>moi</jbophrase>, <jbophrase>mei</jbophrase>, <jbophrase>si'e</jbophrase>, and <jbophrase>cu'o</jbophrase>, see <xref linkend="section-mekso-selbri"/>)</description>
</cmavo-entry>
<cmavo-entry>
<selmaho>MOhE</selmaho>
<description>make sumti into operand</description>
</cmavo-entry>
<cmavo-entry>
<selmaho>NAhU</selmaho>
<description>make selbri into operator</description>
</cmavo-entry>
<cmavo-entry>
<selmaho>NIhE</selmaho>
<description>make selbri into operand</description>
</cmavo-entry>
<cmavo-entry>
<selmaho>NUhA</selmaho>
<description>make operator into selbri</description>
</cmavo-entry>
<cmavo-entry>
<selmaho>PA</selmaho>
- <description>numbers (see <xref linkend="cll_chapter18-section25"/>)</description>
+ <description>numbers (see <xref linkend="section-pa"/>)</description>
</cmavo-entry>
<cmavo-entry>
<selmaho>PEhO</selmaho>
<description>optional forethought mekso marker</description>
</cmavo-entry>
<cmavo-entry>
<selmaho>TEhU</selmaho>
<description>elidable terminator for NAhU, NIhE, MOhE, MAhO, and JOhI</description>
</cmavo-entry>
<cmavo-entry>
<selmaho>VEI</selmaho>
<description>left parenthesis</description>
</cmavo-entry>
<cmavo-entry>
<selmaho>VEhO</selmaho>
<description>right parenthesis</description>
</cmavo-entry>
<cmavo-entry>
<selmaho>VUhU</selmaho>
- <description>operators (see <xref linkend="cll_chapter18-section24"/>)</description>
+ <description>operators (see <xref linkend="section-vuhu"/>)</description>
</cmavo-entry>
<cmavo-entry>
<selmaho>XI</selmaho>
<description>subscript flag</description>
</cmavo-entry>
</place-structure>
</section>
- <section xml:id="cll_chapter18-section24">
+ <section xml:id="section-vuhu">
<title>Complete table of VUhU cmavo, with operand structures</title>
<para>The operand structures specify what various operands (labeled a, b, c, ...) mean. The implied context is forethought, since only forethought operators can have a variable number of operands; however, the same rules apply to infix and RP uses of VUhU.</para>
<para> <indexterm type="general-imported"><primary>operators</primary><secondary>list of simple</secondary></indexterm> FIXME: TAG SPOT</para>
+ <!-- FIXME: use actual equations for integral, derivative, etc. -->
<place-structure>
<cmavo-entry>
<selmaho>su'i</selmaho>
- <description>plus </description>
+ <description>plus</description>
<math-description><inlineequation><mathphrase>(((a + b) + c) + ...)</mathphrase></inlineequation></math-description>
</cmavo-entry>
<cmavo-entry>
<selmaho>pi'i</selmaho>
- <description>times </description>
+ <description>times</description>
<math-description><inlineequation><mathphrase>(((a × b) × c) × ...)</mathphrase></inlineequation></math-description>
</cmavo-entry>
<cmavo-entry>
<selmaho>vu'u</selmaho>
- <description>minus </description>
+ <description>minus</description>
<math-description><inlineequation><mathphrase>(((a − b) − c) − ...)</mathphrase></inlineequation></math-description>
</cmavo-entry>
<cmavo-entry>
<selmaho>fe'i</selmaho>
- <description>divided by </description>
+ <description>divided by</description>
<math-description><inlineequation><mathphrase>(((a / b) / c) / ...)</mathphrase></inlineequation></math-description>
</cmavo-entry>
<cmavo-entry>
<selmaho>ju'u</selmaho>
- <description>number base </description>
+ <description>number base</description>
<math-description>numeral string <varname>a</varname> interpreted in the base <varname>b</varname></math-description>
</cmavo-entry>
<cmavo-entry>
<selmaho>pa'i</selmaho>
- <description>ratio </description>
- <math-description>the ratio of a to b, a:b</math-description>
+ <description>ratio</description>
+ <math-description>the ratio of <varname>a</varname> to <varname>b</varname> a:b</math-description>
</cmavo-entry>
<cmavo-entry>
<selmaho>fa'i</selmaho>
- <description>reciprocal of/multiplicative inverse </description>
- <math-description>1 / <varname>a</varname></math-description>
+ <description>reciprocal of/multiplicative inverse</description>
+ <math-description><inlineequation><mathphrase>1 / a</mathphrase></inlineequation></math-description>
</cmavo-entry>
<cmavo-entry>
<selmaho>gei</selmaho>
- <description>scientific notation </description>
+ <description>scientific notation</description>
<math-description>b × (c [default 10] to the <varname>a</varname> power)</math-description>
</cmavo-entry>
<cmavo-entry>
<selmaho>ge'a</selmaho>
- <description>null operator </description>
+ <description>null operator</description>
<math-description>(no operands)</math-description>
</cmavo-entry>
<cmavo-entry>
<selmaho>de'o</selmaho>
- <description>logarithm </description>
+ <description>logarithm</description>
<math-description>log <varname>a</varname> to base <varname>b</varname> (default 10 or <varname>e</varname> as appropriate)</math-description>
</cmavo-entry>
<cmavo-entry>
<selmaho>te'a</selmaho>
- <description>to the power/exponential </description>
+ <description>to the power/exponential</description>
<math-description><varname>a</varname> to the <varname>b</varname> power</math-description>
</cmavo-entry>
<cmavo-entry>
<selmaho>fe'a</selmaho>
- <description>nth root of/inverse power </description>
+ <description>nth root of/inverse power</description>
<math-description>b<superscript>th</superscript> root of a (default square root: b = 2)</math-description>
</cmavo-entry>
<cmavo-entry>
<selmaho>cu'a</selmaho>
- <description>absolute value/norm </description>
- <math-description>| a |</math-description>
+ <description>absolute value/norm</description>
+ <math-description><inlineequation><mathphrase>| a |</mathphrase></inlineequation></math-description>
</cmavo-entry>
<cmavo-entry>
<selmaho>ne'o</selmaho>
- <description>factorial </description>
+ <description>factorial</description>
<math-description>a!</math-description>
</cmavo-entry>
<cmavo-entry>
<selmaho>pi'a</selmaho>
- <description>matrix row vector combiner </description>
+ <description>matrix row vector combiner</description>
<math-description>(all operands are row vectors)</math-description>
</cmavo-entry>
<cmavo-entry>
<selmaho>sa'i</selmaho>
- <description>matrix column vector combiner </description>
+ <description>matrix column vector combiner</description>
<math-description>(all operands are column vectors)</math-description>
</cmavo-entry>
<cmavo-entry>
<selmaho>ri'o</selmaho>
- <description>integral </description>
- <math-description>integral of a with respect to b over range c</math-description>
+ <description>integral</description>
+ <math-description>integral of a with respect to b over range c</math-description> <!-- FIXME: ? -->
</cmavo-entry>
<cmavo-entry>
<selmaho>sa'o</selmaho>
- <description>derivative </description>
+ <description>derivative</description>
<math-description>derivative of a with respect to b of degree c (default 1)</math-description>
</cmavo-entry>
<cmavo-entry>
<selmaho>fu'u</selmaho>
- <description>non-specific operator </description>
+ <description>non-specific operator</description>
<math-description>(variable)</math-description>
</cmavo-entry>
<cmavo-entry>
<selmaho>si'i</selmaho>
- <description>sigma (Σ) summation </description>
+ <description>sigma (Σ) summation</description>
<math-description>summation of a using variable b over range c</math-description>
</cmavo-entry>
<cmavo-entry>
<selmaho>va'a</selmaho>
- <description>negation of/additive inverse </description>
+ <description>negation of/additive inverse</description>
<math-description>-a</math-description>
</cmavo-entry>
<cmavo-entry>
<selmaho>re'a</selmaho>
- <description>matrix transpose/dual </description>
- <math-description>a<superscript>*</superscript></math-description>
+ <description>matrix transpose/dual</description>
+ <math-description><inlineequation><mathphrase>a<superscript>*</superscript></mathphrase></inlineequation></math-description>
</cmavo-entry>
</place-structure>
</section>
- <section xml:id="cll_chapter18-section25">
+ <section xml:id="section-pa">
<title>Complete table of PA cmavo: digits, punctuation, and other numbers.</title>
<itemizedlist>
<listitem>
<para> <indexterm type="general-imported"><primary>digits</primary><secondary>list of decimal</secondary></indexterm> Decimal digits:</para>
- <informaltable orient="land">
- <tgroup cols="10">
- <colspec colnum="1" colname="col1"/>
- <colspec colnum="2" colname="col2"/>
- <colspec colnum="3" colname="col3"/>
- <colspec colnum="4" colname="col4"/>
- <colspec colnum="5" colname="col5"/>
- <colspec colnum="6" colname="col6"/>
- <colspec colnum="7" colname="col7"/>
- <colspec colnum="8" colname="col8"/>
- <colspec colnum="9" colname="col9"/>
- <colspec colnum="10" colname="col10"/>
- <thead>
- <row>
- <entry/>
- <entry/>
- <entry>rafsi</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry><jbophrase>no</jbophrase></entry>
- <entry><jbophrase>pa</jbophrase></entry>
- <entry><jbophrase>re</jbophrase></entry>
- <entry><jbophrase>ci</jbophrase></entry>
- <entry><jbophrase>vo</jbophrase></entry>
- <entry><jbophrase>mu</jbophrase></entry>
- <entry><jbophrase>xa</jbophrase></entry>
- <entry><jbophrase>ze</jbophrase></entry>
- <entry><jbophrase>bi</jbophrase></entry>
- <entry><jbophrase>so</jbophrase></entry>
- </row>
- <row>
- <entry>0</entry>
- <entry>1</entry>
- <entry>2</entry>
- <entry>3</entry>
- <entry>4</entry>
- <entry>5</entry>
- <entry>6</entry>
- <entry>7</entry>
- <entry>8</entry>
- <entry>9</entry>
- </row>
- <row>
- <entry><jbophrase role="rafsi">non</jbophrase></entry>
- <entry><jbophrase role="rafsi">pav</jbophrase></entry>
- <entry><jbophrase role="rafsi">rel</jbophrase></entry>
- <entry><jbophrase role="rafsi">cib</jbophrase></entry>
- <entry><jbophrase role="rafsi">von</jbophrase></entry>
- <entry><jbophrase role="rafsi">mum</jbophrase></entry>
- <entry><jbophrase role="rafsi">xav</jbophrase></entry>
- <entry><jbophrase role="rafsi">zel</jbophrase></entry>
- <entry><jbophrase role="rafsi">biv</jbophrase></entry>
- <entry><jbophrase role="rafsi">soz</jbophrase></entry>
- </row>
- </tbody>
- </tgroup>
- </informaltable>
+ <cmavo-list>
+ <cmavo-entry>
+ <cmavo><jbophrase>no</jbophrase></cmavo>
+ <rafsi><jbophrase role="rafsi">non</jbophrase></rafsi>
+ <math-description>0</math-description>
+ </cmavo-entry>
+ <cmavo-entry>
+ <cmavo><jbophrase>pa</jbophrase></cmavo>
+ <rafsi><jbophrase role="rafsi">pav</jbophrase></rafsi>
+ <math-description>1</math-description>
+ </cmavo-entry>
+ <cmavo-entry>
+ <cmavo><jbophrase>re</jbophrase></cmavo>
+ <rafsi><jbophrase role="rafsi">rel</jbophrase></rafsi>
+ <math-description>2</math-description>
+ </cmavo-entry>
+ <cmavo-entry>
+ <cmavo><jbophrase>ci</jbophrase></cmavo>
+ <rafsi><jbophrase role="rafsi">cib</jbophrase></rafsi>
+ <math-description>3</math-description>
+ </cmavo-entry>
+ <cmavo-entry>
+ <cmavo><jbophrase>vo</jbophrase></cmavo>
+ <rafsi><jbophrase role="rafsi">von</jbophrase></rafsi>
+ <math-description>4</math-description>
+ </cmavo-entry>
+ <cmavo-entry>
+ <cmavo><jbophrase>mu</jbophrase></cmavo>
+ <rafsi><jbophrase role="rafsi">mum</jbophrase></rafsi>
+ <math-description>5</math-description>
+ </cmavo-entry>
+ <cmavo-entry>
+ <cmavo><jbophrase>xa</jbophrase></cmavo>
+ <rafsi><jbophrase role="rafsi">xav</jbophrase></rafsi>
+ <math-description>6</math-description>
+ </cmavo-entry>
+ <cmavo-entry>
+ <cmavo><jbophrase>ze</jbophrase></cmavo>
+ <rafsi><jbophrase role="rafsi">zel</jbophrase></rafsi>
+ <math-description>7</math-description>
+ </cmavo-entry>
+ <cmavo-entry>
+ <cmavo><jbophrase>bi</jbophrase></cmavo>
+ <rafsi><jbophrase role="rafsi">biv</jbophrase></rafsi>
+ <math-description>8</math-description>
+ </cmavo-entry>
+ <cmavo-entry>
+ <cmavo><jbophrase>so</jbophrase></cmavo>
+ <rafsi><jbophrase role="rafsi">soz</jbophrase></rafsi>
+ <math-description>9</math-description>
+ </cmavo-entry>
+ </cmavo-list>
</listitem>
<listitem>
<para> <indexterm type="general-imported"><primary>digits</primary><secondary>list of hexadecimal</secondary></indexterm> Hexadecimal digits:</para>
- <informaltable orient="land">
- <tgroup cols="6">
- <colspec colnum="1" colname="col1"/>
- <colspec colnum="2" colname="col2"/>
- <colspec colnum="3" colname="col3"/>
- <colspec colnum="4" colname="col4"/>
- <colspec colnum="5" colname="col5"/>
- <colspec colnum="6" colname="col6"/>
- <tbody>
- <row>
- <entry><jbophrase>dau</jbophrase></entry>
- <entry><jbophrase>fei</jbophrase></entry>
- <entry><jbophrase>gai</jbophrase></entry>
- <entry><jbophrase>jau</jbophrase></entry>
- <entry><jbophrase>rei</jbophrase></entry>
- <entry><jbophrase>vai</jbophrase></entry>
- </row>
- <row>
- <entry>A/10</entry>
- <entry>B/11</entry>
- <entry>C/12</entry>
- <entry>D/13</entry>
- <entry>E/14</entry>
- <entry>F/15</entry>
- </row>
- </tbody>
- </tgroup>
- </informaltable>
+ <cmavo-list>
+ <cmavo-entry>
+ <cmavo><jbophrase>dau</jbophrase></cmavo>
+ <math-description>A/10</math-description>
+ </cmavo-entry><cmavo-entry>
+ <cmavo><jbophrase>fei</jbophrase></cmavo>
+ <math-description>B/11</math-description>
+ </cmavo-entry><cmavo-entry>
+ <cmavo><jbophrase>gai</jbophrase></cmavo>
+ <math-description>C/12</math-description>
+ </cmavo-entry><cmavo-entry>
+ <cmavo><jbophrase>jau</jbophrase></cmavo>
+ <math-description>D/13</math-description>
+ </cmavo-entry><cmavo-entry>
+ <cmavo><jbophrase>rei</jbophrase></cmavo>
+ <math-description>E/14</math-description>
+ </cmavo-entry><cmavo-entry>
+ <cmavo><jbophrase>vai</jbophrase></cmavo>
+ <math-description>F/15</math-description>
+ </cmavo-entry>
+ </cmavo-list>
</listitem>
<listitem>
<para> <indexterm type="general-imported"><primary>numbers</primary><secondary>list of special</secondary></indexterm> Special numbers:</para>
- <informaltable orient="land">
- <tgroup cols="3">
- <colspec colnum="1" colname="col1"/>
- <colspec colnum="2" colname="col2"/>
- <colspec colnum="3" colname="col3"/>
- <colspec colnum="4" colname="col4"/>
- <tbody>
- <row>
- <entry>pai</entry>
- <entry>ka'o</entry>
- <entry>te'o</entry>
- <entry>ci'i</entry>
- </row>
- <row>
- <entry>π</entry>
- <entry>imaginary i</entry>
- <entry>exponential e</entry>
- <entry>infinity (∞)</entry>
- </row>
- </tbody>
- </tgroup>
- </informaltable>
+ <cmavo-list>
+ <cmavo-entry>
+ <cmavo>pai</cmavo>
+ <math-description>π</math-description>
+ </cmavo-entry>
+ <cmavo-entry>
+ <cmavo>ka'o</cmavo>
+ <math-description>imaginary i</math-description>
+ </cmavo-entry>
+ <cmavo-entry>
+ <cmavo>te'o</cmavo>
+ <math-description>exponential e</math-description>
+ </cmavo-entry>
+ <cmavo-entry>
+ <cmavo>ci'i</cmavo>
+ <math-description>infinity (∞)</math-description>
+ </cmavo-entry>
+ </cmavo-list>
</listitem>
<listitem>
<para> <indexterm type="general-imported"><primary>punctuation</primary><secondary>list of numerical</secondary></indexterm> Number punctuation:</para>
- <informaltable orient="land">
- <tgroup cols="3">
- <colspec colnum="1" colname="col1"/>
- <colspec colnum="2" colname="col2"/>
- <colspec colnum="3" colname="col3"/>
- <tbody>
- <row>
- <entry>pi</entry>
- <entry>ce'i</entry>
- <entry>fi'u</entry>
- </row>
- <row>
- <entry>decimal point</entry>
- <entry>percentage</entry>
- <entry>fraction (not division)</entry>
- </row>
- <row>
- <entry>piz</entry>
- <entry>cez</entry>
- <entry>fi'u (from frinu; see <xref linkend="cll_chapter18-section20"/>)</entry>
- </row>
- <row>
- <entry>pi'e</entry>
- <entry>ma'u</entry>
- <entry>ni'u</entry>
- </row>
- <row>
- <entry>mixed-base point</entry>
- <entry>plus sign (not addition)</entry>
- <entry>minus sign (not subtraction)</entry>
- </row>
- <row>
- <entry>ki'o</entry>
- <entry>ra'e</entry>
- </row>
- <row>
- <entry>thousands comma</entry>
- <entry>repeating-decimal indicator</entry>
- </row>
- <row>
- <entry>ji'i</entry>
- <entry>ka'o</entry>
- </row>
- <row>
- <entry>approximation sign</entry>
- <entry>complex number separator</entry>
- </row>
- </tbody>
- </tgroup>
- </informaltable>
+ <cmavo-list>
+ <cmavo-entry>
+ <cmavo>pi</cmavo>
+ <rafsi>piz</rafsi>
+ <description>decimal point</description>
+ </cmavo-entry>
+ <cmavo-entry>
+ <cmavo>ce'i</cmavo>
+ <rafsi>cez</rafsi>
+ <description>percentage</description>
+ </cmavo-entry>
+ <cmavo-entry>
+ <cmavo>fi'u</cmavo>
+ <rafsi>fi'u (from frinu; see <xref linkend="section-explicit-operator-precedence"/>)</rafsi>
+ <description>fraction (not division)</description>
+ </cmavo-entry>
+ <cmavo-entry>
+ <cmavo>pi'e</cmavo>
+ <description>mixed-base point</description>
+ </cmavo-entry>
+ <cmavo-entry>
+ <cmavo>ma'u</cmavo>
+ <description>plus sign (not addition)</description>
+ </cmavo-entry>
+ <cmavo-entry>
+ <cmavo>ni'u</cmavo>
+ <description>minus sign (not subtraction)</description>
+ </cmavo-entry>
+ <cmavo-entry>
+ <cmavo>ki'o</cmavo>
+ <description>thousands comma</description>
+ </cmavo-entry>
+ <cmavo-entry>
+ <cmavo>ra'e</cmavo>
+ <description>repeating-decimal indicator</description>
+ </cmavo-entry>
+ <cmavo-entry>
+ <cmavo>ji'i</cmavo>
+ <description>approximation sign</description>
+ </cmavo-entry>
+ <cmavo-entry>
+ <cmavo>ka'o</cmavo>
+ <description>complex number separator</description>
+ </cmavo-entry>
+ </cmavo-list>
</listitem>
<listitem>
<para> <indexterm type="general-imported"><primary>numbers</primary><secondary>list of indefinite</secondary></indexterm> Indefinite numbers:</para>
<cmavo-list>
<cmavo-entry>
- <cmavo>ro, so'a, so'e, so'i, so'o,</cmavo>
- <selmaho>so'u,</selmaho>
- <description>da'a</description>
+ <cmavo>ro</cmavo>
+ <description>all</description>
+ <rafsi>rol</rafsi>
</cmavo-entry>
<cmavo-entry>
- <cmavo>all, almost all, most, many, several,</cmavo>
- <selmaho>few,</selmaho>
- <description>all but</description>
+ <cmavo>so'a</cmavo>
+ <rafsi>soj</rafsi>
+ <description>almost all</description>
+ </cmavo-entry>
+ <cmavo-entry>
+ <cmavo>so'e</cmavo>
+ <rafsi>sop</rafsi>
+ <description>most</description>
</cmavo-entry>
<cmavo-entry>
- <cmavo>rafsi: rol, soj, sor or so'i, sos,</cmavo>
- <selmaho>sot,</selmaho>
- <description>daz</description>
+ <cmavo>so'i</cmavo>
+ <description>many</description>
+ <rafsi>sor or so'i</rafsi>
+ </cmavo-entry>
+ <cmavo-entry>
+ <cmavo>so'o</cmavo>
+ <rafsi>sos</rafsi>
+ <description>several</description>
+ </cmavo-entry>
+ <cmavo-entry>
+ <cmavo>so'u</cmavo>
+ <rafsi>sot</rafsi>
+ <description>few</description>
+ </cmavo-entry>
+ <cmavo-entry>
+ <cmavo>da'a</cmavo>
+ <rafsi>daz</rafsi>
+ <description>all but</description>
</cmavo-entry>
</cmavo-list>
</listitem>
<listitem>
<para>Subjective numbers:</para>
<cmavo-list>
<cmavo-entry>
- <cmavo>rau,</cmavo>
- <selmaho>du'e,</selmaho>
- <description>mo'a</description>
- </cmavo-entry> enough, too many, too few</cmavo-list>
+ <cmavo>rau</cmavo>
+ <description>enough</description>
+ </cmavo-entry>
+ <cmavo-entry>
+ <cmavo>du'e</cmavo>
+ <description>too few</description>
+ </cmavo-entry>
+ <cmavo-entry>
+ <cmavo>mo'a</cmavo>
+ <description>too many</description>
+ </cmavo-entry>
+ </cmavo-list>
</listitem>
<listitem>
<para>Miscellaneous:</para>
- <place-structure>
- xo, tu'o
- number question, null operand
- </place-structure>
+ <cmavo-list>
+ <cmavo-entry>
+ <cmavo>xo</cmavo>
+ <description>number question</description>
+ </cmavo-entry>
+ <cmavo-entry>
+ <cmavo>tu'o</cmavo>
+ <description>null operand</description>
+ </cmavo-entry>
+ </cmavo-list>
</listitem>
</itemizedlist>
</section>
- <section xml:id="cll_chapter18-section26">
+ <section xml:id="section-moi">
<title>Table of MOI cmavo, with associated rafsi and place structures</title>
- <place-structure>
- mei x1 is a mass formed from a set x2 of n members, one or more of
- which is/are x3, [measured relative to the set x4/by standard x4]
- rafsi: mem, mei
- moi x1 is the (n)th member of set x2 when ordered by rule x3
- [by standard x4]
- rafsi: mom, moi
- si'e x1 is an (n)th portion of mass x2 [by standard x3]
- rafsi: none
- cu'o event x1 has probability (n) of occurring under conditions x2
- [by standard x3]
- rafsi: cu'o (borrowed from cunso; see <xref linkend="cll_chapter18-section20"/>)
- va'e x1 is at scale position (n) on the scale x2
- [by standard x3]
- rafsi: none
- </place-structure>
+ <cmavo-list>
+ <cmavo-entry>
+ <cmavo>mei</cmavo>
+ <rafsi>mem, mei</rafsi>
+ <description>x1 is a mass formed from a set x2 of n members, one or more of which is/are x3, [measured relative to the set x4/by standard x4]</description>
+ </cmavo-entry>
+ <cmavo-entry>
+ <cmavo>moi</cmavo>
+ <rafsi>mom, moi</rafsi>
+ <description>x1 is the (n)th member of set x2 when ordered by rule x3 [by standard x4]</description>
+ </cmavo-entry>
+ <cmavo-entry>
+ <cmavo>si'e</cmavo>
+ <rafsi>none</rafsi>
+ <description>x1 is an (n)th portion of mass x2 [by standard x3]</description>
+ </cmavo-entry>
+ <cmavo-entry>
+ <cmavo>cu'o</cmavo>
+ <rafsi>cu'o (borrowed from <jbophrase>cunso</jbophrase>; see <xref linkend="section-explicit-operator-precedence"/>)</rafsi>
+ <description>event x1 has probability (n) of occurring under conditions x2 [by standard x3]</description>
+ </cmavo-entry>
+ <cmavo-entry>
+ <cmavo>va'e</cmavo>
+ <rafsi>none</rafsi>
+ <description>x1 is at scale position (n) on the scale x2 [by standard x3]</description>
+ </cmavo-entry>
+ </cmavo-list>
</section>
</chapter>
diff --git a/todocbook/20.xml b/todocbook/20.xml
index 9916119..0e66406 100644
--- a/todocbook/20.xml
+++ b/todocbook/20.xml
@@ -70,21 +70,21 @@
<para>Elidable terminator for
<xref linkend="BE"/>. Terminates sumti that are attached to a tanru unit.</para>
<programlisting xml:space="preserve">
mi klama be le zarci be'o troci
I am-a-(goer to-the market) type-of-trier.
I try to go to the market.
</programlisting>
<bridgehead>
<anchor xml:id="BIhE"/> selma'o BIhE (
- <xref linkend="cll_chapter18-section5"/>)
+ <xref linkend="chapter-mekso-section-simple-infix"/>)
</bridgehead>
<para>Prefixed to a mathematical operator to mark it as higher priority than other mathematical operators, binding its operands more closely.</para>
<programlisting xml:space="preserve">
li ci bi'e pi'u vo su'i mu du li paze
The-number 3 [priority] times 4 plus 5 equals the-number 17.
3 × 4 + 5 = 17
</programlisting>
<bridgehead>
<anchor xml:id="BIhI"/> selma'o BIhI (<xref linkend="chapter-connectives-section-non-logical-continued-continued"/>)
@@ -94,33 +94,33 @@
<xref linkend="GAhO"/>.</para>
<programlisting xml:space="preserve">
mi ca sanli la drezdn. bi'i la frankfurt.
I [present] stand-on-surface Dresden [interval] Frankfurt.
I am standing between Dresden and Frankfurt.
</programlisting>
<bridgehead>
<anchor xml:id="BO"/> selma'o BO (
<xref linkend="section-three-part-tanru"/>,
<xref linkend="chapter-negation-section-sumti-negation"/>,
- <xref linkend="cll_chapter18-section17"/>)
+ <xref linkend="chapter-mekso-section-connectives-within-mekso"/>)
</bridgehead>
<para>Joins tanru units, binding them together closely. Also used to bind logically or non-logically connected phrases, sentences, etc.
<xref linkend="BO"/> is always high precedence and right-grouping.</para>
<programlisting xml:space="preserve">
ta cmalu nixli bo ckule
That is-a-small type-of (girl type-of school).
That is a small school for girls.
</programlisting>
<bridgehead>
<anchor xml:id="BOI"/> selma'o BOI (
- <xref linkend="cll_chapter18-section6"/>)
+ <xref linkend="chapter-mekso-section-forethought"/>)
</bridgehead>
<para>Elidable terminator for
<xref linkend="PA"/> or
<xref linkend="BY"/>. Used to terminate a number (string of numeric cmavo) or lerfu string (string of letter words) when another string immediately follows.</para>
<programlisting xml:space="preserve">
li re du li vu'u voboi re
The-number two equals the-number the-difference-of four-and two.
</programlisting>
<bridgehead>
@@ -332,21 +332,21 @@
<para>Signals the end of a compound alphabet letter word that begins with
<xref linkend="TEI"/>. Not an elidable terminator.</para>
<programlisting xml:space="preserve">
tei .ebu .akut. bu foi
( “e” “acute” )
the letter “e” with an acute accent
</programlisting>
<bridgehead>
<anchor xml:id="FUhA"/> selma'o FUhA (
- <xref linkend="cll_chapter18-section16"/>)
+ <xref linkend="chapter-mekso-section-reverse-polish-notation"/>)
</bridgehead>
<para>Indicates that the following mathematical expression is to be interpreted as reverse Polish (RP), a mode in which mathematical operators follow their operands.</para>
<programlisting xml:space="preserve">
li fu'a reboi re[boi] su'i du li vo
the-number [RP!] two, two, plus equals the-number four
2 + 2 = 4
</programlisting>
<bridgehead>
<anchor xml:id="FUhE"/> selma'o FUhE (<xref linkend="chapter-structure-section-attitudinal-scope"/>)
@@ -493,21 +493,21 @@
<para>Specifies a non-logical connection (e.g. together-with-as-mass, -set, or -sequence) between two sumti, tanru units, or various other things. When immediately followed by
<xref linkend="GI"/>, provides forethought non-logical connection analogous to
<xref linkend="GA"/>.</para>
<programlisting xml:space="preserve">
la djan. joi la .alis. cu bevri le pipno
John massed-with Alice carry the piano.
</programlisting>
<bridgehead>
<anchor xml:id="JOhI"/> selma'o JOhI (
- <xref linkend="cll_chapter18-section15"/>)
+ <xref linkend="chapter-mekso-section-vectors-matrices"/>)
</bridgehead>
<para>Indicates that the following mathematical operands (a list terminated by
<xref linkend="TEhU"/>) form a mathematical vector (one-dimensional array).</para>
<programlisting xml:space="preserve">
li jo'i paboi reboi te'u su'i jo'i ciboi voboi du
li jo'i voboi xaboi
The-number array( one, two ) plus array( three, four) equals
the-number array (four, six).
(1,2) + (3,4) = (4,6)
@@ -577,21 +577,21 @@
<xref linkend="LA"/>. Indicates the end of a description sumti. Also used after a tense or modal to indicate that no sumti follows, and in the compound
<xref linkend="NA"/>+
<xref linkend="KU"/> to indicate natural language-style negation.</para>
<programlisting xml:space="preserve">
le prenu ku le zdani ku klama
The person, to-the house, goes.
The person goes to the house.
</programlisting>
<bridgehead>
<anchor xml:id="KUhE"/> selma'o KUhE (
- <xref linkend="cll_chapter18-section6"/>)
+ <xref linkend="chapter-mekso-section-forethought"/>)
</bridgehead>
<para>Elidable terminator for
<xref linkend="PEhO"/>: indicates the end of a forethought mathematical expression (one in which the operator precedes the operands).</para>
<programlisting xml:space="preserve">
li pe'o su'i reboi reboi re[boi] ku'e du li xa
The number [forethought] the-sum-of two two two [end] equals the-number six.
</programlisting>
<bridgehead>
<anchor xml:id="KUhO"/> selma'o KUhO (<xref linkend="chapter-relative-clauses-section-poi"/>)
@@ -654,21 +654,21 @@
<para>Indicates the end of a quotation begun with
<xref linkend="LOhU"/>. Not an elidable terminator.</para>
<programlisting xml:space="preserve">
lo'u mi du do du mi le'u cu na lojbo drani
[quote] mi du do du mi [unquote] is-not Lojbanically correct.
“mi du do du mi” is not correct Lojban.
</programlisting>
<bridgehead>
<anchor xml:id="LI"/> selma'o LI (
- <xref linkend="cll_chapter18-section5"/>)
+ <xref linkend="chapter-mekso-section-simple-infix"/>)
</bridgehead>
<para>Descriptors which change numbers or other mathematical expressions into sumti which specify numbers or numerical expressions. Terminated by
<xref linkend="LOhO"/>.</para>
<programlisting xml:space="preserve">
li re su'u re na du li vo su'i vo
The-number 2 minus 2 not equals the-number 4 plus 4.
2 - 2 ≠ 4 + 4
</programlisting>
<bridgehead>
@@ -676,21 +676,21 @@
</bridgehead>
<para>Elidable terminator for
<xref linkend="LU"/>. Indicates the end of a text quotation.</para>
<programlisting xml:space="preserve">
mi cusku lu mi klama le zarci li'u
I express [quote] I go-to the market [end quote].
</programlisting>
<bridgehead>
<anchor xml:id="LOhO"/> selma'o LOhO (
- <xref linkend="cll_chapter18-section17"/>)
+ <xref linkend="chapter-mekso-section-connectives-within-mekso"/>)
</bridgehead>
<para>Elidable terminator for
<xref linkend="LI"/>. Indicates the end of a mathematical expression used in a
<xref linkend="LI"/> description.</para>
<programlisting xml:space="preserve">
li vo lo'o li ci lo'o cu zmadu
The-number 4 [end number], the number 3 [end number], is greater.
4 > 3
</programlisting>
@@ -723,47 +723,47 @@
<xref linkend="LAhE"/> and
<xref linkend="NAhE"/>+
<xref linkend="BO"/>. Indicates the end of a qualified sumti.</para>
<programlisting xml:space="preserve">
mi viska la'e lu barda gerku li'u lu'u
I see the-referent-of [quote] big dog [end quote] [end ref]
I saw “Big Dog” [not the words, but a book or movie].
</programlisting>
<bridgehead>
<anchor xml:id="MAI"/> selma'o MAI (
- <xref linkend="cll_chapter18-section19"/>,
+ <xref linkend="chapter-mekso-section-other-mekso-uses"/>,
<xref linkend="chapter-structure-section-introduction"/>)
</bridgehead>
<para>When suffixed to a number or string of letter words, produces a free modifier which serves as an index number within a text.</para>
<programlisting xml:space="preserve">
pamai mi pu klama le zarci
1-thly, I [past] go to-the market.
First, I went to the market.
</programlisting>
<bridgehead>
<anchor xml:id="MAhO"/> selma'o MAhO (
- <xref linkend="cll_chapter18-section6"/>)
+ <xref linkend="chapter-mekso-section-forethought"/>)
</bridgehead>
<para>Produces a mathematical operator from a letter or other operand. Terminated by
<xref linkend="TEhU"/>. See
<xref linkend="VUhU"/>.</para>
<programlisting xml:space="preserve">
ma'o fy. boi xy.
[operator] f x
<emphasis>f(x)</emphasis>
</programlisting>
<bridgehead>
<anchor xml:id="ME"/> selma'o ME (
<xref linkend="section-me-selbri"/>,
- <xref linkend="cll_chapter18-section1"/>)
+ <xref linkend="chapter-mekso-section-introduction"/>)
</bridgehead>
<para>Produces a tanru unit from a sumti, which is applicable to the things referenced by the sumti. Terminated by
<xref linkend="MEhU"/>.</para>
<programlisting xml:space="preserve">
ta me la ford. karce
That is-a-Ford-type car
That’s a Ford car.
</programlisting>
<bridgehead>
@@ -772,32 +772,32 @@
<para>The elidable terminator for
<xref linkend="ME"/>. Indicates the end of a sumti converted to a tanru unit.</para>
<programlisting xml:space="preserve">
ta me mi me'u zdani
That’s a me type of house.
</programlisting>
<bridgehead>
<anchor xml:id="MOI"/> selma'o MOI (
<xref linkend="section-place-conversion"/>,
- <xref linkend="cll_chapter18-section18"/>)
+ <xref linkend="chapter-mekso-section-lojban-within-mekso"/>)
</bridgehead>
<para>Suffixes added to numbers or other quantifiers to make various numerically-based selbri.</para>
<programlisting xml:space="preserve">
la djan. joi la frank. cu bruna remei
John in-a-mass-with Frank are-a-brother-type-of twosome.
John and Frank are two brothers.
</programlisting>
<bridgehead>
<anchor xml:id="MOhE"/> selma'o MOhE (
- <xref linkend="cll_chapter18-section18"/>)
+ <xref linkend="chapter-mekso-section-lojban-within-mekso"/>)
</bridgehead>
<para>Produces a mathematical operand from a sumti; used to make dimensioned units. Terminated by
<xref linkend="TEhU"/>.</para>
<programlisting xml:space="preserve">
li mo'e re ratcu su'i mo'e re ractu du li mo'e vo danlu
The-number two rats plus two rabbits equals the-number four animals.
2 rats + 2 rabbits = 4 animals.
</programlisting>
<bridgehead>
@@ -838,36 +838,36 @@
<para>Scalar negators, modifying a selbri or a sumti to a value other than the one stated, the opposite of the one stated, etc. Also used with following
<xref linkend="BO"/> to construct a sumti qualifier; see
<xref linkend="LAhE"/>.</para>
<programlisting xml:space="preserve">
ta na'e blanu zdani
That is-a-non- blue house.
That is a house which is other than blue.
</programlisting>
<bridgehead>
<anchor xml:id="NAhU"/> selma'o NAhU (
- <xref linkend="cll_chapter18-section18"/>)
+ <xref linkend="chapter-mekso-section-lojban-within-mekso"/>)
</bridgehead>
<para>Creates a mathematical operator from a selbri. Terminated by
<xref linkend="TEhU"/>. See
<xref linkend="VUhU"/>.</para>
<programlisting xml:space="preserve">
li na'u tanjo te'u vei pai fe'i re [ve'o] du li ci'i
The-number the-operator tangent (
<phrase role="IPA">π</phrase> / 2 ) = the-number infinity.
tan(
<phrase role="IPA">π</phrase>/2) = ∞
</programlisting>
<bridgehead>
<anchor xml:id="NIhE"/> selma'o NIhE (
- <xref linkend="cll_chapter18-section18"/>)
+ <xref linkend="chapter-mekso-section-lojban-within-mekso"/>)
</bridgehead>
<para>Creates a mathematical operand from a selbri, usually a “ni” abstraction. Terminated by
<xref linkend="TEhU"/>.</para>
<programlisting xml:space="preserve">
li ni'e ni clani [te'u] pi'i ni'e ni ganra [te'u] pi'i
ni'e ni condi te'u du li ni'e ni canlu
The-number quantity-of length times quantity-of width times
quantity-of depth equals the-number quantity-of volume.
Length × Width × Depth = Volume
@@ -893,21 +893,21 @@
</bridgehead>
<para>Abstractors which, when prefixed to a bridi, create abstraction selbri. Terminated by
<xref linkend="KEI"/>.</para>
<programlisting xml:space="preserve">
la djan. cu djica le nu sonci [kei]
John desires the event-of being-a-soldier.
</programlisting>
<bridgehead>
<anchor xml:id="NUhA"/> selma'o NUhA (
- <xref linkend="cll_chapter18-section19"/>)
+ <xref linkend="chapter-mekso-section-other-mekso-uses"/>)
</bridgehead>
<para>Creates a selbri from a mathematical operator. See
<xref linkend="VUhU"/>.</para>
<programlisting xml:space="preserve">
li ni'umu cu nu'a va'a li ma'umu
The-number -5 is-the-negation-of the-number +5
</programlisting>
<bridgehead>
<anchor xml:id="NUhI"/> selma'o NUhI (
@@ -926,21 +926,21 @@
</bridgehead>
<para>Elidable terminator for
<xref linkend="NUhI"/>. Marks the end of a termset.</para>
<programlisting xml:space="preserve">
mi klama nu'i ge le zarci le briju nu'u gi le zdani le ckule [nu'u]
I go [start] to-the market from-the office [joint] and to-the house from-the school.
</programlisting>
<bridgehead>
<anchor xml:id="PA"/> selma'o PA (
- <xref linkend="cll_chapter18-section2"/>)
+ <xref linkend="chapter-mekso-section-numbers"/>)
</bridgehead>
<para>Digits and related quantifiers (some, all, many, etc.). Terminated by
<xref linkend="BOI"/>.</para>
<programlisting xml:space="preserve">
mi speni re ninmu
I am-married-to two women.
</programlisting>
<bridgehead>
<anchor xml:id="PEhE"/> selma'o PEhE (<xref linkend="chapter-connectives-section-termsets"/>)
@@ -948,21 +948,21 @@
<para>Precedes a logical or non-logical connective that joins two termsets. Termsets (see
<xref linkend="CEhE"/>) are used to associate several terms for logical connectives, for equal quantifier scope, or for special constructs in tenses.</para>
<programlisting xml:space="preserve">
mi ce'e do pe'e je la djan. ce'e la djeimyz. cu pendo
I [,] you [joint] and John [,] James are-friends-of.
I am a friend of you, and John is a friend of James.
</programlisting>
<bridgehead>
<anchor xml:id="PEhO"/> selma'o PEhO (
- <xref linkend="cll_chapter18-section6"/>)
+ <xref linkend="chapter-mekso-section-forethought"/>)
</bridgehead>
<para>An optional signal of forethought mathematical operators, which precede their operands. Terminated by
<xref linkend="KUhE"/>.</para>
<programlisting xml:space="preserve">
li vo du li pe'o su'i reboi re
The-number four equals the-number [forethought] sum-of two two.
</programlisting>
<bridgehead>
<anchor xml:id="PU"/> selma'o PU (<xref linkend="chapter-tenses-section-temporal-tenses"/>)
@@ -1081,21 +1081,21 @@
<para>Signals the beginning of a compound letter word, which acts grammatically like a single letter. Compound letter words end with the non-elidable selma'o
<xref linkend="FOI"/>.</para>
<programlisting xml:space="preserve">
tei .ebu .akut. bu foi
( “e” “acute” )
the letter “e” with an acute accent
</programlisting>
<bridgehead>
<anchor xml:id="TEhU"/> selma'o TEhU (
- <xref linkend="cll_chapter18-section15"/>)
+ <xref linkend="chapter-mekso-section-vectors-matrices"/>)
</bridgehead>
<para>Elidable terminator for
<xref linkend="JOhI"/>,
<xref linkend="MAhO"/>,
<xref linkend="MOhE"/>,
<xref linkend="NAhU"/>, or
<xref linkend="NIhE"/>. Marks the end of a mathematical conversion construct.</para>
<programlisting xml:space="preserve">
li jo'i paboi reboi te'u su'i jo'i ciboi voboi du
@@ -1168,21 +1168,21 @@
</bridgehead>
<para>Elidable terminator for a simple bridi, or for each bridi-tail of a
<xref linkend="GIhA"/> logical connection.</para>
<programlisting xml:space="preserve">
mi dunda le cukta [vau] gi'e lebna lo rupnu vau do [vau]
I (give the book) and (take some currency-units) to/from you.
</programlisting>
<bridgehead>
<anchor xml:id="VEI"/> selma'o VEI (
- <xref linkend="cll_chapter18-section5"/>)
+ <xref linkend="chapter-mekso-section-simple-infix"/>)
</bridgehead>
<para>Left mathematical parenthesis: groups mathematical operations. Terminated by
<xref linkend="VEhO"/>.</para>
<programlisting xml:space="preserve">
li vei ny. su'i pa ve'o pi'i vei ny. su'i pa [ve'o] du
li ny. [bo] te'a re su'i re bo pi'i ny. su'i pa
The-number (“n” plus one) times (“n” plus one) equals
the-number n-power-two plus two-times-“n” plus 1.
(n + 1)(n + 1) = n
@@ -1223,33 +1223,33 @@
</bridgehead>
<para>Attaches relative clauses or phrases to a whole (possibly connected) sumti, rather than simply to the leftmost portion of the sumti.</para>
<programlisting xml:space="preserve">
la frank. ce la djordj. vu'o noi gidva cu zvati le kumfa
Frank [in-set-with] George, which are-guides, are-in the room.
Frank and George, who are guides, are in the room.
</programlisting>
<bridgehead>
<anchor xml:id="VUhU"/> selma'o VUhU (
- <xref linkend="cll_chapter18-section5"/>)
+ <xref linkend="chapter-mekso-section-simple-infix"/>)
</bridgehead>
<para>Mathematical operators (e.g. +, −). See
<xref linkend="MAhO"/>.</para>
<programlisting xml:space="preserve">
li mu vu'u re du li ci
The-number 5 minus 2 equals the-number 3.
5 − 2 = 3
</programlisting>
<bridgehead>
<anchor xml:id="XI"/> selma'o XI (
- <xref linkend="cll_chapter18-section13"/>)
+ <xref linkend="chapter-mekso-section-subscripts"/>)
</bridgehead>
<para>The subscript marker: the following number or lerfu string is a subscript for whatever precedes it.</para>
<programlisting xml:space="preserve">
xy. xi re
x sub 2
x
<subscript>2</subscript>
</programlisting>
<bridgehead>
commit a2cbb0a4f260557e1e422861caced687899adebc
Author: Eitan Postavsky <eitanp32@gmail.com>
Date: Sun Jan 16 20:43:57 2011 -0500
Chapter 20 section title and neatening.
diff --git a/todocbook/14.xml b/todocbook/14.xml
index 37d5770..b5da6b6 100644
--- a/todocbook/14.xml
+++ b/todocbook/14.xml
@@ -478,23 +478,23 @@
<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>
<para> <indexterm type="lojban-word-imported"><primary>se</primary></indexterm> <indexterm type="lojban-word-imported"><primary>nai</primary></indexterm> <indexterm type="lojban-word-imported"><primary>na</primary></indexterm> <indexterm type="general-imported"><primary>na</primary><secondary>order in logical connectives with se</secondary></indexterm> <indexterm type="general-imported"><primary>se</primary><secondary>order in logical connectives with na</secondary></indexterm> If both
<jbophrase>na</jbophrase> and
<jbophrase>se</jbophrase> are present, which is legal but never necessary,
<jbophrase>na</jbophrase> would come before
<jbophrase>se</jbophrase>.</para>
<para> <indexterm type="lojban-word-imported"><primary>JA selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>I selma'o</primary></indexterm> <indexterm type="general-imported"><primary>ijeks</primary><secondary>syntax of</secondary></indexterm> The full syntax of ijeks, therefore, is:</para>
- <xxx>
+ <place-structure>
.i [na] [se] JA [nai]
- </xxx>
+ </place-structure>
<para>where the cmavo in brackets are optional.</para>
</section>
<section xml:id="section-forethought-bridi-connection">
<title>Forethought bridi connection</title>
<para> <indexterm type="general-imported"><primary>forethought connectives</primary><secondary>contrasted with afterthought connectives</secondary></indexterm> <indexterm type="general-imported"><primary>afterthought connectives</primary><secondary>contrasted with forethought connectives</secondary></indexterm> Many concepts in Lojban are expressible in two different ways, generally referred to as
<quote>afterthought</quote> and
<quote>forethought</quote>.
<xref linkend="section-bridi-connection"/> discussed what is called
diff --git a/todocbook/20.xml b/todocbook/20.xml
index 2146e9c..9916119 100644
--- a/todocbook/20.xml
+++ b/todocbook/20.xml
@@ -1,1271 +1,1344 @@
<chapter xml:id="chapter-catalogue">
<title>A Catalogue of selma'o</title>
- <section xml:id="cll_chapter20-sectionindex.html">
+ <section xml:id="section-index">
<title/>
<!--
- <h6>$Revision: 4.3 $<br />
- mkhtml: 1.1</h6>
- -->
+ <h6>$Revision: 4.3 $<br />
+ mkhtml: 1.1</h6>
+ -->
<para> <indexterm type="general-imported"><primary>selma'o</primary><secondary>cross-reference list of</secondary><tertiary>selma'o catalog</tertiary></indexterm> The following paragraphs list all the selma'o of Lojban, with a brief explanation of what each one is about, and reference to the chapter number where each is explained more fully. As usual, all selma'o names are given in capital letters (with “h” serving as the capital of “'”) and are the names of a representative cmavo, often the most important or the first in alphabetical order. One example is given of each selma'o: for selma'o which have several uses, the most common use is shown.</para>
-
- <bridgehead> <indexterm type="lojban-word-imported"><primary>A</primary><secondary>selma'o catalog</secondary></indexterm> <indexterm type="general-imported"><primary>connection</primary><secondary>of sumti</secondary><tertiary>selma'o catalog</tertiary></indexterm>
- <anchor xml:id="A"/> selma'o A (<xref linkend="chapter-connectives-section-sumti-connection"/>)</bridgehead>
+ <bridgehead>
+ <indexterm type="lojban-word-imported"><primary>A</primary><secondary>selma'o catalog</secondary></indexterm> <indexterm type="general-imported"><primary>connection</primary><secondary>of sumti</secondary><tertiary>selma'o catalog</tertiary></indexterm>
+ <anchor xml:id="A"/> selma'o A (<xref linkend="chapter-connectives-section-sumti-connection"/>)
+ </bridgehead>
<para>Specifies a logical connection (e.g. “and”, “or”, “if”), usually between sumti.</para>
<programlisting xml:space="preserve">
- la djan. .a la djein. klama le zarci
- John and/or Jane goes to the store.
-</programlisting>
+ la djan. .a la djein. klama le zarci
+ John and/or Jane goes to the store.
+ </programlisting>
+
<para>Also used to create vowel lerfu words when followed with “bu”.</para>
- <bridgehead> <indexterm type="lojban-word-imported"><primary>BAI</primary><secondary>selma'o catalog</secondary></indexterm> <indexterm type="general-imported"><primary>sumti place</primary><secondary>additional</secondary><tertiary>selma'o catalog</tertiary></indexterm>
- <anchor xml:id="BAI"/> selma'o BAI (
- <xref linkend="chapter-sumti-tcita-section-BAI"/>)</bridgehead>
+ <bridgehead>
+ <indexterm type="lojban-word-imported"><primary>BAI</primary><secondary>selma'o catalog</secondary></indexterm> <indexterm type="general-imported"><primary>sumti place</primary><secondary>additional</secondary><tertiary>selma'o catalog</tertiary></indexterm>
+ <anchor xml:id="BAI"/> selma'o BAI (<xref linkend="chapter-sumti-tcita-section-BAI"/>)
+ </bridgehead>
+
<para>May be prefixed to a sumti to specify an additional place, not otherwise present in the place structure of the selbri, and derived from a single place of some other selbri.</para>
<programlisting xml:space="preserve">
- mi tavla bau la lojban.
- I speak in-language Lojban.
-</programlisting>
- <bridgehead> <indexterm type="lojban-word-imported"><primary>BAhE</primary><secondary>selma'o catalog</secondary></indexterm> <indexterm type="general-imported"><primary>nonce word</primary><secondary>marking</secondary><tertiary>selma'o catalog</tertiary></indexterm> <indexterm type="general-imported"><primary>emphasis</primary><secondary>marking</secondary><tertiary>selma'o catalog</tertiary></indexterm>
- <anchor xml:id="BAhE"/> selma'o BAhE (
- <xref linkend="chapter-structure-section-bahe"/>)</bridgehead>
- <para>Emphasizes the next single word, or marks it as a nonce word (one invented for the occasion).</para>
+ mi tavla bau la lojban.
+ I speak in-language Lojban.
+ </programlisting>
+ <bridgehead>
+ <indexterm type="lojban-word-imported"><primary>BAhE</primary><secondary>selma'o catalog</secondary></indexterm> <indexterm type="general-imported"><primary>nonce word</primary><secondary>marking</secondary><tertiary>selma'o catalog</tertiary></indexterm> <indexterm type="general-imported"><primary>emphasis</primary><secondary>marking</secondary><tertiary>selma'o catalog</tertiary></indexterm>
+ <anchor xml:id="BAhE"/> selma'o BAhE (<xref linkend="chapter-structure-section-bahe"/>)
+ </bridgehead>
+ <para>Emphasizes the next single word, or marks it as a nonce word (one invented for the occasion).</para>
<programlisting xml:space="preserve">
- la ba'e .djordj. klama le zarci
-
-<emphasis>George</emphasis> goes to the store.
- It is George who goes to the store.
-</programlisting>
+ la ba'e .djordj. klama le zarci
+ <emphasis>George</emphasis> goes to the store.
+ It is George who goes to the store.
+ </programlisting>
<bridgehead>
- <anchor xml:id="BE"/> selma'o BE (
- <xref linkend="section-be-sumti"/>)</bridgehead>
+ <anchor xml:id="BE"/> selma'o BE (<xref linkend="section-be-sumti"/>)
+ </bridgehead>
+
<para>Attaches sumti which fill the place structure of a single unit making up a tanru. Unless otherwise indicated, the sumti fill the x2, x3, and successive places in that order.
<xref linkend="BE"/> is most useful in descriptions formed with
<xref linkend="LE"/>. See
<xref linkend="BEI"/>,
<xref linkend="BEhO"/>.</para>
<programlisting xml:space="preserve">
- mi klama be ta troci
- I am-a-(goer to-that) type-of-trier.
- I try to go to that place.
-
-</programlisting>
+ mi klama be ta troci
+ I am-a-(goer to-that) type-of-trier.
+ I try to go to that place.
+ </programlisting>
<bridgehead>
- <anchor xml:id="BEI"/> selma'o BEI (
- <xref linkend="section-be-sumti"/>)</bridgehead>
+ <anchor xml:id="BEI"/> selma'o BEI (<xref linkend="section-be-sumti"/>)
+ </bridgehead>
+
<para>Separates multiple sumti attached by
<xref linkend="BE"/> to a tanru unit.</para>
<programlisting xml:space="preserve">
- mi klama be le zarci bei le zdani be'o troci
- I am-a-(goer to-the store from-the home) type-of-trier.
- I try to go from the home to the market.
-
-</programlisting>
+ mi klama be le zarci bei le zdani be'o troci
+ I am-a-(goer to-the store from-the home) type-of-trier.
+ I try to go from the home to the market.
+ </programlisting>
<bridgehead>
- <anchor xml:id="BEhO"/> selma'o BEhO (
- <xref linkend="section-be-sumti"/>)</bridgehead>
+ <anchor xml:id="BEhO"/> selma'o BEhO (<xref linkend="section-be-sumti"/>)
+ </bridgehead>
+
<para>Elidable terminator for
<xref linkend="BE"/>. Terminates sumti that are attached to a tanru unit.</para>
<programlisting xml:space="preserve">
- mi klama be le zarci be'o troci
- I am-a-(goer to-the market) type-of-trier.
- I try to go to the market.
-
-</programlisting>
+ mi klama be le zarci be'o troci
+ I am-a-(goer to-the market) type-of-trier.
+ I try to go to the market.
+ </programlisting>
<bridgehead>
- <anchor xml:id="BIhE"/> selma'o BIhE (
- <xref linkend="cll_chapter18-section5"/>)</bridgehead>
- <para>Prefixed to a mathematical operator to mark it as higher priority than other mathematical operators, binding its operands more closely.</para>
+ <anchor xml:id="BIhE"/> selma'o BIhE (
+ <xref linkend="cll_chapter18-section5"/>)
+ </bridgehead>
+ <para>Prefixed to a mathematical operator to mark it as higher priority than other mathematical operators, binding its operands more closely.</para>
<programlisting xml:space="preserve">
- li ci bi'e pi'u vo su'i mu du li paze
-
-
- The-number 3 [priority] times 4 plus 5 equals the-number 17.
- 3 × 4 + 5 = 17
-</programlisting>
+ li ci bi'e pi'u vo su'i mu du li paze
+ The-number 3 [priority] times 4 plus 5 equals the-number 17.
+ 3 × 4 + 5 = 17
+ </programlisting>
<bridgehead>
- <anchor xml:id="BIhI"/> selma'o BIhI (
- <xref linkend="chapter-connectives-section-non-logical-continued-continued"/>)</bridgehead>
+ <anchor xml:id="BIhI"/> selma'o BIhI (<xref linkend="chapter-connectives-section-non-logical-continued-continued"/>)
+ </bridgehead>
+
<para>Joins sumti or tanru units (as well as some other things) to form intervals. See
<xref linkend="GAhO"/>.</para>
<programlisting xml:space="preserve">
- mi ca sanli la drezdn. bi'i la frankfurt.
- I [present] stand-on-surface Dresden [interval] Frankfurt.
- I am standing between Dresden and Frankfurt.
-
-</programlisting>
+ mi ca sanli la drezdn. bi'i la frankfurt.
+ I [present] stand-on-surface Dresden [interval] Frankfurt.
+ I am standing between Dresden and Frankfurt.
+ </programlisting>
<bridgehead>
- <anchor xml:id="BO"/> selma'o BO (
- <xref linkend="section-three-part-tanru"/>,
- <xref linkend="chapter-negation-section-sumti-negation"/>,
- <xref linkend="cll_chapter18-section17"/>)</bridgehead>
+ <anchor xml:id="BO"/> selma'o BO (
+ <xref linkend="section-three-part-tanru"/>,
+ <xref linkend="chapter-negation-section-sumti-negation"/>,
+ <xref linkend="cll_chapter18-section17"/>)
+ </bridgehead>
+
<para>Joins tanru units, binding them together closely. Also used to bind logically or non-logically connected phrases, sentences, etc.
<xref linkend="BO"/> is always high precedence and right-grouping.</para>
<programlisting xml:space="preserve">
- ta cmalu nixli bo ckule
- That is-a-small type-of (girl type-of school).
- That is a small school for girls.
-</programlisting>
+ ta cmalu nixli bo ckule
+ That is-a-small type-of (girl type-of school).
+ That is a small school for girls.
+ </programlisting>
<bridgehead>
- <anchor xml:id="BOI"/> selma'o BOI (
- <xref linkend="cll_chapter18-section6"/>)</bridgehead>
+ <anchor xml:id="BOI"/> selma'o BOI (
+ <xref linkend="cll_chapter18-section6"/>)
+ </bridgehead>
+
<para>Elidable terminator for
<xref linkend="PA"/> or
<xref linkend="BY"/>. Used to terminate a number (string of numeric cmavo) or lerfu string (string of letter words) when another string immediately follows.</para>
<programlisting xml:space="preserve">
- li re du li vu'u voboi re
- The-number two equals the-number the-difference-of four-and two.
-</programlisting>
+ li re du li vu'u voboi re
+ The-number two equals the-number the-difference-of four-and two.
+ </programlisting>
<bridgehead>
- <anchor xml:id="BU"/> selma'o BU (
- <xref linkend="chapter-letterals-section-bu"/>)</bridgehead>
+ <anchor xml:id="BU"/> selma'o BU (<xref linkend="chapter-letterals-section-bu"/>)
+ </bridgehead>
+
<para>A suffix which can be attached to any word, typically a word representing a letter of the alphabet or else a name, to make a word for a symbol or a different letter of the alphabet. In particular, attached to single-vowel cmavo to make words for vowel letters.</para>
<programlisting xml:space="preserve">
- .abu .ebu .ibu .obu .ubu .ybu
- a, e, i, o, u, y.
-</programlisting>
+ .abu .ebu .ibu .obu .ubu .ybu
+ a, e, i, o, u, y.
+ </programlisting>
<bridgehead>
- <anchor xml:id="BY"/> selma'o BY (
- <xref linkend="chapter-letterals-section-lerfu-liste"/>)</bridgehead>
- <para>Words representing the letters of the Lojban alphabet, plus various shift words which alter the interpretation of other letter words. Terminated by BOI.</para>
+ <anchor xml:id="BY"/> selma'o BY (<xref linkend="chapter-letterals-section-lerfu-liste"/>)
+ </bridgehead>
+ <para>Words representing the letters of the Lojban alphabet, plus various shift words which alter the interpretation of other letter words. Terminated by BOI.</para>
<programlisting xml:space="preserve">
- .abu tavla .by le la .ibymym. skami
- A talks-to B about-the of-IBM computers.
-
- A talks to B about IBM computers.
-
-</programlisting>
+ .abu tavla .by le la .ibymym. skami
+ A talks-to B about-the of-IBM computers.
+ A talks to B about IBM computers.
+ </programlisting>
<bridgehead>
- <anchor xml:id="CAI"/> selma'o CAI (
- <xref linkend="chapter-attitudinals-section-intensity-scale"/>)</bridgehead>
+ <anchor xml:id="CAI"/> selma'o CAI (<xref linkend="chapter-attitudinals-section-intensity-scale"/>)
+ </bridgehead>
+
<para>Indicates the intensity of an emotion: maximum, strong, weak, or not at all. Typically follows another particle which specifies the emotion.</para>
<programlisting xml:space="preserve">
- .ei cai mi klama le zarci
-
- [Obligation!] [Intense!] I go-to the market.
- I must go to the market.
-</programlisting>
+ .ei cai mi klama le zarci
+ [Obligation!] [Intense!] I go-to the market.
+ I must go to the market.
+ </programlisting>
<bridgehead>
- <anchor xml:id="CAhA"/> selma'o CAhA (
- <xref linkend="chapter-tenses-section-caha"/>)</bridgehead>
- <para>Specifies whether a bridi refers to an actual fact, a potential (achieved or not), or merely an innate capability.</para>
+ <anchor xml:id="CAhA"/> selma'o CAhA (<xref linkend="chapter-tenses-section-caha"/>)
+ </bridgehead>
+ <para>Specifies whether a bridi refers to an actual fact, a potential (achieved or not), or merely an innate capability.</para>
<programlisting xml:space="preserve">
- ro datka ka'e flulimna
-
- All ducks [capability] are-float-swimmers.
- All ducks have the capability of swimming by floating.
-</programlisting>
+ ro datka ka'e flulimna
+ All ducks [capability] are-float-swimmers.
+ All ducks have the capability of swimming by floating.
+ </programlisting>
<bridgehead>
- <anchor xml:id="CEI"/> selma'o CEI (
- <xref linkend="chapter-anaphoric-cmavo-section-koha-broda-series"/>)</bridgehead>
+ <anchor xml:id="CEI"/> selma'o CEI (<xref linkend="chapter-anaphoric-cmavo-section-koha-broda-series"/>)
+ </bridgehead>
+
<para>Assigns a selbri definition to one of the five pro-bridi gismu: “broda”, “brode”, “brodi”, “brodo”, or “brodu”, for later use.</para>
<programlisting xml:space="preserve">
- ti slasi je mlatu bo cidja lante gacri cei broda
-
- .i le crino broda cu barda .i le xunre broda cu cmalu
- This is a plastic cat-food can cover, or thingy.
-
- The green thingy is large. The red thingy is small.
-
-</programlisting>
- <bridgehead>
- <anchor xml:id="CEhE"/> selma'o CEhE (
- <xref linkend="chapter-connectives-section-termsets"/>,
- <xref linkend="chapter-quantifiers-section-grouping"/>)</bridgehead>
- <para>Joins multiple terms into a termset. Termsets are used to associate several terms for logical connectives, for equal quantifier scope, or for special constructs in tenses.</para>
+ ti slasi je mlatu bo cidja lante gacri cei broda
+ .i le crino broda cu barda .i le xunre broda cu cmalu
+ This is a plastic cat-food can cover, or thingy.
+ The green thingy is large. The red thingy is small.
+ </programlisting>
+ <bridgehead>
+ <anchor xml:id="CEhE"/> selma'o CEhE (
+ <xref linkend="chapter-connectives-section-termsets"/>,
+ <xref linkend="chapter-quantifiers-section-grouping"/>)
+ </bridgehead>
+ <para>Joins multiple terms into a termset. Termsets are used to associate several terms for logical connectives, for equal quantifier scope, or for special constructs in tenses.</para>
<programlisting xml:space="preserve">
- mi ce'e do pe'e je la djan. ce'e la djeimyz. cu pendo
-
- I [,] you [joint] and John [,] James are-friends-of.
- I am a friend of you, and John is a friend of James.
-</programlisting>
+ mi ce'e do pe'e je la djan. ce'e la djeimyz. cu pendo
+ I [,] you [joint] and John [,] James are-friends-of.
+ I am a friend of you, and John is a friend of James.
+ </programlisting>
<bridgehead>
- <anchor xml:id="CO"/> selma'o CO (
- <xref linkend="section-co-inversion"/>)</bridgehead>
+ <anchor xml:id="CO"/> selma'o CO (<xref linkend="section-co-inversion"/>)
+ </bridgehead>
+
<para>When inserted between the components of a tanru, inverts it, so that the following tanru unit modifies the previous one.</para>
<programlisting xml:space="preserve">
- mi troci co klama le zarci le zdani
- I am-a-trier of-type (goer to-the market from-the house).
- I try to go to the market from the house.
-
-</programlisting>
+ mi troci co klama le zarci le zdani
+ I am-a-trier of-type (goer to-the market from-the house).
+ I try to go to the market from the house.
+ </programlisting>
<bridgehead>
- <anchor xml:id="COI"/> selma'o COI (
- <xref linkend="chapter-sumti-section-vocatives"/>,
- <xref linkend="chapter-attitudinals-section-vocatives"/>)</bridgehead>
- <para>When prefixed to a name, description, or sumti, produces a vocative: a phrase which indicates who is being spoken to (or who is speaking). Vocatives are used in conversational protocols, including greeting, farewell, and radio communication. Terminated by
+ <anchor xml:id="COI"/> selma'o COI (
+ <xref linkend="chapter-sumti-section-vocatives"/>,
+ <xref linkend="chapter-attitudinals-section-vocatives"/>)
+ </bridgehead>
+ <para>When prefixed to a name, description, or sumti, produces a vocative: a phrase which indicates who is being spoken to (or who is speaking). Vocatives are used in conversational protocols, including greeting, farewell, and radio communication. Terminated by
<xref linkend="DOhU"/>. See
<xref linkend="DOI"/>.</para>
<programlisting xml:space="preserve">
- coi .djan.
- Greetings, John.
-</programlisting>
+ coi .djan.
+ Greetings, John.
+ </programlisting>
<bridgehead>
- <anchor xml:id="CU"/> selma'o CU (
- <xref linkend="chapter-sumti-tcita-section-cu"/>)</bridgehead>
- <para>Separates the selbri of a bridi from any sumti which precede it. Never strictly necessary, but often useful to eliminate various elidable terminators.</para>
+ <anchor xml:id="CU"/> selma'o CU (<xref linkend="chapter-sumti-tcita-section-cu"/>)
+ </bridgehead>
+ <para>Separates the selbri of a bridi from any sumti which precede it. Never strictly necessary, but often useful to eliminate various elidable terminators.</para>
<programlisting xml:space="preserve">
- le gerku cu klama le zarci
- The dog goes to-the store.
-</programlisting>
+ le gerku cu klama le zarci
+ The dog goes to-the store.
+ </programlisting>
<bridgehead>
- <anchor xml:id="CUhE"/> selma'o CUhE (
- <xref linkend="chapter-tenses-section-tense-questions"/>)</bridgehead>
+ <anchor xml:id="CUhE"/> selma'o CUhE (<xref linkend="chapter-tenses-section-tense-questions"/>)
+ </bridgehead>
+
<para>Forms a question which asks when, where, or in what mode the rest of the bridi is true. See
<xref linkend="PU"/>,
<xref linkend="CAhA"/>,
<xref linkend="TAhE"/>, and
<xref linkend="BAI"/>.</para>
<programlisting xml:space="preserve">
- do cu'e klama le zarci
- You [When/Where?] go to-the store?
- When are you going to the store?
-</programlisting>
+ do cu'e klama le zarci
+ You [When/Where?] go to-the store?
+ When are you going to the store?
+ </programlisting>
<bridgehead>
- <anchor xml:id="DAhO"/> selma'o DAhO (
- <xref linkend="chapter-anaphoric-cmavo-section-daho"/>)</bridgehead>
+ <anchor xml:id="DAhO"/> selma'o DAhO (<xref linkend="chapter-anaphoric-cmavo-section-daho"/>)
+ </bridgehead>
+
<para>Cancels the assigned significance of all sumti cmavo (of selma'o
<xref linkend="KOhA"/>) and bridi cmavo (of selma'o
<xref linkend="GOhA"/>).</para>
<bridgehead>
- <anchor xml:id="DOI"/> selma'o DOI (
- <xref linkend="chapter-attitudinals-section-vocatives"/>)</bridgehead>
- <para>The non-specific vocative indicator. May be used with or without
+ <anchor xml:id="DOI"/> selma'o DOI (<xref linkend="chapter-attitudinals-section-vocatives"/>)
+ </bridgehead>
+ <para>The non-specific vocative indicator. May be used with or without
<xref linkend="COI"/>. No pause is required between “doi” and a following name. See
<xref linkend="DOhU"/>.</para>
<programlisting xml:space="preserve">
- doi frank. mi tavla do
- O Frank, I speak-to you.
- Frank, I’m talking to you.
-</programlisting>
+ doi frank. mi tavla do
+ O Frank, I speak-to you.
+ Frank, I’m talking to you.
+ </programlisting>
<bridgehead>
- <anchor xml:id="DOhU"/> selma'o DOhU (
- <xref linkend="chapter-attitudinals-section-vocatives"/>)</bridgehead>
+ <anchor xml:id="DOhU"/> selma'o DOhU (<xref linkend="chapter-attitudinals-section-vocatives"/>)
+ </bridgehead>
+
<para>Elidable terminator for
<xref linkend="COI"/> or
<xref linkend="DOI"/>. Signals the end of a vocative.</para>
<programlisting xml:space="preserve">
- coi do'u
-
- Greetings [terminator]
- Greetings, O unspecified one!
-</programlisting>
+ coi do'u
+ Greetings [terminator]
+ Greetings, O unspecified one!
+ </programlisting>
<bridgehead>
- <anchor xml:id="FA"/> selma'o FA (
- <xref linkend="chapter-sumti-tcita-section-FA"/>)</bridgehead>
+ <anchor xml:id="FA"/> selma'o FA (<xref linkend="chapter-sumti-tcita-section-FA"/>)
+ </bridgehead>
+
<para>Prefix for a sumti, indicating which numbered place in the place structure the sumti belongs in; overrides word order.</para>
<programlisting xml:space="preserve">
- fa mi cu klama fi la .atlantas. fe la bastn. fo le dargu fu le karce
- x1= I go x3= Atlanta x2= Boston x4= the road x5= the car.
- I go from Atlanta to Boston via the road using the car.
-</programlisting>
+ fa mi cu klama fi la .atlantas. fe la bastn. fo le dargu fu le karce
+ x1= I go x3= Atlanta x2= Boston x4= the road x5= the car.
+ I go from Atlanta to Boston via the road using the car.
+ </programlisting>
<bridgehead>
- <anchor xml:id="FAhA"/> selma'o FAhA (
- <xref linkend="chapter-tenses-section-spatial-tenses"/>)</bridgehead>
+ <anchor xml:id="FAhA"/> selma'o FAhA (<xref linkend="chapter-tenses-section-spatial-tenses"/>)
+ </bridgehead>
+
<para>Specifies the direction in which, or toward which (when marked with
<xref linkend="MOhI"/>) or along which (when prefixed by
<xref linkend="VEhA"/> or
<xref linkend="VIhA"/>) the action of the bridi takes place.</para>
<programlisting xml:space="preserve">
- le nanmu zu'a batci le gerku
- The man [left] bites the dog.
- To my left, the man bites the dog.
-</programlisting>
+ le nanmu zu'a batci le gerku
+ The man [left] bites the dog.
+ To my left, the man bites the dog.
+ </programlisting>
<bridgehead>
- <anchor xml:id="FAhO"/> selma'o FAhO (
- <xref linkend="chapter-structure-section-faho"/>)</bridgehead>
+ <anchor xml:id="FAhO"/> selma'o FAhO (<xref linkend="chapter-structure-section-faho"/>)
+ </bridgehead>
+
<para>A mechanical signal, outside the grammar, indicating that there is no more text. Useful in talking to computers.</para>
<bridgehead>
- <anchor xml:id="FEhE"/> selma'o FEhE (
- <xref linkend="chapter-tenses-section-fehe"/>)</bridgehead>
+ <anchor xml:id="FEhE"/> selma'o FEhE (<xref linkend="chapter-tenses-section-fehe"/>)
+ </bridgehead>
+
<para>Indicates that the following interval modifier (using
<xref linkend="TAhE"/>,
<xref linkend="ROI"/>, or
<xref linkend="ZAhO"/>) refers to space rather than time.</para>
<programlisting xml:space="preserve">
- ko vi'i fe'e di'i sombo le gurni
-
- You-imperative [1-dimensional] [space] [regularly] sow the grain.
- Sow the grain in a line and evenly!
-</programlisting>
+ ko vi'i fe'e di'i sombo le gurni
+ You-imperative [1-dimensional] [space] [regularly] sow the grain.
+ Sow the grain in a line and evenly!
+ </programlisting>
<bridgehead>
- <anchor xml:id="FEhU"/> selma'o FEhU (
- <xref linkend="chapter-sumti-tcita-section-selbri-modals"/>)</bridgehead>
+ <anchor xml:id="FEhU"/> selma'o FEhU (<xref linkend="chapter-sumti-tcita-section-selbri-modals"/>)
+ </bridgehead>
+
<para>Elidable terminator for
<xref linkend="FIhO"/>. Indicates the end of an ad hoc modal tag: the tagged sumti immediately follows.</para>
<programlisting xml:space="preserve">
- mi viska do fi'o kanla [fe'u] le zunle
- I see you [modal] eye: the left-thing
- I see you with the left eye.
-</programlisting>
+ mi viska do fi'o kanla [fe'u] le zunle
+ I see you [modal] eye: the left-thing
+ I see you with the left eye.
+ </programlisting>
<bridgehead>
- <anchor xml:id="FIhO"/> selma'o FIhO (
- <xref linkend="chapter-sumti-tcita-section-selbri-modals"/>)</bridgehead>
+ <anchor xml:id="FIhO"/> selma'o FIhO (<xref linkend="chapter-sumti-tcita-section-selbri-modals"/>)
+ </bridgehead>
+
<para>When placed before a selbri, transforms the selbri into a modal tag, grammatically and semantically equivalent to a member of selma'o
<xref linkend="BAI"/>. Terminated by
<xref linkend="FEhU"/>.</para>
<programlisting xml:space="preserve">
- mi viska do fi'o kanla le zunle
- I see you with eye the left-thing
- I see you with my left eye.
-</programlisting>
+ mi viska do fi'o kanla le zunle
+ I see you with eye the left-thing
+ I see you with my left eye.
+ </programlisting>
<bridgehead>
- <anchor xml:id="FOI"/> selma'o FOI (
- <xref linkend="chapter-letterals-section-accents"/>)</bridgehead>
+ <anchor xml:id="FOI"/> selma'o FOI (<xref linkend="chapter-letterals-section-accents"/>)
+ </bridgehead>
+
<para>Signals the end of a compound alphabet letter word that begins with
<xref linkend="TEI"/>. Not an elidable terminator.</para>
<programlisting xml:space="preserve">
- tei .ebu .akut. bu foi
- ( “e” “acute” )
- the letter “e” with an acute accent
-</programlisting>
+ tei .ebu .akut. bu foi
+ ( “e” “acute” )
+ the letter “e” with an acute accent
+ </programlisting>
<bridgehead>
- <anchor xml:id="FUhA"/> selma'o FUhA (
- <xref linkend="cll_chapter18-section16"/>)</bridgehead>
- <para>Indicates that the following mathematical expression is to be interpreted as reverse Polish (RP), a mode in which mathematical operators follow their operands.</para>
+ <anchor xml:id="FUhA"/> selma'o FUhA (
+ <xref linkend="cll_chapter18-section16"/>)
+ </bridgehead>
+ <para>Indicates that the following mathematical expression is to be interpreted as reverse Polish (RP), a mode in which mathematical operators follow their operands.</para>
<programlisting xml:space="preserve">
- li fu'a reboi re[boi] su'i du li vo
-
- the-number [RP!] two, two, plus equals the-number four
- 2 + 2 = 4
-</programlisting>
+ li fu'a reboi re[boi] su'i du li vo
+ the-number [RP!] two, two, plus equals the-number four
+ 2 + 2 = 4
+ </programlisting>
<bridgehead>
- <anchor xml:id="FUhE"/> selma'o FUhE (
- <xref linkend="chapter-structure-section-attitudinal-scope"/>)</bridgehead>
+ <anchor xml:id="FUhE"/> selma'o FUhE (<xref linkend="chapter-structure-section-attitudinal-scope"/>)
+ </bridgehead>
+
<para>Indicates that the following indicator(s) of selma'o
<xref linkend="UI"/> affect not the preceding word, as usual, but rather all following words until a
<xref linkend="FUhO"/>.</para>
<programlisting xml:space="preserve">
- mi viska le fu'e .ia blanu zdani fu'o ponse
-
-
- I see the [start] [belief] blue house [end] possessor
- I see the owner of a blue house, or what I believe to be one.
-</programlisting>
+ mi viska le fu'e .ia blanu zdani fu'o ponse
+ I see the [start] [belief] blue house [end] possessor
+ I see the owner of a blue house, or what I believe to be one.
+ </programlisting>
<bridgehead>
- <anchor xml:id="FUhO"/> selma'o FUhO (
- <xref linkend="chapter-structure-section-attitudinal-scope"/>)</bridgehead>
+ <anchor xml:id="FUhO"/> selma'o FUhO (<xref linkend="chapter-structure-section-attitudinal-scope"/>)
+ </bridgehead>
+
<para>Cancels all indicators of selma'o
<xref linkend="UI"/> which are in effect.</para>
<programlisting xml:space="preserve">
- mi viska le fu'e .ia blanu zdani fu'o ponse
-
-
- I see the [start] [belief] blue house [end] possessor.
- I see the owner of what I believe to be a blue house.
-</programlisting>
+ mi viska le fu'e .ia blanu zdani fu'o ponse
+ I see the [start] [belief] blue house [end] possessor.
+ I see the owner of what I believe to be a blue house.
+ </programlisting>
<bridgehead>
- <anchor xml:id="GA"/> selma'o GA (
- <xref linkend="chapter-connectives-section-forethought-bridi-connection"/>)</bridgehead>
- <para>Indicates the beginning of two logically connected sumti, bridi-tails, or various other things. Logical connections include “both ... and”, “either ... or”, “if ... then”, and so on. See
+ <anchor xml:id="GA"/> selma'o GA (<xref linkend="chapter-connectives-section-forethought-bridi-connection"/>)
+ </bridgehead>
+ <para>Indicates the beginning of two logically connected sumti, bridi-tails, or various other things. Logical connections include “both ... and”, “either ... or”, “if ... then”, and so on. See
<xref linkend="GI"/>.</para>
<programlisting xml:space="preserve">
- ga la djan. nanmu gi la djeimyz. ninmu
- Either John is a man or James is a woman (or both).
-</programlisting>
+ ga la djan. nanmu gi la djeimyz. ninmu
+ Either John is a man or James is a woman (or both).
+ </programlisting>
<bridgehead>
- <anchor xml:id="GAhO"/> selma'o GAhO (
- <xref linkend="chapter-connectives-section-non-logical-continued-continued"/>)</bridgehead>
+ <anchor xml:id="GAhO"/> selma'o GAhO (<xref linkend="chapter-connectives-section-non-logical-continued-continued"/>)
+ </bridgehead>
+
<para>Specifies whether an interval specified by
<xref linkend="BIhI"/> includes or excludes its endpoints. Used in pairs before and after the
<xref linkend="BIhI"/> cmavo, to specify the nature of both the left- and the right-hand endpoints.</para>
<programlisting xml:space="preserve">
- mi ca sanli la drezdn. ga'o bi'i ga'o la frankfurt.
- I [present] stand Dresden [inclusive] [interval] [inclusive] Frankfurt.
- I am standing between Dresden and Frankfurt, inclusive of both.
-
-</programlisting>
+ mi ca sanli la drezdn. ga'o bi'i ga'o la frankfurt.
+ I [present] stand Dresden [inclusive] [interval] [inclusive] Frankfurt.
+ I am standing between Dresden and Frankfurt, inclusive of both.
+ </programlisting>
<bridgehead>
- <anchor xml:id="GEhU"/> selma'o GEhU (
- <xref linkend="chapter-relative-clauses-section-relative-phrases"/>)</bridgehead>
+ <anchor xml:id="GEhU"/> selma'o GEhU (<xref linkend="chapter-relative-clauses-section-relative-phrases"/>)
+ </bridgehead>
+
<para>Elidable terminator for
<xref linkend="GOI"/>. Marks the end of a relative phrase. See
<xref linkend="KUhO"/>.</para>
<programlisting xml:space="preserve">
- la djan. goi ko'a ge'u blanu
- John (referred to as it-1) is-blue.
-</programlisting>
+ la djan. goi ko'a ge'u blanu
+ John (referred to as it-1) is-blue.
+ </programlisting>
<bridgehead>
- <anchor xml:id="GI"/> selma'o GI (
- <xref linkend="chapter-connectives-section-forethought-bridi-connection"/>)</bridgehead>
- <para>Separates two logically or non-logically connected sumti, tanru units, bridi-tails, or other things, when the prefix is a forethought connective involving
+ <anchor xml:id="GI"/> selma'o GI (<xref linkend="chapter-connectives-section-forethought-bridi-connection"/>)
+ </bridgehead>
+ <para>Separates two logically or non-logically connected sumti, tanru units, bridi-tails, or other things, when the prefix is a forethought connective involving
<xref linkend="GA"/>,
<xref linkend="GUhA"/>, or
<xref linkend="JOI"/>.</para>
<programlisting xml:space="preserve">
- ge la djan. nanmu gi la djeimyz. ninmu
- (It is true that) both John is a man and James is a woman.
-</programlisting>
+ ge la djan. nanmu gi la djeimyz. ninmu
+ (It is true that) both John is a man and James is a woman.
+ </programlisting>
<bridgehead>
- <anchor xml:id="GIhA"/> selma'o GIhA (
- <xref linkend="chapter-connectives-section-six-types"/>)</bridgehead>
+ <anchor xml:id="GIhA"/> selma'o GIhA (<xref linkend="chapter-connectives-section-six-types"/>)
+ </bridgehead>
+
<para>Specifies a logical connective (e.g. “and”, “or”, “if”) between two bridi-tails: a bridi-tail is a selbri with any associated following sumti, but not including any preceding sumti.</para>
<programlisting xml:space="preserve">
- mi klama le zarci gi'e nelci la djan.
- I go-to the market and like John.
-</programlisting>
+ mi klama le zarci gi'e nelci la djan.
+ I go-to the market and like John.
+ </programlisting>
<bridgehead>
- <anchor xml:id="GOI"/> selma'o GOI (
- <xref linkend="chapter-relative-clauses-section-relative-phrases"/>)</bridgehead>
+ <anchor xml:id="GOI"/> selma'o GOI (<xref linkend="chapter-relative-clauses-section-relative-phrases"/>)
+ </bridgehead>
+
<para>Specifies the beginning of a relative phrase, which associates a subordinate sumti (following) to another sumti (preceding). Terminated by
<xref linkend="GEhU"/> See
<xref linkend="NOI"/>.</para>
<programlisting xml:space="preserve">
- la djan. goi ko'a cu blanu
- John (referred to as it-1) is blue.
-</programlisting>
+ la djan. goi ko'a cu blanu
+ John (referred to as it-1) is blue.
+ </programlisting>
<bridgehead>
- <anchor xml:id="GOhA"/> selma'o GOhA (
- <xref linkend="chapter-anaphoric-cmavo-section-ri-gohi-series"/>)</bridgehead>
+ <anchor xml:id="GOhA"/> selma'o GOhA (<xref linkend="chapter-anaphoric-cmavo-section-ri-gohi-series"/>)
+ </bridgehead>
+
<para>A general selma'o for all cmavo which can take the place of brivla. There are several groups of these.</para>
<programlisting xml:space="preserve">
- A: mi klama le zarci
- B: mi go'i
-
- A: I’m going to the market.
- B: Me, too.
-</programlisting>
+ A: mi klama le zarci
+ B: mi go'i
+ A: I’m going to the market.
+ B: Me, too.
+ </programlisting>
<bridgehead>
- <anchor xml:id="GUhA"/> selma'o GUhA (
- <xref linkend="chapter-connectives-section-six-types"/>)</bridgehead>
+ <anchor xml:id="GUhA"/> selma'o GUhA (<xref linkend="chapter-connectives-section-six-types"/>)
+ </bridgehead>
+
<para>Indicates the beginning of two logically connected tanru units. Takes the place of
<xref linkend="GA"/> when forming logically-connected tanru. See
<xref linkend="GI"/>.</para>
<programlisting xml:space="preserve">
- la .alis. gu'e ricfu gi blanu
- Alice is both rich and blue.
-</programlisting>
+ la .alis. gu'e ricfu gi blanu
+ Alice is both rich and blue.
+ </programlisting>
<bridgehead>
- <anchor xml:id="I"/> selma'o I (
- <xref linkend="chapter-structure-section-i"/>)</bridgehead>
+ <anchor xml:id="I"/> selma'o I (<xref linkend="chapter-structure-section-i"/>)
+ </bridgehead>
+
<para>Separates two sentences from each other.</para>
<programlisting xml:space="preserve">
- mi klama le zarci .i mi klama le zdani
- I go-to the market. I go-to the office.
-</programlisting>
+ mi klama le zarci .i mi klama le zdani
+ I go-to the market. I go-to the office.
+ </programlisting>
<bridgehead>
- <anchor xml:id="JA"/> selma'o JA (
- <xref linkend="chapter-connectives-section-six-types"/>)</bridgehead>
+ <anchor xml:id="JA"/> selma'o JA (<xref linkend="chapter-connectives-section-six-types"/>)
+ </bridgehead>
+
<para>Specifies a logical connection (e.g. “and”, “or”, “if”) between two tanru units, mathematical operands, tenses, or abstractions.</para>
<programlisting xml:space="preserve">
- ti blanu je zdani
- This is-blue and a-house.
-</programlisting>
+ ti blanu je zdani
+ This is-blue and a-house.
+ </programlisting>
<bridgehead>
- <anchor xml:id="JAI"/> selma'o JAI (
- <xref linkend="chapter-sumti-tcita-section-jai"/>)</bridgehead>
+ <anchor xml:id="JAI"/> selma'o JAI (<xref linkend="chapter-sumti-tcita-section-jai"/>)
+ </bridgehead>
+
<para>When followed by a tense or modal, creates a conversion operator attachable to a selbri which exchanges the modal place with the x1 place of the selbri. When alone, is a conversion operator exchanging the x1 place of the selbri (which should be an abstract sumti) with one of the places of the abstracted-over bridi.</para>
<programlisting xml:space="preserve">
- mi jai gau galfi le bitmu skari
- I am-the-actor-in modifying the wall color.
- I act so as to modify the wall color.
- I change the color of the wall.
-</programlisting>
+ mi jai gau galfi le bitmu skari
+ I am-the-actor-in modifying the wall color.
+ I act so as to modify the wall color.
+ I change the color of the wall.
+ </programlisting>
<bridgehead>
- <anchor xml:id="JOI"/> selma'o JOI (
- <xref linkend="chapter-connectives-section-non-logical-connectives"/>)</bridgehead>
- <para>Specifies a non-logical connection (e.g. together-with-as-mass, -set, or -sequence) between two sumti, tanru units, or various other things. When immediately followed by
+ <anchor xml:id="JOI"/> selma'o JOI (<xref linkend="chapter-connectives-section-non-logical-connectives"/>)
+ </bridgehead>
+ <para>Specifies a non-logical connection (e.g. together-with-as-mass, -set, or -sequence) between two sumti, tanru units, or various other things. When immediately followed by
<xref linkend="GI"/>, provides forethought non-logical connection analogous to
-
<xref linkend="GA"/>.</para>
<programlisting xml:space="preserve">
- la djan. joi la .alis. cu bevri le pipno
- John massed-with Alice carry the piano.
-
-</programlisting>
+ la djan. joi la .alis. cu bevri le pipno
+ John massed-with Alice carry the piano.
+ </programlisting>
<bridgehead>
- <anchor xml:id="JOhI"/> selma'o JOhI (
- <xref linkend="cll_chapter18-section15"/>)</bridgehead>
+ <anchor xml:id="JOhI"/> selma'o JOhI (
+ <xref linkend="cll_chapter18-section15"/>)
+ </bridgehead>
+
<para>Indicates that the following mathematical operands (a list terminated by
<xref linkend="TEhU"/>) form a mathematical vector (one-dimensional array).</para>
<programlisting xml:space="preserve">
- li jo'i paboi reboi te'u su'i jo'i ciboi voboi du
- li jo'i voboi xaboi
- The-number array( one, two ) plus array( three, four) equals
- the-number array (four, six).
- (1,2) + (3,4) = (4,6)
-</programlisting>
+ li jo'i paboi reboi te'u su'i jo'i ciboi voboi du
+ li jo'i voboi xaboi
+ The-number array( one, two ) plus array( three, four) equals
+ the-number array (four, six).
+ (1,2) + (3,4) = (4,6)
+ </programlisting>
<bridgehead>
- <anchor xml:id="KE"/> selma'o KE (
- <xref linkend="section-ke-grouping"/>)</bridgehead>
+ <anchor xml:id="KE"/> selma'o KE (<xref linkend="section-ke-grouping"/>)
+ </bridgehead>
+
<para>Groups everything between itself and a following
<xref linkend="KEhE"/> for purposes of logical connection, tanru construction, or other purposes.
<xref linkend="KE"/> and
<xref linkend="KEhE"/> are not used for mathematical (see
<xref linkend="VEI"/> and
<xref linkend="VEhO"/>) or discursive (see
<xref linkend="TO"/> and
<xref linkend="TOI"/>) purposes.</para>
<programlisting xml:space="preserve">
- ta ke melbi cmalu ke'e nixli ckule
- That is-a-( pretty little ) girl school.
- That is a school for girls who are pretty in their littleness.
-</programlisting>
+ ta ke melbi cmalu ke'e nixli ckule
+ That is-a-( pretty little ) girl school.
+ That is a school for girls who are pretty in their littleness.
+ </programlisting>
<bridgehead>
- <anchor xml:id="KEI"/> selma'o KEI (
- <xref linkend="chapter-abstractions-section-syntax"/>)</bridgehead>
+ <anchor xml:id="KEI"/> selma'o KEI (<xref linkend="chapter-abstractions-section-syntax"/>)
+ </bridgehead>
+
<para>Elidable terminator for
<xref linkend="NU"/>. Marks the end of an abstraction bridi.</para>
-
<programlisting xml:space="preserve">
- la djan. cu nu sonci kei djica
- John is-an-(event-of being-a-soldier) type-of desirer.
- John wants to be a soldier.
-</programlisting>
+ la djan. cu nu sonci kei djica
+ John is-an-(event-of being-a-soldier) type-of desirer.
+ John wants to be a soldier.
+ </programlisting>
<bridgehead>
- <anchor xml:id="KEhE"/> selma'o KEhE (
- <xref linkend="section-ke-grouping"/>)</bridgehead>
+ <anchor xml:id="KEhE"/> selma'o KEhE (<xref linkend="section-ke-grouping"/>)
+ </bridgehead>
+
<para>Elidable terminator for
<xref linkend="KE"/>. Marks the end of a grouping.</para>
<programlisting xml:space="preserve">
- ta ke melbi cmalu ke'e nixli ckule
- That is-a-( pretty little ) girl school.
- That is a school for girls who are pretty in their littleness.
-</programlisting>
+ ta ke melbi cmalu ke'e nixli ckule
+ That is-a-( pretty little ) girl school.
+ That is a school for girls who are pretty in their littleness.
+ </programlisting>
<bridgehead>
- <anchor xml:id="KI"/> selma'o KI (
- <xref linkend="chapter-tenses-section-sticky-tenses"/>)</bridgehead>
+ <anchor xml:id="KI"/> selma'o KI (<xref linkend="chapter-tenses-section-sticky-tenses"/>)
+ </bridgehead>
+
<para>When preceded by a tense or modal, makes it “sticky”, so that it applies to all further bridi until reset by another appearance of
<xref linkend="KI"/>. When alone, eliminates all sticky tenses.</para>
<bridgehead>
- <anchor xml:id="KOhA"/> selma'o KOhA (
- <xref linkend="chapter-anaphoric-cmavo-section-introduction"/>)</bridgehead>
+ <anchor xml:id="KOhA"/> selma'o KOhA (<xref linkend="chapter-anaphoric-cmavo-section-introduction"/>)
+ </bridgehead>
+
<para>A general selma'o which contains all cmavo which can substitute for sumti. These cmavo are divided into several groups.</para>
<programlisting xml:space="preserve">
- le blanu zdani goi ko'a cu barda .i ko'a na cmamau ti
- The blue house (referred to as it-1) is big. It-1 is-not smaller-than this-thing.
-</programlisting>
+ le blanu zdani goi ko'a cu barda .i ko'a na cmamau ti
+ The blue house (referred to as it-1) is big. It-1 is-not smaller-than this-thing.
+ </programlisting>
<bridgehead>
- <anchor xml:id="KU"/> selma'o KU (
- <xref linkend="chapter-sumti-section-basic-descriptors"/>,
- <xref linkend="chapter-tenses-section-introduction"/>)</bridgehead>
+ <anchor xml:id="KU"/> selma'o KU (
+ <xref linkend="chapter-sumti-section-basic-descriptors"/>,
+ <xref linkend="chapter-tenses-section-introduction"/>)
+ </bridgehead>
+
<para>Elidable terminator for
<xref linkend="LE"/> and some uses of
<xref linkend="LA"/>. Indicates the end of a description sumti. Also used after a tense or modal to indicate that no sumti follows, and in the compound
<xref linkend="NA"/>+
<xref linkend="KU"/> to indicate natural language-style negation.</para>
<programlisting xml:space="preserve">
- le prenu ku le zdani ku klama
- The person, to-the house, goes.
- The person goes to the house.
-</programlisting>
+ le prenu ku le zdani ku klama
+ The person, to-the house, goes.
+ The person goes to the house.
+ </programlisting>
<bridgehead>
- <anchor xml:id="KUhE"/> selma'o KUhE (
- <xref linkend="cll_chapter18-section6"/>)</bridgehead>
+ <anchor xml:id="KUhE"/> selma'o KUhE (
+ <xref linkend="cll_chapter18-section6"/>)
+ </bridgehead>
+
<para>Elidable terminator for
<xref linkend="PEhO"/>: indicates the end of a forethought mathematical expression (one in which the operator precedes the operands).</para>
<programlisting xml:space="preserve">
- li pe'o su'i reboi reboi re[boi] ku'e du li xa
-
- The number [forethought] the-sum-of two two two [end] equals the-number six.
-</programlisting>
+ li pe'o su'i reboi reboi re[boi] ku'e du li xa
+ The number [forethought] the-sum-of two two two [end] equals the-number six.
+ </programlisting>
<bridgehead>
- <anchor xml:id="KUhO"/> selma'o KUhO (
- <xref linkend="chapter-relative-clauses-section-poi"/>)</bridgehead>
+ <anchor xml:id="KUhO"/> selma'o KUhO (<xref linkend="chapter-relative-clauses-section-poi"/>)
+ </bridgehead>
+
<para>Elidable terminator for
<xref linkend="NOI"/>. Indicates the end of a relative clause.</para>
<programlisting xml:space="preserve">
- le zdani poi blanu ku'o barda
- The house which is-blue is-big.
-</programlisting>
+ le zdani poi blanu ku'o barda
+ The house which is-blue is-big.
+ </programlisting>
<bridgehead>
- <anchor xml:id="LA"/> selma'o LA (
- <xref linkend="chapter-sumti-section-basic-descriptors"/>)</bridgehead>
- <para>Descriptors which change name words (or selbri) into sumti which identify people or things by name. Similar to
+ <anchor xml:id="LA"/> selma'o LA (<xref linkend="chapter-sumti-section-basic-descriptors"/>)
+ </bridgehead>
+ <para>Descriptors which change name words (or selbri) into sumti which identify people or things by name. Similar to
<xref linkend="LE"/>. May be terminated with
<xref linkend="KU"/> if followed by a description selbri.</para>
<programlisting xml:space="preserve">
- la kikeros. du la tulis.
- Cicero is Tully.
-</programlisting>
+ la kikeros. du la tulis.
+ Cicero is Tully.
+ </programlisting>
<bridgehead>
- <anchor xml:id="LAU"/> selma'o LAU (
- <xref linkend="chapter-letterals-section-lerfu-cmavo-summary"/>)</bridgehead>
- <para>Combines with the following alphabetic letter to represent a single marker: change from lower to upper case, change of font, punctuation, etc.)</para>
+ <anchor xml:id="LAU"/> selma'o LAU (<xref linkend="chapter-letterals-section-lerfu-cmavo-summary"/>)
+ </bridgehead>
+ <para>Combines with the following alphabetic letter to represent a single marker: change from lower to upper case, change of font, punctuation, etc.)</para>
<programlisting xml:space="preserve">
- tau sy. .ibu
- [single-shift] “s” “i”
- Si (chemical symbol for silicon)
-</programlisting>
+ tau sy. .ibu
+ [single-shift] “s” “i”
+ Si (chemical symbol for silicon)
+ </programlisting>
<bridgehead>
- <anchor xml:id="LAhE"/> selma'o LAhE (
- <xref linkend="chapter-sumti-section-sumti-qualifiers"/>)</bridgehead>
+ <anchor xml:id="LAhE"/> selma'o LAhE (<xref linkend="chapter-sumti-section-sumti-qualifiers"/>)
+ </bridgehead>
+
<para>Qualifiers which, when prefixed to a sumti, change it into another sumti with related meaning. Qualifiers can also consist of a cmavo from selma'o
<xref linkend="NAhE"/> plus
<xref linkend="BO"/>. Terminated by
<xref linkend="LUhU"/>.</para>
<programlisting xml:space="preserve">
- mi viska la'e zoi kuot. A Tale of Two Cities .kuot
- I see that-represented-by the-text “A Tale of Two Cities”.
- I see the book “A Tale of Two Cities”.
-</programlisting>
+ mi viska la'e zoi kuot. A Tale of Two Cities .kuot
+ I see that-represented-by the-text “A Tale of Two Cities”.
+ I see the book “A Tale of Two Cities”.
+ </programlisting>
<bridgehead>
- <anchor xml:id="LE"/> selma'o LE (
- <xref linkend="chapter-sumti-section-basic-descriptors"/>)</bridgehead>
+ <anchor xml:id="LE"/> selma'o LE (<xref linkend="chapter-sumti-section-basic-descriptors"/>)
+ </bridgehead>
+
<para>Descriptors which make selbri into sumti which describe or specify things that fit into the x1 place of the selbri. Terminated by
<xref linkend="KU"/>. See
<xref linkend="LA"/>.</para>
<programlisting xml:space="preserve">
- le gerku cu klama le zdani
- The dog goes-to the house.
-</programlisting>
+ le gerku cu klama le zdani
+ The dog goes-to the house.
+ </programlisting>
<bridgehead>
- <anchor xml:id="LEhU"/> selma'o LEhU (
- <xref linkend="chapter-structure-section-quotations"/>)</bridgehead>
+ <anchor xml:id="LEhU"/> selma'o LEhU (<xref linkend="chapter-structure-section-quotations"/>)
+ </bridgehead>
+
<para>Indicates the end of a quotation begun with
<xref linkend="LOhU"/>. Not an elidable terminator.</para>
<programlisting xml:space="preserve">
- lo'u mi du do du mi le'u cu na lojbo drani
- [quote] mi du do du mi [unquote] is-not Lojbanically correct.
- “mi du do du mi” is not correct Lojban.
-</programlisting>
+ lo'u mi du do du mi le'u cu na lojbo drani
+ [quote] mi du do du mi [unquote] is-not Lojbanically correct.
+ “mi du do du mi” is not correct Lojban.
+ </programlisting>
<bridgehead>
- <anchor xml:id="LI"/> selma'o LI (
- <xref linkend="cll_chapter18-section5"/>)</bridgehead>
- <para>Descriptors which change numbers or other mathematical expressions into sumti which specify numbers or numerical expressions. Terminated by
+ <anchor xml:id="LI"/> selma'o LI (
+ <xref linkend="cll_chapter18-section5"/>)
+ </bridgehead>
+ <para>Descriptors which change numbers or other mathematical expressions into sumti which specify numbers or numerical expressions. Terminated by
<xref linkend="LOhO"/>.</para>
<programlisting xml:space="preserve">
- li re su'u re na du li vo su'i vo
- The-number 2 minus 2 not equals the-number 4 plus 4.
- 2 - 2 ≠ 4 + 4
-</programlisting>
+ li re su'u re na du li vo su'i vo
+ The-number 2 minus 2 not equals the-number 4 plus 4.
+ 2 - 2 ≠ 4 + 4
+ </programlisting>
<bridgehead>
- <anchor xml:id="LIhU"/> selma'o LIhU (
- <xref linkend="chapter-structure-section-quotations"/>)</bridgehead>
+ <anchor xml:id="LIhU"/> selma'o LIhU (<xref linkend="chapter-structure-section-quotations"/>)
+ </bridgehead>
+
<para>Elidable terminator for
<xref linkend="LU"/>. Indicates the end of a text quotation.</para>
-
<programlisting xml:space="preserve">
- mi cusku lu mi klama le zarci li'u
- I express [quote] I go-to the market [end quote].
-</programlisting>
+ mi cusku lu mi klama le zarci li'u
+ I express [quote] I go-to the market [end quote].
+ </programlisting>
<bridgehead>
- <anchor xml:id="LOhO"/> selma'o LOhO (
- <xref linkend="cll_chapter18-section17"/>)</bridgehead>
+ <anchor xml:id="LOhO"/> selma'o LOhO (
+ <xref linkend="cll_chapter18-section17"/>)
+ </bridgehead>
+
<para>Elidable terminator for
<xref linkend="LI"/>. Indicates the end of a mathematical expression used in a
<xref linkend="LI"/> description.</para>
<programlisting xml:space="preserve">
- li vo lo'o li ci lo'o cu zmadu
-
- The-number 4 [end number], the number 3 [end number], is greater.
- 4 > 3
-</programlisting>
+ li vo lo'o li ci lo'o cu zmadu
+ The-number 4 [end number], the number 3 [end number], is greater.
+ 4 > 3
+ </programlisting>
<bridgehead>
- <anchor xml:id="LOhU"/> selma'o LOhU (
- <xref linkend="chapter-structure-section-quotations"/>)</bridgehead>
+ <anchor xml:id="LOhU"/> selma'o LOhU (<xref linkend="chapter-structure-section-quotations"/>)
+ </bridgehead>
+
<para>Indicates the beginning of a quotation (a sumti) which is grammatical as long as the quoted material consists of Lojban words, whether they form a text or not. Terminated by
<xref linkend="LEhU"/>.</para>
<programlisting xml:space="preserve">
- do cusku lo'u mi du do du ko'a le'u
- You express [quote] mi du do du ko'a [end quote].
- You said, “mi du do du ko'a”.
-</programlisting>
+ do cusku lo'u mi du do du ko'a le'u
+ You express [quote] mi du do du ko'a [end quote].
+ You said, “mi du do du ko'a”.
+ </programlisting>
<bridgehead>
- <anchor xml:id="LU"/> selma'o LU (
- <xref linkend="chapter-structure-section-quotations"/>)</bridgehead>
+ <anchor xml:id="LU"/> selma'o LU (<xref linkend="chapter-structure-section-quotations"/>)
+ </bridgehead>
+
<para>Indicates the beginning of a quotation (a sumti) which is grammatical only if the quoted material also forms a grammatical Lojban text. Terminated by
<xref linkend="LIhU"/>.</para>
<programlisting xml:space="preserve">
- mi cusku lu mi klama le zarci li'u
- I express [quote] I go-to the market [end quote].
-</programlisting>
+ mi cusku lu mi klama le zarci li'u
+ I express [quote] I go-to the market [end quote].
+ </programlisting>
<bridgehead>
- <anchor xml:id="LUhU"/> selma'o LUhU (
- <xref linkend="chapter-sumti-section-sumti-qualifiers"/>)</bridgehead>
+ <anchor xml:id="LUhU"/> selma'o LUhU (<xref linkend="chapter-sumti-section-sumti-qualifiers"/>)
+ </bridgehead>
+
<para>Elidable terminator for
<xref linkend="LAhE"/> and
<xref linkend="NAhE"/>+
<xref linkend="BO"/>. Indicates the end of a qualified sumti.</para>
<programlisting xml:space="preserve">
- mi viska la'e lu barda gerku li'u lu'u
-
-
- I see the-referent-of [quote] big dog [end quote] [end ref]
- I saw “Big Dog” [not the words, but a book or movie].
-</programlisting>
+ mi viska la'e lu barda gerku li'u lu'u
+ I see the-referent-of [quote] big dog [end quote] [end ref]
+ I saw “Big Dog” [not the words, but a book or movie].
+ </programlisting>
<bridgehead>
- <anchor xml:id="MAI"/> selma'o MAI (
- <xref linkend="cll_chapter18-section19"/>,
- <xref linkend="chapter-structure-section-introduction"/>)</bridgehead>
+ <anchor xml:id="MAI"/> selma'o MAI (
+ <xref linkend="cll_chapter18-section19"/>,
+ <xref linkend="chapter-structure-section-introduction"/>)
+ </bridgehead>
+
<para>When suffixed to a number or string of letter words, produces a free modifier which serves as an index number within a text.</para>
<programlisting xml:space="preserve">
- pamai mi pu klama le zarci
- 1-thly, I [past] go to-the market.
- First, I went to the market.
-</programlisting>
+ pamai mi pu klama le zarci
+ 1-thly, I [past] go to-the market.
+ First, I went to the market.
+ </programlisting>
<bridgehead>
- <anchor xml:id="MAhO"/> selma'o MAhO (
- <xref linkend="cll_chapter18-section6"/>)</bridgehead>
+ <anchor xml:id="MAhO"/> selma'o MAhO (
+ <xref linkend="cll_chapter18-section6"/>)
+ </bridgehead>
+
<para>Produces a mathematical operator from a letter or other operand. Terminated by
<xref linkend="TEhU"/>. See
<xref linkend="VUhU"/>.</para>
<programlisting xml:space="preserve">
- ma'o fy. boi xy.
- [operator] f x
-
-<emphasis>f(x)</emphasis>
-</programlisting>
+ ma'o fy. boi xy.
+ [operator] f x
+ <emphasis>f(x)</emphasis>
+ </programlisting>
<bridgehead>
- <anchor xml:id="ME"/> selma'o ME (
- <xref linkend="section-me-selbri"/>,
- <xref linkend="cll_chapter18-section1"/>)</bridgehead>
+ <anchor xml:id="ME"/> selma'o ME (
+ <xref linkend="section-me-selbri"/>,
+ <xref linkend="cll_chapter18-section1"/>)
+ </bridgehead>
+
<para>Produces a tanru unit from a sumti, which is applicable to the things referenced by the sumti. Terminated by
<xref linkend="MEhU"/>.</para>
<programlisting xml:space="preserve">
- ta me la ford. karce
- That is-a-Ford-type car
- That’s a Ford car.
-</programlisting>
+ ta me la ford. karce
+ That is-a-Ford-type car
+ That’s a Ford car.
+ </programlisting>
<bridgehead>
- <anchor xml:id="MEhU"/> selma'o MEhU (
- <xref linkend="section-place-conversion"/>)</bridgehead>
+ <anchor xml:id="MEhU"/> selma'o MEhU (<xref linkend="section-place-conversion"/>)
+ </bridgehead>
+
<para>The elidable terminator for
<xref linkend="ME"/>. Indicates the end of a sumti converted to a tanru unit.</para>
<programlisting xml:space="preserve">
- ta me mi me'u zdani
- That’s a me type of house.
-</programlisting>
+ ta me mi me'u zdani
+ That’s a me type of house.
+ </programlisting>
<bridgehead>
- <anchor xml:id="MOI"/> selma'o MOI (
- <xref linkend="section-place-conversion"/>,
- <xref linkend="cll_chapter18-section18"/>)</bridgehead>
+ <anchor xml:id="MOI"/> selma'o MOI (
+ <xref linkend="section-place-conversion"/>,
+ <xref linkend="cll_chapter18-section18"/>)
+ </bridgehead>
+
<para>Suffixes added to numbers or other quantifiers to make various numerically-based selbri.</para>
<programlisting xml:space="preserve">
- la djan. joi la frank. cu bruna remei
- John in-a-mass-with Frank are-a-brother-type-of twosome.
- John and Frank are two brothers.
-
-
-</programlisting>
+ la djan. joi la frank. cu bruna remei
+ John in-a-mass-with Frank are-a-brother-type-of twosome.
+ John and Frank are two brothers.
+ </programlisting>
<bridgehead>
- <anchor xml:id="MOhE"/> selma'o MOhE (
- <xref linkend="cll_chapter18-section18"/>)</bridgehead>
+ <anchor xml:id="MOhE"/> selma'o MOhE (
+ <xref linkend="cll_chapter18-section18"/>)
+ </bridgehead>
+
<para>Produces a mathematical operand from a sumti; used to make dimensioned units. Terminated by
<xref linkend="TEhU"/>.</para>
<programlisting xml:space="preserve">
- li mo'e re ratcu su'i mo'e re ractu du li mo'e vo danlu
-
- The-number two rats plus two rabbits equals the-number four animals.
- 2 rats + 2 rabbits = 4 animals.
-</programlisting>
+ li mo'e re ratcu su'i mo'e re ractu du li mo'e vo danlu
+ The-number two rats plus two rabbits equals the-number four animals.
+ 2 rats + 2 rabbits = 4 animals.
+ </programlisting>
<bridgehead>
- <anchor xml:id="MOhI"/> selma'o MOhI (
- <xref linkend="chapter-tenses-section-movement"/>)</bridgehead>
+ <anchor xml:id="MOhI"/> selma'o MOhI (<xref linkend="chapter-tenses-section-movement"/>)
+ </bridgehead>
+
<para>A tense flag indicating movement in space, in a direction specified by a following
<xref linkend="FAhA"/> cmavo.</para>
<programlisting xml:space="preserve">
- le verba mo'i ri'u cadzu le bisli
- The child [movement] [right] walks-on the ice.
- The child walks toward my right on the ice.
-
-</programlisting>
+ le verba mo'i ri'u cadzu le bisli
+ The child [movement] [right] walks-on the ice.
+ The child walks toward my right on the ice.
+ </programlisting>
<bridgehead>
- <anchor xml:id="NA"/> selma'o NA (
- <xref linkend="chapter-connectives-section-six-types"/>,
- <xref linkend="chapter-negation-section-other-negation"/>)</bridgehead>
+ <anchor xml:id="NA"/> selma'o NA (
+ <xref linkend="chapter-connectives-section-six-types"/>,
+ <xref linkend="chapter-negation-section-other-negation"/>)
+ </bridgehead>
+
<para>Contradictory negators, asserting that a whole bridi is false (or true).</para>
<programlisting xml:space="preserve">
- mi na klama le zarci
- It is not true that I go to the market.
-</programlisting>
+ mi na klama le zarci
+ It is not true that I go to the market.
+ </programlisting>
+
<para>Also used to construct logical connective compound cmavo.</para>
<bridgehead>
- <anchor xml:id="NAI"/> selma'o NAI (
- <xref linkend="chapter-connectives-section-six-types"/>,
- <xref linkend="chapter-negation-section-other-negation"/>)</bridgehead>
+ <anchor xml:id="NAI"/> selma'o NAI (
+ <xref linkend="chapter-connectives-section-six-types"/>,
+ <xref linkend="chapter-negation-section-other-negation"/>)
+ </bridgehead>
+
<para>Negates the previous word, but can only be used with certain selma'o as specified by the grammar.</para>
<bridgehead>
- <anchor xml:id="NAhE"/> selma'o NAhE (
- <xref linkend="chapter-negation-section-nahe"/>)</bridgehead>
+ <anchor xml:id="NAhE"/> selma'o NAhE (<xref linkend="chapter-negation-section-nahe"/>)
+ </bridgehead>
+
<para>Scalar negators, modifying a selbri or a sumti to a value other than the one stated, the opposite of the one stated, etc. Also used with following
<xref linkend="BO"/> to construct a sumti qualifier; see
<xref linkend="LAhE"/>.</para>
<programlisting xml:space="preserve">
- ta na'e blanu zdani
- That is-a-non- blue house.
- That is a house which is other than blue.
-</programlisting>
+ ta na'e blanu zdani
+ That is-a-non- blue house.
+ That is a house which is other than blue.
+ </programlisting>
<bridgehead>
- <anchor xml:id="NAhU"/> selma'o NAhU (
- <xref linkend="cll_chapter18-section18"/>)</bridgehead>
+ <anchor xml:id="NAhU"/> selma'o NAhU (
+ <xref linkend="cll_chapter18-section18"/>)
+ </bridgehead>
+
<para>Creates a mathematical operator from a selbri. Terminated by
<xref linkend="TEhU"/>. See
<xref linkend="VUhU"/>.</para>
<programlisting xml:space="preserve">
- li na'u tanjo te'u vei pai fe'i re [ve'o] du li ci'i
-
- The-number the-operator tangent (
-<phrase role="IPA">π</phrase> / 2 ) = the-number infinity.
-
- tan(
-<phrase role="IPA">π</phrase>/2) = ∞
-</programlisting>
- <bridgehead>
- <anchor xml:id="NIhE"/> selma'o NIhE (
- <xref linkend="cll_chapter18-section18"/>)</bridgehead>
+ li na'u tanjo te'u vei pai fe'i re [ve'o] du li ci'i
+ The-number the-operator tangent (
+ <phrase role="IPA">π</phrase> / 2 ) = the-number infinity.
+ tan(
+ <phrase role="IPA">π</phrase>/2) = ∞
+ </programlisting>
+ <bridgehead>
+ <anchor xml:id="NIhE"/> selma'o NIhE (
+ <xref linkend="cll_chapter18-section18"/>)
+ </bridgehead>
+
<para>Creates a mathematical operand from a selbri, usually a “ni” abstraction. Terminated by
<xref linkend="TEhU"/>.</para>
<programlisting xml:space="preserve">
- li ni'e ni clani [te'u] pi'i ni'e ni ganra [te'u] pi'i
-
- ni'e ni condi te'u du li ni'e ni canlu
-
- The-number quantity-of length times quantity-of width times
- quantity-of depth equals the-number quantity-of volume.
- Length × Width × Depth = Volume
-</programlisting>
- <bridgehead>
- <anchor xml:id="NIhO"/> selma'o NIhO (
- <xref linkend="chapter-structure-section-niho"/>)</bridgehead>
+ li ni'e ni clani [te'u] pi'i ni'e ni ganra [te'u] pi'i
+ ni'e ni condi te'u du li ni'e ni canlu
+ The-number quantity-of length times quantity-of width times
+ quantity-of depth equals the-number quantity-of volume.
+ Length × Width × Depth = Volume
+ </programlisting>
+ <bridgehead>
+ <anchor xml:id="NIhO"/> selma'o NIhO (<xref linkend="chapter-structure-section-niho"/>)
+ </bridgehead>
+
<para>Marks the beginning of a new paragraph, and indicates whether it contains old or new subject matter.</para>
<bridgehead>
- <anchor xml:id="NOI"/> selma'o NOI (
- <xref linkend="chapter-relative-clauses-section-poi"/>)</bridgehead>
+ <anchor xml:id="NOI"/> selma'o NOI (<xref linkend="chapter-relative-clauses-section-poi"/>)
+ </bridgehead>
+
<para>Introduces relative clauses. The following bridi modifies the preceding sumti. Terminated by
<xref linkend="KUhO"/>. See
<xref linkend="GOI"/>.</para>
<programlisting xml:space="preserve">
- le zdani poi blanu cu cmalu
- The house which is blue is small.
-</programlisting>
+ le zdani poi blanu cu cmalu
+ The house which is blue is small.
+ </programlisting>
<bridgehead>
- <anchor xml:id="NU"/> selma'o NU (
- <xref linkend="chapter-abstractions-section-syntax"/>)</bridgehead>
+ <anchor xml:id="NU"/> selma'o NU (<xref linkend="chapter-abstractions-section-syntax"/>)
+ </bridgehead>
+
<para>Abstractors which, when prefixed to a bridi, create abstraction selbri. Terminated by
<xref linkend="KEI"/>.</para>
<programlisting xml:space="preserve">
- la djan. cu djica le nu sonci [kei]
- John desires the event-of being-a-soldier.
-</programlisting>
+ la djan. cu djica le nu sonci [kei]
+ John desires the event-of being-a-soldier.
+ </programlisting>
<bridgehead>
- <anchor xml:id="NUhA"/> selma'o NUhA (
- <xref linkend="cll_chapter18-section19"/>)</bridgehead>
+ <anchor xml:id="NUhA"/> selma'o NUhA (
+ <xref linkend="cll_chapter18-section19"/>)
+ </bridgehead>
+
<para>Creates a selbri from a mathematical operator. See
<xref linkend="VUhU"/>.</para>
<programlisting xml:space="preserve">
- li ni'umu cu nu'a va'a li ma'umu
- The-number -5 is-the-negation-of the-number +5
-</programlisting>
+ li ni'umu cu nu'a va'a li ma'umu
+ The-number -5 is-the-negation-of the-number +5
+ </programlisting>
<bridgehead>
- <anchor xml:id="NUhI"/> selma'o NUhI (
- <xref linkend="chapter-connectives-section-termsets"/>,
- <xref linkend="chapter-quantifiers-section-grouping"/>)</bridgehead>
+ <anchor xml:id="NUhI"/> selma'o NUhI (
+ <xref linkend="chapter-connectives-section-termsets"/>,
+ <xref linkend="chapter-quantifiers-section-grouping"/>)
+ </bridgehead>
+
<para>Marks the beginning of a termset, which is used to make simultaneous claims involving two or more different places of a selbri. Terminated by
<xref linkend="NUhU"/>.</para>
<programlisting xml:space="preserve">
- mi klama nu'i ge le zarci le briju nu'u gi le zdani le ckule [nu'u]
- I go [start] to-the market from-the office [joint] and to-the house from-the school.
-</programlisting>
+ mi klama nu'i ge le zarci le briju nu'u gi le zdani le ckule [nu'u]
+ I go [start] to-the market from-the office [joint] and to-the house from-the school.
+ </programlisting>
<bridgehead>
- <anchor xml:id="NUhU"/> selma'o NUhU (
- <xref linkend="chapter-connectives-section-termsets"/>)</bridgehead>
+ <anchor xml:id="NUhU"/> selma'o NUhU (<xref linkend="chapter-connectives-section-termsets"/>)
+ </bridgehead>
+
<para>Elidable terminator for
<xref linkend="NUhI"/>. Marks the end of a termset.</para>
<programlisting xml:space="preserve">
- mi klama nu'i ge le zarci le briju nu'u gi le zdani le ckule [nu'u]
- I go [start] to-the market from-the office [joint] and to-the house from-the school.
-</programlisting>
+ mi klama nu'i ge le zarci le briju nu'u gi le zdani le ckule [nu'u]
+ I go [start] to-the market from-the office [joint] and to-the house from-the school.
+ </programlisting>
<bridgehead>
- <anchor xml:id="PA"/> selma'o PA (
- <xref linkend="cll_chapter18-section2"/>)</bridgehead>
+ <anchor xml:id="PA"/> selma'o PA (
+ <xref linkend="cll_chapter18-section2"/>)
+ </bridgehead>
+
<para>Digits and related quantifiers (some, all, many, etc.). Terminated by
<xref linkend="BOI"/>.</para>
<programlisting xml:space="preserve">
- mi speni re ninmu
- I am-married-to two women.
-</programlisting>
+ mi speni re ninmu
+ I am-married-to two women.
+ </programlisting>
<bridgehead>
- <anchor xml:id="PEhE"/> selma'o PEhE (
- <xref linkend="chapter-connectives-section-termsets"/>)</bridgehead>
+ <anchor xml:id="PEhE"/> selma'o PEhE (<xref linkend="chapter-connectives-section-termsets"/>)
+ </bridgehead>
+
<para>Precedes a logical or non-logical connective that joins two termsets. Termsets (see
<xref linkend="CEhE"/>) are used to associate several terms for logical connectives, for equal quantifier scope, or for special constructs in tenses.</para>
-
<programlisting xml:space="preserve">
- mi ce'e do pe'e je la djan. ce'e la djeimyz. cu pendo
-
- I [,] you [joint] and John [,] James are-friends-of.
- I am a friend of you, and John is a friend of James.
-</programlisting>
+ mi ce'e do pe'e je la djan. ce'e la djeimyz. cu pendo
+ I [,] you [joint] and John [,] James are-friends-of.
+ I am a friend of you, and John is a friend of James.
+ </programlisting>
<bridgehead>
- <anchor xml:id="PEhO"/> selma'o PEhO (
- <xref linkend="cll_chapter18-section6"/>)</bridgehead>
- <para>An optional signal of forethought mathematical operators, which precede their operands. Terminated by
+ <anchor xml:id="PEhO"/> selma'o PEhO (
+ <xref linkend="cll_chapter18-section6"/>)
+ </bridgehead>
+ <para>An optional signal of forethought mathematical operators, which precede their operands. Terminated by
<xref linkend="KUhE"/>.</para>
<programlisting xml:space="preserve">
- li vo du li pe'o su'i reboi re
-
- The-number four equals the-number [forethought] sum-of two two.
-</programlisting>
+ li vo du li pe'o su'i reboi re
+ The-number four equals the-number [forethought] sum-of two two.
+ </programlisting>
<bridgehead>
- <anchor xml:id="PU"/> selma'o PU (
- <xref linkend="chapter-tenses-section-temporal-tenses"/>)</bridgehead>
+ <anchor xml:id="PU"/> selma'o PU (<xref linkend="chapter-tenses-section-temporal-tenses"/>)
+ </bridgehead>
+
<para>Specifies simple time directions (future, past, or neither).</para>
<programlisting xml:space="preserve">
- mi pu klama le zarci
- I [past] go-to the market.
- I went to the market.
-</programlisting>
+ mi pu klama le zarci
+ I [past] go-to the market.
+ I went to the market.
+ </programlisting>
<bridgehead>
- <anchor xml:id="RAhO"/> selma'o RAhO (
- <xref linkend="chapter-anaphoric-cmavo-section-ri-gohi-series"/>)</bridgehead>
- <para>The pro-bridi update flag: changes the meaning of sumti implicitly attached to a pro-bridi (see
+ <anchor xml:id="RAhO"/> selma'o RAhO (<xref linkend="chapter-anaphoric-cmavo-section-ri-gohi-series"/>)
+ </bridgehead>
+ <para>The pro-bridi update flag: changes the meaning of sumti implicitly attached to a pro-bridi (see
<xref linkend="GOhA"/>) to fit the current context rather than the original context.</para>
<programlisting xml:space="preserve">
- A: mi ba lumci le mi karce
- B: mi go'i
-
- A: I [future] wash my car.
- B: I do-the-same-thing (i.e. wash A’s car).
-
- A: mi ba lumci le mi karce
- B: mi go'i ra'o
-
-
- A: I [future] wash my car.
- B: I do-the-corresponding-thing (i.e. wash B’s car).
-</programlisting>
- <bridgehead>
- <anchor xml:id="ROI"/> selma'o ROI (
- <xref linkend="chapter-tenses-section-interval-properties"/>)</bridgehead>
+ A: mi ba lumci le mi karce
+ B: mi go'i
+ A: I [future] wash my car.
+ B: I do-the-same-thing (i.e. wash A’s car).
+ A: mi ba lumci le mi karce
+ B: mi go'i ra'o
+ A: I [future] wash my car.
+ B: I do-the-corresponding-thing (i.e. wash B’s car).
+ </programlisting>
+ <bridgehead>
+ <anchor xml:id="ROI"/> selma'o ROI (<xref linkend="chapter-tenses-section-interval-properties"/>)
+ </bridgehead>
+
<para>When suffixed to a number, makes an extensional tense (e.g. once, twice, many times).</para>
<programlisting xml:space="preserve">
- mi reroi klama le zarci
- I twice go-to the market.
-</programlisting>
+ mi reroi klama le zarci
+ I twice go-to the market.
+ </programlisting>
<bridgehead>
- <anchor xml:id="SA"/> selma'o SA (
- <xref linkend="chapter-structure-section-erasure"/>)</bridgehead>
+ <anchor xml:id="SA"/> selma'o SA (<xref linkend="chapter-structure-section-erasure"/>)
+ </bridgehead>
+
<para>Erases the previous phrase or sentence.</para>
<programlisting xml:space="preserve">
- mi klama sa do klama le zarci
- I go, er, you go-to the market.
-</programlisting>
+ mi klama sa do klama le zarci
+ I go, er, you go-to the market.
+ </programlisting>
<bridgehead>
- <anchor xml:id="SE"/> selma'o SE (
- <xref linkend="section-brivla"/>,
- <xref linkend="chapter-sumti-tcita-section-SE"/>)</bridgehead>
+ <anchor xml:id="SE"/> selma'o SE (
+ <xref linkend="section-brivla"/>,
+ <xref linkend="chapter-sumti-tcita-section-SE"/>)
+ </bridgehead>
+
<para>Converts a selbri, rearranging the order of places by exchanging the x1 place with a specified numbered place.</para>
<programlisting xml:space="preserve">
- le zarci cu se klama mi
- The market is-gone-to by me.
-</programlisting>
+ le zarci cu se klama mi
+ The market is-gone-to by me.
+ </programlisting>
+
<para>Also used in constructing connective and modal compound cmavo.</para>
<bridgehead>
- <anchor xml:id="SEI"/> selma'o SEI (
- <xref linkend="chapter-structure-section-parentheses"/>)</bridgehead>
- <para>Marks the beginning of metalinguistic insertions which comment on the main bridi. Terminated by
+ <anchor xml:id="SEI"/> selma'o SEI (<xref linkend="chapter-structure-section-parentheses"/>)
+ </bridgehead>
+ <para>Marks the beginning of metalinguistic insertions which comment on the main bridi. Terminated by
<xref linkend="SEhU"/>.</para>
<programlisting xml:space="preserve">
- la frank. prami sei gleki [se'u] la djein.
- Frank loves (he is happy) Jane.
-</programlisting>
+ la frank. prami sei gleki [se'u] la djein.
+ Frank loves (he is happy) Jane.
+ </programlisting>
<bridgehead>
- <anchor xml:id="SEhU"/> selma'o SEhU (
- <xref linkend="chapter-structure-section-parentheses"/>)</bridgehead>
+ <anchor xml:id="SEhU"/> selma'o SEhU (<xref linkend="chapter-structure-section-parentheses"/>)
+ </bridgehead>
+
<para>Elidable terminator for
<xref linkend="SEI"/> and
<xref linkend="SOI"/>. Ends metalinguistic insertions.</para>
-
<programlisting xml:space="preserve">
- la frank. prami sei gleki se'u la djein.
- Frank loves (he is happy) Jane.
-</programlisting>
+ la frank. prami sei gleki se'u la djein.
+ Frank loves (he is happy) Jane.
+ </programlisting>
<bridgehead>
- <anchor xml:id="SI"/> selma'o SI (
- <xref linkend="chapter-structure-section-erasure"/>)</bridgehead>
+ <anchor xml:id="SI"/> selma'o SI (<xref linkend="chapter-structure-section-erasure"/>)
+ </bridgehead>
+
<para>Erases the previous single word.</para>
<programlisting xml:space="preserve">
- mi si do klama le zarci
- I, er, you go to-the market.
-</programlisting>
+ mi si do klama le zarci
+ I, er, you go to-the market.
+ </programlisting>
<bridgehead>
- <anchor xml:id="SOI"/> selma'o SOI (
- <xref linkend="chapter-anaphoric-cmavo-section-voha-series"/>)</bridgehead>
- <para>Marks reciprocity between two sumti (like “vice versa” in English).</para>
-
+ <anchor xml:id="SOI"/> selma'o SOI (<xref linkend="chapter-anaphoric-cmavo-section-voha-series"/>)
+ </bridgehead>
+ <para>Marks reciprocity between two sumti (like “vice versa” in English).</para>
<programlisting xml:space="preserve">
- mi prami do soi mi
- I love you [reciprocally] me.
- I love you and vice versa.
-</programlisting>
+ mi prami do soi mi
+ I love you [reciprocally] me.
+ I love you and vice versa.
+ </programlisting>
<bridgehead>
- <anchor xml:id="SU"/> selma'o SU (
- <xref linkend="chapter-structure-section-erasure"/>)</bridgehead>
+ <anchor xml:id="SU"/> selma'o SU (<xref linkend="chapter-structure-section-erasure"/>)
+ </bridgehead>
+
<para>Closes and erases the entire previous discourse.</para>
<bridgehead>
- <anchor xml:id="TAhE"/> selma'o TAhE (
- <xref linkend="chapter-tenses-section-interval-properties"/>)</bridgehead>
+ <anchor xml:id="TAhE"/> selma'o TAhE (<xref linkend="chapter-tenses-section-interval-properties"/>)
+ </bridgehead>
+
<para>A tense modifier specifying frequencies within an interval of time or space (regularly, habitually, etc.).</para>
<programlisting xml:space="preserve">
- le verba ta'e klama le ckule
-
- The child habitually goes to-the school.
-</programlisting>
+ le verba ta'e klama le ckule
+ The child habitually goes to-the school.
+ </programlisting>
<bridgehead>
- <anchor xml:id="TEI"/> selma'o TEI (
- <xref linkend="chapter-letterals-section-accents"/>)</bridgehead>
+ <anchor xml:id="TEI"/> selma'o TEI (<xref linkend="chapter-letterals-section-accents"/>)
+ </bridgehead>
+
<para>Signals the beginning of a compound letter word, which acts grammatically like a single letter. Compound letter words end with the non-elidable selma'o
<xref linkend="FOI"/>.</para>
<programlisting xml:space="preserve">
- tei .ebu .akut. bu foi
- ( “e” “acute” )
- the letter “e” with an acute accent
-</programlisting>
+ tei .ebu .akut. bu foi
+ ( “e” “acute” )
+ the letter “e” with an acute accent
+ </programlisting>
<bridgehead>
- <anchor xml:id="TEhU"/> selma'o TEhU (
- <xref linkend="cll_chapter18-section15"/>)</bridgehead>
+ <anchor xml:id="TEhU"/> selma'o TEhU (
+ <xref linkend="cll_chapter18-section15"/>)
+ </bridgehead>
+
<para>Elidable terminator for
<xref linkend="JOhI"/>,
<xref linkend="MAhO"/>,
<xref linkend="MOhE"/>,
<xref linkend="NAhU"/>, or
<xref linkend="NIhE"/>. Marks the end of a mathematical conversion construct.</para>
<programlisting xml:space="preserve">
- li jo'i paboi reboi te'u su'i jo'i ciboi voboi du
- li jo'i voboi xaboi
- The-number array (one, two) plus array (three, four) equals
- the-number array( four, six).
- (1,2) + (3,4) = (4,6)
-</programlisting>
+ li jo'i paboi reboi te'u su'i jo'i ciboi voboi du
+ li jo'i voboi xaboi
+ The-number array (one, two) plus array (three, four) equals
+ the-number array( four, six).
+ (1,2) + (3,4) = (4,6)
+ </programlisting>
<bridgehead>
- <anchor xml:id="TO"/> selma'o TO (
- <xref linkend="chapter-structure-section-parentheses"/>)</bridgehead>
+ <anchor xml:id="TO"/> selma'o TO (<xref linkend="chapter-structure-section-parentheses"/>)
+ </bridgehead>
+
<para>Left discursive parenthesis: allows inserting a digression. Terminated by
<xref linkend="TOI"/>.</para>
<programlisting xml:space="preserve">
- doi lisas. mi djica le nu to doi frank. ko sisti toi do viska le mlatu
- O Lisa, I desire the event-of ( O Frank, [imperative] stop! ) you see the cat.
- Lisa, I want you to (Frank! Stop!) see the cat.
-</programlisting>
+ doi lisas. mi djica le nu to doi frank. ko sisti toi do viska le mlatu
+ O Lisa, I desire the event-of ( O Frank, [imperative] stop! ) you see the cat.
+ Lisa, I want you to (Frank! Stop!) see the cat.
+ </programlisting>
<bridgehead>
- <anchor xml:id="TOI"/> selma'o TOI (
- <xref linkend="chapter-structure-section-parentheses"/>)</bridgehead>
+ <anchor xml:id="TOI"/> selma'o TOI (<xref linkend="chapter-structure-section-parentheses"/>)
+ </bridgehead>
+
<para>Elidable terminator for
<xref linkend="TO"/>. The right discursive parenthesis.</para>
<programlisting xml:space="preserve">
- doi lisas. mi djica le nu to doi frank. ko sisti toi do viska le mlatu
- O Lisa, I desire the event-of ( O Frank, [imperative] stop! ) you see the cat.
- Lisa, I want you to (Frank! Stop!) see the cat.
-</programlisting>
+ doi lisas. mi djica le nu to doi frank. ko sisti toi do viska le mlatu
+ O Lisa, I desire the event-of ( O Frank, [imperative] stop! ) you see the cat.
+ Lisa, I want you to (Frank! Stop!) see the cat.
+ </programlisting>
<bridgehead>
- <anchor xml:id="TUhE"/> selma'o TUhE (
- <xref linkend="chapter-structure-section-i"/>)</bridgehead>
+ <anchor xml:id="TUhE"/> selma'o TUhE (<xref linkend="chapter-structure-section-i"/>)
+ </bridgehead>
+
<para>Groups multiple sentences or paragraphs into a logical unit. Terminated by
<xref linkend="TUhU"/>.</para>
<programlisting xml:space="preserve">
- lo xagmau zo'u tu'e ganai cidja gi citno .i ganai vanju gi tolci'o [tu'u]
- Is-best : [start] If food, then new. If wine, then old.
- As for what is best: if food, then new [is best]; if wine, then old [is best].
-</programlisting>
+ lo xagmau zo'u tu'e ganai cidja gi citno .i ganai vanju gi tolci'o [tu'u]
+ Is-best : [start] If food, then new. If wine, then old.
+ As for what is best: if food, then new [is best]; if wine, then old [is best].
+ </programlisting>
<bridgehead>
- <anchor xml:id="TUhU"/> selma'o TUhU (
- <xref linkend="chapter-structure-section-i"/>)</bridgehead>
+ <anchor xml:id="TUhU"/> selma'o TUhU (<xref linkend="chapter-structure-section-i"/>)
+ </bridgehead>
+
<para>Elidable terminator for
<xref linkend="TUhE"/>. Marks the end of a multiple sentence group.</para>
<bridgehead>
- <anchor xml:id="UI"/> selma'o UI (
- <xref linkend="chapter-attitudinals-section-introduction"/>)</bridgehead>
+ <anchor xml:id="UI"/> selma'o UI (<xref linkend="chapter-attitudinals-section-introduction"/>)
+ </bridgehead>
+
<para>Particles which indicate the speaker’s emotional state or source of knowledge, or the present stage of discourse.</para>
<programlisting xml:space="preserve">
- .ui la djan. klama
- [Happiness!] John is-coming.
- Hurrah! John is coming!
-</programlisting>
+ .ui la djan. klama
+ [Happiness!] John is-coming.
+ Hurrah! John is coming!
+ </programlisting>
<bridgehead>
- <anchor xml:id="VA"/> selma'o VA (
- <xref linkend="chapter-tenses-section-spatial-tenses"/>)</bridgehead>
+ <anchor xml:id="VA"/> selma'o VA (<xref linkend="chapter-tenses-section-spatial-tenses"/>)
+ </bridgehead>
+
<para>A tense indicating distance in space (near, far, or neither).</para>
<programlisting xml:space="preserve">
- le nanmu va batci le gerku
- The man [medium distance] bites the dog.
- Over there the man is biting the dog.
-</programlisting>
+ le nanmu va batci le gerku
+ The man [medium distance] bites the dog.
+ Over there the man is biting the dog.
+ </programlisting>
<bridgehead>
- <anchor xml:id="VAU"/> selma'o VAU (
- <xref linkend="chapter-connectives-section-compound-bridi"/>)</bridgehead>
- <para>Elidable terminator for a simple bridi, or for each bridi-tail of a
+ <anchor xml:id="VAU"/> selma'o VAU (<xref linkend="chapter-connectives-section-compound-bridi"/>)
+ </bridgehead>
+ <para>Elidable terminator for a simple bridi, or for each bridi-tail of a
<xref linkend="GIhA"/> logical connection.</para>
<programlisting xml:space="preserve">
- mi dunda le cukta [vau] gi'e lebna lo rupnu vau do [vau]
- I (give the book) and (take some currency-units) to/from you.
-</programlisting>
+ mi dunda le cukta [vau] gi'e lebna lo rupnu vau do [vau]
+ I (give the book) and (take some currency-units) to/from you.
+ </programlisting>
<bridgehead>
- <anchor xml:id="VEI"/> selma'o VEI (
- <xref linkend="cll_chapter18-section5"/>)</bridgehead>
- <para>Left mathematical parenthesis: groups mathematical operations. Terminated by
+ <anchor xml:id="VEI"/> selma'o VEI (
+ <xref linkend="cll_chapter18-section5"/>)
+ </bridgehead>
+ <para>Left mathematical parenthesis: groups mathematical operations. Terminated by
<xref linkend="VEhO"/>.</para>
<programlisting xml:space="preserve">
- li vei ny. su'i pa ve'o pi'i vei ny. su'i pa [ve'o] du
- li ny. [bo] te'a re su'i re bo pi'i ny. su'i pa
-
- The-number (“n” plus one) times (“n” plus one) equals
- the-number n-power-two plus two-times-“n” plus 1.
- (n + 1)(n + 1) = n
-<superscript>2</superscript> + 2n + 1
-</programlisting>
- <bridgehead>
- <anchor xml:id="VEhA"/> selma'o VEhA (
- <xref linkend="chapter-tenses-section-interval-sizes"/>)</bridgehead>
+ li vei ny. su'i pa ve'o pi'i vei ny. su'i pa [ve'o] du
+ li ny. [bo] te'a re su'i re bo pi'i ny. su'i pa
+ The-number (“n” plus one) times (“n” plus one) equals
+ the-number n-power-two plus two-times-“n” plus 1.
+ (n + 1)(n + 1) = n
+ <superscript>2</superscript> + 2n + 1
+ </programlisting>
+ <bridgehead>
+ <anchor xml:id="VEhA"/> selma'o VEhA (<xref linkend="chapter-tenses-section-interval-sizes"/>)
+ </bridgehead>
+
<para>A tense indicating the size of an interval in space (long, medium, or short).</para>
<bridgehead>
- <anchor xml:id="VEhO"/> selma'o VEhO (
- <xref linkend="chapter-structure-section-questions"/>)</bridgehead>
+ <anchor xml:id="VEhO"/> selma'o VEhO (<xref linkend="chapter-structure-section-questions"/>)
+ </bridgehead>
+
<para>Elidable terminator for
<xref linkend="VEI"/>: right mathematical parenthesis.</para>
-
<programlisting xml:space="preserve">
- li vei ny. su'i pa ve'o pi'i vei ny. su'i pa [ve'o] du
- li ny. [bo] te'a re su'i re bo pi'i ny. su'i pa
-
- The-number (“n” plus one) times (“n” plus one) equals
- the-number n-power-two plus two-times-“n” plus 1.
- (n + 1)(n + 1) = n
-<superscript>2</superscript> + 2n + 1
-</programlisting>
+ li vei ny. su'i pa ve'o pi'i vei ny. su'i pa [ve'o] du
+ li ny. [bo] te'a re su'i re bo pi'i ny. su'i pa
+ The-number (“n” plus one) times (“n” plus one) equals
+ the-number n-power-two plus two-times-“n” plus 1.
+ (n + 1)(n + 1) = n
+ <superscript>2</superscript> + 2n + 1
+ </programlisting>
<bridgehead>
- <anchor xml:id="VIhA"/> selma'o VIhA (
- <xref linkend="chapter-tenses-section-dimensionality"/>)</bridgehead>
- <para>A tense indicating dimensionality in space (line, plane, volume, or space-time interval).</para>
+ <anchor xml:id="VIhA"/> selma'o VIhA (<xref linkend="chapter-tenses-section-dimensionality"/>)
+ </bridgehead>
+ <para>A tense indicating dimensionality in space (line, plane, volume, or space-time interval).</para>
<programlisting xml:space="preserve">
- le verba ve'a vi'a cadzu le bisli
-
- The child [medium space interval] [2-dimensional] walks-on the ice.
- In a medium-sized area, the child walks on the ice.
-</programlisting>
+ le verba ve'a vi'a cadzu le bisli
+ The child [medium space interval] [2-dimensional] walks-on the ice.
+ In a medium-sized area, the child walks on the ice.
+ </programlisting>
<bridgehead>
- <anchor xml:id="VUhO"/> selma'o VUhO (
- <xref linkend="cll_chapter8-section8"/>)</bridgehead>
+ <anchor xml:id="VUhO"/> selma'o VUhO (
+ <xref linkend="cll_chapter8-section8"/>)
+ </bridgehead>
+
<para>Attaches relative clauses or phrases to a whole (possibly connected) sumti, rather than simply to the leftmost portion of the sumti.</para>
<programlisting xml:space="preserve">
- la frank. ce la djordj. vu'o noi gidva cu zvati le kumfa
- Frank [in-set-with] George, which are-guides, are-in the room.
- Frank and George, who are guides, are in the room.
-</programlisting>
+ la frank. ce la djordj. vu'o noi gidva cu zvati le kumfa
+ Frank [in-set-with] George, which are-guides, are-in the room.
+ Frank and George, who are guides, are in the room.
+ </programlisting>
<bridgehead>
- <anchor xml:id="VUhU"/> selma'o VUhU (
- <xref linkend="cll_chapter18-section5"/>)</bridgehead>
+ <anchor xml:id="VUhU"/> selma'o VUhU (
+ <xref linkend="cll_chapter18-section5"/>)
+ </bridgehead>
+
<para>Mathematical operators (e.g. +, −). See
<xref linkend="MAhO"/>.</para>
<programlisting xml:space="preserve">
- li mu vu'u re du li ci
- The-number 5 minus 2 equals the-number 3.
- 5 − 2 = 3
-</programlisting>
+ li mu vu'u re du li ci
+ The-number 5 minus 2 equals the-number 3.
+ 5 − 2 = 3
+ </programlisting>
<bridgehead>
- <anchor xml:id="XI"/> selma'o XI (
- <xref linkend="cll_chapter18-section13"/>)</bridgehead>
+ <anchor xml:id="XI"/> selma'o XI (
+ <xref linkend="cll_chapter18-section13"/>)
+ </bridgehead>
+
<para>The subscript marker: the following number or lerfu string is a subscript for whatever precedes it.</para>
<programlisting xml:space="preserve">
- xy. xi re
- x sub 2
- x
-<subscript>2</subscript>
-</programlisting>
+ xy. xi re
+ x sub 2
+ x
+ <subscript>2</subscript>
+ </programlisting>
<bridgehead>
- <anchor xml:id="Y"/> selma'o Y (
- <xref linkend="chapter-structure-section-hesitation"/>)</bridgehead>
- <para>Hesitation noise: content-free, but holds the floor or continues the conversation. It is different from silence in that silence may be interpreted as having nothing more to say.</para>
+ <anchor xml:id="Y"/> selma'o Y (<xref linkend="chapter-structure-section-hesitation"/>)
+ </bridgehead>
+ <para>Hesitation noise: content-free, but holds the floor or continues the conversation. It is different from silence in that silence may be interpreted as having nothing more to say.</para>
<programlisting xml:space="preserve">
- doi .y. .y. .djan
- O, uh, uh, John!
-</programlisting>
+ doi .y. .y. .djan
+ O, uh, uh, John!
+ </programlisting>
<bridgehead>
- <anchor xml:id="ZAhO"/> selma'o ZAhO (
- <xref linkend="chapter-tenses-section-event-contours"/>)</bridgehead>
+ <anchor xml:id="ZAhO"/> selma'o ZAhO (<xref linkend="chapter-tenses-section-event-contours"/>)
+ </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>
+ 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-section-rafsi"/>)</bridgehead>
- <para>A morphological glue word, which joins the two words it stands between into the equivalent of a lujvo.</para>
+ <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>
+ 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 (
- <xref linkend="chapter-tenses-section-interval-sizes"/>)</bridgehead>
+ <anchor xml:id="ZEhA"/> selma'o ZEhA (<xref linkend="chapter-tenses-section-interval-sizes"/>)
+ </bridgehead>
+
<para>A tense indicating the size of an interval in time (long, medium, or short).</para>
<programlisting xml:space="preserve">
- mi puze'a citka
- I [past] [short interval] eat.
- I ate for a little while.
-</programlisting>
+ mi puze'a citka
+ I [past] [short interval] eat.
+ I ate for a little while.
+ </programlisting>
<bridgehead>
- <anchor xml:id="ZI"/> selma'o ZI (
- <xref linkend="chapter-tenses-section-temporal-tenses"/>)</bridgehead>
+ <anchor xml:id="ZI"/> selma'o ZI (<xref linkend="chapter-tenses-section-temporal-tenses"/>)
+ </bridgehead>
+
<para>A tense indicating distance in time (a long, medium or short time ago or in the future).</para>
<programlisting xml:space="preserve">
- mi puzi citka
- I [past] [short distance] eat.
- I ate a little while ago.
-</programlisting>
+ mi puzi citka
+ I [past] [short distance] eat.
+ I ate a little while ago.
+ </programlisting>
<bridgehead>
- <anchor xml:id="ZIhE"/> selma'o ZIhE (
- <xref linkend="chapter-relative-clauses-section-zihe"/>)</bridgehead>
+ <anchor xml:id="ZIhE"/> selma'o ZIhE (<xref linkend="chapter-relative-clauses-section-zihe"/>)
+ </bridgehead>
+
<para>Joins multiple relative phrases or clauses which apply to the same sumti. Although generally translated with “and”, it is not considered a logical connective.</para>
<programlisting xml:space="preserve">
- mi ponse pa gerku ku poi blabi zi'e noi mi prami ke'a
- I own one dog such-that it-is-white and such-that-incidentally I love it.
- I own a dog that is white and which, incidentally, I love.
- I own a white dog, which I love.
-</programlisting>
+ mi ponse pa gerku ku poi blabi zi'e noi mi prami ke'a
+ I own one dog such-that it-is-white and such-that-incidentally I love it.
+ I own a dog that is white and which, incidentally, I love.
+ I own a white dog, which I love.
+ </programlisting>
<bridgehead>
- <anchor xml:id="ZO"/> selma'o ZO (
- <xref linkend="chapter-structure-section-more-quotations"/>)</bridgehead>
- <para>Single-word quotation: quotes the following single Lojban word.</para>
+ <anchor xml:id="ZO"/> selma'o ZO (<xref linkend="chapter-structure-section-more-quotations"/>)
+ </bridgehead>
+ <para>Single-word quotation: quotes the following single Lojban word.</para>
<programlisting xml:space="preserve">
- zo si cu lojbo valsi
- The-word “si” is-a-Lojbanic word.
-</programlisting>
+ zo si cu lojbo valsi
+ The-word “si” is-a-Lojbanic word.
+ </programlisting>
<bridgehead>
- <anchor xml:id="ZOI"/> selma'o ZOI (
- <xref linkend="chapter-structure-section-more-quotations"/>)</bridgehead>
+ <anchor xml:id="ZOI"/> selma'o ZOI (<xref linkend="chapter-structure-section-more-quotations"/>)
+ </bridgehead>
+
<para>Non-Lojban quotation: quotes any text using a delimiting word (which can be any single Lojban word) placed before and after the text. The delimiting word must not appear in the text, and must be separated from the text by pauses.</para>
<programlisting xml:space="preserve">
- zoi kuot. Socrates is mortal .kuot. cu glico jufra
-
- The-text “Socrates is mortal” is-an-English sentence.
-
-</programlisting>
+ zoi kuot. Socrates is mortal .kuot. cu glico jufra
+ The-text “Socrates is mortal” is-an-English sentence.
+ </programlisting>
<bridgehead>
- <anchor xml:id="ZOhU"/> selma'o ZOhU (
- <xref linkend="chapter-quantifiers-section-da-and-zohu"/>,
- <xref linkend="chapter-structure-section-topic-comments"/>)</bridgehead>
+ <anchor xml:id="ZOhU"/> selma'o ZOhU (<xref linkend="chapter-quantifiers-section-da-and-zohu"/>, <xref linkend="chapter-structure-section-topic-comments"/>)
+ </bridgehead>
+
<para>Separates a logical prenex from a bridi or group of sentences to which it applies. Also separates a topic from a comment in topic/comment sentences.</para>
<programlisting xml:space="preserve">
- su'o da poi remna ro da poi finpe zo'u da prami de
- For-at-least-one X which is-a-man, for-all Ys which are-fish : X loves Y
- There is a man who loves all fish.
-</programlisting>
+ su'o da poi remna ro da poi finpe zo'u da prami de
+ For-at-least-one X which is-a-man, for-all Ys which are-fish : X loves Y
+ There is a man who loves all fish.
+ </programlisting>
</section>
</chapter>
--
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.