[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bpfk] dag-cll git updates for Fri Jan 28 17:21:09 EST 2011
commit dd83d67f677ea3c2a3febdb48156e020c1d19bd6
Merge: 7143025 985b472
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date: Fri Jan 28 11:54:58 2011 -0800
Merge commit '985b472a79ec5ebce0f569c94f262a11e7f18151' into gh-pages
commit 985b472a79ec5ebce0f569c94f262a11e7f18151
Author: Eitan Postavsky <eitanp32@gmail.com>
Date: Mon Jan 3 11:27:51 2011 -0500
Various stuff in TODO, 1.xml, 3.xml, mostly 4.xml. Some FIXMEs.
Invented <example role="compound-cmavo-example"> and <compound-cmavo>
(replacing <interlinear-gloss>) for examples showing how compound
cmavo break apart. The FIXMEs are regarding some usual stuff, one
jcowan-approved erratum, and what layout to use for a certain table.
diff --git a/todocbook/1.xml b/todocbook/1.xml
index 1e8e339..73b2cd5 100644
--- a/todocbook/1.xml
+++ b/todocbook/1.xml
@@ -72,29 +72,30 @@
<quote>mangle</quote>? As yet, nobody in the real Lojbanistan speaks the language at all well, by the standards of the imaginary Lojbanistan; that is one of the circumstances this book is meant to help remedy.</para>
</section>
<section xml:id="section-conventions">
<title>What are the typographical conventions of this book?</title>
<para>Each chapter is broken into numbered sections; each section contains a mixture of expository text, numbered examples, and possibly tables.</para>
<para> <indexterm type="general-imported"><primary>this book</primary><secondary>examples of</secondary></indexterm> <indexterm type="general-imported"><primary>examples in this book</primary></indexterm> The reader will notice a certain similarity in the examples used throughout the book. One chapter after another rings the changes on the self-same sentences:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-hrtj">
<title>
+ <indexterm type="example-imported"><primary>go to the store</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c1e3d1"/>
</title>
<interlinear-gloss>
<jbo>mi klama le zarci</jbo>
<gloss>I go-to that-which-I-describe-as-a store.</gloss>
<en>I go to the store.</en>
</interlinear-gloss>
</example>
- <para> <indexterm type="example-imported"><primary>go to the store</primary><secondary>example</secondary></indexterm> will become wearisomely familiar before
+ <para> will become wearisomely familiar before
<xref linkend="chapter-grammars"/> is reached. This method is deliberate; I have tried to use simple and (eventually) familiar examples wherever possible, to avoid obscuring new grammatical points with new vocabulary. Of course, this is not the method of a textbook, but this book is not a textbook (although people have learned Lojban from it and its predecessors). Rather, it is intended both for self-learning (of course, at present would-be Lojban teachers must be self-learners) and to serve as a reference in the usual sense, for looking up obscure points about the language.</para>
<para> <indexterm type="general-imported"><primary>examples</primary><secondary>structure of</secondary></indexterm> <indexterm type="general-imported"><primary>structure of examples</primary></indexterm> <indexterm type="general-imported"><primary>example of examples</primary></indexterm> It is useful to talk further about
<xref linkend="example-random-id-hrtj"/> for what it illustrates about examples in this book. Examples usually occupy three lines. The first of these is in Lojban, the second in a word-by-word literal translation of the Lojban into English, and the third in colloquial English. The second and third lines are sometimes called the
<quote>literal translation</quote> and the
<quote>colloquial translation</quote> respectively. Sometimes, when clarity is not sacrificed thereby, one or both are omitted. If there is more than one Lojban sentence, it generally means that they have the same meaning.</para>
<para> <indexterm type="general-imported"><primary>square brackets</primary><secondary>use of in notation</secondary></indexterm> Words are sometimes surrounded by square brackets. In Lojban texts, these enclose optional grammatical particles that may (in the context of the particular example) be either omitted or included. In literal translations, they enclose words that are used as conventional translations of specific Lojban words, but don't have exactly the meanings or uses that the English word would suggest. In
<xref linkend="chapter-phonology"/>, square brackets surround phonetic representations in the International Phonetic Alphabet.</para>
@@ -164,25 +165,25 @@
<para>
<anchor xml:id="c1"/>
<mediaobject>
<alt>The picture for chapter 1</alt>
<imageobject>
<imagedata fileref="chapter-about.gif"/>
</imageobject>
</mediaobject> has the following text:</para>
<programlisting xml:space="preserve">
coi lojban. coi rodo
-</programlisting>
+ </programlisting>
<para>which has the following translation:</para>
<programlisting xml:space="preserve">
Greetings, O Lojban! Greetings, all-of you
-</programlisting>
+ </programlisting>
</listitem>
<listitem>
<para>
<anchor xml:id="c2"/>
<mediaobject>
<alt>The picture for chapter 2</alt>
<imageobject>
<imagedata fileref="chapter-tour.gif"/>
</imageobject>
</mediaobject> has no text.</para>
diff --git a/todocbook/3.xml b/todocbook/3.xml
index edf99ac..bf4093f 100644
--- a/todocbook/3.xml
+++ b/todocbook/3.xml
@@ -32,22 +32,21 @@
<member>p</member>
<member>r</member>
<member>s</member>
<member>t</member>
<member>u</member>
<member>v</member>
<member>x</member>
<member>y</member>
<member>z</member>
</simplelist>
- </para>
- <para>omitting the letters
+ omitting the letters
<quote>h</quote>,
<quote>q</quote>, and
<quote>w</quote>.</para>
<para> <indexterm type="general-imported"><primary>alphabetic order</primary></indexterm> The alphabetic order given above is that of the ASCII coded character set, widely used in computers. By making Lojban alphabetical order the same as ASCII, computerized sorting and searching of Lojban text is facilitated.</para>
<para> <indexterm type="general-imported"><primary>stress</primary><secondary>showing non-standard</secondary></indexterm> <indexterm type="general-imported"><primary>capital letters</primary><secondary>use of</secondary></indexterm> Capital letters are used only to represent non-standard stress, which can appear only in the representation of Lojbanized names. Thus the English name
<quote>Josephine</quote>, as normally pronounced, is Lojbanized as
<jbophrase>DJOsefin.</jbophrase>, pronounced
<phrase role="IPA">['d蕭os蓻fin蕯]</phrase>. (See
@@ -427,21 +426,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 mark: I 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>
@@ -548,21 +547,21 @@
<jbophrase role="letteral">m</jbophrase>,
<jbophrase role="letteral">n</jbophrase>, or
<jbophrase role="letteral">r</jbophrase> that is not syllabic, it may not be clear which is which:</para>
<example role="pronunciation-example" xml:id="example-random-id-k2CE">
<title>
<anchor xml:id="c3e4d1"/>
</title>
<pronunciation>
<jbo>brlgan.</jbo>
<ipa><phrase role="IPA">[br泰l gan]</phrase></ipa>
- or <!--zort mark: this gets deleted-->
+ or <!--FIXME: this gets deleted-->
<ipa><phrase role="IPA">[brl泰 gan]</phrase></ipa>
</pronunciation>
</example>
<para>is a hypothetical Lojbanized name with more than one valid pronunciation; however it is pronounced, it remains the same word.</para>
<para> <!--FIXME: there's no example for this "Earl" to go in--><indexterm type="example-imported"><primary>Earl</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>syllabic consonants</primary><secondary>final in word</secondary></indexterm> Syllabic consonants are treated as consonants rather than vowels from the standpoint of Lojban morphology. Thus Lojbanized names, which are generally required to end in a consonant, are allowed to end with a syllabic consonant. An example is
<jbophrase>rl.</jbophrase>, which is an approximation of the English name
<quote>Earl</quote>, and has two syllabic consonants.</para>
@@ -783,22 +782,20 @@
<quote>James</quote>, which is
<phrase role="IPA">[d蕭蓻jmz]</phrase>, would Lojbanize as
<jbophrase valid="false">djeimz.</jbophrase>, which contains a forbidden consonant pair.</para>
</section>
<section xml:id="section-initial-pairs">
<title>Initial Consonant Pairs</title>
<para> <indexterm type="general-imported"><primary>consonant pairs</primary><secondary>initial</secondary></indexterm> The set of consonant pairs that may appear at the beginning of a word (excluding Lojbanized names) is far more restricted than the fairly large group of permissible consonant pairs described in
<xref linkend="section-clusters"/>. Even so, it is more than English allows, although hopefully not more than English-speakers (and others) can learn to pronounce.</para>
<para> <indexterm type="general-imported"><primary>initial consonant pairs</primary><secondary>list of</secondary></indexterm> There are just 48 such permissible initial consonant pairs, as follows:</para>
-
-
<informaltable>
<tgroup cols="8">
<colspec colnum="1" colname="col1"/>
<colspec colnum="2" colname="col2"/>
<colspec colnum="3" colname="col3"/>
<colspec colnum="4" colname="col4"/>
<colspec colnum="5" colname="col5"/>
<colspec colnum="6" colname="col6"/>
<colspec colnum="7" colname="col7"/>
<colspec colnum="8" colname="col8"/>
@@ -1025,33 +1022,33 @@
<phrase role="IPA">[蕣]</phrase>, or even
<phrase role="IPA">[蕪]</phrase>, but there probably is no universally acceptable buffer sound. When using a consonant buffer, the sound should be made as short as possible. Two examples showing such buffering (we will use
<phrase role="IPA">[瑟]</phrase> in this chapter) are:</para>
<example role="pronunciation-example" xml:id="example-random-id-k2dg">
<title>
<anchor xml:id="c3e8d1"/>
</title>
<pronunciation>
<jbo>vrusi</jbo>
<ipa><phrase role="IPA">[藞vru si]</phrase></ipa>
- or <!--zort mark: this gets deleted-->
+ or <!--FIXME: this gets deleted-->
<ipa><phrase role="IPA">[v瑟 藞ru si]</phrase></ipa>
</pronunciation>
</example>
<example role="pronunciation-example" xml:id="example-random-id-k2dI">
<title>
<anchor xml:id="c3e8d2"/>
<indexterm type="example-imported"><primary>Amsterdam</primary><secondary>example</secondary></indexterm>
</title>
<pronunciation>
- <jbo>.AMsterdam.</jbo>
+ <jbo role="pronunciation">.AMsterdam.</jbo>
<ipa><phrase role="IPA">[蕯am ster dam蕯]</phrase></ipa>
- or <!--zort mark: this gets deleted-->
+ or <!--FIXME: this gets deleted-->
<ipa><phrase role="IPA">[藞蕯a m瑟 s瑟 t蓻 r瑟 da m瑟蕯]</phrase></ipa>
</pronunciation>
</example>
<para> <indexterm type="general-imported"><primary>stress</primary><secondary>effect of buffer vowel on</secondary></indexterm> <indexterm type="general-imported"><primary>buffer vowel</primary><secondary>and stress</secondary></indexterm> When a buffer vowel is used, it splits each buffered consonant into its own syllable. However, the buffering syllables are never stressed, and are not counted in determining stress. They are, in effect, not really syllables to a Lojban listener, and thus their impact is ignored.</para>
<para>Here are more examples of unbuffered and buffered pronunciations:</para>
<example role="pronunciation-example" xml:id="example-random-id-k2DT">
<title>
<anchor xml:id="c3e8d3"/>
</title>
@@ -1284,23 +1281,23 @@
<jbophrase role="morphology">ng</jbophrase> represents two separate consonants that must both be pronounced; you may not use
<phrase role="IPA">[艐]</phrase> to pronounce Lojban
<jbophrase role="morphology">ng</jbophrase>, although
<phrase role="IPA">[艐g]</phrase> is acceptable. English speakers are likely to have to pronounce the ending with a buffer, as one of the following:</para>
<example role="pronunciation-example" xml:id="example-random-id-k2T5">
<title>
<anchor xml:id="c3e9d9"/>
</title>
<pronunciation>
<ipa><phrase role="IPA">[藞蕯arm stron g瑟蕯]</phrase></ipa>
- or <!--zort mark: this gets deleted-->
+ or <!--FIXME: this gets deleted-->
<ipa><phrase role="IPA">[藞蕯arm stro艐 g瑟蕯]</phrase></ipa>
- or even <!--zort mark: this gets deleted-->
+ or even <!--FIXME: this gets deleted-->
<ipa><phrase role="IPA">[藞蕯arm stro n瑟g蕯]</phrase></ipa>
</pronunciation>
</example>
<para>The normal English pronunciation of the name
<quote>Armstrong</quote> could be Lojbanized as:</para>
<example role="pronunciation-example" xml:id="example-random-id-vY2y">
<title>
<anchor xml:id="c3e9d10"/>
</title>
@@ -1740,21 +1737,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 <!--zort mark: not sure how else to designate two languages at once-->
+ <phrase xml:lang="de"><quote xml:lang="fr">r</quote></phrase> in <!--not sure 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>
@@ -2086,21 +2083,21 @@
<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>
<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> <!--zort mark: not sure how to make the two tgroups display side by side-->
+ <informaltable>
<tgroup cols="2">
<colspec colnum="1" colname="col1"/>
<colspec colnum="2" colname="col2"/>
<tbody>
<row>
<entry><jbophrase role="letteral">t</jbophrase></entry>
<entry><phrase xml:lang="art">tinco</phrase></entry>
</row>
<row>
<entry>-</entry>
diff --git a/todocbook/4.xml b/todocbook/4.xml
index 84042e9..9b8deba 100644
--- a/todocbook/4.xml
+++ b/todocbook/4.xml
@@ -8,209 +8,211 @@
<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>
- <variablelist>
- <varlistentry>
- <term>1)</term>
- <listitem>
- <para> <indexterm type="general-imported"><primary>y</primary><secondary>considered not to be a vowel for morphological discussions</secondary></indexterm> <indexterm type="general-imported"><primary>V</primary><secondary>as a symbol for a single vowel</secondary></indexterm> <indexterm type="general-imported"><primary>morphology</primary><secondary>symbolic conventions for discussing</secondary></indexterm> V represents any single Lojban vowel except
- <jbophrase role="letteral">y</jbophrase>; that is, it represents
- <jbophrase role="letteral">a</jbophrase>,
- <jbophrase role="letteral">e</jbophrase>,
- <jbophrase role="letteral">i</jbophrase>,
- <jbophrase role="letteral">o</jbophrase>, or
- <jbophrase role="letteral">u</jbophrase>.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>2)</term>
- <listitem>
- <para> <indexterm type="general-imported"><primary>VV string</primary><secondary>as a symbol for a double vowel</secondary></indexterm> VV represents either a diphthong, one of the following:
- <programlisting xml:space="preserve">
- ai ei oi au
- </programlisting> or a two-syllable vowel pair with an apostrophe separating the vowels, one of the following:
- <cmavo-list>
- <cmavo-entry>
- <cmavo>a'a a'e a'i</cmavo>
-
-
- <selmaho>a'o</selmaho>
-
- <description>a'u</description>
- </cmavo-entry>
- <cmavo-entry>
- <cmavo>e'a e'e e'i</cmavo>
-
-
- <selmaho>e'o</selmaho>
-
- <description>e'u</description>
- </cmavo-entry>
- <cmavo-entry>
- <cmavo>i'a i'e i'i</cmavo>
-
- <selmaho>i'o</selmaho>
- <description>i'u</description>
- </cmavo-entry>
- <cmavo-entry>
- <cmavo>o'a o'e o'i</cmavo>
-
- <selmaho>o'o</selmaho>
- <description>o'u</description>
-
- </cmavo-entry>
- <cmavo-entry>
- <cmavo>u'a u'e u'i</cmavo>
- <selmaho>u'o</selmaho>
- <description>u'u</description>
-
- </cmavo-entry>
- </cmavo-list></para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>3)</term>
- <listitem>
- <para> <indexterm type="general-imported"><primary>apostrophe</primary><secondary>as not a consonant for morphological discussions</secondary></indexterm> <indexterm type="general-imported"><primary>syllabic r</primary><secondary>as a consonant for morphological discussions</secondary></indexterm> <indexterm type="general-imported"><primary>syllabic n</primary><secondary>as a consonant for morphological discussions</secondary></indexterm> <indexterm type="general-imported"><primary>syllabic m</primary><secondary>as a consonant for morphological discussions</secondary></indexterm> <indexterm type="general-imported"><primary>syllabic l</primary><secondary>considered as a consonant for morphological discussions</secondary></indexterm> <indexterm type="general-imported"><primary>C string</primary><secondary>as a symbol for a single consonant</secondary></indexterm> C represents a single Lojban consonant, not including the apostrophe, one of
- <jbophrase role="letteral">b</jbophrase>,
- <jbophrase role="letteral">c</jbophrase>,
- <jbophrase role="letteral">d</jbophrase>,
- <jbophrase role="letteral">f</jbophrase>,
- <jbophrase role="letteral">g</jbophrase>,
- <jbophrase role="letteral">j</jbophrase>,
- <jbophrase role="letteral">k</jbophrase>,
- <jbophrase role="letteral">l</jbophrase>,
- <jbophrase role="letteral">m</jbophrase>,
- <jbophrase role="letteral">n</jbophrase>,
- <jbophrase role="letteral">p</jbophrase>,
- <jbophrase role="letteral">r</jbophrase>,
- <jbophrase role="letteral">s</jbophrase>,
- <jbophrase role="letteral">t</jbophrase>,
- <jbophrase role="letteral">v</jbophrase>,
- <jbophrase role="letteral">x</jbophrase>, or
- <jbophrase role="letteral">z</jbophrase>. Syllabic
- <jbophrase role="letteral">l</jbophrase>,
- <jbophrase role="letteral">m</jbophrase>,
- <jbophrase role="letteral">n</jbophrase>, and
- <jbophrase role="letteral">r</jbophrase> always count as consonants for the purposes of this chapter.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>4)</term>
- <listitem>
- <para> <indexterm type="general-imported"><primary>CC string</primary><secondary>as a symbol for a permissible initial consonant pair</secondary></indexterm> CC represents two adjacent consonants of type C which constitute one of the 48 permissible initial consonant pairs:
+ <orderedlist>
+ <listitem>
+ <para> <indexterm type="general-imported"><primary>y</primary><secondary>considered not to be a vowel for morphological discussions</secondary></indexterm> <indexterm type="general-imported"><primary>V</primary><secondary>as a symbol for a single vowel</secondary></indexterm> <indexterm type="general-imported"><primary>morphology</primary><secondary>symbolic conventions for discussing</secondary></indexterm> V represents any single Lojban vowel except
+ <jbophrase role="letteral">y</jbophrase>; that is, it represents
+ <jbophrase role="letteral">a</jbophrase>,
+ <jbophrase role="letteral">e</jbophrase>,
+ <jbophrase role="letteral">i</jbophrase>,
+ <jbophrase role="letteral">o</jbophrase>, or
+ <jbophrase role="letteral">u</jbophrase>.</para>
+ </listitem>
+ <listitem>
+ <para> <indexterm type="general-imported"><primary>VV string</primary><secondary>as a symbol for a double vowel</secondary></indexterm> VV represents either a diphthong, one of the following:
+ <simplelist type="horiz" columns="4">
+ <member><jbophrase role="dipthong">ai</jbophrase></member>
+ <member><jbophrase role="dipthong">ei</jbophrase></member>
+ <member><jbophrase role="dipthong">oi</jbophrase></member>
+ <member><jbophrase role="dipthong">au</jbophrase></member>
+ </simplelist>
+ or a two-syllable vowel pair with an apostrophe separating the vowels, one of the following:
+ <simplelist type="horiz" columns="5">
+ <member><jbophrase>a'a</jbophrase></member>
+ <member><jbophrase>a'e</jbophrase></member>
+ <member><jbophrase>a'i</jbophrase></member>
+ <member><jbophrase>a'o</jbophrase></member>
+ <member><jbophrase>a'u</jbophrase></member>
+ <member><jbophrase>e'a</jbophrase></member>
+ <member><jbophrase>e'e</jbophrase></member>
+ <member><jbophrase>e'i</jbophrase></member>
+ <member><jbophrase>e'o</jbophrase></member>
+ <member><jbophrase>e'u</jbophrase></member>
- <programlisting xml:space="preserve">
- bl br
- cf ck cl cm cn cp cr ct
- dj dr dz
- fl fr
- gl gr
- jb jd jg jm jv
- kl kr
- ml mr
- pl pr
- sf sk sl sm sn sp sr st
- tc tr ts
- vl vr
- xl xr
- zb zd zg zm zv
- </programlisting></para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>5)</term>
- <listitem>
- <para> <indexterm type="general-imported"><primary>C/C string</primary><secondary>as a symbol for a permissible consonant pair</secondary></indexterm> C/C represents two adjacent consonants which constitute one of the permissible consonant pairs (not necessarily a permissible initial consonant pair). The permissible consonant pairs are explained in
+ <member><jbophrase>i'a</jbophrase></member>
+ <member><jbophrase>i'e</jbophrase></member>
+ <member><jbophrase>i'i</jbophrase></member>
+ <member><jbophrase>i'o</jbophrase></member>
+ <member><jbophrase>i'u</jbophrase></member>
- <xref linkend="chapter-phonology"/>. In brief, any consonant pair is permissible unless it: contains two identical letters, contains both a voiced (excluding
- <jbophrase role="letteral">r</jbophrase>,
- <jbophrase role="letteral">l</jbophrase>,
- <jbophrase role="letteral">m</jbophrase>,
- <jbophrase role="letteral">n</jbophrase>) and an unvoiced consonant, or is one of certain specified forbidden pairs.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>6)</term>
- <listitem>
- <para> <indexterm type="general-imported"><primary>C/CC string</primary><secondary>as a symbol for a consonant triple</secondary></indexterm> C/CC represents a consonant triple. The first two consonants must constitute a permissible consonant pair; the last two consonants must constitute a permissible initial consonant pair.</para>
- </listitem>
- </varlistentry>
- </variablelist>
+ <member><jbophrase>o'a</jbophrase></member>
+ <member><jbophrase>o'e</jbophrase></member>
+ <member><jbophrase>o'i</jbophrase></member>
+ <member><jbophrase>o'o</jbophrase></member>
+ <member><jbophrase>o'u</jbophrase></member>
+
+ <member><jbophrase>u'a</jbophrase></member>
+ <member><jbophrase>u'e</jbophrase></member>
+ <member><jbophrase>u'i</jbophrase></member>
+ <member><jbophrase>u'o</jbophrase></member>
+ <member><jbophrase>u'u</jbophrase></member>
+ </simplelist>
+ </para>
+ </listitem>
+ <listitem>
+ <para> <indexterm type="general-imported"><primary>apostrophe</primary><secondary>as not a consonant for morphological discussions</secondary></indexterm> <indexterm type="general-imported"><primary>syllabic r</primary><secondary>as a consonant for morphological discussions</secondary></indexterm> <indexterm type="general-imported"><primary>syllabic n</primary><secondary>as a consonant for morphological discussions</secondary></indexterm> <indexterm type="general-imported"><primary>syllabic m</primary><secondary>as a consonant for morphological discussions</secondary></indexterm> <indexterm type="general-imported"><primary>syllabic l</primary><secondary>considered as a consonant for morphological discussions</secondary></indexterm> <indexterm type="general-imported"><primary>C string</primary><secondary>as a symbol for a single consonant</secondary></indexterm> C represents a single Lojban consonant, not including the apostrophe, one of
+ <simplelist type="inline">
+ <member><jbophrase role="letteral">b</jbophrase></member>
+ <member><jbophrase role="letteral">c</jbophrase></member>
+ <member><jbophrase role="letteral">d</jbophrase></member>
+ <member><jbophrase role="letteral">f</jbophrase></member>
+ <member><jbophrase role="letteral">g</jbophrase></member>
+ <member><jbophrase role="letteral">j</jbophrase></member>
+ <member><jbophrase role="letteral">k</jbophrase></member>
+ <member><jbophrase role="letteral">l</jbophrase></member>
+ <member><jbophrase role="letteral">m</jbophrase></member>
+ <member><jbophrase role="letteral">n</jbophrase></member>
+ <member><jbophrase role="letteral">p</jbophrase></member>
+ <member><jbophrase role="letteral">r</jbophrase></member>
+ <member><jbophrase role="letteral">s</jbophrase></member>
+ <member><jbophrase role="letteral">t</jbophrase></member>
+ <member><jbophrase role="letteral">v</jbophrase></member>
+ <member><jbophrase role="letteral">x</jbophrase></member>
+ or
+ <member><jbophrase role="letteral">z</jbophrase></member>
+ </simplelist>
+ . Syllabic
+ <simplelist type="inline">
+ <member><jbophrase role="letteral">l</jbophrase></member>
+ <member><jbophrase role="letteral">m</jbophrase></member>
+ <member><jbophrase role="letteral">n</jbophrase></member> and
+ <member><jbophrase role="letteral">r</jbophrase></member>
+ </simplelist>
+ always count as consonants for the purposes of this chapter.
+ </para>
+ </listitem>
+ <listitem>
+ <para> <indexterm type="general-imported"><primary>CC string</primary><secondary>as a symbol for a permissible initial consonant pair</secondary></indexterm> CC represents two adjacent consonants of type C which constitute one of the 48 permissible initial consonant pairs:
+ <!-- FIXME: There's a table of the permissible initial pairs in chapter 3, too; however, the pairs are grouped differently in that table. Can we copy that or must we use this specific grouping here? Also, in draft CLL it's not even a table, just a straight inline list. -->
+ <programlisting xml:space="preserve">
+ bl br
+ cf ck cl cm cn cp cr ct
+ dj dr dz
+ fl fr
+ gl gr
+ jb jd jg jm jv
+ kl kr
+ ml mr
+ pl pr
+ sf sk sl sm sn sp sr st
+ tc tr ts
+ vl vr
+ xl xr
+ zb zd zg zm zv
+ </programlisting></para>
+ </listitem>
+ <listitem>
+ <para> <indexterm type="general-imported"><primary>C/C string</primary><secondary>as a symbol for a permissible consonant pair</secondary></indexterm> C/C represents two adjacent consonants which constitute one of the permissible consonant pairs (not necessarily a permissible initial consonant pair). The permissible consonant pairs are explained in <xref linkend="chapter-phonology"/>. In brief, any consonant pair is permissible unless it: contains two identical letters, contains both a voiced (excluding
+ <simplelist>
+ <member><jbophrase role="letteral">r</jbophrase></member>
+ <member><jbophrase role="letteral">l</jbophrase></member>
+ <member><jbophrase role="letteral">m</jbophrase></member>
+ <member><jbophrase role="letteral">n</jbophrase></member>
+ </simplelist>) and an unvoiced consonant, or is one of certain specified forbidden pairs.
+ </para>
+ </listitem>
+ <listitem>
+ <para> <indexterm type="general-imported"><primary>C/CC string</primary><secondary>as a symbol for a consonant triple</secondary></indexterm> C/CC represents a consonant triple. The first two consonants must constitute a permissible consonant pair; the last two consonants must constitute a permissible initial consonant pair.</para>
+ </listitem>
+ </orderedlist>
<para> <indexterm type="general-imported"><primary>brivla</primary><secondary>as one of the 3 basic word classes</secondary></indexterm> <indexterm type="general-imported"><primary>cmene</primary><secondary>as one of the 3 basic word classes</secondary></indexterm> <indexterm type="general-imported"><primary>cmavo</primary><secondary>as one of the 3 basic word classes</secondary></indexterm> <indexterm type="general-imported"><primary>parts of speech</primary></indexterm> <indexterm type="general-imported"><primary>word classes</primary></indexterm> Lojban has three basic word classes - parts of speech - in contrast to the eight that are traditional in English. These three classes are called cmavo, brivla, and cmene. Each of these classes has uniquely identifying properties - an arrangement of letters that allows the word to be uniquely and unambiguously recognized as a separate word in a string of Lojban, upon either reading or hearing, and as belonging to a specific word-class.</para>
<para>They are also functionally different: cmavo are the structure words, corresponding to English words like
<quote>and</quote>,
<quote>if</quote>,
<quote>the</quote> and
- <jbophrase>to</jbophrase>; brivla are the content words, corresponding to English words like
+ <quote>to</quote>; brivla are the content words, corresponding to English words like
<quote>come</quote>,
<quote>red</quote>,
<quote>doctor</quote>, and
<quote>freely</quote>; cmene are proper names, corresponding to English
<quote>James</quote>,
<quote>Afghanistan</quote>, and
<quote>Pope John Paul II</quote>.</para>
</section>
<section xml:id="section-cmavo">
<title>cmavo</title>
- <para> <indexterm type="general-imported"><primary>punctuation marks</primary><secondary>cmavo as Lojban equivalents</secondary></indexterm> <indexterm type="general-imported"><primary>numbers</primary><secondary>cmavo as Lojban equivalents</secondary></indexterm> <indexterm type="general-imported"><primary>prepositions</primary><secondary>cmavo as Lojban equivalents</secondary></indexterm> <indexterm type="general-imported"><primary>conjunctions</primary><secondary>cmavo as Lojban equivalents</secondary></indexterm> <indexterm type="general-imported"><primary>articles</primary><secondary>cmavo as Lojban equivalents</secondary></indexterm> <indexterm type="general-imported"><primary>structure words</primary></indexterm> <indexterm type="general-imported"><primary>selma'o</primary><secondary>definition</secondary></indexterm> <indexterm type="general-imported"><primary>cmavo</primary><secondary>definition</secondary></indexterm> The first group of Lojban words discussed in this chapter are the cmavo. They are the structure words that hold the Lojban language together. They often have no semantic meaning in themselves, though they may affect the semantics of brivla to which they are attached. The cmavo include the equivalent of English articles, conjunctions, prepositions, numbers, and punctuation marks. There are over a hundred subcategories of cmavo, known as
-
-
-
-
-
-
- <jbophrase>selma'o</jbophrase>, each having a specifically defined grammatical usage. The various selma'o are discussed throughout
+ <para> <indexterm type="general-imported"><primary>punctuation marks</primary><secondary>cmavo as Lojban equivalents</secondary></indexterm> <indexterm type="general-imported"><primary>numbers</primary><secondary>cmavo as Lojban equivalents</secondary></indexterm> <indexterm type="general-imported"><primary>prepositions</primary><secondary>cmavo as Lojban equivalents</secondary></indexterm> <indexterm type="general-imported"><primary>conjunctions</primary><secondary>cmavo as Lojban equivalents</secondary></indexterm> <indexterm type="general-imported"><primary>articles</primary><secondary>cmavo as Lojban equivalents</secondary></indexterm> <indexterm type="general-imported"><primary>structure words</primary></indexterm> <indexterm type="general-imported"><primary>selma'o</primary><secondary>definition</secondary></indexterm> <indexterm type="general-imported"><primary>cmavo</primary><secondary>definition</secondary></indexterm> The first group of Lojban words discussed in this chapter are the cmavo. They are the structure words that hold the Lojban language together. They often have no semantic meaning in themselves, though they may affect the semantics of brivla to which they are attached. The cmavo include the equivalent of English articles, conjunctions, prepositions, numbers, and punctuation marks. There are over a hundred subcategories of cmavo, known as <jbophrase>selma'o</jbophrase>, each having a specifically defined grammatical usage. The various selma'o are discussed throughout
<xref linkend="chapter-selbri"/> to
<xref linkend="chapter-structure"/> and summarized in
<xref linkend="chapter-catalogue"/>.</para>
<para> <indexterm type="general-imported"><primary>cmavo</primary><secondary>structure of</secondary></indexterm> Standard cmavo occur in four forms defined by their word structure. Here are some examples of the various forms:</para>
- <cmavo-list>
- <cmavo-entry>
- <cmavo>V-form .a .e .i</cmavo>
- <selmaho>.o</selmaho>
- <description>.u</description>
- </cmavo-entry>
- <cmavo-entry>
- <cmavo>CV-form ba ce di</cmavo>
- <selmaho>fo</selmaho>
- <description>gu</description>
- </cmavo-entry>
- <cmavo-entry>
- <cmavo>VV-form .au .ei</cmavo>
- <selmaho>.ia</selmaho>
- <description>.o'u .u'e</description>
-
- </cmavo-entry>
- <cmavo-entry>
- <cmavo>CVV-form ki'a pei mi'o</cmavo>
- <selmaho>coi</selmaho>
- <description>cu'u</description>
-
- </cmavo-entry>
- </cmavo-list>
+ <informaltable>
+ <tgroup cols="6">
+ <colspec colnum="1" colname="col1"/>
+ <colspec colnum="2" colname="col2"/>
+ <colspec colnum="3" colname="col3"/>
+ <colspec colnum="4" colname="col4"/>
+ <colspec colnum="5" colname="col5"/>
+ <colspec colnum="6" colname="col6"/>
+ <tbody>
+ <row>
+ <entry>V-form</entry>
+ <entry><jbophrase>.a</jbophrase></entry>
+ <entry><jbophrase>.e</jbophrase></entry>
+ <entry><jbophrase>.i</jbophrase></entry>
+ <entry><jbophrase>.o</jbophrase></entry>
+ <entry><jbophrase>.u</jbophrase></entry>
+ </row>
+ <row>
+ <entry>CV-form</entry>
+ <entry><jbophrase>ba</jbophrase></entry>
+ <entry><jbophrase>ce</jbophrase></entry>
+ <entry><jbophrase>di</jbophrase></entry>
+ <entry><jbophrase>fo</jbophrase></entry>
+ <entry><jbophrase>gu</jbophrase></entry>
+ </row>
+ <row>
+ <entry>VV-form</entry>
+ <entry><jbophrase>.au</jbophrase></entry>
+ <entry><jbophrase>.ei</jbophrase></entry>
+ <entry><jbophrase>.ia</jbophrase></entry>
+ <entry><jbophrase>.o'u</jbophrase></entry>
+ <entry><jbophrase>.u'e</jbophrase></entry>
+ </row>
+ <row>
+ <entry>CVV-form</entry>
+ <entry><jbophrase>ki'a</jbophrase></entry>
+ <entry><jbophrase>pei</jbophrase></entry>
+ <entry><jbophrase>mi'o</jbophrase></entry>
+ <entry><jbophrase>coi</jbophrase></entry>
+ <entry><jbophrase>cu'u</jbophrase></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
<para>In addition, there is the cmavo
<jbophrase>.y.</jbophrase> (remember that
<jbophrase role="letteral">y</jbophrase> is not a V), which must have pauses before and after it.</para>
<para> <indexterm type="general-imported"><primary>cmavo</primary><secondary>lack of relation of form to grammatical use</secondary></indexterm> <indexterm type="general-imported"><primary>experimental cmavo</primary><secondary>forms for</secondary></indexterm> <indexterm type="general-imported"><primary>cmavo</primary><secondary>for experimental use</secondary></indexterm> <indexterm type="general-imported"><primary>cmavo</primary><secondary>simple</secondary></indexterm> A simple cmavo thus has the property of having only one or two vowels, or of having a single consonant followed by one or two vowels. Words consisting of three or more vowels in a row, or a single consonant followed by three or more vowels, are also of cmavo form, but are reserved for experimental use: a few examples are
- <!-- FIXME: is this valid="false"? -->
+ <!-- FIXME: is this valid="false"? probably not, but just checking -->
<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>
@@ -243,85 +245,81 @@
</listitem>
</varlistentry>
<varlistentry>
<term>2)</term>
<listitem>
<para>They end in a vowel.</para>
</listitem>
</varlistentry>
</variablelist>
<para>For example:</para>
- <example xml:id="example-random-id-qiXV" role="interlinear-gloss-example">
+ <example xml:id="example-random-id-qiXV" role="compound-cmavo-example">
<title>
<anchor xml:id="c4e2d1"/>
</title>
- <interlinear-gloss>
+ <compound-cmavo>
<jbo>.iseci'i</jbo>
- <en>.i se ci'i</en>
-
- </interlinear-gloss>
+ <jbo>.i se ci'i</jbo>
+ </compound-cmavo>
</example>
- <example xml:id="example-random-id-qIYK" role="interlinear-gloss-example">
+ <example xml:id="example-random-id-qIYK" role="compound-cmavo-example">
<title>
<anchor xml:id="c4e2d2"/>
</title>
- <interlinear-gloss>
+ <compound-cmavo>
<jbo>punaijecanai</jbo>
- <en>pu nai je ca nai</en>
- </interlinear-gloss>
+ <jbo>pu nai je ca nai</jbo>
+ </compound-cmavo>
</example>
- <example xml:id="example-random-id-qiz6" role="interlinear-gloss-example">
+ <example xml:id="example-random-id-qiz6" role="compound-cmavo-example">
<title>
<anchor xml:id="c4e2d3"/>
</title>
- <interlinear-gloss>
+ <compound-cmavo>
<jbo>ki'e.u'e</jbo>
-
- <en>ki'e .u'e</en>
-
- </interlinear-gloss>
+ <jbo>ki'e .u'e</jbo>
+ </compound-cmavo>
</example>
<para> <indexterm type="general-imported"><primary>pauses</primary><secondary>before vowels</secondary></indexterm> The cmavo
<jbophrase>.u'e</jbophrase> begins with a vowel, and like all words beginning with a vowel, requires a pause (represented by
- <jbophrase>.</jbophrase>) before it. This pause cannot be omitted simply because the cmavo is incorporated into a compound cmavo. On the other hand,</para>
+ <jbophrase role="letteral">.</jbophrase>) before it. This pause cannot be omitted simply because the cmavo is incorporated into a compound cmavo. On the other hand,</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-FDhH">
<title>
<anchor xml:id="c4e2d4"/>
</title>
<interlinear-gloss>
<jbo>ki'e'u'e</jbo>
</interlinear-gloss>
</example>
<para>is a single cmavo reserved for experimental purposes: it has four vowels.</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-CtnR">
+ <example role="compound-cmavo-example" xml:id="example-random-id-CtnR">
<title>
<anchor xml:id="c4e2d5"/>
</title>
<interlinear-gloss>
<jbo>cy.ibu.abu</jbo>
- <en>cy. .ibu .abu</en>
+ <jbo>cy. .ibu .abu</jbo>
</interlinear-gloss>
</example>
<para>Again the pauses are required (see
<xref linkend="section-pauses"/>); the pause after
<jbophrase>cy.</jbophrase> merges with the pause before
<jbophrase>.ibu</jbophrase>.</para>
<para> <indexterm type="general-imported"><primary>stress</primary><secondary>on cmavo</secondary></indexterm> <indexterm type="general-imported"><primary>cmavo</primary><secondary>stress on</secondary></indexterm> There is no particular stress required in cmavo or their compounds. Some conventions do exist that are not mandatory. For two-syllable cmavo, for example, stress is typically placed on the first vowel; an example is</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-pdGY">
+ <example role="pronunciation-example" xml:id="example-random-id-pdGY">
<title>
<anchor xml:id="c4e2d6"/>
</title>
<interlinear-gloss>
<jbo>.e'o ko ko kurji</jbo>
-
- <en>.E'o ko ko KURji</en>
+ <jbo role="pronunciation">.E'o ko ko KURji</jbo>
</interlinear-gloss>
</example>
<para>This convention results in a consistent rhythm to the language, since brivla are required to have penultimate stress; some find this esthetically pleasing.</para>
<para> <indexterm type="general-imported"><primary>pause</primary><secondary>requirement between stressed syllables</secondary></indexterm> If the final syllable of one word is stressed, and the first syllable of the next word is stressed, you must insert a pause or glottal stop between the two stressed syllables. Thus</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-uqDz">
<title>
<anchor xml:id="c4e2d7"/>
</title>
<interlinear-gloss>
@@ -352,26 +350,26 @@
<jbo>LE re NANmu</jbo>
</interlinear-gloss>
</example>
<para>is also valid; this would apply secondary stress (used for purposes of emphasis, contrast or sentence rhythm) to
<jbophrase>le</jbophrase>, comparable in rhythmical effect to the English phrase
<quote>THE two men</quote>. In
<xref linkend="example-random-id-dfzc"/>, the secondary stress on
<jbophrase>re</jbophrase> would be similar to that in the English phrase
<quote>the TWO men</quote>.</para>
<para>Both cmavo may also be left unstressed, thus:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-sg0p">
+ <example role="pronunciation-example" xml:id="example-random-id-sg0p">
<title>
<anchor xml:id="c4e2d10"/>
</title>
<interlinear-gloss>
- <jbo>le re NANmu</jbo>
+ <jbo role="pronunciation">le re NANmu</jbo>
</interlinear-gloss>
</example>
<para>This would probably be the most common usage.</para>
</section>
<section xml:id="section-brivla">
<title>brivla</title>
<para> <indexterm type="general-imported"><primary>adverbs</primary><secondary>brivla as Lojban equivalents</secondary></indexterm> <indexterm type="general-imported"><primary>verbs</primary><secondary>brivla as Lojban equivalents</secondary></indexterm> <indexterm type="general-imported"><primary>adjectives</primary><secondary>brivla as Lojban equivalents</secondary></indexterm> <indexterm type="general-imported"><primary>nouns</primary><secondary>brivla as Lojban equivalents</secondary></indexterm> <indexterm type="general-imported"><primary>brivla</primary><secondary>definition</secondary></indexterm> Predicate words, called
<jbophrase>brivla</jbophrase>, are at the core of Lojban. They carry most of the semantic information in the language. They serve as the equivalent of English nouns, verbs, adjectives, and adverbs, all in a single part of speech.</para>
@@ -1016,32 +1014,32 @@
<jbophrase>zuljma</jbophrase> are all legitimate and equivalent forms made from the tanru
<jbophrase>zunle jamfu</jbophrase> (
<quote>left foot</quote>). Of these,
<jbophrase>zuljma</jbophrase> is the preferred one since it is the shortest; it thus is likely to be the form listed in a Lojban dictionary.</para>
<para> <indexterm type="general-imported"><primary>lujvo form</primary><secondary>requirements for n-hyphen insertion in</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo form</primary><secondary>requirements for r-hyphen insertion in</secondary></indexterm> <indexterm type="general-imported"><primary>r-hyphen</primary><secondary>use of</secondary></indexterm> The
<jbophrase role="letteral">r</jbophrase>-hyphen and its close relative, the
<jbophrase role="letteral">n</jbophrase>-hyphen, are used in lujvo only after CVV-form rafsi. A hyphen is always required in a two-part lujvo of the form CVV-CVV, since otherwise there would be no consonant cluster.</para>
<para>An
<jbophrase role="letteral">r</jbophrase>- hyphen or
<jbophrase role="letteral">n</jbophrase>-hyphen is also required after the CVV-form rafsi of any lujvo of the form CVV-CVC/CV or CVV-CCVCV since it would otherwise fall apart into a CVV-form cmavo and a gismu. In any lujvo with more than two parts, a CVV-form rafsi in the initial position must always be followed by a hyphen. If the hyphen were to be omitted, the supposed lujvo could be broken into smaller words without the hyphen: because the CVV-form rafsi would be interpreted as a cmavo, and the remainder of the word as a valid lujvo that is one rafsi shorter.</para>
- <para> <indexterm type="general-imported"><primary>r-hyphen</primary><secondary>contrasted with "n"-hyphen in requirements for use</secondary></indexterm> <indexterm type="general-imported"><primary>n-hyphen</primary><secondary>contrasted with "r"-hyphen in requirements for use</secondary></indexterm> <indexterm type="general-imported"><primary>n-hyphen</primary><secondary>use of</secondary></indexterm> An
+ <para> <indexterm type="general-imported"><primary>r-hyphen</primary><secondary>contrasted with <jbophrase role="letteral">n</jbophrase>-hyphen in requirements for use</secondary></indexterm> <indexterm type="general-imported"><primary>n-hyphen</primary><secondary>contrasted with <jbophrase role="letteral">r</jbophrase>-hyphen in requirements for use</secondary></indexterm> <indexterm type="general-imported"><primary>n-hyphen</primary><secondary>use of</secondary></indexterm> An
<jbophrase role="letteral">n</jbophrase>-hyphen is only used in place of an
<jbophrase role="letteral">r</jbophrase>-hyphen when the following rafsi begins with
<jbophrase role="letteral">r</jbophrase>. For example, the tanru
<jbophrase>rokci renro</jbophrase> (
<quote>rock throw</quote>) cannot be expressed as
<jbophrase valid="false">ro'ire'o</jbophrase> (which breaks up into two cmavo), nor can it be
<jbophrase valid="false">ro'irre'o</jbophrase> (which has an impermissible double consonant); the
<jbophrase role="letteral">n</jbophrase>-hyphen is required, and the correct form of the hyphenated lujvo is
<jbophrase>ro'inre'o</jbophrase>. The same lujvo could also be expressed without hyphenation as
<jbophrase>rokre'o</jbophrase>.</para>
- <para> <indexterm type="lojban-word-imported"><primary>ZEI selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>zei</primary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>with zei</secondary></indexterm> There is also a different way of building lujvo, or rather phrases which are grammatically and semantically equivalent to lujvo. You can make a phrase containing any desired words, joining each pair of them with the special cmavo
+ <para><!-- FIXME: what to do with this indexterm? --><indexterm type="lojban-word-imported"><primary>ZEI selma'o</primary></indexterm><indexterm type="general-imported"><primary>lujvo</primary><secondary>with zei</secondary></indexterm> There is also a different way of building lujvo, or rather phrases which are grammatically and semantically equivalent to lujvo. You can make a phrase containing any desired words, joining each pair of them with the special cmavo
<jbophrase>zei</jbophrase>. Thus,</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-VeGL">
<title>
<anchor xml:id="c4e6d12"/>
</title>
<interlinear-gloss>
<jbo>bridi zei valsi</jbo>
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>cmavo without rafsi</primary><secondary>method of including in lujvo</secondary></indexterm> <indexterm type="general-imported"><primary>fu'ivla</primary><secondary>method of including in lujvo</secondary></indexterm> <indexterm type="general-imported"><primary>cmene</primary><secondary>method of including in lujvo</secondary></indexterm> <indexterm type="general-imported"><primary>rafsi</primary><secondary>lack of</secondary><tertiary>effect on forming lujvo</tertiary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>from cmavo with no rafsi</secondary></indexterm> is the exact equivalent of
@@ -1061,68 +1059,58 @@
<example xml:id="example-random-id-qJeE" role="interlinear-gloss-example">
<title>
<indexterm type="example-imported"><primary>Persian rug</primary><secondary>example</secondary></indexterm>
<indexterm type="example-imported"><primary>rug</primary><secondary>Persian</secondary><tertiary>example</tertiary></indexterm>
<anchor xml:id="c4e6d14"/>
</title>
<interlinear-gloss>
<jbo>kulnr,farsi zei lolgai</jbo>
<gloss>Farsi floor-cover</gloss>
<en>Persian rug</en>
-
-
-
-
</interlinear-gloss>
</example>
<example xml:id="example-random-id-qJef" role="interlinear-gloss-example">
<title>
<indexterm type="example-imported"><primary>hepatitis</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c4e6d15"/>
</title>
<interlinear-gloss>
<jbo>na'e zei .a zei na'e zei by. livgyterbilma</jbo>
<gloss>non-A, non-B liver-disease</gloss>
<en>non-A, non-B hepatitis</en>
-
</interlinear-gloss>
</example>
<example xml:id="example-random-id-qJEh" role="interlinear-gloss-example">
<title>
<indexterm type="example-imported"><primary>Sherman tank</primary><secondary>example</secondary></indexterm>
<indexterm type="example-imported"><primary>tank</primary><secondary>Sherman</secondary><tertiary>example</tertiary></indexterm>
<anchor xml:id="c4e6d16"/>
</title>
<interlinear-gloss>
<jbo>.cerman. zei jamkarce</jbo>
<gloss>Sherman war-car</gloss>
<en>Sherman tank</en>
-
-
-
-
</interlinear-gloss>
</example>
<para><xref linkend="example-random-id-qJef"/> is particularly noteworthy because the phrase that would be produced by removing the
<jbophrase>zei</jbophrase> s from it doesn't end with a brivla, and in fact is not even grammatical. As written, the example is a tanru with two components, but by adding a
<jbophrase>zei</jbophrase> between
<jbophrase>by.</jbophrase> and
<jbophrase>livgyterbilma</jbophrase> to produce</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-Wnaz">
<title>
<indexterm type="example-imported"><primary>hepatitis</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c4e6d17"/>
</title>
<interlinear-gloss>
<jbo>na'e zei .a zei na'e zei by. zei livgyterbilma</jbo>
<en>non-A-non-B-hepatitis</en>
-
</interlinear-gloss>
</example>
<para>the whole phrase would become a single lujvo. The longer lujvo of
<xref linkend="example-random-id-Wnaz"/> may be preferable, because its place structure can be built from that of
<jbophrase>bilma</jbophrase>, whereas the place structure of a lujvo without a brivla must be constructed ad hoc.</para>
<para> <indexterm type="general-imported"><primary>cmavo</primary><secondary>contrasted with rafsi in usage</secondary></indexterm> <indexterm type="general-imported"><primary>rafsi</primary><secondary>contrasted with cmavo in usage</secondary></indexterm> <indexterm type="general-imported"><primary>rafsi</primary><secondary>contrasted with words</secondary></indexterm> Note that rafsi may not be used in
<jbophrase>zei</jbophrase> phrases, because they are not words. CVV rafsi look like words (specifically cmavo) but there can be no confusion between the two uses of the same letters, because cmavo appear only as separate words or in compound cmavo (which are really just a notation for writing separate but closely related words as if they were one); rafsi appear only as parts of lujvo.</para>
</section>
<section xml:id="section-fuhivla">
<title>fu'ivla</title>
@@ -1133,21 +1121,21 @@
<quote>cobra</quote>), or for jargon words specialized to a narrow field (e.g.
<quote>quark</quote>,
<quote>integral</quote>, or
<quote>iambic pentameter</quote>). These words are in effect names for concepts, and the names were invented by speakers of another language. The vast majority of words referring to plants, animals, foods, and scientific terminology cannot be easily expressed as tanru. They thus must be borrowed (actually
<quote>copied</quote>) into Lojban from the original language.</para>
- <para> <indexterm type="lojban-word-imported"><primary>la'o</primary></indexterm> <indexterm type="general-imported"><primary>borrowings</primary><secondary>Stage 1</secondary></indexterm> <indexterm type="general-imported"><primary>borrowings</primary><secondary>using foreign-language name</secondary></indexterm> <indexterm type="general-imported"><primary>borrowing</primary><secondary>four stages of</secondary></indexterm> There are four stages of borrowing in Lojban, as words become more and more modified (but shorter and easier to use). Stage 1 is the use of a foreign name quoted with the cmavo
+ <para><indexterm type="general-imported"><primary>borrowings</primary><secondary>Stage 1</secondary></indexterm> <indexterm type="general-imported"><primary>borrowings</primary><secondary>using foreign-language name</secondary></indexterm> <indexterm type="general-imported"><primary>borrowing</primary><secondary>four stages of</secondary></indexterm> There are four stages of borrowing in Lojban, as words become more and more modified (but shorter and easier to use). Stage 1 is the use of a foreign name quoted with the cmavo
<jbophrase>la'o</jbophrase> (explained in full in
<xref linkend="chapter-structure"/>):</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-QpNm">
<title>
<anchor xml:id="c4e7d1"/>
</title>
<interlinear-gloss>
<jbo>me la'o ly. spaghetti .ly.</jbo>
@@ -1239,42 +1227,42 @@
</listitem>
</orderedlist>
<para> In this section, the hyphen is set off with commas in the examples, but these commas are not required in writing, and the hyphen need not be pronounced as a separate syllable.</para>
<para>Here are a few examples:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-ufin">
<title>
<indexterm type="example-imported"><primary>spaghetti</primary><secondary>example</secondary></indexterm>
<indexterm type="example-imported"><primary>syllabic pronunciations of consonants</primary><secondary>in fu'ivla category attachment</secondary><tertiary>example</tertiary></indexterm> <!-- FIXME: this indexterm fits with five different examples; should it go in all five or just the first? -->
<anchor xml:id="c4e7d3"/>
</title>
- <interlinear-gloss>
+ <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>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>
- <interlinear-gloss>
+ <interlinear-gloss> <!-- FIXME: should the commentary sit inside the jbo/gloss/en or outside in para? -->
<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
@@ -1387,62 +1375,62 @@
<jbophrase>dinju</jbophrase> and
<jbophrase>tarmi</jbophrase> mean
<quote>building</quote> and
<quote>form</quote> respectively.</para>
<para>Here are some fu'ivla representing cultures and related things, shown with more than one rafsi prefix:</para>
<example xml:id="example-random-id-qJG8" role="interlinear-gloss-example">
<title>
<anchor xml:id="c4e7d9"/>
</title>
<interlinear-gloss>
- <jbo>bang,r,blgaria</jbo>
+ <jbo role="pronunciation">bang,r,blgaria</jbo>
<en>Bulgarian (in language)</en>
</interlinear-gloss>
</example>
<example xml:id="example-random-id-qJga" role="interlinear-gloss-example">
<title>
<anchor xml:id="c4e7d10"/>
</title>
<interlinear-gloss>
- <jbo>kuln,r,blgaria</jbo>
+ <jbo role="pronunciation">kuln,r,blgaria</jbo>
<en>Bulgarian (in culture)</en>
</interlinear-gloss>
</example>
<example xml:id="example-random-id-qjGf" role="interlinear-gloss-example">
<title>
<indexterm type="example-imported"><primary>Bulgarian</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c4e7d11"/>
</title>
<interlinear-gloss>
- <jbo>gugd,r,blgaria</jbo>
+ <jbo role="pronunciation">gugd,r,blgaria</jbo>
<en>Bulgaria (the country)</en>
</interlinear-gloss>
</example>
<example xml:id="example-random-id-qJGv" role="interlinear-gloss-example">
<title>
<anchor xml:id="c4e7d12"/>
</title>
<interlinear-gloss>
- <jbo>bang,r,kore,a</jbo>
+ <jbo role="pronunciation">bang,r,kore,a</jbo>
<en>Korean (the language)</en>
</interlinear-gloss>
</example>
<example xml:id="example-random-id-qjh0" role="interlinear-gloss-example">
<title>
<indexterm type="example-imported"><primary>Korean</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c4e7d13"/>
</title>
<interlinear-gloss>
- <jbo>kuln,r,kore,a</jbo>
+ <jbo role="pronunciation">kuln,r,kore,a</jbo>
<en>Korean (the culture)</en>
</interlinear-gloss>
</example>
<para><!-- FIXME: there's nowhere for this indexterm to go --><indexterm type="example-imported"><primary>Navajo</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>fu'ivla</primary><secondary>considerations for choosing basis word</secondary></indexterm> <indexterm type="general-imported"><primary>fu'ivla</primary><secondary>with invalid diphthongs</secondary></indexterm> <indexterm type="general-imported"><primary>invalid diphthongs</primary><secondary>in fu'ivla</secondary></indexterm> Note the commas in
<xref linkend="example-random-id-qJGv"/> and
<xref linkend="example-random-id-qjh0"/>, used because
<jbophrase role="diphthong" valid="false">ea</jbophrase> is not a valid diphthong in Lojban. Arguably, some form of the native name
<quote>Chosen</quote> should have been used instead of the internationally known
<quote>Korea</quote>; this is a recurring problem in all borrowings. In general, it is better to use the native name unless using it will severely impede understanding:
@@ -1561,21 +1549,21 @@
<interlinear-gloss>
<jbo>djan. djonz.</jbo>
</interlinear-gloss>
</example>
<para> and</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-QnyL">
<title>
<anchor xml:id="c4e8d10"/>
</title>
<interlinear-gloss>
- <jbo>djandjonz.</jbo>
+ <jbo>djandjonz.</jbo> <!-- FIXME: "ndj" not an allowed cluster (jcowan-approved) -->
</interlinear-gloss>
</example>
<para>are both valid Lojbanizations of
<quote>John Jones</quote>.</para>
<para> <indexterm type="general-imported"><primary>names</primary><secondary>authority for</secondary></indexterm> <indexterm type="general-imported"><primary>cmene</primary><secondary>authority for</secondary></indexterm> The final arbiter of the correct form of a name is the person doing the naming, although most cultures grant people the right to determine how they want their own name to be spelled and pronounced. The English name
<quote>Mary</quote> can thus be Lojbanized as
<jbophrase>meris.</jbophrase>,
<jbophrase>maris.</jbophrase>,
<jbophrase>meiris.</jbophrase>,
@@ -1585,92 +1573,92 @@
<para> <indexterm type="general-imported"><primary>names</primary><secondary>restrictions on form of</secondary></indexterm> <indexterm type="general-imported"><primary>cmene</primary><secondary>restrictions on form of</secondary></indexterm> Names are not permitted to have the sequences
<jbophrase>la</jbophrase>,
<jbophrase>lai</jbophrase>, or
<jbophrase>doi</jbophrase> embedded in them, unless the sequence is immediately preceded by a consonant. These minor restrictions are due to the fact that all Lojban cmene embedded in a speech stream will be preceded by one of these words or by a pause. With one of these words embedded, the cmene might break up into valid Lojban words followed by a shorter cmene. However, break-up cannot happen after a consonant, because that would imply that the word before the
<jbophrase>la</jbophrase>, or whatever, ended in a consonant without pause, which is impossible.</para>
<para> <!-- FIXME: there's nowhere for these two indexterms to go --><indexterm type="example-imported"><primary>Nederlands</primary><secondary>example</secondary></indexterm> <indexterm type="example-imported"><primary>Laplace</primary><secondary>example</secondary></indexterm> For example, the invalid name
<jbophrase>laplas.</jbophrase> would look like the Lojban words
<jbophrase>la plas.</jbophrase>, and
<jbophrase>ilanas.</jbophrase> would be misunderstood as
<jbophrase>.i la nas.</jbophrase>. However,
- <jbophrase role="pronuncation">NEderlants.</jbophrase> cannot be misheard as
- <jbophrase role="pronuncation">NEder lants.</jbophrase>, because
- <jbophrase role="pronuncation">NEder</jbophrase> with no following pause is not a possible Lojban word.</para>
+ <jbophrase role="pronunciation">NEderlants.</jbophrase> cannot be misheard as
+ <jbophrase role="pronunciation">NEder lants.</jbophrase>, because
+ <jbophrase role="pronunciation">NEder</jbophrase> with no following pause is not a possible Lojban word.</para>
<para> <indexterm type="general-imported"><primary>names</primary><secondary>alternatives for restricted sequences in</secondary></indexterm> <indexterm type="general-imported"><primary>cmene</primary><secondary>alternatives for restricted sequences in</secondary></indexterm> There are close alternatives to these forbidden sequences that can be used in Lojbanizing names, such as
<jbophrase>ly</jbophrase>,
<jbophrase>lei</jbophrase>, and
<jbophrase>dai</jbophrase> or
<jbophrase>do'i</jbophrase>, that do not cause these problems.</para>
<para> <indexterm type="general-imported"><primary>cmene</primary><secondary>rules for</secondary></indexterm> <indexterm type="general-imported"><primary>names</primary><secondary>rules for</secondary></indexterm> Lojban cmene are identifiable as word forms by the following characteristics:</para>
<orderedlist>
<listitem>
<para> <indexterm type="general-imported"><primary>cmene</primary><secondary>consonant clusters permitted in</secondary></indexterm> <indexterm type="general-imported"><primary>cmene</primary><secondary>final letter in</secondary></indexterm> They must end in one or more consonants. There are no rules about how many consonants may appear in a cluster in cmene, provided that each consonant pair (whether standing by itself, or as part of a larger cluster) is a permissible pair.</para>
</listitem>
<listitem>
<para> <indexterm type="general-imported"><primary>diphthongs</primary><secondary>specific to cmene</secondary></indexterm> <indexterm type="general-imported"><primary>diphthongs</primary><secondary>specific to names</secondary></indexterm> <indexterm type="general-imported"><primary>uy diphthong</primary><secondary>in cmene</secondary></indexterm> <indexterm type="general-imported"><primary>iy diphthong</primary><secondary>in cmene</secondary></indexterm> They may contain the letter y as a normal, non-hyphenating vowel. They are the only kind of Lojban word that may contain the two diphthongs
<jbophrase role="diphthong">iy</jbophrase> and
<jbophrase role="diphthong">uy</jbophrase>.</para>
</listitem>
<listitem>
<para> <indexterm type="general-imported"><primary>names</primary><secondary>requirement for pause after</secondary></indexterm> <indexterm type="general-imported"><primary>cmene</primary><secondary>requirement for pause after</secondary></indexterm> They are always followed in speech by a pause after the final consonant, written as
- <jbophrase>.</jbophrase>.</para>
+ <jbophrase role="letteral">.</jbophrase>.</para>
</listitem>
<listitem>
<para> <indexterm type="general-imported"><primary>capitalization</primary><secondary>use of</secondary></indexterm> <indexterm type="general-imported"><primary>capitalization</primary><secondary>for unusual stress in names</secondary></indexterm> <indexterm type="general-imported"><primary>capitalization</primary><secondary>use in names</secondary></indexterm> <indexterm type="general-imported"><primary>names</primary><secondary>stress in</secondary></indexterm> <indexterm type="general-imported"><primary>cmene</primary><secondary>stress in</secondary></indexterm> They may be stressed on any syllable; if this syllable is not the penultimate one, it must be capitalized when writing. Neither names nor words that begin sentences are capitalized in Lojban, so this is the only use of capital letters.</para>
</listitem>
</orderedlist>
<para> <indexterm type="general-imported"><primary>names</primary><secondary>from Lojban words</secondary></indexterm> <indexterm type="general-imported"><primary>cmene</primary><secondary>from Lojban words</secondary></indexterm> Names meeting these criteria may be invented, Lojbanized from names in other languages, or formed by appending a consonant onto a cmavo, a gismu, a fu'ivla or a lujvo. Some cmene built from Lojban words are:</para>
<example xml:id="example-random-id-qjj1" role="interlinear-gloss-example">
<title>
<indexterm type="example-imported"><primary>One</primary><secondary>the</secondary><tertiary>example</tertiary></indexterm>
<anchor xml:id="c4e8d11"/>
</title>
<interlinear-gloss>
<jbo>pav.</jbo>
- <gloss>the One</gloss>
+ <en>the One</en>
</interlinear-gloss>
</example>
<para>from the cmavo <jbophrase>pa</jbophrase>, with rafsi <jbophrase role="rafsi">pav</jbophrase>, meaning <quote>one</quote></para>
<example xml:id="example-random-id-qjjN" role="interlinear-gloss-example">
<title>
<indexterm type="example-imported"><primary>Sun</primary><secondary>the</secondary><tertiary>example</tertiary></indexterm>
<anchor xml:id="c4e8d12"/>
</title>
<interlinear-gloss>
<jbo>sol.</jbo>
- <gloss>the Sun</gloss>
+ <en>the Sun</en>
</interlinear-gloss>
</example>
<para>from the gismu <jbophrase>solri</jbophrase>, meaning <quote>solar</quote>, or actually <quote>pertaining to the Sun</quote></para>
<example xml:id="example-random-id-qjJz" role="interlinear-gloss-example">
<title>
<indexterm type="example-imported"><primary>Chief</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c4e8d13"/>
</title>
<interlinear-gloss>
<jbo>ralj.</jbo>
- <gloss>Chief (as a title)</gloss>
+ <en>Chief (as a title)</en>
</interlinear-gloss>
</example>
<para>from the gismu <jbophrase>ralju</jbophrase>, meaning <quote>principal</quote>.</para>
<example xml:id="example-random-id-qJKt" role="interlinear-gloss-example">
<title>
<indexterm type="example-imported"><primary>Lord</primary><secondary>example</secondary></indexterm>
<indexterm type="example-imported"><primary>Lady</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c4e8d14"/>
</title>
<interlinear-gloss>
<jbo>nol.</jbo>
- <gloss>Lord/Lady</gloss>
+ <en>Lord/Lady</en>
</interlinear-gloss>
</example>
<para>from the gismu <jbophrase>nobli</jbophrase>, with rafsi <jbophrase role="rafsi">nol</jbophrase>, meaning <quote>noble</quote>.</para>
<para><indexterm type="general-imported"><primary>cmene</primary><secondary>algorithm for</secondary></indexterm> <indexterm type="general-imported"><primary>names</primary><secondary>algorithm for</secondary></indexterm> To Lojbanize a name from the various natural languages, apply the following rules:</para>
<orderedlist>
<listitem>
<para>Eliminate double consonants and silent letters.</para>
</listitem>
<listitem>
<para>Add a final
@@ -1874,42 +1862,42 @@
<jbophrase>la</jbophrase>,
<jbophrase>lai</jbophrase>,
<jbophrase>la'i</jbophrase>, or
<jbophrase>doi</jbophrase> (which is why those strings are forbidden in cmene). However, the situation triggering this rule rarely occurs.</para>
</listitem>
<listitem>
<para> <indexterm type="general-imported"><primary>pause</primary><secondary>and final-syllable stress</secondary></indexterm> <indexterm type="general-imported"><primary>final syllable stress</primary><secondary>rules for pause after</secondary></indexterm> <indexterm type="general-imported"><primary>stress</primary><secondary>final syllable</secondary><tertiary>rules for pause after</tertiary></indexterm> If the last syllable of a word bears the stress, and a brivla follows, the two must be separated by a pause, to prevent confusion with the primary stress of the brivla. In this case, the first word must be either a cmavo or a cmene with unusual stress (which already ends with a pause, of course).</para>
</listitem>
<listitem>
<para> <indexterm type="general-imported"><primary>pause</primary><secondary>and Cy-form cmavo</secondary></indexterm> <indexterm type="general-imported"><primary>cmavo</primary><secondary>rules for pause after Cy-form</secondary></indexterm> <indexterm type="general-imported"><primary>Cy-form cmavo</primary><secondary>rules for pause after</secondary></indexterm> A cmavo of the form
- <jbophrase role="morphology">Cy</jbophrase> must be followed by a pause unless another
- <jbophrase role="morphology">Cy</jbophrase>-form cmavo follows.</para>
+ <quote>Cy</quote> must be followed by a pause unless another
+ <quote>Cy</quote>-form cmavo follows.</para>
</listitem>
<listitem>
<para> <indexterm type="general-imported"><primary>non-Lojban text</primary><secondary>rules for pause with</secondary></indexterm> <indexterm type="general-imported"><primary>pause</primary><secondary>and non-Lojban text</secondary></indexterm> When non-Lojban text is embedded in Lojban, it must be preceded and followed by pauses. (How to embed non-Lojban text is explained in
<xref linkend="chapter-structure"/>.)</para>
</listitem>
</orderedlist>
</section>
<section xml:id="section-lujvo-considerations">
<title>Considerations for making lujvo</title>
<para>Given a tanru which expresses an idea to be used frequently, it can be turned into a lujvo by following the lujvo-making algorithm which is given in
<xref linkend="section-lujvo-making"/>.</para>
<para>In building a lujvo, the first step is to replace each gismu with a rafsi that uniquely represents that gismu. These rafsi are then attached together by fixed rules that allow the resulting compound to be recognized as a single word and to be analyzed in only one way.</para>
<para>There are three other complications; only one is serious.</para>
<para> <indexterm type="general-imported"><primary>rafsi</primary><secondary>multiple for each gismu</secondary></indexterm> The first is that there is usually more than one rafsi that can be used for each gismu. The one to be used is simply whichever one sounds or looks best to the speaker or writer. There are usually many valid combinations of possible rafsi. They all are equally valid, and all of them mean exactly the same thing. (The scoring algorithm given in
<xref linkend="section-lujvo-scoring"/> is used to choose the standard form of the lujvo - the version which would be entered into a dictionary.)</para>
<para> <indexterm type="general-imported"><primary>linguistic drift in Lojban</primary><secondary>possible source of</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>consideration in choosing meaning for</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>unambiguity of</secondary></indexterm> The second complication is the serious one. Remember that a tanru is ambiguous - it has several possible meanings. A lujvo, or at least one that would be put into the dictionary, has just a single meaning. Like a gismu, a lujvo is a predicate which encompasses one area of the semantic universe, with one set of places. Hopefully the meaning chosen is the most useful of the possible semantic spaces. A possible source of linguistic drift in Lojban is that as Lojbanic society evolves, the concept that seems the most useful one may change.</para>
- <para> <indexterm type="lojban-word-imported"><primary>za'e</primary></indexterm> <indexterm type="general-imported"><primary>za'e</primary><secondary>use to avoid lujvo misunderstandings</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>meaning drift of</secondary></indexterm> You must also be aware of the possibility of some prior meaning of a new lujvo, especially if you are writing for posterity. If a lujvo is invented which involves the same tanru as one that is in the dictionary, and is assigned a different meaning (or even just a different place structure), linguistic drift results. This isn't necessarily bad. Every natural language does it. But in communication, when you use a meaning different from the dictionary definition, someone else may use the dictionary and therefore misunderstand you. You can use the cmavo
+ <para><indexterm type="general-imported"><primary>za'e</primary><secondary>use to avoid lujvo misunderstandings</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>meaning drift of</secondary></indexterm> You must also be aware of the possibility of some prior meaning of a new lujvo, especially if you are writing for posterity. If a lujvo is invented which involves the same tanru as one that is in the dictionary, and is assigned a different meaning (or even just a different place structure), linguistic drift results. This isn't necessarily bad. Every natural language does it. But in communication, when you use a meaning different from the dictionary definition, someone else may use the dictionary and therefore misunderstand you. You can use the cmavo
<jbophrase>za'e</jbophrase> (explained in
<xref linkend="chapter-structure"/>) before a newly coined lujvo to indicate that it may have a non-dictionary meaning.</para>
<para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>ultimate guideline for choice of meaning/place-structure</secondary></indexterm> The essential nature of human communication is that if the listener understands, then all is well. Let this be the ultimate guideline for choosing meanings and place structures for invented lujvo.</para>
<para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>dropping elements of</secondary></indexterm> <indexterm type="general-imported"><primary>Zipf's Law</primary></indexterm> The third complication is also simple, but tends to scare new Lojbanists with its implications. It is based on Zipf's Law, which says that the length of words is inversely proportional to their usage. The shortest words are those which are used more; the longest ones are used less. Conversely, commonly used concepts will be tend to be abbreviated. In English, we have abbreviations and acronyms and jargon, all of which represent complex ideas that are used often by small groups of people, so they shortened them to convey more information more rapidly.</para>
<para>Therefore, given a complicated tanru with grouping markers, abstraction markers, and other cmavo in it to make it syntactically unambiguous, the psychological basis of Zipf's Law may compel the lujvo-maker to drop some of the cmavo to make a shorter (technically incorrect) tanru, and then use that tanru to make the lujvo.</para>
diff --git a/todocbook/TODO b/todocbook/TODO
index 2455093..9dd7079 100644
--- a/todocbook/TODO
+++ b/todocbook/TODO
@@ -4,21 +4,21 @@
==================
Most of the below is intended to be done as needed as you review a
particular chapter/section. It looks like more complexity than it
actually is; you'll get used to it.
SAY HERE WHAT YOU'VE DONE, including parts you haven't completed
(like index work).
Robin Powell: 5.1, 5.2, 5.3
-Zort: 3.*, 5.*
+Zort: 3, 5
------
Ignore Chapter 2 for now.
------
If you have any trouble, add a FIXME comment, like so:
<!-- FIXME: detailed explanation here -->
@@ -27,32 +27,32 @@ If you have any trouble, add a FIXME comment, like so:
Fix the chapter name so it's just the second part, i.e.
<title>Chapter 5
<quote>Pretty Little Girls' School</quote>: The Structure Of Lojban selbri</title>
becomes:
<title><quote>Pretty Little Girls' School</quote>: The Structure Of Lojban selbri</title>
-Make sure the <interlinear-gloss> bits look right (which is why the
-columns are so spaced out).
+Make sure the <interlinear-gloss> bits look right in the output (which
+is why the columns are so spaced out).
------
Fix IDs/tags. A command like the following should do the trick:
- sed -i 's/"cll_chapter5"/"chapter-selbri"/g' [0-9]*.xml
+ sed -i 's/"cll_chapter8-section1"/"chapter-relative-clauses-section-poi"/g' [0-9]*.xml
BUT FIRST: check that it doesn't already exist:
- grep '"chapter-selbri"' [0-9]*.xml
+ grep '"chapter-relative-clauses-section-poi"' [0-9]*.xml
because duplicates would really suck.
Please run "git diff" afterwards to make sure it did what you
expected. Check in as often as you like (to make the diffs
manageable).
We want short and meaningful; these are used to make file names and
so on. If multi-word, please make a slug (see
http://en.wikipedia.org/wiki/Slug_%28web_publishing%29 ); we are
@@ -60,20 +60,23 @@ using - based slugs rather than _ based, so drop all special
characters, lowercase, replace space with -.
Make sure that the ids for chapters have "chapter-" at the start,
"section-" for the sections, and "example-" for the examples; we
might need them for auto-processing.
Do this for all sections. Feel free to do it for examples too if an
example has an obvious title, but it's much less important there, so
not worth spending time on for the first pass.
+References to examples should be changed to <xref>s, using the random
+id of the example in question, e.g. <xref linkend="example-random-id-qjmr"/>
+
The important thing here is that *NOTHING* mentions a fixed number!
*NOWHERE* in the docbook should *ANYTHING* be aware that it is in
chapter 20 or section 7 or anything like that. This is to give us
the freedom to move things around later.
Numeric-based stuff will all be autogenerated during processing,
based on the current state of the docs.
THERE IS ONE EXCEPTION: DO NOT change anchors that are one to three
pairs of letters and numbers, like this:
@@ -92,38 +95,45 @@ after their terminators; it doesn't really matter, but it's
annoying.
------
If you see a <quote>...</quote> around Lojban text, replace it with
<jbophrase>...</jbophrase>. There are lots of these.
Also, use <jbophrase valid="false">...</jbophrase> for purposeful na
gendra and <jbophrase valid="iffy">...</jbophrase> for na smudra
-Turn letterals, like <quote>l</quote>, into <jbophrase
-role="letteral">l</jbophrase>
+Turn letters, like <quote>l</quote>, into <jbophrase
+role="letteral">l</jbophrase> (including ",", ".", and "'").
Similarily we have role="morphology" (consonant clusters),
-role="diphthong", and role="rafsi"
+role="diphthong", and role="rafsi".
------
<programlisting> is bad; change it. If you can't figure out how to
change it, or think it's actually correct in some particular place,
post to the BPFK list.
------
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
as the <indexterm> entry. If you can't find such a correspondance,
add a FIXME comment.
------
Entries like <indexterm type="example-imported"> (NOTE the type)
@@ -137,52 +147,61 @@ which are artificial paragraphs solely for index importing.
All such indexterm entries should end up in the example itself, like so:
<title>
<indexterm type="example-imported"><primary>lemon tree</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c5e2d1"/>
</title>
------
-
==================
Data
==================
-- Need some sort of structure for the per-section cmavo lists.
+- The per-section cmavo lists should be like this:
+ <cmavo-list>
+ <cmavo-entry>
+ <cmavo>ke</cmavo>
+ <selmaho>KE</selmaho>
+ <description>start grouping</description>
+ </cmavo-entry>
+ ...
+ </cmavo-list>
- also need to wrap the lojban words there in a way that does
indexing, and ideally auto-generation of the cmavo-per-selmaho
lists we want for chapter 20
+ - does the <cmavo-list> structure achieve this?
+- It seems that there is a problem with the cmavo lists at the
+ beginning of sections having missing entries; in particular, ones
+ wwith + in the selma'o, maybe?; they need to be manually checked
- 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
- <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 na gendra and
- <jbophrase valid="iffy">...</jbophrase> for na smudra
+ - use <jbophrase valid="false">...</jbophrase> for purposely na
+ gendra and <jbophrase valid="iffy">...</jbophrase> for na smudra
- In the mediaobjects in chapter 1, can we do better than <alt>The
picture for chapter 20</alt> in terms of non-numerical cross
referencing?
-- 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
- Replace chapter xrefs with section xrefs
- Fix all FIXMEs; in particular the output of:
grep 'FIXME:' [0-9]*.xml | grep -v 'TAG SPOT'
==================
Display
==================
- links to examples should *say* "example N"; easy to test from the
index
- links to sections should say the number of section and chapter
--
You received this message because you are subscribed to the Google Groups "BPFK" group.
To post to this group, send email to bpfk-list@googlegroups.com.
To unsubscribe from this group, send email to bpfk-list+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/bpfk-list?hl=en.