[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bpfk] dag-cll git updates for Sat Jan 29 01:21:01 EST 2011
commit d3fdace7c469126cf9ecc6516db5cf608c8407fc
Merge: 3a4feb7 83bcd68
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date: Fri Jan 28 20:59:04 2011 -0800
Merge commit '83bcd684208754f9009e53a7a0f663ae89cd0c4d' into gh-pages
commit 83bcd684208754f9009e53a7a0f663ae89cd0c4d
Author: Eitan Postavsky <eitanp32@gmail.com>
Date: Tue Jan 4 19:21:59 2011 -0500
Fixed chapter 3 inline simplelists, made tables/lists in chapter 4.
diff --git a/todocbook/3.xml b/todocbook/3.xml
index f8662df..34ca43c 100644
--- a/todocbook/3.xml
+++ b/todocbook/3.xml
@@ -438,21 +438,21 @@
<para> <indexterm type="general-imported"><primary>period</primary><secondary>optional</secondary></indexterm> Technically, the period is an optional reminder to the reader of a mandatory pause that is dictated by the rules of the language; because these rules are unambiguous, a missing period can be inferred from otherwise correct text. Periods are included only as an aid to the reader.</para>
<para> <indexterm type="general-imported"><primary>period</primary><secondary>within a word</secondary></indexterm> A period also may be found apparently embedded in a word. When this occurs, such a written string is not one word but two, written together to indicate that the writer intends a unitary meaning for the compound. It is not really necessary to use a space between words if a period appears.</para>
<para> <indexterm type="general-imported"><primary>pause</primary><secondary>contrasted with syllable break</secondary></indexterm> <indexterm type="general-imported"><primary>syllable break</primary><secondary>contrasted with pause</secondary></indexterm> <indexterm type="general-imported"><primary>syllable break</primary><secondary>representation in Lojban</secondary></indexterm> <indexterm type="general-imported"><primary>comma</primary><secondary>definition of</secondary></indexterm> The comma is used to indicate a syllable break within a word, generally one that is not obvious to the reader. Such a comma is written to separate syllables, but indicates that there must be no pause between them, in contrast to the period. Between two vowels, a comma indicates that some type of glide may be necessary to avoid a pause that would split the two syllables into separate words. It is always legal to use the apostrophe (IPA
<phrase role="IPA">[h]</phrase>) sound in pronouncing a comma. However, a comma cannot be pronounced as a pause or glottal stop between the two letters separated by the comma, because that pronunciation would split the word into two words.</para>
<para> <indexterm type="general-imported"><primary>comma</primary><secondary>optional</secondary></indexterm> <indexterm type="general-imported"><primary>comma</primary><secondary>main use of</secondary></indexterm> Otherwise, a comma is usually only used to clarify the presence of syllabic
<simplelist type="inline">
<member><jbophrase role="letteral">l</jbophrase></member>
<member><jbophrase role="letteral">m</jbophrase></member>
- <member><jbophrase role="letteral">n</jbophrase></member> or
+ <member><jbophrase role="letteral">n</jbophrase> or</member>
<member><jbophrase role="letteral">r</jbophrase></member>
</simplelist>
(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>
@@ -616,50 +616,50 @@
</row>
</tbody>
</tgroup>
</informaltable>
<para>(Approximate English equivalents of most of these diphthongs exist: see
<xref linkend="section-anglophone-diphthongs"/> for examples.)</para>
<para> <indexterm type="general-imported"><primary>diphthongs</primary><secondary>classification of</secondary></indexterm> The first four diphthongs above (
<simplelist type="inline">
<member><jbophrase role="diphthong">ai</jbophrase></member>
<member><jbophrase role="diphthong">ei</jbophrase></member>
- <member><jbophrase role="diphthong">oi</jbophrase></member> and
+ <member><jbophrase role="diphthong">oi</jbophrase> and</member>
<member><jbophrase role="diphthong">au</jbophrase></member>
</simplelist>
, the ones with off-glides) are freely used in most types of Lojban words; the ten following ones are used only as stand-alone words and in Lojbanized names and borrowings; and the last two (<jbophrase role="diphthong">iy</jbophrase> and <jbophrase role="diphthong">uy</jbophrase>) are used only in Lojbanized names.</para>
<para> <indexterm type="general-imported"><primary>syllabic consonants</primary></indexterm> <indexterm type="general-imported"><primary>consonants</primary><secondary>syllabic</secondary></indexterm> The syllabic consonants of Lojban,
<simplelist type="inline">
<member><phrase role="IPA">[l̩]</phrase></member>
<member><phrase role="IPA">[m̩]</phrase></member>
- <member><phrase role="IPA">[n̩]</phrase></member> and
+ <member><phrase role="IPA">[n̩]</phrase> and</member>
<member><phrase role="IPA">[r̩]</phrase></member>
</simplelist>
, are variants of the non-syllabic
<simplelist type="inline">
<member><phrase role="IPA">[l]</phrase></member>
<member><phrase role="IPA">[m]</phrase></member>
- <member><phrase role="IPA">[n]</phrase></member> and
+ <member><phrase role="IPA">[n]</phrase> and</member>
<member><phrase role="IPA">[r]</phrase></member>
</simplelist>
respectively. They normally have only a limited distribution, appearing in Lojban names and borrowings, although in principle any
<simplelist type="inline">
<member><jbophrase role="letteral">l</jbophrase></member>
<member><jbophrase role="letteral">m</jbophrase></member>
- <member><jbophrase role="letteral">n</jbophrase></member> or
+ <member><jbophrase role="letteral">n</jbophrase> or</member>
<member><jbophrase role="letteral">r</jbophrase></member>
</simplelist>
may be pronounced syllabically. If a syllabic consonant appears next to a
<simplelist type="inline">
<member><jbophrase role="letteral">l</jbophrase></member>
<member><jbophrase role="letteral">m</jbophrase></member>
- <member><jbophrase role="letteral">n</jbophrase></member> or
+ <member><jbophrase role="letteral">n</jbophrase> or</member>
<member><jbophrase role="letteral">r</jbophrase></member>
</simplelist>
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>
@@ -815,21 +815,21 @@
<entry>-</entry>
</row>
</tbody>
</tgroup>
</informaltable>
<para>The consonant
<jbophrase role="letteral">x</jbophrase> has no voiced counterpart in Lojban. The remaining consonants,
<simplelist type="inline">
<member><jbophrase role="letteral">l</jbophrase></member>
<member><jbophrase role="letteral">m</jbophrase></member>
- <member><jbophrase role="letteral">n</jbophrase></member> and
+ <member><jbophrase role="letteral">n</jbophrase> and</member>
<member><jbophrase role="letteral">r</jbophrase></member>
</simplelist>, are typically pronounced with voice, but can be pronounced unvoiced.</para>
<para> <indexterm type="general-imported"><primary>consonant clusters</primary><secondary>contrasted with single consonants</secondary></indexterm> <indexterm type="general-imported"><primary>consonant clusters</primary><secondary>contrasted with doubled consonants</secondary></indexterm> <indexterm type="general-imported"><primary>doubled consonants</primary><secondary>contrasted with consonant clusters</secondary></indexterm> <indexterm type="general-imported"><primary>doubled consonants</primary><secondary>contrasted with single consonants</secondary></indexterm> <indexterm type="general-imported"><primary>single consonants</primary><secondary>contrasted with consonant clusters</secondary></indexterm> <indexterm type="general-imported"><primary>single consonants</primary><secondary>contrasted with doubled consonants</secondary></indexterm> <indexterm type="general-imported"><primary>consonant clusters</primary><secondary>definition of</secondary></indexterm> Consonant sounds occur in languages as single consonants, or as doubled, or as clustered combinations. Single consonant sounds are isolated by word boundaries or by intervening vowel sounds from other consonant sounds. Doubled consonant sounds are either lengthened like
<phrase role="IPA">[s]</phrase> in English
<quote>hiss</quote>, or repeated like
<phrase role="IPA">[k]</phrase> in English
<quote>backcourt</quote>. Consonant clusters consist of two or more single or doubled consonant sounds in a group, each of which is different from its immediate neighbor. In Lojban, doubled consonants are excluded altogether, and clusters are limited to two or three members, except in Lojbanized names.</para>
<para> <indexterm type="general-imported"><primary>consonants</primary><secondary>position of</secondary></indexterm> Consonants can occur in three positions in words: initial (at the beginning), medial (in the middle), and final (at the end). In many languages, the sound of a consonant varies depending upon its position in the word. In Lojban, as much as possible, the sound of a consonant is unrelated to its position. In particular, the common American English trait of changing a
<quote>t</quote> between vowels into a
@@ -841,48 +841,48 @@
<para> <indexterm type="general-imported"><primary>consonant pairs</primary><secondary>restrictions on</secondary></indexterm> Pairs of consonants can also appear freely, with the following restrictions:</para>
<orderedlist>
<listitem>
<para>It is forbidden for both consonants to be the same, as this would violate the rule against double consonants.</para>
</listitem>
<listitem>
<para> <indexterm type="general-imported"><primary>voiced/unvoiced consonants</primary><secondary>restrictions on</secondary></indexterm> It is forbidden for one consonant to be voiced and the other unvoiced. The consonants
<simplelist type="inline">
<member><jbophrase role="letteral">l</jbophrase></member>
<member><jbophrase role="letteral">m</jbophrase></member>
- <member><jbophrase role="letteral">n</jbophrase></member> and
+ <member><jbophrase role="letteral">n</jbophrase> and</member>
<member><jbophrase role="letteral">r</jbophrase></member>
</simplelist> are exempt from this restriction. As a result,
<jbophrase role="morphology" valid="false">bf</jbophrase> is forbidden, and so is
<jbophrase role="morphology" valid="false">sd</jbophrase>, but both
<jbophrase role="morphology">fl</jbophrase> and
<jbophrase role="morphology">vl</jbophrase>, and both
<jbophrase role="morphology">ls</jbophrase> and
<jbophrase role="morphology">lz</jbophrase>, are permitted.
</para>
</listitem>
<listitem>
<para>It is forbidden for both consonants to be drawn from the set
<simplelist type="inline">
<member><jbophrase role="letteral">c</jbophrase></member>
<member><jbophrase role="letteral">j</jbophrase></member>
- <member><jbophrase role="letteral">s</jbophrase></member> and
+ <member><jbophrase role="letteral">s</jbophrase> and</member>
<member><jbophrase role="letteral">z</jbophrase></member>
</simplelist>
</para>
</listitem>
<listitem>
<para>The specific pairs
<simplelist type="inline">
<member><jbophrase role="morphology" valid="false">cx</jbophrase></member>
<member><jbophrase role="morphology" valid="false">kx</jbophrase></member>
<member><jbophrase role="morphology" valid="false">xc</jbophrase></member>
- <member><jbophrase role="morphology" valid="false">xk</jbophrase></member> and
+ <member><jbophrase role="morphology" valid="false">xk</jbophrase> and</member>
<member><jbophrase role="morphology" valid="false">mz</jbophrase></member>
</simplelist> are forbidden.
</para>
</listitem>
</orderedlist>
<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>
@@ -1128,21 +1128,21 @@
</section>
<section xml:id="section-buffer-vowels">
<title>Buffering Of Consonant Clusters</title>
<para> <indexterm type="general-imported"><primary>vowel</primary><secondary>buffer</secondary></indexterm> <indexterm type="general-imported"><primary>buffer vowel</primary></indexterm> <indexterm type="general-imported"><primary>consonant clusters</primary><secondary>buffering of</secondary></indexterm> Many languages do not have consonant clusters at all, and even those languages that do have them often allow only a subset of the full Lojban set. As a result, the Lojban design allows the use of a buffer sound between consonant combinations which a speaker finds unpronounceable. This sound may be any non-Lojbanic vowel which is clearly separable by the listener from the Lojban vowels. Some possibilities are IPA
<simplelist>
<member><phrase role="IPA">[ɪ]</phrase></member>
<member><phrase role="IPA">[ɨ]</phrase></member>
- <member><phrase role="IPA">[ʊ]</phrase></member> or even
+ <member><phrase role="IPA">[ʊ]</phrase> or even</member>
<member><phrase role="IPA">[ʏ]</phrase></member>
</simplelist> 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>
@@ -1332,21 +1332,21 @@
<quote>stressed syllable</quote> and
<quote>stressed vowel</quote> are largely interchangeable concepts.</para>
<para> <indexterm type="general-imported"><primary>stress</primary><secondary>rules for</secondary></indexterm> Most Lojban words are stressed on the next-to-the-last, or penultimate, syllable. In counting syllables, however, syllables whose vowel is <jbophrase role="letteral">y</jbophrase> or which contain a syllabic consonant (
<simplelist type="inline">
<member><jbophrase role="letteral">l</jbophrase></member>
<member><jbophrase role="letteral">m</jbophrase></member>
- <member><jbophrase role="letteral">n</jbophrase></member> or
+ <member><jbophrase role="letteral">n</jbophrase> or</member>
<member><jbophrase role="letteral">r</jbophrase></member>
</simplelist>) are never counted. (The Lojban term for penultimate stress is
<jbophrase>da'amoi terbasna</jbophrase>.) Similarly, syllables created solely by adding a buffer vowel, such as
<phrase role="IPA">[ɪ]</phrase>, are not counted.</para>
<para> <indexterm type="general-imported"><primary>stress</primary><secondary>levels of</secondary></indexterm> There are actually three levels of stress - primary, secondary, and weak. Weak stress is the lowest level, so it really means no stress at all. Weak stress is required for syllables containing
<jbophrase role="letteral">y</jbophrase>, a syllabic consonant, or a buffer vowel.</para>
<para> <indexterm type="general-imported"><primary>names</primary><secondary>stress on</secondary></indexterm> <indexterm type="general-imported"><primary>brivla</primary><secondary>stress on</secondary></indexterm> <indexterm type="general-imported"><primary>cmavo</primary><secondary>stress on</secondary></indexterm> <indexterm type="general-imported"><primary>stress</primary><secondary>primary</secondary></indexterm> Primary stress is required on the penultimate syllable of Lojban content words (called
<jbophrase>brivla</jbophrase>). Lojbanized names may be stressed on any syllable, but if a syllable other than the penultimate is stressed, the syllable (or at least its vowel) must be capitalized in writing. Lojban structural words (called
@@ -2180,21 +2180,21 @@
<member><quote>л</quote></member>
<member><quote>м</quote></member>
<member><quote>н</quote></member>
<member><quote>о</quote></member>
<member><quote>п</quote></member>
<member><quote>р</quote></member>
<member><quote>с</quote></member>
<member><quote>т</quote></member>
<member><quote>у</quote></member>
<member><quote>ф</quote></member>
- <member><quote>х</quote></member> and
+ <member><quote>х</quote> and</member>
<member><quote>ш</quote></member>
</simplelist> in the obvious ways. The Latin letter
<quote>y</quote> is mapped onto the hard sign
<quote>ъ</quote>, as in Bulgarian. The apostrophe, comma, and period are unchanged. Diphthongs are written as vowel pairs, as in the Roman representation.
</para>
<para> <indexterm type="general-imported"><primary>Tolkien</primary><secondary>and non-standard Lojban orthography</secondary></indexterm> <indexterm type="general-imported"><primary>non-standard orthographies</primary><secondary>Tengwar</secondary></indexterm> Finally, an orthography using the Tengwar of Féanor, a fictional orthography invented by J. R. R. Tolkien and described in the Appendixes to
diff --git a/todocbook/4.xml b/todocbook/4.xml
index bfb6bff..33e929f 100644
--- a/todocbook/4.xml
+++ b/todocbook/4.xml
@@ -2192,21 +2192,21 @@
<varlistentry>
<term>5)</term>
<listitem>
<para>Count the number of vowels, not including
<jbophrase role="letteral">y</jbophrase>; call it
<quote>V</quote>.</para>
</listitem>
</varlistentry>
</variablelist>
<para> <indexterm type="general-imported"><primary>lujvo form</primary><secondary>hierarchy of priorities for selection of</secondary></indexterm> <indexterm type="general-imported"><primary>hierarchy of priorities for selecting lujvo form</primary></indexterm> The score is then:
- <informalequation>(1000 * L) - (500 * A) + (100 * H) - (10 * R) - V</informalequation>
+ <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="interlinear-gloss-example">
<title>
<anchor xml:id="c4e12d1"/>
</title>
<interlinear-gloss>
<jbo>zbasai</jbo>
<gloss>zba + sai</gloss>
@@ -2246,255 +2246,255 @@
</title>
<interlinear-gloss>
<jbo>zbazbasysarji</jbo>
<gloss>zba + zbas + y + sarji</gloss>
<gloss>(1000 * 13) - (500 * 0) + (100 * 1) - (10 * 12) - 4</gloss>
<en>= 12976</en>
</interlinear-gloss>
</example>
</section>
<section xml:id="section-lujvo-making-examples">
- <title>lujvo-making examples</title>
- <para>This section contains examples of making and scoring lujvo. First, we will start with the tanru
- <jbophrase>gerku zdani</jbophrase> (
- <quote>dog house</quote>) and construct a lujvo meaning
-
-
- <quote>doghouse</quote>, that is, a house where a dog lives. We will use a brute-force application of the algorithm in
- <xref linkend="section-lujvo-scoring"/>, using every possible rafsi.</para>
- <para>The rafsi for
- <jbophrase>gerku</jbophrase> are:</para>
- <simplelist type="horiz" columns="4">
- <member>-<jbophrase role="rafsi">ger</jbophrase>-, </member>
- <member>-<jbophrase role="rafsi">ge'u</jbophrase>-, </member>
- <member>-<jbophrase role="rafsi">gerk</jbophrase>-, </member>
- <member>-<jbophrase role="rafsi">gerku</jbophrase></member>
- </simplelist>
- <para>The rafsi for
- <jbophrase>zdani</jbophrase> are:</para>
- <simplelist type="horiz" columns="3">
- <member>-<jbophrase role="rafsi">zda</jbophrase>-, </member>
- <member>-<jbophrase role="rafsi">zdan</jbophrase>-, </member>
- <member>-<jbophrase role="rafsi">zdani</jbophrase>.</member>
- </simplelist>
- <para>Step 1 of the algorithm directs us to use
- -<jbophrase role="rafsi">ger</jbophrase>-,
- -<jbophrase role="rafsi">ge'u</jbophrase>- and
- -<jbophrase role="rafsi">gerk</jbophrase>- as possible rafsi for
- <jbophrase>gerku</jbophrase>; Step 2 directs us to use
- -<jbophrase role="rafsi">zda</jbophrase>- and
- -<jbophrase role="rafsi">zdani</jbophrase> as possible rafsi for
- <jbophrase>zdani</jbophrase>. The six possible forms of the lujvo are then:</para>
- <simplelist type="vert" columns="1">
- <member><jbophrase>ger-zda</jbophrase></member>
- <member><jbophrase>ger-zdani</jbophrase></member>
- <member><jbophrase>ge'u-zda</jbophrase></member>
- <member><jbophrase>ge'u-zdani</jbophrase></member>
- <member><jbophrase>gerk-zda</jbophrase></member>
- <member><jbophrase>gerk-zdani</jbophrase></member>
- </simplelist>
- <para>We must then insert appropriate hyphens in each case. The first two forms need no hyphenation:
-
- <jbophrase>ge</jbophrase> cannot fall off the front, because the following word would begin with
- <jbophrase role="morphology">rz</jbophrase>, which is not a permissible initial consonant pair. So the lujvo forms are
- <jbophrase>gerzda</jbophrase> and
- <jbophrase>gerzdani</jbophrase>.</para>
- <para>The third form,
- <jbophrase>ge'u-zda</jbophrase>, needs no hyphen, because even though the first rafsi is CVV, the second one is CCV, so there is a consonant cluster in the first five letters. So
- <jbophrase>ge'uzda</jbophrase> is this form of the lujvo.</para>
- <para>The fourth form,
- <jbophrase valid="false">ge'u-zdani</jbophrase>, however, requires an
- <jbophrase role="letteral">r</jbophrase>-hyphen; otherwise, the
- <jbophrase role="rafsi">ge'u</jbophrase>- part would fall off as a cmavo. So this form of the lujvo is
- <jbophrase>ge'urzdani</jbophrase>.</para>
- <para>The last two forms require
- <jbophrase role="letteral">y</jbophrase>-hyphens, as all 4-letter rafsi do, and so are
-
- <jbophrase>gerkyzda</jbophrase> and
- <jbophrase>gerkyzdani</jbophrase> respectively.</para>
- <para> <!-- FIXME: there's nowhere for this indexterm to go --><indexterm type="example-imported"><primary>boat class</primary><secondary>example</secondary></indexterm> The scoring algorithm is heavily weighted in favor of short lujvo, so we might expect that
- <jbophrase>gerzda</jbophrase> would win. Its <varname>L</varname> score is 6, its <varname>A</varname> score is 0, its <varname>H</varname> score is 0, its <varname>R</varname> score is 12, and its <varname>V</varname> score is 3, for a final score of 5878. The other forms have scores of 7917, 6367, 9506, 8008, and 10047 respectively. Consequently, this lujvo would probably appear in the dictionary in the form
- <jbophrase>gerzda</jbophrase>.</para>
- <para>For the next example, we will use the tanru
- <jbophrase>bloti klesi</jbophrase> (
- <quote>boat class</quote>) presumably referring to the category (rowboat, motorboat, cruise liner) into which a boat falls. We will omit the long rafsi from the process, since lujvo containing long rafsi are almost never preferred by the scoring algorithm when there are short rafsi available.</para>
- <para>The rafsi for
- <jbophrase>bloti</jbophrase> are
- -<jbophrase role="rafsi">lot</jbophrase>-,
- -<jbophrase role="rafsi">blo</jbophrase>-, and
- -<jbophrase role="rafsi">lo'i</jbophrase>-; for
- <jbophrase>klesi</jbophrase> they are
- -<jbophrase role="rafsi">kle</jbophrase>- and
- -<jbophrase role="rafsi">lei</jbophrase>-. Both these gismu are among the handful which have both CVV-form and CCV-form rafsi, so there is an unusual number of possibilities available for a two-part tanru:</para>
- <simplelist type="horiz" columns="3">
- <member><jbophrase>lotkle</jbophrase></member>
- <member><jbophrase>blokle</jbophrase></member>
- <member><jbophrase>lo'ikle</jbophrase></member>
-
- <member><jbophrase>lotlei</jbophrase></member>
- <member><jbophrase>blolei</jbophrase></member>
- <member><jbophrase>lo'irlei</jbophrase></member>
- </simplelist>
- <para>Only
- <jbophrase>lo'irlei</jbophrase> requires hyphenation (to avoid confusion with the cmavo sequence
- <jbophrase>lo'i lei</jbophrase>). All six forms are valid versions of the lujvo, as are the six further forms using long rafsi; however, the scoring algorithm produces the following results:</para>
-
- <simplelist type="horiz" columns="6">
- <member><jbophrase>lotkle</jbophrase></member>
- <member>5878</member>
- <member><jbophrase>blokle</jbophrase></member>
- <member>5858</member>
- <member><jbophrase>lo'ikle</jbophrase></member>
- <member>6367</member>
-
- <member><jbophrase>lotlei</jbophrase></member>
- <member>5867</member>
- <member><jbophrase>blolei</jbophrase></member>
- <member>5847</member>
- <member><jbophrase>lo'irlei</jbophrase></member>
- <member>7456</member>
- </simplelist>
- <para> <indexterm type="example-imported"><primary>Logical Language Group</primary><secondary>example</secondary></indexterm> So the form
- <jbophrase>blolei</jbophrase> is preferred, but only by a tiny margin over
- <jbophrase>blokle</jbophrase>; "lotlei" and "lotkle" are only slightly worse;
- <jbophrase>lo'ikle</jbophrase> suffers because of its apostrophe, and
- <jbophrase>lo'irlei</jbophrase> because of having both apostrophe and hyphen.</para>
- <para>Our third example will result in forming both a lujvo and a name from the tanru
- <jbophrase>logji bangu girzu</jbophrase>, or
- <quote>logical-language group</quote> in English. (
- <quote>The Logical Language Group</quote> is the name of the publisher of this book and the organization for the promotion of Lojban.)</para>
- <para>The available rafsi are
- -<jbophrase role="rafsi">loj</jbophrase>- and
- -<jbophrase role="rafsi">logj</jbophrase>-;
- -<jbophrase role="rafsi">ban</jbophrase>-,
- -<jbophrase role="rafsi">bau</jbophrase>-, and
- -<jbophrase role="rafsi">bang</jbophrase>-; and
- -<jbophrase role="rafsi">gri</jbophrase>- and
- -<jbophrase role="rafsi">girzu</jbophrase>, and (for name purposes only)
- -<jbophrase role="rafsi">gir</jbophrase>- and
- -<jbophrase role="rafsi">girz</jbophrase>-. The resulting 12 lujvo possibilities are:</para>
- <simplelist type="horiz" columns="3">
- <member><jbophrase>loj-ban-gri</jbophrase></member>
- <member><jbophrase>loj-bau-gri</jbophrase></member>
- <member><jbophrase>loj-bang-gri</jbophrase></member>
-
- <member><jbophrase>logj-ban-gri</jbophrase></member>
- <member><jbophrase>logj-bau-gri</jbophrase></member>
- <member><jbophrase>logj-bang-gri</jbophrase></member>
-
- <member><jbophrase>loj-ban-girzu</jbophrase></member>
- <member><jbophrase>loj-bau-girzu</jbophrase></member>
- <member><jbophrase>loj-bang-girzu</jbophrase></member>
-
- <member><jbophrase>logj-ban-girzu</jbophrase></member>
- <member><jbophrase>logj-bau-girzu</jbophrase></member>
- <member><jbophrase>logj-bang-girzu</jbophrase></member>
- </simplelist>
- <para>and the 12 name possibilities are:</para>
- <simplelist type="horiz" columns="3">
- <member><jbophrase>loj-ban-gir</jbophrase></member>
- <member><jbophrase>loj-bau-gir</jbophrase></member>
- <member><jbophrase>loj-bang-gir</jbophrase></member>
-
- <member><jbophrase>logj-ban-gir</jbophrase></member>
- <member><jbophrase>logj-bau-gir</jbophrase></member>
- <member><jbophrase>logj-bang-gir</jbophrase></member>
-
- <member><jbophrase>loj-ban-girz</jbophrase></member>
- <member><jbophrase>loj-bau-girz</jbophrase></member>
- <member><jbophrase>loj-bang-girz</jbophrase></member>
-
- <member><jbophrase>logj-ban-girz</jbophrase></member>
- <member><jbophrase>logj-bau-girz</jbophrase></member>
- <member><jbophrase>logj-bang-girz</jbophrase></member>
- </simplelist>
- <para>After hyphenation, we have:</para>
- <simplelist type="horiz" columns="3">
- <member><jbophrase>lojbangri</jbophrase></member>
- <member><jbophrase>lojbaugri</jbophrase></member>
- <member><jbophrase>lojbangygri</jbophrase></member>
-
- <member><jbophrase>logjybangri</jbophrase></member>
- <member><jbophrase>logjybaugri</jbophrase></member>
- <member><jbophrase>logjybangygri</jbophrase></member>
-
- <member><jbophrase>lojbangirzu</jbophrase></member>
- <member><jbophrase>lojbaugirzu</jbophrase></member>
- <member><jbophrase>lojbangygirzu</jbophrase></member>
-
- <member><jbophrase>logjybangirzu</jbophrase></member>
- <member><jbophrase>logjybaugirzu</jbophrase></member>
- <member><jbophrase>logjybangygirzu</jbophrase></member>
-
- <member><jbophrase>lojbangir</jbophrase></member>
- <member><jbophrase>lojbaugir</jbophrase></member>
- <member><jbophrase>lojbangygir</jbophrase></member>
-
- <member><jbophrase>logjybangir</jbophrase></member>
- <member><jbophrase>logjybaugir</jbophrase></member>
- <member><jbophrase>logjybangygir</jbophrase></member>
-
- <member><jbophrase>lojbangirz</jbophrase></member>
- <member><jbophrase>lojbaugirz</jbophrase></member>
- <member><jbophrase>lojbangygirz</jbophrase></member>
-
- <member><jbophrase>logjybangirz</jbophrase></member>
- <member><jbophrase>logjybaugirz</jbophrase></member>
- <member><jbophrase>logjybangygirz</jbophrase></member>
- </simplelist>
- <para> <!-- FIXME: there's nowhere for these two indexterms to go --><indexterm type="example-imported"><primary>sexual teacher</primary><secondary>male</secondary><tertiary>example</tertiary></indexterm> <indexterm type="example-imported"><primary>male sexual teacher</primary><secondary>example</secondary></indexterm> The only fully reduced lujvo forms are
-
- <jbophrase>lojbangri</jbophrase> and
- <jbophrase>lojbaugri</jbophrase>, of which the latter has a slightly lower score: 8827 versus 8796, respectively. However, for the name of the organization, we chose to make sure the name of the language was embedded in it, and to use the clearer long-form rafsi for
- <jbophrase>girzu</jbophrase>, producing
- <jbophrase>lojbangirz.</jbophrase></para>
- <para>Finally, here is a four-part lujvo with a cmavo in it, based on the tanru
- <jbophrase>nakni ke cinse ctuca</jbophrase> or
- <quote>male (sexual teacher)</quote>. The
-
- <jbophrase>ke</jbophrase> cmavo ensures the interpretation
- <quote>teacher of sexuality who is male</quote>, rather than
- <quote>teacher of male sexuality</quote>. Here are the possible forms of the lujvo, both before and after hyphenation:</para>
- <simplelist type="horiz" columns="2">
- <member><jbophrase>nak-kem-cin-ctu</jbophrase></member>
- <member><jbophrase>nakykemcinctu</jbophrase></member>
-
- <member><jbophrase>nak-kem-cin-ctuca</jbophrase></member>
- <member><jbophrase>nakykemcinctuca</jbophrase></member>
-
- <member><jbophrase>nak-kem-cins-ctu</jbophrase></member>
- <member><jbophrase>nakykemcinsyctu</jbophrase></member>
-
- <member><jbophrase>nak-kem-cins-ctuca</jbophrase></member>
- <member><jbophrase>nakykemcinsyctuca</jbophrase></member>
-
- <member><jbophrase>nakn-kem-cin-ctu</jbophrase></member>
- <member><jbophrase>naknykemcinctu</jbophrase></member>
-
- <member><jbophrase>nakn-kem-cin-ctuca</jbophrase></member>
- <member><jbophrase>naknykemcinctuca</jbophrase></member>
-
- <member><jbophrase>nakn-kem-cins-ctu</jbophrase></member>
- <member><jbophrase>naknykemcinsyctu</jbophrase></member>
-
- <member><jbophrase>nakn-kem-cins-ctuca</jbophrase></member>
- <member><jbophrase>naknykemcinsyctuca</jbophrase></member>
- </simplelist>
- <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>algorithm for</secondary></indexterm> Of these forms,
- <jbophrase>nakykemcinctu</jbophrase> is the shortest and is preferred by the scoring algorithm. On the whole, however, it might be better to just make a lujvo for
- <jbophrase>cinse ctuca</jbophrase> (which would be
- <jbophrase>cinctu</jbophrase>) since the sex of the teacher is rarely important. If there was a reason to specify
- <quote>male</quote>, then the simpler tanru
- <jbophrase>nakni cinctu</jbophrase> (
- <quote>male sexual-teacher</quote>) would be appropriate. This tanru is actually shorter than the four-part lujvo, since the
- <jbophrase>ke</jbophrase> required for grouping need not be expressed.</para>
-</section>
+ <title>lujvo-making examples</title>
+ <para>This section contains examples of making and scoring lujvo. First, we will start with the tanru
+ <jbophrase>gerku zdani</jbophrase> (
+ <quote>dog house</quote>) and construct a lujvo meaning
+
+
+ <quote>doghouse</quote>, that is, a house where a dog lives. We will use a brute-force application of the algorithm in
+ <xref linkend="section-lujvo-scoring"/>, using every possible rafsi.</para>
+ <para>The rafsi for
+ <jbophrase>gerku</jbophrase> are:</para>
+ <simplelist type="horiz" columns="4">
+ <member>-<jbophrase role="rafsi">ger</jbophrase>-, </member>
+ <member>-<jbophrase role="rafsi">ge'u</jbophrase>-, </member>
+ <member>-<jbophrase role="rafsi">gerk</jbophrase>-, </member>
+ <member>-<jbophrase role="rafsi">gerku</jbophrase></member>
+ </simplelist>
+ <para>The rafsi for
+ <jbophrase>zdani</jbophrase> are:</para>
+ <simplelist type="horiz" columns="3">
+ <member>-<jbophrase role="rafsi">zda</jbophrase>-, </member>
+ <member>-<jbophrase role="rafsi">zdan</jbophrase>-, </member>
+ <member>-<jbophrase role="rafsi">zdani</jbophrase>.</member>
+ </simplelist>
+ <para>Step 1 of the algorithm directs us to use
+ -<jbophrase role="rafsi">ger</jbophrase>-,
+ -<jbophrase role="rafsi">ge'u</jbophrase>- and
+ -<jbophrase role="rafsi">gerk</jbophrase>- as possible rafsi for
+ <jbophrase>gerku</jbophrase>; Step 2 directs us to use
+ -<jbophrase role="rafsi">zda</jbophrase>- and
+ -<jbophrase role="rafsi">zdani</jbophrase> as possible rafsi for
+ <jbophrase>zdani</jbophrase>. The six possible forms of the lujvo are then:</para>
+ <simplelist type="vert" columns="1">
+ <member><jbophrase>ger-zda</jbophrase></member>
+ <member><jbophrase>ger-zdani</jbophrase></member>
+ <member><jbophrase>ge'u-zda</jbophrase></member>
+ <member><jbophrase>ge'u-zdani</jbophrase></member>
+ <member><jbophrase>gerk-zda</jbophrase></member>
+ <member><jbophrase>gerk-zdani</jbophrase></member>
+ </simplelist>
+ <para>We must then insert appropriate hyphens in each case. The first two forms need no hyphenation:
+
+ <jbophrase>ge</jbophrase> cannot fall off the front, because the following word would begin with
+ <jbophrase role="morphology">rz</jbophrase>, which is not a permissible initial consonant pair. So the lujvo forms are
+ <jbophrase>gerzda</jbophrase> and
+ <jbophrase>gerzdani</jbophrase>.</para>
+ <para>The third form,
+ <jbophrase>ge'u-zda</jbophrase>, needs no hyphen, because even though the first rafsi is CVV, the second one is CCV, so there is a consonant cluster in the first five letters. So
+ <jbophrase>ge'uzda</jbophrase> is this form of the lujvo.</para>
+ <para>The fourth form,
+ <jbophrase valid="false">ge'u-zdani</jbophrase>, however, requires an
+ <jbophrase role="letteral">r</jbophrase>-hyphen; otherwise, the
+ <jbophrase role="rafsi">ge'u</jbophrase>- part would fall off as a cmavo. So this form of the lujvo is
+ <jbophrase>ge'urzdani</jbophrase>.</para>
+ <para>The last two forms require
+ <jbophrase role="letteral">y</jbophrase>-hyphens, as all 4-letter rafsi do, and so are
+
+ <jbophrase>gerkyzda</jbophrase> and
+ <jbophrase>gerkyzdani</jbophrase> respectively.</para>
+ <para> <!-- FIXME: there's nowhere for this indexterm to go --><indexterm type="example-imported"><primary>boat class</primary><secondary>example</secondary></indexterm> The scoring algorithm is heavily weighted in favor of short lujvo, so we might expect that
+ <jbophrase>gerzda</jbophrase> would win. Its <varname>L</varname> score is 6, its <varname>A</varname> score is 0, its <varname>H</varname> score is 0, its <varname>R</varname> score is 12, and its <varname>V</varname> score is 3, for a final score of 5878. The other forms have scores of 7917, 6367, 9506, 8008, and 10047 respectively. Consequently, this lujvo would probably appear in the dictionary in the form
+ <jbophrase>gerzda</jbophrase>.</para>
+ <para>For the next example, we will use the tanru
+ <jbophrase>bloti klesi</jbophrase> (
+ <quote>boat class</quote>) presumably referring to the category (rowboat, motorboat, cruise liner) into which a boat falls. We will omit the long rafsi from the process, since lujvo containing long rafsi are almost never preferred by the scoring algorithm when there are short rafsi available.</para>
+ <para>The rafsi for
+ <jbophrase>bloti</jbophrase> are
+ -<jbophrase role="rafsi">lot</jbophrase>-,
+ -<jbophrase role="rafsi">blo</jbophrase>-, and
+ -<jbophrase role="rafsi">lo'i</jbophrase>-; for
+ <jbophrase>klesi</jbophrase> they are
+ -<jbophrase role="rafsi">kle</jbophrase>- and
+ -<jbophrase role="rafsi">lei</jbophrase>-. Both these gismu are among the handful which have both CVV-form and CCV-form rafsi, so there is an unusual number of possibilities available for a two-part tanru:</para>
+ <simplelist type="horiz" columns="3">
+ <member><jbophrase>lotkle</jbophrase></member>
+ <member><jbophrase>blokle</jbophrase></member>
+ <member><jbophrase>lo'ikle</jbophrase></member>
+
+ <member><jbophrase>lotlei</jbophrase></member>
+ <member><jbophrase>blolei</jbophrase></member>
+ <member><jbophrase>lo'irlei</jbophrase></member>
+ </simplelist>
+ <para>Only
+ <jbophrase>lo'irlei</jbophrase> requires hyphenation (to avoid confusion with the cmavo sequence
+ <jbophrase>lo'i lei</jbophrase>). All six forms are valid versions of the lujvo, as are the six further forms using long rafsi; however, the scoring algorithm produces the following results:</para>
+
+ <simplelist type="horiz" columns="6">
+ <member><jbophrase>lotkle</jbophrase></member>
+ <member>5878</member>
+ <member><jbophrase>blokle</jbophrase></member>
+ <member>5858</member>
+ <member><jbophrase>lo'ikle</jbophrase></member>
+ <member>6367</member>
+
+ <member><jbophrase>lotlei</jbophrase></member>
+ <member>5867</member>
+ <member><jbophrase>blolei</jbophrase></member>
+ <member>5847</member>
+ <member><jbophrase>lo'irlei</jbophrase></member>
+ <member>7456</member>
+ </simplelist>
+ <para> <indexterm type="example-imported"><primary>Logical Language Group</primary><secondary>example</secondary></indexterm> So the form
+ <jbophrase>blolei</jbophrase> is preferred, but only by a tiny margin over
+ <jbophrase>blokle</jbophrase>; "lotlei" and "lotkle" are only slightly worse;
+ <jbophrase>lo'ikle</jbophrase> suffers because of its apostrophe, and
+ <jbophrase>lo'irlei</jbophrase> because of having both apostrophe and hyphen.</para>
+ <para>Our third example will result in forming both a lujvo and a name from the tanru
+ <jbophrase>logji bangu girzu</jbophrase>, or
+ <quote>logical-language group</quote> in English. (
+ <quote>The Logical Language Group</quote> is the name of the publisher of this book and the organization for the promotion of Lojban.)</para>
+ <para>The available rafsi are
+ -<jbophrase role="rafsi">loj</jbophrase>- and
+ -<jbophrase role="rafsi">logj</jbophrase>-;
+ -<jbophrase role="rafsi">ban</jbophrase>-,
+ -<jbophrase role="rafsi">bau</jbophrase>-, and
+ -<jbophrase role="rafsi">bang</jbophrase>-; and
+ -<jbophrase role="rafsi">gri</jbophrase>- and
+ -<jbophrase role="rafsi">girzu</jbophrase>, and (for name purposes only)
+ -<jbophrase role="rafsi">gir</jbophrase>- and
+ -<jbophrase role="rafsi">girz</jbophrase>-. The resulting 12 lujvo possibilities are:</para>
+ <simplelist type="horiz" columns="3">
+ <member><jbophrase>loj-ban-gri</jbophrase></member>
+ <member><jbophrase>loj-bau-gri</jbophrase></member>
+ <member><jbophrase>loj-bang-gri</jbophrase></member>
+
+ <member><jbophrase>logj-ban-gri</jbophrase></member>
+ <member><jbophrase>logj-bau-gri</jbophrase></member>
+ <member><jbophrase>logj-bang-gri</jbophrase></member>
+
+ <member><jbophrase>loj-ban-girzu</jbophrase></member>
+ <member><jbophrase>loj-bau-girzu</jbophrase></member>
+ <member><jbophrase>loj-bang-girzu</jbophrase></member>
+
+ <member><jbophrase>logj-ban-girzu</jbophrase></member>
+ <member><jbophrase>logj-bau-girzu</jbophrase></member>
+ <member><jbophrase>logj-bang-girzu</jbophrase></member>
+ </simplelist>
+ <para>and the 12 name possibilities are:</para>
+ <simplelist type="horiz" columns="3">
+ <member><jbophrase>loj-ban-gir</jbophrase></member>
+ <member><jbophrase>loj-bau-gir</jbophrase></member>
+ <member><jbophrase>loj-bang-gir</jbophrase></member>
+
+ <member><jbophrase>logj-ban-gir</jbophrase></member>
+ <member><jbophrase>logj-bau-gir</jbophrase></member>
+ <member><jbophrase>logj-bang-gir</jbophrase></member>
+
+ <member><jbophrase>loj-ban-girz</jbophrase></member>
+ <member><jbophrase>loj-bau-girz</jbophrase></member>
+ <member><jbophrase>loj-bang-girz</jbophrase></member>
+
+ <member><jbophrase>logj-ban-girz</jbophrase></member>
+ <member><jbophrase>logj-bau-girz</jbophrase></member>
+ <member><jbophrase>logj-bang-girz</jbophrase></member>
+ </simplelist>
+ <para>After hyphenation, we have:</para>
+ <simplelist type="horiz" columns="3">
+ <member><jbophrase>lojbangri</jbophrase></member>
+ <member><jbophrase>lojbaugri</jbophrase></member>
+ <member><jbophrase>lojbangygri</jbophrase></member>
+
+ <member><jbophrase>logjybangri</jbophrase></member>
+ <member><jbophrase>logjybaugri</jbophrase></member>
+ <member><jbophrase>logjybangygri</jbophrase></member>
+
+ <member><jbophrase>lojbangirzu</jbophrase></member>
+ <member><jbophrase>lojbaugirzu</jbophrase></member>
+ <member><jbophrase>lojbangygirzu</jbophrase></member>
+
+ <member><jbophrase>logjybangirzu</jbophrase></member>
+ <member><jbophrase>logjybaugirzu</jbophrase></member>
+ <member><jbophrase>logjybangygirzu</jbophrase></member>
+
+ <member><jbophrase>lojbangir</jbophrase></member>
+ <member><jbophrase>lojbaugir</jbophrase></member>
+ <member><jbophrase>lojbangygir</jbophrase></member>
+
+ <member><jbophrase>logjybangir</jbophrase></member>
+ <member><jbophrase>logjybaugir</jbophrase></member>
+ <member><jbophrase>logjybangygir</jbophrase></member>
+
+ <member><jbophrase>lojbangirz</jbophrase></member>
+ <member><jbophrase>lojbaugirz</jbophrase></member>
+ <member><jbophrase>lojbangygirz</jbophrase></member>
+
+ <member><jbophrase>logjybangirz</jbophrase></member>
+ <member><jbophrase>logjybaugirz</jbophrase></member>
+ <member><jbophrase>logjybangygirz</jbophrase></member>
+ </simplelist>
+ <para> <!-- FIXME: there's nowhere for these two indexterms to go --><indexterm type="example-imported"><primary>sexual teacher</primary><secondary>male</secondary><tertiary>example</tertiary></indexterm> <indexterm type="example-imported"><primary>male sexual teacher</primary><secondary>example</secondary></indexterm> The only fully reduced lujvo forms are
+
+ <jbophrase>lojbangri</jbophrase> and
+ <jbophrase>lojbaugri</jbophrase>, of which the latter has a slightly lower score: 8827 versus 8796, respectively. However, for the name of the organization, we chose to make sure the name of the language was embedded in it, and to use the clearer long-form rafsi for
+ <jbophrase>girzu</jbophrase>, producing
+ <jbophrase>lojbangirz.</jbophrase></para>
+ <para>Finally, here is a four-part lujvo with a cmavo in it, based on the tanru
+ <jbophrase>nakni ke cinse ctuca</jbophrase> or
+ <quote>male (sexual teacher)</quote>. The
+
+ <jbophrase>ke</jbophrase> cmavo ensures the interpretation
+ <quote>teacher of sexuality who is male</quote>, rather than
+ <quote>teacher of male sexuality</quote>. Here are the possible forms of the lujvo, both before and after hyphenation:</para>
+ <simplelist type="horiz" columns="2">
+ <member><jbophrase>nak-kem-cin-ctu</jbophrase></member>
+ <member><jbophrase>nakykemcinctu</jbophrase></member>
+
+ <member><jbophrase>nak-kem-cin-ctuca</jbophrase></member>
+ <member><jbophrase>nakykemcinctuca</jbophrase></member>
+
+ <member><jbophrase>nak-kem-cins-ctu</jbophrase></member>
+ <member><jbophrase>nakykemcinsyctu</jbophrase></member>
+
+ <member><jbophrase>nak-kem-cins-ctuca</jbophrase></member>
+ <member><jbophrase>nakykemcinsyctuca</jbophrase></member>
+
+ <member><jbophrase>nakn-kem-cin-ctu</jbophrase></member>
+ <member><jbophrase>naknykemcinctu</jbophrase></member>
+
+ <member><jbophrase>nakn-kem-cin-ctuca</jbophrase></member>
+ <member><jbophrase>naknykemcinctuca</jbophrase></member>
+
+ <member><jbophrase>nakn-kem-cins-ctu</jbophrase></member>
+ <member><jbophrase>naknykemcinsyctu</jbophrase></member>
+
+ <member><jbophrase>nakn-kem-cins-ctuca</jbophrase></member>
+ <member><jbophrase>naknykemcinsyctuca</jbophrase></member>
+ </simplelist>
+ <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>algorithm for</secondary></indexterm> Of these forms,
+ <jbophrase>nakykemcinctu</jbophrase> is the shortest and is preferred by the scoring algorithm. On the whole, however, it might be better to just make a lujvo for
+ <jbophrase>cinse ctuca</jbophrase> (which would be
+ <jbophrase>cinctu</jbophrase>) since the sex of the teacher is rarely important. If there was a reason to specify
+ <quote>male</quote>, then the simpler tanru
+ <jbophrase>nakni cinctu</jbophrase> (
+ <quote>male sexual-teacher</quote>) would be appropriate. This tanru is actually shorter than the four-part lujvo, since the
+ <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 (
@@ -2536,318 +2536,671 @@
<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>
+ <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>
- <programlisting>
- Chinese 0.36
- English 0.21
- Hindi 0.16
- Spanish 0.11
- Russian 0.09
- Arabic 0.07
- </programlisting>
+ <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>
- <programlisting>
- Chinese 0.347
- Hindi 0.196
- English 0.160
- Spanish 0.123
- Russian 0.089
- Arabic 0.085
- </programlisting>
+ <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>
<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>
<para>The following gismu were not made by the gismu creation algorithm. They are, in effect, coined words similar to fu'ivla. They are exceptions to the otherwise mandatory gismu creation algorithm where there was sufficient justification for such exceptions. Except for the small metric prefixes and the assignable predicates beginning with
<jbophrase role="rafsi">brod</jbophrase>-, they all end in the letter
<jbophrase role="letteral">o</jbophrase>, which is otherwise a rare letter in Lojban gismu.</para>
<para> <indexterm type="general-imported"><primary>gismu</primary><secondary>scientific-mathematical</secondary></indexterm> The following gismu represent concepts that are sufficiently unique to Lojban that they were either coined from combining forms of other gismu, or else made up out of whole cloth. These gismu are thus conceptually similar to lujvo even though they are only five letters long; however, unlike lujvo, they have rafsi assigned to them for use in building more complex lujvo. Assigning gismu to these concepts helps to keep the resulting lujvo reasonably short.</para>
- <programlisting xml:space="preserve">
- broda 1st assignable predicate
- brode 2nd assignable predicate
- brodi 3rd assignable predicate
- brodo 4th assignable predicate
- brodu 5th assignable predicate
- cmavo structure word (from
- <jbophrase>cmalu valsi</jbophrase>)
- lojbo Lojbanic (from
- <jbophrase>logji bangu</jbophrase>)
- lujvo compound word (from
- <jbophrase>pluja valsi</jbophrase>)
- mekso Mathematical EXpression
- </programlisting>
+ <variablelist>
+ <varlistentry>
+ <term><jbophrase>broda</jbophrase></term>
+ <listitem><para>1st assignable predicate</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>brode</jbophrase></term>
+ <listitem><para>2nd assignable predicate</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>brodi</jbophrase></term>
+ <listitem><para>3rd assignable predicate</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>brodo</jbophrase></term>
+ <listitem><para>4th assignable predicate</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>brodu</jbophrase></term>
+ <listitem><para>5th assignable predicate</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>cmavo</jbophrase></term>
+ <listitem><para>structure word (from <jbophrase>cmalu valsi</jbophrase>)</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>lojbo</jbophrase></term>
+ <listitem><para>Lojbanic (from <jbophrase>logji bangu</jbophrase>)</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>lujvo</jbophrase></term>
+ <listitem><para>compound word (from <jbophrase>pluja valsi</jbophrase>)</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>mekso</jbophrase></term>
+ <listitem><para>Mathematical EXpression</para></listitem>
+ </varlistentry>
+ </variablelist>
<para>It is important to understand that even though
<jbophrase>cmavo</jbophrase>,
<jbophrase>lojbo</jbophrase>, and
<jbophrase>lujvo</jbophrase> were made up from parts of other gismu, they are now full-fledged gismu used in exactly the same way as all other gismu, both in grammar and in word formation.</para>
<para>The following three groups of gismu represent concepts drawn from the international language of science and mathematics. They are used for concepts that are represented in most languages by a root which is recognized internationally.</para>
<para>Small metric prefixes (values less than 1):</para>
- <programlisting xml:space="preserve">
- decti .1/deci
- centi .01/centi
- milti .001/milli
- mikri 1E-6/micro
- nanvi 1E-9/nano
- picti 1E-12/pico
- femti 1E-15/femto
- xatsi 1E-18/atto
- zepti 1E-21/zepto
- gocti 1E-24/yocto
- </programlisting>
+ <variablelist>
+ <varlistentry>
+ <term><jbophrase>decti</jbophrase></term>
+ <listitem><para>.1/deci</para></listitem>
+ </varlistentry>
+ <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>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>nanvi</jbophrase></term>
+ <listitem><para>1E-9/nano</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>picti</jbophrase></term>
+ <listitem><para>1E-12/pico</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>femti</jbophrase></term>
+ <listitem><para>1E-15/femto</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>xatsi</jbophrase></term>
+ <listitem><para>1E-18/atto</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>zepti</jbophrase></term>
+ <listitem><para>1E-21/zepto</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>gocti</jbophrase></term>
+ <listitem><para>1E-24/yocto</para></listitem>
+ </varlistentry>
+ </variablelist>
<para>Large metric prefixes (values greater than 1):</para>
- <programlisting xml:space="preserve">
- dekto 10/deka
- xecto 100/hecto
- kilto 1000/kilo
- megdo 1E6/mega
- gigdo 1E9/giga
- terto 1E12/tera
- petso 1E15/peta
- xexso 1E18/exa
- zetro 1E21/zetta
- gotro 1E24/yotta
- </programlisting>
+ <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>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>gigdo</jbophrase></term>
+ <listitem><para>1E9/giga</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>terto</jbophrase></term>
+ <listitem><para>1E12/tera</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>petso</jbophrase></term>
+ <listitem><para>1E15/peta</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>xexso</jbophrase></term>
+ <listitem><para>1E18/exa</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>zetro</jbophrase></term>
+ <listitem><para>1E21/zetta</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>gotro</jbophrase></term>
+ <listitem><para>1E24/yotta</para></listitem>
+ </varlistentry>
+ </variablelist>
<para> <indexterm type="general-imported"><primary>gismu</primary><secondary>cultural</secondary></indexterm> Other scientific or mathematical terms:</para>
- <programlisting xml:space="preserve">
- delno candela
- kelvo kelvin
- molro mole
- radno radian
- sinso sine
- stero steradian
- tanjo tangent
- xampo ampere
- </programlisting>
+ <variablelist>
+ <varlistentry>
+ <term><jbophrase>delno</jbophrase></term>
+ <listitem><para>candela</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>kelvo</jbophrase></term>
+ <listitem><para>kelvin</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>molro</jbophrase></term>
+ <listitem><para>mole</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>radno</jbophrase></term>
+ <listitem><para>radian</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>sinso</jbophrase></term>
+ <listitem><para>sine</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>stero</jbophrase></term>
+ <listitem><para>steradian</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>tanjo</jbophrase></term>
+ <listitem><para>tangent</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>xampo</jbophrase></term>
+ <listitem><para>ampere</para></listitem>
+ </varlistentry>
+ </variablelist>
<para> <indexterm type="general-imported"><primary>gismu</primary><secondary>for Lojban source languages</secondary></indexterm> <indexterm type="general-imported"><primary>gismu</primary><secondary>for languages</secondary></indexterm> The gismu
<jbophrase>sinso</jbophrase> and
<jbophrase>tanjo</jbophrase> were only made non-algorithmically because they were identical (having been borrowed from a common source) in all the dictionaries that had translations. The other terms in this group are units in the international metric system; some metric units, however, were made by the ordinary process (usually because they are different in Chinese).</para>
<para>Finally, there are the cultural gismu, which are also borrowed, but by modifying a word from one particular language, instead of using the multi-lingual gismu creation algorithm. Cultural gismu are used for words that have local importance to a particular culture; other cultures or languages may have no word for the concept at all, or may borrow the word from its home culture, just as Lojban does. In such a case, the gismu algorithm, which uses weighted averages, doesn't accurately represent the frequency of usage of the individual concept. Cultural gismu are not even required to be based on the six major languages.</para>
<para>The six Lojban source languages:</para>
-
- <programlisting xml:space="preserve">
- jungo Chinese (from
- <quote>Zhong
- <superscript>1</superscript> guo
- <superscript>2</superscript></quote>)
- glico English
- xindo Hindi
- spano Spanish
- rusko Russian
- xrabo Arabic
- </programlisting>
+
+ <variablelist>
+ <varlistentry>
+ <term><jbophrase>jungo</jbophrase></term>
+ <listitem><para>Chinese (from <quote xml:lang="zh">Zhong <superscript>1</superscript> guo <superscript>2</superscript></quote>)</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>glico</jbophrase></term>
+ <listitem><para>English</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>xindo</jbophrase></term>
+ <listitem><para>Hindi</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>spano</jbophrase></term>
+ <listitem><para>Spanish</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>rusko</jbophrase></term>
+ <listitem><para>Russian</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>xrabo</jbophrase></term>
+ <listitem><para>Arabic</para></listitem>
+ </varlistentry>
+ </variablelist>
<para> <indexterm type="general-imported"><primary>gismu</primary><secondary>for countries</secondary></indexterm> Seven other widely spoken languages that were on the list of candidates for gismu-making, but weren't used:</para>
- <programlisting xml:space="preserve">
- bengo Bengali
- porto Portuguese
- baxso Bahasa Melayu/Bahasa Indonesia
- ponjo Japanese (from
- <quote>Nippon</quote>)
- dotco German (from
- <quote>Deutsch</quote>)
- fraso French (from
- <quote>Français</quote>)
- xurdo Urdu
- </programlisting>
+ <variablelist>
+ <varlistentry>
+ <term><jbophrase>bengo</jbophrase></term>
+ <listitem><para>Bengali</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>porto</jbophrase></term>
+ <listitem><para>Portuguese</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>baxso</jbophrase></term>
+ <listitem><para>Bahasa Melayu/Bahasa Indonesia</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>ponjo</jbophrase></term>
+ <listitem><para>Japanese (from <quote xml:lang="ja">Nippon</quote>)</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>dotco</jbophrase></term>
+ <listitem><para>German (from <quote xml:lang="de">Deutsch</quote>)</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>fraso</jbophrase></term>
+ <listitem><para>French (from <quote xml:lang="fr">Français</quote>)</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>xurdo</jbophrase></term>
+ <listitem><para>Urdu</para></listitem>
+ </varlistentry>
+ </variablelist>
<para> <indexterm type="general-imported"><primary>continents</primary><secondary>gismu for</secondary></indexterm> <indexterm type="general-imported"><primary>gismu</primary><secondary>geographical</secondary></indexterm> (Urdu and Hindi began as the same language with different writing systems, but have now become somewhat different, principally in borrowed vocabulary. Urdu-speakers were counted along with Hindi-speakers when weights were assigned for gismu-making purposes.)</para>
- <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>ethnic</secondary></indexterm> Countries with a large number of speakers of any of the above languages (where the meaning of
- <jbophrase>large</jbophrase> is dependent on the specific language):</para>
- <programlisting xml:space="preserve">
- English:
-
- merko American
- brito British
- skoto Scottish
- sralo Australian
- kadno Canadian
-
- Spanish:
-
- gento Argentinian
- mexno Mexican
-
- Russian:
-
- softo Soviet/USSR
- vukro Ukrainian
-
- Arabic:
-
- filso Palestinian
- jerxo Algerian
- jordo Jordanian
- libjo Libyan
- lubno Lebanese
- misro Egyptian (from
- <quote>Mizraim</quote>)
- morko Moroccan
- rakso Iraqi
- sadjo Saudi
- sirxo Syrian
-
- Bahasa Melayu/Bahasa Indonesia:
-
- bindo Indonesian
- meljo Malaysian
-
- Portuguese:
-
- brazo Brazilian
-
- Urdu:
-
- kisto Pakistani
-
- </programlisting>
+ <para> <indexterm type="general-imported"><primary>gismu</primary><secondary>ethnic</secondary></indexterm> Countries with a large number of speakers of any of the above languages (where the meaning of <quote>large</quote> is dependent on the specific language):</para>
+ <informaltable>
+ <tgroup cols="2">
+ <colspec colnum="1" colname="col1"/>
+ <colspec colnum="2" colname="col2"/>
+ <thead>
+ <row>
+ <entry nameend="col2">English:</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry><jbophrase>merko</jbophrase></entry>
+ <entry>American</entry>
+ </row>
+ <row>
+ <entry><jbophrase>brito</jbophrase></entry>
+ <entry>British</entry>
+ </row>
+ <row>
+ <entry><jbophrase>skoto</jbophrase></entry>
+ <entry>Scottish</entry>
+ </row>
+ <row>
+ <entry><jbophrase>sralo</jbophrase></entry>
+ <entry>Australian</entry>
+ </row>
+ <row>
+ <entry><jbophrase>kadno</jbophrase></entry>
+ <entry>Canadian</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ <tgroup cols="2">
+ <colspec colnum="1" colname="col1"/>
+ <colspec colnum="2" colname="col2"/>
+ <thead>
+ <row>
+ <entry nameend="col2">Spanish:</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry><jbophrase>gento</jbophrase></entry>
+ <entry>Argentinian</entry>
+ </row>
+ <row>
+ <entry><jbophrase>mexno</jbophrase></entry>
+ <entry>Mexican</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ <tgroup cols="2">
+ <colspec colnum="1" colname="col1"/>
+ <colspec colnum="2" colname="col2"/>
+ <thead>
+ <row>
+ <entry nameend="col2">Russian:</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry><jbophrase>softo</jbophrase></entry>
+ <entry>Soviet/USSR</entry>
+ </row>
+ <row>
+ <entry><jbophrase>vukro</jbophrase></entry>
+ <entry>Ukrainian</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ <tgroup cols="2">
+ <colspec colnum="1" colname="col1"/>
+ <colspec colnum="2" colname="col2"/>
+ <thead>
+ <row>
+ <entry nameend="col2">Arabic:</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry><jbophrase>filso</jbophrase></entry>
+ <entry>Palestinian</entry>
+ </row>
+ <row>
+ <entry><jbophrase>jerxo</jbophrase></entry>
+ <entry>Algerian</entry>
+ </row>
+ <row>
+ <entry><jbophrase>jordo</jbophrase></entry>
+ <entry>Jordanian</entry>
+ </row>
+ <row>
+ <entry><jbophrase>libjo</jbophrase></entry>
+ <entry>Libyan</entry>
+ </row>
+ <row>
+ <entry><jbophrase>lubno</jbophrase></entry>
+ <entry>Lebanese</entry>
+ </row>
+ <row>
+ <entry><jbophrase>misro</jbophrase></entry>
+ <entry>Egyptian (from <quote xml:lang="he">Mizraim</quote>)</entry>
+ </row>
+ <row>
+ <entry><jbophrase>morko</jbophrase></entry>
+ <entry>Moroccan</entry>
+ </row>
+ <row>
+ <entry><jbophrase>rakso</jbophrase></entry>
+ <entry>Iraqi</entry>
+ </row>
+ <row>
+ <entry><jbophrase>sadjo</jbophrase></entry>
+ <entry>Saudi</entry>
+ </row>
+ <row>
+ <entry><jbophrase>sirxo</jbophrase></entry>
+ <entry>Syrian</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ <tgroup cols="2">
+ <colspec colnum="1" colname="col1"/>
+ <colspec colnum="2" colname="col2"/>
+ <thead>
+ <row>
+ <entry nameend="col2">Bahasa Melayu/Bahasa Indonesia:</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry><jbophrase>bindo</jbophrase></entry>
+ <entry>Indonesian</entry>
+ </row>
+ <row>
+ <entry><jbophrase>meljo</jbophrase></entry>
+ <entry>Malaysian</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ <tgroup cols="2">
+ <colspec colnum="1" colname="col1"/>
+ <colspec colnum="2" colname="col2"/>
+ <thead>
+ <row>
+ <entry nameend="col2">Portuguese:</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry><jbophrase>brazo</jbophrase></entry>
+ <entry>Brazilian</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ <tgroup cols="2">
+ <colspec colnum="1" colname="col1"/>
+ <colspec colnum="2" colname="col2"/>
+ <thead>
+ <row>
+ <entry nameend="col2">Urdu:</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry><jbophrase>kisto</jbophrase></entry>
+ <entry>Pakistani</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
<para> <indexterm type="general-imported"><primary>gismu</primary><secondary>religious</secondary></indexterm> The continents (and oceanic regions) of the Earth:</para>
-
- <programlisting xml:space="preserve">
- bemro North American (from
- <jbophrase>berti merko</jbophrase>)
- dzipo Antarctican (from
- <jbophrase>cadzu cipni</jbophrase>)
- ketco South American (from
- <quote>Quechua</quote>)
- friko African
- polno Polynesian/Oceanic
- ropno European
- xazdo Asiatic
- </programlisting>
+
+ <variablelist>
+ <varlistentry>
+ <term><jbophrase>bemro</jbophrase></term>
+ <listitem><para>North American (from <jbophrase>berti merko</jbophrase>)</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>dzipo</jbophrase></term>
+ <listitem><para>Antarctican (from <jbophrase>cadzu cipni</jbophrase>)</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>ketco</jbophrase></term>
+ <listitem><para>South American (from <quote xml:lang="qu">Quechua</quote>)</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>friko</jbophrase></term>
+ <listitem><para>African</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>polno</jbophrase></term>
+ <listitem><para>Polynesian/Oceanic</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>ropno</jbophrase></term>
+ <listitem><para>European</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>xazdo</jbophrase></term>
+ <listitem><para>Asiatic</para></listitem>
+ </varlistentry>
+ </variablelist>
<para>A few smaller but historically important cultures:</para>
- <programlisting xml:space="preserve">
- latmo Latin/Roman
- srito Sanskrit
- xebro Hebrew/Israeli/Jewish
- xelso Greek (from
- <quote>Hellas</quote>)
- </programlisting>
+ <variablelist>
+ <varlistentry>
+ <term><jbophrase>latmo</jbophrase></term>
+ <listitem><para>Latin/Roman</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>srito</jbophrase></term>
+ <listitem><para>Sanskrit</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>xebro</jbophrase></term>
+ <listitem><para>Hebrew/Israeli/Jewish</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>xelso</jbophrase></term>
+ <listitem><para>Greek (from <quote xml:lang="el">Hellas</quote>)</para></listitem>
+ </varlistentry>
+ </variablelist>
<para> <indexterm type="general-imported"><primary>cultural words</primary><secondary>rafsi fu'ivla proposal for</secondary></indexterm> <indexterm type="general-imported"><primary>rafsi fu'ivla</primary></indexterm> Major world religions:</para>
- <programlisting xml:space="preserve">
- budjo Buddhist
- dadjo Taoist
- muslo Islamic/Moslem
- xriso Christian
- </programlisting>
+ <variablelist>
+ <varlistentry>
+ <term><jbophrase>budjo</jbophrase></term>
+ <listitem><para>Buddhist</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>dadjo</jbophrase></term>
+ <listitem><para>Taoist</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>muslo</jbophrase></term>
+ <listitem><para>Islamic/Moslem</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>xriso</jbophrase></term>
+ <listitem><para>Christian</para></listitem>
+ </varlistentry>
+ </variablelist>
<para> <indexterm type="general-imported"><primary>fu'ivla</primary><secondary>form for rafsi fu'ivla proposal</secondary></indexterm> <indexterm type="general-imported"><primary>CCVVCV fu'ivla</primary><secondary>and rafsi fu'ivla proposal</secondary></indexterm> A few terms that cover multiple groups of the above:</para>
- <programlisting xml:space="preserve">
- jegvo Jehovist (Judeo-Christian-Moslem)
- semto Semitic
- slovo Slavic
- xispo Hispanic (New World Spanish)
- </programlisting>
+ <variablelist>
+ <varlistentry>
+ <term><jbophrase>jegvo</jbophrase></term>
+ <listitem><para>Jehovist (Judeo-Christian-Moslem)</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>semto</jbophrase></term>
+ <listitem><para>Semitic</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>slovo</jbophrase></term>
+ <listitem><para>Slavic</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><jbophrase>xispo</jbophrase></term>
+ <listitem><para>Hispanic (New World Spanish)</para></listitem>
+ </varlistentry>
+ </variablelist>
</section>
<section xml:id="section-rafsi-fuhivla">
<title>rafsi fu'ivla: a proposal</title>
<para>The list of cultures represented by gismu, given in
<xref linkend="section-cultural-gismu"/>, is unavoidably controversial. Much time has been spent debating whether this or that culture
<quote>deserves a gismu</quote> or
<quote>must languish in fu'ivla space</quote>. To help defuse this argument, a last-minute proposal was made when this book was already substantially complete. I have added it here with experimental status: it is not yet a standard part of Lojban, since all its implications have not been tested in open debate, and it affects a part of the language (lujvo-making) that has long been stable, but is known to be fragile in the face of small changes. (Many attempts were made to add general mechanisms for making lujvo that contained fu'ivla, but all failed on obvious or obscure counterexamples; finally the general
<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>
@@ -2861,31 +3214,31 @@
<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>
- <jbo>tci'ile ke canre tutra</jbo>
+ <jbo valid="false">tci'ile ke canre tutra</jbo>
<gloss>Chilean type-of (sand territory)</gloss>
<en>Chilean desert</en>
</interlinear-gloss>
</example>
<para>could be represented by the lujvo</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-0rzn">
<title>
<anchor xml:id="c4e16d3"/>
</title>
<interlinear-gloss>
- <jbo>tci'ilykemcantutra</jbo>
+ <jbo valid="false">tci'ilykemcantutra</jbo>
</interlinear-gloss>
</example>
<para>which is an illegal word in standard Lojban, but a valid lujvo under this proposal. There would be no short rafsi or 5-letter rafsi assigned to any fu'ivla, so no fu'ivla could appear as the last element of a lujvo.</para>
<para>The cultural fu'ivla introduced under this proposal are called
<jbophrase>rafsi fu'ivla</jbophrase>, since they are distinguished from other Type 4 fu'ivla by the property of having rafsi. If this proposal is workable and introduces no problems into Lojban morphology, it might become standard for all Type 4 fu'ivla, including those made for plants, animals, foodstuffs, and other things.</para>
</section>
</chapter>
--
You received this message because you are subscribed to the Google Groups "BPFK" group.
To post to this group, send email to bpfk-list@googlegroups.com.
To unsubscribe from this group, send email to bpfk-list+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/bpfk-list?hl=en.