[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bpfk] dag-cll git updates for Sat Jan 29 22:21:02 EST 2011
commit e0d8a89a76dc736b53192f916430c13034119c1c
Merge: 5519d94 e05f4a6
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date: Sat Jan 29 18:28:43 2011 -0800
Merge commit 'e05f4a6c34635238e6fc8959734ade107b38e53d' into gh-pages
commit 5519d947fcbff94319b1f3a2d10651a3e03805a9
Merge: a67e27b bbf5da6
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date: Sat Jan 29 18:16:06 2011 -0800
Merge commit 'bbf5da6a5b61b4365dc055215f9fa1b411a10c4c' into gh-pages
commit e05f4a6c34635238e6fc8959734ade107b38e53d
Author: Eitan Postavsky <eitanp32@gmail.com>
Date: Wed Jan 5 16:17:46 2011 -0500
Chapter 3: removed redundant <phrase role=ipa>s. Chapter 6: <quote>s to <jbophrase>s and a variablelist to orderedlist.
diff --git a/todocbook/3.xml b/todocbook/3.xml
index 348dc8e..30a227d 100644
--- a/todocbook/3.xml
+++ b/todocbook/3.xml
@@ -1,21 +1,15 @@
<chapter xml:id="chapter-phonology">
<title>The Hills Are Alive With The Sounds Of Lojban</title>
<section xml:id="section-orthography">
<title>Orthography</title>
- <para> <indexterm type="general-imported"><primary>orthography</primary><secondary>relation to pronunciation</secondary></indexterm> <indexterm type="general-imported"><primary>pronunciation</primary><secondary>relation to orthography</secondary></indexterm> <indexterm type="general-imported"><primary>audio-visual isomorphism</primary></indexterm> <indexterm type="general-imported"><primary>isomorphism</primary><secondary>audio-visual</secondary></indexterm> Lojban is designed so that any properly spoken Lojban utterance can be uniquely transcribed in writing, and any properly written Lojban can be spoken so as to be uniquely reproduced by another person. As a consequence, the standard Lojban orthography must assign to each distinct sound, or phoneme, a unique letter or symbol. Each letter or symbol has only one sound or, more accurately, a limited range of sounds that are permitted pronunciations for that phoneme. Some symbols indicate stress (speech emphasis) and pause, which are also essential to Lojban word recognition. In addition, everything that is represented in other languages by punctuation (when written) or by tone of voice (when spoken) is represented in Lojban by words. These two properties together are known technically as
-
-
- <quote>audio-visual isomorphism</quote>.</para>
-
-
-
+ <para> <indexterm type="general-imported"><primary>orthography</primary><secondary>relation to pronunciation</secondary></indexterm> <indexterm type="general-imported"><primary>pronunciation</primary><secondary>relation to orthography</secondary></indexterm> <indexterm type="general-imported"><primary>audio-visual isomorphism</primary></indexterm> <indexterm type="general-imported"><primary>isomorphism</primary><secondary>audio-visual</secondary></indexterm> Lojban is designed so that any properly spoken Lojban utterance can be uniquely transcribed in writing, and any properly written Lojban can be spoken so as to be uniquely reproduced by another person. As a consequence, the standard Lojban orthography must assign to each distinct sound, or phoneme, a unique letter or symbol. Each letter or symbol has only one sound or, more accurately, a limited range of sounds that are permitted pronunciations for that phoneme. Some symbols indicate stress (speech emphasis) and pause, which are also essential to Lojban word recognition. In addition, everything that is represented in other languages by punctuation (when written) or by tone of voice (when spoken) is represented in Lojban by words. These two properties together are known technically as <quote>audio-visual isomorphism</quote>.</para>
<para> <indexterm type="general-imported"><primary>alphabet</primary><secondary>Lojban</secondary></indexterm> <indexterm type="general-imported"><primary>Lojban alphabet</primary></indexterm> <indexterm type="general-imported"><primary>Latin alphabet</primary></indexterm> Lojban uses a variant of the Latin (Roman) alphabet, consisting of the following letters and symbols:
<simplelist type="horiz" columns="26">
<member>'</member>
<member>,</member>
<member>.</member>
<member>a</member>
<member>b</member>
<member>c</member>
<member>d</member>
@@ -351,34 +345,34 @@
<jbophrase role="letteral">r</jbophrase> (discussed later). Commas are never required: no two Lojban words differ solely because of the presence or placement of a comma.</para>
<para> <indexterm type="general-imported"><primary>period</primary><secondary>example of</secondary></indexterm> Here is a somewhat artificial example of the difference in pronunciation between periods, commas and apostrophes. In the English song about Old MacDonald's Farm, the vowel string which is written as
<quote>ee-i-ee-i-o</quote> in English could be Lojbanized with periods as:</para>
<example role="pronunciation-example" xml:id="example-random-id-k2B4">
<title>
<indexterm type="example-imported"><primary>Old McDonald</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c3e3d1"/>
</title>
<pronunciation>
<jbo>.i.ai.i.ai.o</jbo>
- <ipa><phrase role="IPA">[ʔi ʔaj ʔi ʔaj ʔo]</phrase></ipa>
+ <ipa>[ʔi ʔaj ʔi ʔaj ʔo]</ipa>
<en>Ee! Eye! Ee! Eye! Oh!</en>
</pronunciation>
</example>
<para>However, this would sound clipped, staccato, and unmusical compared to the English. Furthermore, although
<xref linkend="example-random-id-k2B4"/> is a string of meaningful Lojban words, as a sentence it makes very little sense. (Note the use of periods embedded within the written word.)</para>
<para> <indexterm type="general-imported"><primary>comma</primary><secondary>example of</secondary></indexterm> If commas were used instead of periods, we could represent the English string as a Lojbanized name, ending in a consonant:</para>
<example role="pronunciation-example" xml:id="example-random-id-k2b9">
<title>
<anchor xml:id="c3e3d2"/>
</title>
<pronunciation>
<jbo>.i,ai,i,ai,on.</jbo>
- <ipa><phrase role="IPA">[ʔi jaj ji jaj jonʔ]</phrase></ipa>
+ <ipa>[ʔi jaj ji jaj jonʔ]</ipa>
</pronunciation>
</example>
<para> <indexterm type="general-imported"><primary>comma</primary><secondary>variant of</secondary></indexterm> The commas represent new syllable breaks, but prohibit the use of pauses or glottal stop. The pronunciation shown is just one possibility, but closely parallels the intended English pronunciation.</para>
<para>However, the use of commas in this way is risky to unambiguous interpretation, since the glides might be heard by some listeners as diphthongs, producing something like</para>
<example role="pronunciation-example" xml:id="example-random-id-dQfn">
<title>
<anchor xml:id="c3e3d3"/>
</title>
<pronunciation>
@@ -388,21 +382,21 @@
<para>which is technically a different Lojban name. Since the intent with Lojbanized names is to allow them to be pronounced more like their native counterparts, the comma is allowed to represent vowel glides or some non-Lojbanic sound. Such an exception affects only spelling accuracy and the ability of a reader to replicate the desired pronunciation exactly; it will not affect the recognition of word boundaries.</para>
<para> <indexterm type="general-imported"><primary>apostrophe</primary><secondary>as preferable over comma in names</secondary></indexterm> Still, it is better if Lojbanized names are always distinct. Therefore, the apostrophe is preferred in regular Lojbanized names that are not attempting to simulate a non-Lojban pronunciation perfectly. (Perfection, in any event, is not really achievable, because some sounds simply lack reasonable Lojbanic counterparts.)</para>
<para>If apostrophes were used instead of commas in
<xref linkend="example-random-id-k2b9"/>, it would appear as:</para>
<example role="pronunciation-example" xml:id="example-random-id-k2bc">
<title>
<anchor xml:id="c3e3d4"/>
</title>
<pronunciation>
<jbo>.i'ai'i'ai'on.</jbo>
- <ipa><phrase role="IPA">[ʔi hai hi hai honʔ]</phrase></ipa>
+ <ipa>[ʔi hai hi hai honʔ]</ipa>
</pronunciation>
</example>
<para> <indexterm type="general-imported"><primary>apostrophe</primary><secondary>example of</secondary></indexterm> which preserves the rhythm and length, if not the exact sounds, of the original English.</para>
</section>
<section xml:id="section-diphthongs">
<title>Diphthongs and Syllabic Consonants</title>
<para> <indexterm type="general-imported"><primary>diphthongs</primary><secondary>definition of</secondary></indexterm> There exist 16 diphthongs in the Lojban language. A diphthong is a vowel sound that consists of two elements, a short vowel sound and a glide, either a labial (IPA
<phrase role="IPA">[w]</phrase>) or palatal (IPA
<phrase role="IPA">[j]</phrase>) glide, that either precedes (an on-glide) or follows (an off-glide) the main vowel. Diphthongs always constitute a single syllable.</para>
<para> <indexterm type="general-imported"><primary>vowels</primary><secondary>contrasted with consonants</secondary></indexterm> <indexterm type="general-imported"><primary>consonants</primary><secondary>contrasted with vowels</secondary></indexterm> For Lojban purposes, a vowel sound is a relatively long speech-sound that forms the nucleus of a syllable. Consonant sounds are relatively brief and normally require an accompanying vowel sound in order to be audible. Consonants may occur at the beginning or end of a syllable, around the vowel, and there may be several consonants in a cluster in either position. Each separate vowel sound constitutes a distinct syllable; consonant sounds do not affect the determination of syllables.</para>
@@ -546,23 +540,23 @@
<jbophrase role="letteral">l</jbophrase>,
<jbophrase role="letteral">m</jbophrase>,
<jbophrase role="letteral">n</jbophrase>, or
<jbophrase role="letteral">r</jbophrase> that is not syllabic, it may not be clear which is which:</para>
<example role="pronunciation-example" xml:id="example-random-id-k2CE">
<title>
<anchor xml:id="c3e4d1"/>
</title>
<pronunciation>
<jbo>brlgan.</jbo>
- <ipa><phrase role="IPA">[br̩l gan]</phrase></ipa>
+ <ipa>[br̩l gan]</ipa>
or <!--FIXME: this gets deleted-->
- <ipa><phrase role="IPA">[brl̩ gan]</phrase></ipa>
+ <ipa>[brl̩ gan]</ipa>
</pronunciation>
</example>
<para>is a hypothetical Lojbanized name with more than one valid pronunciation; however it is pronounced, it remains the same word.</para>
<para> <!--FIXME: there's no example for this "Earl" to go in--><indexterm type="example-imported"><primary>Earl</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>syllabic consonants</primary><secondary>final in word</secondary></indexterm> Syllabic consonants are treated as consonants rather than vowels from the standpoint of Lojban morphology. Thus Lojbanized names, which are generally required to end in a consonant, are allowed to end with a syllabic consonant. An example is
<jbophrase>rl.</jbophrase>, which is an approximation of the English name
<quote>Earl</quote>, and has two syllabic consonants.</para>
<para> <indexterm type="general-imported"><primary>syllabic consonants</primary><secondary>effect on stress</secondary></indexterm> <indexterm type="general-imported"><primary>stress</primary><secondary>effect of syllabic consonants on</secondary></indexterm> Syllables with syllabic consonants and no vowel are never stressed or counted when determining which syllables to stress (see
@@ -767,21 +761,21 @@
<para> <indexterm type="general-imported"><primary>y</primary><secondary>use in avoiding forbidden consonant pairs</secondary></indexterm> These rules apply to all kinds of words, even Lojbanized names. If a name would normally contain a forbidden consonant pair, a
<jbophrase role="letteral">y</jbophrase> can be inserted to break up the pair:
</para>
<example role="pronunciation-example" xml:id="example-random-id-k2cK">
<title>
<indexterm type="example-imported"><primary>James</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c3e6d1"/>
</title>
<pronunciation>
<jbo>djeimyz.</jbo>
- <ipa><phrase role="IPA">[dʒɛj məzʔ]</phrase></ipa>
+ <ipa>[dʒɛj məzʔ]</ipa>
<en>James</en>
</pronunciation>
</example>
<para>The regular English pronunciation of
<quote>James</quote>, which is
<phrase role="IPA">[dʒɛjmz]</phrase>, would Lojbanize as
<jbophrase valid="false">djeimz.</jbophrase>, which contains a forbidden consonant pair.</para>
</section>
<section xml:id="section-initial-pairs">
<title>Initial Consonant Pairs</title>
@@ -1019,127 +1013,127 @@
<phrase role="IPA">[ɨ]</phrase>,
<phrase role="IPA">[ʊ]</phrase>, or even
<phrase role="IPA">[ʏ]</phrase>, but there probably is no universally acceptable buffer sound. When using a consonant buffer, the sound should be made as short as possible. Two examples showing such buffering (we will use
<phrase role="IPA">[ɪ]</phrase> in this chapter) are:</para>
<example role="pronunciation-example" xml:id="example-random-id-k2dg">
<title>
<anchor xml:id="c3e8d1"/>
</title>
<pronunciation>
<jbo>vrusi</jbo>
- <ipa><phrase role="IPA">[ˈvru si]</phrase></ipa>
+ <ipa>[ˈvru si]</ipa>
or <!--FIXME: this gets deleted-->
- <ipa><phrase role="IPA">[vɪ ˈru si]</phrase></ipa>
+ <ipa>[vɪ ˈru si]</ipa>
</pronunciation>
</example>
<example role="pronunciation-example" xml:id="example-random-id-k2dI">
<title>
<anchor xml:id="c3e8d2"/>
<indexterm type="example-imported"><primary>Amsterdam</primary><secondary>example</secondary></indexterm>
</title>
<pronunciation>
<jbo role="pronunciation">.AMsterdam.</jbo>
- <ipa><phrase role="IPA">[ʔam ster damʔ]</phrase></ipa>
+ <ipa>[ʔam ster damʔ]</ipa>
or <!--FIXME: this gets deleted-->
- <ipa><phrase role="IPA">[ˈʔa mɪ sɪ tɛ rɪ da mɪʔ]</phrase></ipa>
+ <ipa>[ˈʔa mɪ sɪ tɛ rɪ da mɪʔ]</ipa>
</pronunciation>
</example>
<para> <indexterm type="general-imported"><primary>stress</primary><secondary>effect of buffer vowel on</secondary></indexterm> <indexterm type="general-imported"><primary>buffer vowel</primary><secondary>and stress</secondary></indexterm> When a buffer vowel is used, it splits each buffered consonant into its own syllable. However, the buffering syllables are never stressed, and are not counted in determining stress. They are, in effect, not really syllables to a Lojban listener, and thus their impact is ignored.</para>
<para>Here are more examples of unbuffered and buffered pronunciations:</para>
<example role="pronunciation-example" xml:id="example-random-id-k2DT">
<title>
<anchor xml:id="c3e8d3"/>
</title>
<pronunciation>
<jbo>klama</jbo>
- <ipa><phrase role="IPA">[ˈkla ma]</phrase></ipa>
- <ipa><phrase role="IPA">[kɪ ˈla ma]</phrase></ipa>
+ <ipa>[ˈkla ma]</ipa>
+ <ipa>[kɪ ˈla ma]</ipa>
</pronunciation>
</example>
<example role="pronunciation-example" xml:id="example-random-id-k2Gg">
<title>
<anchor xml:id="c3e8d4"/>
</title>
<pronunciation>
<jbo>xapcke</jbo>
- <ipa><phrase role="IPA">[ˈxap ʃkɛ]</phrase></ipa>
- <ipa><phrase role="IPA">[ˈxa pɪ ʃkɛ]</phrase></ipa>
- <ipa><phrase role="IPA">[ˈxa pɪ ʃɪ kɛ]</phrase></ipa>
+ <ipa>[ˈxap ʃkɛ]</ipa>
+ <ipa>[ˈxa pɪ ʃkɛ]</ipa>
+ <ipa>[ˈxa pɪ ʃɪ kɛ]</ipa>
</pronunciation>
</example>
<para>In
<xref linkend="example-random-id-k2Gg"/>, we see that buffering vowels can be used in just some, rather than all, of the possible places: the second pronunciation buffers the
<jbophrase role="morphology" valid="false">pc</jbophrase> consonant pair but not the
<jbophrase role="morphology">ck</jbophrase>. The third pronunciation buffers both.</para>
<example role="pronunciation-example" xml:id="example-random-id-k2hN">
<title>
<anchor xml:id="c3e8d5"/>
</title>
<pronunciation>
<jbo>ponyni'u</jbo>
- <ipa><phrase role="IPA">[po nə 'ni hu]</phrase></ipa>
+ <ipa>[po nə 'ni hu]</ipa>
</pronunciation>
</example>
<para> <indexterm type="general-imported"><primary>y sound</primary><secondary>contrasted with vowel buffer</secondary></indexterm> <indexterm type="general-imported"><primary>vowel buffer</primary><secondary>contrasted with y sound</secondary></indexterm>
<xref linkend="example-random-id-k2hN"/> cannot contain any buffering vowel. It is important not to confuse the vowel
<jbophrase role="letteral">y</jbophrase>, which is pronounced
<phrase role="IPA">[ə]</phrase>, with the buffer, which has a variety of possible pronunciations and is never written. Consider the contrast between</para>
<example role="pronunciation-example" xml:id="example-random-id-k2jU">
<title>
<indexterm type="example-imported"><primary>bone bread</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c3e8d6"/>
</title>
<pronunciation>
<jbo>bongynanba</jbo>
- <ipa><phrase role="IPA">[boŋ gə ˈnan ba]</phrase></ipa>
+ <ipa>[boŋ gə ˈnan ba]</ipa>
</pronunciation>
</example>
<para>an unlikely Lojban compound word meaning
<quote>bone bread</quote> (note the use of
<phrase role="IPA">[ŋ]</phrase> as a representative of
<jbophrase role="letteral">n</jbophrase> before
<jbophrase role="letteral">g</jbophrase>) and</para>
<example role="pronunciation-example" xml:id="example-random-id-k2jv">
<title>
<anchor xml:id="c3e8d7"/>
</title>
<pronunciation>
<jbo>bongnanba</jbo>
- <ipa><phrase role="IPA">[boŋ ˈgnan ba]</phrase></ipa>
+ <ipa>[boŋ ˈgnan ba]</ipa>
</pronunciation>
</example>
<para>a possible borrowing from another language (Lojban borrowings can only take a limited form). If
<xref linkend="example-random-id-k2jv"/> were pronounced with buffering, as</para>
<example role="pronunciation-example" xml:id="example-random-id-k2Kb">
<title>
<anchor xml:id="c3e8d8"/>
</title>
<pronunciation>
- <ipa><phrase role="IPA">[boŋ gɪ ˈnan ba]</phrase></ipa>
+ <ipa>[boŋ gɪ ˈnan ba]</ipa>
</pronunciation>
</example>
<para>it would be very similar to
<xref linkend="example-random-id-k2jU"/>. Only a clear distinction between
<jbophrase role="letteral">y</jbophrase> and any buffering vowel would keep the two words distinct.</para>
<para> <indexterm type="general-imported"><primary>buffer vowel</primary><secondary>shortening of</secondary></indexterm> <indexterm type="general-imported"><primary>vowels</primary><secondary>length of</secondary></indexterm> Since buffering is done for the benefit of the speaker in order to aid pronounceability, there is no guarantee that the listener will not mistake a buffer vowel for one of the six regular Lojban vowels. The buffer vowel should be as laxly pronounced as possible, as central as possible, and as short as possible. Furthermore, it is worthwhile for speakers who use buffers to pronounce their regular vowels a bit longer than usual, to avoid confusion with buffer vowels. The speakers of many languages will have trouble correctly hearing any of the suggested buffer vowels otherwise. By this guideline,
<xref linkend="example-random-id-k2Kb"/> would be pronounced</para>
<example role="pronunciation-example" xml:id="example-random-id-k2oF">
<title>
<anchor xml:id="c3e8d9"/>
</title>
<pronunciation>
- <ipa><phrase role="IPA">[boːŋ gɪ ˈnaːn baː]</phrase></ipa>
+ <ipa>[boːŋ gɪ ˈnaːn baː]</ipa>
</pronunciation>
</example>
<para>with lengthened vowels.</para>
</section>
<section xml:id="section-stress">
<title>Syllabication And Stress</title>
<para> <indexterm type="general-imported"><primary>syllabication</primary><secondary>definition of</secondary></indexterm> A Lojban word has one syllable for each of its vowels, diphthongs, and syllabic consonants (referred to simply as
<quote>vowels</quote> for the purposes of this section.) Syllabication rules determine which of the consonants separating two vowels belong to the preceding vowel and which to the following vowel. These rules are conventional only; the phonetic facts of the matter about how utterances are syllabified in any language are always very complex.</para>
<para> <indexterm type="general-imported"><primary>syllabication</primary><secondary>rules for</secondary></indexterm> A single consonant always belongs to the following vowel. A consonant pair is normally divided between the two vowels; however, if the pair constitute a valid initial consonant pair, they are normally both assigned to the following vowel. A consonant triple is divided between the first and second consonants. Apostrophes and commas, of course, also represent syllable breaks. Syllabic consonants usually appear alone in their syllables.</para>
@@ -1253,43 +1247,43 @@
</example>
<para>This is a Lojbanized version of the name
<quote>Armstrong</quote>. The final
<jbophrase role="letteral">g</jbophrase> must be explicitly pronounced. With full buffering, the name would be pronounced:</para>
<example role="pronunciation-example" xml:id="example-random-id-k2PA">
<title>
<anchor xml:id="c3e9d8"/>
</title>
<pronunciation>
- <ipa><phrase role="IPA">[ˈʔa rɪ mɪ sɪ tɪ ro nɪ gɪʔ]</phrase></ipa>
+ <ipa>[ˈʔa rɪ mɪ sɪ tɪ ro nɪ gɪʔ]</ipa>
</pronunciation>
</example>
<para>However, there is no need to insert a buffer in every possible place just because it is inserted in one place: partial buffering is also acceptable. In every case, however, the stress remains in the same place: on the first syllable.</para>
<para> <indexterm type="general-imported"><primary>-ng</primary><secondary>Lojban contrasted with English</secondary></indexterm> The English pronunciation of
<quote>Armstrong</quote>, as spelled in English, is not correct by Lojban standards; the letters
<quote>ng</quote> in English represent a velar nasal (IPA
<phrase role="IPA">[ŋ]</phrase>) which is a single consonant. In Lojban,
<jbophrase role="morphology">ng</jbophrase> represents two separate consonants that must both be pronounced; you may not use
<phrase role="IPA">[ŋ]</phrase> to pronounce Lojban
<jbophrase role="morphology">ng</jbophrase>, although
<phrase role="IPA">[ŋg]</phrase> is acceptable. English speakers are likely to have to pronounce the ending with a buffer, as one of the following:</para>
<example role="pronunciation-example" xml:id="example-random-id-k2T5">
<title>
<anchor xml:id="c3e9d9"/>
</title>
<pronunciation>
- <ipa><phrase role="IPA">[ˈʔarm stron gɪʔ]</phrase></ipa>
+ <ipa>[ˈʔarm stron gɪʔ]</ipa>
or <!--FIXME: this gets deleted-->
- <ipa><phrase role="IPA">[ˈʔarm stroŋ gɪʔ]</phrase></ipa>
+ <ipa>[ˈʔarm stroŋ gɪʔ]</ipa>
or even <!--FIXME: this gets deleted-->
- <ipa><phrase role="IPA">[ˈʔarm stro nɪgʔ]</phrase></ipa>
+ <ipa>[ˈʔarm stro nɪgʔ]</ipa>
</pronunciation>
</example>
<para>The normal English pronunciation of the name
<quote>Armstrong</quote> could be Lojbanized as:</para>
<example role="pronunciation-example" xml:id="example-random-id-vY2y">
<title>
<anchor xml:id="c3e9d10"/>
</title>
<pronunciation>
@@ -1879,21 +1873,21 @@
</listitem>
</varlistentry>
</variablelist>
</section>
<section xml:id="section-anglophone-diphthongs">
<title>English Analogues For Lojban Diphthongs</title>
<para> <indexterm type="general-imported"><primary>diphthongs</primary><secondary>English analogues of</secondary></indexterm> Here is a list of English words that contain diphthongs that are similar to the Lojban diphthongs. This list does not constitute an official pronunciation guide; it is intended as a help to English-speakers.</para>
<informaltable>
<tgroup cols="2">
<colspec colnum="1" colname="col1"/>
- <colspec colnum="1" colname="col1"/>
+ <colspec colnum="2" colname="col2"/>
<thead>
<row>
<entry>Lojban</entry>
<entry>English</entry>
</row>
</thead>
<tbody>
<row>
<entry><jbophrase role="diphthong">ai</jbophrase></entry>
<entry><quote>pie</quote></entry>
diff --git a/todocbook/6.xml b/todocbook/6.xml
index 0c79316..7c1a208 100644
--- a/todocbook/6.xml
+++ b/todocbook/6.xml
@@ -14,64 +14,49 @@
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>pro-sumti</primary><secondary>contrasted with description</secondary></indexterm> In
<xref linkend="example-random-id-VKU6"/>,
<jbophrase>mi</jbophrase> and
<jbophrase>le zarci</jbophrase> are the sumti. It is easy to see that these two sumti are not of the same kind:
<jbophrase>mi</jbophrase> is a pro-sumti (the Lojban analogue of a pronoun) referring to the speaker, whereas
<jbophrase>le zarci</jbophrase> is a description which refers to something described as being a market.</para>
<para> <indexterm type="general-imported"><primary>sumti</primary><secondary>kinds of</secondary></indexterm> There are five kinds of simple sumti provided by Lojban:</para>
- <variablelist>
- <varlistentry>
- <term>1)</term>
- <listitem>
- <para> <indexterm type="lojban-word-imported"><primary>le</primary></indexterm> <indexterm type="general-imported"><primary>gadri</primary><secondary>definition</secondary></indexterm> <indexterm type="general-imported"><primary>sumti</primary><secondary>descriptions as</secondary></indexterm> descriptions like
- <jbophrase>le zarci</jbophrase>, which usually begin with a descriptor (called a
- <jbophrase>gadri</jbophrase> in Lojban) such as
-
- <quote>le</quote>;</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>2)</term>
- <listitem>
- <para> <indexterm type="lojban-word-imported"><primary>mi</primary></indexterm> <indexterm type="general-imported"><primary>sumti</primary><secondary>pro-sumti as</secondary></indexterm> pro-sumti, such as
- <jbophrase>mi</jbophrase>;</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>3)</term>
- <listitem>
- <para> <indexterm type="lojban-word-imported"><primary>la</primary></indexterm> <indexterm type="general-imported"><primary>sumti</primary><secondary>names as</secondary></indexterm> names, such as
- <jbophrase>la lojban.</jbophrase>, which usually begin with
- <quote>la</quote>;</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>4)</term>
- <listitem>
- <para> <indexterm type="lojban-word-imported"><primary>zoi</primary></indexterm> <indexterm type="lojban-word-imported"><primary>zo</primary></indexterm> <indexterm type="lojban-word-imported"><primary>le'u</primary></indexterm> <indexterm type="lojban-word-imported"><primary>lu</primary></indexterm> <indexterm type="general-imported"><primary>sumti</primary><secondary>quotations as</secondary></indexterm> quotations, which begin with
- <jbophrase>lu</jbophrase>,
- <quote>le'u</quote>,
- <quote>zo</quote>, or
- <quote>zoi</quote>;</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>5)</term>
- <listitem>
- <para> <indexterm type="lojban-word-imported"><primary>li</primary></indexterm> <indexterm type="general-imported"><primary>sumti</primary><secondary>numbers as</secondary></indexterm> pure numbers, which usually begin with
- <quote>li</quote>.</para>
- </listitem>
- </varlistentry>
- </variablelist>
+ <orderedlist>
+ <listitem>
+ <para> <indexterm type="lojban-word-imported"><primary>le</primary></indexterm> <indexterm type="general-imported"><primary>gadri</primary><secondary>definition</secondary></indexterm> <indexterm type="general-imported"><primary>sumti</primary><secondary>descriptions as</secondary></indexterm> descriptions like
+ <jbophrase>le zarci</jbophrase>, which usually begin with a descriptor (called a
+ <jbophrase>gadri</jbophrase> in Lojban) such as
+
+ <jbophrase>le</jbophrase>;</para>
+ </listitem>
+ <listitem>
+ <para> <indexterm type="lojban-word-imported"><primary>mi</primary></indexterm> <indexterm type="general-imported"><primary>sumti</primary><secondary>pro-sumti as</secondary></indexterm> pro-sumti, such as
+ <jbophrase>mi</jbophrase>;</para>
+ </listitem>
+ <listitem>
+ <para> <indexterm type="lojban-word-imported"><primary>la</primary></indexterm> <indexterm type="general-imported"><primary>sumti</primary><secondary>names as</secondary></indexterm> names, such as
+ <jbophrase>la lojban.</jbophrase>, which usually begin with
+ <jbophrase>la</jbophrase>;</para>
+ </listitem>
+ <listitem>
+ <para> <indexterm type="lojban-word-imported"><primary>zoi</primary></indexterm> <indexterm type="lojban-word-imported"><primary>zo</primary></indexterm> <indexterm type="lojban-word-imported"><primary>le'u</primary></indexterm> <indexterm type="lojban-word-imported"><primary>lu</primary></indexterm> <indexterm type="general-imported"><primary>sumti</primary><secondary>quotations as</secondary></indexterm> quotations, which begin with
+ <jbophrase>lu</jbophrase>,
+ <jbophrase>le'u</jbophrase>,
+ <jbophrase>zo</jbophrase>, or
+ <jbophrase>zoi</jbophrase>;</para>
+ </listitem>
+ <listitem>
+ <para> <indexterm type="lojban-word-imported"><primary>li</primary></indexterm> <indexterm type="general-imported"><primary>sumti</primary><secondary>numbers as</secondary></indexterm> pure numbers, which usually begin with
+ <jbophrase>li</jbophrase>.</para>
+ </listitem>
+ </orderedlist>
<para>Here are a few examples of each kind of sumti:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-Dx1s">
<title>
<anchor xml:id="c6e1d2"/>
</title>
<interlinear-gloss>
<jbo>e'osai ko sarji la lojban.</jbo>
<en>Please support Lojban!</en>
</interlinear-gloss>
</example>
@@ -147,30 +132,30 @@
<title>
<anchor xml:id="c6e2d1"/>
</title>
<interlinear-gloss>
<jbo>le zarci</jbo>
<gloss>one-or-more-specific-things-each-of-which-I-describe-as being-a-market</gloss>
<en>the market</en>
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>le</primary><secondary>compared with English the</secondary></indexterm> The long gloss for
- <quote>le</quote> is of course far too long to use most of the time, and in fact
+ <jbophrase>le</jbophrase> is of course far too long to use most of the time, and in fact
- <quote>le</quote> is quite close in meaning to English
+ <jbophrase>le</jbophrase> is quite close in meaning to English
<quote>the</quote>. It has particular implications, however, which
<quote>the</quote> does not have.</para>
<para> <indexterm type="general-imported"><primary>descriptions</primary><secondary>importance of selbri first place in</secondary></indexterm> <indexterm type="general-imported"><primary>descriptors</primary><secondary>purpose of</secondary></indexterm> The general purpose of all descriptors is to create a sumti which might occur in the x1 place of the selbri belonging to the description. Thus
<jbophrase>le zarci</jbophrase> conveys something which might be found in the x1 place of
<jbophrase>zarci</jbophrase>, namely a market.</para>
<para> <indexterm type="general-imported"><primary>le</primary><secondary>and truth of selbri</secondary></indexterm> <indexterm type="general-imported"><primary>le</primary><secondary>and specificity</secondary></indexterm> <indexterm type="general-imported"><primary>le</primary><secondary>implications of</secondary></indexterm> The specific purpose of
- <quote>le</quote> is twofold. First, it indicates that the speaker has one or more specific markets in mind (whether or not the listener knows which ones they are). Second, it also indicates that the speaker is merely describing the things he or she has in mind as markets, without being committed to the truth of that description.</para>
+ <jbophrase>le</jbophrase> is twofold. First, it indicates that the speaker has one or more specific markets in mind (whether or not the listener knows which ones they are). Second, it also indicates that the speaker is merely describing the things he or she has in mind as markets, without being committed to the truth of that description.</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-ULGC">
<title>
<anchor xml:id="c6e2d2"/>
</title>
<interlinear-gloss>
<jbo>le zarci cu barda</jbo>
<gloss>One-or-more-specific-things-which-I-describe as
<quote>markets</quote> is/are-big.</gloss>
<gloss>The market is big.</gloss>
<en>The markets are big.</en>
@@ -195,63 +180,63 @@
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>le</primary><secondary>in false-to-fact descriptions</secondary></indexterm>
<xref linkend="example-random-id-PutX"/> is not self-contradictory in Lojban, because
<jbophrase>le nanmu</jbophrase> merely means something or other which, for my present purposes, I choose to describe as a man, whether or not it really is a man. A plausible instance would be: someone we had assumed to be a man at a distance turned out to be actually a woman on closer observation.
<xref linkend="example-random-id-PutX"/> is what I would say to point out my observation to you.</para>
<para> <indexterm type="general-imported"><primary>descriptions</primary><secondary>specific</secondary></indexterm> <indexterm type="general-imported"><primary>specific descriptions</primary></indexterm> In all descriptions with
- <quote>le</quote>, the listener is presumed to either know what I have in mind or else not to be concerned at present (perhaps I will give more identifying details later). In particular, I might be pointing at the supposed man or men:
+ <jbophrase>le</jbophrase>, the listener is presumed to either know what I have in mind or else not to be concerned at present (perhaps I will give more identifying details later). In particular, I might be pointing at the supposed man or men:
<xref linkend="example-random-id-PutX"/> would then be perfectly intelligible, since
<jbophrase>le nanmu</jbophrase> merely clarifies that I am pointing at the supposed man, not at a landscape, or a nose, which happens to lie in the same direction.</para>
<para> <indexterm type="lojban-word-imported"><primary>lo</primary></indexterm> <indexterm type="general-imported"><primary>lo</primary><secondary>implications of</secondary></indexterm> <indexterm type="general-imported"><primary>descriptions</primary><secondary>non-specific</secondary></indexterm> <indexterm type="general-imported"><primary>non-specific descriptions</primary></indexterm> The second descriptor dealt with in this section is
- <quote>lo</quote>. Unlike
- <quote>le</quote>,
- <quote>lo</quote> is nonspecific:</para>
+ <jbophrase>lo</jbophrase>. Unlike
+ <jbophrase>le</jbophrase>,
+ <jbophrase>lo</jbophrase> is nonspecific:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-t11z">
<title>
<anchor xml:id="c6e2d4"/>
</title>
<interlinear-gloss>
<jbo>lo zarci</jbo>
<gloss>one-or-more-of-all-the-things-which-really are-markets</gloss>
<gloss>a market</gloss>
<en>some markets</en>
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>lo</primary><secondary>and truth of selbri</secondary></indexterm> <indexterm type="general-imported"><primary>lo</primary><secondary>contrasted with le in truth requirement</secondary></indexterm> <indexterm type="general-imported"><primary>le</primary><secondary>contrasted with lo in truth requirement</secondary></indexterm> <indexterm type="general-imported"><primary>le</primary><secondary>contrasted with lo in specificity</secondary></indexterm> <indexterm type="general-imported"><primary>lo</primary><secondary>contrasted with le in specificity</secondary></indexterm> Again, there are two colloquial English translations. The effect of using
- <quote>lo</quote> in
+ <jbophrase>lo</jbophrase> in
<xref linkend="example-random-id-t11z"/> is to refer generally to one or more markets, without being specific about which. Unlike
<jbophrase>le zarci</jbophrase>,
<jbophrase>lo zarci</jbophrase> must refer to something which actually is a market (that is, which can appear in the x1 place of a truthful bridi whose selbri is
<jbophrase>zarci</jbophrase>). Thus</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-fSxN">
<title>
<anchor xml:id="c6e2d5"/>
</title>
<interlinear-gloss>
<jbo>lo nanmu cu ninmu</jbo>
<gloss>Some man is a woman.</gloss>
<en>Some men are women.</en>
</interlinear-gloss>
</example>
<para>must be false in Lojban, given that there are no objects in the real world which are both men and women. Pointing at some specific men or women would not make
<xref linkend="example-random-id-fSxN"/> true, because those specific individuals are no more both-men-and-women than any others. In general,
- <quote>lo</quote> refers to whatever individuals meet its description.</para>
+ <jbophrase>lo</jbophrase> refers to whatever individuals meet its description.</para>
<para> <indexterm type="lojban-word-imported"><primary>la</primary></indexterm> <indexterm type="general-imported"><primary>la</primary><secondary>use with descriptions contrasted with use before Lojbanized names</secondary></indexterm> <indexterm type="general-imported"><primary>le</primary><secondary>compared with la in specificity</secondary></indexterm> <indexterm type="general-imported"><primary>la</primary><secondary>compared with le in specificity</secondary></indexterm> <indexterm type="general-imported"><primary>la</primary><secondary>implications of</secondary></indexterm> The last descriptor of this section is
- <quote>la</quote>, which indicates that the selbri which follows it has been dissociated from its normal meaning and is being used as a name. Like
- <quote>le</quote> descriptions,
- <quote>la</quote> descriptions are implicitly restricted to those I have in mind. (Do not confuse this use of
- <quote>la</quote> with its use before regular Lojbanized names, which is discussed in
+ <jbophrase>la</jbophrase>, which indicates that the selbri which follows it has been dissociated from its normal meaning and is being used as a name. Like
+ <jbophrase>le</jbophrase> descriptions,
+ <jbophrase>la</jbophrase> descriptions are implicitly restricted to those I have in mind. (Do not confuse this use of
+ <jbophrase>la</jbophrase> with its use before regular Lojbanized names, which is discussed in
<xref linkend="cll_chapter6-section12"/>.) For example:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-PrGp">
<title>
<anchor xml:id="c6e2d6"/>
</title>
<interlinear-gloss>
<jbo>la cribe pu finti le lisri</jbo>
<gloss>The-one-named
<quote>bear</quote> [past] creates the story.</gloss>
<en>Bear wrote the story.</en>
@@ -306,22 +291,22 @@
</example>
<para> <indexterm type="general-imported"><primary>la</primary><secondary>contrasted with lo in implications</secondary></indexterm>
<xref linkend="example-random-id-nXyo"/> is about a specific bear or bearlike thing(s), or thing(s) which the speaker (perhaps whimsically or metaphorically) describes as a bear (or more than one);
<xref linkend="example-random-id-93Yv"/> is about one or more of the really existing, objectively defined bears. In either case, though, each of them must have contributed to the writing of the story, if more than one bear (or
<quote>bear</quote>) is meant.</para>
<para> <indexterm type="general-imported"><primary>descriptions with lo</primary><secondary>teddy bear contrasted with real bear</secondary></indexterm> (The notion of a
<quote>really existing, objectively defined bear</quote> raises certain difficulties. Is a panda bear a
<quote>real bear</quote>? How about a teddy bear? In general, the answer is
<quote>yes</quote>. Lojban gismu are defined as broadly as possible, allowing tanru and lujvo to narrow down the definition. There probably are no necessary and sufficient conditions for defining what is and what is not a bear that can be pinned down with complete precision: the real world is fuzzy. In borderline cases,
- <quote>le</quote> may communicate better than
- <quote>lo</quote>.)</para>
+ <jbophrase>le</jbophrase> may communicate better than
+ <jbophrase>lo</jbophrase>.)</para>
<para>So while
<xref linkend="example-random-id-PrGp"/> could easily be true (there is a real writer named
<quote>Greg Bear</quote>), and
<xref linkend="example-random-id-nXyo"/> could be true if the speaker is sufficiently peculiar in what he or she describes as a bear,
<xref linkend="example-random-id-93Yv"/> is certainly false.</para>
<para>Similarly, compare the following two examples, which are analogous to
<xref linkend="example-random-id-nXyo"/> and
<xref linkend="example-random-id-93Yv"/> respectively:</para>
<example xml:id="example-random-id-qKw7" role="interlinear-gloss-example">
<title>
@@ -341,25 +326,25 @@
<gloss>A human being wrote the story.</gloss>
<en>Some human beings wrote the story.</en>
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>lo</primary><secondary>contrasted with le in implications</secondary></indexterm> <indexterm type="general-imported"><primary>le</primary><secondary>contrasted with lo in implications</secondary></indexterm>
<xref linkend="example-random-id-qKw7"/> says who the author of the story is: one or more particular human beings that the speaker has in mind. If the topic of conversation is the story, then
<xref linkend="example-random-id-qKw7"/> identifies the author as someone who can be pointed out or who has been previously mentioned; whereas if the topic is a person, then
<jbophrase>le remna</jbophrase> is in effect a shorthand reference to that person.
<xref linkend="example-random-id-qKYf"/> merely says that the author is human.</para>
<para> <indexterm type="lojban-word-imported"><primary>ku</primary></indexterm> <indexterm type="general-imported"><primary>ku</primary><secondary>uses of</secondary></indexterm> <indexterm type="general-imported"><primary>cu</primary><secondary>effect on elidability of ku</secondary></indexterm> <indexterm type="general-imported"><primary>ku</primary><secondary>effect of following selbri on elidability of</secondary></indexterm> <indexterm type="general-imported"><primary>ku</primary><secondary>as elidable terminator for descriptions</secondary></indexterm> The elidable terminator for all descriptions is
- <quote>ku</quote>. It can almost always be omitted with no danger of ambiguity. The main exceptions are in certain uses of relative clauses, which are discussed in
+ <jbophrase>ku</jbophrase>. It can almost always be omitted with no danger of ambiguity. The main exceptions are in certain uses of relative clauses, which are discussed in
<xref linkend="chapter-relative-clauses"/>, and in the case of a description immediately preceding the selbri. In this latter case, using an explicit
- <quote>cu</quote> before the selbri makes the
- <quote>ku</quote> unnecessary. There are also a few other uses of
- <quote>ku</quote>: in the compound negator
+ <jbophrase>cu</jbophrase> before the selbri makes the
+ <jbophrase>ku</jbophrase> unnecessary. There are also a few other uses of
+ <jbophrase>ku</jbophrase>: in the compound negator
<jbophrase>naku</jbophrase> (discussed in
<xref linkend="chapter-negation"/>) and to terminate place-structure, tense, and modal tags that do not have associated sumti (discussed in
<xref linkend="chapter-sumti-tcita"/> and
<xref linkend="chapter-tenses"/>).</para>
</section>
<section xml:id="cll_chapter6-section3">
<title>Individuals and masses</title>
<para>The following cmavo are discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
@@ -391,64 +376,64 @@
</title>
<interlinear-gloss>
<jbo>le prenu cu bevri le pipno</jbo>
<gloss>One-or-more-of-those-I-describe-as persons carry the piano.</gloss>
<en>The person(s) carry the piano.</en>
</interlinear-gloss>
</example>
<para>(Of course the second
- <quote>le</quote> should really get the same translation as the first, but I am putting the focus of this discussion on the first
- <quote>le</quote>, the one preceding
+ <jbophrase>le</jbophrase> should really get the same translation as the first, but I am putting the focus of this discussion on the first
+ <jbophrase>le</jbophrase>, the one preceding
<jbophrase>prenu</jbophrase>. I will assume that there is only one piano under discussion.)</para>
<para> <indexterm type="general-imported"><primary>individual objects</primary><secondary>multiple</secondary></indexterm> <indexterm type="general-imported"><primary>multiple individual objects</primary><secondary>meaning of</secondary></indexterm> <indexterm type="general-imported"><primary>le</primary><secondary>meaning of in the plural</secondary></indexterm> <indexterm type="general-imported"><primary>plurals with le</primary><secondary>meaning of</secondary></indexterm> Suppose the context of
<xref linkend="example-random-id-mwhq"/> is such that you can determine that I am talking about three persons. What am I claiming? I am claiming that each of the three persons carried the piano. This claim can be true if the persons carried the piano one at a time, or in turns, or in a variety of other ways. But in order for
<xref linkend="example-random-id-mwhq"/> to be true, I must be willing to assert that person 1 carried the piano, and that person 2 carried the piano, and that person 3 carried the piano.</para>
<para>But suppose I am not willing to claim that. For in fact pianos are heavy, and very few persons can carry a piano all by themselves. The most likely factual situation is that person 1 carried one end of the piano, and person 2 the other end, while person 3 either held up the middle or else supervised the whole operation without actually lifting anything. The correct way of expressing such a situation in Lojban is:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-eCsh">
<title>
<anchor xml:id="c6e3d2"/>
</title>
<interlinear-gloss>
<jbo>lei prenu cu bevri le pipno</jbo>
<en>The-mass-of-one-or-more-of-those-I-describe-as persons carry the piano.</en>
</interlinear-gloss>
</example>
<para> <indexterm type="lojban-word-imported"><primary>lei</primary></indexterm> <indexterm type="example-imported"><primary>piano-moving</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>mass object</primary><secondary>and logical reasoning</secondary></indexterm> <indexterm type="general-imported"><primary>mass object</primary><secondary>properties of</secondary></indexterm> <indexterm type="general-imported"><primary>multiple individual objects</primary><secondary>contrasted with mass object</secondary></indexterm> <indexterm type="general-imported"><primary>mass object</primary><secondary>contrasted with multiple individual objects</secondary></indexterm> Here the same three persons are treated not as individuals, but as a so-called
<quote>mass entity</quote>, or just
<quote>mass</quote>. A mass has the properties of each individual which composes it, and may have other properties of its own as well. This can lead to apparent contradictions. Thus suppose in the piano-moving example above that person 1 has fair skin, whereas person 2 has dark skin. Then it is correct to say that the person-mass has both fair skin and dark skin. Using the mass descriptor
- <quote>lei</quote> signals that ordinary logical reasoning is not applicable: contradictions can be maintained, and all sorts of other peculiarities may exist. However, we can safely say that a mass inherits only the component properties that are relevant to it; it would be ludicrous to say that a mass of two persons is of molecular dimensions, simply because some of the parts (namely, the molecules) of the persons are that small.</para>
+ <jbophrase>lei</jbophrase> signals that ordinary logical reasoning is not applicable: contradictions can be maintained, and all sorts of other peculiarities may exist. However, we can safely say that a mass inherits only the component properties that are relevant to it; it would be ludicrous to say that a mass of two persons is of molecular dimensions, simply because some of the parts (namely, the molecules) of the persons are that small.</para>
<para> <indexterm type="lojban-word-imported"><primary>lai</primary></indexterm> <indexterm type="lojban-word-imported"><primary>loi</primary></indexterm> <indexterm type="general-imported"><primary>lai</primary><secondary>as mass counterpart of lai</secondary></indexterm> <indexterm type="general-imported"><primary>loi</primary><secondary>as mass counterpart of lo</secondary></indexterm> The descriptors
- <quote>loi</quote> and
- <quote>lai</quote> are analogous to
- <quote>lo</quote> and
- <quote>la</quote> respectively, but refer to masses either by property (
- <quote>loi</quote>) or by name (
- <quote>lai</quote>). A classic example of
- <quote>loi</quote> use is:</para>
+ <jbophrase>loi</jbophrase> and
+ <jbophrase>lai</jbophrase> are analogous to
+ <jbophrase>lo</jbophrase> and
+ <jbophrase>la</jbophrase> respectively, but refer to masses either by property (
+ <jbophrase>loi</jbophrase>) or by name (
+ <jbophrase>lai</jbophrase>). A classic example of
+ <jbophrase>loi</jbophrase> use is:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-T1pF">
<title>
<anchor xml:id="c6e3d3"/>
</title>
<interlinear-gloss>
<jbo>loi cinfo cu xabju le fi'ortu'a</jbo>
<gloss>Part-of-the-mass-of-those-which-really are-lions dwell in-the African-land.</gloss>
<gloss>The lion dwells in Africa.</gloss>
<en>Lions dwell in Africa.</en>
</interlinear-gloss>
</example>
<para> <indexterm type="example-imported"><primary>lions in Africa</primary><secondary>example</secondary></indexterm> <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
- <quote>lei</quote> and
- <quote>loi</quote> is that
+ <jbophrase>lei</jbophrase> and
+ <jbophrase>loi</jbophrase> is that
<jbophrase>lei cinfo</jbophrase> refers to a mass of specific individuals which the speaker calls lions, whereas
<jbophrase>loi cinfo</jbophrase> refers to some part of the mass of all those individuals which actually are lions. The restriction to
<quote>some part of the mass</quote> allows statements like
<xref linkend="example-random-id-T1pF"/> to be true even though some lions do not dwell in Africa - they live in various zoos around the world. On the other hand,
<xref linkend="example-random-id-T1pF"/> 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>
<anchor xml:id="c6e3d4"/>
</title>
<interlinear-gloss>
@@ -471,48 +456,48 @@
</title>
<interlinear-gloss>
<jbo>loi matne cu ranti</jbo>
<gloss>Part-of-the-mass-of-that-which-really is-a-quantity-of-butter is-soft.</gloss>
<en>Butter is soft.</en>
</interlinear-gloss>
</example>
<para> <indexterm type="lojban-word-imported"><primary>matne</primary></indexterm> <indexterm type="example-imported"><primary>butter is soft</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>mass object</primary><secondary>as dependent on intention</secondary></indexterm> Of course, some butter is hard (for example, if it is frozen butter), so the
<quote>part-of</quote> implication of
- <quote>loi</quote> becomes once again useful. The reason this mechanism works is that the English words like
+ <jbophrase>loi</jbophrase> becomes once again useful. The reason this mechanism works is that the English words like
<quote>butter</quote>, which are seen as already describing masses, are translated in Lojban by non-mass forms. The place structure of
<jbophrase>matne</jbophrase> is
<quote>x1 is a quantity of butter from source x2</quote>, so the single English word
<quote>butter</quote> is translated as something like
<quote>a part of the mass formed from all the quantities of butter that exist</quote>. (Note that the operation of forming a mass entity does not imply, in Lojban, that the components of the mass are necessarily close to one another or even related in any way other than conceptually. Masses are formed by the speaker's intention to form a mass, and can in principle contain anything.)</para>
<para> <indexterm type="general-imported"><primary>mass name</primary><secondary>use of</secondary></indexterm> The mass name descriptor
- <quote>lai</quote> is used in circumstances where we wish to talk about a mass of things identified by a name which is common to all of them. It is not used to identify a mass by a single name peculiar to it. Thus the mass version of
+ <jbophrase>lai</jbophrase> is used in circumstances where we wish to talk about a mass of things identified by a name which is common to all of them. It is not used to identify a mass by a single name peculiar to it. Thus the mass version of
<xref linkend="example-random-id-fSxN"/>,</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-H8z5">
<title>
<anchor xml:id="c6e3d6"/>
</title>
<interlinear-gloss>
<jbo>lai cribe pu finti le vi cukta</jbo>
<gloss>The-mass-of-those-named
<quote>bear</quote> [past] creates the nearby book.</gloss>
<en>The Bears wrote this book.</en>
</interlinear-gloss>
</example>
<para> <indexterm type="example-imported"><primary>Bears wrote book</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>lai</primary><secondary>contrasted with la in implications</secondary></indexterm> <indexterm type="general-imported"><primary>la</primary><secondary>contrasted with lai in implications</secondary></indexterm> in a context where
<jbophrase>la cribe</jbophrase> would be understood as plural, would mean that either Tom Bear or Fred Bear (to make up some names) might have written the book, or that Tom and Fred might have written it as collaborators. Using
- <quote>la</quote> instead of
- <quote>lai</quote> in
+ <jbophrase>la</jbophrase> instead of
+ <jbophrase>lai</jbophrase> in
<xref linkend="example-random-id-H8z5"/> would give the implication that each of Tom and Fred, considered individually, had written it.</para>
</section>
<section xml:id="cll_chapter6-section4">
<title>Masses and sets</title>
<para>The following cmavo are discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>le'i</cmavo>
<selmaho>LE</selmaho>
<description>the set described as</description>
@@ -526,29 +511,29 @@
<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="lojban-word-imported"><primary>la'i</primary></indexterm> <indexterm type="lojban-word-imported"><primary>lo'i</primary></indexterm> <indexterm type="lojban-word-imported"><primary>le'i</primary></indexterm> <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
- <quote>le'i</quote>,
- <quote>lo'i</quote> and
- <quote>la'i</quote> correspond exactly to the mass descriptors
- <quote>lei</quote>,
- <quote>loi</quote>, and
- <quote>lai</quote> except that normally we talk of the whole of a set, not just part of it. Here are some examples contrasting
- <quote>lo</quote>,
- <quote>loi</quote>, and
- <quote>lo'i</quote>:</para>
+ <jbophrase>le'i</jbophrase>,
+ <jbophrase>lo'i</jbophrase> and
+ <jbophrase>la'i</jbophrase> correspond exactly to the mass descriptors
+ <jbophrase>lei</jbophrase>,
+ <jbophrase>loi</jbophrase>, and
+ <jbophrase>lai</jbophrase> except that normally we talk of the whole of a set, not just part of it. Here are some examples contrasting
+ <jbophrase>lo</jbophrase>,
+ <jbophrase>loi</jbophrase>, and
+ <jbophrase>lo'i</jbophrase>:</para>
<example xml:id="example-random-id-qL1E" role="interlinear-gloss-example">
<title>
<anchor xml:id="c6e4d1"/>
</title>
<interlinear-gloss>
<jbo>lo ratcu cu bunre</jbo>
<gloss>One-or-more-of-those-which-really-are rats are-brown.</gloss>
<en>Some rats are brown.</en>
</interlinear-gloss>
@@ -590,22 +575,22 @@
<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
- <quote>lo'i</quote> were changed to
- <quote>lo</quote> in
+ <jbophrase>lo'i</jbophrase> were changed to
+ <jbophrase>lo</jbophrase> in
<xref linkend="example-random-id-xIXo"/>, the meaning would be something like
<quote>I am typical of some Lojban user</quote>, which is nonsense.</para>
</section>
<section xml:id="cll_chapter6-section5">
<title>Descriptors for typical objects</title>
<para>The following cmavo are discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>lo'e</cmavo>
@@ -616,21 +601,21 @@
<cmavo>le'e</cmavo>
<selmaho>LE</selmaho>
<description>the stereotypical</description>
</cmavo-entry>
</cmavo-list>
<para> <indexterm type="lojban-word-imported"><primary>lo'e</primary></indexterm> As promised in
<xref linkend="cll_chapter6-section3"/>, Lojban has a method for discriminating between
<quote>the lion</quote> who lives in Africa and
<quote>the Englishman</quote> who, generally speaking, doesn't live in Africa even though some Englishmen do. The descriptor
- <quote>lo'e</quote> means
+ <jbophrase>lo'e</jbophrase> means
<quote>the typical</quote>, as in</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-AJKt">
<title>
<anchor xml:id="c6e5d1"/>
</title>
<interlinear-gloss>
<jbo>lo'e cinfo cu xabju le fi'ortu'a</jbo>
<gloss>The-typical lion dwells-in the African-land.</gloss>
<en>The lion dwells in Africa.</en>
</interlinear-gloss>
@@ -646,57 +631,57 @@
<jbo>lo'e glipre cu xabju le fi'ortu'a na.e</jbo>
<gloss>le gligugde</gloss>
<gloss>The-typical English-person dwells-in the African-land (Not!) and</gloss>
<gloss>the English-country.</gloss>
<en>The typical English person dwells not in Africa but in England.</en>
</interlinear-gloss>
</example>
<para> <indexterm type="example-imported"><primary>typical Englishman</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>le'i</primary><secondary>relationship to le'e</secondary></indexterm> <indexterm type="general-imported"><primary>le'e</primary><secondary>relationship to le'i</secondary></indexterm> <indexterm type="general-imported"><primary>lo'i</primary><secondary>relationship to lo'e</secondary></indexterm> <indexterm type="general-imported"><primary>lo'e</primary><secondary>relationship to lo'i</secondary></indexterm> The relationship between
<jbophrase>lo'e cinfo</jbophrase> and
<jbophrase>lo'i cinfo</jbophrase> may be explained thus: the typical lion is an imaginary lion-abstraction which best exemplifies the set of lions. There is a similar relationship between
- <quote>le'e</quote> and
- <quote>le'i</quote>:</para>
+ <jbophrase>le'e</jbophrase> and
+ <jbophrase>le'i</jbophrase>:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-D88V">
<title>
<anchor xml:id="c6e5d3"/>
</title>
<interlinear-gloss>
<jbo>le'e xelso merko cu gusta ponse</jbo>
<gloss>The-stereotypical Greek-type-of American is-a-restaurant-type-of owner.</gloss>
<en>Lots of Greek-Americans own restaurants.</en>
</interlinear-gloss>
</example>
<para> <indexterm type="lojban-word-imported"><primary>le'e</primary></indexterm> <indexterm type="general-imported"><primary>stereotypical</primary><secondary>compared with typical</secondary></indexterm> <indexterm type="general-imported"><primary>typical</primary><secondary>compared with stereotypical</secondary></indexterm> <indexterm type="general-imported"><primary>stereotypical</primary><secondary>as not derogatory in Lojban</secondary></indexterm> <indexterm type="general-imported"><primary>Greek-Americans own restaurants</primary></indexterm> <indexterm type="general-imported"><primary>stereotypical objects</primary></indexterm> Here we are concerned not with the actual set of Greek-Americans, but with the set of those the speaker has in mind, which is typified by one (real or imaginary) who owns a restaurant. The word
<quote>stereotypical</quote> is often derogatory in English, but
- <quote>le'e</quote> need not be derogatory in Lojban: it simply suggests that the example is typical in the speaker's imagination rather than in some objectively agreed-upon way. Of course, different speakers may disagree about what the features of
+ <jbophrase>le'e</jbophrase> need not be derogatory in Lojban: it simply suggests that the example is typical in the speaker's imagination rather than in some objectively agreed-upon way. Of course, different speakers may disagree about what the features of
<quote>the typical lion</quote> are (some would include having a short intestine, whereas others would know nothing of lions' intestines), so the distinction between
<jbophrase>lo'e cinfo</jbophrase> and
<jbophrase>le'e cinfo</jbophrase> may be very fine.</para>
<para>Furthermore,</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-NVFy">
<title>
<anchor xml:id="c6e5d4"/>
</title>
<interlinear-gloss>
<jbo>le'e skina cu se finti ne'i la xali,uyd.</jbo>
<en>The-stereotypical movie is-invented in Hollywood.</en>
</interlinear-gloss>
</example>
<para> <indexterm type="example-imported"><primary>Hollywood</primary><secondary>example</secondary></indexterm> is probably true to an American, but might be false (not the stereotype) to someone living in India or Russia.</para>
<para> <indexterm type="example-imported"><primary>typical Smith</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>name equivalent for "typical"</primary><secondary>rationale for lack of</secondary></indexterm> Note that there is no naming equivalent of
- <quote>lo'e</quote> and
- <quote>le'e</quote>, because there is no need, as a rule, for a
+ <jbophrase>lo'e</jbophrase> and
+ <jbophrase>le'e</jbophrase>, because there is no need, as a rule, for a
<quote>typical George</quote> or a
<quote>typical Smith</quote>. People or things who share a common name do not, in general, have any other common attributes worth mentioning.</para>
</section>
<section xml:id="cll_chapter6-section6">
<title>Quantified sumti</title>
<para>The following cmavo are discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>ro</cmavo>
@@ -982,35 +967,35 @@
<entry>all the stereotypes of the at-least-one described as</entry>
</row>
<row>
<entry><jbophrase>lo'e</jbophrase>:</entry>
<entry><jbophrase>su'o lo'e ro</jbophrase></entry>
<entry>at least one of the types of all those that really are</entry>
</row>
</tbody>
</tgroup>
</informaltable> <para> <indexterm type="general-imported"><primary>le-series cmavo</primary><secondary>as encompassing le-series and la-series descriptors for quantification discussion</secondary></indexterm> <indexterm type="general-imported"><primary>le-series cmavo</primary><secondary>definition</secondary></indexterm> <indexterm type="general-imported"><primary>la-series descriptors</primary><secondary>compared with le-series in implicit quantification</secondary></indexterm> <indexterm type="general-imported"><primary>le-series descriptors</primary><secondary>compared with la-series in implicit quantification</secondary></indexterm> When examined for the first time, this table looks dreadfully arbitrary. In fact, there are quite a few regularities in it. First of all, the la-series (that is, the descriptors
- <quote>la</quote>,
- <quote>lai</quote>, and
- <quote>la'i</quote>) and the le-series (that is, the descriptors
- <quote>le</quote>,
- <quote>lei</quote>,
- <quote>le'i</quote>, and
- <quote>le'e</quote>) always have corresponding implicit quantifiers, so we may subsume the la-series under the le-series for the rest of this discussion:
+ <jbophrase>la</jbophrase>,
+ <jbophrase>lai</jbophrase>, and
+ <jbophrase>la'i</jbophrase>) and the le-series (that is, the descriptors
+ <jbophrase>le</jbophrase>,
+ <jbophrase>lei</jbophrase>,
+ <jbophrase>le'i</jbophrase>, and
+ <jbophrase>le'e</jbophrase>) always have corresponding implicit quantifiers, so we may subsume the la-series under the le-series for the rest of this discussion:
<quote>le-series cmavo</quote> will refer to both the le-series proper and to the la-series.</para>
<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,
- <quote>lo</quote>,
- <quote>loi</quote>,
- <quote>lo'i</quote>, and
- <quote>lo'e</quote>) all have an implicit inner quantifier of
+ <jbophrase>lo</jbophrase>,
+ <jbophrase>loi</jbophrase>,
+ <jbophrase>lo'i</jbophrase>, and
+ <jbophrase>lo'e</jbophrase>) all have an implicit inner quantifier of
<jbophrase>ro</jbophrase>, whereas the le-series cmavo all have an implicit inner quantifier of
<jbophrase>su'o</jbophrase>.</para>
<para> <indexterm type="general-imported"><primary>le-series cmavo</primary><secondary>rationale for implicit inner quantifier</secondary></indexterm> <indexterm type="general-imported"><primary>lo-series cmavo</primary><secondary>rationale for implicit inner quantifier</secondary></indexterm> Why? Because lo-series descriptors always refer to all of the things which really fit into the x1 place of the selbri. They are not restricted by the speaker's intention. Descriptors of the le-series, however, are so restricted, and therefore talk about some number, definite or indefinite, of objects the speaker has in mind - but never less than one.</para>
<para> <indexterm type="lojban-word-imported"><primary>piro</primary></indexterm> <indexterm type="general-imported"><primary>masses</primary><secondary>rule for implicit outer quantifier</secondary></indexterm> <indexterm type="general-imported"><primary>sets</primary><secondary>rule for implicit outer quantifier</secondary></indexterm> Understanding the implicit outer quantifier requires rules of greater subtlety. In the case of mass and set descriptors, a single rule suffices for each: reference to a mass is implicitly a reference to some part of the mass; reference to a set is implicitly a reference to the whole set. Masses and sets are inherently singular objects: it makes no sense to talk about two distinct masses with the same components, or two distinct sets with the same members. Therefore, the largest possible outer quantifier for either a set description or a mass description is
<jbophrase>piro</jbophrase>, the whole of it.</para>
<para> <indexterm type="general-imported"><primary>plural masses</primary><secondary>possible use for</secondary></indexterm> (Pedantically, it is possible that the mass of water molecules composing an ice cube might be thought of as different from the same mass of water molecules in liquid form, in which case we might talk about
<jbophrase>re lei djacu</jbophrase>, two masses of the water-bits I have in mind.)</para>
<para> <indexterm type="lojban-word-imported"><primary>pi</primary></indexterm> <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
<quote>pi-</quote>? It is the Lojban cmavo for the decimal point. Just as
@@ -1019,123 +1004,123 @@
<quote>.5</quote>, and when used as a quantifier specifies a portion consisting of five tenths of a thing,
<jbophrase>piro</jbophrase> means a portion consisting of the all-ness – the entirety - of a thing. Similarly,
<jbophrase>pisu'o</jbophrase> specifies a portion consisting of at least one part of a thing, i.e. some of it.</para>
<para> <indexterm type="general-imported"><primary>portion</primary><secondary>on set contrasted with on individual</secondary></indexterm> <indexterm type="general-imported"><primary>outer quantifiers</primary><secondary>for expressing subsets</secondary></indexterm> <indexterm type="general-imported"><primary>subsets</primary><secondary>expressing with outer quantifiers</secondary></indexterm> Smaller quantifiers are possible for sets, and refer to subsets. Thus
<jbophrase>pimu le'i nanmu</jbophrase> is a subset of the set of men I have in mind; we don't know precisely which elements make up this subset, but it must have half the size of the full set. This is the best way to say
<quote>half of the men</quote>; saying
<jbophrase>pimu le nanmu</jbophrase> would give us a half-portion of one of them instead! Of course, the result of
<jbophrase>pimu le'i nanmu</jbophrase> is still a set; if you need to refer to the individuals of the subset, you must say so (see
- <quote>lu'a</quote> in
+ <jbophrase>lu'a</jbophrase> in
<xref linkend="cll_chapter6-section10"/>).</para>
<para> <indexterm type="general-imported"><primary>lo</primary><secondary>implicit outer quantifier for</secondary></indexterm> <indexterm type="general-imported"><primary>le</primary><secondary>implicit outer quantifier for</secondary></indexterm> <indexterm type="general-imported"><primary>individual descriptors</primary><secondary>different implicit outer quantifiers among</secondary></indexterm> <indexterm type="general-imported"><primary>outer quantifiers</primary><secondary>rationale for differences in implicit quantifier on descriptors</secondary></indexterm> The case of outer quantifiers for individual descriptors (including
- <quote>le</quote>,
- <quote>lo</quote>,
- <quote>la</quote>, and the typical descriptors
- <quote>le'e</quote> and
- <quote>lo'e</quote>) is special. When we refer to specific individuals with
- <quote>le</quote>, we mean to refer to all of those we have in mind, so
+ <jbophrase>le</jbophrase>,
+ <jbophrase>lo</jbophrase>,
+ <jbophrase>la</jbophrase>, and the typical descriptors
+ <jbophrase>le'e</jbophrase> and
+ <jbophrase>lo'e</jbophrase>) is special. When we refer to specific individuals with
+ <jbophrase>le</jbophrase>, we mean to refer to all of those we have in mind, so
<jbophrase>ro</jbophrase> is appropriate as the implicit quantifier, just as it is appropriate for
<jbophrase>do</jbophrase>. Reference to non-specific individuals with
- <quote>lo</quote>, however, is typically to only some of the objects which can be correctly described, and so
+ <jbophrase>lo</jbophrase>, however, is typically to only some of the objects which can be correctly described, and so
<jbophrase>su'o</jbophrase> is the appropriate implicit quantifier, just as for quotations.</para>
<para> <indexterm type="general-imported"><primary>lo</primary><secondary>contrasted with le in implicit quantification</secondary></indexterm> <indexterm type="general-imported"><primary>le</primary><secondary>contrasted with lo in implicit quantification</secondary></indexterm> From the English-speaking point of view, the difference in structure between the following example using
- <quote>le</quote>:</para>
+ <jbophrase>le</jbophrase>:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-f643">
<title>
<anchor xml:id="c6e7d4"/>
</title>
<interlinear-gloss>
<jbo>[ro] le ci gerku cu blabi</jbo>
<gloss>[All-of] those-described-as three dogs are-white.</gloss>
<en>The three dogs are white.</en>
</interlinear-gloss>
</example>
<para>and the corresponding form with
- <quote>lo</quote>:</para>
+ <jbophrase>lo</jbophrase>:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-gr7Y">
<title>
<anchor xml:id="c6e7d5"/>
</title>
<interlinear-gloss>
<jbo>ci lo [ro] gerku cu blabi</jbo>
<gloss>Three-of those-which-are [all] dogs are-white.</gloss>
<en>Three dogs are white.</en>
</interlinear-gloss>
</example>
<para>looks very peculiar. Why is the number
<jbophrase>ci</jbophrase> found as an inner quantifier in
<xref linkend="example-random-id-f643"/> and as an outer quantifier in
<xref linkend="example-random-id-gr7Y"/>? The number of dogs is the same in either case. The answer is that the
<jbophrase>ci</jbophrase> in
<xref linkend="example-random-id-f643"/> is part of the specification: it tells us the actual number of dogs in the group that the speaker has in mind. In
<xref linkend="example-random-id-gr7Y"/>, however, the dogs referred to by
- <quote>... lo gerku</quote> are all the dogs that exist: the outer quantifier then restricts the number to three; which three, we cannot tell. The implicit quantifiers are chosen to avoid claiming too much or too little: in the case of
- <quote>le</quote>, the implicit outer quantifier
+ <jbophrase>... lo gerku</jbophrase> are all the dogs that exist: the outer quantifier then restricts the number to three; which three, we cannot tell. The implicit quantifiers are chosen to avoid claiming too much or too little: in the case of
+ <jbophrase>le</jbophrase>, the implicit outer quantifier
<jbophrase>ro</jbophrase> says that each of the dogs in the restricted group is white; in the case of
- <quote>lo</quote>, the implicit inner quantifier simply says that three dogs, chosen from the group of all the dogs there are, are white.</para>
+ <jbophrase>lo</jbophrase>, the implicit inner quantifier simply says that three dogs, chosen from the group of all the dogs there are, are white.</para>
<para> <indexterm type="general-imported"><primary>lo-series description</primary><secondary>caution on exact numbers as inner quantifiers on</secondary></indexterm> Using exact numbers as inner quantifiers in lo-series descriptions is dangerous, because you are stating that exactly that many things exist which really fit the description. So examples like</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-uYH4">
<title>
<anchor xml:id="c6e7d6"/>
</title>
<interlinear-gloss>
<jbo>[so'o] lo ci gerku cu blabi</jbo>
<en>[some-of] those-which-really-are three dogs are-white</en>
</interlinear-gloss>
</example>
<para>are semantically anomalous;
<xref linkend="example-random-id-uYH4"/> claims that some dog (or dogs) is white, but also that there are just three dogs in the universe!</para>
<para>Nevertheless, inner quantifiers are permitted on
- <quote>lo</quote> descriptors for consistency's sake, and may occasionally be useful.</para>
+ <jbophrase>lo</jbophrase> descriptors for consistency's sake, and may occasionally be useful.</para>
<para>Note that the inner quantifier of
- <quote>le</quote>, even when exact, need not be truthful:
+ <jbophrase>le</jbophrase>, even when exact, need not be truthful:
<jbophrase>le ci nanmu</jbophrase> means
<quote>what I describe as three men</quote>, not
<quote>three of what I describe as men</quote>. This follows from the rule that what is described by a
- <quote>le</quote> description represents the speaker's viewpoint rather than the objective way things are.</para>
+ <jbophrase>le</jbophrase> description represents the speaker's viewpoint rather than the objective way things are.</para>
</section>
<section xml:id="cll_chapter6-section8">
<title>Indefinite descriptions</title>
<para> <indexterm type="general-imported"><primary>descriptors</primary><secondary>omission of</secondary></indexterm> <indexterm type="general-imported"><primary>lo</primary><secondary>omission of</secondary></indexterm> By a quirk of Lojban syntax, it is possible to omit the descriptor
- <quote>lo</quote>, but never any other descriptor, from a description like that of
+ <jbophrase>lo</jbophrase>, but never any other descriptor, from a description like that of
<xref linkend="example-random-id-gr7Y"/>; namely, one which has an explicit outer quantifier but no explicit inner quantifier. The following example:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-EsVd">
<title>
<anchor xml:id="c6e8d1"/>
</title>
<interlinear-gloss>
<jbo>ci gerku [ku] cu blabi</jbo>
<en>Three dogs are white.</en>
</interlinear-gloss>
</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
- <quote>ku</quote> may still be used. The name
+ <jbophrase>ku</jbophrase> may still be used. The name
<quote>indefinite description</quote> for this syntactic form is historically based: of course, it is no more and no less indefinite than its counterpart with an explicit
- <quote>lo</quote>. Indefinite descriptions were introduced into the language in order to imitate the syntax of English and other natural languages.</para>
+ <jbophrase>lo</jbophrase>. Indefinite descriptions were introduced into the language in order to imitate the syntax of English and other natural languages.</para>
<para> <indexterm type="general-imported"><primary>inner quantifier</primary><secondary>in indefinite description</secondary></indexterm> <indexterm type="general-imported"><primary>outer quantifier</primary><secondary>in indefinite description</secondary></indexterm> <indexterm type="general-imported"><primary>indefinite description</primary><secondary>as prohibiting explicit inner quantifier</secondary></indexterm> <indexterm type="general-imported"><primary>indefinite description</primary><secondary>as needing explicit outer quantifier</secondary></indexterm> Indefinite descriptions must fit this mold exactly: there is no way to make one which does not have an explicit outer quantifier (thus
<quote>*gerku cu blabi</quote> is ungrammatical), or which has an explicit inner quantifier (thus
<quote>*reboi ci gerku cu blabi</quote> is also ungrammatical -
<jbophrase>re ci gerku cu blabi</jbophrase> is fine, but means
<quote>23 dogs are white</quote>).</para>
<para>Note:
<xref linkend="example-random-id-gLpy"/> also contains an indefinite description, namely
<jbophrase>su'o ci cutci</jbophrase>; another version of that example using an explicit
- <quote>lo</quote> would be:</para>
+ <jbophrase>lo</jbophrase> would be:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-SMvA">
<title>
<anchor xml:id="c6e8d2"/>
</title>
<interlinear-gloss>
<jbo>mi ponse su'o ci lo cutci</jbo>
<gloss>I possess at-least three things-which-really-are shoes</gloss>
<en>I own three (or more) shoes.</en>
</interlinear-gloss>
</example>
@@ -1281,23 +1266,23 @@ FIXME: the NAhE+BO entries are missing:
<selmaho>LUhU</selmaho>
<description>elidable terminator for LAhE and NAhE+BO</description>
</cmavo-entry>
</cmavo-list>
<para>Well, that's quite a list of cmavo. What are they all about?</para>
<para> <indexterm type="lojban-word-imported"><primary>lu'u</primary></indexterm> <indexterm type="lojban-word-imported"><primary>BO selma'o</primary></indexterm> <indexterm type="general-imported"><primary>lu'u</primary><secondary>as elidable terminator for qualified sumti</secondary></indexterm> <indexterm type="general-imported"><primary>sumti qualifiers</primary><secondary>elidable terminator for qualified sumti</secondary></indexterm> <indexterm type="general-imported"><primary>sumti qualifiers</primary><secondary>external syntax of</secondary></indexterm> <indexterm type="general-imported"><primary>sumti qualifiers</primary><secondary>internal syntax of</secondary></indexterm> <indexterm type="general-imported"><primary>NAhE selma'o</primary></indexterm> <indexterm type="general-imported"><primary>LAhE selma'o</primary></indexterm> The above cmavo and compound cmavo are called the
<quote>sumti qualifiers</quote>. All of them are either single cmavo of selma'o LAhE, or else compound cmavo involving a scalar negation cmavo of selma'o NAhE immediately followed by
- <quote>bo</quote> of selma'o BO. Syntactically, you can prefix a sumti qualifier to any sumti and produce another simple sumti. (You may need to add the elidable terminator
+ <jbophrase>bo</jbophrase> of selma'o BO. Syntactically, you can prefix a sumti qualifier to any sumti and produce another simple sumti. (You may need to add the elidable terminator
- <quote>lu'u</quote> to show where the qualified sumti ends.)</para>
+ <jbophrase>lu'u</jbophrase> to show where the qualified sumti ends.)</para>
<para> <indexterm type="general-imported"><primary>sumti qualifiers</primary><secondary>as short forms for common special cases</secondary></indexterm> Semantically, sumti qualifiers represent short forms of certain common special cases. Suppose you want to say
<quote>I see 'The Red Pony'</quote>, where
<quote>The Red Pony</quote> is the title of a book. How about:</para>
<para> <indexterm type="example-imported"><primary>Red Pony</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>unqualified sumti</primary><secondary>contrasted with qualified sumti</secondary></indexterm> <indexterm type="general-imported"><primary>qualified sumti</primary><secondary>contrasted with unqualified sumti</secondary></indexterm> FIXME: TAG SPOT</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-6W3v">
<title>
<anchor xml:id="c6e10d1"/>
@@ -1336,28 +1321,28 @@ FIXME: the NAhE+BO entries are missing:
<anchor xml:id="c6e10d3"/>
</title>
<interlinear-gloss>
<jbo>mi viska la'e lu le xunre cmaxirma li'u [lu'u]</jbo>
<en>I see the-referent-of [quote] the red small-horse [unquote].</en>
</interlinear-gloss>
</example>
<para> <indexterm type="lojban-word-imported"><primary>la'e</primary></indexterm> <indexterm type="general-imported"><primary>referent</primary><secondary>referring to with la'e</secondary></indexterm> <indexterm type="general-imported"><primary>la'e</primary><secondary>effect of on meaning</secondary></indexterm> <indexterm type="general-imported"><primary>dereferencing a pointer</primary><secondary>with la'e</secondary></indexterm> <indexterm type="general-imported"><primary>la'e</primary><secondary>as short for "le selsinxa be"</secondary></indexterm> So when
- <quote>la'e</quote> is prefixed to a sumti referring to a symbol, it produces a sumti referring to the referent of that symbol. (In computer jargon,
+ <jbophrase>la'e</jbophrase> is prefixed to a sumti referring to a symbol, it produces a sumti referring to the referent of that symbol. (In computer jargon,
- <quote>la'e</quote> dereferences a pointer.)</para>
+ <jbophrase>la'e</jbophrase> dereferences a pointer.)</para>
<para>By introducing a sumti qualifier, we correct a false sentence (
<xref linkend="example-random-id-6W3v"/>), which too closely resembles its literal English equivalent, into a true sentence (
<xref linkend="example-random-id-Ajty"/>), without having to change it overmuch; in particular, the structure remains the same. Most of the uses of sumti qualifiers are of this general kind.</para>
<para> <indexterm type="lojban-word-imported"><primary>lu'e</primary></indexterm> <indexterm type="general-imported"><primary>symbol</primary><secondary>referring to with lu'e</secondary></indexterm> <indexterm type="general-imported"><primary>lu'e</primary><secondary>effect of on meaning</secondary></indexterm> The sumti qualifier
- <quote>lu'e</quote> provides the converse operation: it can be prefixed to a sumti referring to some thing to produce a sumti referring to a sign or symbol for the thing. For example,</para>
+ <jbophrase>lu'e</jbophrase> provides the converse operation: it can be prefixed to a sumti referring to some thing to produce a sumti referring to a sign or symbol for the thing. For example,</para>
<para> <indexterm type="example-imported"><primary>title of book</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>lu'e</primary><secondary>as short for "le sinxa be"</secondary></indexterm> FIXME: TAG SPOT</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-7ytm">
<title>
<anchor xml:id="c6e10d4"/>
</title>
<interlinear-gloss>
<jbo>mi pu cusku lu'e le vi cukta</jbo>
<gloss>I [past] express a-symbol-for the nearby book.</gloss>
<en>I said the title of this book.</en>
</interlinear-gloss>
@@ -1368,29 +1353,29 @@ FIXME: the NAhE+BO entries are missing:
<anchor xml:id="c6e10d5"/>
</title>
<interlinear-gloss>
<jbo>mi pu cusku le sinxa be le vi cukta</jbo>
<en>I [past] express the symbol-for the nearby book.</en>
</interlinear-gloss>
</example>
<para>which is equivalent to
<xref linkend="example-random-id-7ytm"/>, but longer.</para>
<para> <indexterm type="lojban-word-imported"><primary>vu'i</primary></indexterm> <indexterm type="lojban-word-imported"><primary>lu'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>lu'i</primary></indexterm> <indexterm type="lojban-word-imported"><primary>lu'a</primary></indexterm> <indexterm type="lojban-word-imported"><primary>tu'a</primary></indexterm> <indexterm type="general-imported"><primary>sequence</primary><secondary>contrasted with set</secondary></indexterm> <indexterm type="general-imported"><primary>vu'i</primary><secondary>use for creating sequence</secondary></indexterm> <indexterm type="general-imported"><primary>tu'a</primary><secondary>use for forming abstractions</secondary></indexterm> <indexterm type="general-imported"><primary>vu'i</primary><secondary>effect of on meaning</secondary></indexterm> <indexterm type="general-imported"><primary>lu'o</primary><secondary>effect of on meaning</secondary></indexterm> <indexterm type="general-imported"><primary>lu'i</primary><secondary>effect of on meaning</secondary></indexterm> <indexterm type="general-imported"><primary>lu'a</primary><secondary>effect of on meaning</secondary></indexterm> <indexterm type="general-imported"><primary>tu'a</primary><secondary>effect of on meaning</secondary></indexterm> The other sumti qualifiers follow the same rules. The cmavo
- <quote>tu'a</quote> is used in forming abstractions, and is explained more fully in
+ <jbophrase>tu'a</jbophrase> is used in forming abstractions, and is explained more fully in
<xref linkend="chapter-abstractions"/>. The triplet
- <quote>lu'a</quote>,
+ <jbophrase>lu'a</jbophrase>,
- <quote>lu'i</quote>, and
+ <jbophrase>lu'i</jbophrase>, and
- <quote>lu'o</quote> convert between individuals, sets, and masses;
+ <jbophrase>lu'o</jbophrase> convert between individuals, sets, and masses;
- <quote>vu'i</quote> belongs to this group as well, but creates a sequence, which is similar to a set but has a definite order. (The set of John and Charles is the same as the set of Charles and John, but the sequences are different.) Here are some examples:</para>
+ <jbophrase>vu'i</jbophrase> belongs to this group as well, but creates a sequence, which is similar to a set but has a definite order. (The set of John and Charles is the same as the set of Charles and John, but the sequences are different.) Here are some examples:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-ioCu">
<title>
<anchor xml:id="c6e10d6"/>
</title>
<interlinear-gloss>
<jbo>mi troci tu'a le vorme</jbo>
<gloss>I try some-abstraction-about the door.</gloss>
<en>I try (to open) the door.</en>
</interlinear-gloss>
@@ -1438,36 +1423,36 @@ FIXME: the NAhE+BO entries are missing:
<gloss>I in-a-set-with you are-a-set.</gloss>
<gloss>The-mass-of it-last-mentioned is-a-mass.</gloss>
<gloss>The-sequence-of it-last-mentioned is-a-sequence</gloss>
<gloss>The set of you and me is a set.</gloss>
<gloss>The mass of you and me is a mass.</gloss>
<en>The sequence of you and me is a sequence.</en>
</interlinear-gloss>
</example>
<para> <indexterm type="example-imported"><primary>set of rats</primary><secondary>example</secondary></indexterm> (Yes, I know these examples are a bit silly. This set was introduced for completeness, and practical examples are as yet hard to come by.)</para>
<para> <indexterm type="general-imported"><primary>negation sumti qualifiers</primary><secondary>meanings of</secondary></indexterm> <indexterm type="general-imported"><primary>sumti qualifiers</primary><secondary>for negation</secondary></indexterm> Finally, the four sumti qualifiers formed from a cmavo of NAhE and
- <quote>bo</quote> are all concerned with negation, which is discussed in detail in
+ <jbophrase>bo</jbophrase> are all concerned with negation, which is discussed in detail in
<xref linkend="chapter-negation"/>. Here are a few examples of negation sumti qualifiers:</para>
<para> <indexterm type="lojban-word-imported"><primary>na'ebo</primary></indexterm> FIXME: TAG SPOT</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-4Mte">
<title>
<anchor xml:id="c6e10d10"/>
</title>
<interlinear-gloss>
<jbo>mi viska na'ebo le gerku</jbo>
<en>I see something-other-than the dog.</en>
</interlinear-gloss>
</example>
<para>This compound,
- <quote>na'ebo</quote>, is the most common of the four negation sumti qualifiers. The others usually only make sense in the context of repeating, with modifications, something already referred to:</para>
+ <jbophrase>na'ebo</jbophrase>, is the most common of the four negation sumti qualifiers. The others usually only make sense in the context of repeating, with modifications, something already referred to:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-JwCb">
<title>
<anchor xml:id="c6e10d11"/>
</title>
<interlinear-gloss>
<jbo>mi nelci loi glare cidja</jbo>
<gloss>.ije do nelci to'ebo ri</gloss>
<gloss>.ije la djein. nelci no'ebo ra</gloss>
@@ -1548,34 +1533,34 @@ FIXME: the NAhE+BO entries are missing:
<example role="interlinear-gloss-example" xml:id="example-random-id-ULHn">
<title>
<anchor xml:id="c6e11d5"/>
</title>
<interlinear-gloss>
<jbo>doi djan.</jbo>
<en>John!</en>
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>vocative phrase</primary><secondary>implicit descriptor on</secondary></indexterm> <indexterm type="general-imported"><primary>vocative phrase</primary><secondary>with sumti without descriptor</secondary></indexterm> <indexterm type="general-imported"><primary>vocative phrase</primary><secondary>forms of</secondary></indexterm> In place of a name, a description may appear, lacking its descriptor, which is understood to be
- <quote>le</quote>:</para>
+ <jbophrase>le</jbophrase>:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-V530">
<title>
<anchor xml:id="c6e11d6"/>
</title>
<interlinear-gloss>
<jbo>coi xunre pastu nixli</jbo>
<gloss>Hello, (red-type-of dress)-type-of girl.</gloss>
<en>Hello, girl with the red dress!</en>
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>vocative phrase</primary><secondary>explicit quantifiers prohibited on</secondary></indexterm> <indexterm type="general-imported"><primary>vocative phrase</primary><secondary>implicit quantifiers on</secondary></indexterm> The listener need not really be a
<jbophrase>xunre pastu nixli</jbophrase>, as long as she understands herself correctly from the description. (Actually, only a bare selbri can appear; explicit quantifiers are forbidden in this form of vocative, so the implicit quantifiers
- <quote>su'o le ro</quote> are in effect.)</para>
+ <jbophrase>su'o le ro</jbophrase> are in effect.)</para>
<para>Finally, a complete sumti may be used, the most general case.</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-tBTa">
<title>
<anchor xml:id="c6e11d7"/>
</title>
<interlinear-gloss>
<jbo>co'o la bab. .e la noras.</jbo>
<en>Goodbye, Bob and Nora.</en>
</interlinear-gloss>
</example>
@@ -1595,21 +1580,21 @@ FIXME: the NAhE+BO entries are missing:
<example role="interlinear-gloss-example" xml:id="example-random-id-bx2C">
<title>
<anchor xml:id="c6e11d9"/>
</title>
<interlinear-gloss>
<jbo>doi la djan.</jbo>
<en>The-one-named John!</en>
</interlinear-gloss>
</example>
<para> <indexterm type="lojban-word-imported"><primary>DOhU selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>do'u</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
- <quote>do'u</quote> (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
+ <jbophrase>do'u</jbophrase> (of selma'o DOhU), which is rarely needed except when a simple vocative word is being placed somewhere within a bridi. It may also be required when a vocative is placed between a sumti and its relative clause, or when there are a sequence of so-called
<quote>free modifiers</quote> (vocatives, subscripts, utterance ordinals - see
<xref linkend="chapter-mekso"/>- metalinguistic comments - see
<xref linkend="chapter-structure"/>- or reciprocals - see
<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
@@ -1649,23 +1634,23 @@ FIXME: the NAhE+BO entries are missing:
<jbo>djan. meris. djein. .alis.</jbo>
<en>John. Mary. Jane. Alice.</en>
</interlinear-gloss>
</example>
<para>(Note that
<jbophrase>.alis.</jbophrase> begins as well as ends with a pause, because all Lojban words beginning with a vowel must be preceded by a pause. See
<xref linkend="chapter-morphology"/> for more information.)</para>
<para> <indexterm type="general-imported"><primary>names</primary><secondary>with LA descriptor</secondary></indexterm> <indexterm type="general-imported"><primary>names</primary><secondary>in vocative phrase</secondary></indexterm> <indexterm type="general-imported"><primary>names</primary><secondary>uses of</secondary></indexterm> Names of this kind have two basic uses in Lojban: when used in a vocative phrase (see
<xref linkend="cll_chapter6-section11"/>) they indicate who the listener is or should be. When used with a descriptor of selma'o LA, namely
- <quote>la</quote>,
- <quote>lai</quote>, or
- <quote>la'i</quote>, they form sumti which refer to the persons or things known by the name.</para>
+ <jbophrase>la</jbophrase>,
+ <jbophrase>lai</jbophrase>, or
+ <jbophrase>la'i</jbophrase>, they form sumti which refer to the persons or things known by the name.</para>
<example xml:id="example-random-id-qLgw" role="interlinear-gloss-example">
<title>
<anchor xml:id="c6e12d2"/>
</title>
<interlinear-gloss>
<jbo>la djonz. klama le zarci</jbo>
<gloss>Jones goes to-the store.</gloss>
<en>The Joneses go to-the store.</en>
</interlinear-gloss>
</example>
@@ -1682,33 +1667,33 @@ FIXME: the NAhE+BO entries are missing:
</example>
<para>In
<xref linkend="example-random-id-qLgw"/>, the significance is that all the persons (perhaps only one) I mean to refer to by the name
<jbophrase>djonz.</jbophrase> are going to the store. In
<xref linkend="example-random-id-qLHn"/>, the Joneses are massified, and only some part of them needs to be going. Of course, by
<jbophrase>djonz.</jbophrase> I can mean whomever I want: that person need not use the name
<jbophrase>djonz.</jbophrase> at all.</para>
<para> <indexterm type="general-imported"><primary>LA selma'o</primary><secondary>contrasted with LE in use of name-words</secondary></indexterm> <indexterm type="general-imported"><primary>LE selma'o</primary><secondary>contrasted with LA in use of name-words</secondary></indexterm> The sumti in
<xref linkend="example-random-id-qLgw"/> and
<xref linkend="example-random-id-qLHn"/> operate exactly like the similar uses of
- <quote>la</quote> and
- <quote>lai</quote> in
+ <jbophrase>la</jbophrase> and
+ <jbophrase>lai</jbophrase> in
<xref linkend="example-random-id-PrGp"/> and
<xref linkend="example-random-id-H8z5"/> respectively. The only difference is that these descriptors are followed by Lojban name-words. And in fact, the only difference between descriptors of selma'o LA (these three) and of selma'o LE (all the other descriptors) is that the former can be followed by name-words, whereas the latter cannot.</para>
<para> <indexterm type="lojban-word-imported"><primary>la'i</primary></indexterm> <indexterm type="lojban-word-imported"><primary>lai</primary></indexterm> <indexterm type="lojban-word-imported"><primary>la</primary></indexterm> <indexterm type="lojban-word-imported"><primary>LA selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>doi</primary></indexterm> <indexterm type="general-imported"><primary>doi</primary><secondary>effect on necessity for pause before name-word</secondary></indexterm> <indexterm type="general-imported"><primary>LA selma'o</primary><secondary>effect on necessity for pause before name-word</secondary></indexterm> <indexterm type="general-imported"><primary>name-words</primary><secondary>pause requirements before</secondary></indexterm> <indexterm type="general-imported"><primary>name-words</primary><secondary>limitations on</secondary></indexterm> There are certain limitations on the form of name-words in Lojban. In particular, they cannot contain the letter-sequences (or sound-sequences)
- <quote>la</quote>,
- <quote>lai</quote>, or
+ <jbophrase>la</jbophrase>,
+ <jbophrase>lai</jbophrase>, or
<jbophrase>doi</jbophrase> unless a consonant immediately precedes within the name. Reciprocally, every name not preceded by
- <quote>la</quote>,
- <quote>lai</quote>,
- <quote>la'i</quote>, or
+ <jbophrase>la</jbophrase>,
+ <jbophrase>lai</jbophrase>,
+ <jbophrase>la'i</jbophrase>, or
<jbophrase>doi</jbophrase> must be preceded by a pause instead:</para>
<example xml:id="example-random-id-qLiB" role="interlinear-gloss-example">
<title>
<anchor xml:id="c6e12d4"/>
</title>
<interlinear-gloss>
<jbo>coi .djan.</jbo>
<en>Hello, John.</en>
</interlinear-gloss>
</example>
@@ -1721,45 +1706,45 @@ FIXME: the NAhE+BO entries are missing:
<gloss>The-word
<quote>John</quote> is-the-name-of me.</gloss>
<en>My name is John.</en>
</interlinear-gloss>
</example>
<para>In
<xref linkend="example-random-id-qLiB"/> and
<xref linkend="example-random-id-qLIJ"/>,
<jbophrase>.djan.</jbophrase> appears with a pause before it as well as after it, because the preceding word is not one of the four special cases. These rules force names to always be separable from the general word-stream.</para>
<para> <indexterm type="general-imported"><primary>names</primary><secondary>multiple</secondary></indexterm> Unless some other rule prevents it (such as the rule that
- <quote>zo</quote> is always followed by a single word, which is quoted), multiple names may appear wherever one name is permitted, each with its terminating pause:</para>
+ <jbophrase>zo</jbophrase> is always followed by a single word, which is quoted), multiple names may appear wherever one name is permitted, each with its terminating pause:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-cw3p">
<title>
<anchor xml:id="c6e12d6"/>
</title>
<interlinear-gloss>
<jbo>doi djan. pol. djonz. le bloti cu klama fi la niuport. niuz.</jbo>
<en>John Paul Jones, the boat comes (to somewhere) from Newport News.</en>
</interlinear-gloss>
</example>
<para> <indexterm type="example-imported"><primary>John Paul Jones</primary><secondary>example</secondary></indexterm> <indexterm type="example-imported"><primary>Newport News</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>name-words</primary><secondary>permissible consonant combinations</secondary></indexterm> A name may not contain any consonant combination that is illegal in Lojban words generally: the
<quote>impermissible consonant clusters</quote> of Lojban morphology (explained in
<xref linkend="chapter-phonology"/>). Thus
- <quote>djeimz.</quote> is not a valid version of
- <quote>James</quote> (because
- <quote>mz</quote> is invalid):
+ <jbophrase valid="false">djeimz.</jbophrase> is not a valid version of
+ <jbophrase>James</jbophrase> (because
+ <jbophrase role="morphology" valid="false">mz</jbophrase> is invalid):
<jbophrase>djeimyz</jbophrase> will suffice. Similarly,
- <quote>la</quote> may be replaced by
+ <jbophrase>la</jbophrase> may be replaced by
<jbophrase>ly</jbophrase>,
- <quote>lai</quote> by
- <quote>ly'i</quote>,
+ <jbophrase>lai</jbophrase> by
+ <jbophrase>ly'i</jbophrase>,
<jbophrase>doi</jbophrase> by
<jbophrase>do'i</jbophrase> or
<jbophrase>dai</jbophrase>. Here are a few examples:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>Doyle</cmavo>
<selmaho>*doi,l</selmaho>
<description>do'il or dai,l</description>
@@ -1787,27 +1772,27 @@ FIXME: the NAhE+BO entries are missing:
<title>
<anchor xml:id="c6e12d7"/>
</title>
<interlinear-gloss>
<jbo>lojban.</jbo>
<en>Lojban</en>
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>names from vowel-final base</primary><secondary>commonly used consonant endings</secondary></indexterm> <indexterm type="general-imported"><primary>names</primary><secondary>borrowing from other languages</secondary></indexterm> When borrowing names from another language which end in a vowel, or when turning a Lojban brivla (all of which end in vowels) into a name, the vowel may be removed or an arbitrary consonant added. It is common (but not required) to use the consonants
- <quote>s</quote> or
- <quote>n</quote> when borrowing vowel-final names from English; speakers of other languages may wish to use other consonant endings.</para>
+ <jbophrase role="rafsi">s</jbophrase> or
+ <jbophrase role="rafsi">n</jbophrase> when borrowing vowel-final names from English; speakers of other languages may wish to use other consonant endings.</para>
<para> <indexterm type="general-imported"><primary>names with la</primary><secondary>implicit quantifier for</secondary></indexterm> The implicit quantifier for name sumti of the form
- <quote>la</quote> followed by a name is
+ <jbophrase>la</jbophrase> followed by a name is
<jbophrase>su'o</jbophrase>, just as for
- <quote>la</quote> followed by a selbri.</para>
+ <jbophrase>la</jbophrase> followed by a selbri.</para>
</section>
<section xml:id="cll_chapter6-section13">
<title>Pro-sumti summary</title>
<para> <indexterm type="general-imported"><primary>pro-sumti</primary><secondary>classes of</secondary></indexterm> The Lojban pro-sumti are the cmavo of selma'o KOhA. They fall into several classes: personal, definable, quantificational, reflexive, back-counting, indefinite, demonstrative, metalinguistic, relative, question. More details are given in
<xref linkend="chapter-anaphoric-cmavo"/>; this section mostly duplicates information found there, but adds material on the implicit quantifier of each pro-sumti.</para>
<para> <indexterm type="lojban-word-imported"><primary>ro</primary></indexterm> <indexterm type="general-imported"><primary>pro-sumti</primary><secondary>implicit quantifier for</secondary></indexterm> The following examples illustrate each of the classes. Unless otherwise noted below, the implicit quantification for pro-sumti is
<jbophrase>ro</jbophrase> (all). In the case of pro-sumti which refer to other sumti, the
<jbophrase>ro</jbophrase> signifies
<quote>all of those referred to by the other sumti</quote>: thus it is possible to restrict, but not to extend, the quantification of the other sumti.</para>
<para> <indexterm type="general-imported"><primary>personal pro-sumti</primary></indexterm> Personal pro-sumti (
@@ -1847,21 +1832,21 @@ FIXME: the NAhE+BO entries are missing:
<jbophrase>ko'e</jbophrase>,
<jbophrase>ko'i</jbophrase>,
<jbophrase>ko'o</jbophrase>,
<jbophrase>ko'u</jbophrase>,
<jbophrase>fo'a</jbophrase>,
<jbophrase>fo'e</jbophrase>,
<jbophrase>fo'i</jbophrase>,
<jbophrase>fo'o</jbophrase>,
<jbophrase>fo'u</jbophrase>) refer to whatever the speaker has explicitly made them refer to. This reference is accomplished with
- <quote>goi</quote> (of selma'o GOI), which means
+ <jbophrase>goi</jbophrase> (of selma'o GOI), which means
<quote>defined-as</quote>.</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-8whK">
<title>
<anchor xml:id="c6e13d2"/>
</title>
<interlinear-gloss>
<jbo>le cribe goi ko'a cu xekri .i ko'a citka le smacu</jbo>
<en>The bear defined-as it-1 is-black. It-1 eats the mouse.</en>
</interlinear-gloss>
</example>
@@ -1972,21 +1957,21 @@ FIXME: the NAhE+BO entries are missing:
<interlinear-gloss>
<jbo>li re su'i re du li vo</jbo>
<gloss>.i la'e di'u jetnu</gloss>
<gloss>The-number two plus two equals the-number four.</gloss>
<en>The-referent-of the-previous-utterance is-true.</en>
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>metalinguistic pro-sumti</primary><secondary>implicit quantifier for</secondary></indexterm> The implicit quantifier for metalinguistic pro-sumti is
<jbophrase>su'o</jbophrase> (at least one), because they are considered analogous to
- <quote>lo</quote> descriptions: they refer to things which really are previous, current, or following utterances.</para>
+ <jbophrase>lo</jbophrase> descriptions: they refer to things which really are previous, current, or following utterances.</para>
<para> <indexterm type="general-imported"><primary>relative pro-sumti</primary></indexterm> The relative pro-sumti (
<jbophrase>ke'a</jbophrase>) is used within relative clauses (see
<xref linkend="chapter-relative-clauses"/> for a discussion of relative clauses) to refer to whatever sumti the relative clause is attached to.</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-sf2T">
<title>
<anchor xml:id="c6e13d9"/>
</title>
<interlinear-gloss>
<jbo>mi viska le mlatu ku poi zo'e zbasu ke'a</jbo>
@@ -2020,44 +2005,44 @@ FIXME: the NAhE+BO entries are missing:
<para> <indexterm type="general-imported"><primary>quotation</primary><secondary>four kinds</secondary></indexterm> There are four kinds of quotation in Lojban: text quotation, words quotation, single-word quotation, non-Lojban quotation. More information is provided in
<xref linkend="chapter-structure"/>.</para>
<para> <indexterm type="lojban-word-imported"><primary>li'u</primary></indexterm> <indexterm type="lojban-word-imported"><primary>lu</primary></indexterm> <indexterm type="general-imported"><primary>text quotation</primary><secondary>as internally grammatical</secondary></indexterm> <indexterm type="general-imported"><primary>text quotation</primary><secondary>syntax of</secondary></indexterm> Text quotations are preceded by
<jbophrase>lu</jbophrase> and followed by
- <quote>li'u</quote>, and are an essential part of the surrounding text: they must be grammatical Lojban texts.</para>
+ <jbophrase>li'u</jbophrase>, and are an essential part of the surrounding text: they must be grammatical Lojban texts.</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-v1DE">
<title>
<anchor xml:id="c6e14d1"/>
</title>
<interlinear-gloss>
<jbo>mi cusku lu mi'e djan. li'u</jbo>
<gloss>I say the-text [quote] I-am John [unquote].</gloss>
<en>I say
<quote>I'm John</quote>.</en>
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>word quotation</primary><secondary>internal grammar of</secondary></indexterm> <indexterm type="general-imported"><primary>word quotation</primary><secondary>as morphologically valid</secondary></indexterm> Words quotations are quotations of one or more Lojban words. The words need not mean anything, but they must be morphologically valid so that the end of the quotation can be discerned.</para>
<para> <indexterm type="lojban-word-imported"><primary>le'u</primary></indexterm> <indexterm type="lojban-word-imported"><primary>lo'u</primary></indexterm> FIXME: TAG SPOT</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-UMDQ">
<title>
<anchor xml:id="c6e14d2"/>
</title>
<interlinear-gloss>
<jbo>mi cusku lo'u li mi le'u</jbo>
<gloss>I say the-words [quote]
- <quote>li mi</quote> [unquote].</gloss>
+ <jbophrase>li mi</jbophrase> [unquote].</gloss>
<en>I say
- <quote>li mi</quote>.</en>
+ <jbophrase>li mi</jbophrase>.</en>
</interlinear-gloss>
</example>
<para>Note that the translation of
<xref linkend="example-random-id-UMDQ"/> does not translate the Lojban words, because they are not presumed to have any meaning (in fact, they are ungrammatical).</para>
<para> <indexterm type="general-imported"><primary>single-word quotation</primary></indexterm> Single-word quotation quotes a single Lojban word. Compound cmavo are not allowed.</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-XqKv">
<title>
<anchor xml:id="c6e14d3"/>
</title>
@@ -2073,26 +2058,26 @@ FIXME: the NAhE+BO entries are missing:
<anchor xml:id="c6e14d4"/>
</title>
<interlinear-gloss>
<jbo>mi cusku zoi kuot. I'm John .kuot</jbo>
<en>I say
<quote>I'm John</quote>.</en>
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>quotation</primary><secondary>implicit quantifier for</secondary></indexterm> The implicit quantifier for all types of quotation is
<jbophrase>su'o</jbophrase> (at least one), because quotations are analogous to
- <quote>lo</quote> descriptions: they refer to things which actually are words or sequences of words.</para>
+ <jbophrase>lo</jbophrase> descriptions: they refer to things which actually are words or sequences of words.</para>
</section>
<section xml:id="cll_chapter6-section15">
<title>Number summary</title>
<para> <indexterm type="lojban-word-imported"><primary>li</primary></indexterm> <indexterm type="general-imported"><primary>number sumti</primary><secondary>with li</secondary></indexterm> <indexterm type="general-imported"><primary>number sumti</primary><secondary>syntax of</secondary></indexterm> The sumti which refer to numbers consist of the cmavo
- <quote>li</quote> (of selma'o LI) followed by an arbitrary Lojban mekso, or mathematical expression. This can be anything from a simple number up to the most complicated combination of numbers, variables, operators, and so on. Much more information on numbers is given in
+ <jbophrase>li</jbophrase> (of selma'o LI) followed by an arbitrary Lojban mekso, or mathematical expression. This can be anything from a simple number up to the most complicated combination of numbers, variables, operators, and so on. Much more information on numbers is given in
<xref linkend="chapter-mekso"/>. Here are a few examples of increasing complexity:</para>
<example xml:id="example-random-id-qLIm" role="interlinear-gloss-example">
<title>
<anchor xml:id="c6e15d1"/>
</title>
<interlinear-gloss>
<jbo>li vo</jbo>
<gloss>the-number four</gloss>
<en>4</en>
</interlinear-gloss>
@@ -2111,23 +2096,23 @@ FIXME: the NAhE+BO entries are missing:
<title>
<anchor xml:id="c6e15d3"/>
</title>
<interlinear-gloss>
<jbo>li .abu bopi'i xy. bote'a re su'i by. bopi'i xy. su'i cy.</jbo>
<gloss>the-number a times x to-power 2 plus b times x plus c</gloss>
<en>ax</en>
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>number sumti</primary><secondary>with li contrasted with me'o</secondary></indexterm> <indexterm type="general-imported"><primary>number sumti</primary><secondary>with me'o contrasted with li</secondary></indexterm> <indexterm type="general-imported"><primary>LI selma'o</primary></indexterm> <indexterm type="general-imported"><primary>me'o</primary></indexterm> <indexterm type="general-imported"><primary>number sumti</primary><secondary>with me'o</secondary></indexterm> An alternative to
- <quote>li</quote> is
- <quote>me'o</quote>, also of selma'o LI. Number expressions beginning with
- <quote>me'o</quote> refer to the actual expression, rather than its value. Thus
+ <jbophrase>li</jbophrase> is
+ <jbophrase>me'o</jbophrase>, also of selma'o LI. Number expressions beginning with
+ <jbophrase>me'o</jbophrase> refer to the actual expression, rather than its value. Thus
<xref linkend="example-random-id-qLIm"/> and
<xref linkend="example-random-id-qLis"/> above have the same meaning, the number four, whereas</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-sW7u">
<title>
<anchor xml:id="c6e15d4"/>
</title>
<interlinear-gloss>
<jbo>me'o vo</jbo>
<gloss>the-expression four</gloss>
<en>
@@ -2145,15 +2130,15 @@ FIXME: the NAhE+BO entries are missing:
<gloss>the-expression two plus two</gloss>
<en>
<quote>2+2</quote>
</en>
</interlinear-gloss>
</example>
<para>refer to different pieces of text.</para>
<para> <indexterm type="general-imported"><primary>mathematical expressions</primary><secondary>implicit quantifier for</secondary></indexterm> <indexterm type="general-imported"><primary>numbers</primary><secondary>implicit quantifier for</secondary></indexterm> The implicit quantifier for numbers and mathematical expressions is
<jbophrase>su'o</jbophrase>, because these sumti are analogous to
- <quote>lo</quote> descriptions: they refer to things which actually are numbers or pieces of text. In the case of numbers (with
- <quote>li</quote>), this is a distinction without a difference, as there is only one number which is 4; but there are many texts
+ <jbophrase>lo</jbophrase> descriptions: they refer to things which actually are numbers or pieces of text. In the case of numbers (with
+ <jbophrase>li</jbophrase>), this is a distinction without a difference, as there is only one number which is 4; but there are many texts
<quote>4</quote>, as many as there are documents in which that numeral appears.</para>
</section>
</chapter>
diff --git a/todocbook/TODO b/todocbook/TODO
index 99c859b..1e3cc75 100644
--- a/todocbook/TODO
+++ b/todocbook/TODO
@@ -4,21 +4,21 @@
==================
Most of the below is intended to be done as needed as you review a
particular chapter/section. It looks like more complexity than it
actually is; you'll get used to it.
SAY HERE WHAT YOU'VE DONE, including parts you haven't completed
(like index work).
Robin Powell: 5.1, 5.2, 5.3
-Zort: 3, 5
+Zort: 3, 4, 5 (they still contain FIXMEs though)
------
Ignore Chapter 2 for now.
------
If you have any trouble, add a FIXME comment, like so:
<!-- FIXME: detailed explanation here -->
commit bbf5da6a5b61b4365dc055215f9fa1b411a10c4c
Author: Eitan Postavsky <eitanp32@gmail.com>
Date: Wed Jan 5 10:38:03 2011 -0500
Chapter 4: variablelists to orderedlists, example classification, invented <foreign> for lojbanization examples.
diff --git a/todocbook/4.xml b/todocbook/4.xml
index 18f29f6..bc4fef7 100644
--- a/todocbook/4.xml
+++ b/todocbook/4.xml
@@ -215,35 +215,28 @@
<member><jbophrase role="diphthong">.uo</jbophrase></member>
<member><jbophrase role="diphthong">.uu</jbophrase></member>
</simplelist>
<para>In addition, cmavo can have the form
<jbophrase role="morphology">Cy</jbophrase>, a consonant followed by the letter
<jbophrase role="letteral">y</jbophrase>. These cmavo represent letters of the Lojban alphabet, and are discussed in detail in
<xref linkend="chapter-letterals"/>.</para>
<para> <indexterm type="general-imported"><primary>compound cmavo</primary><secondary>compared with sequence of simple cmavo</secondary></indexterm> <indexterm type="general-imported"><primary>compound cmavo</primary><secondary>definition</secondary></indexterm> <indexterm type="general-imported"><primary>cmavo</primary><secondary>compound</secondary></indexterm> Compound cmavo are sequences of cmavo attached together to form a single written word. A compound cmavo is always identical in meaning and in grammatical use to the separated sequence of simple cmavo from which it is composed. These words are written in compound form merely to save visual space, and to ease the reader's burden in identifying when the component cmavo are acting together.</para>
<para> <indexterm type="general-imported"><primary>compound cmavo</primary><secondary>recognition of</secondary></indexterm> Compound cmavo, while not visually short like their components, can be readily identified by two characteristics:</para>
- <variablelist>
- <varlistentry>
- <term>1)</term>
+ <orderedlist>
<listitem>
<para>They have no consonant pairs or clusters, and</para>
-
</listitem>
- </varlistentry>
- <varlistentry>
- <term>2)</term>
<listitem>
<para>They end in a vowel.</para>
</listitem>
- </varlistentry>
- </variablelist>
+ </orderedlist>
<para>For example:</para>
<example xml:id="example-random-id-qiXV" role="compound-cmavo-example">
<title>
<anchor xml:id="c4e2d1"/>
</title>
<compound-cmavo>
<jbo>.iseci'i</jbo>
<jbo>.i se ci'i</jbo>
</compound-cmavo>
</example>
@@ -589,55 +582,55 @@
</example>
<para>respectively.</para>
<para> <indexterm type="general-imported"><primary>tanru</primary><secondary>ambiguity in</secondary></indexterm> The possibility of semantic ambiguity can easily be seen in the last case. To interpret
<xref linkend="example-random-id-KQ4s"/>, the listener must determine what type of motherliness pertains to the father being referred to. In an appropriate context,
<jbophrase>mamta patfu</jbophrase> could mean not
<quote>grandfather</quote> but simply
<quote>father with some motherly attributes</quote>, depending on the culture. If absolute clarity is required, there are ways to expand upon and explain the exact interrelationship between the components; but such detail is usually not needed.</para>
<para> <indexterm type="general-imported"><primary>tanru</primary><secondary>to lujvo</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>from tanru</secondary></indexterm> <indexterm type="general-imported"><primary>brivla</primary><secondary>from tanru</secondary></indexterm> When a concept expressed in a tanru proves useful, or is frequently expressed, it is desirable to choose one of the possible meanings of the tanru and assign it to a new brivla. For
<xref linkend="example-random-id-xhQP"/>, we would probably choose
<quote>user of computers</quote>, and form the new word</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-v5YD">
+ <example role="lujvo-example" xml:id="example-random-id-v5YD">
<title>
<anchor xml:id="c4e5d5"/>
</title>
- <interlinear-gloss>
+ <lujvo>
<jbo>sampli</jbo>
- </interlinear-gloss>
+ </lujvo>
</example>
<para>Such a brivla, built from the rafsi which represent its component words, is called a
<jbophrase>lujvo</jbophrase>. Another example, corresponding to the tanru of
<xref linkend="example-random-id-oLE3"/>, would be:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-aiAR">
+ <example role="lujvo-example" xml:id="example-random-id-aiAR">
<title>
<anchor xml:id="c4e5d6"/>
</title>
- <interlinear-gloss>
+ <lujvo>
<jbo>bralo'i</jbo>
<gloss>big-boat</gloss>
<en>ship</en>
- </interlinear-gloss>
+ </lujvo>
</example>
<para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>construction of</secondary></indexterm> <indexterm type="general-imported"><primary>rafsi</primary><secondary>definition</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>unambiguous decomposition of</secondary></indexterm> The lujvo representing a given tanru is built from units representing the component gismu. These units are called
<jbophrase>rafsi</jbophrase> in Lojban. Each rafsi represents only one gismu. The rafsi are attached together in the order of the words in the tanru, occasionally inserting so-called
<quote>hyphen</quote> letters to ensure that the pieces stick together as a single word and cannot accidentally be broken apart into cmavo, gismu, or other word forms. As a result, each lujvo can be readily and accurately recognized, allowing a listener to pick out the word from a string of spoken Lojban, and if necessary, unambiguously decompose the word to a unique source tanru, thus providing a strong clue to its meaning.</para>
<para>The lujvo that can be built from the tanru
<jbophrase>mamta patfu</jbophrase> in
<xref linkend="example-random-id-KQ4s"/> is</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-TCUH">
+ <example role="lujvo-example" xml:id="example-random-id-TCUH">
<title>
<anchor xml:id="c4e5d7"/>
</title>
- <interlinear-gloss>
+ <lujvo>
<jbo>mampa'u</jbo>
- </interlinear-gloss>
+ </lujvo>
</example>
<para>which refers specifically to the concept
<quote>maternal grandfather</quote>. The two gismu that constitute the tanru are represented in
<jbophrase>mampa'u</jbophrase> by the rafsi
<jbophrase role="rafsi">mam</jbophrase>- and
-<jbophrase role="rafsi">pa'u</jbophrase>, respectively; these two rafsi are then concatenated together to form
<jbophrase>mampa'u</jbophrase>.</para>
<para> <indexterm type="general-imported"><primary>long rafsi form</primary><secondary>compared with short form in effect on lujvo meaning</secondary></indexterm> <indexterm type="general-imported"><primary>short rafsi form</primary><secondary>compared with long form in effect on lujvo meaning</secondary></indexterm> <indexterm type="general-imported"><primary>rafsi form</primary><secondary>effect of choice on meaning of lujvo</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>multiple forms of</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>meaning of</secondary></indexterm> Like gismu, lujvo have only one meaning. When a lujvo is formally entered into a dictionary of the language, a specific definition will be assigned based on one particular interrelationship between the terms. (See
<xref linkend="chapter-lujvo"/> for how this has been done.) Unlike gismu, lujvo may have more than one form. This is because there is no difference in meaning between the various rafsi for a gismu when they are used to build a lujvo. A long rafsi may be used, especially in noisy environments, in place of a short rafsi; the result is considered the same lujvo, even though the word is spelled and pronounced differently. Thus the word
@@ -651,32 +644,31 @@
<jbophrase role="letteral">y</jbophrase> and
<jbophrase role="letteral">'</jbophrase>), and the lujvo must end in a vowel.</para>
<para> <indexterm type="general-imported"><primary>glue in lujvo</primary><secondary>y-hyphen as</secondary></indexterm> <indexterm type="general-imported"><primary>y-hyphen</primary><secondary>and stress determination</secondary></indexterm> <indexterm type="general-imported"><primary>y-hyphen</primary><secondary>use of</secondary></indexterm> A
<jbophrase role="letteral">y</jbophrase> (which is ignored in determining stress or consonant clusters) is inserted in the middle of the consonant cluster to glue the word together when the resulting cluster is either not permissible or the word is likely to break up. There are specific rules describing these conditions, detailed in
<xref linkend="section-rafsi"/>.</para>
<para> <indexterm type="general-imported"><primary>glue in lujvo</primary><secondary>n-hyphen as</secondary></indexterm> <indexterm type="general-imported"><primary>n-hyphen</primary><secondary>use of</secondary></indexterm> <indexterm type="general-imported"><primary>glue in lujvo</primary><secondary>r-hyphen as</secondary></indexterm> <indexterm type="general-imported"><primary>r-hyphen</primary><secondary>use of</secondary></indexterm> An
<jbophrase role="letteral">r</jbophrase> (in some cases, an
<jbophrase role="letteral">n</jbophrase>) is inserted when a CVV-form rafsi attaches to the beginning of a lujvo in such a way that there is no consonant cluster. For example, in the lujvo</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-3Qtv">
+ <example role="lujvo-example" xml:id="example-random-id-3Qtv">
<title>
<indexterm type="example-imported"><primary>field rations</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c4e5d8"/>
</title>
- <interlinear-gloss>
+ <lujvo>
<jbo>soirsai</jbo>
- <jbo>sonci sanmi</jbo>
+ <veljvo>sonci sanmi</veljvo>
<gloss>soldier meal</gloss>
<en>field rations</en>
-
- </interlinear-gloss>
+ </lujvo>
</example>
<para> <indexterm type="general-imported"><primary>cmavo</primary><secondary>contrasted with same-form rafsi in meaning</secondary></indexterm> <indexterm type="general-imported"><primary>rafsi</primary><secondary>contrasted with same-form cmavo in meaning</secondary></indexterm> the rafsi
<jbophrase role="rafsi">soi</jbophrase>- and
-<jbophrase role="rafsi">sai</jbophrase> are joined, with the additional
<jbophrase role="letteral">r</jbophrase> making up the
<jbophrase role="morphology">rs</jbophrase> consonant pair needed to make the word a brivla. Without the
<jbophrase role="letteral">r</jbophrase>, the word would break up into
<jbophrase>soi sai</jbophrase>, two cmavo. The pair of cmavo have no relation to their rafsi lookalikes; they will either be ungrammatical (as in this case), or will express a different meaning from what was intended.</para>
@@ -995,91 +987,91 @@
<jbophrase role="letteral">r</jbophrase>. For example, the tanru
<jbophrase>rokci renro</jbophrase> (
<quote>rock throw</quote>) cannot be expressed as
<jbophrase valid="false">ro'ire'o</jbophrase> (which breaks up into two cmavo), nor can it be
<jbophrase valid="false">ro'irre'o</jbophrase> (which has an impermissible double consonant); the
<jbophrase role="letteral">n</jbophrase>-hyphen is required, and the correct form of the hyphenated lujvo is
<jbophrase>ro'inre'o</jbophrase>. The same lujvo could also be expressed without hyphenation as
<jbophrase>rokre'o</jbophrase>.</para>
<para><!-- FIXME: what to do with this indexterm? --><indexterm type="lojban-word-imported"><primary>ZEI selma'o</primary></indexterm><indexterm type="general-imported"><primary>lujvo</primary><secondary>with zei</secondary></indexterm> There is also a different way of building lujvo, or rather phrases which are grammatically and semantically equivalent to lujvo. You can make a phrase containing any desired words, joining each pair of them with the special cmavo
<jbophrase>zei</jbophrase>. Thus,</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-VeGL">
+ <example role="lujvo-example" xml:id="example-random-id-VeGL">
<title>
<anchor xml:id="c4e6d12"/>
</title>
- <interlinear-gloss>
+ <lujvo>
<jbo>bridi zei valsi</jbo>
- </interlinear-gloss>
+ </lujvo>
</example>
<para> <indexterm type="general-imported"><primary>cmavo without rafsi</primary><secondary>method of including in lujvo</secondary></indexterm> <indexterm type="general-imported"><primary>fu'ivla</primary><secondary>method of including in lujvo</secondary></indexterm> <indexterm type="general-imported"><primary>cmene</primary><secondary>method of including in lujvo</secondary></indexterm> <indexterm type="general-imported"><primary>rafsi</primary><secondary>lack of</secondary><tertiary>effect on forming lujvo</tertiary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>from cmavo with no rafsi</secondary></indexterm> is the exact equivalent of
<jbophrase>brivla</jbophrase> (but not necessarily the same as the underlying tanru
<jbophrase>bridi valsi</jbophrase>, which could have other meanings.) Using
<jbophrase>zei</jbophrase> is the only way to get a cmavo lacking a rafsi, a cmene, or a fu'ivla into a lujvo:</para>
- <example xml:id="example-random-id-qJe1" role="interlinear-gloss-example">
+ <example xml:id="example-random-id-qJe1" role="lujvo-example">
<title>
<indexterm type="example-imported"><primary>X-ray</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c4e6d13"/>
</title>
- <interlinear-gloss>
+ <lujvo>
<jbo>xy. zei kantu</jbo>
<en>X ray</en>
- </interlinear-gloss>
+ </lujvo>
</example>
- <example xml:id="example-random-id-qJeE" role="interlinear-gloss-example">
+ <example xml:id="example-random-id-qJeE" role="lujvo-example">
<title>
<indexterm type="example-imported"><primary>Persian rug</primary><secondary>example</secondary></indexterm>
<indexterm type="example-imported"><primary>rug</primary><secondary>Persian</secondary><tertiary>example</tertiary></indexterm>
<anchor xml:id="c4e6d14"/>
</title>
- <interlinear-gloss>
+ <lujvo>
<jbo>kulnr,farsi zei lolgai</jbo>
<gloss>Farsi floor-cover</gloss>
<en>Persian rug</en>
- </interlinear-gloss>
+ </lujvo>
</example>
- <example xml:id="example-random-id-qJef" role="interlinear-gloss-example">
+ <example xml:id="example-random-id-qJef" role="lujvo-example">
<title>
<indexterm type="example-imported"><primary>hepatitis</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c4e6d15"/>
</title>
- <interlinear-gloss>
+ <lujvo>
<jbo>na'e zei .a zei na'e zei by. livgyterbilma</jbo>
<gloss>non-A, non-B liver-disease</gloss>
<en>non-A, non-B hepatitis</en>
- </interlinear-gloss>
+ </lujvo>
</example>
- <example xml:id="example-random-id-qJEh" role="interlinear-gloss-example">
+ <example xml:id="example-random-id-qJEh" role="lujvo-example">
<title>
<indexterm type="example-imported"><primary>Sherman tank</primary><secondary>example</secondary></indexterm>
<indexterm type="example-imported"><primary>tank</primary><secondary>Sherman</secondary><tertiary>example</tertiary></indexterm>
<anchor xml:id="c4e6d16"/>
</title>
- <interlinear-gloss>
+ <lujvo>
<jbo>.cerman. zei jamkarce</jbo>
<gloss>Sherman war-car</gloss>
<en>Sherman tank</en>
- </interlinear-gloss>
+ </lujvo>
</example>
<para><xref linkend="example-random-id-qJef"/> is particularly noteworthy because the phrase that would be produced by removing the
<jbophrase>zei</jbophrase>s from it doesn't end with a brivla, and in fact is not even grammatical. As written, the example is a tanru with two components, but by adding a
<jbophrase>zei</jbophrase> between
<jbophrase>by.</jbophrase> and
<jbophrase>livgyterbilma</jbophrase> to produce</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-Wnaz">
+ <example role="lujvo-example" xml:id="example-random-id-Wnaz">
<title>
<indexterm type="example-imported"><primary>hepatitis</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c4e6d17"/>
</title>
- <interlinear-gloss>
+ <lujvo>
<jbo>na'e zei .a zei na'e zei by. zei livgyterbilma</jbo>
<en>non-A-non-B-hepatitis</en>
- </interlinear-gloss>
+ </lujvo>
</example>
<para>the whole phrase would become a single lujvo. The longer lujvo of
<xref linkend="example-random-id-Wnaz"/> may be preferable, because its place structure can be built from that of
<jbophrase>bilma</jbophrase>, whereas the place structure of a lujvo without a brivla must be constructed ad hoc.</para>
<para> <indexterm type="general-imported"><primary>cmavo</primary><secondary>contrasted with rafsi in usage</secondary></indexterm> <indexterm type="general-imported"><primary>rafsi</primary><secondary>contrasted with cmavo in usage</secondary></indexterm> <indexterm type="general-imported"><primary>rafsi</primary><secondary>contrasted with words</secondary></indexterm> Note that rafsi may not be used in
<jbophrase>zei</jbophrase> phrases, because they are not words. CVV rafsi look like words (specifically cmavo) but there can be no confusion between the two uses of the same letters, because cmavo appear only as separate words or in compound cmavo (which are really just a notation for writing separate but closely related words as if they were one); rafsi appear only as parts of lujvo.</para>
</section>
<section xml:id="section-fuhivla">
<title>fu'ivla</title>
<para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>unsuitability of for concrete/specific terms and jargon</secondary></indexterm> <indexterm type="general-imported"><primary>food</primary><secondary>use of fu'ivla for specific</secondary></indexterm> <indexterm type="general-imported"><primary>animals</primary><secondary>use of fu'ivla for specific</secondary></indexterm> <indexterm type="general-imported"><primary>plants</primary><secondary>use of fu'ivla for specific</secondary></indexterm> <indexterm type="general-imported"><primary>jargon</primary><secondary>use of fu'ivla for</secondary></indexterm> <indexterm type="general-imported"><primary>specific terms</primary><secondary>use of fu'ivla for</secondary></indexterm> <indexterm type="general-imported"><primary>concrete terms</primary><secondary>use of fu'ivla for</secondary></indexterm> <indexterm type="general-imported"><primary>fu'ivla</primary><secondary>use of</secondary></indexterm> The use of tanru or lujvo is not always appropriate for very concrete or specific terms (e.g.
@@ -1966,150 +1958,103 @@
<xref linkend="chapter-selbri"/>; abstraction is explained in
<xref linkend="chapter-abstractions"/>.) Plausibility is the key to learning new ideas and to evaluating unfamiliar lujvo.</para>
</section>
<section xml:id="section-lujvo-making">
<title>The lujvo-making algorithm</title>
<para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>algorithm for</secondary></indexterm> The following is the current algorithm for generating Lojban lujvo given a known tanru and a complete list of gismu and their assigned rafsi. The algorithm was designed by Bob LeChevalier and Dr. James Cooke Brown for computer program implementation. It was modified in 1989 with the assistance of Nora LeChevalier, who detected a flaw in the original
<quote>tosmabru test</quote>.</para>
<para>Given a tanru that is to be made into a lujvo:</para>
- <variablelist>
- <varlistentry>
- <term>1)</term>
- <listitem>
- <para>Choose a 3-letter or 4-letter rafsi for each of the gismu and cmavo in the tanru except the last.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>2)</term>
- <listitem>
- <para>Choose a 3-letter (CVV-form or CCV-form) or 5-letter rafsi for the final gismu in the tanru.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>3)</term>
- <listitem>
- <para>Join the resulting string of rafsi, initially without hyphens.</para>
-
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>4)</term>
- <listitem>
- <para> <indexterm type="general-imported"><primary>hyphens in lujvo</primary><secondary>proscribed where not required</secondary></indexterm> Add hyphen letters where necessary. It is illegal to add a hyphen at a place that is not required by this algorithm. Right-to-left tests are recommended, for reasons discussed below.
- <variablelist>
- <varlistentry>
- <term>4a)</term>
- <listitem>
- <para>If there are more than two words in the tanru, put an
- <jbophrase role="letteral">r</jbophrase>-hyphen (or an
- <jbophrase role="letteral">n</jbophrase>-hyphen) after the first rafsi if it is CVV-form. If there are exactly two words, then put an
- <jbophrase role="letteral">r</jbophrase>-hyphen (or an
- <jbophrase role="letteral">n</jbophrase>-hyphen) between the two rafsi if the first rafsi is CVV-form, unless the second rafsi is CCV-form (for example,
- <jbophrase>saicli</jbophrase> requires no hyphen). Use an
- <jbophrase role="letteral">r</jbophrase>-hyphen unless the letter after the hyphen is
- <jbophrase role="letteral">r</jbophrase>, in which case use an
- <jbophrase role="letteral">n</jbophrase>-hyphen. Never use an
- <jbophrase role="letteral">n</jbophrase>-hyphen unless it is required.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>4b)</term>
- <listitem>
- <para>Put a
- <jbophrase role="letteral">y</jbophrase>-hyphen between the consonants of any impermissible consonant pair. This will always appear between rafsi.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>4c)</term>
- <listitem>
- <para> <indexterm type="general-imported"><primary>tosmabru test</primary></indexterm> Put a
- <jbophrase role="letteral">y</jbophrase>-hyphen after any 4-letter rafsi form.</para>
-
- </listitem>
- </varlistentry>
- </variablelist></para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>5)</term>
- <listitem>
- <para>Test all forms with one or more initial CVC-form rafsi - with the pattern
- <quote>CVC ... CVC + X</quote> - for
- <jbophrase>tosmabru failure</jbophrase>. X must either be a CVCCV long rafsi that happens to have a permissible initial pair as the consonant cluster, or is something which has caused a
- <jbophrase role="letteral">y</jbophrase>-hyphen to be installed between the previous CVC and itself by one of the above rules.</para>
- <para>The test is as follows:</para>
- <variablelist>
- <varlistentry>
- <term>5a)</term>
- <listitem>
- <para>Examine all the C/C consonant pairs up to the first <jbophrase role="letteral">y</jbophrase>-hyphen, or up to the end of the word in case there are no <jbophrase role="letteral">y</jbophrase>-hyphens.</para>
- <para>These consonant pairs are called "joints”.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>5b)</term>
- <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>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>5c)</term>
- <listitem>
- <para>Install a <jbophrase role="letteral">y</jbophrase>-hyphen at the first such joint.</para>
- </listitem>
- </varlistentry>
- </variablelist>
- </listitem>
- </varlistentry>
- </variablelist>
+ <orderedlist>
+ <listitem>
+ <para>Choose a 3-letter or 4-letter rafsi for each of the gismu and cmavo in the tanru except the last.</para>
+ </listitem>
+ <listitem>
+ <para>Choose a 3-letter (CVV-form or CCV-form) or 5-letter rafsi for the final gismu in the tanru.</para>
+ </listitem>
+ <listitem>
+ <para>Join the resulting string of rafsi, initially without hyphens.</para>
+ </listitem>
+ <listitem>
+ <para> <indexterm type="general-imported"><primary>hyphens in lujvo</primary><secondary>proscribed where not required</secondary></indexterm> Add hyphen letters where necessary. It is illegal to add a hyphen at a place that is not required by this algorithm. Right-to-left tests are recommended, for reasons discussed below.</para>
+ <orderedlist>
+ <listitem>
+ <para>If there are more than two words in the tanru, put an
+ <jbophrase role="letteral">r</jbophrase>-hyphen (or an
+ <jbophrase role="letteral">n</jbophrase>-hyphen) after the first rafsi if it is CVV-form. If there are exactly two words, then put an
+ <jbophrase role="letteral">r</jbophrase>-hyphen (or an
+ <jbophrase role="letteral">n</jbophrase>-hyphen) between the two rafsi if the first rafsi is CVV-form, unless the second rafsi is CCV-form (for example,
+ <jbophrase>saicli</jbophrase> requires no hyphen). Use an
+ <jbophrase role="letteral">r</jbophrase>-hyphen unless the letter after the hyphen is
+ <jbophrase role="letteral">r</jbophrase>, in which case use an
+ <jbophrase role="letteral">n</jbophrase>-hyphen. Never use an
+ <jbophrase role="letteral">n</jbophrase>-hyphen unless it is required.</para>
+ </listitem>
+ <listitem>
+ <para>Put a
+ <jbophrase role="letteral">y</jbophrase>-hyphen between the consonants of any impermissible consonant pair. This will always appear between rafsi.</para>
+ </listitem>
+ <listitem>
+ <para> <indexterm type="general-imported"><primary>tosmabru test</primary></indexterm> Put a
+ <jbophrase role="letteral">y</jbophrase>-hyphen after any 4-letter rafsi form.</para>
+ </listitem>
+ </orderedlist>
+ </listitem>
+ <listitem>
+ <para>Test all forms with one or more initial CVC-form rafsi - with the pattern
+ <quote>CVC ... CVC + X</quote> - for
+ <jbophrase>tosmabru failure</jbophrase>. X must either be a CVCCV long rafsi that happens to have a permissible initial pair as the consonant cluster, or is something which has caused a
+ <jbophrase role="letteral">y</jbophrase>-hyphen to be installed between the previous CVC and itself by one of the above rules.</para>
+ <para>The test is as follows:</para>
+ <orderedlist>
+ <listitem>
+ <para>Examine all the C/C consonant pairs up to the first <jbophrase role="letteral">y</jbophrase>-hyphen, or up to the end of the word in case there are no <jbophrase role="letteral">y</jbophrase>-hyphens.</para>
+ <para>These consonant pairs are called "joints”.</para>
+ </listitem>
+ <listitem>
+ <para>If all of those joints are permissible initials, then the trial word will break up into a cmavo and a shorter brivla. If not, the word will not break up, and no further hyphens are needed.</para>
+ </listitem>
+ <listitem>
+ <para>Install a <jbophrase role="letteral">y</jbophrase>-hyphen at the first such joint.</para>
+ </listitem>
+ </orderedlist>
+ </listitem>
+</orderedlist>
<para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>selection of best form of</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>scoring of</secondary></indexterm> Note that the
<quote>tosmabru test</quote> implies that the algorithm will be more efficient if rafsi junctures are tested for required hyphens from right to left, instead of from left to right; when the test is required, it cannot be completed until hyphenation to the right has been determined.</para>
</section>
<section xml:id="section-lujvo-scoring">
<title>The lujvo scoring algorithm</title>
<para>This algorithm was devised by Bob and Nora LeChevalier in 1989. It is not the only possible algorithm, but it usually gives a choice that people find preferable. The algorithm may be changed in the future. The lowest-scoring variant will usually be the dictionary form of the lujvo. (In previous versions, it was the highest-scoring variant.)</para>
- <variablelist>
- <varlistentry>
- <term>1)</term>
+ <orderedlist>
<listitem>
<para>Count the total number of letters, including hyphens and apostrophes; call it
-
- <quote>L</quote>.</para>
+ <varname>L</varname>.</para>
</listitem>
- </varlistentry>
- <varlistentry>
- <term>2)</term>
<listitem>
<para>Count the number of apostrophes; call it
- <quote>A</quote>.</para>
+ <varname>A</varname>.</para>
</listitem>
- </varlistentry>
- <varlistentry>
- <term>3)</term>
<listitem>
<para>Count the number of
<jbophrase role="letteral">y</jbophrase>-,
<jbophrase role="letteral">r</jbophrase>-, and
<jbophrase role="letteral">n</jbophrase>-hyphens; call it
- <quote>H</quote>.</para>
+ <varname>H</varname>.</para>
</listitem>
- </varlistentry>
- <varlistentry>
- <term>4)</term>
<listitem>
<para>For each rafsi, find the value in the following table. Sum this value over all rafsi; call it
- <quote>R</quote>:
+ <varname>R</varname>:
<informaltable>
<tgroup cols="3">
<colspec colnum="1" colname="col1"/>
<colspec colnum="2" colname="col2"/>
<colspec colnum="3" colname="col3"/>
<tbody>
<row>
<entry>CVC/CV (final)</entry>
<entry>(-<jbophrase role="rafsi">sarji</jbophrase>-)</entry>
<entry>1</entry>
@@ -2147,30 +2092,26 @@
<row>
<entry>CVV with no apostrophe</entry>
<entry>(-<jbophrase role="rafsi">sai</jbophrase>-)</entry>
<entry>8</entry>
</row>
</tbody>
</tgroup>
</informaltable>
</para>
</listitem>
- </varlistentry>
- <varlistentry>
- <term>5)</term>
<listitem>
<para>Count the number of vowels, not including
<jbophrase role="letteral">y</jbophrase>; call it
- <quote>V</quote>.</para>
+ <varname>V</varname>.</para>
</listitem>
- </varlistentry>
- </variablelist>
+ </orderedlist>
<para> <indexterm type="general-imported"><primary>lujvo form</primary><secondary>hierarchy of priorities for selection of</secondary></indexterm> <indexterm type="general-imported"><primary>hierarchy of priorities for selecting lujvo form</primary></indexterm> The score is then:
<informalequation><mathphrase>(1000 * L) - (500 * A) + (100 * H) - (10 * R) - V</mathphrase></informalequation>
<indexterm type="general-imported"><primary>lujvo</primary><secondary>scored examples of</secondary></indexterm> In case of ties, there is no preference. This should be rare. Note that the algorithm essentially encodes a hierarchy of priorities: short words are preferred (counting apostrophes as half a letter), then words with fewer hyphens, words with more pleasing rafsi (this judgment is subjective), and finally words with more vowels are chosen. Each decision principle is applied in turn if the ones before it have failed to choose; it is possible that a lower-ranked principle might dominate a higher-ranked one if it is ten times better than the alternative.</para>
<para> <!-- FIXME: there's nowhere for this indexterm to go --><indexterm type="example-imported"><primary>doghouse</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>examples of making</secondary></indexterm> Here are some lujvo with their scores (not necessarily the lowest scoring forms for these lujvo, nor even necessarily sensible lujvo):</para>
<example xml:id="example-random-id-qJKu" role="lujvo-making-example">
<title>
<anchor xml:id="c4e12d1"/>
</title>
<lujvo-making>
@@ -2458,220 +2399,193 @@
<jbophrase>cinse ctuca</jbophrase> (which would be
<jbophrase>cinctu</jbophrase>) since the sex of the teacher is rarely important. If there was a reason to specify
<quote>male</quote>, then the simpler tanru
<jbophrase>nakni cinctu</jbophrase> (
<quote>male sexual-teacher</quote>) would be appropriate. This tanru is actually shorter than the four-part lujvo, since the
<jbophrase>ke</jbophrase> required for grouping need not be expressed.</para>
</section>
<section xml:id="section-gismu-making">
<title>The gismu creation algorithm</title>
<para> <indexterm type="general-imported"><primary>source languages</primary><secondary>use in creating gismu</secondary></indexterm> The gismu were created through the following process:</para>
- <variablelist>
- <varlistentry>
- <term>1)</term>
- <listitem>
- <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>creation</secondary><tertiary>scoring rules</tertiary></indexterm> At least one word was found in each of the six source languages (Chinese, English, Hindi, Spanish, Russian, Arabic) corresponding to the proposed gismu. This word was rendered into Lojban phonetics rather liberally: consonant clusters consisting of a stop and the corresponding fricative were simplified to just the fricative (
-
-
-
- <jbophrase role="morphology">tc</jbophrase> became
- <jbophrase role="letteral">c</jbophrase>,
- <jbophrase role="morphology">dj</jbophrase> became
- <jbophrase role="letteral">j</jbophrase>) and non-Lojban vowels were mapped onto Lojban ones. Furthermore, morphological endings were dropped. The same mapping rules were applied to all six languages for the sake of consistency.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>2)</term>
- <listitem>
- <para>All possible gismu forms were matched against the six source-language forms. The matches were scored as follows:
- <variablelist>
- <varlistentry>
- <term>2a)</term>
- <listitem>
- <para>If three or more letters were the same in the proposed gismu and the source-language word, and appeared in the same order, the score was equal to the number of letters that were the same. Intervening letters, if any, did not matter.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>2b)</term>
- <listitem>
- <para>If exactly two letters were the same in the proposed gismu and the source-language word, and either the two letters were consecutive in both words, or were separated by a single letter in both words, the score was 2. Letters in reversed order got no score.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>2c)</term>
- <listitem>
- <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>creation</secondary><tertiary>considerations for selection after scoring</tertiary></indexterm> Otherwise, the score was 0.</para>
- </listitem>
- </varlistentry>
- </variablelist></para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>3)</term>
- <listitem>
- <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>creation</secondary><tertiary>proscribed gismu pairs</tertiary></indexterm> <indexterm type="general-imported"><primary>gismu</primary><secondary>too-similar</secondary></indexterm> The scores were divided by the length of the source-language word in its Lojbanized form, and then multiplied by a weighting value specific to each language, reflecting the proportional number of first-language and second-language speakers of the language. (Second-language speakers were reckoned at half their actual numbers.) The weights were chosen to sum to 1.00. The sum of the weighted scores was the total score for the proposed gismu form.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>4)</term>
- <listitem>
- <para>Any gismu forms that conflicted with existing gismu were removed. Obviously, being identical with an existing gismu constitutes a conflict. In addition, a proposed gismu that was identical to an existing gismu except for the final vowel was considered a conflict, since two such gismu would have identical 4-letter rafsi.</para>
- <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>creation</secondary><tertiary>and transcription blunders</tertiary></indexterm> More subtly: If the proposed gismu was identical to an existing gismu except for a single consonant, and the consonant was "too similar” based on the following table, then the proposed gismu was rejected.</para>
- <informaltable>
- <tgroup cols="2">
- <colspec colnum="1" colname="col1"/>
- <colspec colnum="1" colname="col1"/>
- <thead>
- <row>
- <entry>proposed gismu</entry>
- <entry>existing gismu</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry><jbophrase role="letteral">b</jbophrase></entry>
- <entry><jbophrase role="letteral">p</jbophrase>, <jbophrase role="letteral">v</jbophrase></entry>
- </row>
- <row>
- <entry><jbophrase role="letteral">c</jbophrase></entry>
- <entry><jbophrase role="letteral">j</jbophrase>, <jbophrase role="letteral">s</jbophrase></entry>
- </row>
- <row>
- <entry><jbophrase role="letteral">d</jbophrase></entry>
- <entry><jbophrase role="letteral">t</jbophrase></entry>
- </row>
- <row>
- <entry><jbophrase role="letteral">f</jbophrase></entry>
- <entry><jbophrase role="letteral">p</jbophrase>, <jbophrase role="letteral">v</jbophrase></entry>
- </row>
- <row>
- <entry><jbophrase role="letteral">g</jbophrase></entry>
- <entry><jbophrase role="letteral">k</jbophrase>, <jbophrase role="letteral">x</jbophrase></entry>
- </row>
- <row>
- <entry><jbophrase role="letteral">j</jbophrase></entry>
- <entry><jbophrase role="letteral">c</jbophrase>, <jbophrase role="letteral">z</jbophrase></entry>
- </row>
- <row>
- <entry><jbophrase role="letteral">k</jbophrase></entry>
- <entry><jbophrase role="letteral">g</jbophrase>, <jbophrase role="letteral">x</jbophrase></entry>
- </row>
- <row>
- <entry><jbophrase role="letteral">l</jbophrase></entry>
- <entry><jbophrase role="letteral">r</jbophrase></entry>
- </row>
- <row>
- <entry><jbophrase role="letteral">m</jbophrase></entry>
- <entry><jbophrase role="letteral">n</jbophrase></entry>
- </row>
- <row>
- <entry><jbophrase role="letteral">n</jbophrase></entry>
- <entry><jbophrase role="letteral">m</jbophrase></entry>
- </row>
- <row>
- <entry><jbophrase role="letteral">p</jbophrase></entry>
- <entry><jbophrase role="letteral">b</jbophrase>, <jbophrase role="letteral">f</jbophrase></entry>
- </row>
- <row>
- <entry><jbophrase role="letteral">r</jbophrase></entry>
- <entry><jbophrase role="letteral">l</jbophrase></entry>
- </row>
- <row>
- <entry><jbophrase role="letteral">s</jbophrase></entry>
- <entry><jbophrase role="letteral">c</jbophrase>, <jbophrase role="letteral">z</jbophrase></entry>
- </row>
- <row>
- <entry><jbophrase role="letteral">t</jbophrase></entry>
- <entry><jbophrase role="letteral">d</jbophrase></entry>
- </row>
- <row>
- <entry><jbophrase role="letteral">v</jbophrase></entry>
- <entry><jbophrase role="letteral">b</jbophrase>, <jbophrase role="letteral">f</jbophrase></entry>
- </row>
- <row>
- <entry><jbophrase role="letteral">x</jbophrase></entry>
- <entry><jbophrase role="letteral">g</jbophrase>, <jbophrase role="letteral">k</jbophrase></entry>
- </row>
- <row>
- <entry><jbophrase role="letteral">z</jbophrase></entry>
- <entry><jbophrase role="letteral">j</jbophrase>, <jbophrase role="letteral">s</jbophrase></entry>
- </row>
- </tbody>
- </tgroup>
- </informaltable>
- <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>source-language weights for</secondary></indexterm> See <xref linkend="section-gismu"/> for an example.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>5)</term>
- <listitem>
- <para>The gismu form with the highest score usually became the actual gismu. Sometimes a lower-scoring form was used to provide a better rafsi. A few gismu were changed in error as a result of transcription blunders (for example, the gismu
- <jbophrase>gismu</jbophrase> should have been
- <jbophrase>gicmu</jbophrase>, but it's too late to fix it now).</para>
- <para>The language weights used to make most of the gismu were as follows:</para>
- <informaltable>
- <tgroup cols="2">
- <colspec colnum="1" colname="col1"/>
- <colspec colnum="2" colname="col2"/>
- <tbody>
- <row>
- <entry>Chinese</entry><entry>0.36</entry>
- </row>
- <row>
- <entry>English</entry><entry>0.21</entry>
- </row>
- <row>
- <entry>Hindi</entry><entry>0.16</entry>
- </row>
- <row>
- <entry>Spanish</entry><entry>0.11</entry>
- </row>
- <row>
- <entry>Russian</entry><entry>0.09</entry>
- </row>
- <row>
- <entry>Arabic</entry><entry>0.07</entry>
- </row>
- </tbody>
- </tgroup>
- </informaltable>
- <para>reflecting 1985 number-of-speakers data. A few gismu were made much later using updated weights:</para>
- <informaltable>
- <tgroup cols="2">
- <colspec colnum="1" colname="col1"/>
- <colspec colnum="2" colname="col2"/>
- <tbody>
- <row>
- <entry>Chinese</entry><entry>0.347</entry>
- </row>
- <row>
- <entry>Hindi</entry><entry>0.196</entry>
- </row>
- <row>
- <entry>English</entry><entry>0.160</entry>
- </row>
- <row>
- <entry>Spanish</entry><entry>0.123</entry>
- </row>
- <row>
- <entry>Russian</entry><entry>0.089</entry>
- </row>
- <row>
- <entry>Arabic</entry><entry>0.085</entry>
- </row>
- </tbody>
- </tgroup>
- </informaltable>
- <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>coined</secondary></indexterm> <indexterm type="general-imported"><primary>gismu</primary><secondary>exceptions to gismu creation by algorithm</secondary></indexterm> (English and Hindi switched places due to demographic changes.)</para>
- </listitem>
- </varlistentry>
- </variablelist>
+ <orderedlist>
+ <listitem>
+ <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>creation</secondary><tertiary>scoring rules</tertiary></indexterm> At least one word was found in each of the six source languages (Chinese, English, Hindi, Spanish, Russian, Arabic) corresponding to the proposed gismu. This word was rendered into Lojban phonetics rather liberally: consonant clusters consisting of a stop and the corresponding fricative were simplified to just the fricative (
+ <jbophrase role="morphology">tc</jbophrase> became
+ <jbophrase role="letteral">c</jbophrase>,
+ <jbophrase role="morphology">dj</jbophrase> became
+ <jbophrase role="letteral">j</jbophrase>) and non-Lojban vowels were mapped onto Lojban ones. Furthermore, morphological endings were dropped. The same mapping rules were applied to all six languages for the sake of consistency.</para>
+ </listitem>
+ <listitem>
+ <para>All possible gismu forms were matched against the six source-language forms. The matches were scored as follows:
+ <orderedlist>
+ <listitem>
+ <para>If three or more letters were the same in the proposed gismu and the source-language word, and appeared in the same order, the score was equal to the number of letters that were the same. Intervening letters, if any, did not matter.</para>
+ </listitem>
+ <listitem>
+ <para>If exactly two letters were the same in the proposed gismu and the source-language word, and either the two letters were consecutive in both words, or were separated by a single letter in both words, the score was 2. Letters in reversed order got no score.</para>
+ </listitem>
+ <listitem>
+ <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>creation</secondary><tertiary>considerations for selection after scoring</tertiary></indexterm> Otherwise, the score was 0.</para>
+ </listitem>
+ </orderedlist></para>
+ </listitem>
+ <listitem>
+ <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>creation</secondary><tertiary>proscribed gismu pairs</tertiary></indexterm> <indexterm type="general-imported"><primary>gismu</primary><secondary>too-similar</secondary></indexterm> The scores were divided by the length of the source-language word in its Lojbanized form, and then multiplied by a weighting value specific to each language, reflecting the proportional number of first-language and second-language speakers of the language. (Second-language speakers were reckoned at half their actual numbers.) The weights were chosen to sum to 1.00. The sum of the weighted scores was the total score for the proposed gismu form.</para>
+ </listitem>
+ <listitem>
+ <para>Any gismu forms that conflicted with existing gismu were removed. Obviously, being identical with an existing gismu constitutes a conflict. In addition, a proposed gismu that was identical to an existing gismu except for the final vowel was considered a conflict, since two such gismu would have identical 4-letter rafsi.</para>
+ <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>creation</secondary><tertiary>and transcription blunders</tertiary></indexterm> More subtly: If the proposed gismu was identical to an existing gismu except for a single consonant, and the consonant was "too similar” based on the following table, then the proposed gismu was rejected.</para>
+ <informaltable>
+ <tgroup cols="2">
+ <colspec colnum="1" colname="col1"/>
+ <colspec colnum="2" colname="col2"/>
+ <thead>
+ <row>
+ <entry>proposed gismu</entry>
+ <entry>existing gismu</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry><jbophrase role="letteral">b</jbophrase></entry>
+ <entry><jbophrase role="letteral">p</jbophrase>, <jbophrase role="letteral">v</jbophrase></entry>
+ </row>
+ <row>
+ <entry><jbophrase role="letteral">c</jbophrase></entry>
+ <entry><jbophrase role="letteral">j</jbophrase>, <jbophrase role="letteral">s</jbophrase></entry>
+ </row>
+ <row>
+ <entry><jbophrase role="letteral">d</jbophrase></entry>
+ <entry><jbophrase role="letteral">t</jbophrase></entry>
+ </row>
+ <row>
+ <entry><jbophrase role="letteral">f</jbophrase></entry>
+ <entry><jbophrase role="letteral">p</jbophrase>, <jbophrase role="letteral">v</jbophrase></entry>
+ </row>
+ <row>
+ <entry><jbophrase role="letteral">g</jbophrase></entry>
+ <entry><jbophrase role="letteral">k</jbophrase>, <jbophrase role="letteral">x</jbophrase></entry>
+ </row>
+ <row>
+ <entry><jbophrase role="letteral">j</jbophrase></entry>
+ <entry><jbophrase role="letteral">c</jbophrase>, <jbophrase role="letteral">z</jbophrase></entry>
+ </row>
+ <row>
+ <entry><jbophrase role="letteral">k</jbophrase></entry>
+ <entry><jbophrase role="letteral">g</jbophrase>, <jbophrase role="letteral">x</jbophrase></entry>
+ </row>
+ <row>
+ <entry><jbophrase role="letteral">l</jbophrase></entry>
+ <entry><jbophrase role="letteral">r</jbophrase></entry>
+ </row>
+ <row>
+ <entry><jbophrase role="letteral">m</jbophrase></entry>
+ <entry><jbophrase role="letteral">n</jbophrase></entry>
+ </row>
+ <row>
+ <entry><jbophrase role="letteral">n</jbophrase></entry>
+ <entry><jbophrase role="letteral">m</jbophrase></entry>
+ </row>
+ <row>
+ <entry><jbophrase role="letteral">p</jbophrase></entry>
+ <entry><jbophrase role="letteral">b</jbophrase>, <jbophrase role="letteral">f</jbophrase></entry>
+ </row>
+ <row>
+ <entry><jbophrase role="letteral">r</jbophrase></entry>
+ <entry><jbophrase role="letteral">l</jbophrase></entry>
+ </row>
+ <row>
+ <entry><jbophrase role="letteral">s</jbophrase></entry>
+ <entry><jbophrase role="letteral">c</jbophrase>, <jbophrase role="letteral">z</jbophrase></entry>
+ </row>
+ <row>
+ <entry><jbophrase role="letteral">t</jbophrase></entry>
+ <entry><jbophrase role="letteral">d</jbophrase></entry>
+ </row>
+ <row>
+ <entry><jbophrase role="letteral">v</jbophrase></entry>
+ <entry><jbophrase role="letteral">b</jbophrase>, <jbophrase role="letteral">f</jbophrase></entry>
+ </row>
+ <row>
+ <entry><jbophrase role="letteral">x</jbophrase></entry>
+ <entry><jbophrase role="letteral">g</jbophrase>, <jbophrase role="letteral">k</jbophrase></entry>
+ </row>
+ <row>
+ <entry><jbophrase role="letteral">z</jbophrase></entry>
+ <entry><jbophrase role="letteral">j</jbophrase>, <jbophrase role="letteral">s</jbophrase></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>source-language weights for</secondary></indexterm> See <xref linkend="section-gismu"/> for an example.</para>
+ </listitem>
+ <listitem>
+ <para>The gismu form with the highest score usually became the actual gismu. Sometimes a lower-scoring form was used to provide a better rafsi. A few gismu were changed in error as a result of transcription blunders (for example, the gismu
+ <jbophrase>gismu</jbophrase> should have been
+ <jbophrase>gicmu</jbophrase>, but it's too late to fix it now).</para>
+ <para>The language weights used to make most of the gismu were as follows:</para>
+ <informaltable>
+ <tgroup cols="2">
+ <colspec colnum="1" colname="col1"/>
+ <colspec colnum="2" colname="col2"/>
+ <tbody>
+ <row>
+ <entry>Chinese</entry><entry>0.36</entry>
+ </row>
+ <row>
+ <entry>English</entry><entry>0.21</entry>
+ </row>
+ <row>
+ <entry>Hindi</entry><entry>0.16</entry>
+ </row>
+ <row>
+ <entry>Spanish</entry><entry>0.11</entry>
+ </row>
+ <row>
+ <entry>Russian</entry><entry>0.09</entry>
+ </row>
+ <row>
+ <entry>Arabic</entry><entry>0.07</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ <para>reflecting 1985 number-of-speakers data. A few gismu were made much later using updated weights:</para>
+ <informaltable>
+ <tgroup cols="2">
+ <colspec colnum="1" colname="col1"/>
+ <colspec colnum="2" colname="col2"/>
+ <tbody>
+ <row>
+ <entry>Chinese</entry><entry>0.347</entry>
+ </row>
+ <row>
+ <entry>Hindi</entry><entry>0.196</entry>
+ </row>
+ <row>
+ <entry>English</entry><entry>0.160</entry>
+ </row>
+ <row>
+ <entry>Spanish</entry><entry>0.123</entry>
+ </row>
+ <row>
+ <entry>Russian</entry><entry>0.089</entry>
+ </row>
+ <row>
+ <entry>Arabic</entry><entry>0.085</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>coined</secondary></indexterm> <indexterm type="general-imported"><primary>gismu</primary><secondary>exceptions to gismu creation by algorithm</secondary></indexterm> (English and Hindi switched places due to demographic changes.)</para>
+ </listitem>
+ </orderedlist>
<para> <indexterm type="general-imported"><primary>gismu</primary><secondary>Lojban-specific</secondary></indexterm> Note that the stressed vowel of the gismu was considered sufficiently distinctive that two or more gismu may differ only in this vowel; as an extreme example,
<jbophrase>bradi</jbophrase>,
<jbophrase>bredi</jbophrase>,
<jbophrase>bridi</jbophrase>, and
<jbophrase>brodi</jbophrase> (but fortunately not
<jbophrase>brudi</jbophrase>) are all existing gismu.</para>
</section>
<section xml:id="section-cultural-gismu">
<title>Cultural and other non-algorithmic gismu</title>
@@ -2731,88 +2645,88 @@
<varlistentry>
<term><jbophrase>centi</jbophrase></term>
<listitem><para>.01/centi</para></listitem>
</varlistentry>
<varlistentry>
<term><jbophrase>milti</jbophrase></term>
<listitem><para>.001/milli</para></listitem>
</varlistentry>
<varlistentry>
<term><jbophrase>mikri</jbophrase></term>
- <listitem><para>1E-6/micro</para></listitem>
+ <listitem><para><inlineequation><mathphrase>10<superscript>-6</superscript></mathphrase></inlineequation>/micro</para></listitem>
</varlistentry>
<varlistentry>
<term><jbophrase>nanvi</jbophrase></term>
- <listitem><para>1E-9/nano</para></listitem>
+ <listitem><para><inlineequation><mathphrase>10<superscript>-9</superscript></mathphrase></inlineequation>/nano</para></listitem>
</varlistentry>
<varlistentry>
<term><jbophrase>picti</jbophrase></term>
- <listitem><para>1E-12/pico</para></listitem>
+ <listitem><para><inlineequation><mathphrase>10<superscript>-12</superscript></mathphrase></inlineequation>/pico</para></listitem>
</varlistentry>
<varlistentry>
<term><jbophrase>femti</jbophrase></term>
- <listitem><para>1E-15/femto</para></listitem>
+ <listitem><para><inlineequation><mathphrase>10<superscript>-15</superscript></mathphrase></inlineequation>/femto</para></listitem>
</varlistentry>
<varlistentry>
<term><jbophrase>xatsi</jbophrase></term>
- <listitem><para>1E-18/atto</para></listitem>
+ <listitem><para><inlineequation><mathphrase>10<superscript>-18</superscript></mathphrase></inlineequation>/atto</para></listitem>
</varlistentry>
<varlistentry>
<term><jbophrase>zepti</jbophrase></term>
- <listitem><para>1E-21/zepto</para></listitem>
+ <listitem><para><inlineequation><mathphrase>10<superscript>-21</superscript></mathphrase></inlineequation>/zepto</para></listitem>
</varlistentry>
<varlistentry>
<term><jbophrase>gocti</jbophrase></term>
- <listitem><para>1E-24/yocto</para></listitem>
+ <listitem><para><inlineequation><mathphrase>10<superscript>-24</superscript></mathphrase></inlineequation>/yocto</para></listitem>
</varlistentry>
</variablelist>
<para>Large metric prefixes (values greater than 1):</para>
<variablelist>
<varlistentry>
<term><jbophrase>dekto</jbophrase></term>
<listitem><para>10/deka</para></listitem>
</varlistentry>
<varlistentry>
<term><jbophrase>xecto</jbophrase></term>
<listitem><para>100/hecto</para></listitem>
</varlistentry>
<varlistentry>
<term><jbophrase>kilto</jbophrase></term>
<listitem><para>1000/kilo</para></listitem>
</varlistentry>
<varlistentry>
<term><jbophrase>megdo</jbophrase></term>
- <listitem><para>1E6/mega</para></listitem>
+ <listitem><para><inlineequation><mathphrase>10<superscript>6</superscript></mathphrase></inlineequation>/mega</para></listitem>
</varlistentry>
<varlistentry>
<term><jbophrase>gigdo</jbophrase></term>
- <listitem><para>1E9/giga</para></listitem>
+ <listitem><para><inlineequation><mathphrase>10<superscript>9</superscript></mathphrase></inlineequation>/giga</para></listitem>
</varlistentry>
<varlistentry>
<term><jbophrase>terto</jbophrase></term>
- <listitem><para>1E12/tera</para></listitem>
+ <listitem><para><inlineequation><mathphrase>10<superscript>12</superscript></mathphrase></inlineequation>/tera</para></listitem>
</varlistentry>
<varlistentry>
<term><jbophrase>petso</jbophrase></term>
- <listitem><para>1E15/peta</para></listitem>
+ <listitem><para><inlineequation><mathphrase>10<superscript>15</superscript></mathphrase></inlineequation>/peta</para></listitem>
</varlistentry>
<varlistentry>
<term><jbophrase>xexso</jbophrase></term>
- <listitem><para>1E18/exa</para></listitem>
+ <listitem><para><inlineequation><mathphrase>10<superscript>18</superscript></mathphrase></inlineequation>/exa</para></listitem>
</varlistentry>
<varlistentry>
<term><jbophrase>zetro</jbophrase></term>
- <listitem><para>1E21/zetta</para></listitem>
+ <listitem><para><inlineequation><mathphrase>10<superscript>21</superscript></mathphrase></inlineequation>/zetta</para></listitem>
</varlistentry>
<varlistentry>
<term><jbophrase>gotro</jbophrase></term>
- <listitem><para>1E24/yotta</para></listitem>
+ <listitem><para><inlineequation><mathphrase>10<superscript>24</superscript></mathphrase></inlineequation>/yotta</para></listitem>
</varlistentry>
</variablelist>
<para> <indexterm type="general-imported"><primary>gismu</primary><secondary>cultural</secondary></indexterm> Other scientific or mathematical terms:</para>
<variablelist>
<varlistentry>
<term><jbophrase>delno</jbophrase></term>
<listitem><para>candela</para></listitem>
</varlistentry>
<varlistentry>
<term><jbophrase>kelvo</jbophrase></term>
@@ -3177,21 +3091,21 @@
<quote>must languish in fu'ivla space</quote>. To help defuse this argument, a last-minute proposal was made when this book was already substantially complete. I have added it here with experimental status: it is not yet a standard part of Lojban, since all its implications have not been tested in open debate, and it affects a part of the language (lujvo-making) that has long been stable, but is known to be fragile in the face of small changes. (Many attempts were made to add general mechanisms for making lujvo that contained fu'ivla, but all failed on obvious or obscure counterexamples; finally the general
<jbophrase>zei</jbophrase> mechanism was devised instead.)</para>
<para>The first part of the proposal is uncontroversial and involves no change to the language mechanisms. All valid Type 4 fu'ivla of the form CCVVCV would be reserved for cultural brivla analogous to those described in
<xref linkend="section-cultural-gismu"/>. For example,</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-PMb2">
<title>
<indexterm type="example-imported"><primary>Chilean desert</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c4e16d1"/>
</title>
<interlinear-gloss>
- <jbo>tci'ile</jbo>
+ <jbo valid="false">tci'ile</jbo>
<en>Chilean</en>
</interlinear-gloss>
</example>
<para> is of the appropriate form, and passes all tests required of a Stage 4 fu'ivla. No two fu'ivla of this form would be allowed to coexist if they differed only in the final vowel; this rule was applied to gismu, but does not apply to other fu'ivla or to lujvo.</para>
<para>The second, and fully experimental, part of the proposal is to allow rafsi to be formed from these cultural fu'ivla by removing the final vowel and treating the result as a 4-letter rafsi (although it would contain five letters, not four). These rafsi could then be used on a par with all other rafsi in forming lujvo. The tanru</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-hcR6">
<title>
<anchor xml:id="c4e16d2"/>
</title>
<interlinear-gloss>
--
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.