[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bpfk] dag-cll git updates for Sun Feb 13 12:21:07 EST 2011
commit 1e83e7bc5533611c4534165e621a2495c42036f9
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date: Sun Feb 13 09:00:01 2011 -0800
automated replacement of – with –, and addition of an entities
file to handle that, and some TODO changes.
diff --git a/todocbook/1.xml b/todocbook/1.xml
index 2b58c1a..68a2708 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
<citetitle pubwork="book">English As We Speak It In Ireland</citetitle>, 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 38d2740..e2754c8 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? –
<valsi>zu'a</valsi> means
<quote>on the left</quote> and
<valsi>vi</valsi> 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"/>
@@ -609,21 +609,21 @@
<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>
@@ -745,21 +745,21 @@
<valsi>vi'u</valsi>. 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
<valsi>vi'e</valsi> 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
<valsi>vi'e</valsi> 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>
@@ -841,21 +841,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
<valsi>roi</valsi></title>
<para>The following cmavo are discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>di'i</cmavo>
@@ -1086,21 +1086,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
<valsi>ze'e</valsi> has a slightly different meaning from one that follows another ZEhA cmavo. The compound cmavo
<oldjbophrase>ze'epu</oldjbophrase> signifies the interval stretching from the infinite past to the reference point (wherever the imaginary journey has taken you);
<oldjbophrase>ze'eba</oldjbophrase> is the interval stretching from the reference point to the infinite future. The remaining form,
<oldjbophrase>ze'eca</oldjbophrase>, makes specific the
@@ -1649,21 +1649,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
<oldjbophrase>xelklama</oldjbophrase> 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>
@@ -1809,21 +1809,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
<valsi>ki</valsi> 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>
@@ -2226,21 +2226,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="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>
@@ -2600,21 +2600,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
<valsi>ki</valsi>, 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
<valsi>ka'e</valsi> 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 9c10468..d4a0507 100644
--- a/todocbook/11.xml
+++ b/todocbook/11.xml
@@ -1279,21 +1279,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
<valsi>tu'a</valsi>,
- <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
<valsi>cafne</valsi> 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
<oldjbophrase>djan.</oldjbophrase> 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
<valsi>tu'a</valsi> which transposes an abstract sumti into a concrete one. This is achieved at the selbri level by the cmavo
<valsi>jai</valsi> (of selma'o JAI). This cmavo has more than one function, discussed in
<xref linkend="section-modal-jai"/> and
<xref linkend="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"/>
@@ -1325,21 +1325,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
- <valsi>jai</valsi> modifies the selbri and can be incorporated into the description – not so for
+ <valsi>jai</valsi> modifies the selbri and can be incorporated into the description – not so for
<valsi>tu'a</valsi>.</para>
<para>The weakness of
<valsi>jai</valsi> 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
<valsi>jai</valsi> explained in
<xref linkend="section-modal-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 f67d595..64ac227 100644
--- a/todocbook/12.xml
+++ b/todocbook/12.xml
@@ -36,37 +36,37 @@
<oldjbophrase>fagyfesti</oldjbophrase> is derived from the tanru
<oldjbophrase>fagri festi</oldjbophrase>, it is not equivalent in meaning to it. In particular,
<oldjbophrase>fagyfesti</oldjbophrase> has a distinct place structure of its own, not the same as that of
<valsi>festi</valsi>. (In contrast, the tanru does have the same place structure as
<valsi>festi</valsi>.) The lujvo needs to take account of the places of
<valsi>fagri</valsi> as well. When a tanru is made into a lujvo, there is no equivalent of
<oldjbophrase>be ... bei ... be'o</oldjbophrase> (described in
<xref linkend="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
<valsi>bo</valsi>,
<valsi>ke</valsi>,
<valsi>ke'e</valsi>, or
<valsi>je</valsi>, or conversion or abstraction cmavo such as
<valsi>se</valsi> or
<valsi>nu</valsi>, 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="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
<oldjbophrase>veljvo</oldjbophrase> 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
<oldjbophrase>seltau</oldjbophrase>, and the right (modified) part the
<oldjbophrase>tertau</oldjbophrase>, 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
<oldjbophrase>seltau</oldjbophrase> and
<quote>modified</quote> for
<oldjbophrase>tertau</oldjbophrase> 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><place-structure>x1 goes to destination x2 from origin point x3 via route x4 using means x5</place-structure></para>
</example>
<para>The tanru
<oldjbophrase>klama zdani</oldjbophrase> will also have two places, namely those of
<valsi>zdani</valsi>. Since a
<oldjbophrase>klama zdani</oldjbophrase> is a type of
- <valsi>zdani</valsi>, we can assume that all goer-houses – whatever they may be – are also houses.</para>
+ <valsi>zdani</valsi>, 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:
<oldjbophrase>gerku zdani</oldjbophrase>, literally
<quote>dog house</quote>. A tanru expresses a very loose relation: a
<oldjbophrase>gerku zdani</oldjbophrase> 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
<oldjbophrase>lo gerku zdani</oldjbophrase> 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
<valsi>zdani</valsi> continues to apply.</para>
<para>For something (call it z1) to qualify as a
<oldjbophrase>gerku zdani</oldjbophrase> 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
<oldjbophrase>gerku zdani</oldjbophrase>, as opposed to just
<valsi>zdani</valsi>, there's got to be some relationship (called r) between some place of
<valsi>zdani</valsi> and some place of
<valsi>gerku</valsi>. It doesn't matter which places, because if there's a relationship between some place of
<valsi>zdani</valsi> and any place of
<valsi>gerku</valsi>, then that relationship can be compounded with the relationship between the places of
<valsi>gerku</valsi>- namely,
- <valsi>gerku</valsi> itself – to reach any of the other
+ <valsi>gerku</valsi> itself – to reach any of the other
<valsi>gerku</valsi> 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
<oldjbophrase>gerku zdani</oldjbophrase>. 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
- <valsi>zdani</valsi>. 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
+ <valsi>zdani</valsi>. 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
<oldjbophrase>gerku zdani</oldjbophrase> 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
<oldjbophrase>gerku zdani</oldjbophrase>.</para>
<para>As we have seen, no less than five elements are involved in the definition of
- <oldjbophrase>gerku zdani</oldjbophrase>: 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>
+ <oldjbophrase>gerku zdani</oldjbophrase>: 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 @@
<oldjbophrase>gerku zdani</oldjbophrase>, then the meaning of
<oldjbophrase>gerku zdani</oldjbophrase> changes. So if we understand
<oldjbophrase>gerku zdani</oldjbophrase> as having the same meaning as the English word
<quote>doghouse</quote>, the White House would no longer be a
<oldjbophrase>gerku zdani</oldjbophrase> 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
<oldjbophrase>gerku zdani</oldjbophrase>, the person creating
<oldjbophrase>gerzda</oldjbophrase> 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
<valsi>zdani</valsi> 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
<oldjbophrase>se jbopli</oldjbophrase> or a
<oldjbophrase>te klagau</oldjbophrase> 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
<oldjbophrase>balsoi</oldjbophrase>: 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,
@@ -371,21 +371,21 @@
<valsi>zdani</valsi>, 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
<oldjbophrase>gerzda</oldjbophrase> 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><place-structure>z1 is the house dwelt in by dog z2=g1</place-structure></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>
@@ -851,21 +851,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>
<gloss>(crime inside) go</gloss>
</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,
<oldjbophrase>xaskemcakcurnu</oldjbophrase> 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>
@@ -1122,42 +1122,42 @@
</example>
<para>Now we can transform the veljvo of
<oldjbophrase>nunctikezgau</oldjbophrase> into
<oldjbophrase>nuncti gasnu</oldjbophrase>. 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><place-structure>g1 is the actor in the event n1=g2 of c1 eating c2</place-structure></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
<oldjbophrase>nunctikezgau</oldjbophrase> is:</para>
<example xml:id="example-random-id-9oTP">
<title>
<anchor xml:id="c12e13d4"/>
</title>
<para><place-structure>g1 is the actor in the event of c1 eating c2</place-structure></para>
</example>
<para>There is one further step that can be taken. As we have already seen with
<oldjbophrase>balsoi</oldjbophrase> 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
<valsi>gasnu</valsi> as its tertau will involve an event abstraction either implicitly or explicitly, since that is how the g2 place of
<valsi>gasnu</valsi> is defined.</para>
<para>Therefore, if we assume that
<valsi>nu</valsi> is the type of abstraction one would expect to be a
<oldjbophrase>se gasnu</oldjbophrase>, then the rafsi
<rafsi>nun</rafsi> and
<rafsi>kez</rafsi> in
- <oldjbophrase>nunctikezgau</oldjbophrase> are only telling us what we would already have guessed – that the seltau of a
+ <oldjbophrase>nunctikezgau</oldjbophrase> are only telling us what we would already have guessed – that the seltau of a
<valsi>gasnu</valsi> lujvo is an event. If we drop these rafsi out, and use instead the shorter lujvo
<oldjbophrase>ctigau</oldjbophrase>, 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>/
<oldjbophrase>gasnu lo citka</oldjbophrase>, with the meaning of
<valsi>do</valsi> as
<quote>bring about an event</quote>; so the seltau must refer to an event,
<oldjbophrase>nu citka</oldjbophrase>. The English slang meanings of
@@ -1419,21 +1419,21 @@
<oldjbophrase>xanplimi'e</oldjbophrase>,
<oldjbophrase>mi'erxanpli</oldjbophrase>, and
<oldjbophrase>minkemxanpli</oldjbophrase> respectively.</para>
<para> <indexterm type="general-imported"><primary>latent component</primary></indexterm> Does this make
<oldjbophrase>xanmi'e</oldjbophrase> wrong? By no means. But it does mean that there is a latent component to the meaning of
<oldjbophrase>xanmi'e</oldjbophrase>, the gismu
<valsi>pilno</valsi>, which is not explicit in the veljvo. And it also means that, for a place structure derivation that actually makes sense, rather than being ad-hoc, the Lojbanist should probably go through a derivation for
<oldjbophrase>xancypliminde</oldjbophrase> or one of the other possibilities that is analogous to the analysis of
<oldjbophrase>terlantroge'u</oldjbophrase> above, even if he or she decides to stick with a shorter, more convenient form like
- <oldjbophrase>xanmi'e</oldjbophrase>. In addition, of course, the possibilities of elliptical lujvo increase their potential ambiguity enormously – an unavoidable fact which should be borne in mind.</para>
+ <oldjbophrase>xanmi'e</oldjbophrase>. 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 048d4be..176a2c5 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
<letteral>o</letteral> or
<letteral>i</letteral> from those beginning with
<letteral>u</letteral>, 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
<valsi>cai</valsi>. You could also indicate that you don't care using
<valsi>cu'i</valsi> 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
<valsi>cu'i</valsi>, 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
<oldjbophrase>.ii.iinai</oldjbophrase>- 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>
@@ -1047,21 +1047,21 @@
<oldjbophrase>.o'unairo'a</oldjbophrase>. Some emotions that we label
<quote>stress</quote> in English are expressed in Lojban with
<oldjbophrase>.o'unairo'i</oldjbophrase>. Physical distress can be expressed with
<oldjbophrase>.o'unairo'o</oldjbophrase>, 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,
<oldjbophrase>o'unairo'u</oldjbophrase>. Spiritual discomfort,
<oldjbophrase>o'unaire'e</oldjbophrase>, 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 (
- <oldjbophrase>.eiro'u</oldjbophrase>, for example – look it up).</para>
+ <oldjbophrase>.eiro'u</oldjbophrase>, 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
<valsi>nai</valsi> 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
<valsi>ro'e</valsi>, and if you are feeling anti-social in some non-specific way,
<oldjbophrase>ro'anai</oldjbophrase> 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>
@@ -1244,21 +1244,21 @@
<oldjbophrase>ro'ole'o</oldjbophrase>.
<valsi>le'o</valsi> is also useful in threats as an alternative to
<oldjbophrase>o'onai</oldjbophrase>, 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
<valsi>vu'e</valsi> 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
<oldjbophrase>o'onaivu'e</oldjbophrase>. Note that this is distinct from lack of guilt:
<oldjbophrase>.u'unai</oldjbophrase>.</para>
<para> <indexterm type="lojban-word-imported"><primary>se'i</primary></indexterm> The cmavo
<valsi>se'i</valsi> expresses the difference between selfishness and generosity, for example (in combination with
<diphthong>.au</diphthong>):</para>
<example xml:id="example-random-id-qFxm" role="interlinear-gloss-example">
@@ -1336,21 +1336,21 @@
<valsi>be'u</valsi> 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
<valsi>se'a</valsi> 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>
@@ -1414,21 +1414,21 @@
<oldjbophrase>.ie ge'eru'e</oldjbophrase> 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,
<oldjbophrase>.oinaicu'i ro'ucai</oldjbophrase> expresses a feeling midway between pain (
<diphthong>.oi</diphthong>) and pleasure (
<oldjbophrase>.oinai</oldjbophrase>) which is intensely sexual (
<valsi>ro'u</valsi>) 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
- <valsi>nai</valsi> 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,
+ <valsi>nai</valsi> 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,
<valsi>nai</valsi> 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
<valsi>nai</valsi> negator, the
<valsi>nai</valsi> 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>
@@ -1494,21 +1494,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>
@@ -1523,25 +1523,25 @@
<attitudinal-scale point="cu'i">continue emotion</attitudinal-scale>
<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
<valsi>pei</valsi> 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,
- <valsi>pei</valsi> acts like other Lojban question words – it requests the respondent to
+ <valsi>pei</valsi> 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
- <valsi>ge'e</valsi>, however, is always in order – you are not required to answer emotionally. This is not the same as
+ <valsi>ge'e</valsi>, however, is always in order – you are not required to answer emotionally. This is not the same as
<oldjbophrase>.i'inai</oldjbophrase>, 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
<valsi>pei</valsi> as a place holder for an intensity marker. (As a result,
<valsi>pei</valsi> 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>
@@ -1627,21 +1627,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
<valsi>dai</valsi>. (Don't confuse empathy with sympathy, which is
<oldjbophrase>.uuse'inai</oldjbophrase>.) 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
- <valsi>dai</valsi>, which attributes the preceding attitudinal to someone else – exactly whom, must be determined from context. You can also use
+ <valsi>dai</valsi>, which attributes the preceding attitudinal to someone else – exactly whom, must be determined from context. You can also use
<valsi>dai</valsi> 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>
@@ -1876,21 +1876,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
- <valsi>ka'u</valsi> 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
+ <valsi>ka'u</valsi> 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,
<valsi>se'o</valsi> 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
<valsi>ka'u</valsi> and
<valsi>se'o</valsi> 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
<valsi>za'a</valsi> is based on perception or direct observation by the speaker. This use of
@@ -2194,21 +2194,21 @@
<quote>broadly construed</quote>; for
<oldjbophrase>do'anai</oldjbophrase> (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
<valsi>pa'e</valsi> is used to claim (truly or falsely) that one is being fair or just to all parties mentioned, whereas
<oldjbophrase>pa'enai</oldjbophrase> 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
<valsi>je'u</valsi> and
- <oldjbophrase>je'unai</oldjbophrase> 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
+ <oldjbophrase>je'unai</oldjbophrase> 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
<oldjbophrase>je'unai</oldjbophrase> be used, or
<valsi>je'u</valsi> be useful? For one thing,
<valsi>je'u</valsi> can be used to mark a tautology: a sentence that is a truth of logic, like
<quote>All cats are cats.</quote> Its counterpart
<oldjbophrase>je'unai</oldjbophrase> then serves to mark a logical contradiction. In addition,
<oldjbophrase>je'unai</oldjbophrase> 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
<valsi>zo'o</valsi> (humor) or
@@ -2589,37 +2589,37 @@
<en>I know who goes to the store.</en>
</interlinear-gloss>
</example>
</section>
<section xml:id="section-vocative-scales">
<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
- <valsi>la</valsi> (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
+ <valsi>la</valsi> (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
<valsi>nai</valsi> 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
<valsi>nai</valsi> 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="section-vocative-syntax"/>; but in brief, a vocative may be followed by a name (without
<valsi>la</valsi>), a description (without
<valsi>le</valsi> or its relatives), a complete sumti, or nothing at all (if the addressee is obvious from the context). There is an elidable terminator,
<valsi>do'u</valsi> (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
<valsi>mi'e</valsi> (explained below) implicitly defines the meaning of the pro-sumti
- <valsi>do</valsi>, 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
+ <valsi>do</valsi>, 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
<valsi>doi</valsi> is the general-purpose vocative. Unlike the cmavo of selma'o COI, explained below,
<valsi>doi</valsi> can precede a name directly without an intervening pause. It is not considered a scale, and
<oldjbophrase valid="false">doinai</oldjbophrase> is not grammatical. In general,
<valsi>doi</valsi> needs no translation in English (we just use names by themselves without any preceding word, although in poetic styles we sometimes say
@@ -3153,24 +3153,24 @@
<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
<valsi>sei</valsi>, explained in
<xref linkend="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>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 81db734..060b204 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
<valsi>ke</valsi>, unavoidable ambiguities would result, so
<valsi>ke</valsi> grouping of sumti is allowed only just after a logical connective. This rule does not apply to
<valsi>tu'e</valsi> 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
<valsi>e</valsi>, 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
<valsi>ge'i</valsi> and
- <valsi>gu'i</valsi> 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
+ <valsi>gu'i</valsi> 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 @@
<valsi>liste</valsi> is a sequence of the things which are mentioned in the list. (It is worth pointing out that
<oldjbophrase>lo liste</oldjbophrase> means a physical object such as a grocery list: a purely abstract list is
<oldjbophrase>lo porsi</oldjbophrase>, a sequence.) Here the three sumti connected by
<valsi>ce'o</valsi> 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
<valsi>joi</valsi>,
<valsi>ce</valsi>, and
<valsi>ce'o</valsi> 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
- <valsi>jo'u</valsi> 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>
+ <valsi>jo'u</valsi> 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
<oldjbophrase>.ije</oldjbophrase> is replaced by
<oldjbophrase>.ijebo</oldjbophrase>, and the tense cmavo
<valsi>ba</valsi> is inserted between
<oldjbophrase>.ije</oldjbophrase> and
<valsi>bo</valsi>:</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 7600931..668053c 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
<valsi>na'e</valsi> 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
<valsi>na'e</valsi> 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
- <valsi>mo</valsi> 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>
+ <valsi>mo</valsi> 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
<valsi>na'e</valsi>):</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:
<rafsi>-kem-</rafsi> is the rafsi for
- <valsi>ke</valsi>, but it is omitted in the final lujvo as superfluous –
+ <valsi>ke</valsi>, but it is omitted in the final lujvo as superfluous –
<valsi>ke'e</valsi> is its own rafsi, and its inclusion in the lujvo implies a
<valsi>ke</valsi> after the
<rafsi>-nal-</rafsi>, since it needs to close something; only a
<valsi>ke</valsi> immediately after the negation would make the
<valsi>ke'e</valsi> meaningful in the tanru expressed in this lujvo.</para>
<para>In a lujvo, it is probably clearest to translate
<rafsi>-nal-</rafsi> as
<quote>non-</quote>, to match the English combining forms, except when the
<valsi>na'e</valsi> 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
<oldjbophrase>nalmle</oldjbophrase>,
<oldjbophrase>normle</oldjbophrase>, and
<oldjbophrase>tolmle</oldjbophrase> 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
- <valsi>to'e</valsi>- what is the opposite of a dog? – while others have more than one, and need
+ <valsi>to'e</valsi>- what is the opposite of a dog? – while others have more than one, and need
<valsi>ci'u</valsi> 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
<oldjbophrase>na'ebo</oldjbophrase> before the sumti. It turns out that a zero quantification serves for contradictory negation. As the cmavo we use implies,
<oldjbophrase>na'ebo</oldjbophrase> forms a scalar negation.</para>
@@ -1083,21 +1083,21 @@
<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,
<valsi>nai</valsi> denotes a polar negation. As discussed in
<xref linkend="section-intensity-scale"/>, most indicators have an implicit scale, and
<valsi>nai</valsi> changes the indicator to refer to the opposite end of the scale. Thus
<oldjbophrase>.uinai</oldjbophrase> expresses unhappiness, and
<oldjbophrase>.ienai</oldjbophrase> expresses disagreement (not ambivalence, which is expressed with the neutral or undecided intensity as
<oldjbophrase>.iecu'i</oldjbophrase>).</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,
@@ -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
<valsi>na</valsi> to the one already there (forming a double negative and hence a positive statement), or does the
<valsi>na</valsi> 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
<valsi>na</valsi> 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 @@
<valsi>na'i</valsi> 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
<valsi>na'i</valsi> to the descriptor
<valsi>lo</valsi> or the
<valsi>poi</valsi> in a
<oldjbophrase>da poi</oldjbophrase>-form sumti. (See
<xref linkend="section-basic-descriptors"/> and
<xref linkend="section-restricted-claims"/> for details on these constructions.) Remember that if a
- <valsi>le</valsi> sumti seems to refer to a non-existent referent, you may not understand what the speaker has in mind – the appropriate response is then
+ <valsi>le</valsi> sumti seems to refer to a non-existent referent, you may not understand what the speaker has in mind – the appropriate response is then
<valsi>ki'a</valsi>, 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
<valsi>ji'u</valsi>;
<oldjbophrase>ji'uku</oldjbophrase> thus explicitly refers to an unexpressed assumption, and
<oldjbophrase>ji'una'iku</oldjbophrase> 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.
<valsi>le'a</valsi> 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
<valsi>jo'a</valsi>, another cmavo of selma'o UI. A common use for
- <valsi>jo'a</valsi> 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>
+ <valsi>jo'a</valsi> 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 edb9b13..e337987 100644
--- a/todocbook/16.xml
+++ b/todocbook/16.xml
@@ -118,21 +118,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
<oldjbophrase>da zo'u</oldjbophrase>, called the prenex, and the part
<oldjbophrase>da viska mi</oldjbophrase>, the main bridi. Almost any Lojban bridi can be preceded by a prenex, which syntactically is any number of sumti followed by the cmavo
<valsi>zo'u</valsi> (of selma'o ZOhU). For the moment, the sumti will consist of one or more of the cmavo
<valsi>da</valsi>,
<valsi>de</valsi>, and
@@ -921,21 +921,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
<oldjbophrase>naku</oldjbophrase> in the prenex, which is identified and compounded by the lexer before looking at the sentence grammar. In Lojban grammar,
<oldjbophrase>naku</oldjbophrase> is then treated like a sumti. In a prenex,
<oldjbophrase>naku</oldjbophrase> 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,
- <oldjbophrase>naku</oldjbophrase> 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
+ <oldjbophrase>naku</oldjbophrase> 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
<valsi>na</valsi> from before the selbri and place
<oldjbophrase>naku</oldjbophrase> 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
<valsi>na</valsi>. The prenex version of
@@ -1523,21 +1523,21 @@
<valsi>nai</valsi>,
<valsi>na</valsi> and
<valsi>se</valsi> 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
<valsi>nai</valsi>,
<valsi>na</valsi> and
<valsi>se</valsi> 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
- <oldjbophrase>naku</oldjbophrase> negation, whenever a logical connective moves in to, or out of, the scope of a negation – when it crosses a negation boundary.</para>
+ <oldjbophrase>naku</oldjbophrase> 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="section-forethought-bridi-connection"/>. It suffices to know that
<valsi>ga</valsi> and
<valsi>gi</valsi>, used before each of a pair of sumti or bridi, mean
<quote>either</quote> and
<quote>or</quote> respectively, and that
<valsi>ge</valsi> and
<valsi>gi</valsi> used similarly mean
<quote>both</quote> and
@@ -1718,21 +1718,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
<valsi>su'o</valsi>; it is ungrammatical to just say
<oldjbophrase>bu'a zo'u</oldjbophrase>. This rule is necessary because only sumti can appear in the prenex, and
- <oldjbophrase>su'o bu'a</oldjbophrase> is technically a sumti – in fact, it is an indefinite description like
+ <oldjbophrase>su'o bu'a</oldjbophrase> is technically a sumti – in fact, it is an indefinite description like
<oldjbophrase>re nanmu</oldjbophrase>, since
<valsi>bu'a</valsi> is grammatically equivalent to a brivla like
<valsi>nanmu</valsi>. 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>
@@ -1770,21 +1770,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
<oldjbophrase>ci da</oldjbophrase> quantifies
<valsi>da</valsi> as referring to three things, which are restricted by the relative clause to be cats. When
- <oldjbophrase>re da</oldjbophrase> appears later, it refers to two of those three things – there is no saying which ones. Further uses of
+ <oldjbophrase>re da</oldjbophrase> appears later, it refers to two of those three things – there is no saying which ones. Further uses of
<valsi>da</valsi> alone, if there were any, would refer once more to the three cats, so the requantification of
<valsi>da</valsi> 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="section-bridi-connection"/>) such as the
<oldjbophrase>.ije</oldjbophrase> in
<xref linkend="example-random-id-x0FP"/>. Theoretically, a bare
<valsi>i</valsi> terminates the scope of the prenex. Informally, however, variables may persist for a while even after an
<valsi>i</valsi>, as if it were an
<oldjbophrase>.ije</oldjbophrase>. 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 bb7d4ec..39f2327 100644
--- a/todocbook/17.xml
+++ b/todocbook/17.xml
@@ -22,21 +22,21 @@
<valsi>lerfu</valsi>, 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
<valsi>lerfu</valsi> 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
<oldjbophrase>lerfu valsi</oldjbophrase> or
<oldjbophrase>lervla</oldjbophrase>.</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
<letteral>y</letteral> 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"/>
@@ -821,21 +821,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.
<oldjbophrase>by. cy.</oldjbophrase> 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
<valsi>boi</valsi> (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
- <valsi>boi</valsi> is to attach a free modifier – subscript, parenthesis, or what have you – to a lerfu string.) The correct version is:</para>
+ <valsi>boi</valsi> 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>
@@ -894,21 +894,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
- <letteral>e</letteral> lerfu rather than fourteen, the translation is not a literal one – but
+ <letteral>e</letteral> 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
<oldjbophrase>lu ... li'u</oldjbophrase> instead of
<valsi>me'o</valsi>, producing:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-pbDf">
<title>
<anchor xml:id="c17e10d4"/>
</title>
@@ -1319,21 +1319,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
<valsi>bu</valsi>, another LAU cmavo (and its required sequel), or a
<oldjbophrase>tei ... foi</oldjbophrase> 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 8cacb0c..f154ce3 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-mekso-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
<valsi>au</valsi>,
<valsi>ei</valsi>,
- <valsi>ai</valsi> 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>
+ <valsi>ai</valsi> 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
<valsi>pi</valsi> 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/19.xml b/todocbook/19.xml
index 2438270..7cfa2c6 100644
--- a/todocbook/19.xml
+++ b/todocbook/19.xml
@@ -98,21 +98,21 @@
<valsi>i</valsi> as a sentence separator, and in addition signals a new topic or paragraph. Grammatically, any number of
<valsi>ni'o</valsi> cmavo can appear consecutively and are equivalent to a single one; semantically, a greater number of
<valsi>ni'o</valsi> cmavo indicates a larger-scale change of topic. This feature allows complexly structured text, with topics, subtopics, and sub-subtopics, to be represented clearly and unambiguously in both spoken and written Lojban. However, some conventional differences do exist between
<valsi>ni'o</valsi> in writing and in conversation.</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>paragraph separation</primary><secondary>written text</secondary></indexterm> <indexterm type="general-imported"><primary>tense</primary><secondary>scope effect of new paragraph</secondary></indexterm> <indexterm type="general-imported"><primary>indicators</primary><secondary>scope effect of new paragraph</secondary></indexterm> <indexterm type="general-imported"><primary>pro-sumti</primary><secondary>scope effect of new paragraph</secondary></indexterm> <indexterm type="general-imported"><primary>pro-bridi</primary><secondary>scope effect of new paragraph</secondary></indexterm> <indexterm type="general-imported"><primary>paragraphs</primary><secondary>effects on scope</secondary></indexterm> <indexterm type="general-imported"><primary>discursive indicator</primary></indexterm> <indexterm type="general-imported"><primary>indicator scope</primary></indexterm> In written text, a single
<valsi>ni'o</valsi> is a mere discursive indicator of a new subject, whereas
<oldjbophrase>ni'oni'o</oldjbophrase> marks a change in the context. In this situation,
<oldjbophrase>ni'oni'o</oldjbophrase> implicitly cancels the definitions of all pro-sumti of selma'o KOhA as well as pro-bridi of selma'o GOhA. (Explicit cancelling is expressed by the cmavo
- <valsi>da'o</valsi> of selma'o DAhO, which has the free grammar of an indicator – it can appear almost anywhere.) The use of
+ <valsi>da'o</valsi> of selma'o DAhO, which has the free grammar of an indicator – it can appear almost anywhere.) The use of
<oldjbophrase>ni'oni'o</oldjbophrase> does not affect indicators (of selma'o UI) or tense references, but
<oldjbophrase>ni'oni'oni'o</oldjbophrase>, indicating a drastic change of topic, would serve to reset both indicators and tenses. (See
<xref linkend="section-attitudinal-scope"/> for a discussion of indicator scope.)</para>
<para> <indexterm type="general-imported"><primary>paragraph separation</primary><secondary>spoken text</secondary></indexterm> <indexterm type="general-imported"><primary>Arabian Nights</primary></indexterm> In spoken text, which is inherently less structured, these levels are reduced by one, with
<valsi>ni'o</valsi> indicating a change in context sufficient to cancel pro-sumti and pro-bridi assignment. On the other hand, in a book, or in stories within stories such as
<quote>The Arabian Nights</quote>, further levels may be expressed by extending the
@@ -430,21 +430,21 @@
<example role="interlinear-gloss-example" xml:id="example-random-id-WUvX">
<title>
<anchor xml:id="c19e5d4"/>
</title>
<interlinear-gloss>
<jbo>le zarci</jbo>
<en>The store.</en>
</interlinear-gloss>
</example>
- <para>A sumti, then, is a legal utterance, although it does not by itself constitute a bridi – it does not claim anything, but merely completes the open-ended claim of the previous bridi.</para>
+ <para>A sumti, then, is a legal utterance, although it does not by itself constitute a bridi – it does not claim anything, but merely completes the open-ended claim of the previous bridi.</para>
<para> <indexterm type="general-imported"><primary>questions</primary><secondary>multiple</secondary></indexterm> There can be two
<valsi>ma</valsi> cmavo in a single question:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-Cx50">
<title>
<anchor xml:id="c19e5d5"/>
</title>
<interlinear-gloss>
<jbo>ma klama ma</jbo>
<en>Who goes where?</en>
</interlinear-gloss>
@@ -532,30 +532,30 @@
</interlinear-gloss>
</example>
<para>Fill-in-the-blank questions may also be asked about: logical connectives (using cmavo
<valsi>ji</valsi> of A,
<valsi>ge'i</valsi> of GA,
<valsi>gi'i</valsi> of GIhA,
<valsi>gu'i</valsi> of GUhA, or
- <valsi>je'i</valsi> of JA, and receiving an ek, gihek, ijek, or ijoik as an answer) – see
+ <valsi>je'i</valsi> of JA, and receiving an ek, gihek, ijek, or ijoik as an answer) – see
<xref linkend="section-truth-and-connective-questions"/>; attitudes (using
- <valsi>pei</valsi> of UI, and receiving an attitudinal as an answer) – see
+ <valsi>pei</valsi> of UI, and receiving an attitudinal as an answer) – see
<xref linkend="section-questions-empathy-contours"/>; place structures (using
- <valsi>fi'a</valsi> of FA, and receiving a cmavo of FA as an answer) – see
+ <valsi>fi'a</valsi> of FA, and receiving a cmavo of FA as an answer) – see
<xref linkend="section-FA"/>; tenses and modals (using
- <valsi>cu'e</valsi> of CUhE, and receiving any tense or BAI cmavo as an answer) – see
+ <valsi>cu'e</valsi> of CUhE, and receiving any tense or BAI cmavo as an answer) – see
<xref linkend="section-BAI"/> and
<xref linkend="chapter-tenses"/>.</para>
<para>Questions can be marked by placing
<valsi>pau</valsi> (of selma'o UI) before the question bridi. See
<xref linkend="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
diff --git a/todocbook/2.xml b/todocbook/2.xml
index 4ffe52b..abc38e4 100644
--- a/todocbook/2.xml
+++ b/todocbook/2.xml
@@ -705,21 +705,21 @@
<para>The cmavo
<valsi>ni'o</valsi> separates paragraphs (covering different topics of discussion). In a long text or utterance, the topical structure of the text may be indicated by multiple
<valsi>ni'o</valsi> s, with perhaps
<oldjbophrase>ni'oni'oni'o</oldjbophrase> used to indicate a chapter,
<oldjbophrase>ni'oni'o</oldjbophrase> to indicate a section, and a single
<valsi>ni'o</valsi> to indicate a subtopic corresponding to a single English paragraph.</para>
<para>The cmavo
<valsi>i</valsi> 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
<valsi>xu</valsi>, discussed in
- <xref linkend="section-basic-questions"/>, 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="section-basic-questions"/>, 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
<valsi>i</valsi> 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
<valsi>i</valsi> 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
<valsi>i</valsi> 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="section-basic-tanru">
<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 f108bbc..93d7bb0 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="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="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 c92892a..6f61e94 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 <quote>non-Lojban</quote> 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 <valsi>zoi</valsi> (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 <quote>
<xref linkend="cll_yacc-699"/></quote> 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 <valsi>zo</valsi> (selma'o ZO) is identified, treat the following Lojban word as a token labelled <quote>
<xref linkend="cll_yacc-698"/></quote>, instead of lexing it by its normal grammatical function.</para>
@@ -34,42 +34,42 @@
<listitem>
<para>If the word <valsi>si</valsi> (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 <valsi>sa</valsi> (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 <valsi>su</valsi> (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 <valsi>su</valsi> 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>
</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 <quote>lexer token</quote> 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"/>
;
/* <quote>words</quote> 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 ed72158..83a6abc 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="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>
+ <xref linkend="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
<letteral>l</letteral>,
<letteral>m</letteral>,
<letteral>n</letteral>, or
@@ -616,21 +616,21 @@
<member><oldjbophrase>y'a</oldjbophrase></member>
<member><oldjbophrase>y'e</oldjbophrase></member>
<member><oldjbophrase>y'i</oldjbophrase></member>
<member><oldjbophrase>y'o</oldjbophrase></member>
<member><oldjbophrase>y'u</oldjbophrase></member>
<member><oldjbophrase>y'y</oldjbophrase></member>
</simplelist>
<para> <indexterm type="general-imported"><primary>vowel pairs</primary><secondary>involving y</secondary></indexterm> Vowel pairs involving
<letteral>y</letteral> appear only in Lojbanized names. They could appear in cmavo (structure words), but only
- <oldjbophrase>.y'y.</oldjbophrase> is so used – it is the Lojban name of the apostrophe letter (see
+ <oldjbophrase>.y'y.</oldjbophrase> is so used – it is the Lojban name of the apostrophe letter (see
<xref linkend="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
<letteral>y</letteral> or which contain a syllabic consonant (
<letteral>l</letteral>,
<letteral>m</letteral>,
<letteral>n</letteral>, or
<letteral>r</letteral>) are never counted. (The Lojban term for penultimate stress is
<oldjbophrase>da'amoi terbasna</oldjbophrase>.) 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
<letteral>y</letteral>, 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
<oldjbophrase>brivla</oldjbophrase>). 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
<valsi>cmavo</valsi>) 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"/>,
<valsi>e'u</valsi> is a cmavo and
<valsi>bridi</valsi> is a brivla. Either of the first two pronunciations is permitted: no primary stress on either syllable of
- <valsi>e'u</valsi>, 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>
+ <valsi>e'u</valsi>, 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 6b99cf5..532ac4b 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="section-clusters"/>. In brief, any consonant pair is permissible unless it: contains two identical letters, contains both a voiced (excluding <letteral>r</letteral>, <letteral>l</letteral>, <letteral>m</letteral>, <letteral>n</letteral>) 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-morphology-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
<oldjbophrase>brivla</oldjbophrase>, 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 @@
<letteral>r</letteral> making up the
<morphology>rs</morphology> consonant pair needed to make the word a brivla. Without the
<letteral>r</letteral>, the word would break up into
<oldjbophrase>soi sai</oldjbophrase>, 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 @@
<valsi>zmadu</valsi>, corresponding in general to English comparative adjectives ending in
<quote>-er</quote> such as
<quote>whiter</quote> (Lojban
<oldjbophrase>labmau</oldjbophrase>). On the other hand,
<valsi>bakri</valsi> (
<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 <valsi>sakli</valsi>. 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>
@@ -934,21 +934,21 @@
<example xml:id="example-random-id-qJDg" role="lujvo-example">
<title>
<anchor xml:id="c4e6d11"/>
</title>
<lujvo-making>
<jbo>lerste</jbo>
<veljvo>lerfu liste</veljvo>
<gloss><quote>letter list</quote> or a <quote>list of letters</quote></gloss>
</lujvo-making>
</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
<letteral>y</letteral> or one of the consonants
<letteral>r</letteral> and
<letteral>n</letteral>. (The letter
<letteral>l</letteral> 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
<letteral>y-</letteral>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
@@ -1117,21 +1117,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
- <oldjbophrase>fukpi valsi</oldjbophrase>) 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>
+ <oldjbophrase>fukpi valsi</oldjbophrase>) 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:
<oldjbophrase>spraile</oldjbophrase> is acceptable, but not
<oldjbophrase valid="false">ktraile</oldjbophrase> or
<oldjbophrase valid="false">trkaile</oldjbophrase>;</para>
</listitem>
<listitem>
<para>must end in one or more vowels;</para>
</listitem>
@@ -1303,22 +1303,22 @@
<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,
<oldjbophrase>spageti</oldjbophrase> and
<oldjbophrase>kuarka</oldjbophrase> are valid Stage 4 fu'ivla, but
<oldjbophrase valid="false">xaceru</oldjbophrase> looks like a compound cmavo, and
<oldjbophrase valid="false">kobra</oldjbophrase> 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
- <oldjbophrase>integrale</oldjbophrase>, 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>
+ <oldjbophrase>integrale</oldjbophrase>, 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,
<oldjbophrase>integrale</oldjbophrase> 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
<oldjbophrase>cmacrntegrale</oldjbophrase>, if the
<letteral>i</letteral> of
<oldjbophrase>integrale</oldjbophrase> is removed, or something like
<oldjbophrase>cmacrnintegrale</oldjbophrase>, if a new consonant is added to the beginning;
@@ -1925,22 +1925,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
<valsi>za'e</valsi> (explained in
<xref linkend="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>
@@ -1993,22 +1993,22 @@
<para>Put a
<letteral>y-</letteral>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
<letteral>y-</letteral>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
<oldjbophrase>tosmabru failure</oldjbophrase>. 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
<letteral>y-</letteral>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 <letteral>y-</letteral>hyphen, or up to the end of the word in case there are no <letteral>y-</letteral>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 3698b23..8f73193 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
<oldjbophrase>mutce bo barda</oldjbophrase> and tertau
<oldjbophrase>gerku bo kavbu</oldjbophrase>. 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
- <citetitle pubwork="book">Word and Object</citetitle> (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
+ <citetitle pubwork="book">Word and Object</citetitle> (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
<valsi>melbi</valsi> 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
<oldjbophrase>blanu zdani</oldjbophrase>. Furthermore,
<oldjbophrase>blanu zdani</oldjbophrase> refers to something which is blue in the way that houses are blue;
- <oldjbophrase>blanu je zdani</oldjbophrase> has no such implication – the blueness of a
+ <oldjbophrase>blanu je zdani</oldjbophrase> has no such implication – the blueness of a
<oldjbophrase>blanu je zdani</oldjbophrase> is independent of its houseness.</para>
<para>With the addition of
<valsi>je</valsi>, 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
<valsi>troci</valsi> 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"/>,
<valsi>mi</valsi> fills the x1 place of
<oldjbophrase>troci co klama</oldjbophrase>, which is the x1 place of
<valsi>troci</valsi>. The other places of the selbri remain unfilled. The trailing sumti
<oldjbophrase>le zarci</oldjbophrase> and
<oldjbophrase>le zdani</oldjbophrase> 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
@@ -1941,21 +1941,21 @@
<xref linkend="example-random-id-qjyW"/> and
<xref linkend="example-random-id-qjyy"/>, which are equivalent in meaning, but use
<valsi>ke</valsi> grouping and
<valsi>bo</valsi> grouping respectively:</para>
<example xml:id="example-random-id-qjyW" role="interlinear-gloss-example">
<title>
<anchor xml:id="c5e12d6"/>
</title>
<interlinear-gloss>
<jbo>mi sutra cadzu be fi le birka be'o je masno klama le zarci</jbo>
- <gloss>I (quickly – (walking using the arms) and slowly) go-to the market.</gloss>
+ <gloss>I (quickly – (walking using the arms) and slowly) go-to the market.</gloss>
<en>I go to the market, both quickly walking using my arms and slowly.</en>
</interlinear-gloss>
</example>
<example xml:id="example-random-id-qjyy" role="interlinear-gloss-example">
<title>
<anchor xml:id="c5e12d7"/>
</title>
<interlinear-gloss>
<jbo>mi ke sutra cadzu be fi le birka [be'o] ke'e je masno klama le zarci</jbo>
<gloss>I ( (quickly (walking using the arms) ) and slowly) go-to the market.</gloss>
@@ -3722,21 +3722,21 @@
<para>The logical connective
<valsi>je</valsi> 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
<valsi>je</valsi> were replaced by
<oldjbophrase>naja</oldjbophrase> or
<valsi>jo</valsi> 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 a138131..2fd1d51 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
<valsi>lei</valsi> and
<valsi>loi</valsi> is that
<oldjbophrase>lei cinfo</oldjbophrase> refers to a mass of specific individuals which the speaker calls lions, whereas
<oldjbophrase>loi cinfo</oldjbophrase> 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
<valsi>le'i</valsi>,
<valsi>lo'i</valsi> and
<valsi>la'i</valsi> correspond exactly to the mass descriptors
<valsi>lei</valsi>,
<valsi>loi</valsi>, and
<valsi>lai</valsi> except that normally we talk of the whole of a set, not just part of it. Here are some examples contrasting
<valsi>lo</valsi>,
@@ -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
<valsi>fadni</valsi> 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
<valsi>fadni</valsi> 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
<valsi>fadni</valsi> 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
<valsi>lo'i</valsi> were changed to
<valsi>lo</valsi> 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
<valsi>pa</valsi>,
<valsi>re</valsi>,
<valsi>ci</valsi>,
<valsi>vo</valsi>, and
<valsi>mu</valsi>, 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,
<oldjbophrase>piro</oldjbophrase> and
<oldjbophrase>pisu'o</oldjbophrase>, 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,
<valsi>lo</valsi>,
<valsi>loi</valsi>,
<valsi>lo'i</valsi>, and
<valsi>lo'e</valsi>) all have an implicit inner quantifier of
<valsi>ro</valsi>, whereas the le-series cmavo all have an implicit inner quantifier of
<valsi>su'o</valsi>.</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
<oldjbophrase>piro</oldjbophrase>, 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
<oldjbophrase>re lei djacu</oldjbophrase>, 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
<valsi>pi</valsi>? It is the Lojban cmavo for the decimal point. Just as
<oldjbophrase>pimu</oldjbophrase> means
<quote><inlinemath>.5</inlinemath></quote>, and when used as a quantifier specifies a portion consisting of five tenths of a thing,
- <oldjbophrase>piro</oldjbophrase> means a portion consisting of the all-ness – the entirety – of a thing. Similarly,
+ <oldjbophrase>piro</oldjbophrase> means a portion consisting of the all-ness – the entirety – of a thing. Similarly,
<oldjbophrase>pisu'o</oldjbophrase> 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
<oldjbophrase>pimu le'i nanmu</oldjbophrase> 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
<oldjbophrase>pimu le nanmu</oldjbophrase> would give us a half-portion of one of them instead! Of course, the result of
<oldjbophrase>pimu le'i nanmu</oldjbophrase> is still a set; if you need to refer to the individuals of the subset, you must say so (see
<valsi>lu'a</valsi> 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
<valsi>ku</valsi> 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
<valsi>lo</valsi>. 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
<oldjbophrase valid="false">*gerku cu blabi</oldjbophrase> is ungrammatical), or which has an explicit inner quantifier (thus
- <oldjbophrase valid="false">*reboi ci gerku cu blabi</oldjbophrase> is also ungrammatical –
+ <oldjbophrase valid="false">*reboi ci gerku cu blabi</oldjbophrase> is also ungrammatical –
<oldjbophrase>re ci gerku cu blabi</oldjbophrase> 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
<oldjbophrase>su'o ci cutci</oldjbophrase>; another version of that example using an explicit
<valsi>lo</valsi> 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>
@@ -1292,21 +1292,21 @@
<jbo>mi viska lu le xunre cmaxirma li'u</jbo>
<gloss>I see [quote] the red small-horse [unquote].</gloss>
</interlinear-gloss>
</example>
<para>But
<xref linkend="example-random-id-6W3v"/> doesn't work: it says that you see a piece of text
<quote>The Red Pony</quote>. That might be all right if you were looking at the cover of the book, where the words
<quote>The Red Pony</quote> are presumably written. (More precisely, where the words
- <oldjbophrase>le xunre cmaxirma</oldjbophrase> are written – but we may suppose the book has been translated into Lojban.)</para>
+ <oldjbophrase>le xunre cmaxirma</oldjbophrase> are written – but we may suppose the book has been translated into Lojban.)</para>
<para>What you really want to say is:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-MSVK">
<title>
<anchor xml:id="c6e10d2"/>
</title>
<interlinear-gloss>
<jbo>mi viska le selsinxa be lu le xunre cmaxirma li'u</jbo>
<gloss>I see the thing-represented-by [quote] the red small-horse [unquote].</gloss>
</interlinear-gloss>
</example>
@@ -1574,23 +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
<valsi>do'u</valsi> (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="section-parentheses"/> – or reciprocals – see
+ <quote>free modifiers</quote> (vocatives, subscripts, utterance ordinals – see
+ <xref linkend="chapter-mekso"/> – metalinguistic comments – see
+ <xref linkend="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>
diff --git a/todocbook/7.xml b/todocbook/7.xml
index 9382213..6b1011c 100644
--- a/todocbook/7.xml
+++ b/todocbook/7.xml
@@ -1041,21 +1041,21 @@
<xref linkend="example-random-id-qdCR"/> and eliminates any possibility of
<valsi>ko'a</valsi> 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
<valsi>go'i</valsi>,
<valsi>go'a</valsi>, and
<valsi>go'u</valsi> follow exactly the same rules as
<valsi>ri</valsi>,
<valsi>ra</valsi>, and
- <valsi>ru</valsi>, 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
+ <valsi>ru</valsi>, 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
<valsi>go'i</valsi> 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 fe12615..52c3833 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
<valsi>ne</valsi> and
<valsi>no'u</valsi> stand to
<valsi>pe</valsi> and
<valsi>po'u</valsi>, respectively, as
<valsi>noi</valsi> does to
<oldjbophrase>poi-</oldjbophrase> 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
<oldjbophrase>lo prenu noi blabi</oldjbophrase> mean? Well, the default inner quantifier is
<valsi>ro</valsi> (meaning
<quote>all</quote>), and the default outer quantifier is
<valsi>su'o</valsi> (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
<valsi>ku</valsi> when attaching a
<valsi>noi</valsi> relative clause to a
<valsi>lo</valsi> 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
<valsi>la</valsi>, 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
<valsi>ku</valsi>, whether before or after the selbri, is reckoned part of the name; a relative clause outside the
<valsi>ku</valsi> 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 1227f80..7e3ba36 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
<oldjbophrase>fi'o se pilno</oldjbophrase> frequently would make many Lojban sentences unnecessarily verbose and clunky, so an abbreviation is provided in the language design: the compound cmavo
<oldjbophrase>sepi'o</oldjbophrase>.</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
<valsi>se</valsi> is used before a cmavo, namely
<valsi>pi'o</valsi>, rather than before a brivla. The meaning of this cmavo, which belongs to selma'o BAI, is exactly the same as that of
<oldjbophrase>fi'o pilno fe'u</oldjbophrase>. Since what we want is a tag based on
<oldjbophrase>se pilno</oldjbophrase> rather than
- <oldjbophrase>pilno-</oldjbophrase> the tool, not the tool user – the grammar allows a BAI cmavo to be converted using a SE cmavo.
+ <oldjbophrase>pilno-</oldjbophrase> 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>
@@ -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
<oldjbophrase>le cukta</oldjbophrase> is set off by the non-elidable
- <valsi>vau</valsi> and is made to belong to both bridi-tails – see
+ <valsi>vau</valsi> and is made to belong to both bridi-tails – see
<xref linkend="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>
diff --git a/todocbook/TODO b/todocbook/TODO
index f7d0bd4..0d1e76b 100644
--- a/todocbook/TODO
+++ b/todocbook/TODO
@@ -1,44 +1,15 @@
All the imported/manual indexterm entries for single words or selma'o need
removing. Might be nice to re-apply * cb87291250fa978bcb67f965bfb880601ce9f367
Chapter 6 lojban-word-importeds. for this.
-How about we split <jbophrase> into <jboword>, <jbophrase>, and
-<jbofragment>? (is fragment quite right? pseudojbo? For things
-that are lojbanic in structure, but not actual words; ktraile or
-rafsi or similar). Basically all are Lojbanic to some extent;
-<jbophrase> are valid unless marked otherwise but have no
-definition because phrasal; <jboword> are valid unless marked
-otherwise and have a definition unless marked otherwise; <pseudojbo>
-is never valid nor has a definition.
-
- There should, however, be a way to mark that morphology fragments
- are valid or not; consider <jbophrase role="morphology"
- valid="false">cc</jbophrase>
-
- What about cmevla? Maybe do <cmene>, <valsi>, ... ?
-
-<!-- FIXME: non-lojban-non-english component of example <jbo>자모
-(from Korean)</jbo> ; how do we mark this? <nonen>? <foreign>? -->
-(from 4.xml): make <en> into <natlang>
-
-zort-: So for things like "<jbo>spageti (Lojbanize)</jbo>", what do you think of <jbo>spageti
-<comment>(Lojbanize)</comment></jbo> or something?
-I was thinking <commentary>, but that seems a bit pointlessly bulky.
-Oh, actually, without the parens at that point; they can get added back in later if we want them.
-By the code.
-
-Replace ’ with '
-
-Replace – with —
-
WRT rafsi: <rafsi type="prefix">man</rafsi> seems best
Will that suck for <member><jbophrase role="rafsi">ger</jbophrase><jbophrase role="rafsi">-zda</jbophrase></member> ?
Let alone <member><jbophrase
role="rafsi">logj</jbophrase><jbophrase
role="rafsi">-bang</jbophrase><jbophrase
role="rafsi">-girz</jbophrase></member>
<jbophrase role="letteral">r-</jbophrase>hyphen -- just wrong
@@ -439,21 +410,21 @@ after their terminators; it doesn't really matter, but it's
annoying.
------
If you see a <quote>...</quote> around Lojban text, replace it with
<jbophrase>...</jbophrase>. There are lots of these.
Also, use <jbophrase valid="false">...</jbophrase> for purposeful na
gendra and <jbophrase valid="iffy">...</jbophrase> for na smudra
-Turn letters, like <quote>l</quote>, into <jbophrase
+Turn Lojban letters, like <quote>l</quote>, into <jbophrase
role="letteral">l</jbophrase> (including ",", ".", and "'").
Similarily we have role="morphology" (consonant clusters),
role="diphthong", and role="rafsi".
------
<programlisting> is bad; change it. If you can't figure out how to
change it, or think it's actually correct in some particular place,
post to the BPFK list.
@@ -509,21 +480,21 @@ All such indexterm entries should end up in the example itself, like so:
<description>start grouping</description>
</cmavo-entry>
...
</cmavo-list>
- also need to wrap the lojban words there in a way that does
indexing, and ideally auto-generation of the cmavo-per-selmaho
lists we want for chapter 20
- does the <cmavo-list> structure achieve this?
- It seems that there is a problem with the cmavo lists at the
beginning of sections having missing entries; in particular, ones
- wwith + in the selma'o, maybe?; they need to be manually checked
+ wwith +/* in the selma'o, maybe?; they need to be manually checked
- lojban words, lojban phrases, terms of art ("abstraction"),
others?... should each have their own index
- cll_chapter5-section1 should be content-words-brivla or so ; those
IDs should not change when things are moved around
- list the members of each selma'o in chapter 20
- make sure the examples that aren't interlinear glosses don't have
that as their role
- so far there's
- pronunciation-example
- compound-cmavo-example
@@ -560,10 +531,11 @@ All such indexterm entries should end up in the example itself, like so:
has the number of the chapter you're in.
==================
Both/Other
==================
- make sure backwards-compatible anchors exist
- Ideally, make sure they are autogenerated as part of the HTML
production.
- Similarily, generate more-readable anchors based on current
section number and such
+�ý5:q!
diff --git a/todocbook/iso-pub.ent b/todocbook/iso-pub.ent
new file mode 100644
index 0000000..033fd24
--- /dev/null
+++ b/todocbook/iso-pub.ent
@@ -0,0 +1,132 @@
+<!-- iso-pub.ent (initially distributed with DocBook XML DTD V4.1.1beta1) -->
+
+<!-- Derived from the corresponding ISO 8879 standard entity set
+ and the Unicode character mappings provided by Sebastian Rahtz -->
+
+<!ENTITY emsp " "> <!-- EM SPACE -->
+<!ENTITY ensp " "> <!-- EN SPACE -->
+<!ENTITY emsp13 " "> <!-- THREE-PER-EM SPACE -->
+<!ENTITY emsp14 " "> <!-- FOUR-PER-EM SPACE -->
+<!ENTITY numsp " "> <!-- FIGURE SPACE -->
+<!ENTITY puncsp " "> <!-- PUNCTUATION SPACE -->
+<!ENTITY thinsp " "> <!-- THIN SPACE -->
+<!ENTITY hairsp " "> <!-- HAIR SPACE -->
+<!ENTITY mdash "—"> <!-- EM DASH -->
+<!ENTITY ndash "–"> <!-- EN DASH -->
+<!ENTITY dash "‐"> <!-- HYPHEN -->
+<!ENTITY blank "␣"> <!-- OPEN BOX -->
+<!ENTITY hellip "…"> <!-- HORIZONTAL ELLIPSIS -->
+<!ENTITY nldr "‥"> <!-- TWO DOT LEADER -->
+<!ENTITY frac13 "⅓"> <!-- VULGAR FRACTION ONE THIRD -->
+<!ENTITY frac23 "⅔"> <!-- VULGAR FRACTION TWO THIRDS -->
+<!ENTITY frac15 "⅕"> <!-- VULGAR FRACTION ONE FIFTH -->
+<!ENTITY frac25 "⅖"> <!-- VULGAR FRACTION TWO FIFTHS -->
+<!ENTITY frac35 "⅗"> <!-- VULGAR FRACTION THREE FIFTHS -->
+<!ENTITY frac45 "⅘"> <!-- VULGAR FRACTION FOUR FIFTHS -->
+<!ENTITY frac16 "⅙"> <!-- VULGAR FRACTION ONE SIXTH -->
+<!ENTITY frac56 "⅚"> <!-- VULGAR FRACTION FIVE SIXTHS -->
+<!ENTITY incare "℅"> <!-- CARE OF -->
+<!ENTITY block "█"> <!-- FULL BLOCK -->
+<!ENTITY uhblk "▀"> <!-- UPPER HALF BLOCK -->
+<!ENTITY lhblk "▄"> <!-- LOWER HALF BLOCK -->
+<!ENTITY blk14 "░"> <!-- LIGHT SHADE -->
+<!ENTITY blk12 "▒"> <!-- MEDIUM SHADE -->
+<!ENTITY blk34 "▓"> <!-- DARK SHADE -->
+<!ENTITY marker "▮"> <!-- BLACK VERTICAL RECTANGLE -->
+<!ENTITY cir "○"> <!-- WHITE CIRCLE -->
+<!ENTITY squ "□"> <!-- WHITE SQUARE -->
+<!ENTITY rect "▭"> <!-- WHITE RECTANGLE -->
+<!ENTITY utri "▵"> <!-- WHITE UP-POINTING TRIANGLE -->
+<!ENTITY dtri "▿"> <!-- WHITE DOWN-POINTING TRIANGLE -->
+<!ENTITY star "⋆"> <!-- STAR OPERATOR -->
+<!ENTITY bull "•"> <!-- BULLET -->
+<!ENTITY squf "▪"> <!-- -->
+<!ENTITY utrif "▴"> <!-- BLACK UP-POINTING TRIANGLE -->
+<!ENTITY dtrif "▾"> <!-- BLACK DOWN-POINTING TRIANGLE -->
+<!ENTITY ltrif "◂"> <!-- BLACK LEFT-POINTING TRIANGLE -->
+<!ENTITY rtrif "▸"> <!-- BLACK RIGHT-POINTING TRIANGLE -->
+<!ENTITY clubs "♣"> <!-- BLACK CLUB SUIT -->
+<!ENTITY diams "♦"> <!-- BLACK DIAMOND SUIT -->
+<!ENTITY hearts "♥"> <!-- BLACK HEART SUIT -->
+<!ENTITY spades "♠"> <!-- BLACK SPADE SUIT -->
+<!ENTITY malt "✠"> <!-- MALTESE CROSS -->
+<!ENTITY dagger "†"> <!-- DAGGER -->
+<!ENTITY Dagger "‡"> <!-- DOUBLE DAGGER -->
+<!ENTITY check "✓"> <!-- CHECK MARK -->
+<!ENTITY cross "✗"> <!-- BALLOT X -->
+<!ENTITY sharp "♯"> <!-- MUSIC SHARP SIGN -->
+<!ENTITY flat "♭"> <!-- MUSIC FLAT SIGN -->
+<!ENTITY male "♂"> <!-- MALE SIGN -->
+<!ENTITY female "♀"> <!-- -->
+<!ENTITY phone "☎"> <!-- TELEPHONE SIGN -->
+<!ENTITY telrec "⌕"> <!-- TELEPHONE RECORDER -->
+<!ENTITY copysr "℗"> <!-- SOUND RECORDING COPYRIGHT -->
+<!ENTITY caret "⁁"> <!-- CARET -->
+<!ENTITY lsquor "‚"> <!-- SINGLE LOW-9 QUOTATION MARK -->
+<!ENTITY ldquor "„"> <!-- DOUBLE LOW-9 QUOTATION MARK -->
+<!ENTITY fflig "ff"> <!-- -->
+<!ENTITY filig "fi"> <!-- -->
+<!-- fjlig Unknown unicode character -->
+<!ENTITY ffilig "ffi"> <!-- -->
+<!ENTITY ffllig "ffl"> <!-- -->
+<!ENTITY fllig "fl"> <!-- -->
+<!ENTITY mldr "…"> <!-- HORIZONTAL ELLIPSIS -->
+<!ENTITY rdquor "“"> <!-- -->
+<!ENTITY rsquor "‘"> <!-- -->
+<!ENTITY vellip "⋮"> <!-- -->
+<!ENTITY hybull "⁃"> <!-- HYPHEN BULLET -->
+<!ENTITY loz "◊"> <!-- LOZENGE -->
+<!ENTITY lozf "✦"> <!-- -->
+<!ENTITY ltri "◃"> <!-- WHITE LEFT-POINTING TRIANGLE -->
+<!ENTITY rtri "▹"> <!-- WHITE RIGHT-POINTING TRIANGLE -->
+<!ENTITY starf "★"> <!-- BLACK STAR -->
+<!ENTITY natur "♮"> <!-- MUSIC NATURAL SIGN -->
+<!ENTITY rx "℞"> <!-- PRESCRIPTION TAKE -->
+<!ENTITY sext "✶"> <!-- SIX POINTED BLACK STAR -->
+<!ENTITY target "⌖"> <!-- POSITION INDICATOR -->
+<!ENTITY dlcrop "⌍"> <!-- BOTTOM LEFT CROP -->
+<!ENTITY drcrop "⌌"> <!-- BOTTOM RIGHT CROP -->
+<!ENTITY ulcrop "⌏"> <!-- TOP LEFT CROP -->
+<!ENTITY urcrop "⌎"> <!-- TOP RIGHT CROP -->
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/todocbook/merge.sh b/todocbook/merge.sh
index 7963e37..8aefb02 100755
--- a/todocbook/merge.sh
+++ b/todocbook/merge.sh
@@ -1,15 +1,17 @@
#!/bin/sh
echo '<?xml version="1.0"?>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V5.0//EN"
- "dtd/docbook-5.0.dtd">
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V5.0//EN" "dtd/docbook-5.0.dtd" [
+ <!ENTITY % iso-pub-ent SYSTEM "iso-pub.ent">
+ %iso-pub-ent;
+]>
<book xmlns:xlink="http://www.w3.org/1999/xlink";>
<!-- THIS FILE IS AUTOGENERATED. DO NOT EDIT OR CHECK IN! -->
' >cll.xml
testing=""
if [ "$1" = "-t" ]
then
--
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.