[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bpfk] dag-cll git updates for Sat Jan 29 00:21:09 EST 2011
commit 3a4feb76bf428a9628b73edb1566e5d319863de2
Merge: c48de71 3663b8a
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date: Fri Jan 28 20:33:43 2011 -0800
Merge commit '3663b8ae64c5f047e2f579ed895c9fe34aef1541' into gh-pages
commit c48de71d4a72201a54dadc88d18450bd7e47c06c
Merge: dd83d67 ab3a84b
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date: Fri Jan 28 13:58:28 2011 -0800
Merge commit 'ab3a84b5994b565d40fed0b9ccc4167fd1b793a1' into gh-pages
commit 3663b8ae64c5f047e2f579ed895c9fe34aef1541
Author: Eitan Postavsky <eitanp32@gmail.com>
Date: Tue Jan 4 18:02:00 2011 -0500
Some chapter 4 tables/simplelists and minor TODO change.
diff --git a/todocbook/4.xml b/todocbook/4.xml
index 9b8deba..bfb6bff 100644
--- a/todocbook/4.xml
+++ b/todocbook/4.xml
@@ -1,16 +1,16 @@
<chapter xml:id="chapter-morphology">
<title>The Shape Of Words To Come: Lojban Morphology</title>
<section xml:id="section-introduction">
<title>Introductory</title>
- <para> <indexterm type="general-imported"><primary>word forms</primary><secondary>in Lojban (see also morphology)</secondary></indexterm> <indexterm type="general-imported"><primary>morphology</primary><secondary>definition</secondary></indexterm> <indexterm type="general-imported"><primary>morphology</primary><secondary>simplicity of</secondary></indexterm> Morphology is the part of grammar that deals with the form of words. Lojban's morphology is fairly simple compared to that of many languages, because Lojban words don't change form depending on how they are used. English has only a small number of such changes compared to languages like Russian, but it does have changes like
+ <para><jbophrase role="letteral">,</jbophrase> <indexterm type="general-imported"><primary>word forms</primary><secondary>in Lojban (see also morphology)</secondary></indexterm> <indexterm type="general-imported"><primary>morphology</primary><secondary>definition</secondary></indexterm> <indexterm type="general-imported"><primary>morphology</primary><secondary>simplicity of</secondary></indexterm> Morphology is the part of grammar that deals with the form of words. Lojban's morphology is fairly simple compared to that of many languages, because Lojban words don't change form depending on how they are used. English has only a small number of such changes compared to languages like Russian, but it does have changes like
<quote>boys</quote> as the plural of
<quote>boy</quote>, or
<quote>walked</quote> as the past-tense form of
<quote>walk</quote>. To make plurals or past tenses in Lojban, you add separate words to the sentence that express the number of boys, or the time when the walking was going on.</para>
<para> <indexterm type="general-imported"><primary>word forms</primary><secondary>as related to grammatical uses</secondary></indexterm> <indexterm type="general-imported"><primary>derivational morphology</primary><secondary>definition</secondary></indexterm> <indexterm type="general-imported"><primary>morphology</primary><secondary>derivational</secondary></indexterm> However, Lojban does have what is called
<quote>derivational morphology</quote>: the capability of building new words from old words. In addition, the form of words tells us something about their grammatical uses, and sometimes about the means by which they entered the language. Lojban has very orderly rules for the formation of words of various types, both the words that already exist and new words yet to be created by speakers and writers.</para>
<para> <indexterm type="general-imported"><primary>morphology</primary><secondary>conventions for</secondary></indexterm> A stream of Lojban sounds can be uniquely broken up into its component words according to specific rules. These so-called
<quote>morphology rules</quote> are summarized in this chapter. (However, a detailed algorithm for breaking sounds into words has not yet been fully debugged, and so is not presented in this book.) First, here are some conventions used to talk about groups of Lojban letters, including vowels and consonants.</para>
@@ -209,33 +209,33 @@
<jbophrase>ku'a'e</jbophrase>,
<jbophrase>sau'e</jbophrase>, and
<jbophrase>bai'ai</jbophrase>. All CVV cmavo beginning with the letter
<jbophrase role="letteral">x</jbophrase> are also reserved for experimental use. In general, though, the form of a cmavo tells you little or nothing about its grammatical use.</para>
<para> <indexterm type="general-imported"><primary>experimental cmavo</primary><secondary>definition</secondary></indexterm> <indexterm type="general-imported"><primary>cmavo</primary><secondary>experimental</secondary></indexterm>
<quote>Experimental use</quote> means that the language designers will not assign any standard meaning or usage to these words, and words and usages coined by Lojban speakers will not appear in official dictionaries for the indefinite future. Experimental-use words provide an escape hatch for adding grammatical mechanisms (as opposed to semantic concepts) the need for which was not foreseen.</para>
<para> <indexterm type="general-imported"><primary>cmavo</primary><secondary>diphthongs in</secondary></indexterm> The cmavo of VV-form include not only the diphthongs and vowel pairs listed in
<xref linkend="section-introduction"/>, but also the following ten additional diphthongs:</para>
- <cmavo-list>
- <cmavo-entry>
- <cmavo>.ia .ie .ii</cmavo>
- <selmaho>.io</selmaho>
- <description>.iu</description>
- </cmavo-entry>
- <cmavo-entry>
- <cmavo>.ua .ue .ui</cmavo>
-
- <selmaho>.uo</selmaho>
- <description>.uu</description>
- </cmavo-entry>
- </cmavo-list>
+ <simplelist type="horiz" columns="5">
+ <member><jbophrase role="diphthong">.ia</jbophrase></member>
+ <member><jbophrase role="diphthong">.ie</jbophrase></member>
+ <member><jbophrase role="diphthong">.ii</jbophrase></member>
+ <member><jbophrase role="diphthong">.io</jbophrase></member>
+ <member><jbophrase role="diphthong">.iu</jbophrase></member>
+
+ <member><jbophrase role="diphthong">.ua</jbophrase></member>
+ <member><jbophrase role="diphthong">.ue</jbophrase></member>
+ <member><jbophrase role="diphthong">.ui</jbophrase></member>
+ <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>
@@ -441,21 +441,21 @@
<para>always start with a consonant and end with a single vowel;</para>
</listitem>
<listitem>
<para>always contain exactly one consonant pair, which is a permissible initial pair (CC) if it's at the beginning of the gismu, but otherwise only has to be a permissible pair (C/C);</para>
</listitem>
<listitem>
<para>are always stressed on the first syllable (since that is penultimate).</para>
</listitem>
</orderedlist>
<para> <indexterm type="general-imported"><primary>gismu</primary><secondary>length of</secondary></indexterm> The five letter length distinguishes gismu from lujvo and fu'ivla. In addition, no gismu contains
- <jbophrase>'</jbophrase>.</para>
+ <jbophrase role="letteral">'</jbophrase>.</para>
<para> <indexterm type="general-imported"><primary>gismu</primary><secondary>conflicts between</secondary></indexterm> <indexterm type="general-imported"><primary>gismu</primary><secondary>special</secondary></indexterm> With the exception of five special brivla variables,
<jbophrase>broda</jbophrase>,
<jbophrase>brode</jbophrase>,
<jbophrase>brodi</jbophrase>,
<jbophrase>brodo</jbophrase>, and
<jbophrase>brodu</jbophrase>, no two gismu differ only in the final vowel. Furthermore, the set of gismu was specifically designed to reduce the likelihood that two similar sounding gismu could be confused. For example, because
<jbophrase>gismu</jbophrase> is in the set of gismu,
<jbophrase>kismu</jbophrase>,
<jbophrase>xismu</jbophrase>,
<jbophrase>gicmu</jbophrase>,
@@ -643,59 +643,59 @@
<title>
<anchor xml:id="c4e5d7"/>
</title>
<interlinear-gloss>
<jbo>mampa'u</jbo>
</interlinear-gloss>
</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 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
<jbophrase>brivla</jbophrase>, built from the tanru
<jbophrase>bridi valsi</jbophrase>, is the same lujvo as
<jbophrase>brivalsi</jbophrase>,
<jbophrase>bridyvla</jbophrase>, and
<jbophrase>bridyvalsi</jbophrase>, each of which uses a different combination of rafsi.</para>
<para> <indexterm type="general-imported"><primary>apostrophe</primary><secondary>and consonant cluster determination in lujvo</secondary></indexterm> <indexterm type="general-imported"><primary>' symbol</primary><secondary>and consonant cluster determination in lujvo</secondary></indexterm> <indexterm type="general-imported"><primary>y-hyphen</primary><secondary>and consonant cluster determination</secondary></indexterm> <indexterm type="general-imported"><primary>rafsi</primary><secondary>rules for combining to form lujvo</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>rules for formation of</secondary></indexterm> When assembling rafsi together into lujvo, the rules for valid brivla must be followed: a consonant cluster must occur in the first five letters (excluding
<jbophrase role="letteral">y</jbophrase> and
- <jbophrase>'</jbophrase>), and the lujvo must end in a vowel.</para>
+ <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">
<title>
<indexterm type="example-imported"><primary>field rations</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c4e5d8"/>
</title>
<interlinear-gloss>
<jbo>soirsai</jbo>
- <gloss>sonci sanmi</gloss>
+ <jbo>sonci sanmi</jbo>
<gloss>soldier meal</gloss>
<en>field rations</en>
</interlinear-gloss>
</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="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>
<para>Learning rafsi and the rules for assembling them into lujvo is clearly seen to be necessary for fully using the potential Lojban vocabulary.</para>
<para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>invention of</secondary></indexterm> Most important, it is possible to invent new lujvo while you speak or write in order to represent a new or unfamiliar concept, one for which you do not know any existing Lojban word. As long as you follow the rules for building these compounds, there is a good chance that you will be understood without explanation.</para>
</section>
<section xml:id="section-rafsi">
@@ -835,21 +835,21 @@
<description>-kli-</description>
</cmavo-entry>
<cmavo-entry>
<cmavo>CCV</cmavo>
<selmaho>132</selmaho>
<description>-ska-</description>
</cmavo-entry>
</cmavo-list>
<para>(The only actual short rafsi for
<jbophrase>sakli</jbophrase> is
- <jbophrase role="rafsi">-sal-</jbophrase>.)</para>
+ -<jbophrase role="rafsi">sal</jbophrase>-.)</para>
<para>For gismu of the form CCVCV, like
<jbophrase>blaci</jbophrase>, the only short rafsi forms that can exist are:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>CVC</cmavo>
<selmaho>134</selmaho>
<description>-bac-</description>
</cmavo-entry>
<cmavo-entry>
<cmavo>CVC</cmavo>
@@ -1237,21 +1237,21 @@
<interlinear-gloss> <!-- FIXME: should the commentary sit inside the jbo/gloss/en or outside in para? -->
<jbo>spaghetti (from English or Italian)</jbo>
<gloss>spageti (Lojbanize)</gloss>
<gloss>cidj,r,spageti (prefix long rafsi)</gloss>
<en>dja,r,spageti (prefix short rafsi)</en>
</interlinear-gloss>
</example>
<para> where
- <jbophrase role="rafsi">cidj-</jbophrase> is the 4-letter rafsi for
+ <jbophrase role="rafsi">cidj</jbophrase>- is the 4-letter rafsi for
<jbophrase>cidja</jbophrase>, the Lojban gismu for
<quote>food</quote>, thus categorizing
<jbophrase>cidjrspageti</jbophrase> as a kind of food. The form with the short rafsi happens to work, but such good fortune cannot be relied on: in any event, it means the same thing.</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-pzXe">
<title>
<indexterm type="example-imported"><primary>maple trees</primary><secondary>example</secondary></indexterm>
<indexterm type="example-imported"><primary>Acer</primary><secondary>example</secondary></indexterm>
<indexterm type="example-imported"><primary>maple sugar</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c4e7d4"/>
</title>
@@ -1259,22 +1259,22 @@
<jbo>Acer (the scientific name of maple trees)</jbo>
<gloss>acer (Lojbanize)</gloss>
<gloss>xaceru (add initial consonant and final vowel)</gloss>
<gloss>tric,r,xaceru (prefix rafsi)</gloss>
<en>ric,r,xaceru (prefix short rafsi)</en>
</interlinear-gloss>
</example>
<para>where
- <jbophrase role="rafsi">tric-</jbophrase> and
- <jbophrase role="rafsi">ric-</jbophrase> are rafsi for
+ <jbophrase role="rafsi">tric</jbophrase>- and
+ <jbophrase role="rafsi">ric</jbophrase>- are rafsi for
<jbophrase>tricu</jbophrase>, the gismu for
<quote>tree</quote>. Note that by the same principles,
<quote>maple sugar</quote> could get the fu'ivla
<jbophrase>saktrxaceru</jbophrase>, or could be represented by the tanru
<jbophrase>tricrxaceru sakta</jbophrase>. Technically,
<jbophrase>ricrxaceru</jbophrase> and
<jbophrase>tricrxaceru</jbophrase> are distinct fu'ivla, but they would surely be given the same meanings if both happened to be in use.</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-C0YS">
<title>
@@ -1282,73 +1282,73 @@
<anchor xml:id="c4e7d5"/>
</title>
<interlinear-gloss>
<jbo>brie (from French)</jbo>
<gloss>bri (Lojbanize)</gloss>
<en>cirl,r,bri (prefix rafsi)</en>
</interlinear-gloss>
</example>
<para> where
- <jbophrase role="rafsi">cirl-</jbophrase> represents
+ <jbophrase role="rafsi">cirl</jbophrase>- represents
<jbophrase>cirla</jbophrase> (
<quote>cheese</quote>).</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-DQju">
<title>
<indexterm type="example-imported"><primary>cobra</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c4e7d6"/>
</title>
<interlinear-gloss>
<jbo>cobra</jbo>
<gloss>kobra (Lojbanize)</gloss>
<en>sinc,r,kobra (prefix rafsi)</en>
</interlinear-gloss>
</example>
<para> where
- <jbophrase role="rafsi">sinc-</jbophrase> represents
+ <jbophrase role="rafsi">sinc</jbophrase>- represents
<jbophrase>since</jbophrase> (
<quote>snake</quote>).</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-TFzH">
<title>
<indexterm type="example-imported"><primary>quark</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c4e7d7"/>
</title>
<interlinear-gloss>
<jbo>quark</jbo>
<gloss>kuark (Lojbanize)</gloss>
<gloss>kuarka (add final vowel)</gloss>
<en>sask,r,kuarka (prefix rafsi)</en>
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>allowable diphthongs</primary><secondary>in gismu and lujvo contrasted with in fu'ivla</secondary></indexterm> <indexterm type="general-imported"><primary>allowable diphthongs</primary><secondary>in fu'ivla contrasted with in gismu and lujvo</secondary></indexterm> <indexterm type="general-imported"><primary>diphthongs</primary><secondary>in fu'ivla</secondary></indexterm> <indexterm type="general-imported"><primary>fu'ivla</primary><secondary>diphthongs in</secondary></indexterm> where
- <jbophrase role="rafsi">sask-</jbophrase> represents
+ <jbophrase role="rafsi">sask</jbophrase>- represents
<jbophrase>saske</jbophrase> (
<quote>science</quote>). Note the extra vowel
<jbophrase role="letteral">a</jbophrase> added to the end of the word, and the diphthong
<jbophrase role="diphthong">ua</jbophrase>, which never appears in gismu or lujvo, but may appear in fu'ivla.</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-FTfQ">
<title>
<anchor xml:id="c4e7d8"/>
</title>
<interlinear-gloss>
<!-- FIXME: non-lojban-non-english component of example; how do we mark this? <nonen>? <foreign>? -->
<jbo>자모 (from Korean)</jbo>
<gloss>djamo (Lojbanize)</gloss>
<gloss>lerf,r,djamo (prefix rafsi)</gloss>
<en>ler,l,djamo (prefix rafsi)</en>
</interlinear-gloss>
</example>
<para>where
- <jbophrase role="rafsi">ler-</jbophrase> represents
+ <jbophrase role="rafsi">ler</jbophrase>- represents
<jbophrase>lerfu</jbophrase> (
<quote>letter</quote>). Note the l-hyphen in "lerldjamo", since "lerndjamo" contains the forbidden cluster "ndj".</para>
<para> <indexterm type="general-imported"><primary>fu'ivla categorizer</primary><secondary>for distinguishing fu'ivla form</secondary></indexterm> <indexterm type="general-imported"><primary>fu'ivla</primary><secondary>disambiguation of</secondary></indexterm> The use of the prefix helps distinguish among the many possible meanings of the borrowed word, depending on the field. As it happens,
<jbophrase>spageti</jbophrase> and
<jbophrase>kuarka</jbophrase> are valid Stage 4 fu'ivla, but
<jbophrase valid="false">xaceru</jbophrase> looks like a compound cmavo, and
<jbophrase valid="false">kobra</jbophrase> like a gismu.</para>
<para> <indexterm type="general-imported"><primary>fu'ivla categorizer</primary><secondary>for distinguishing specialized meanings</secondary></indexterm> For another example,
<quote>integral</quote> has a specific meaning to a mathematician. But the Lojban fu'ivla
@@ -1358,21 +1358,21 @@
<para>Left uncontrolled,
<jbophrase>integrale</jbophrase> almost certainly would eventually come to mean the same collection of loosely related concepts that English associates with
<quote>integral</quote>, with only the context to indicate (possibly) that the mathematical term is meant.</para>
<para> <!-- FIXME: there's nowhere for these two indexterms to go --><indexterm type="example-imported"><primary>integral</primary><secondary>architectural concept</secondary><tertiary>example</tertiary></indexterm> <indexterm type="example-imported"><primary>integral</primary><secondary>mathematical concept</secondary><tertiary>example</tertiary></indexterm> The prefix method would render the mathematical concept as
<jbophrase>cmacrntegrale</jbophrase>, if the
<jbophrase role="letteral">i</jbophrase> of
<jbophrase>integrale</jbophrase> is removed, or something like
<jbophrase>cmacrnintegrale</jbophrase>, if a new consonant is added to the beginning;
- <jbophrase role="rafsi">cmac-</jbophrase> is the rafsi for
+ <jbophrase role="rafsi">cmac</jbophrase>- is the rafsi for
<jbophrase>cmaci</jbophrase> (
<quote>mathematics</quote>). The architectural sense of
<quote>integral</quote> might be conveyed with
<jbophrase>djinrnintegrale</jbophrase> or
<jbophrase>tarmrnintegrale</jbophrase>, where
<jbophrase>dinju</jbophrase> and
<jbophrase>tarmi</jbophrase> mean
<quote>building</quote> and
<quote>form</quote> respectively.</para>
@@ -1742,115 +1742,204 @@
<jbophrase role="morphology">pn</jbophrase> to
<jbophrase role="letteral">n</jbophrase> initially.</para>
</listitem>
<listitem>
<para>Change final
<jbophrase role="diphthong">ie</jbophrase> and
<jbophrase role="diphthong">ii</jbophrase> to
<jbophrase role="letteral">i</jbophrase>.</para>
</listitem>
<listitem>
- <para>Make the following idiosyncratic substitutions:
- <programlisting xml:space="preserve">
- aa a
- ae e
- ch k
- ee i
- eigh ei
- ew u
- igh ai
- oo u
- ou u
- ow au
- ph f
- q k
- sc sk
- w u
- y i
- </programlisting> However, the diphthong substitutions should not be done if the two vowels are in two different syllables.</para>
+ <para>Make the following idiosyncratic substitutions:</para>
+ <informaltable>
+ <tgroup cols="2">
+ <colspec colnum="1" colname="col1"/>
+ <colspec colnum="2" colname="col2"/>
+ <tbody>
+ <row>
+ <entry>aa</entry><entry>a</entry>
+ </row>
+ <row>
+ <entry>ae</entry><entry>e</entry>
+ </row>
+ <row>
+ <entry>ch</entry><entry>k</entry>
+ </row>
+ <row>
+ <entry>ee</entry><entry>i</entry>
+ </row>
+ <row>
+ <entry>eigh</entry><entry>ei</entry>
+ </row>
+ <row>
+ <entry>ew</entry><entry>u</entry>
+ </row>
+ <row>
+ <entry>igh</entry><entry>ai</entry>
+ </row>
+ <row>
+ <entry>oo</entry><entry>u</entry>
+ </row>
+ <row>
+ <entry>ou</entry><entry>u</entry>
+ </row>
+ <row>
+ <entry>ow</entry><entry>au</entry>
+ </row>
+ <row>
+ <entry>ph</entry><entry>f</entry>
+ </row>
+ <row>
+ <entry>q</entry><entry>k</entry>
+ </row>
+ <row>
+ <entry>sc</entry><entry>sk</entry>
+ </row>
+ <row>
+ <entry>w</entry><entry>u</entry>
+ </row>
+ <row>
+ <entry>y</entry><entry>i</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ <para>However, the diphthong substitutions should not be done if the two vowels are in two different syllables.</para>
</listitem>
<listitem>
<para>Change
<quote>h</quote> between two vowels to
- <jbophrase>'</jbophrase>, but otherwise remove it completely. If preservation of the
+ <jbophrase role="letteral">'</jbophrase>, but otherwise remove it completely. If preservation of the
<quote>h</quote> seems essential, change it to
<jbophrase role="letteral">x</jbophrase> instead.</para>
</listitem>
<listitem>
- <para>Place
- <jbophrase>'</jbophrase> between any remaining vowel pairs that do not form Lojban diphthongs.</para>
-
+ <para>Place <jbophrase role="letteral">'</jbophrase> between any remaining vowel pairs that do not form Lojban diphthongs.</para>
</listitem>
</orderedlist>
<para>Some further examples of Lojbanized names are:</para>
- <programlisting xml:space="preserve">
- English
- <quote>Mary</quote> meris.
- or meiris.
- English
- <quote>Smith</quote> smit.
- English
- <quote>Jones</quote> djonz.
- English
- <quote>John</quote> djan. or jan. (American)
- or djon. or jon. (British)
- English
- <quote>Alice</quote> .alis.
- English
- <quote>Elise</quote> .eLIS.
- English
- <quote>Johnson</quote> djansn.
-
- English
- <quote>William</quote> .uiliam.
-
- or .uil,iam.
- English
- <quote>Brown</quote> braun.
-
- English
- <quote>Charles</quote> tcarlz.
- French
- <quote>Charles</quote> carl.
- French
- <quote>De Gaulle</quote> dyGOL.
-
- German
- <quote>Heinrich</quote> xainrix.
- Spanish
- <quote>Joaquin</quote> xuaKIN.
- Russian
- <quote>Svetlana</quote> sfietlanys.
-
- Russian
- <quote>Khrushchev</quote> xrucTCOF.
-
- Hindi
- <quote>Krishna</quote> kricnas.
-
- Polish
- <quote>Lech Walesa</quote> lex. va,uensas.
-
- Spanish
- <quote>Don Quixote</quote> don. kicotes.
-
- or modern Spanish: don. kixotes.
- or Mexican dialect: don. ki'otes.
- Chinese
- <quote>Mao Zedong</quote> maudzydyn.
-
- Japanese
- <quote>Fujiko</quote> fudjikos.
-
- or fujikos.
- </programlisting>
+ <informaltable>
+ <tgroup cols="3">
+ <colspec colnum="1" colname="col1"/>
+ <colspec colnum="2" colname="col2"/>
+ <colspec colnum="3" colname="col3"/>
+ <tbody>
+ <row>
+ <entry>English</entry>
+ <entry><quote>Mary</quote></entry>
+ <entry><jbophrase>meris.</jbophrase> or <jbophrase>meiris.</jbophrase></entry>
+ </row>
+ <row>
+ <entry>English</entry>
+ <entry><quote>Smith</quote></entry>
+ <entry><jbophrase>smit.</jbophrase></entry>
+ </row>
+ <row>
+ <entry>English</entry>
+ <entry><quote>Jones</quote></entry>
+ <entry><jbophrase>djonz.</jbophrase></entry>
+ </row>
+ <row>
+ <entry>English</entry>
+ <entry><quote>John</quote></entry>
+ <entry><jbophrase>djan.</jbophrase> or <jbophrase>jan.</jbophrase> (American) or <jbophrase>djon.</jbophrase> or <jbophrase>jon.</jbophrase> (British)</entry>
+ </row>
+ <row>
+ <entry>English</entry>
+ <entry><quote>Alice</quote></entry>
+ <entry><jbophrase>.alis.</jbophrase></entry>
+ </row>
+ <row>
+ <entry>English</entry>
+ <entry><quote>Elise</quote></entry>
+ <entry><jbophrase>.eLIS.</jbophrase></entry>
+ </row>
+ <row>
+ <entry>English</entry>
+ <entry><quote>Johnson</quote></entry>
+ <entry><jbophrase>djansn.</jbophrase></entry>
+ </row>
+ <row>
+ <entry>English</entry>
+ <entry><quote>William</quote></entry>
+ <entry><jbophrase>.uiliam.</jbophrase> or <jbophrase>.uil,iam.</jbophrase></entry>
+ </row>
+ <row>
+ <entry>English</entry>
+ <entry><quote>Brown</quote></entry>
+ <entry><jbophrase>braun.</jbophrase></entry>
+ </row>
+ <row>
+ <entry>English</entry>
+ <entry><quote>Charles</quote></entry>
+ <entry><jbophrase>tcarlz.</jbophrase></entry>
+ </row>
+ <row>
+ <entry>French</entry>
+ <entry><quote>Charles</quote></entry>
+ <entry><jbophrase>carl.</jbophrase></entry>
+ </row>
+ <row>
+ <entry>French</entry>
+ <entry><quote>De Gaulle</quote></entry>
+ <entry><jbophrase>dyGOL.</jbophrase></entry>
+ </row>
+ <row>
+ <entry>German</entry>
+ <entry><quote>Heinrich</quote></entry>
+ <entry><jbophrase>xainrix.</jbophrase></entry>
+ </row>
+ <row>
+ <entry>Spanish</entry>
+ <entry><quote>Joaquin</quote></entry>
+ <entry><jbophrase>xuaKIN.</jbophrase></entry>
+ </row>
+ <row>
+ <entry>Russian</entry>
+ <entry><quote>Svetlana</quote></entry>
+ <entry><jbophrase>sfietlanys.</jbophrase></entry>
+ </row>
+ <row>
+ <entry>Russian</entry>
+ <entry><quote>Khrushchev</quote></entry>
+ <entry><jbophrase>xrucTCOF.</jbophrase></entry>
+ </row>
+ <row>
+ <entry>Hindi</entry>
+ <entry><quote>Krishna</quote></entry>
+ <entry><jbophrase>kricnas.</jbophrase></entry>
+ </row>
+ <row>
+ <entry>Polish</entry>
+ <entry><quote>Lech Walesa</quote></entry>
+ <entry><jbophrase>lex. va,uensas.</jbophrase></entry>
+ </row>
+ <row>
+ <entry>Spanish</entry>
+ <entry><quote>Don Quixote</quote></entry>
+ <entry><jbophrase>don. kicotes.</jbophrase> or modern Spanish: <jbophrase>don. kixotes.</jbophrase> or Mexican dialect: <jbophrase>don. ki'otes.</jbophrase></entry>
+ </row>
+ <row>
+ <entry>Chinese</entry>
+ <entry><quote>Mao Zedong</quote></entry>
+ <entry><jbophrase>maudzydyn.</jbophrase></entry>
+ </row>
+ <row>
+ <entry>Japanese</entry>
+ <entry><quote>Fujiko</quote></entry>
+ <entry><jbophrase>fudjikos.</jbophrase> or <jbophrase>fujikos.</jbophrase></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
</section>
+
<section xml:id="section-pauses">
<title>Rules for inserting pauses</title>
<para> <indexterm type="general-imported"><primary>pauses</primary><secondary>rules for</secondary></indexterm> Summarized in one place, here are the rules for inserting pauses between Lojban words:</para>
<orderedlist>
<listitem>
<para> <indexterm type="general-imported"><primary>pause</primary><secondary>between words</secondary></indexterm> <indexterm type="general-imported"><primary>pause</primary><secondary>proscribed within words</secondary></indexterm> Any two words may have a pause between them; it is always illegal to pause in the middle of a word, because that breaks up the word into two words.</para>
</listitem>
<listitem>
<para> <indexterm type="general-imported"><primary>pause</primary><secondary>and consonant-final words</secondary></indexterm> <indexterm type="general-imported"><primary>consonant-final words</primary><secondary>necessity for pause after</secondary></indexterm> Every word ending in a consonant must be followed by a pause. Necessarily, all such words are cmene.</para>
</listitem>
@@ -2041,80 +2130,84 @@
<jbophrase role="letteral">n</jbophrase>-hyphens; call it
<quote>H</quote>.</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>:
- <cmavo-list>
- <cmavo-entry>
- <cmavo>CVC/CV (final)</cmavo>
- <selmaho>(-sarji)</selmaho>
- <description>1</description>
- </cmavo-entry>
- <cmavo-entry>
- <cmavo>CVC/C</cmavo>
- <selmaho>(-sarj-)</selmaho>
- <description>2</description>
- </cmavo-entry>
- <cmavo-entry>
- <cmavo>CCVCV (final)</cmavo>
- <selmaho>(-zbasu)</selmaho>
- <description>3</description>
- </cmavo-entry>
- <cmavo-entry>
- <cmavo>CCVC</cmavo>
- <selmaho>(-zbas-)</selmaho>
- <description>4</description>
- </cmavo-entry>
- <cmavo-entry>
- <cmavo>CVC</cmavo>
- <selmaho>(-nun-)</selmaho>
- <description>5</description>
- </cmavo-entry>
- <cmavo-entry>
- <cmavo>CVV with an apostrophe</cmavo>
- <selmaho>(-ta'u-)</selmaho>
-
- <description>6</description>
- </cmavo-entry>
- <cmavo-entry>
- <cmavo>CCV</cmavo>
- <selmaho>(-zba-)</selmaho>
- <description>7</description>
- </cmavo-entry>
- <cmavo-entry>
- <cmavo>CVV with no apostrophe</cmavo>
- <selmaho>(-sai-)</selmaho>
-
- <description>8</description>
- </cmavo-entry>
- </cmavo-list></para>
+ <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>
+ </row>
+ <row>
+ <entry>CVC/C</entry>
+ <entry>(-<jbophrase role="rafsi">sarj</jbophrase>-)</entry>
+ <entry>2</entry>
+ </row>
+ <row>
+ <entry>CCVCV (final)</entry>
+ <entry>(-<jbophrase role="rafsi">zbasu</jbophrase>-)</entry>
+ <entry>3</entry>
+ </row>
+ <row>
+ <entry>CCVC</entry>
+ <entry>(-<jbophrase role="rafsi">zbas</jbophrase>-)</entry>
+ <entry>4</entry>
+ </row>
+ <row>
+ <entry>CVC</entry>
+ <entry>(-<jbophrase role="rafsi">nun</jbophrase>-)</entry>
+ <entry>5</entry>
+ </row>
+ <row>
+ <entry>CVV with an apostrophe</entry>
+ <entry>(-<jbophrase role="rafsi">ta'u</jbophrase>-)</entry>
+ <entry>6</entry>
+ </row>
+ <row>
+ <entry>CCV</entry>
+ <entry>(-<jbophrase role="rafsi">zba</jbophrase>-)</entry>
+ <entry>7</entry>
+ </row>
+ <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>
</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:</para>
- <programlisting xml:space="preserve">
- (1000 * L) - (500 * A) + (100 * H) - (10 * R) - V
- </programlisting>
- <para> <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> <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>
+ <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>
@@ -2153,182 +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>
- <programlisting xml:space="preserve">
- -ger-, -ge'u-, -gerk-, -gerku
- </programlisting>
- <para>The rafsi for
- <jbophrase>zdani</jbophrase> are:</para>
- <programlisting xml:space="preserve">
- -zda-, -zdan-, -zdani.
- </programlisting>
- <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>
- <programlisting xml:space="preserve">
- ger-zda
- ger-zdani
- ge'u-zda
- ge'u-zdani
- gerk-zda
- gerk-zdani
- </programlisting>
- <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" valid="false">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 L score is 6, its A score is 0, its H score is 0, its R score is 12, and its V 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>
- <programlisting xml:space="preserve">
- lotkle blokle lo'ikle
- <!-- not a cmavo list -->
- lotlei blolei lo'irlei
- </programlisting>
- <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>
-
- <programlisting xml:space="preserve">
- lotkle 5878 blokle 5858 lo'ikle 6367
- <!-- not a cmavo list -->
- lotlei 5867 blolei 5847 lo'irlei 7456
- </programlisting>
- <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>
- <programlisting xml:space="preserve">
- loj-ban-gri loj-bau-gri loj-bang-gri
- <!-- not a cmavo list -->
- logj-ban-gri logj-bau-gri logj-bang-gri
- loj-ban-girzu loj-bau-girzu loj-bang-girzu
- logj-ban-girzu logj-bau-girzu logj-bang-girzu
- </programlisting>
- <para>and the 12 name possibilities are:</para>
- <programlisting xml:space="preserve">
- loj-ban-gir. loj-bau-gir. loj-bang-gir.
- <!-- not a cmavo list -->
- logj-ban-gir. logj-bau-gir. logj-bang-gir.
- loj-ban-girz. loj-bau-girz. loj-bang-girz.
- logj-ban-girz. logj-bau-girz. logj-bang-girz.
- </programlisting>
- <para>After hyphenation, we have:</para>
- <programlisting xml:space="preserve">
- lojbangri lojbaugri lojbangygri
- <!-- not a cmavo list -->
- logjybangri logjybaugri logjybangygri
- lojbangirzu lojbaugirzu lojbangygirzu
- logjybangirzu logjybaugirzu logjybangygirzu
-
- lojbangir. lojbaugir. lojbangygir.
- logjybangir. logjybaugir. logjybangygir.
- lojbangirz. lojbaugirz. lojbangygirz.
- logjybangirz. logjybaugirz. logjybangygirz.
- </programlisting>
- <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>
- <programlisting xml:space="preserve">
- nak-kem-cin-ctu nakykemcinctu
- nak-kem-cin-ctuca nakykemcinctuca
- nak-kem-cins-ctu nakykemcinsyctu
- nak-kem-cins-ctuca nakykemcinsyctuca
- nakn-kem-cin-ctu naknykemcinctu
- nakn-kem-cin-ctuca naknykemcinctuca
- nakn-kem-cins-ctu naknykemcinsyctu
- nakn-kem-cins-ctuca naknykemcinsyctuca
- </programlisting>
- <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 (
@@ -2369,40 +2535,102 @@
<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>
- <programlisting>
- proposed gismu existing gismu
- b p, v
- c j, s
- d t
- f p, v
- g k, x
- j c, z
- k g, x
- l r
- m n
- n m
- p b, f
- r l
- s c, z
- t d
- v b, f
- x g, k
- z j, s
- </programlisting>
+ <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>
@@ -2431,21 +2659,21 @@
<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>brod-</jbophrase>, they all end in the letter
+ <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>)
diff --git a/todocbook/TODO b/todocbook/TODO
index 9dd7079..9325489 100644
--- a/todocbook/TODO
+++ b/todocbook/TODO
@@ -114,20 +114,21 @@ role="diphthong", and role="rafsi".
change it, or think it's actually correct in some particular place,
post to the BPFK list.
------
If an example/interlinear-gloss consists solely of English, replace
the <interlinear-gloss>...</interlinear-gloss> with <para>...</para>
------
+
Make sure all the components of <example>s are appropriate wrapped in
<jbo>, <gloss>, <en>, or <ipa> (if it doesn't fit one of those, make
up a tag and report it). Many of the non-three-part examples are
messed up like this.
------
Entries like <indexterm type="lojban-word-imported"> (NOTE the type)
probably need to be destroyed; there should be a bit of Lojban near
them that can be wrapped in <jbophrase>, to exactly the same effect
@@ -173,21 +174,21 @@ All such indexterm entries should end up in the example itself, like so:
- It seems that there is a problem with the cmavo lists at the
beginning of sections having missing entries; in particular, ones
wwith + in the selma'o, maybe?; they need to be manually checked
- lojban words, lojban phrases, terms of art ("abstraction"),
others?... should each have their own index
- cll_chapter5-section1 should be content-words-brivla or so ; those
IDs should not change when things are moved around
- list the members of each selma'o in chapter 20
- make sure the examples that aren't interlinear glosses don't have
that as their role
- - so far there's also role="pronunciation-example", probably need more
+ - so far there's also pronunciation-example, compound-cmavo-example
- <phrase role="IPA">∞</phrase> is *not* IPA
- <@xalbo> I do think having distinct structures for quoted correct
lojban and for intentionally incorrect lojban (if there's any, but
I would expect there is) would probably be a good thing. <@xalbo>
(found one: search for djeimz) <@xalbo> I see three cases, though
I don't know if they're all represented in the text: valid, good
lojban, invalid lojban, and something in between ({lo nanmu
bajra}, for instance; maybe worth flagging with a "this isn't what
you think it is" type of thing
- use <jbophrase valid="false">...</jbophrase> for purposely na
commit ab3a84b5994b565d40fed0b9ccc4167fd1b793a1
Author: Eitan Postavsky <eitanp32@gmail.com>
Date: Mon Jan 3 12:18:50 2011 -0500
Replaced comma-lists in chapter 3 with <simplelist>s.
diff --git a/todocbook/3.xml b/todocbook/3.xml
index bf4093f..f8662df 100644
--- a/todocbook/3.xml
+++ b/todocbook/3.xml
@@ -1,22 +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>
<member>e</member>
@@ -98,131 +91,227 @@
<entry>the syllable separator</entry>
</row>
<row>
<entry><jbophrase role="letteral">.</jbophrase></entry>
<entry><phrase role="IPA">[ʔ]</phrase></entry>
<entry><phrase role="X-SAMPA">[?]</phrase></entry>
<entry>a glottal stop or a pause</entry>
</row>
<row>
<entry><jbophrase role="letteral">a</jbophrase></entry>
- <entry><phrase role="IPA">[a]</phrase>, <phrase role="IPA">[ɑ]</phrase>
+ <entry>
+ <simplelist type="inline">
+ <member><phrase role="IPA">[a]</phrase></member>
+ <member><phrase role="IPA">[ɑ]</phrase></member>
+ </simplelist>
</entry>
- <entry><phrase role="X-SAMPA">[a]</phrase>, <phrase role="X-SAMPA">[A]</phrase>
+ <entry>
+ <simplelist type="inline">
+ <member><phrase role="X-SAMPA">[a]</phrase></member>
+ <member><phrase role="X-SAMPA">[A]</phrase></member>
+ </simplelist>
</entry>
<entry>an open vowel</entry>
</row>
<row>
<entry><jbophrase role="letteral">b</jbophrase></entry>
<entry><phrase role="IPA">[b]</phrase></entry>
<entry><phrase role="X-SAMPA">[b]</phrase></entry>
<entry>a voiced bilabial stop</entry>
</row>
<row>
<entry><jbophrase role="letteral">c</jbophrase></entry>
- <entry><phrase role="IPA">[ʃ]</phrase>, <phrase role="IPA">[ʂ]</phrase>
+ <entry>
+ <simplelist type="inline">
+ <member><phrase role="IPA">[ʃ]</phrase></member>
+ <member><phrase role="IPA">[ʂ]</phrase></member>
+ </simplelist>
</entry>
- <entry><phrase role="X-SAMPA">[S]</phrase>, <phrase role="X-SAMPA">[s`]</phrase>
+ <entry>
+ <simplelist type="inline">
+ <member><phrase role="X-SAMPA">[S]</phrase></member>
+ <member><phrase role="X-SAMPA">[s`]</phrase></member>
+ </simplelist>
</entry>
<entry>an unvoiced coronal sibilant</entry>
</row>
<row>
<entry><jbophrase role="letteral">d</jbophrase></entry>
<entry><phrase role="IPA">[d]</phrase></entry>
<entry><phrase role="X-SAMPA">[d]</phrase></entry>
<entry>a voiced dental/alveolar stop</entry>
</row>
<row>
<entry><jbophrase role="letteral">e</jbophrase></entry>
- <entry><phrase role="IPA">[ɛ]</phrase>, <phrase role="IPA">[e]</phrase>
+ <entry>
+ <simplelist type="inline">
+ <member><phrase role="IPA">[ɛ]</phrase></member>
+ <member><phrase role="IPA">[e]</phrase></member>
+ </simplelist>
</entry>
- <entry><phrase role="X-SAMPA">[E]</phrase>, <phrase role="X-SAMPA">[e]</phrase>
+ <entry>
+ <simplelist type="inline">
+ <member><phrase role="X-SAMPA">[E]</phrase></member>
+ <member><phrase role="X-SAMPA">[e]</phrase></member>
+ </simplelist>
</entry>
<entry>a front mid vowel</entry>
</row>
<row>
<entry><jbophrase role="letteral">f</jbophrase></entry>
- <entry><phrase role="IPA">[f]</phrase>, <phrase role="IPA">[ɸ]</phrase>
+ <entry>
+ <simplelist type="inline">
+ <member><phrase role="IPA">[f]</phrase></member>
+ <member><phrase role="IPA">[ɸ]</phrase></member>
+ </simplelist>
</entry>
- <entry><phrase role="X-SAMPA">[f]</phrase>, <phrase role="X-SAMPA">[p\]</phrase>
+ <entry>
+ <simplelist type="inline">
+ <member><phrase role="X-SAMPA">[f]</phrase></member>
+ <member><phrase role="X-SAMPA">[p\]</phrase></member>
+ </simplelist>
</entry>
<entry>an unvoiced labial fricative</entry>
</row>
<row>
<entry><jbophrase role="letteral">g</jbophrase></entry>
<entry><phrase role="IPA">[ɡ]</phrase></entry>
<entry><phrase role="X-SAMPA">[g]</phrase></entry>
<entry>a voiced velar stop</entry>
</row>
<row>
<entry><jbophrase role="letteral">i</jbophrase></entry>
<entry><phrase role="IPA">[i]</phrase></entry>
<entry><phrase role="X-SAMPA">[i]</phrase></entry>
<entry>a front close vowel</entry>
</row>
<row>
<entry><jbophrase role="letteral">j</jbophrase></entry>
- <entry><phrase role="IPA">[ʒ]</phrase>, <phrase role="IPA">[ʐ]</phrase>
+ <entry>
+ <simplelist type="inline">
+ <member><phrase role="IPA">[ʒ]</phrase></member>
+ <member><phrase role="IPA">[ʐ]</phrase></member>
+ </simplelist>
</entry>
- <entry><phrase role="X-SAMPA">[Z]</phrase>, <phrase role="X-SAMPA">[z`]</phrase>
+ <entry>
+ <simplelist type="inline">
+ <member><phrase role="X-SAMPA">[Z]</phrase></member>
+ <member><phrase role="X-SAMPA">[z`]</phrase></member>
+ </simplelist>
</entry>
<entry>a voiced coronal sibilant</entry>
</row>
<row>
<entry><jbophrase role="letteral">k</jbophrase></entry>
<entry><phrase role="IPA">[k]</phrase></entry>
<entry><phrase role="X-SAMPA">[k]</phrase></entry>
<entry>an unvoiced velar stop</entry>
</row>
<row>
<entry><jbophrase role="letteral">l</jbophrase></entry>
- <entry><phrase role="IPA">[l]</phrase>, <phrase role="IPA">[l̩]</phrase>
+ <entry>
+ <simplelist type="inline">
+ <member><phrase role="IPA">[l]</phrase></member>
+ <member><phrase role="IPA">[l̩]</phrase></member>
+ </simplelist>
</entry>
- <entry><phrase role="X-SAMPA">[l]</phrase>, <phrase role="X-SAMPA">[l=]</phrase>
+ <entry>
+ <simplelist type="inline">
+ <member><phrase role="X-SAMPA">[l]</phrase></member>
+ <member><phrase role="X-SAMPA">[l=]</phrase></member>
+ </simplelist>
</entry>
<entry>a voiced lateral approximant (may be syllabic)</entry>
</row>
<row>
<entry><jbophrase role="letteral">m</jbophrase></entry>
- <entry><phrase role="IPA">[m]</phrase>, <phrase role="IPA">[m̩]</phrase>
+ <entry>
+ <simplelist type="inline">
+ <member><phrase role="IPA">[m]</phrase></member>
+ <member><phrase role="IPA">[m̩]</phrase></member>
+ </simplelist>
</entry>
- <entry><phrase role="X-SAMPA">[m]</phrase>, <phrase role="X-SAMPA">[m=]</phrase>
+ <entry>
+ <simplelist type="inline">
+ <member><phrase role="X-SAMPA">[m]</phrase></member>
+ <member><phrase role="X-SAMPA">[m=]</phrase></member>
+ </simplelist>
</entry>
<entry>a voiced bilabial nasal (may be syllabic)</entry>
</row>
<row>
<entry><jbophrase role="letteral">n</jbophrase></entry>
- <entry><phrase role="IPA">[n]</phrase>, <phrase role="IPA">[n̩]</phrase>, <phrase role="IPA">[ŋ̍]</phrase>, <phrase role="IPA">[ŋ̩]</phrase>
+ <entry>
+ <simplelist type="inline">
+ <member><phrase role="IPA">[n]</phrase></member>
+ <member><phrase role="IPA">[n̩]</phrase></member>
+ <member><phrase role="IPA">[ŋ̍]</phrase></member>
+ <member><phrase role="IPA">[ŋ̩]</phrase></member>
+ </simplelist>
</entry>
- <entry><phrase role="X-SAMPA">[n]</phrase>, <phrase role="X-SAMPA">[n=]</phrase>, <phrase role="X-SAMPA">[N]</phrase>, <phrase role="X-SAMPA">[N=]</phrase>
+ <entry>
+ <simplelist type="inline">
+ <member><phrase role="X-SAMPA">[n]</phrase></member>
+ <member><phrase role="X-SAMPA">[n=]</phrase></member>
+ <member><phrase role="X-SAMPA">[N]</phrase></member>
+ <member><phrase role="X-SAMPA">[N=]</phrase></member>
+ </simplelist>
</entry>
<entry>a voiced dental or velar nasal (may be syllabic)</entry>
</row>
<row>
<entry><jbophrase role="letteral">o</jbophrase></entry>
- <entry><phrase role="IPA">[o]</phrase>, <phrase role="IPA">[ɔ]</phrase>
+ <entry>
+ <simplelist type="inline">
+ <member><phrase role="IPA">[o]</phrase></member>
+ <member><phrase role="IPA">[ɔ]</phrase></member>
+ </simplelist>
</entry>
- <entry><phrase role="X-SAMPA">[o]</phrase>, <phrase role="X-SAMPA">[O]</phrase>
+ <entry>
+ <simplelist type="inline">
+ <member><phrase role="X-SAMPA">[o]</phrase></member>
+ <member><phrase role="X-SAMPA">[O]</phrase></member>
+ </simplelist>
</entry>
<entry>a back mid vowel</entry>
</row>
<row>
<entry><jbophrase role="letteral">p</jbophrase></entry>
<entry><phrase role="IPA">[p]</phrase></entry>
<entry><phrase role="X-SAMPA">[p]</phrase></entry>
<entry>an unvoiced bilabial stop</entry>
</row>
<row>
<entry><jbophrase role="letteral">r</jbophrase></entry>
- <entry><phrase role="IPA">[r]</phrase>, <phrase role="IPA">[ɹ]</phrase>, <phrase role="IPA">[ɾ]</phrase>, <phrase role="IPA">[ʀ]</phrase>, <phrase role="IPA">[r̩]</phrase>, <phrase role="IPA">[ɹ̩]</phrase>, <phrase role="IPA">[ɾ̩]</phrase>, <phrase role="IPA">[ʀ̩]</phrase>
+ <entry>
+ <simplelist type="inline">
+ <member><phrase role="IPA">[r]</phrase></member>
+ <member><phrase role="IPA">[ɹ]</phrase></member>
+ <member><phrase role="IPA">[ɾ]</phrase></member>
+ <member><phrase role="IPA">[ʀ]</phrase></member>
+ <member><phrase role="IPA">[r̩]</phrase></member>
+ <member><phrase role="IPA">[ɹ̩]</phrase></member>
+ <member><phrase role="IPA">[ɾ̩]</phrase></member>
+ <member><phrase role="IPA">[ʀ̩]</phrase></member>
+ </simplelist>
</entry>
- <entry><phrase role="X-SAMPA">[r]</phrase>, <phrase role="X-SAMPA">[r\]</phrase>, <phrase role="X-SAMPA">[4]</phrase>, <phrase role="X-SAMPA">[R\]</phrase>, <phrase role="X-SAMPA">[r=]</phrase>, <phrase role="X-SAMPA">[r\=]</phrase>, <phrase role="X-SAMPA">[4=]</phrase>, <phrase role="X-SAMPA">[R\=]</phrase>
+ <entry>
+ <simplelist type="inline">
+ <member><phrase role="X-SAMPA">[r]</phrase></member>
+ <member><phrase role="X-SAMPA">[r\]</phrase></member>
+ <member><phrase role="X-SAMPA">[4]</phrase></member>
+ <member><phrase role="X-SAMPA">[R\]</phrase></member>
+ <member><phrase role="X-SAMPA">[r=]</phrase></member>
+ <member><phrase role="X-SAMPA">[r\=]</phrase></member>
+ <member><phrase role="X-SAMPA">[4=]</phrase></member>
+ <member><phrase role="X-SAMPA">[R\=]</phrase></member>
+ </simplelist>
</entry>
<entry>a rhotic sound</entry>
</row>
<row>
<entry><jbophrase role="letteral">s</jbophrase></entry>
<entry><phrase role="IPA">[s]</phrase></entry>
<entry><phrase role="X-SAMPA">[s]</phrase></entry>
<entry>an unvoiced alveolar sibilant</entry>
</row>
<row>
@@ -232,23 +321,31 @@
<entry>an unvoiced dental/alveolar stop</entry>
</row>
<row>
<entry><jbophrase role="letteral">u</jbophrase></entry>
<entry><phrase role="IPA">[u]</phrase></entry>
<entry><phrase role="X-SAMPA">[u]</phrase></entry>
<entry>a back close vowel</entry>
</row>
<row>
<entry><jbophrase role="letteral">v</jbophrase></entry>
- <entry><phrase role="IPA">[v]</phrase>, <phrase role="IPA">[β]</phrase>
+ <entry>
+ <simplelist type="inline">
+ <member><phrase role="IPA">[v]</phrase></member>
+ <member><phrase role="IPA">[β]</phrase></member>
+ </simplelist>
</entry>
- <entry><phrase role="X-SAMPA">[v]</phrase>, <phrase role="X-SAMPA">[B]</phrase>
+ <entry>
+ <simplelist type="inline">
+ <member><phrase role="X-SAMPA">[v]</phrase></member>
+ <member><phrase role="X-SAMPA">[B]</phrase></member>
+ </simplelist>
</entry>
<entry>a voiced labial fricative</entry>
</row>
<row>
<entry><jbophrase role="letteral">x</jbophrase></entry>
<entry><phrase role="IPA">[x]</phrase></entry>
<entry><phrase role="X-SAMPA">[x]</phrase></entry>
<entry>an unvoiced velar fricative</entry>
</row>
<row>
@@ -338,24 +435,27 @@
<phrase role="IPA">[ʔ]</phrase>) is considered a pause of shortest length. A pause (or glottal stop) may appear between any two words, and in certain cases - explained in detail in
<xref linkend="chapter-morphology"/>- must occur. In particular, a word beginning with a vowel is always preceded by a pause, and a word ending in a consonant is always followed by a pause.</para>
<para> <indexterm type="general-imported"><primary>period</primary><secondary>optional</secondary></indexterm> Technically, the period is an optional reminder to the reader of a mandatory pause that is dictated by the rules of the language; because these rules are unambiguous, a missing period can be inferred from otherwise correct text. Periods are included only as an aid to the reader.</para>
<para> <indexterm type="general-imported"><primary>period</primary><secondary>within a word</secondary></indexterm> A period also may be found apparently embedded in a word. When this occurs, such a written string is not one word but two, written together to indicate that the writer intends a unitary meaning for the compound. It is not really necessary to use a space between words if a period appears.</para>
<para> <indexterm type="general-imported"><primary>pause</primary><secondary>contrasted with syllable break</secondary></indexterm> <indexterm type="general-imported"><primary>syllable break</primary><secondary>contrasted with pause</secondary></indexterm> <indexterm type="general-imported"><primary>syllable break</primary><secondary>representation in Lojban</secondary></indexterm> <indexterm type="general-imported"><primary>comma</primary><secondary>definition of</secondary></indexterm> The comma is used to indicate a syllable break within a word, generally one that is not obvious to the reader. Such a comma is written to separate syllables, but indicates that there must be no pause between them, in contrast to the period. Between two vowels, a comma indicates that some type of glide may be necessary to avoid a pause that would split the two syllables into separate words. It is always legal to use the apostrophe (IPA
<phrase role="IPA">[h]</phrase>) sound in pronouncing a comma. However, a comma cannot be pronounced as a pause or glottal stop between the two letters separated by the comma, because that pronunciation would split the word into two words.</para>
<para> <indexterm type="general-imported"><primary>comma</primary><secondary>optional</secondary></indexterm> <indexterm type="general-imported"><primary>comma</primary><secondary>main use of</secondary></indexterm> Otherwise, a comma is usually only used to clarify the presence of syllabic
- <jbophrase role="letteral">l</jbophrase>,
- <jbophrase role="letteral">m</jbophrase>,
- <jbophrase role="letteral">n</jbophrase>, or
- <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>
+ <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">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>
<pronunciation>
<jbo>.i.ai.i.ai.o</jbo>
<ipa><phrase role="IPA">[ʔi ʔaj ʔi ʔaj ʔo]</phrase></ipa>
@@ -426,21 +526,21 @@
<colspec colnum="2" colname="col2"/>
<colspec colnum="3" colname="col3"/>
<thead>
<row>
<entry>Letters</entry>
<entry>IPA</entry>
<entry>Description</entry>
</row>
</thead>
<tbody>
- <!--zort found the first row of the very first table pasted here for some reason; if you find anything funny going on that may have to do with it-->
+ <!-- zort found the first row of the very first table pasted here for some reason; if you find anything funny going on that may have to do with it -->
<row>
<entry><jbophrase role="diphthong">ai</jbophrase></entry>
<entry><phrase role="IPA">[aj]</phrase></entry>
<entry>an open vowel with palatal off-glide</entry>
</row>
<row>
<entry><jbophrase role="diphthong">ei</jbophrase></entry>
<entry><phrase role="IPA">[ɛj]</phrase></entry>
<entry>a front mid vowel with palatal off-glide</entry>
</row>
@@ -512,48 +612,57 @@
<row>
<entry><jbophrase role="diphthong">uy</jbophrase></entry>
<entry><phrase role="IPA">[wə]</phrase></entry>
<entry>a central mid vowel with labial on-glide</entry>
</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 (
- <jbophrase role="diphthong">ai</jbophrase>,
- <jbophrase role="diphthong">ei</jbophrase>,
- <jbophrase role="diphthong">oi</jbophrase>, and
- <jbophrase role="diphthong">au</jbophrase>, 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,
-
- <phrase role="IPA">[l̩]</phrase>,
- <phrase role="IPA">[m̩]</phrase>,
- <phrase role="IPA">[n̩]</phrase>, and
- <phrase role="IPA">[r̩]</phrase>, are variants of the non-syllabic
- <phrase role="IPA">[l]</phrase>,
- <phrase role="IPA">[m]</phrase>,
- <phrase role="IPA">[n]</phrase>, and
- <phrase role="IPA">[r]</phrase> respectively. They normally have only a limited distribution, appearing in Lojban names and borrowings, although in principle any
-
- <jbophrase role="letteral">l</jbophrase>,
- <jbophrase role="letteral">m</jbophrase>,
- <jbophrase role="letteral">n</jbophrase>, or
- <jbophrase role="letteral">r</jbophrase> may be pronounced syllabically. If a syllabic consonant appears next to a
-
- <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>
+ <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">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">[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">[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">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">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>
or <!--FIXME: this gets deleted-->
<ipa><phrase role="IPA">[brl̩ gan]</phrase></ipa>
</pronunciation>
@@ -702,72 +811,80 @@
<entry><jbophrase role="letteral">z</jbophrase></entry>
</row>
<row>
<entry><jbophrase role="letteral">x</jbophrase></entry>
<entry>-</entry>
</row>
</tbody>
</tgroup>
</informaltable>
<para>The consonant
- <jbophrase role="letteral">x</jbophrase> has no voiced counterpart in Lojban. The remaining consonants,
- <jbophrase role="letteral">l</jbophrase>,
- <jbophrase role="letteral">m</jbophrase>,
- <jbophrase role="letteral">n</jbophrase>, and
- <jbophrase role="letteral">r</jbophrase>, are typically pronounced with voice, but can be pronounced unvoiced.</para>
+ <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">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
<quote>d</quote> or even an alveolar tap (IPA
<phrase role="IPA">[ɾ]</phrase>) is unacceptable in Lojban.
</para>
<para> <indexterm type="general-imported"><primary>consonants</primary><secondary>final</secondary></indexterm> <indexterm type="general-imported"><primary>consonants</primary><secondary>restrictions on</secondary></indexterm> Lojban imposes no restrictions on the appearance of single consonants in any valid consonant position; however, no consonant (including syllabic consonants) occurs final in a word except in Lojbanized names.</para>
<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
- <jbophrase role="letteral">l</jbophrase>,
- <jbophrase role="letteral">m</jbophrase>,
- <jbophrase role="letteral">n</jbophrase>, and
- <jbophrase role="letteral">r</jbophrase> 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.
+ <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">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
- <jbophrase role="letteral">c</jbophrase>,
- <jbophrase role="letteral">j</jbophrase>,
- <jbophrase role="letteral">s</jbophrase>,
- <jbophrase role="letteral">z</jbophrase>.
+ <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">z</jbophrase></member>
+ </simplelist>
</para>
</listitem>
<listitem>
- <para>The specific pairs
- <jbophrase role="morphology" valid="false">cx</jbophrase>,
- <jbophrase role="morphology" valid="false">kx</jbophrase>,
- <jbophrase role="morphology" valid="false">xc</jbophrase>,
- <jbophrase role="morphology" valid="false">xk</jbophrase>, and
- <jbophrase role="morphology" valid="false">mz</jbophrase> are forbidden.
+ <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">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>
<indexterm type="example-imported"><primary>James</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c3e6d1"/>
@@ -1007,27 +1124,27 @@
</orderedlist>
<para> <indexterm type="general-imported"><primary>consonant clusters</primary><secondary>more than three consonants in</secondary></indexterm> Lojbanized names can begin or end with any permissible consonant pair, not just the 48 initial consonant pairs listed above, and can have consonant triples in any location, as long as the pairs making up those triples are permissible. In addition, names can contain consonant clusters with more than three consonants, again requiring that each pair within the cluster is valid.</para>
</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
-
-
- <phrase role="IPA">[ɪ]</phrase>,
- <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
+ <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></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>
or <!--FIXME: this gets deleted-->
<ipa><phrase role="IPA">[vɪ ˈru si]</phrase></ipa>
@@ -1076,22 +1193,22 @@
<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>
</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
+ <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>
</pronunciation>
@@ -1211,29 +1328,28 @@
<jbophrase role="letteral">z</jbophrase> and
<jbophrase role="letteral">b</jbophrase> or before
<jbophrase role="morphology">zb</jbophrase>.</para>
<para> <indexterm type="general-imported"><primary>stressed vowel</primary><secondary>compared with stressed syllable</secondary></indexterm> <indexterm type="general-imported"><primary>stressed syllable</primary><secondary>compared with stressed vowel</secondary></indexterm> <indexterm type="general-imported"><primary>stress</primary><secondary>definition of</secondary></indexterm> Stress is a relatively louder pronunciation of one syllable in a word or group of words. Since every syllable has a vowel sound (or diphthong or syllabic consonant) as its nucleus, and the stress is on the vowel sound itself, the terms
<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 (
-
- <jbophrase role="letteral">l</jbophrase>,
- <jbophrase role="letteral">m</jbophrase>,
- <jbophrase role="letteral">n</jbophrase>, or
- <jbophrase role="letteral">r</jbophrase>) are never counted. (The Lojban term for penultimate stress is
- <jbophrase>da'amoi terbasna</jbophrase>.) Similarly, syllables created solely by adding a buffer vowel, such as
-
+ <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">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
<jbophrase>cmavo</jbophrase>) may be stressed on any syllable or none at all. However, primary stress may not be used in a syllable just preceding a brivla, unless a pause divides them; otherwise, the two words may run together.</para>
<para> <indexterm type="general-imported"><primary>stress</primary><secondary>secondary</secondary></indexterm> Secondary stress is the optional and non-distinctive emphasis used for other syllables besides those required to have either weak or primary stress. There are few rules governing secondary stress, which typically will follow a speaker's native language habits or preferences. Secondary stress can be used for contrast, or for emphasis of a point. Secondary stress can be emphasized at any level up to primary stress, although the speaker must not allow a false primary stress in brivla, since errors in word resolution could result.</para>
<para> The following are Lojban words with stress explicitly shown:</para>
@@ -1737,21 +1853,21 @@
<quote>d</quote> in the words
<quote>metal</quote> and
<quote>medal</quote> respectively. A tongue-tip flap.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>[ʀ]</term>
<listitem>
<para>One version of Lojban
<jbophrase role="letteral">r</jbophrase>. Not an English sound. The French or German
- <phrase xml:lang="de"><quote xml:lang="fr">r</quote></phrase> in <!--not sure how else to designate two languages at once-->
+ <phrase xml:lang="de"><quote xml:lang="fr">r</quote></phrase> in <!-- how else to designate two languages at once? -->
<quote xml:lang="fr">reine</quote> or
<quote xml:lang="de">rot</quote> respectively. A uvular trill.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<phrase role="IPA">[r̩]</phrase>,
<phrase role="IPA">[ɹ̩]</phrase>,
<phrase role="IPA">[ɾ̩]</phrase>,
<phrase role="IPA">[ʀ̩]</phrase></term>
@@ -1998,26 +2114,23 @@
<para>
<jbophrase role="diphthong">ia</jbophrase> through
<jbophrase role="diphthong">iu</jbophrase> and
<jbophrase role="diphthong">ua</jbophrase> through
<jbophrase role="diphthong">uu</jbophrase> remain unchanged.
</para>
</listitem>
<listitem>
<para>
<jbophrase>a'i</jbophrase>,
-
<jbophrase>e'i</jbophrase>,
<jbophrase>o'i</jbophrase> and
-
<jbophrase>a'o</jbophrase> become
-
<jbophrase glossary="false" valid="false">a,i</jbophrase>,
<jbophrase glossary="false" valid="false">e,i</jbophrase>,
<jbophrase glossary="false" valid="false">o,i</jbophrase> and
<jbophrase glossary="false" valid="false">a,o</jbophrase>.
</para>
</listitem>
<listitem>
<para>
<jbophrase>i'a</jbophrase> through
<jbophrase>i'u</jbophrase> and
@@ -2032,64 +2145,61 @@
<jbophrase role="diphthong" valid="false">i,u</jbophrase> and
<jbophrase role="diphthong" valid="false">u,a</jbophrase> through
<jbophrase role="diphthong" valid="false">u,u</jbophrase> in names, fu'ivla, and attitudinal cmavo.
</para>
</listitem>
<listitem>
<para>All other vowel pairs simply drop the apostrophe.</para>
</listitem>
</itemizedlist>
- <para>The result of these rules is to eliminate the apostrophe altogether, replacing it with comma where necessary, and otherwise with nothing. In addition, names and the cmavo
- <jbophrase>.i</jbophrase> are capitalized, and irregular stress is marked with an apostrophe (now no longer used for a sound) following the stressed syllable.</para>
-
-
+ <para>The result of these rules is to eliminate the apostrophe altogether, replacing it with comma where necessary, and otherwise with nothing. In addition, names and the cmavo <jbophrase>.i</jbophrase> are capitalized, and irregular stress is marked with an apostrophe (now no longer used for a sound) following the stressed syllable.</para>
<para>Three points must be emphasized about this alternative orthography:</para>
-
<itemizedlist>
<listitem>
- <para> <indexterm type="general-imported"><primary>non-standard orthographies</primary><secondary>caveat</secondary></indexterm> It is not standard, and has not been used.</para>
+ <para><indexterm type="general-imported"><primary>non-standard orthographies</primary><secondary>caveat</secondary></indexterm>It is not standard, and has not been used.</para>
</listitem>
<listitem>
<para>It does not represent any changes to the standard Lojban phonology; it is simply a representation of the same phonology using a different written form.</para>
</listitem>
<listitem>
<para>It was designed to aid in a planned rapprochement between the Logical Language Group and The Loglan Institute, a group headed by James Cooke Brown. The rapprochement never took place.</para>
-
</listitem>
</itemizedlist>
<para> <indexterm type="general-imported"><primary>non-standard orthographies</primary><secondary>Cyrillic</secondary></indexterm> There also exists a Cyrillic orthography for Lojban which was designed when the introductory Lojban brochure was translated into Russian. It uses the
-
- <quote>а</quote>,
- <quote>б</quote>,
- <quote>в</quote>,
- <quote>г</quote>,
- <quote>д</quote>,
- <quote>е</quote>,
- <quote>ж</quote>,
- <quote>з</quote>,
- <quote>и</quote>,
- <quote>к</quote>,
- <quote>л</quote>,
- <quote>м</quote>,
- <quote>н</quote>,
- <quote>о</quote>,
- <quote>п</quote>,
- <quote>р</quote>,
- <quote>с</quote>,
- <quote>т</quote>,
- <quote>у</quote>,
- <quote>ф</quote>,
- <quote>х</quote>, and
- <quote>ш</quote> 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>
+ <simplelist type="inline">
+ <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>
+ <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></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
<citation>The Lord Of The Rings</citation>, has been devised for Lojban. The following mapping, which closely resembles that used for Westron, will be meaningful only to those who have read those appendixes. In brief, the tincotéma and parmatéma are used in the conventional ways; the calmatéma represents palatal consonants, and the quessetéma represents velar consonants.</para>
<informaltable>
<tgroup cols="2">
<colspec colnum="1" colname="col1"/>
--
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.