[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bpfk] dag-cll git updates for Sat Jan 29 21:21:02 EST 2011
commit a67e27b99fe3b87f24a44aab5a1934be2696b664
Merge: 35f5841 15becb2
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date: Sat Jan 29 17:40:54 2011 -0800
Merge commit '15becb2f717ee3100bc7419a18ded1db80a15320' into gh-pages
commit 35f58419ec795bd06fad3012ac4fa4ebb2dffc21
Merge: 4e31f5d 5219c6c
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date: Sat Jan 29 14:49:25 2011 -0800
Merge commit '5219c6c67eb437c0aada0bf5fa46d2e392109f95' into gh-pages
commit 15becb2f717ee3100bc7419a18ded1db80a15320
Author: Eitan Postavsky <eitanp32@gmail.com>
Date: Tue Jan 4 23:48:07 2011 -0500
Chapter 4: tables and examples (invented two example roles).
The first invented role is role="lojbanization-example", for lojbanization of jargon (i.e. fu'ivla making) or names.
The second is role="lujvo-making-example", and it probably only applies to a certain four examples which illustrate the lujvo-making algorithm. Here, <rafsi> encloses the rafsi used to make the lujvo and <score> encloses the equation of the luvjo's score.
diff --git a/todocbook/4.xml b/todocbook/4.xml
index 312a964..18f29f6 100644
--- a/todocbook/4.xml
+++ b/todocbook/4.xml
@@ -770,197 +770,192 @@
<jbophrase>labmau</jbophrase>). On the other hand,
<jbophrase>bakri</jbophrase> (
<quote>chalk</quote>) has no short rafsi and few lujvo.</para>
<para>There are at most one CVC-form, one CCV-form, and one CVV-form rafsi per gismu. In fact, only a tiny handful of gismu have both a CCV-form and a CVV-form rafsi assigned, and still fewer have all three forms of short rafsi. However, gismu with both a CVC-form and another short rafsi are fairly common, partly because more possible CVC-form rafsi exist. Yet CVC-form rafsi, even though they are fairly easy to remember, cannot be used at the end of a lujvo (because lujvo must end in vowels), so justifying the assignment of an additional short rafsi to many gismu.</para>
<para> <indexterm type="general-imported"><primary>rafsi</primary><secondary>rationale for assignments of</secondary></indexterm> <indexterm type="general-imported"><primary>rafsi space</primary></indexterm> The intention was to use the available
<quote>rafsi space</quote>- the set of all possible short rafsi forms - in the most efficient way possible; the goal is to make the most-used lujvo as short as possible (thus maximizing the use of short rafsi), while keeping the rafsi very recognizable to anyone who knows the source gismu. For this reason, the letters in a rafsi have always been chosen from among the five letters of the corresponding gismu. As a result, there are a limited set of short rafsi available for assignment to each gismu. At most seven possible short rafsi are available for consideration (of which at most three can be used, as explained above).</para>
- <para> <indexterm type="general-imported"><primary>rafsi</primary><secondary>possible forms for construction of</secondary></indexterm> Here are the only short rafsi forms that can possibly exist for gismu of the form CVC/CV, like
- <jbophrase>sakli</jbophrase>. The digits in the second column represent the gismu letters used to form the rafsi.</para>
- <cmavo-list>
- <cmavo-entry>
- <cmavo>CVC</cmavo>
- <selmaho>123</selmaho>
- <description>-sak-</description>
- </cmavo-entry>
- <cmavo-entry>
- <cmavo>CVC</cmavo>
- <selmaho>124</selmaho>
- <description>-sal-</description>
- </cmavo-entry>
- <cmavo-entry>
- <cmavo>CVV</cmavo>
- <selmaho>12'5</selmaho>
- <description>-sa'i-</description>
-
- </cmavo-entry>
- <cmavo-entry>
- <cmavo>CVV</cmavo>
- <selmaho>125</selmaho>
- <description>-sai-</description>
-
- </cmavo-entry>
- <cmavo-entry>
- <cmavo>CCV</cmavo>
- <selmaho>345</selmaho>
- <description>-kli-</description>
- </cmavo-entry>
- <cmavo-entry>
- <cmavo>CCV</cmavo>
- <selmaho>132</selmaho>
- <description>-ska-</description>
- </cmavo-entry>
- </cmavo-list>
+ <para> <indexterm type="general-imported"><primary>rafsi</primary><secondary>possible forms for construction of</secondary></indexterm> Here are the only short rafsi forms that can possibly exist for gismu of the form CVC/CV, like <jbophrase>sakli</jbophrase>. The digits in the second column represent the gismu letters used to form the rafsi.</para>
+ <informaltable>
+ <tgroup cols="3">
+ <colspec colnum="1" colname="col1"/>
+ <colspec colnum="2" colname="col2"/>
+ <colspec colnum="3" colname="col3"/>
+ <tbody>
+ <row>
+ <entry>CVC</entry>
+ <entry>123</entry>
+ <entry>-<jbophrase role="rafsi" valid="false">sak</jbophrase>-</entry>
+ </row>
+ <row>
+ <entry>CVC</entry>
+ <entry>124</entry>
+ <entry>-<jbophrase role="rafsi">sal</jbophrase>-</entry>
+ </row>
+ <row>
+ <entry>CVV</entry>
+ <entry>12'5</entry>
+ <entry>-<jbophrase role="rafsi" valid="false">sa'i</jbophrase>-</entry>
+
+ </row>
+ <row>
+ <entry>CVV</entry>
+ <entry>125</entry>
+ <entry>-<jbophrase role="rafsi" valid="false">sai</jbophrase>-</entry>
+
+ </row>
+ <row>
+ <entry>CCV</entry>
+ <entry>345</entry>
+ <entry>-<jbophrase role="rafsi" valid="false">kli</jbophrase>-</entry>
+ </row>
+ <row>
+ <entry>CCV</entry>
+ <entry>132</entry>
+ <entry>-<jbophrase role="rafsi" valid="false">ska</jbophrase>-</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
<para>(The only actual short rafsi for
<jbophrase>sakli</jbophrase> is
-<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>
- <selmaho>234</selmaho>
- <description>-lac</description>
- </cmavo-entry>
- <cmavo-entry>
- <cmavo>CVV</cmavo>
- <selmaho>13'5</selmaho>
- <description>-ba'i-</description>
- </cmavo-entry>
- <cmavo-entry>
- <cmavo>CVV</cmavo>
- <selmaho>135</selmaho>
- <description>-bai-</description>
- </cmavo-entry>
- <cmavo-entry>
- <cmavo>CVV</cmavo>
- <selmaho>23'5</selmaho>
- <description>-la'i-</description>
- </cmavo-entry>
- <cmavo-entry>
- <cmavo>CVV</cmavo>
- <selmaho>235</selmaho>
- <description>-lai-</description>
- </cmavo-entry>
- <cmavo-entry>
- <cmavo>CCV</cmavo>
- <selmaho>123</selmaho>
- <description>-bla-</description>
- </cmavo-entry>
- </cmavo-list>
+ <informaltable>
+ <tgroup cols="">
+ <colspec colnum="1" colname="col1"/>
+ <colspec colnum="2" colname="col2"/>
+ <colspec colnum="3" colname="col3"/>
+ <tbody>
+ <row>
+ <entry>CVC</entry>
+ <entry>134</entry>
+ <entry>-<jbophrase role="rafsi" valid="false">bac</jbophrase>-</entry>
+ </row>
+ <row>
+ <entry>CVC</entry>
+ <entry>234</entry>
+ <entry>-<jbophrase role="rafsi" valid="false">lac</jbophrase></entry>
+ </row>
+ <row>
+ <entry>CVV</entry>
+ <entry>13'5</entry>
+ <entry>-<jbophrase role="rafsi" valid="false">ba'i</jbophrase>-</entry>
+ </row>
+ <row>
+ <entry>CVV</entry>
+ <entry>135</entry>
+ <entry>-<jbophrase role="rafsi" valid="false">bai</jbophrase>-</entry>
+ </row>
+ <row>
+ <entry>CVV</entry>
+ <entry>23'5</entry>
+ <entry>-<jbophrase role="rafsi" valid="false">la'i</jbophrase>-</entry>
+ </row>
+ <row>
+ <entry>CVV</entry>
+ <entry>235</entry>
+ <entry>-<jbophrase role="rafsi" valid="false">lai</jbophrase>-</entry>
+ </row>
+ <row>
+ <entry>CCV</entry>
+ <entry>123</entry>
+ <entry>-<jbophrase role="rafsi" valid="false">bla</jbophrase>-</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
<para> <indexterm type="general-imported"><primary>rafsi assignments</primary><secondary>non-reassignability of</secondary></indexterm> (In fact,
<jbophrase>blaci</jbophrase> has none of these short rafsi; they are all assigned to other gismu. Lojban speakers are not free to reassign any of the rafsi; the tables shown here are to help understand how the rafsi were chosen in the first place.)</para>
<para> <indexterm type="general-imported"><primary>rafsi</primary><secondary>considerations restricting construction of</secondary></indexterm> There are a few restrictions: a CVV-form rafsi without an apostrophe cannot exist unless the vowels make up one of the four diphthongs
<jbophrase role="diphthong">ai</jbophrase>,
<jbophrase role="diphthong">ei</jbophrase>,
<jbophrase role="diphthong">oi</jbophrase>, or
<jbophrase role="diphthong">au</jbophrase>; and a CCV-form rafsi is possible only if the two consonants form a permissible initial consonant pair (see
<xref linkend="section-introduction"/>). Thus
<jbophrase>mamta</jbophrase>, which has the same form as
<jbophrase>salci</jbophrase>, can only have
<jbophrase role="rafsi">mam</jbophrase>,
- <jbophrase role="rafsi">mat</jbophrase>, and
- <jbophrase role="rafsi">ma'a</jbophrase> as possible rafsi: in fact, only
+ <jbophrase role="rafsi" valid="false">mat</jbophrase>, and
+ <jbophrase role="rafsi" valid="false">ma'a</jbophrase> as possible rafsi: in fact, only
<jbophrase role="rafsi">mam</jbophrase> is assigned to it.</para>
<para> <indexterm type="general-imported"><primary>numbers</primary><secondary>rafsi for</secondary></indexterm> <indexterm type="general-imported"><primary>rafsi for numbers</primary></indexterm> Some cmavo also have associated rafsi, usually CVC-form. For example, the ten common numerical digits, which are all CV form cmavo, each have a CVC-form rafsi formed by adding a consonant to the cmavo. Most cmavo that have rafsi are ones used in composing tanru (for a complete list, see
<xref linkend="chapter-lujvo"/>).</para>
<para> <indexterm type="general-imported"><primary>fully reduced lujvo</primary><secondary>definition</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>fully reduced</secondary></indexterm> The term for a lujvo made up solely of short rafsi is
<quote>fully reduced lujvo</quote>. Here are some examples of fully reduced lujvo:</para>
- <example xml:id="example-random-id-qJc2" role="interlinear-gloss-example">
+ <example xml:id="example-random-id-qJc2" role="lujvo-example">
<title>
<anchor xml:id="c4e6d6"/>
</title>
- <interlinear-gloss>
+ <lujvo>
<jbo>cumfri</jbo>
- <gloss>from
- <jbophrase>cumki lifri</jbophrase></gloss>
- <en>
- <quote>possible experience</quote>
- </en>
- </interlinear-gloss>
+ <veljvo>from <jbophrase>cumki lifri</jbophrase></veljvo>
+ <gloss><quote>possible experiglossce</quote></gloss>
+ </lujvo>
</example>
- <example xml:id="example-random-id-qjcA" role="interlinear-gloss-example">
+ <example xml:id="example-random-id-qjcA" role="lujvo-example">
<title>
<anchor xml:id="c4e6d7"/>
</title>
- <interlinear-gloss>
+ <lujvo>
<jbo>klezba</jbo>
- <gloss>from
- <jbophrase>klesi zbasu</jbophrase></gloss>
- <en>
- <quote>category make</quote>
- </en>
- </interlinear-gloss>
+ <veljvo>from <jbophrase>klesi zbasu</jbophrase></veljvo>
+ <gloss><quote>category make</quote></gloss>
+ </lujvo>
</example>
- <example xml:id="example-random-id-qjD7" role="interlinear-gloss-example">
+ <example xml:id="example-random-id-qjD7" role="lujvo-example">
<title>
<anchor xml:id="c4e6d8"/>
</title>
- <interlinear-gloss>
+ <lujvo>
<jbo>kixta'a</jbo>
- <gloss>from
- <jbophrase>krixa tavla</jbophrase></gloss>
- <en>
- <quote>cry-out talk</quote>
- </en>
- </interlinear-gloss>
+ <veljvo>from <jbophrase>krixa tavla</jbophrase></veljvo>
+ <gloss><quote>cry-out talk</quote></gloss>
+ </lujvo>
</example>
- <example xml:id="example-random-id-qJDa" role="interlinear-gloss-example">
+ <example xml:id="example-random-id-qJDa" role="lujvo-example">
<title>
<anchor xml:id="c4e6d9"/>
</title>
- <interlinear-gloss>
+ <lujvo>
<jbo>sniju'o</jbo>
- <gloss>from
- <jbophrase>sinxa djuno</jbophrase></gloss>
- <en>
- <quote>sign know</quote>
- </en>
- </interlinear-gloss>
+ <veljvo>from <jbophrase>sinxa djuno</jbophrase></veljvo>
+ <gloss><quote>sign know</quote></gloss>
+ </lujvo>
</example>
- <para>In addition, some of the unreduced forms in the previous example may be fully reduced to:</para>
- <example xml:id="example-random-id-qjdE" role="interlinear-gloss-example">
+ <para>In addition, some of the unreduced forms in the previous examples may be fully reduced to:</para>
+ <example xml:id="example-random-id-qjdE" role="lujvo-example">
<title>
<anchor xml:id="c4e6d10"/>
</title>
- <interlinear-gloss>
+ <lujvo>
<jbo>mampa'u</jbo>
- <gloss>from
- <jbophrase>mamta patfu</jbophrase></gloss>
- <en>
- <quote>mother father</quote> or
-
- <quote>maternal grandfather</quote></en>
- </interlinear-gloss>
+ <veljvo>from <jbophrase>mamta patfu</jbophrase></veljvo>
+ <gloss><quote>mother father</quote></gloss>
+ <en>or <quote>maternal grandfather</quote></en>
+ </lujvo>
</example>
- <example xml:id="example-random-id-qJDg" role="interlinear-gloss-example">
+ <example xml:id="example-random-id-qJDg" role="lujvo-example">
<title>
<anchor xml:id="c4e6d11"/>
</title>
- <interlinear-gloss>
+ <lujvo>
<jbo>lerste</jbo>
- <gloss>from
- <jbophrase>lerfu liste</jbophrase></gloss>
- <en>
- <quote>letter list</quote> or a
- <quote>list of letters</quote></en>
- </interlinear-gloss>
+ <veljvo>from <jbophrase>lerfu liste</jbophrase></veljvo>
+ <gloss><quote>letter list</quote> or a <quote>list of letters</quote></gloss>
+ </lujvo>
</example>
<para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>recognizing</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo form</primary><secondary>number of letters in</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo form</primary><secondary>consonant cluster requirement in</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo form</primary><secondary>final letter of</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>summary of form characteristics</secondary></indexterm> As noted above, CVC-form rafsi cannot appear as the final rafsi in a lujvo, because all lujvo must end with one or two vowels. As a brivla, a lujvo must also contain a consonant cluster within the first five letters - this ensures that they cannot be mistaken for compound cmavo. Of course, all lujvo have at least six letters since they have two or more rafsi, each at least three letters long; hence they cannot be confused with gismu.</para>
<para> <indexterm type="general-imported"><primary>lujvo form</primary><secondary>requirements for hyphen insertion in</secondary></indexterm> <indexterm type="general-imported"><primary>hyphen letter</primary><secondary>definition</secondary></indexterm> <indexterm type="general-imported"><primary>hyphens</primary><secondary>use of</secondary></indexterm> When attaching two rafsi together, it may be necessary to insert a hyphen letter. In Lojban, the term
<quote>hyphen</quote> always refers to a letter, either the vowel
<jbophrase role="letteral">y</jbophrase> or one of the consonants
<jbophrase role="letteral">r</jbophrase> and
<jbophrase role="letteral">n</jbophrase>. (The letter
<jbophrase role="letteral">l</jbophrase> can also be a hyphen, but is not used as one in lujvo.)</para>
<para> <indexterm type="general-imported"><primary>lujvo form</primary><secondary>requirements for y-hyphen insertion in</secondary></indexterm> The
@@ -985,21 +980,21 @@
<jbophrase>zunlyjma</jbophrase>,
<jbophrase>zuljamfu</jbophrase>, and
<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">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 <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
@@ -1194,131 +1189,129 @@
<jbophrase role="letteral">l</jbophrase>-hyphen in Lojban.)</para>
<para>Alternatively, if a CVC-form short rafsi is available it can be used instead of the long rafsi.</para>
</listitem>
<listitem>
<para>Remember that the stress necessarily appears on the penultimate (next-to-the-last) syllable.</para>
</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">
+ <example role="lojbanization-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> <!-- FIXME: should the commentary sit inside the jbo/gloss/en or outside in para? -->
+ <lojbanization> <!-- 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>
+ <jbo>spageti (Lojbanize)</jbo>
+ <jbo>cidj,r,spageti (prefix long rafsi)</jbo>
- <en>dja,r,spageti (prefix short rafsi)</en>
- </interlinear-gloss>
+ <jbo>dja,r,spageti (prefix short rafsi)</jbo>
+ </lojbanization>
</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">
+ <example role="lojbanization-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> <!-- FIXME: should the commentary sit inside the jbo/gloss/en or outside in para? -->
+ <lojbanization> <!-- 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>
+ <jbo>acer (Lojbanize)</jbo>
+ <jbo>xaceru (add initial consonant and final vowel)</jbo>
+ <jbo>tric,r,xaceru (prefix rafsi)</jbo>
+ <jbo>ric,r,xaceru (prefix short rafsi)</jbo>
+ </lojbanization>
</example>
<para>where
<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">
+ <example role="lojbanization-example" xml:id="example-random-id-C0YS">
<title>
<indexterm type="example-imported"><primary>brie</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c4e7d5"/>
</title>
- <interlinear-gloss>
+ <lojbanization>
<jbo>brie (from French)</jbo>
- <gloss>bri (Lojbanize)</gloss>
- <en>cirl,r,bri (prefix rafsi)</en>
- </interlinear-gloss>
+ <jbo>bri (Lojbanize)</jbo>
+ <jbo>cirl,r,bri (prefix rafsi)</jbo>
+ </lojbanization>
</example>
<para> where
<jbophrase role="rafsi">cirl</jbophrase>- represents
<jbophrase>cirla</jbophrase> (
<quote>cheese</quote>).</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-DQju">
+ <example role="lojbanization-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>
+ <lojbanization>
<jbo>cobra</jbo>
- <gloss>kobra (Lojbanize)</gloss>
- <en>sinc,r,kobra (prefix rafsi)</en>
- </interlinear-gloss>
+ <jbo>kobra (Lojbanize)</jbo>
+ <jbo>sinc,r,kobra (prefix rafsi)</jbo>
+ </lojbanization>
</example>
<para> where
<jbophrase role="rafsi">sinc</jbophrase>- represents
<jbophrase>since</jbophrase> (
<quote>snake</quote>).</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-TFzH">
+ <example role="lojbanization-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>
+ <lojbanization>
<jbo>quark</jbo>
- <gloss>kuark (Lojbanize)</gloss>
- <gloss>kuarka (add final vowel)</gloss>
- <en>sask,r,kuarka (prefix rafsi)</en>
- </interlinear-gloss>
+ <jbo>kuark (Lojbanize)</jbo>
+ <jbo>kuarka (add final vowel)</jbo>
+ <jbo>sask,r,kuarka (prefix rafsi)</jbo>
+ </lojbanization>
</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>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">
+ <example role="lojbanization-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>
+ <lojbanization>
+ <foreign>자모 (from Korean)</foreign>
+ <jbo>djamo (Lojbanize)</jbo>
+ <jbo>lerf,r,djamo (prefix rafsi)</jbo>
+ <jbo>ler,l,djamo (prefix rafsi)</jbo>
+ </lojbanization>
</example>
<para>where
<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
@@ -1343,201 +1336,201 @@
<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>
<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">
+ <example xml:id="example-random-id-qJG8" role="lojbanization-example">
<title>
<anchor xml:id="c4e7d9"/>
</title>
- <interlinear-gloss>
+ <lojbanization>
<jbo role="pronunciation">bang,r,blgaria</jbo>
<en>Bulgarian (in language)</en>
- </interlinear-gloss>
+ </lojbanization>
</example>
- <example xml:id="example-random-id-qJga" role="interlinear-gloss-example">
+ <example xml:id="example-random-id-qJga" role="lojbanization-example">
<title>
<anchor xml:id="c4e7d10"/>
</title>
- <interlinear-gloss>
+ <lojbanization>
<jbo role="pronunciation">kuln,r,blgaria</jbo>
<en>Bulgarian (in culture)</en>
- </interlinear-gloss>
+ </lojbanization>
</example>
- <example xml:id="example-random-id-qjGf" role="interlinear-gloss-example">
+ <example xml:id="example-random-id-qjGf" role="lojbanization-example">
<title>
<indexterm type="example-imported"><primary>Bulgarian</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c4e7d11"/>
</title>
- <interlinear-gloss>
+ <lojbanization>
<jbo role="pronunciation">gugd,r,blgaria</jbo>
<en>Bulgaria (the country)</en>
- </interlinear-gloss>
+ </lojbanization>
</example>
- <example xml:id="example-random-id-qJGv" role="interlinear-gloss-example">
+ <example xml:id="example-random-id-qJGv" role="lojbanization-example">
<title>
<anchor xml:id="c4e7d12"/>
</title>
- <interlinear-gloss>
+ <lojbanization>
<jbo role="pronunciation">bang,r,kore,a</jbo>
<en>Korean (the language)</en>
- </interlinear-gloss>
+ </lojbanization>
</example>
- <example xml:id="example-random-id-qjh0" role="interlinear-gloss-example">
+ <example xml:id="example-random-id-qjh0" role="lojbanization-example">
<title>
<indexterm type="example-imported"><primary>Korean</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c4e7d13"/>
</title>
- <interlinear-gloss>
+ <lojbanization>
<jbo role="pronunciation">kuln,r,kore,a</jbo>
<en>Korean (the culture)</en>
- </interlinear-gloss>
+ </lojbanization>
</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:
<quote>Navajo</quote> is far more widely known than
<quote>Dine'e</quote>.</para>
</section>
<section xml:id="section-cmene">
<title>cmene</title>
<para> <indexterm type="general-imported"><primary>names in Lojban (see also cmene)</primary></indexterm> <indexterm type="general-imported"><primary>cmene</primary><secondary>definition</secondary></indexterm> <indexterm type="general-imported"><primary>names</primary><secondary>purpose of</secondary></indexterm> <indexterm type="general-imported"><primary>cmene</primary><secondary>purpose of</secondary></indexterm> Lojbanized names, called
<jbophrase>cmene</jbophrase>, are very much like their counterparts in other languages. They are labels applied to things (or people) to stand for them in descriptions or in direct address. They may convey meaning in themselves, but do not necessarily do so.</para>
<para> <indexterm type="general-imported"><primary>names</primary><secondary>rationale for lojbanizing</secondary></indexterm> <indexterm type="general-imported"><primary>cmene</primary><secondary>rationale for lojbanizing</secondary></indexterm> <indexterm type="general-imported"><primary>cmene</primary><secondary>and analyzability of speech stream</secondary></indexterm> <indexterm type="general-imported"><primary>names</primary><secondary>examples of</secondary></indexterm> <indexterm type="general-imported"><primary>cmene</primary><secondary>examples of</secondary></indexterm> Because names are often highly personal and individual, Lojban attempts to allow native language names to be used with a minimum of modification. The requirement that the Lojban speech stream be unambiguously analyzable, however, means that most names must be modified somewhat when they are Lojbanized. Here are a few examples of English names and possible Lojban equivalents:</para>
- <example xml:id="example-random-id-qjhN" role="interlinear-gloss-example">
+ <example xml:id="example-random-id-qjhN" role="lojbanization-example">
<title>
<indexterm type="example-imported"><primary>Jim</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c4e8d1"/>
</title>
- <interlinear-gloss>
+ <lojbanization>
<jbo>djim.</jbo>
<en>Jim</en>
- </interlinear-gloss>
+ </lojbanization>
</example>
- <example xml:id="example-random-id-qjHo" role="interlinear-gloss-example">
+ <example xml:id="example-random-id-qjHo" role="lojbanization-example">
<title>
<indexterm type="example-imported"><primary>Jane</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c4e8d2"/>
</title>
- <interlinear-gloss>
+ <lojbanization>
<jbo>djein.</jbo>
<en>Jane</en>
- </interlinear-gloss>
+ </lojbanization>
</example>
- <example xml:id="example-random-id-qjIj" role="interlinear-gloss-example">
+ <example xml:id="example-random-id-qjIj" role="lojbanization-example">
<title>
<indexterm type="example-imported"><primary>Arnold</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c4e8d3"/>
</title>
- <interlinear-gloss>
+ <lojbanization>
<jbo>.arnold.</jbo>
<en>Arnold</en>
- </interlinear-gloss>
+ </lojbanization>
</example>
- <example xml:id="example-random-id-qjim" role="interlinear-gloss-example">
+ <example xml:id="example-random-id-qjim" role="lojbanization-example">
<title>
<indexterm type="example-imported"><primary>Pete</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c4e8d4"/>
</title>
- <interlinear-gloss>
+ <lojbanization>
<jbo>pit.</jbo>
<en>Pete</en>
- </interlinear-gloss>
+ </lojbanization>
</example>
- <example xml:id="example-random-id-qjin" role="interlinear-gloss-example">
+ <example xml:id="example-random-id-qjin" role="lojbanization-example">
<title>
<indexterm type="example-imported"><primary>Katrina</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c4e8d5"/>
</title>
- <interlinear-gloss>
+ <lojbanization>
<jbo>katrinas.</jbo>
<en>Katrina</en>
- </interlinear-gloss>
+ </lojbanization>
</example>
- <example xml:id="example-random-id-qjIq" role="interlinear-gloss-example">
+ <example xml:id="example-random-id-qjIq" role="lojbanization-example">
<title>
<indexterm type="example-imported"><primary>Catherine</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c4e8d6"/>
</title>
- <interlinear-gloss>
+ <lojbanization>
<jbo>kat,r,in.</jbo>
<en>Catherine</en>
- </interlinear-gloss>
+ </lojbanization>
</example>
<para><indexterm type="general-imported"><primary>syllabic consonant</primary><secondary>effect on stress determination</secondary></indexterm> (Note that syllabic
<jbophrase role="letteral">r</jbophrase> is skipped in determining the stressed syllable, so
<xref linkend="example-random-id-qjIq"/> is stressed on the
<jbophrase>ka</jbophrase>.)</para>
- <example xml:id="example-random-id-qJiv" role="interlinear-gloss-example">
+ <example xml:id="example-random-id-qJiv" role="lojbanization-example">
<title>
<indexterm type="example-imported"><primary>Cathy</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c4e8d7"/>
</title>
- <interlinear-gloss>
+ <lojbanization>
<jbo>katis.</jbo>
<en>Cathy</en>
- </interlinear-gloss>
+ </lojbanization>
</example>
- <example xml:id="example-random-id-qjIy" role="interlinear-gloss-example">
+ <example xml:id="example-random-id-qjIy" role="lojbanization-example">
<title>
<indexterm type="example-imported"><primary>Kate</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c4e8d8"/>
</title>
- <interlinear-gloss>
+ <lojbanization>
<jbo>keit.</jbo>
<en>Kate</en>
- </interlinear-gloss>
+ </lojbanization>
</example>
<para><indexterm type="general-imported"><primary>names</primary><secondary>unusual stress in</secondary></indexterm> <indexterm type="general-imported"><primary>cmene</primary><secondary>unusual stress in</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> <indexterm type="general-imported"><primary>names</primary><secondary>rules for formation</secondary></indexterm> <indexterm type="general-imported"><primary>cmene</primary><secondary>rules for formation</secondary></indexterm> Names may have almost any form, but always end in a consonant, and are followed by a pause. They are penultimately stressed, unless unusual stress is marked with capitalization. A name may have multiple parts, each ending with a consonant and pause, or the parts may be combined into a single word with no pause. For example,</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-43uP">
+ <example role="lojbanization-example" xml:id="example-random-id-43uP">
<title>
<!-- FIXME: these two indexterms match two different examples; should they go in both or just the first? -->
<indexterm type="example-imported"><primary>John Jones</primary><secondary>example</secondary></indexterm>
<indexterm type="example-imported"><primary>Jones</primary><secondary>John</secondary><tertiary>example</tertiary></indexterm>
<anchor xml:id="c4e8d9"/>
</title>
- <interlinear-gloss>
+ <lojbanization>
<jbo>djan. djonz.</jbo>
- </interlinear-gloss>
+ </lojbanization>
</example>
<para> and</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-QnyL">
+ <example role="lojbanization-example" xml:id="example-random-id-QnyL">
<title>
<anchor xml:id="c4e8d10"/>
</title>
- <interlinear-gloss>
+ <lojbanization>
<jbo>djandjonz.</jbo> <!-- FIXME: "ndj" not an allowed cluster (jcowan-approved) -->
- </interlinear-gloss>
+ </lojbanization>
</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 glossay="false">meris.</jbophrase>,
<jbophrase glossay="false">maris.</jbophrase>,
<jbophrase glossay="false">meiris.</jbophrase>,
<jbophrase glossay="false">merix.</jbophrase>, or even
@@ -2169,67 +2162,59 @@
<jbophrase role="letteral">y</jbophrase>; call it
<quote>V</quote>.</para>
</listitem>
</varlistentry>
</variablelist>
<para> <indexterm type="general-imported"><primary>lujvo form</primary><secondary>hierarchy of priorities for selection of</secondary></indexterm> <indexterm type="general-imported"><primary>hierarchy of priorities for selecting lujvo form</primary></indexterm> The score is then:
<informalequation><mathphrase>(1000 * L) - (500 * A) + (100 * H) - (10 * R) - V</mathphrase></informalequation>
<indexterm type="general-imported"><primary>lujvo</primary><secondary>scored examples of</secondary></indexterm> In case of ties, there is no preference. This should be rare. Note that the algorithm essentially encodes a hierarchy of priorities: short words are preferred (counting apostrophes as half a letter), then words with fewer hyphens, words with more pleasing rafsi (this judgment is subjective), and finally words with more vowels are chosen. Each decision principle is applied in turn if the ones before it have failed to choose; it is possible that a lower-ranked principle might dominate a higher-ranked one if it is ten times better than the alternative.</para>
<para> <!-- FIXME: there's nowhere for this indexterm to go --><indexterm type="example-imported"><primary>doghouse</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>examples of making</secondary></indexterm> Here are some lujvo with their scores (not necessarily the lowest scoring forms for these lujvo, nor even necessarily sensible lujvo):</para>
- <example xml:id="example-random-id-qJKu" role="interlinear-gloss-example">
+ <example xml:id="example-random-id-qJKu" role="lujvo-making-example">
<title>
<anchor xml:id="c4e12d1"/>
</title>
- <interlinear-gloss>
+ <lujvo-making>
<jbo>zbasai</jbo>
- <gloss>zba + sai</gloss>
-
- <gloss>(1000 * 6) - (500 * 0) + (100 * 0) - (10 * 15) - 3</gloss>
- <en>= 5847</en>
- </interlinear-gloss>
+ <rafsi>zba + sai</rafsi>
+ <score><inlineequation><mathphrase>(1000 * 6) - (500 * 0) + (100 * 0) - (10 * 15) - 3 = 5847</mathphrase></inlineequation></score>
+ </lujvo-making>
</example>
- <example xml:id="example-random-id-qjLd" role="interlinear-gloss-example">
+ <example xml:id="example-random-id-qjLd" role="lujvo-making-example">
<title>
<anchor xml:id="c4e12d2"/>
</title>
- <interlinear-gloss>
+ <lujvo-making>
<jbo>nunynau</jbo>
- <gloss>nun + y + nau</gloss>
-
- <gloss>(1000 * 7) - (500 * 0) + (100 * 1) - (10 * 13) - 3</gloss>
- <en>= 6967</en>
- </interlinear-gloss>
+ <rafsi>nun + y + nau</rafsi>
+ <score><inlineequation><mathphrase>(1000 * 7) - (500 * 0) + (100 * 1) - (10 * 13) - 3 = 6967</mathphrase></inlineequation></score>
+ </lujvo-making>
</example>
- <example xml:id="example-random-id-qJLQ" role="interlinear-gloss-example">
+ <example xml:id="example-random-id-qJLQ" role="lujvo-making-example">
<title>
<anchor xml:id="c4e12d3"/>
</title>
- <interlinear-gloss>
+ <lujvo-making>
<jbo>sairzbata'u</jbo>
- <gloss>sai + r + zba + ta'u</gloss>
-
-
- <gloss>(1000 * 11) - (500 * 1) + (100 * 1) - (10 * 21) - 5</gloss>
- <en>= 10385</en>
- </interlinear-gloss>
+ <rafsi>sai + r + zba + ta'u</rafsi>
+ <score><inlineequation><mathphrase>(1000 * 11) - (500 * 1) + (100 * 1) - (10 * 21) - 5 = 10385</mathphrase></inlineequation></score>
+ </lujvo-making>
</example>
- <example xml:id="example-random-id-qJmn" role="interlinear-gloss-example">
+ <example xml:id="example-random-id-qJmn" role="lujvo-making-example">
<title>
<anchor xml:id="c4e12d4"/>
</title>
- <interlinear-gloss>
+ <lujvo-making>
<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>
+ <rafsi>zba + zbas + y + sarji</rafsi>
+ <score><inlineequation><mathphrase>(1000 * 13) - (500 * 0) + (100 * 1) - (10 * 12) - 4 = 12976</mathphrase></inlineequation></score>
+ </lujvo-making>
</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
@@ -2303,36 +2288,52 @@
<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>
+ <informaltable>
+ <tgroup cols="2">
+ <colspec colnum="1" colname="col1"/>
+ <colspec colnum="2" colname="col2"/>
+ <tbody>
+ <row>
+ <entry><jbophrase>lotkle</jbophrase></entry>
+ <entry>5878</entry>
+ </row>
+ <row>
+ <entry><jbophrase>blokle</jbophrase></entry>
+ <entry>5858</entry>
+ </row>
+ <row>
+ <entry><jbophrase>lo'ikle</jbophrase></entry>
+ <entry>6367</entry>
+ </row>
+ <row>
+ <entry><jbophrase>lotlei</jbophrase></entry>
+ <entry>5867</entry>
+ </row>
+ <row>
+ <entry><jbophrase>blolei</jbophrase></entry>
+ <entry>5847</entry>
+ </row>
+ <row>
+ <entry><jbophrase>lo'irlei</jbophrase></entry>
+ <entry>7456</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
<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
diff --git a/todocbook/TODO b/todocbook/TODO
index 9325489..99c859b 100644
--- a/todocbook/TODO
+++ b/todocbook/TODO
@@ -174,21 +174,22 @@ 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 pronunciation-example, compound-cmavo-example
+ - so far there's also pronunciation-example,
+ compound-cmavo-example, lujvo-making-example, lojbanization-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 5219c6c67eb437c0aada0bf5fa46d2e392109f95
Author: Eitan Postavsky <eitanp32@gmail.com>
Date: Tue Jan 4 22:07:45 2011 -0500
Chapter 4: some jbophrases, examples. Invented lujvo example.
Invented role="lujvo-example" for examples which simply exhibit lujvo,
along with <lujvo> to replace <interlinear-gloss>, and <veljvo>, which
goes inside <lujvo>, for the veljvo of the lujvo in question.
diff --git a/todocbook/4.xml b/todocbook/4.xml
index 41004a9..312a964 100644
--- a/todocbook/4.xml
+++ b/todocbook/4.xml
@@ -147,39 +147,39 @@
<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>
+ <entry><jbophrase role="letteral">.a</jbophrase></entry>
+ <entry><jbophrase role="letteral">.e</jbophrase></entry>
+ <entry><jbophrase role="letteral">.i</jbophrase></entry>
+ <entry><jbophrase role="letteral">.o</jbophrase></entry>
+ <entry><jbophrase role="letteral">.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 role="diphthong">.au</jbophrase></entry>
+ <entry><jbophrase role="diphthong">.ei</jbophrase></entry>
+ <entry><jbophrase role="diphthong">.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>
@@ -267,96 +267,95 @@
</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 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="compound-cmavo-example" xml:id="example-random-id-CtnR">
<title>
<anchor xml:id="c4e2d5"/>
</title>
- <interlinear-gloss>
+ <compound-cmavo>
<jbo>cy.ibu.abu</jbo>
<jbo>cy. .ibu .abu</jbo>
- </interlinear-gloss>
+ </compound-cmavo>
</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="pronunciation-example" xml:id="example-random-id-pdGY">
<title>
<anchor xml:id="c4e2d6"/>
</title>
- <interlinear-gloss>
+ <pronunciation>
<jbo>.e'o ko ko kurji</jbo>
<jbo role="pronunciation">.E'o ko ko KURji</jbo>
- </interlinear-gloss>
+ </pronunciation>
</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>
<jbo>le re nanmu</jbo>
</interlinear-gloss>
</example>
<para>can be optionally pronounced</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-dfzc">
+ <example role="pronunciation-example" xml:id="example-random-id-dfzc">
<title>
<anchor xml:id="c4e2d8"/>
</title>
- <interlinear-gloss>
- <jbo>le RE. NANmu</jbo>
- </interlinear-gloss>
+ <pronunciation>
+ <jbo role="pronunciation">le RE. NANmu</jbo>
+ </pronunciation>
</example>
<para>since there are no rules forcing stress on either of the first two words; the stress on
<jbophrase>re</jbophrase>, though, demands that a pause separate
<jbophrase>re</jbophrase> from the following syllable
<jbophrase>nan</jbophrase> to ensure that the stress on
<jbophrase>nan</jbophrase> is properly heard as a stressed syllable. The alternative pronunciation</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-bLbf">
+ <example role="pronunciation-example" xml:id="example-random-id-bLbf">
<title>
<anchor xml:id="c4e2d9"/>
</title>
- <interlinear-gloss>
+ <pronunciation>
<jbo>LE re NANmu</jbo>
- </interlinear-gloss>
+ </pronunciation>
</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="pronunciation-example" xml:id="example-random-id-sg0p">
<title>
<anchor xml:id="c4e2d10"/>
</title>
- <interlinear-gloss>
+ <pronunciation>
<jbo role="pronunciation">le re NANmu</jbo>
- </interlinear-gloss>
+ </pronunciation>
</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>
@@ -691,88 +690,76 @@
<para> <indexterm type="general-imported"><primary>unreduced lujvo</primary><secondary>definition</secondary></indexterm> <indexterm type="general-imported"><primary>long rafsi</primary><secondary>definition</secondary></indexterm> <indexterm type="general-imported"><primary>4-letter rafsi</primary><secondary>definition</secondary></indexterm> <indexterm type="general-imported"><primary>5-letter rafsi</primary><secondary>definition</secondary></indexterm> <indexterm type="general-imported"><primary>gismu</primary><secondary>basic rafsi for</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>unreduced</secondary></indexterm> <indexterm type="general-imported"><primary>rafsi</primary><secondary>long</secondary></indexterm> <indexterm type="general-imported"><primary>rafsi</primary><secondary>forms of</secondary></indexterm> Each gismu always has at least two rafsi forms; one is the gismu itself (used only at the end of a lujvo), and one is the gismu without its final vowel (used only at the beginning or middle of a lujvo). These forms are represented as CVC/CV or CCVCV (called
<quote>the 5-letter rafsi</quote>), and CVC/C or CCVC (called
<quote>the 4-letter rafsi</quote>) respectively. The dashes in these rafsi form representations show where other rafsi may be attached to form a valid lujvo. When lujvo are formed only from 4-letter and 5-letter rafsi, known collectively as
<quote>long rafsi</quote>, they are called
<quote>unreduced lujvo</quote>.</para>
<para>Some examples of unreduced lujvo forms are:</para>
- <example xml:id="example-random-id-qj84" role="interlinear-gloss-example">
+ <example xml:id="example-random-id-qj84" role="lujvo-example">
<title>
<anchor xml:id="c4e6d1"/>
</title>
- <interlinear-gloss>
+ <lujvo>
<jbo>mamtypatfu</jbo>
- <gloss>from
- <jbophrase>mamta patfu</jbophrase></gloss>
- <en>
- <quote>mother father</quote> or
-
- <quote>maternal grandfather</quote></en>
- </interlinear-gloss>
+ <veljvo>from <jbophrase>mamta patfu</jbophrase></veljvo>
+ <gloss><quote>mother father</quote></gloss>
+ <en>or <quote>maternal grandfather</quote></en>
+ </lujvo>
</example>
- <example xml:id="example-random-id-qj99" role="interlinear-gloss-example">
+ <example xml:id="example-random-id-qj99" role="lujvo-example">
<title>
<anchor xml:id="c4e6d2"/>
</title>
- <interlinear-gloss>
+ <lujvo>
<jbo>lerfyliste</jbo>
- <gloss>from
- <jbophrase>lerfu liste</jbophrase></gloss>
- <gloss>
- <quote>letter list</quote> or a
- <quote>list of letters</quote></gloss>
+ <veljvo>from <jbophrase>lerfu liste</jbophrase></veljvo>
+ <gloss><quote>letter list</quote> or a <quote>list of letters</quote></gloss>
<en>(letters of the alphabet)</en>
- </interlinear-gloss>
+ </lujvo>
</example>
- <example xml:id="example-random-id-qj9G" role="interlinear-gloss-example">
+ <example xml:id="example-random-id-qj9G" role="lujvo-example">
<title>
<anchor xml:id="c4e6d3"/>
</title>
- <interlinear-gloss>
+ <lujvo>
<jbo>nancyprali</jbo>
- <gloss>from
- <jbophrase>nanca prali</jbophrase></gloss>
- <en>
- <quote>year profit</quote> or
- <quote>annual profit</quote></en>
- </interlinear-gloss>
+ <veljvo>from <jbophrase>nanca prali</jbophrase></veljvo>
+ <gloss><quote>year profit</quote></gloss>
+ <en>or <quote>annual profit</quote></en>
+ </lujvo>
</example>
- <example xml:id="example-random-id-qJbi" role="interlinear-gloss-example">
+ <example xml:id="example-random-id-qJbi" role="lujvo-example">
<title>
<anchor xml:id="c4e6d4"/>
</title>
- <interlinear-gloss>
+ <lujvo>
<jbo>prunyplipe</jbo>
- <gloss>from
- <jbophrase>pruni plipe</jbophrase></gloss>
- <en>
- <quote>elastic (springy) leap</quote> or
- <quote>spring</quote> (the verb)</en>
- </interlinear-gloss>
+ <veljvo>from <jbophrase>pruni plipe</jbophrase></veljvo>
+ <gloss><quote>elastic (springy) leap</quote></gloss>
+ <en>or <quote>spring</quote> (the verb)</en>
+ </lujvo>
</example>
- <example xml:id="example-random-id-qjbP" role="interlinear-gloss-example">
+ <example xml:id="example-random-id-qjbP" role="lujvo-example">
<title>
<indexterm type="example-imported"><primary>supper</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c4e6d5"/>
</title>
- <interlinear-gloss>
+ <lujvo>
<jbo>vancysanmi</jbo>
- <gloss>from
- <jbophrase>vanci sanmi</jbophrase></gloss>
- <en>
- <quote>evening meal</quote> or
- <quote>supper</quote></en>
+ <veljvo>from <jbophrase>vanci sanmi</jbophrase></veljvo>
+ <gloss><quote>evening meal</quote></gloss>
+ <en>or <quote>supper</quote></en>
- </interlinear-gloss>
+ </lujvo>
</example>
<para> <indexterm type="general-imported"><primary>short rafsi</primary></indexterm> <indexterm type="general-imported"><primary>rafsi</primary><secondary>short</secondary></indexterm> In addition to these two forms, each gismu may have up to three additional short rafsi, three letters long. All short rafsi have one of the forms CVC, CCV, or CVV. The total number of rafsi forms that are assigned to a gismu depends on how useful the gismu is, or is presumed to be, in making lujvo, when compared to other gismu that could be assigned the rafsi.</para>
<para> <indexterm type="general-imported"><primary>-er</primary><secondary>use of zmadu in forming</secondary></indexterm> <indexterm type="general-imported"><primary>comparatives</primary><secondary>use of zmadu in forming</secondary></indexterm> For example,
<jbophrase>zmadu</jbophrase> (
<quote>more than</quote>) has the two short rafsi
<jbophrase role="rafsi">zma</jbophrase> and
<jbophrase role="rafsi">mau</jbophrase> (in addition to its unreduced rafsi
<jbophrase role="rafsi">zmad</jbophrase> and
<jbophrase>zmadu</jbophrase>), because a vast number of lujvo have been created based on
@@ -1071,21 +1058,21 @@
<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>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>
--
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.