[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bpfk] dag-cll git updates for Wed Feb 2 15:21:02 EST 2011
commit 5c1037023bdd7966f127874dbfa57852e74fde3a
Merge: 5e0c241 7b63287
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date: Wed Feb 2 11:59:48 2011 -0800
Merge commit '7b63287a42909f6e3990ce150cd76a89dfd2c314' into gh-pages
commit 5e0c241fa4db50453eb681217c55db6ec887c5cd
Merge: 9cd20ec 71f32a1
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date: Wed Feb 2 11:23:13 2011 -0800
Merge commit '71f32a122ff534978eee6622a702e5e56fed8f9d' into gh-pages
commit 9cd20ecfbb06d897acb3160058f9a017f7917ea4
Merge: 79c554f 52d1388
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date: Wed Feb 2 10:14:08 2011 -0800
Merge commit '52d1388d91264b9156a3273bc30d4b0b7b631e75' into gh-pages
commit 7b63287a42909f6e3990ce150cd76a89dfd2c314
Author: Eitan Postavsky <eitanp32@gmail.com>
Date: Tue Jan 11 16:17:39 2011 -0500
Chapter 13 jbophrases and chapter 3 language codes.
diff --git a/todocbook/13.xml b/todocbook/13.xml
index f53eaca..cff6a71 100644
--- a/todocbook/13.xml
+++ b/todocbook/13.xml
@@ -1,24 +1,22 @@
<chapter xml:id="chapter-attitudinals">
<title>Oooh! Arrgh! Ugh! Yecch! Attitudinal and Emotional Indicators</title>
<section xml:id="cll_chapter13-section1">
<title>What are attitudinal indicators?</title>
<para>This chapter explains the various words that Lojban provides for expressing attitude and related notions. In natural languages, attitudes are usually expressed by the tone of voice when speaking, and (very imperfectly) by punctuation when writing. For example, the bare words</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-EWHQ">
+ <example xml:id="example-random-id-EWHQ">
<title>
<anchor xml:id="c13e1d1"/>
</title>
- <interlinear-gloss>
- <jbo>John is coming.</jbo>
- </interlinear-gloss>
+ <para>John is coming.</para>
</example>
<para>can be made, through tone of voice, to express the speaker's feeling of happiness, pity, hope, surprise, or disbelief. These fine points of tone cannot be expressed in writing. Attitudes are also expressed with various sounds which show up in print as oddly spelled words, such as the
<quote>Oooh!</quote>,
<quote>Arrgh!</quote>,
<quote>Ugh!</quote>, and
<quote>Yecch!</quote> in the title. These are part of the English language; people born to other languages use a different set; yet you won't find any of these words in a dictionary.</para>
<para> <indexterm type="general-imported"><primary>attitudinal indicators</primary></indexterm> In Lojban, everything that can be spoken can also be written. Therefore, these tones of voice must be represented by explicit words known as
<quote>attitudinal indicators</quote>, or just
@@ -70,94 +68,94 @@
<anchor xml:id="c13e1d6"/>
</title>
<interlinear-gloss>
<jbo>.ianai la djan klama</jbo>
<gloss>[Nonsense!] John is coming.</gloss>
</interlinear-gloss>
</example>
<para> <indexterm type="lojban-word-imported"><primary>UI selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>.ianai</primary></indexterm> <indexterm type="lojban-word-imported"><primary>.ue</primary></indexterm> <indexterm type="lojban-word-imported"><primary>.a'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>.uu</primary></indexterm> <indexterm type="lojban-word-imported"><primary>.ui</primary></indexterm> <indexterm type="example-imported"><primary>John is coming</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>word-form for primary</secondary></indexterm> The primary Lojban attitudinals are all the cmavo of the form VV or V'V: one of the few cases where cmavo have been classified solely by their form. There are 39 of these cmavo: all 25 possible vowel pairs of the form V'V, the four standard diphthongs (
- <jbophrase>.ai</jbophrase>,
- <jbophrase>.au</jbophrase>,
- <jbophrase>.ei</jbophrase>, and
- <jbophrase>.oi</jbophrase>), and the ten more diphthongs that are permitted only in these attitudinal indicators and in names and borrowings (
+ <jbophrase role="diphthong">.ai</jbophrase>,
+ <jbophrase role="diphthong">.au</jbophrase>,
+ <jbophrase role="diphthong">.ei</jbophrase>, and
+ <jbophrase role="diphthong">.oi</jbophrase>), and the ten more diphthongs that are permitted only in these attitudinal indicators and in names and borrowings (
- <jbophrase>.ia</jbophrase>,
- <jbophrase>.ie</jbophrase>,
- <jbophrase>.ii</jbophrase>,
- <jbophrase>.io</jbophrase>,
- <jbophrase>.iu</jbophrase>,
- <jbophrase>.ua</jbophrase>,
- <jbophrase>.ue</jbophrase>,
+ <jbophrase role="diphthong">.ia</jbophrase>,
+ <jbophrase role="diphthong">.ie</jbophrase>,
+ <jbophrase role="diphthong">.ii</jbophrase>,
+ <jbophrase role="diphthong">.io</jbophrase>,
+ <jbophrase role="diphthong">.iu</jbophrase>,
+ <jbophrase role="diphthong">.ua</jbophrase>,
+ <jbophrase role="diphthong">.ue</jbophrase>,
- <jbophrase>.ui</jbophrase>,
- <jbophrase>.uo</jbophrase>, and
- <jbophrase>.uu</jbophrase>). Note that each of these cmavo has a period before it, marking the pause that is mandatory before every word beginning with a vowel. Attitudinals, like most of the other kinds of indicators described in this chapter, belong to selma'o UI.</para>
+ <jbophrase role="diphthong">.ui</jbophrase>,
+ <jbophrase role="diphthong">.uo</jbophrase>, and
+ <jbophrase role="diphthong">.uu</jbophrase>). Note that each of these cmavo has a period before it, marking the pause that is mandatory before every word beginning with a vowel. Attitudinals, like most of the other kinds of indicators described in this chapter, belong to selma'o UI.</para>
<para> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>compound</secondary></indexterm> Attitudinals can also be compound cmavo, of the types explained in Sections 4-8;
<xref linkend="example-random-id-qfgA"/> illustrates one such possibility, the compound attitudinal
<jbophrase>.ianai</jbophrase>. In attitudinals,
- <quote>-nai</quote> indicates polar negation: the opposite of the simple attitudinal without the
- <quote>-nai</quote>. Thus, as you might suppose,
- <jbophrase>.ia</jbophrase> expresses belief, since
+ <jbophrase>-nai</jbophrase> indicates polar negation: the opposite of the simple attitudinal without the
+ <jbophrase>-nai</jbophrase>. Thus, as you might suppose,
+ <jbophrase role="diphthong">.ia</jbophrase> expresses belief, since
<jbophrase>.ianai</jbophrase> expresses disbelief.</para>
<para> <indexterm type="general-imported"><primary>indicators</primary><secondary>types of</secondary></indexterm> <indexterm type="general-imported"><primary>indicators</primary></indexterm> In addition to the attitudinals, there are other classes of indicators: intensity markers, emotion categories, attitudinal modifiers, observationals, and discursives. All of them are grammatically equivalent, which is why they are treated together in this chapter.</para>
<para>Every indicator behaves in more or less the same way with respect to the grammar of the rest of the language. In general, one or more indicators can be inserted at the beginning of an utterance or after any word. Indicators at the beginning apply to the whole utterance; otherwise, they apply to the word that they follow. More details can be found in
<xref linkend="cll_chapter13-section9"/>.</para>
<para>Throughout this chapter, tables of indicators will be written in four columns. The first column is the cmavo itself. The second column is a corresponding English word, not necessarily a literal translation. The fourth column represents the opposite of the second column, and shows the approximate meaning of the attitudinal when suffixed with
- <quote>-nai</quote>. The third column, which is sometimes omitted, indicates a neutral point between the second and fourth columns, and shows the approximate meaning of the attitudinal when it is suffixed with
- <quote>-cu'i</quote>. The cmavo
+ <jbophrase>-nai</jbophrase>. The third column, which is sometimes omitted, indicates a neutral point between the second and fourth columns, and shows the approximate meaning of the attitudinal when it is suffixed with
+ <jbophrase>-cu'i</jbophrase>. The cmavo
<jbophrase>cu'i</jbophrase> belongs to selma'o CAI, and is explained more fully in
<xref linkend="cll_chapter13-section4"/>.</para>
<para>One flaw that the English glosses are particularly subject to is that in English it is often difficult to distinguish between expressing your feelings and talking about them, particularly with the limited resource of the written word. So the gloss for
- <jbophrase>.ui</jbophrase> should not really be
+ <jbophrase role="diphthong">.ui</jbophrase> should not really be
<quote>happiness</quote> but some sound or tone that expresses happiness. However, there aren't nearly enough of those that have unambiguous or obvious meanings in English to go around for all the many, many different emotions Lojban speakers can readily express.</para>
<para>Many indicators of CV'V form are loosely derived from specific gismu. The gismu should be thought of as a memory hook, not an equivalent of the cmavo. Such gismu are shown in this chapter between square brackets, thus: [gismu].</para>
</section>
<section xml:id="cll_chapter13-section2">
<title>Pure emotion indicators</title>
<para>Attitudinals make no claim: they are expressions of attitude, not of facts or alleged facts. As a result, attitudinals themselves have no truth value, nor do they directly affect the truth value of a bridi that they modify. However, since emotional attitudes are carried in your mind, they reflect reactions to that version of the world that the mind is thinking about; this is seldom identical with the real world. At times, we are thinking about our idealized version of the real world; at other times we are thinking about a potential world that might or might not ever exist.</para>
<para>Therefore, there are two groups of attitudinals in Lojban. The
<quote>pure emotion indicators</quote> express the way the speaker is feeling, without direct reference to what else is said. These indicators comprise the attitudinals which begin with
- <quote>u</quote> or
- <quote>o</quote> and many of those beginning with
- <jbophrase>i</jbophrase>.</para>
+ <jbophrase role="letteral">u</jbophrase> or
+ <jbophrase role="letteral">o</jbophrase> and many of those beginning with
+ <jbophrase role="letteral">i</jbophrase>.</para>
<para>The cmavo beginning with
- <quote>u</quote> are simple emotions, which represent the speaker's reaction to the world as it is, or as it is perceived to be.</para>
+ <jbophrase role="letteral">u</jbophrase> are simple emotions, which represent the speaker's reaction to the world as it is, or as it is perceived to be.</para>
<programlisting xml:space="preserve">
.ua discovery confusion
<!-- skip cmavo list automation -->
.u'a gain loss
.ue surprise no surprise expectation
.u'e wonder commonplace
.ui happiness unhappiness
.u'i amusement weariness
.uo completion incompleteness
.u'o courage timidity cowardice
.uu pity cruelty
.u'u repentance lack of regret innocence
</programlisting>
<para>Here are some typical uses of the
- <quote>u</quote> attitudinals:</para>
+ <jbophrase role="letteral">u</jbophrase> attitudinals:</para>
<example xml:id="example-random-id-qFgi" role="interlinear-gloss-example">
<title>
<anchor xml:id="c13e2d1"/>
</title>
<interlinear-gloss>
<jbo>.ua mi facki fi le mi mapku</jbo>
<gloss>[Eureka!] I found my hat! [emphasizes the discovery of the hat]</gloss>
</interlinear-gloss>
</example>
<example xml:id="example-random-id-qFgv" role="interlinear-gloss-example">
@@ -203,31 +201,31 @@
<anchor xml:id="c13e2d6"/>
</title>
<interlinear-gloss>
<jbo>.u'u do cortu</jbo>
<gloss>[Repentance!] You feel-pain. [expresses that speaker feels guilty]</gloss>
</interlinear-gloss>
</example>
<para>In
<xref linkend="example-random-id-qfHA"/>, note that the attitudinal
- <jbophrase>.uo</jbophrase> is translated by an English non-attitudinal phrase:
+ <jbophrase role="diphthong">.uo</jbophrase> is translated by an English non-attitudinal phrase:
<quote>At last!</quote> It is common for the English equivalents of Lojban attitudinals to be short phrases of this sort, with more or less normal grammar, but actually expressions of emotion.</para>
<para>In particular, both
- <jbophrase>.uu</jbophrase> and
- <jbophrase>.u'u</jbophrase> can be translated into English as
+ <jbophrase role="diphthong">.uu</jbophrase> and
+ <jbophrase role="diphthong">.u'u</jbophrase> can be translated into English as
<quote>I'm sorry</quote>; the difference between these two attitudes frequently causes confusion among English-speakers who use this phrase, leading to responses like
<quote>Why are you sorry? It's not your fault!</quote></para>
<para>It is important to realize that
- <jbophrase>.uu</jbophrase>, and indeed all attitudinals, are meant to be used sincerely, not ironically. In English, the exclamation
+ <jbophrase role="diphthong">.uu</jbophrase>, and indeed all attitudinals, are meant to be used sincerely, not ironically. In English, the exclamation
<quote>Pity!</quote> is just as likely to be ironically intended, but this usage does not extend to Lojban. Lying with attitudinals is (normally) as inappropriate to Lojban discourse as any other kind of lying: perhaps worse, because misunderstood emotions can cause even greater problems than misunderstood statements.</para>
<para>The following examples display the effects of
<jbophrase>nai</jbophrase> and
<jbophrase>cu'i</jbophrase> when suffixed to an attitudinal:</para>
<example xml:id="example-random-id-qFiE" role="interlinear-gloss-example">
<title>
<anchor xml:id="c13e2d7"/>
</title>
<interlinear-gloss>
@@ -255,23 +253,23 @@
</interlinear-gloss>
</example>
<para>In
<xref linkend="example-random-id-qfin"/>, John's coming has been anticipated by the speaker. In
<xref linkend="example-random-id-qFiE"/> and
<xref linkend="example-random-id-qfiI"/>, no such anticipation has been made, but in
<xref linkend="example-random-id-qfiI"/> the lack-of-anticipation goes no further - in
<xref linkend="example-random-id-qFiE"/>, it amounts to actual surprise.</para>
<para>It is not possible to firmly distinguish the pure emotion words beginning with
- <quote>o</quote> or
- <jbophrase>i</jbophrase> from those beginning with
- <quote>u</quote>, but in general they represent more complex, more ambivalent, or more difficult emotions.</para>
+ <jbophrase role="letteral">o</jbophrase> or
+ <jbophrase role="letteral">i</jbophrase> from those beginning with
+ <jbophrase role="letteral">u</jbophrase>, but in general they represent more complex, more ambivalent, or more difficult emotions.</para>
<programlisting xml:space="preserve">
.o'a pride modesty shame
<!-- skip cmavo list automation -->
.o'e closeness detachment distance
.oi complaint/pain doing OK pleasure
.o'i caution boldness rashness
.o'o patience mere tolerance anger
.o'u relaxation composure stress
@@ -280,21 +278,21 @@
<example role="interlinear-gloss-example" xml:id="example-random-id-ch2s">
<title>
<anchor xml:id="c13e2d10"/>
</title>
<interlinear-gloss>
<jbo>.oi la djan. klama</jbo>
<gloss>[Complaint!] John is coming.</gloss>
</interlinear-gloss>
</example>
<para>Here the speaker is distressed or discomfited over John's coming. The word
- <jbophrase>.oi</jbophrase> is derived from the Yiddish word
+ <jbophrase role="diphthong">.oi</jbophrase> is derived from the Yiddish word
<quote>oy</quote> of similar meaning. It is the only cmavo with a Yiddish origin.</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-V8eD">
<title>
<anchor xml:id="c13e2d11"/>
</title>
<interlinear-gloss>
<jbo>.o'onai la djan. klama</jbo>
<gloss>[Anger!] John is coming!</gloss>
</interlinear-gloss>
@@ -328,26 +326,26 @@
<interlinear-gloss>
<jbo>.o'u la djan. klama</jbo>
<gloss>[Phew!] John is coming.</gloss>
</interlinear-gloss>
</example>
<para>In
<xref linkend="example-random-id-qfIR"/> and
<xref linkend="example-random-id-qFJf"/>, John's arrival is no problem: in the former example, the speaker feels emotional distance from the situation; in the latter example, John's coming is actually a relief of some kind.</para>
<para>The pure emotion indicators beginning with
- <jbophrase>i</jbophrase> are those which could not be fitted into the
- <quote>u</quote> or
- <quote>o</quote> groups because there was a lack of room, so they are a mixed lot.
- <jbophrase>.ia</jbophrase>,
+ <jbophrase role="letteral">i</jbophrase> are those which could not be fitted into the
+ <jbophrase role="letteral">u</jbophrase> or
+ <jbophrase role="letteral">o</jbophrase> groups because there was a lack of room, so they are a mixed lot.
+ <jbophrase role="diphthong">.ia</jbophrase>,
<jbophrase>.i'a</jbophrase>,
- <jbophrase>.ie</jbophrase>, and
+ <jbophrase role="diphthong">.ie</jbophrase>, and
<jbophrase>.i'e</jbophrase> do not appear here, as they belong in
<xref linkend="cll_chapter13-section3"/> instead.</para>
<programlisting xml:space="preserve">
.ii fear nervousness security
<!-- skip cmavo list automation -->
.i'i togetherness privacy
.io respect disrespect
.i'o appreciation envy
.iu love no love lost hatred
@@ -410,41 +408,41 @@
<para> <indexterm type="general-imported"><primary>hypothetical world</primary></indexterm> <indexterm type="general-imported"><primary>internal world</primary></indexterm> <indexterm type="general-imported"><primary>propositional</primary><secondary>of attitudinals</secondary></indexterm> <indexterm type="general-imported"><primary>indicators</primary><secondary>placement of</secondary></indexterm> As mentioned at the beginning of
<xref linkend="cll_chapter13-section2"/>, attitudinals may be divided into two groups, the pure emotion indicators explained in that section, and a contrasting group which may be called the
<quote>propositional attitude indicators</quote>. These indicators establish an internal, hypothetical world which the speaker is reacting to, distinct from the world as it really is. Thus we may be expressing our attitude towards
<quote>what the world would be like if ...</quote>, or more directly stating our attitude towards making the potential world a reality.</para>
<para> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>propositional effect on claim</secondary></indexterm> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>propositional contrasted with emotional</secondary></indexterm> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>emotional contrasted with propositional</secondary></indexterm> In general, the bridi paraphrases of pure emotions look (in English) something like
<quote>I'm going to the market, and I'm happy about it</quote>. The emotion is present with the subject of the primary claim, but is logically independent of it. Propositional attitudes, though, look more like
<quote>I intend to go to the market</quote>, where the main claim is logically subordinate to the intention: I am not claiming that I am actually going to the market, but merely that I intend to.</para>
<para> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>i- series</secondary></indexterm> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>e- series</secondary></indexterm> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>a- series</secondary></indexterm> There is no sharp distinction between attitudinals beginning with
- <quote>a</quote> and those beginning with
- <jbophrase>e</jbophrase>; however, the original intent (not entirely realized due to the need to cram too many attitudes into too little space) was to make the members of the
- <quote>a</quote>-series the purer, more attitudinal realizers of a potential world, while the members of the
- <jbophrase>e</jbophrase>-series were more ambivalent or complex about the speaker's intention with regard to the predication. The relationship between the
- <quote>a</quote>-series and the
- <jbophrase>e</jbophrase>-series is similar to that between the
- <quote>u</quote>-series and the
- <quote>o</quote>-series, respectively. A few propositional attitude indicators overflowed into the
- <jbophrase>i</jbophrase>-series as well.</para>
+ <jbophrase role="letteral">a</jbophrase> and those beginning with
+ <jbophrase role="letteral">e</jbophrase>; however, the original intent (not entirely realized due to the need to cram too many attitudes into too little space) was to make the members of the
+ <jbophrase role="letteral">a</jbophrase>-series the purer, more attitudinal realizers of a potential world, while the members of the
+ <jbophrase role="letteral">e</jbophrase>-series were more ambivalent or complex about the speaker's intention with regard to the predication. The relationship between the
+ <jbophrase role="letteral">a</jbophrase>-series and the
+ <jbophrase role="letteral">e</jbophrase>-series is similar to that between the
+ <jbophrase role="letteral">u</jbophrase>-series and the
+ <jbophrase role="letteral">o</jbophrase>-series, respectively. A few propositional attitude indicators overflowed into the
+ <jbophrase role="letteral">i</jbophrase>-series as well.</para>
<para> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>logical language and</secondary></indexterm> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>propositional/emotional caveat</secondary></indexterm> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>emotional/propositional caveat</secondary></indexterm> In fact, the entire distinction between pure emotions and propositional attitudes is itself a bit shaky:
<jbophrase>.u'u</jbophrase> can be seen as a propositional attitude indicator meaning
<quote>I regret that ...</quote>, and
<jbophrase>.a'e</jbophrase> (discussed below) can be seen as a pure emotion meaning
<quote>I'm awake/aware</quote>. The division of the attitudinals into pure-emotion and propositional-attitude classes in this chapter is mostly by way of explanation; it is not intended to permit firm rulings on specific points. Attitudinals are the part of Lojban most distant from the
<quote>logical language</quote> aspect.</para>
<para>Here is the list of propositional attitude indicators grouped by initial letter, starting with those beginning with
- <quote>a</quote>:</para>
+ <jbophrase role="letteral">a</jbophrase>:</para>
<programlisting xml:space="preserve">
.a'a attentive inattentive avoiding
<!-- skip cmavo list automation -->
.a'e alertness exhaustion
.ai intent indecision refusal
.a'i effort no real effort repose
.a'o hope despair
@@ -528,24 +526,24 @@
<gloss>[no interest] you complain</gloss>
<en>I have no interest in your complaints.</en>
</interlinear-gloss>
</example>
<para> <indexterm type="lojban-word-imported"><primary>.a'ucu'i</primary></indexterm> <indexterm type="lojban-word-imported"><primary>.au</primary></indexterm> <indexterm type="lojban-word-imported"><primary>.a'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>.a'i</primary></indexterm> <indexterm type="lojban-word-imported"><primary>.ai</primary></indexterm> <indexterm type="lojban-word-imported"><primary>.a'enai</primary></indexterm> <indexterm type="lojban-word-imported"><primary>.a'a</primary></indexterm> (In a real-life situation, Examples 3.1-3.7 would also be decorated by various pure emotion indicators, certainly including
<jbophrase>.oicai</jbophrase>, but probably also
<jbophrase>.iucai</jbophrase>.)</para>
<para> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>rationale for</secondary></indexterm> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>contrasted with bridi</secondary></indexterm> Splitting off the attitude into an indicator allows the regular bridi grammar to do what it does best: express the relationships between concepts that are intended, desired, hoped for, or whatever. Rephrasing these examples to express the attitude as the main selbri would make for unacceptably heavyweight grammar.</para>
<para>Here are the propositional attitude indicators beginning with
- <jbophrase>e</jbophrase>, which stand roughly in the relation to those beginning with
- <quote>a</quote> as the pure-emotion indicators beginning with
- <quote>o</quote> do to those beginning with
- <quote>u</quote>- they are more complex or difficult:</para>
+ <jbophrase role="letteral">e</jbophrase>, which stand roughly in the relation to those beginning with
+ <jbophrase role="letteral">a</jbophrase> as the pure-emotion indicators beginning with
+ <jbophrase role="letteral">o</jbophrase> do to those beginning with
+ <jbophrase role="letteral">u</jbophrase>- they are more complex or difficult:</para>
<programlisting xml:space="preserve">
.e'a permission prohibition
<!-- skip cmavo list automation -->
.e'e competence incompetence
.ei obligation freedom
.e'i constraint independence resistance to constraint
.e'o request negative request
@@ -600,21 +598,21 @@
<title>
<anchor xml:id="c13e3d12"/>
</title>
<interlinear-gloss>
<jbo>.e'u do klama le panka</jbo>
<gloss>[suggestion] You go to-the park.</gloss>
<en>I suggest going to the park.</en>
</interlinear-gloss>
</example>
<para> <indexterm type="lojban-word-imported"><primary>.e'u</primary></indexterm> <indexterm type="lojban-word-imported"><primary>.e'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>.ei</primary></indexterm> <indexterm type="lojban-word-imported"><primary>.e'e</primary></indexterm> <indexterm type="lojban-word-imported"><primary>.e'a</primary></indexterm> Finally, the propositional attitude indicators beginning with
- <jbophrase>i</jbophrase>, which are the overflow from the other sets:</para>
+ <jbophrase role="letteral">i</jbophrase>, which are the overflow from the other sets:</para>
<programlisting xml:space="preserve">
.ia belief skepticism disbelief
<!-- skip cmavo list automation -->
.i'a acceptance blame
.ie agreement disagreement
.i'e approval non-approval disapproval
</programlisting>
<para>Still more examples (much, much later):</para>
<example xml:id="example-random-id-qfSU" role="interlinear-gloss-example">
@@ -685,22 +683,22 @@
<section xml:id="cll_chapter13-section4">
<title>Attitudes as scales</title>
<para> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>neutral</secondary></indexterm> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>negative</secondary></indexterm> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>positive</secondary></indexterm> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>scale of</secondary></indexterm> In Lojban, all emotions and attitudes are scales. These scales run from some extreme value (which we'll call
<quote>positive</quote>) to an opposite extreme (which we'll call
<quote>negative</quote>). In the tables above, we have seen three points on the scale:
<quote>positive</quote>, neutral, and
<quote>negative</quote>. The terms
<quote>positive</quote> and
<quote>negative</quote> are put into quotation marks because they are loaded words when applied to emotions, and the attitudinal system reflects this loading, which is a known cultural bias. Only two of the
<quote>positive</quote> words, namely
- <jbophrase>.ii</jbophrase> (fear) and
- <jbophrase>.oi</jbophrase> (pain/complaint), represent emotions commonly thought of as less
+ <jbophrase role="diphthong">.ii</jbophrase> (fear) and
+ <jbophrase role="diphthong">.oi</jbophrase> (pain/complaint), represent emotions commonly thought of as less
<quote>virtuous</quote> in most cases than their negative counterparts. But these two were felt to be instinctive, distinct, and very powerful emotions that needed to be expressible in a monosyllable when necessary, while their counterparts are less commonly expressed.</para>
<para> <indexterm type="general-imported"><primary>attitudinal scales</primary><secondary>rationale for assignment</secondary></indexterm> (Why the overt bias? Because there are a lot of attitudinals and they will be difficult to learn as an entire set. By aligning our scales arbitrarily, we give the monosyllable
<jbophrase>nai</jbophrase> a useful meaning and make it easier for a novice to recognize at least the positive or negative alignment of an indicator, if not the specific word. Other choices considered were
<quote>random</quote> orientation, which would have unknown biases and be difficult to learn, and orientation based on our guesses as to which scale orientations made the most frequent usages shorter, which would be biased in favor of American perceptions of
<quote>usefulness</quote>. If bias must exist in our indicator set, it might as well be a known bias that eases learning, and in addition might as well favor a harmonious and positive world-view.)</para>
<para> <indexterm type="lojban-word-imported"><primary>CAI selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>naicai</primary></indexterm> <indexterm type="lojban-word-imported"><primary>naisai</primary></indexterm> <indexterm type="lojban-word-imported"><primary>nairu'e</primary></indexterm> <indexterm type="lojban-word-imported"><primary>cu'i</primary></indexterm> <indexterm type="lojban-word-imported"><primary>ru'e</primary></indexterm> <indexterm type="lojban-word-imported"><primary>sai</primary></indexterm> <indexterm type="lojban-word-imported"><primary>cai</primary></indexterm> <indexterm type="general-imported"><primary>attitudinal scale</primary><secondary>seven-position</secondary></indexterm> <indexterm type="general-imported"><primary>emotional scale</primary></indexterm> In fact, though, each emotional scale has seven positions defined, three
<quote>positive</quote> ones (shown below on the left), three
<quote>negative</quote> ones (shown below on the right), and a neutral one indicating that no particular attitude on this scale is felt. The following chart indicates the seven positions of the scale and the associated cmavo. All of these cmavo, except
<jbophrase>nai</jbophrase>, are in selma'o CAI.</para>
@@ -928,21 +926,21 @@
</programlisting>
<para> <indexterm type="example-imported"><primary>self-orientation</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>attitudinal modifiers</primary></indexterm> It turned out that, once we had devised the six emotion categories, we also recognized some other commonalities among emotions. These tended to fit nicely on scales of their own, but generally tend not to be thought of as separate emotions. Some of these are self-explanatory, some need to be placed in context. Some of these tend to go well with only a few of the attitudinals, others go with nearly all of them. To really understand these modifiers, try to use them in combination with one or two of the attitudinals found in
<xref linkend="cll_chapter13-section2"/> and
<xref linkend="cll_chapter13-section3"/>, and see what emotional pictures you can build:</para>
<para> <indexterm type="lojban-word-imported"><primary>ga'inai</primary></indexterm> <indexterm type="lojban-word-imported"><primary>ga'i</primary></indexterm> <indexterm type="example-imported"><primary>condescension</primary><secondary>example</secondary></indexterm> <indexterm type="example-imported"><primary>deference</primary><secondary>example</secondary></indexterm> <indexterm type="example-imported"><primary>inferior</primary><secondary>example</secondary></indexterm> The cmavo
<jbophrase>ga'i</jbophrase> expresses the scale used to indicate condescension or polite deference; it is not respect in general, which is
- <jbophrase>.io</jbophrase>. Whatever it is attached to is marked as being below (for
+ <jbophrase role="diphthong">.io</jbophrase>. Whatever it is attached to is marked as being below (for
<jbophrase>ga'i</jbophrase>) or above (for
<jbophrase>ga'inai</jbophrase>) the speaker's rank or social position. Note that it is always the referent, not the speaker or listener, who is so marked: in order to mark the listener, the listener must appear in the sentence, as with
<jbophrase>doi ga'inai</jbophrase>, which can be appended to a statement addressed to a social superior.</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-Ercd">
<title>
<anchor xml:id="c13e7d1"/>
</title>
@@ -1019,21 +1017,21 @@
<quote>sinful</quote> in the eyes of most ethical systems. On the other hand, we often feel virtuous about our feelings - what we call righteous indignation might be
<jbophrase>o'onaivu'e</jbophrase>. Note that this is distinct from lack of guilt:
<jbophrase>.u'unai</jbophrase>.</para>
<para> <indexterm type="lojban-word-imported"><primary>se'i</primary></indexterm> The cmavo
<jbophrase>se'i</jbophrase> expresses the difference between selfishness and generosity, for example (in combination with
- <jbophrase>.au</jbophrase>):</para>
+ <jbophrase role="diphthong">.au</jbophrase>):</para>
<example xml:id="example-random-id-qFxm" role="interlinear-gloss-example">
<title>
<anchor xml:id="c13e7d5"/>
</title>
<interlinear-gloss>
<jbo>.ause'i</jbo>
<gloss>[desire] [self]</gloss>
<en>I want it!</en>
</interlinear-gloss>
</example>
@@ -1175,21 +1173,21 @@
<para> <indexterm type="general-imported"><primary>unspecified level of emotion</primary></indexterm> <indexterm type="general-imported"><primary>unstated emotion</primary></indexterm> For example,
<jbophrase>.ieru'e</jbophrase> expresses a weak positive value on the scale of agreement: the speaker agrees (presumably with the listener or with something else just stated), but with the least possible degree of intensity. But
<jbophrase>.ie ge'eru'e</jbophrase> expresses agreement (at an unspecified level), followed by some other unstated emotion which is felt at a weak level. A rough English equivalent of
<jbophrase>.ie ge'eru'e</jbophrase> might be
<quote>I agree, but ...</quote> where the
<quote>but</quote> is left hanging. (Again, attitudes aren't always expressed in English by English attitudinals.)</para>
<para> <indexterm type="general-imported"><primary>attitudinal indicators</primary><secondary>placement of scale in</secondary></indexterm> A scale variable similarly modifies the previous emotion word. You put the scale word for a root emotion word before a modifier, since the latter can have its own scale word. This merely maximizes the amount of information expressible. For example,
<jbophrase>.oinaicu'i ro'ucai</jbophrase> expresses a feeling midway between pain (
- <jbophrase>.oi</jbophrase>) and pleasure (
+ <jbophrase role="diphthong">.oi</jbophrase>) and pleasure (
<jbophrase>.oinai</jbophrase>) which is intensely sexual (
<jbophrase>ro'u</jbophrase>) in nature.</para>
<para> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>placement in sentences with "nai"</secondary></indexterm> <indexterm type="general-imported"><primary>attitudinal indicators</primary><secondary>placement of "nai" in</secondary></indexterm> The cmavo
<jbophrase>nai</jbophrase> is the most tightly bound modifier in the language: it always negates exactly one word - the preceding one. Of all the words used in indicator constructs,
<jbophrase>nai</jbophrase> is the only one with any meaning outside the indicator system. If you try to put an indicator between a non-indicator cmavo and its
<jbophrase>nai</jbophrase> negator, the
<jbophrase>nai</jbophrase> will end up negating the last word of the indicator. The result, though unambiguous, is not what you want. For example,</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-9BBA">
<title>
@@ -1231,25 +1229,25 @@
<jbophrase>ge'e</jbophrase> or a VV word must be used to prevent any modifiers from modifying the previous attitudinal.</para>
</section>
<section xml:id="cll_chapter13-section9">
<title>The uses of indicators</title>
<para> <indexterm type="lojban-word-imported"><primary>su</primary></indexterm> <indexterm type="lojban-word-imported"><primary>sa</primary></indexterm> <indexterm type="lojban-word-imported"><primary>si</primary></indexterm> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>external grammar</secondary></indexterm> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>grammar of placement in bridi</secondary></indexterm> The behavior of indicators in the
<quote>outside grammar</quote> is nearly as simple as their internal structure. Indicator groupings are identified immediately after the metalinguistic erasers
<jbophrase>si</jbophrase>,
- <quote>sa</quote>, and
+ <jbophrase>sa</jbophrase>, and
<jbophrase>su</jbophrase> and some, though not all, kinds of quotations. The details of such interactions are discussed in
<xref linkend="chapter-structure"/>.</para>
<para> <indexterm type="lojban-word-imported"><primary>zo</primary></indexterm> A group of indicators may appear anywhere that a single indicator may, except in those few situations (as in
- <quote>zo</quote> quotation, explained in
+ <jbophrase>zo</jbophrase> quotation, explained in
<xref linkend="chapter-structure"/>) where compound cmavo may not be used.</para>
<para> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>at beginning of text</secondary></indexterm> At the beginning of a text, indicators modify everything following them indefinitely: such a usage is taken as a raw emotional expression, and we normally don't turn off our emotions when we start and stop sentences. In every other place in an utterance, the indicator (or group) attaches to the word immediately to its left, and indicates that the attitude is being expressed concerning the object or concept to which the word refers.</para>
<para> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>affecting whole grammatical structures</secondary></indexterm> If the word that an indicator (or group) attaches to is itself a cmavo which governs a grammatical structure, then the indicator construct pertains to the referent of the entire structure. There is also a mechanism, discussed in
<xref linkend="chapter-structure"/>, for explicitly marking the range of words to which an indicator applies.</para>
<para> <indexterm type="general-imported"><primary>attitudinals</primary><secondary>referent uncertainty</secondary></indexterm> More details about the uses of indicators, and the way they interact with other specialized cmavo, are given in
<xref linkend="chapter-structure"/>. It is worth mentioning that real-world interpretation is not necessarily consistent with the formal scope rules. People generally express emotions when they feel them, with only a minimum of grammatical constraint on that expression; complexities of emotional expression are seldom logically analyzable. Lojban attempts to provide a systematic reference that could possibly be ingrained to an instinctive level. However, it should always be assumed that the referent of an indicator has some uncertainty.</para>
<para> <indexterm type="general-imported"><primary>multiple indicators</primary></indexterm> For example, in cases of multiple indicators expressed together, the combined form has some ambiguity of interpretation. It is possible to interpret the second indicator as expressing an attitude about the first, or to interpret both as expressing attitudes about the common referent. For example, in</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-Rs6P">
<title>
@@ -2066,31 +2064,31 @@
<jbophrase>jo'anai</jbophrase> means the same as
<jbophrase>na'i</jbophrase>, but is too long to serve as a convenient metalinguistic negator.</para>
<para> <indexterm type="lojban-word-imported"><primary>li'o</primary></indexterm> <indexterm type="general-imported"><primary>partial quotation</primary></indexterm> <indexterm type="general-imported"><primary>fragmentary text</primary></indexterm> The next two cmavo are used to assist in quoting texts written or spoken by others. It is often the case that we wish to quote only part of a text, or to supply additional material either by way of commentary or to make a fragmentary text grammatical. The cmavo
<jbophrase>li'o</jbophrase> serves the former function. It indicates that words were omitted from the quotation. What remains of the quotation must be grammatical, however, as
<jbophrase>li'o</jbophrase> does not serve any grammatical function. It cannot, for example, take the place of a missing selbri in a bridi, or supply the missing tail of a description sumti:
- <quote>le li'o</quote> in isolation is not grammatical.</para>
+ <jbophrase>le li'o</jbophrase> in isolation is not grammatical.</para>
<para> <indexterm type="lojban-word-imported"><primary>to'i</primary></indexterm> <indexterm type="lojban-word-imported"><primary>sei</primary></indexterm> <indexterm type="lojban-word-imported"><primary>sa'a</primary></indexterm> <indexterm type="general-imported"><primary>sa'a</primary><secondary>interaction with to'i</secondary></indexterm> <indexterm type="general-imported"><primary>sa'a</primary><secondary>interaction with sei</secondary></indexterm> <indexterm type="general-imported"><primary>sa'a</primary><secondary>interaction with li'o</secondary></indexterm> <indexterm type="general-imported"><primary>editorial insertion</primary><secondary>with "sa'a</secondary></indexterm> The cmavo
<jbophrase>sa'a</jbophrase> indicates in a quotation that the marked word or construct was not actually expressed, but is inserted for editorial, narrative, or grammatical purposes. Strictly, even a
<jbophrase>li'o</jbophrase> should appear in the form
<jbophrase>li'osa'a</jbophrase>, since the
<jbophrase>li'o</jbophrase> was not part of the original quotation. In practice, this and other forms which are already associated with metalinguistic expressions, such as
- <quote>sei</quote> (of selma'o SEI) or
+ <jbophrase>sei</jbophrase> (of selma'o SEI) or
<jbophrase>to'i</jbophrase> (of selma'o TO) need not be marked except where confusion might result.</para>
<para> <indexterm type="general-imported"><primary>sa'a</primary><secondary>editorial insertion of text already containing sa'a</secondary></indexterm> <indexterm type="general-imported"><primary>editorial insertion</primary><secondary>of text already containing sa'a</secondary></indexterm> In the rare case that the quoted material already contains one or more instances of
<jbophrase>sa'a</jbophrase>, they can be changed to
<jbophrase>sa'asa'a</jbophrase>.</para>
<para> <indexterm type="lojban-word-imported"><primary>xu</primary></indexterm> <indexterm type="general-imported"><primary>questions</primary><secondary>with "xu"</secondary></indexterm> <indexterm type="general-imported"><primary>truth questions</primary></indexterm> <indexterm type="general-imported"><primary>yes/no questions</primary></indexterm> The cmavo
<jbophrase>xu</jbophrase> marks truth questions, which are discussed in detail in
<xref linkend="chapter-negation"/>. In general,
<jbophrase>xu</jbophrase> may be translated
<quote>Is it true that ... ?</quote> and questions whether the attached bridi is true. When
@@ -2126,21 +2124,21 @@
<jbophrase>blanu</jbophrase> in
<xref linkend="example-random-id-rXiR"/> could mean
<quote>sad</quote> (as in English) or something completely different.</para>
<para> <indexterm type="lojban-word-imported"><primary>pe'anai</primary></indexterm> <indexterm type="general-imported"><primary>literally</primary></indexterm> The negated form,
<jbophrase>pe'anai</jbophrase>, indicates that what has been said is to be interpreted literally, in the usual way for Lojban; natural-language intuition is to be ignored.</para>
<para> <indexterm type="example-imported"><primary>heartburn</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>culturally dependent lujvo</primary></indexterm> <indexterm type="general-imported"><primary>figurative lujvo</primary><secondary>place structure</secondary></indexterm> <indexterm type="general-imported"><primary>figurative lujvo</primary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>place structure of figurative lujvo</secondary></indexterm> Alone among the cmavo of selma'o UI,
<jbophrase>pe'a</jbophrase> has a rafsi, namely
- <quote>pev</quote>. This rafsi is used in forming figurative (culturally dependent) lujvo, whose place structure need have nothing to do with the place structure of the components. Thus
+ <jbophrase role="rafsi">pev</jbophrase>. This rafsi is used in forming figurative (culturally dependent) lujvo, whose place structure need have nothing to do with the place structure of the components. Thus
<jbophrase>risnyjelca</jbophrase> (heart burn) might have a place structure like:</para>
<programlisting xml:space="preserve">
x1 is the heart of x2, burning in atmosphere x3 at temperature x4
</programlisting>
<para>whereas
<jbophrase>pevrisnyjelca</jbophrase>, explicitly marked as figurative, might have the place structure:</para>
<programlisting xml:space="preserve">
x1 is indigestion/heartburn suffered by x2
</programlisting>
@@ -2201,46 +2199,46 @@
<en>I know who goes to the store.</en>
</interlinear-gloss>
</example>
</section>
<section xml:id="cll_chapter13-section14">
<title>Vocative scales</title>
<para> <indexterm type="lojban-word-imported"><primary>COI selma'o</primary></indexterm> <indexterm type="general-imported"><primary>direct address</primary></indexterm> <indexterm type="general-imported"><primary>"la"</primary><secondary>contrasted with vocatives</secondary></indexterm> <indexterm type="general-imported"><primary>vocatives</primary><secondary>contrasted with "la"</secondary></indexterm> <indexterm type="general-imported"><primary>vocatives</primary><secondary>definition</secondary></indexterm>
<quote>Vocatives</quote> are words used to address someone directly; they precede and mark a name used in direct address, just as
- <quote>la</quote> (and the other members of selma'o LA) mark a name used to refer to someone. The vocatives actually are indicators - in fact, discursives - but the need to tie them to names and other descriptions of listeners requires them to be separated from selma'o UI. But like the cmavo of UI, the members of selma'o COI can be
+ <jbophrase>la</jbophrase> (and the other members of selma'o LA) mark a name used to refer to someone. The vocatives actually are indicators - in fact, discursives - but the need to tie them to names and other descriptions of listeners requires them to be separated from selma'o UI. But like the cmavo of UI, the members of selma'o COI can be
<quote>negated</quote> with
<jbophrase>nai</jbophrase> to get the opposite part of the scale.</para>
<para> <indexterm type="general-imported"><primary>vocatives</primary><secondary>rationale for redundancy</secondary></indexterm> <indexterm type="general-imported"><primary>redundancy</primary><secondary>effect on vocative design</secondary></indexterm> Because of the need for redundancy in noisy environments, the Lojban design does not compress the vocatives into a minimum number of scales. Doing so would make a non-redundant
<jbophrase>nai</jbophrase> too often vital to interpretation of a protocol signal, as explained later in this section.</para>
<para> <indexterm type="lojban-word-imported"><primary>do'u</primary></indexterm> <indexterm type="lojban-word-imported"><primary>DOhU selma'o</primary></indexterm> <indexterm type="general-imported"><primary>vocatives</primary><secondary>grammar overview</secondary></indexterm> The grammar of vocatives is explained in
<xref linkend="chapter-sumti"/>; but in brief, a vocative may be followed by a name (without
- <quote>la</quote>), a description (without
- <quote>le</quote> or its relatives), a complete sumti, or nothing at all (if the addressee is obvious from the context). There is an elidable terminator,
- <quote>do'u</quote> (of selma'o DOhU) which is almost never required unless no name (or other indication of the addressee) follows the vocative.</para>
+ <jbophrase>la</jbophrase>), a description (without
+ <jbophrase>le</jbophrase> or its relatives), a complete sumti, or nothing at all (if the addressee is obvious from the context). There is an elidable terminator,
+ <jbophrase>do'u</jbophrase> (of selma'o DOhU) which is almost never required unless no name (or other indication of the addressee) follows the vocative.</para>
<para> <indexterm type="general-imported"><primary>vocatives</primary><secondary>and definition of "you"</secondary></indexterm> <indexterm type="general-imported"><primary>you</primary><secondary>defining</secondary></indexterm> Using any vocative except
<jbophrase>mi'e</jbophrase> (explained below) implicitly defines the meaning of the pro-sumti
<jbophrase>do</jbophrase>, as the whole point of vocatives is to specify the listener, or at any rate the desired listener - even if the desired listener isn't listening! We will use the terms
<quote>speaker</quote> and
<quote>listener</quote> for clarity, although in written Lojban the appropriate terms would be
<quote>writer</quote> and
<quote>reader</quote>.</para>
<para> <indexterm type="general-imported"><primary>vocatives</primary><secondary>notation convention symbol "X"</secondary></indexterm> In the following list of vocatives, the translations include the symbol X. This represents the name (or identifying description, or whatever) of the listener.</para>
<para> <indexterm type="lojban-word-imported"><primary>DOI selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>doi</primary></indexterm> <indexterm type="general-imported"><primary>doi</primary><secondary>effect on pause before name</secondary></indexterm> <indexterm type="general-imported"><primary>pause before name</primary><secondary>effect of doi</secondary></indexterm> The cmavo
<jbophrase>doi</jbophrase> is the general-purpose vocative. Unlike the cmavo of selma'o COI, explained below,
<jbophrase>doi</jbophrase> can precede a name directly without an intervening pause. It is not considered a scale, and
- <quote>doinai</quote> is not grammatical. In general,
+ <jbophrase>doinai</jbophrase> is not grammatical. In general,
<jbophrase>doi</jbophrase> needs no translation in English (we just use names by themselves without any preceding word, although in poetic styles we sometimes say
<quote>Oh X</quote>, which is equivalent to
<jbophrase>doi</jbophrase>). One may attach an attitudinal to
<jbophrase>doi</jbophrase> to express various English vocatives. For example,
<jbophrase>doi .io</jbophrase> means
<quote>Sir/Madam!</quote>, whereas
<jbophrase>doi .ionai</jbophrase> means
<quote>You there!</quote>.</para>
<para> <indexterm type="general-imported"><primary>COI selma'o</primary><secondary>effect on pause before name</secondary></indexterm> <indexterm type="general-imported"><primary>pause before name</primary><secondary>effect of vocatives of COI</secondary></indexterm> All members of selma'o COI require a pause when used immediately before a name, in order to prevent the name from absorbing the COI word. This is unlike selma'o DOI and LA, which do not require pauses because the syllables of these cmavo are not permitted to be embedded in a Lojban name. When calling out to someone, this is fairly natural, anyway.
@@ -2382,24 +2380,24 @@
<quote>Thank you</quote>.</para>
<programlisting xml:space="preserve">
vi'o will comply will not comply
<!-- skip cmavo list automation -->
</programlisting>
<para> <indexterm type="lojban-word-imported"><primary>vi'o</primary></indexterm> <indexterm type="general-imported"><primary>vi'o</primary><secondary>contrasted with je'e</secondary></indexterm> <indexterm type="general-imported"><primary>je'e</primary><secondary>contrasted with vi'o</secondary></indexterm>
<quote>Wilco, X</quote>,
<quote>I understand and will comply</quote>. Similar to
<jbophrase>je'e</jbophrase> but signals an intention (similar to
- <jbophrase>.ai</jbophrase>) to comply with the other speaker's request. This cmavo is the main way of saying
+ <jbophrase role="diphthong">.ai</jbophrase>) to comply with the other speaker's request. This cmavo is the main way of saying
<quote>OK</quote> in Lojban, in the usual sense of
<quote>Agreed!</quote>, although
- <jbophrase>.ie</jbophrase> carries some of the same meaning. The negative form indicates that the message was received but that you will not comply: a very colloquial version is
+ <jbophrase role="diphthong">.ie</jbophrase> carries some of the same meaning. The negative form indicates that the message was received but that you will not comply: a very colloquial version is
<quote>No way!</quote>.</para>
<programlisting xml:space="preserve">
ke'o [krefu] please repeat no repeat needed
<!-- skip cmavo list automation -->
</programlisting>
<para> <indexterm type="lojban-word-imported"><primary>ke'o</primary></indexterm> <indexterm type="general-imported"><primary>ki'a</primary><secondary>compared to ke'o</secondary></indexterm> <indexterm type="general-imported"><primary>ke'o</primary><secondary>compared to ki'a</secondary></indexterm>
<quote>What did you say, X?</quote>; a request for repetition or clarification due to unsuccessful receipt or understanding. This is the vocative equivalent of
<jbophrase>ki'a</jbophrase>, and is related to
<jbophrase>je'enai</jbophrase>. The negative form may be rendered
@@ -2444,21 +2442,21 @@
<quote>over and out</quote>. This form of translation does not mean that Lojban is a language of CB enthusiasts, but rather that in most natural languages these forms are so well handled by the context that only in specific domains (like speaking on the radio) do they need special words. In Lojban, dependence on the context can be dangerous, as speaker and listener may not share the right context, and so the vocatives provide a formal protocol for use when it is appropriate. Other appropriate contexts include computer communications and parliamentary procedure: in the latter context, the protocol question
<jbophrase>ta'apei</jbophrase> would mean
<quote>Will the speaker yield?</quote></para>
</section>
<section xml:id="cll_chapter13-section15">
<title>A sample dialogue</title>
<para>The following dialogue in Lojban illustrates the uses of attitudinals and protocol vocatives in conversation. The phrases enclosed in
- <quote>sei ... se'u</quote> indicate the speaker of each sentence.</para>
+ <jbophrase>sei ... se'u</jbophrase> indicate the speaker of each sentence.</para>
<example xml:id="example-random-id-qg4j" role="interlinear-gloss-example">
<title>
<anchor xml:id="c13e15d1"/>
</title>
<interlinear-gloss>
<jbo>la rik. .e la .alis. nerkla le kafybarja</jbo>
<gloss>Rick and Alice in-go to-the coffee-bar.</gloss>
<en>Rick and Alice go into the coffee bar.</en>
</interlinear-gloss>
</example>
@@ -2722,21 +2720,21 @@
</interlinear-gloss>
</example>
</section>
<section xml:id="cll_chapter13-section16">
<title>Tentative conclusion</title>
<para> <indexterm type="general-imported"><primary>indicators</primary><secondary>ramifications</secondary></indexterm> <indexterm type="general-imported"><primary>aliens</primary><secondary>communication with</secondary></indexterm> <indexterm type="general-imported"><primary>Kzinti</primary><secondary>communication with</secondary></indexterm> The exact ramifications of the indicator system in actual usage are unknown. There has never been anything like it in natural language before. The system provides great potential for emotional expression and transcription, from which significant Sapir-Whorf effects can be anticipated. When communicating across cultural boundaries, where different indicators are often used for the same emotion, accidental offense can be avoided. If we ever ran into an alien race, a culturally neutral language of emotion could be vital. (A classic example, taken from the science fiction of Larry Niven, is to imagine speaking Lojban to the carnivorous warriors called Kzinti, noting that a human smile bares the teeth, and could be seen as an intent to attack.) And for communicating emotions to computers, when we cannot identify all of the signals involved in subliminal human communication (things like body language are also cultural), a system like this is needed.</para>
<para> <indexterm type="general-imported"><primary>indicators</primary><secondary>rationale for selection</secondary></indexterm> We have tried to err on the side of overkill. There are distinctions possible in this system that no one may care to make in any culture. But it was deemed more neutral to overspecify and let usage decide, than to choose a limited set and constrain emotional expression. For circumstances in which even the current indicator set is not enough, it is possible using the cmavo
- <quote>sei</quote>, explained in
+ <jbophrase>sei</jbophrase>, explained in
<xref linkend="chapter-structure"/>, to create metalinguistic comments that act like indicators.</para>
<para> <indexterm type="general-imported"><primary>indicators</primary><secondary>evolutionary development of</secondary></indexterm> We envision an evolutionary development. At this point, the system is little more than a mental toy. Many of you who read this will try playing around with various combinations of indicators, trying to figure out what emotions they express and when the expressions might be useful. You may even find an expression for which there currently is no good English word and start using it. Why not, if it helps you express your feelings?</para>
<para>There will be a couple dozen of these used pretty much universally – mostly just simple attitudinals with, at most, intensity markers. These are the ones that will quickly be expressed at the subconscious level. But every Lojbanist who plays with the list will bring in a couple of new words. Poets will paint emotional pictures, and people who identify with those pictures will use the words so created for their own experiences.</para>
<para>Just as a library of tanru is built up, so will a library of attitudes be built. Unlike the tanru, though, the emotional expressions are built on some fairly nebulous root emotions - words that cannot be defined with the precision of the gismu. The emotion words of Lojban will very quickly take on a life of their own, and the outline given here will evolve into a true system of emotions.</para>
<para> <indexterm type="general-imported"><primary>emotions</primary><secondary>research using indicators</secondary></indexterm> <indexterm type="general-imported"><primary>emotions</primary><secondary>recording using indicators</secondary></indexterm> There are several theories as to the nature of emotion, and they change from year to year as we learn more about ourselves. Whether or not Lojban's additive/scalar emotional model is an accurate model for human emotions, it does support the linguistic needs for expressing those emotions. Researchers may learn more about the nature of human emotions by exploring the use of the system by Lojban speakers. They also may be able to use the Lojban system as a means for more clearly recording emotions.</para>
<para> <indexterm type="general-imported"><primary>emotions</primary><secondary>cultural bias of expression</secondary></indexterm> The full list of scales and attitudes will probably not be used until someone speaks the language from birth. Until then, people will use the attitudes that are important to them. In this way, we counter cultural bias - if a culture is prone to recognizing and/or expressing certain emotions more than others, its members will use only those out of the enormous set available. If a culture hides certain emotions, its members simply won't express them.</para>
<para> <indexterm type="general-imported"><primary>Sapir-Whorf effects</primary><secondary>and emotional indicators</secondary></indexterm> Perhaps native Lojban speakers will be more expressively clear about their emotions than others. Perhaps they will feel some emotions more strongly than others in ways that can be correlated with the word choices; any difference from the norms of other cultures could be significant. Psychologists have devised elaborate tests for measuring attitudes and personality; this may be the easiest area in which to detect any systematic cultural effect of the type sought to confirm Sapir-Whorf, simply because we already have tools in existence to test it. Because Lojban is unique among languages in having such extensive and expressive indicators, it is likely that a Sapir-Whorf effect will occur and will be recognized.</para>
diff --git a/todocbook/3.xml b/todocbook/3.xml
index 30a227d..6e20e63 100644
--- a/todocbook/3.xml
+++ b/todocbook/3.xml
@@ -2072,130 +2072,130 @@
<citation>The Lord Of The Rings</citation>, has been devised for Lojban. The following mapping, which closely resembles that used for Westron, will be meaningful only to those who have read those appendixes. In brief, the tincotéma and parmatéma are used in the conventional ways; the calmatéma represents palatal consonants, and the quessetéma represents velar consonants.</para>
<informaltable>
<tgroup cols="2">
<colspec colnum="1" colname="col1"/>
<colspec colnum="2" colname="col2"/>
<tbody>
<row>
<entry><jbophrase role="letteral">t</jbophrase></entry>
- <entry><phrase xml:lang="art">tinco</phrase></entry>
+ <entry><phrase xml:lang="qya">tinco</phrase></entry>
</row>
<row>
<entry>-</entry>
- <entry><phrase xml:lang="art">calma</phrase></entry>
+ <entry><phrase xml:lang="qya">calma</phrase></entry>
</row>
<row>
<entry><jbophrase role="letteral">d</jbophrase></entry>
- <entry><phrase xml:lang="art">ando</phrase></entry>
+ <entry><phrase xml:lang="qya">ando</phrase></entry>
</row>
<row>
<entry>-</entry>
- <entry><phrase xml:lang="art">anga</phrase></entry>
+ <entry><phrase xml:lang="qya">anga</phrase></entry>
</row>
<row>
<entry>-</entry>
- <entry><phrase xml:lang="art">thule</phrase></entry>
+ <entry><phrase xml:lang="qya">thule</phrase></entry>
</row>
<row>
<entry><jbophrase role="letteral">c</jbophrase></entry>
- <entry><phrase xml:lang="art">harma</phrase></entry>
+ <entry><phrase xml:lang="qya">harma</phrase></entry>
</row>
<row>
<entry>-</entry>
- <entry><phrase xml:lang="art">anto</phrase></entry>
+ <entry><phrase xml:lang="qya">anto</phrase></entry>
</row>
<row>
<entry><jbophrase role="letteral">j</jbophrase></entry>
- <entry><phrase xml:lang="art">anca</phrase></entry>
+ <entry><phrase xml:lang="qya">anca</phrase></entry>
</row>
<row>
<entry><jbophrase role="letteral">n</jbophrase></entry>
- <entry><phrase xml:lang="art">numen</phrase></entry>
+ <entry><phrase xml:lang="qya">numen</phrase></entry>
</row>
<row>
<entry>-</entry>
- <entry><phrase xml:lang="art">noldo</phrase></entry>
+ <entry><phrase xml:lang="qya">noldo</phrase></entry>
</row>
<row>
<entry><jbophrase role="letteral">r</jbophrase></entry>
- <entry><phrase xml:lang="art">ore</phrase></entry>
+ <entry><phrase xml:lang="qya">ore</phrase></entry>
</row>
<row>
<entry><jbophrase role="letteral">i</jbophrase></entry>
- <entry><phrase xml:lang="art">anna</phrase></entry>
+ <entry><phrase xml:lang="qya">anna</phrase></entry>
</row>
</tbody>
</tgroup>
<tgroup cols="2">
<colspec colnum="1" colname="col1"/>
<colspec colnum="2" colname="col2"/>
<tbody>
<row>
<entry><jbophrase role="letteral">p</jbophrase></entry>
- <entry><phrase xml:lang="art">parma</phrase></entry>
+ <entry><phrase xml:lang="qya">parma</phrase></entry>
</row>
<row>
<entry><jbophrase role="letteral">k</jbophrase></entry>
- <entry><phrase xml:lang="art">quesse</phrase></entry>
+ <entry><phrase xml:lang="qya">quesse</phrase></entry>
</row>
<row>
<entry><jbophrase role="letteral">b</jbophrase></entry>
- <entry><phrase xml:lang="art">umbar</phrase></entry>
+ <entry><phrase xml:lang="qya">umbar</phrase></entry>
</row>
<row>
<entry><jbophrase role="letteral">g</jbophrase></entry>
- <entry><phrase xml:lang="art">ungwe</phrase></entry>
+ <entry><phrase xml:lang="qya">ungwe</phrase></entry>
</row>
<row>
<entry><jbophrase role="letteral">f</jbophrase></entry>
- <entry><phrase xml:lang="art">formen</phrase></entry>
+ <entry><phrase xml:lang="qya">formen</phrase></entry>
</row>
<row>
<entry><jbophrase role="letteral">x</jbophrase></entry>
- <entry><phrase xml:lang="art">hwesta</phrase></entry>
+ <entry><phrase xml:lang="qya">hwesta</phrase></entry>
</row>
<row>
<entry><jbophrase role="letteral">v</jbophrase></entry>
- <entry><phrase xml:lang="art">ampa</phrase></entry>
+ <entry><phrase xml:lang="qya">ampa</phrase></entry>
</row>
<row>
<entry>-</entry>
- <entry><phrase xml:lang="art">unque</phrase></entry>
+ <entry><phrase xml:lang="qya">unque</phrase></entry>
</row>
<row>
<entry><jbophrase role="letteral">m</jbophrase></entry>
- <entry><phrase xml:lang="art">malta</phrase></entry>
+ <entry><phrase xml:lang="qya">malta</phrase></entry>
</row>
<row>
<entry>-</entry>
- <entry><phrase xml:lang="art">nwalme</phrase></entry>
+ <entry><phrase xml:lang="qya">nwalme</phrase></entry>
</row>
<row>
<entry><jbophrase role="letteral">u</jbophrase></entry>
- <entry><phrase xml:lang="art">vala</phrase></entry>
+ <entry><phrase xml:lang="qya">vala</phrase></entry>
</row>
<row>
<entry>-</entry>
- <entry><phrase xml:lang="art">vilya</phrase></entry>
+ <entry><phrase xml:lang="qya">vilya</phrase></entry>
</row>
</tbody>
</tgroup>
</informaltable>
<para>The letters
- <quote xml:lang="art">vala</quote> and
- <quote xml:lang="art">anna</quote> are used for
+ <quote xml:lang="qya">vala</quote> and
+ <quote xml:lang="qya">anna</quote> are used for
<jbophrase role="letteral">u</jbophrase> and
<jbophrase role="letteral">i</jbophrase> only when those letters are used to represent glides. Of the additional letters,
<jbophrase role="letteral">r</jbophrase>,
<jbophrase role="letteral">l</jbophrase>,
<jbophrase role="letteral">s</jbophrase>, and
<jbophrase role="letteral">z</jbophrase> are written with
- <quote xml:lang="art">rómen</quote>,
- <quote xml:lang="art">lambe</quote>,
- <quote xml:lang="art">silme</quote>, and
- <quote xml:lang="art">áre</quote>/
- <quote xml:lang="art">esse</quote> respectively; the inverted forms are used as free variants.</para>
- <para>Lojban, like Quenya, is a vowel-last language, so tehtar are read as following the tengwar on which they are placed. The conventional tehtar are used for the five regular vowels, and the dot below for <jbophrase role="letteral">y</jbophrase>. The Lojban apostrophe is represented by <quote xml:lang="art">halla</quote>. There is no equivalent of the Lojban comma or period.</para>
+ <quote xml:lang="qya">rómen</quote>,
+ <quote xml:lang="qya">lambe</quote>,
+ <quote xml:lang="qya">silme</quote>, and
+ <quote xml:lang="qya">áre</quote>/
+ <quote xml:lang="qya">esse</quote> respectively; the inverted forms are used as free variants.</para>
+ <para>Lojban, like Quenya, is a vowel-last language, so tehtar are read as following the tengwar on which they are placed. The conventional tehtar are used for the five regular vowels, and the dot below for <jbophrase role="letteral">y</jbophrase>. The Lojban apostrophe is represented by <quote xml:lang="qya">halla</quote>. There is no equivalent of the Lojban comma or period.</para>
</section>
</chapter>
commit 71f32a122ff534978eee6622a702e5e56fed8f9d
Author: Eitan Postavsky <eitanp32@gmail.com>
Date: Mon Jan 10 16:45:58 2011 -0500
Chapter 12: section titles.
diff --git a/todocbook/12.xml b/todocbook/12.xml
index c306197..b29ae59 100644
--- a/todocbook/12.xml
+++ b/todocbook/12.xml
@@ -1,13 +1,13 @@
<chapter xml:id="chapter-lujvo">
<title>Dog House And White House: Determining lujvo Place Structures</title>
- <section xml:id="cll_chapter12-section1">
+ <section xml:id="section-why-lujvo">
<title>Why have lujvo?</title>
<para>The Lojban vocabulary is founded on its list of 1350-plus gismu, made up by combining word lists from various sources. These gismu are not intended to be either a complete vocabulary for the language nor a minimal list of semantic primitives. Instead, the gismu list serves as a basis for the creation of compound words, or lujvo. The intention is that (except in certain semantically broad but shallow fields such as cultures, nations, foods, plants, and animals) suitable lujvo can be devised to cover the ten million or so concepts expressible in all the world's languages taken together. Grammatically, lujvo behave just like gismu: they have place structures and function as selbri.</para>
@@ -49,21 +49,21 @@
<para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>cmavo incorporation</secondary></indexterm> If the tanru includes connective cmavo such as
<jbophrase>bo</jbophrase>,
<jbophrase>ke</jbophrase>,
<jbophrase>ke'e</jbophrase>, or
<jbophrase>je</jbophrase>, or conversion or abstraction cmavo such as
<jbophrase>se</jbophrase> or
<jbophrase>nu</jbophrase>, there are ways of incorporating them into the lujvo as well. Sometimes this makes the lujvo excessively long; if so, the cmavo may be dropped. This leads to the possibility that more than one tanru could produce the same lujvo. Typically, however, only one of the possible tanru is useful enough to justify making a lujvo for it.</para>
<para>The exact workings of the lujvo-making algorithm, which takes a tanru built from gismu (and possibly cmavo) and produces a lujvo from it, are described in
<xref linkend="chapter-morphology"/>.</para>
</section>
- <section xml:id="cll_chapter12-section2">
+ <section xml:id="section-tanru-meanings">
<title>The meaning of tanru: a necessary detour</title>
<para>The meaning of a lujvo is controlled by - but is not the same as - the meaning of the tanru from which the lujvo was constructed. The tanru corresponding to a lujvo is called its
<jbophrase>veljvo</jbophrase> in Lojban, and since there is no concise English equivalent, that term will be used in this chapter. Furthermore, the left (modifier) part of a tanru will be called the
<jbophrase>seltau</jbophrase>, and the right (modified) part the
<jbophrase>tertau</jbophrase>, following the usage of
<xref linkend="chapter-selbri"/>. For brevity, we will speak of the seltau or tertau of a lujvo, meaning of course the seltau or tertau of the veljvo of that lujvo. (If this terminology is confusing, substituting
<quote>modifier</quote> for
<jbophrase>seltau</jbophrase> and
<quote>modified</quote> for
@@ -148,21 +148,21 @@
</example>
<para> <indexterm type="general-imported"><primary>derogatory terms</primary></indexterm> Not the most elegant sentence ever written in either Lojban or English. Yet if there is any relation at all between Spot and the White House,
<xref linkend="example-random-id-tUDa"/> is arguably true. If we concentrate on just one type of relation in interpreting the tanru
<jbophrase>gerku zdani</jbophrase>, then the meaning of
<jbophrase>gerku zdani</jbophrase> changes. So if we understand
<jbophrase>gerku zdani</jbophrase> as having the same meaning as the English word
<quote>doghouse</quote>, the White House would no longer be a
<jbophrase>gerku zdani</jbophrase> with respect to Spot, because as far as we know Spot does not actually live in the White House, and the White House is not a doghouse (derogatory terms for incumbents notwithstanding).</para>
</section>
- <section xml:id="cll_chapter12-section3">
+ <section xml:id="section-lujvo-meanings">
<title>The meaning of lujvo</title>
<para>This is a fairly long way to go to try and work out how to say
<quote>doghouse</quote>! The reader can take heart; we're nearly there. Recall that one of the components involved in fixing the meaning of a tanru - the one left deliberately vague - is the precise relation between the tertau and the seltau. Indeed, fixing this relation is tantamount to giving an interpretation to the ambiguous tanru.</para>
<para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>and seltau/tertau relationship</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>interpreting</secondary></indexterm> <indexterm type="general-imported"><primary>disambiguated instance</primary></indexterm> A lujvo is defined by a single disambiguated instance of a tanru. That is to say, when we try to design the place structure of a lujvo, we don't need to try to discover the relation between the tertau and the seltau. We already know what kind of relation we're looking for; it's given by the specific need we wish to express, and it determines the place structure of the lujvo itself.</para>
<para>Therefore, it is generally not appropriate to simply devise lujvo and decide on place structures for them without considering one or more specific usages for the coinage. If one does not consider specifics, one will be likely to make erroneous generalizations on the relationship r.</para>
<para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>design consideration for relationship</secondary></indexterm> The insight driving the rest of this chapter is this: while the relation expressed by a tanru can be very distant (e.g. Spot chasing Socks, above), the relationship singled out for disambiguation in a lujvo should be quite close. This is because lujvo-making, paralleling natural language compounding, picks out the most salient relationship r between a tertau place and a seltau place to be expressed in a single word. The relationship
<quote>dog chases cat owned by daughter of person living in house</quote> is too distant, and too incidental, to be likely to need expression as a single short word; the relationship
<quote>dog lives in house</quote> is not. From all the various interpretations of
<jbophrase>gerku zdani</jbophrase>, the person creating
@@ -173,21 +173,21 @@
<jbophrase>le gerku</jbophrase>, the most obvious relation to pick is the very relation named by the tertau,
<jbophrase>zdani</jbophrase>: the relation between a home and its dweller. As a result, the object which fills the first place of
<jbophrase>gerku</jbophrase> (the dog) also fills the second place of
<jbophrase>zdani</jbophrase> (the house-dweller).</para>
<para> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>dropping redundant places</secondary></indexterm> The seltau-tertau relationship in the veljvo is expressed by the seltau or tertau predicate itself. Therefore, at least one of the seltau places is going to be equivalent to a tertau place. This place is thus redundant, and can be dropped from the place structure of the lujvo. As a corollary, the precise relationship between the veljvo components can be implicitly determined by finding one or more places to overlap in this way.</para>
<para>So what is the place structure of
<jbophrase>gerzda</jbophrase>? We're left with three places, since the dweller, the
<jbophrase>se zdani</jbophrase>, turned out to be identical to the dog, the
<jbophrase>gerku</jbophrase>. We can proceed as follows:</para>
<para> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>notation conventions</secondary></indexterm> (The notation introduced casually in
- <xref linkend="cll_chapter12-section2"/> will be useful in the rest of this chapter. Rather than using the regular x1, x2, etc. to represent places, we'll use the first letter of the relevant gismu in place of the
+ <xref linkend="section-tanru-meanings"/> will be useful in the rest of this chapter. Rather than using the regular x1, x2, etc. to represent places, we'll use the first letter of the relevant gismu in place of the
<quote>x</quote>, or more than one letter where necessary to resolve ambiguities. Thus, z1 is the first place of
<jbophrase>zdani</jbophrase>, and g2 is the second place of
<jbophrase>gerku</jbophrase>.)</para>
<para> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>explicated walk-through</secondary></indexterm> <indexterm type="general-imported"><primary>new notation</primary></indexterm> The place structure of
<jbophrase>zdani</jbophrase> is given as
<xref linkend="example-random-id-xcfi"/>, but is repeated here using the new notation:</para>
<para> <indexterm type="example-imported"><primary>doghouse</primary><secondary>example</secondary></indexterm> FIXME: TAG SPOT</para>
<example xml:id="example-random-id-95t5">
<title>
@@ -221,32 +221,32 @@
<para>or more comprehensively</para>
<example xml:id="example-random-id-Wx42">
<title>
<anchor xml:id="c12e3d5"/>
</title>
<para>z1 is a house for dweller/dog z2=g1 of breed g2</para>
</example>
<para>Despite the apparently conclusive nature of
<xref linkend="example-random-id-Wx42"/>, our task is not yet done: we still need to decide whether any of the remaining places should also be eliminated, and what order the lujvo places should appear in. These concerns will be addressed in the remainder of the chapter; but we are now equipped with the terminology needed for those discussions.</para>
</section>
- <section xml:id="cll_chapter12-section4">
+ <section xml:id="section-selecting-places">
<title>Selecting places</title>
<para> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>basis of</secondary></indexterm> The set of places of an ordinary lujvo are selected from the places of its component gismu. More precisely, the places of such a lujvo are derived from the set of places of the component gismu by eliminating unnecessary places, until just enough places remain to give an appropriate meaning to the lujvo. In general, including a place makes the concept expressed by a lujvo more general; excluding a place makes the concept more specific, because omitting the place requires assuming a standard value or range of values for it.</para>
<para> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>rationale for standardization</secondary></indexterm> It would be possible to design the place structure of a lujvo from scratch, treating it as if it were a gismu, and working out what arguments contribute to the notion to be expressed by the lujvo. There are two reasons arguing against doing so and in favor of the procedure detailed in this chapter.</para>
<para>The first is that it might be very difficult for a hearer or reader, who has no preconceived idea of what concept the lujvo is intended to convey, to work out what the place structure actually is. Instead, he or she would have to make use of a lujvo dictionary every time a lujvo is encountered in order to work out what a
<jbophrase>se jbopli</jbophrase> or a
<jbophrase>te klagau</jbophrase> is. But this would mean that, rather than having to learn just the 1300-odd gismu place structures, a Lojbanist would also have to learn myriads of lujvo place structures with little or no apparent pattern or regularity to them. The purpose of the guidelines documented in this chapter is to apply regularity and to make it conventional wherever possible.</para>
<para>The second reason is related to the first: if the veljvo of the lujvo has not been properly selected, and the places for the lujvo are formulated from scratch, then there is a risk that some of the places formulated may not correspond to any of the places of the gismu used in the veljvo of the lujvo. If that is the case - that is to say, if the lujvo places are not a subset of the veljvo gismu places - then it will be very difficult for the hearer or reader to understand what a particular place means, and what it is doing in that particular lujvo. This is a topic that will be further discussed in
- <xref linkend="cll_chapter12-section14"/>.</para>
+ <xref linkend="section-anomalous-lujvo"/>.</para>
<para>However, second-guessing the place structure of the lujvo is useful in guiding the process of subsequently eliminating places from the veljvo. If the Lojbanist has an idea of what the final place structure should look like, he or she should be able to pick an appropriate veljvo to begin with, in order to express the idea, and then to decide which places are relevant or not relevant to expressing that idea.</para>
</section>
- <section xml:id="cll_chapter12-section5">
+ <section xml:id="section-symmetrical-asymmetrical">
<title>Symmetrical and asymmetrical lujvo</title>
<para> <indexterm type="example-imported"><primary>great soldier</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>when first places redundant</secondary></indexterm> <indexterm type="general-imported"><primary>veljvo</primary><secondary>symmetrical</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>symmetrical</secondary></indexterm> A common pattern, perhaps the most common pattern, of lujvo-making creates what is called a
<quote>symmetrical lujvo</quote>. A symmetrical lujvo is one based on a tanru interpretation such that the first place of the seltau is equivalent to the first place of the tertau: each component of the tanru characterizes the same object. As an illustration of this, consider the lujvo
<jbophrase>balsoi</jbophrase>: it is intended to mean
<quote>both great and a soldier</quote>- that is,
<quote>great soldier</quote>, which is the interpretation we would tend to give its veljvo,
<jbophrase>banli sonci</jbophrase>. The underlying gismu place structures are:</para>
<example xml:id="example-random-id-7AFc">
<title>
@@ -297,21 +297,21 @@
<para> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>when first place redundant with non-first</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>asymmetrical</secondary></indexterm> A substantial minority of lujvo have the property that the first place of the seltau (
<jbophrase>gerku</jbophrase> in this case) is equivalent to a place other than the first place of the tertau; such lujvo are said to be
<quote>asymmetrical</quote>. (There is a deliberate parallel here with the terms
<quote>asymmetrical tanru</quote> and
<quote>symmetrical tanru</quote> used in
<xref linkend="chapter-selbri"/>.)</para>
<para> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>effect of "SE"</secondary></indexterm> In principle any asymmetrical lujvo could be expressed as a symmetrical lujvo. Consider
<jbophrase>gerzda</jbophrase>, discussed in
- <xref linkend="cll_chapter12-section3"/>, where we learned that the g1 place was equivalent to the z2 place. In order to get the places aligned, we could convert
+ <xref linkend="section-lujvo-meanings"/>, where we learned that the g1 place was equivalent to the z2 place. In order to get the places aligned, we could convert
<jbophrase>zdani</jbophrase> to
<jbophrase>se zdani</jbophrase> (or
<jbophrase>selzda</jbophrase> when expressed as a lujvo). The place structure of
<jbophrase>selzda</jbophrase> is</para>
<example xml:id="example-random-id-IXoj">
<title>
<anchor xml:id="c12e5d5"/>
</title>
<para>s1 is housed by nest s2</para>
</example>
@@ -357,21 +357,21 @@
<para>But in general we go about in cars, rather than going to cars, so a far more likely place structure treats the ka1 place as equivalent to the kl5 place, leading to</para>
<example xml:id="example-random-id-QiHw">
<title>
<anchor xml:id="c12e5d9"/>
</title>
<para>kl1 goes to destination kl2 from origin kl3 via route kl4</para>
<para>by means of car kl5=ka1 carrying ka2 propelled by ka3.</para>
</example>
<para>instead.</para>
</section>
- <section xml:id="cll_chapter12-section6">
+ <section xml:id="section-dependent-places">
<title>Dependent places</title>
<para> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>dependent places</secondary></indexterm> In order to understand which places, if any, should be completely removed from a lujvo place structure, we need to understand the concept of dependent places. One place of a brivla is said to be dependent on another if its value can be predicted from the values of one or more of the other places. For example, the g2 place of
<jbophrase>gerku</jbophrase> is dependent on the g1 place. Why? Because when we know what fits in the g1 place (Spot, let us say, a well-known dog), then we know what fits in the g2 place (
<quote>St. Bernard</quote>, let us say). In other words, when the value of the g1 place has been specified, the value of the g2 place is determined by it. Conversely, since each dog has only one breed, but each breed contains many dogs, the g1 place is not dependent on the g2 place; if we know only that some dog is a St. Bernard, we cannot tell by that fact alone which dog is meant.</para>
<para>For
<jbophrase>zdani</jbophrase>, on the other hand, there is no dependency between the places. When we know the identity of a house-dweller, we have not determined the house, because a dweller may dwell in more than one house. By the same token, when we know the identity of a house, we do not know the identity of its dweller, for a house may contain more than one dweller.</para>
<para> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>dropping dependent seltau places</secondary></indexterm> The rule for eliminating places from a lujvo is that dependent places provided by the seltau are eliminated. Therefore, in
<jbophrase>gerzda</jbophrase> the dependent g2 place is removed from the tentative place structure given in
@@ -482,21 +482,21 @@
<para> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>selecting tertau</secondary></indexterm> <indexterm type="general-imported"><primary>shoehorn</primary></indexterm> <indexterm type="general-imported"><primary>wrong concept</primary></indexterm> In general, the desire to remove places coming from the tertau is a sign that the veljvo selected is simply wrong. Different place structures imply different concepts, and the lujvo maker may be trying to shoehorn the wrong concept into the place structure of his or her choosing. This is obvious when someone tries to shoehorn a
<jbophrase>klama</jbophrase> tertau into a
<jbophrase>litru</jbophrase> or
<jbophrase>cliva</jbophrase> concept, for example: these gismu differ in their number of arguments, and suppressing places of
<jbophrase>klama</jbophrase> in a lujvo doesn't make any sense if the resulting modified place structure is that of
<jbophrase>litru</jbophrase> or
<jbophrase>cliva</jbophrase>.</para>
<para>Sometimes the dependency is between a single place of the tertau and the whole event described by the seltau. Such cases are discussed further in
- <xref linkend="cll_chapter12-section13"/>.</para>
+ <xref linkend="section-implicit-abstraction"/>.</para>
<para> <indexterm type="example-imported"><primary>school building</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>dropping dependent places</secondary><tertiary>caveat</tertiary></indexterm> <indexterm type="general-imported"><primary>auditoriums</primary></indexterm> <indexterm type="general-imported"><primary>elementary schools</primary></indexterm> <indexterm type="general-imported"><primary>playgrounds</primary></indexterm> <indexterm type="general-imported"><primary>recital rooms</primary></indexterm> Unfortunately, not all dependent places in the seltau can be safely removed: some of them are necessary to interpreting the lujvo's meaning in context. It doesn't matter much to a doghouse what breed of dog inhabits it, but it can make quite a lot of difference to the construction of a school building what kind of school is in it! Music schools need auditoriums and recital rooms, elementary schools need playgrounds, and so on: therefore, the place structure of
<jbophrase>kuldi'u</jbophrase> (from
<jbophrase>ckule dinju</jbophrase>, and meaning
<quote>school building</quote>) needs to be</para>
@@ -504,21 +504,21 @@
<title>
<anchor xml:id="c12e6d9"/>
</title>
<para>d1 is a building housing school c1 teaching subject c3 to audience c4</para>
</example>
<para>even though c3 and c4 are plainly dependent on c1. The other places of
<jbophrase>ckule</jbophrase>, the location (c2) and operators (c5), don't seem to be necessary to the concept
<quote>school building</quote>, and are dependent on c1 to boot, so they are omitted. Again, the need for case-by-case consideration of place structures is demonstrated.</para>
</section>
- <section xml:id="cll_chapter12-section7">
+ <section xml:id="section-order-of-places">
<title>Ordering lujvo places.</title>
<para> <indexterm type="general-imported"><primary>lujvo place order</primary></indexterm> So far, we have concentrated on selecting the places to go into the place structure of a lujvo. However, this is only half the story. In using selbri in Lojban, it is important to remember the right order of the sumti. With lujvo, the need to attend to the order of sumti becomes critical: the set of places selected should be ordered in such a way that a reader unfamiliar with the lujvo should be able to tell which place is which.</para>
<para> <indexterm type="example-imported"><primary>prayer</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo place order</primary><secondary>rationale for standardization</secondary></indexterm> If we aim to make understandable lujvo, then, we should make the order of places in the place structure follow some conventions. If this does not occur, very real ambiguities can turn up. Take for example the lujvo
<jbophrase>jdaselsku</jbophrase>, meaning
<quote>prayer</quote>. In the sentence</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-FfWn">
<title>
<anchor xml:id="c12e7d1"/>
</title>
<interlinear-gloss>
@@ -540,27 +540,27 @@
<para>or is the entity being prayed to, resulting in</para>
<example xml:id="example-random-id-uL3V">
<title>
<anchor xml:id="c12e7d3"/>
</title>
<para>This is a prayer to Dong</para>
</example>
<para>We could resolve such problems on a case-by-case basis for each lujvo (
- <xref linkend="cll_chapter12-section14"/> discusses when this is actually necessary), but case-by-case resolution for run-of-the-mill lujvo makes the task of learning lujvo place structures unmanageable. People need consistent patterns to make sense of what they learn. Such patterns can be found across gismu place structures (see
- <xref linkend="cll_chapter12-section16"/>), and are even more necessary in lujvo place structures. Case-by-case consideration is still necessary; lujvo creation is a subtle art, after all. But it is helpful to take advantage of any available regularities.</para>
+ <xref linkend="section-anomalous-lujvo"/> discusses when this is actually necessary), but case-by-case resolution for run-of-the-mill lujvo makes the task of learning lujvo place structures unmanageable. People need consistent patterns to make sense of what they learn. Such patterns can be found across gismu place structures (see
+ <xref linkend="section-gismu-place-structures"/>), and are even more necessary in lujvo place structures. Case-by-case consideration is still necessary; lujvo creation is a subtle art, after all. But it is helpful to take advantage of any available regularities.</para>
<para> <indexterm type="example-imported"><primary>great soldier</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo place order</primary><secondary>symmetrical lujvo</secondary></indexterm> <indexterm type="general-imported"><primary>elimination process</primary></indexterm> We use two different ordering rules: one for symmetrical lujvo and one for asymmetrical ones. A symmetrical lujvo like
<jbophrase>balsoi</jbophrase> (from
- <xref linkend="cll_chapter12-section5"/>) has the places of its tertau followed by whatever places of the seltau survive the elimination process. For
+ <xref linkend="section-symmetrical-asymmetrical"/>) has the places of its tertau followed by whatever places of the seltau survive the elimination process. For
<jbophrase>balsoi</jbophrase>, the surviving places of
<jbophrase>banli</jbophrase> are b2 and b3, leading to the place structure:</para>
<example xml:id="example-random-id-rv1m">
<title>
<anchor xml:id="c12e7d4"/>
</title>
<para>b1=s1 is a great soldier of army s2 in property b2 by standard b3</para>
</example>
@@ -613,21 +613,21 @@
<example xml:id="example-random-id-WeBW">
<title>
<anchor xml:id="c12e7d8"/>
</title>
<para>m1 is a doctor for animal m2=d1 of species d2 for ailment m3 using treatment m4</para>
</example>
<para> <indexterm type="general-imported"><primary>animal patient</primary></indexterm> Since the shared place is m2=d1, the animal patient, the remaining seltau place d2 is inserted immediately after the shared place; then the remaining tertau places form the last two places of the lujvo.</para>
</section>
- <section xml:id="cll_chapter12-section8">
+ <section xml:id="section-n-part-lujvo">
<title>lujvo with more than two parts.</title>
<para> <indexterm type="example-imported"><primary>tomorrow</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo place order</primary><secondary>based on 3-or-more part veljvo</secondary></indexterm> The theory we have outlined so far is an account of lujvo with two parts. But often lujvo are made containing more than two parts. An example is
<jbophrase>bavlamdei</jbophrase>,
<quote>tomorrow</quote>: it is composed of the rafsi for
<quote>future</quote>,
<quote>adjacent</quote>, and
<quote>day</quote>. How does the account we have given apply to lujvo like this?</para>
<para>The best way to approach such lujvo is to continue to classify them as based on binary tanru, the only difference being that the seltau or the tertau or both is itself a lujvo. So it is easiest to make sense of
<jbophrase>bavlamdei</jbophrase> as having two components:
@@ -686,21 +686,21 @@
<title>
<anchor xml:id="c12e8d5"/>
</title>
<para>xa1=d1=c1 is a long-sword for use against xa2=d2 by wielder xa3, with a blade made of d3, length measured by standard c3.</para>
</example>
<para>If the last place sounds unimportant to you, notice that what counts legally as a
<quote>sword</quote>, rather than just a
<quote>knife</quote>, depends on the length of the blade (the legal limit varies in different jurisdictions). This fifth place of
<jbophrase>cladakyxa'i</jbophrase> may not often be explicitly filled, but it is still useful on occasion. Because it is so seldom important, it is best that it be last.</para>
</section>
- <section xml:id="cll_chapter12-section9">
+ <section xml:id="section-seltau-SE">
<title>Eliding SE rafsi from seltau</title>
<para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>dropping SE rafsi</secondary></indexterm> It is common to form lujvo that omit the rafsi based on cmavo of selma'o SE, as well as other cmavo rafsi. Doing so makes lujvo construction for common or useful constructions shorter. Since it puts more strain on the listener who has not heard the lujvo before, the shortness of the word should not necessarily outweigh ease in understanding, especially if the lujvo refers to a rare or unusual concept.</para>
<para> <indexterm type="general-imported"><primary>proposed law</primary></indexterm> Consider as an example the lujvo
<jbophrase>ti'ifla</jbophrase>, from the veljvo
<jbophrase>stidi flalu</jbophrase>, and meaning
<quote>bill, proposed law</quote>. The gismu place structures are:</para>
<example xml:id="example-random-id-n1LH">
<title>
<anchor xml:id="c12e9d1"/>
@@ -744,21 +744,21 @@
<jbophrase>selti'ifla</jbophrase> (as well as shorter). They don't require the coiner to sit down and work out the precise relation between the seltau and the tertau: he or she can just rattle off a rafsi pair. But should the lujvo get to the stage where a place structure needs to be worked out, then the precise relation does need to be specified. And in that case, such abbreviated lujvo form a trap in lujvo place ordering, since they obscure the most straightforward relation between the seltau and tertau. To give our lujvo-making guidelines as wide an application as possible, and to encourage analyzing the seltau-tertau relation in lujvo, lujvo like
<jbophrase>ti'ifla</jbophrase> are given the place structure they would have with the appropriate SE added to the seltau.</para>
<para> <indexterm type="general-imported"><primary>plausibility</primary><secondary>in abbreviated lujvo</secondary></indexterm> <indexterm type="general-imported"><primary>abbreviated lujvo and plausibility</primary></indexterm> <indexterm type="general-imported"><primary>implausible</primary></indexterm> Note that, with these lujvo, an interpretation requiring SE insertion is safe only if the alternatives are either implausible or unlikely to be needed as a lujvo. This may not always be the case, and Lojbanists should be aware of the risk of ambiguity.</para>
</section>
- <section xml:id="cll_chapter12-section10">
+ <section xml:id="section-tertau-SE">
<title>Eliding SE rafsi from tertau</title>
<para> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>effect of "SE"-dropping in tertau</secondary></indexterm> Eliding SE rafsi from tertau gets us into much more trouble. To understand why, recall that lujvo, following their veljvo, describe some type of whatever their tertau describe. Thus,
<jbophrase>posydji</jbophrase> describes a type of
<jbophrase>djica</jbophrase>,
<jbophrase>gerzda</jbophrase> describes a type of
<jbophrase>zdani</jbophrase>, and so on. What is certain is that
<jbophrase>gerzda</jbophrase> does not describe a
<jbophrase>se zdani</jbophrase>- it is not a word that could be used to describe an inhabitant such as a dog.</para>
<para> <indexterm type="example-imported"><primary>blue-eyed</primary><secondary>example</secondary></indexterm> Now consider how we would translate the word
<quote>blue-eyed</quote>. Let's tentatively translate this word as
@@ -798,21 +798,21 @@
<para>We end up being most interested in talking about the second place, not the first (we talk much more of people than of their eyes), so
<jbophrase>se</jbophrase> would almost always be required.</para>
<para>What is happening here is that we are translating the tertau wrongly, under the influence of English. The English suffix
<quote>-eyed</quote> does not mean
<quote>eye</quote>, but someone with an eye, which is
<jbophrase>selkanla</jbophrase>.</para>
<para>Because we've got the wrong tertau (eliding a
<jbophrase>se</jbophrase> that really should be there), any attempt to accommodate the resulting lujvo into our guidelines for place structure is fitting a square peg in a round hole. Since they can be so misleading, lujvo with SE rafsi elided from the tertau should be avoided in favor of their more explicit counterparts: in this case,
<jbophrase>blaselkanla</jbophrase>.</para>
</section>
- <section xml:id="cll_chapter12-section11">
+ <section xml:id="section-eliding-ke-kehe">
<title>Eliding KE and KEhE rafsi from lujvo</title>
<para> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>dropping "KEhE"</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>dropping "KE"</secondary></indexterm> People constructing lujvo usually want them to be as short as possible. To that end, they will discard any cmavo they regard as niceties. The first such cmavo to get thrown out are usually
<jbophrase>ke</jbophrase> and
<jbophrase>ke'e</jbophrase>, the cmavo used to structure and group tanru. We can usually get away with this, because the interpretation of the tertau with
<jbophrase>ke</jbophrase> and
<jbophrase>ke'e</jbophrase> missing is less plausible than that with the cmavo inserted, or because the distinction isn't really important.</para>
<para> <indexterm type="example-imported"><primary>beefsteak</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>beefsteak</primary></indexterm> For example, in
<jbophrase>bakrecpa'o</jbophrase>, meaning
<quote>beefsteak</quote>, the veljvo is</para>
@@ -964,21 +964,21 @@
<jbophrase>xelxel-</jbophrase> work in the same way.</para>
<para>Other SE combinations like
<jbophrase>selter-</jbophrase>, although they might conceivably mean
<jbophrase>se te</jbophrase>, more than likely should be interpreted in the same way, namely as
<jbophrase>se ke te</jbophrase>, since there is no need to re-order places in the way that
<jbophrase>se te</jbophrase> provides. (See
<xref linkend="chapter-sumti-tcita"/>.)</para>
</section>
- <section xml:id="cll_chapter12-section12">
+ <section xml:id="section-abstraction-lujvo">
<title>Abstract lujvo</title>
<para> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>"nu" lujvo</secondary></indexterm> <indexterm type="general-imported"><primary>abstract lujvo</primary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>abstract</secondary></indexterm> The cmavo of NU can participate in the construction of lujvo of a particularly simple and well-patterned kind. Consider that old standard example,
<jbophrase>klama</jbophrase>:</para>
<example xml:id="example-random-id-KEao">
<title>
<anchor xml:id="c12e12d1"/>
</title>
<para>k1 comes/goes to k2 from k3 via route k4 by means k5.</para>
</example>
<para>The selbri
@@ -1050,21 +1050,21 @@
<jbophrase>-hood</jbophrase> are represented with
<jbophrase role="rafsi">nun-</jbophrase> lujvo, and other words ending in
<quote>-ness</quote> or
<quote>-dom</quote> are often representable with
<jbophrase role="rafsi">kam-</jbophrase> lujvo (
<jbophrase role="rafsi">kam-</jbophrase> is the rafsi for
<jbophrase>ka</jbophrase>);
<jbophrase>kambla</jbophrase> is
<quote>blueness</quote>.</para>
<para>Even though the cmavo of NU are long-scope in nature, governing the whole following bridi, the NU rafsi should generally be used as short-scope modifiers, like the SE and NAhE rafsi discussed in
- <xref linkend="cll_chapter12-section9"/>.</para>
+ <xref linkend="section-seltau-SE"/>.</para>
<para>There is also a rafsi for the cmavo
<jbophrase>jai</jbophrase>, namely
<jbophrase>jax</jbophrase>, which allows sentences like</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-jWYr">
<title>
<anchor xml:id="c12e12d7"/>
</title>
<interlinear-gloss>
<jbo>mi jai rinka le nu do morsi</jbo>
<gloss>I am-associated-with causing the event-of your death.</gloss>
@@ -1085,21 +1085,21 @@
<para>In making a lujvo that contains
<jbophrase role="rafsi">jax-</jbophrase> for a selbri that contains
<jbophrase>jai</jbophrase>, the rule is to leave the
<jbophrase>fai</jbophrase> place as a
<jbophrase>fai</jbophrase> place of the lujvo; it does not participate in the regular lujvo place structure. (The use of
<jbophrase>fai</jbophrase> is also explained in
<xref linkend="chapter-abstractions"/>.)</para>
</section>
- <section xml:id="cll_chapter12-section13">
+ <section xml:id="section-implicit-abstraction">
<title>Implicit-abstraction lujvo</title>
<para>Eliding NU rafsi involves the same restrictions as eliding SE rafsi, plus additional ones. In general, NU rafsi should not be elided from the tertau, since that changes the kind of thing the lujvo is talking about from an abstraction to a concrete sumti. However, they may be elided from the seltau if no reasonable ambiguity would result.</para>
<para>A major difference, however, between SE elision and NU elision is that the former is a rather sparse process, providing a few convenient shortenings. Eliding
<jbophrase>nu</jbophrase>, however, is extremely important in producing a class of lujvo called
<quote>implicit-abstraction lujvo</quote>.</para>
<para>Let us make a detailed analysis of the lujvo
<jbophrase>nunctikezgau</jbophrase>, meaning
@@ -1112,24 +1112,24 @@
<anchor xml:id="c12e13d1"/>
</title>
<para>
<jbophrase>nu</jbophrase>: n1 is an event</para>
<para>
<jbophrase>citka</jbophrase>: c1 eats c2</para>
<para>
<jbophrase>gasnu</jbophrase>: g1 does action/is the agent of event g2</para>
</example>
<para>In accordance with the procedure for analyzing three-part lujvo given in
- <xref linkend="cll_chapter12-section8"/>, we will first create an intermediate lujvo,
+ <xref linkend="section-n-part-lujvo"/>, we will first create an intermediate lujvo,
<jbophrase>nuncti</jbophrase>, whose veljvo is
<jbophrase>nu citka [kei]</jbophrase>. By the rules given in
- <xref linkend="cll_chapter12-section12"/>,
+ <xref linkend="section-abstraction-lujvo"/>,
<jbophrase>nuncti</jbophrase> has the place structure</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-Xhrx">
<title>
<anchor xml:id="c12e13d2"/>
</title>
<interlinear-gloss>
<jbo>n1 is the event of c1 eating c2</jbo>
</interlinear-gloss>
</example>
<para>Now we can transform the veljvo of
@@ -1146,21 +1146,21 @@
<jbophrase>nunctikezgau</jbophrase> is:</para>
<example xml:id="example-random-id-9oTP">
<title>
<anchor xml:id="c12e13d4"/>
</title>
<para>g1 is the actor in the event of c1 eating c2</para>
</example>
<para>There is one further step that can be taken. As we have already seen with
<jbophrase>balsoi</jbophrase> in
- <xref linkend="cll_chapter12-section5"/>, the interpretation of lujvo is constrained by the semantics of gismu and of their sumti places. Now, any asymmetrical lujvo with
+ <xref linkend="section-symmetrical-asymmetrical"/>, the interpretation of lujvo is constrained by the semantics of gismu and of their sumti places. Now, any asymmetrical lujvo with
<jbophrase>gasnu</jbophrase> as its tertau will involve an event abstraction either implicitly or explicitly, since that is how the g2 place of
<jbophrase>gasnu</jbophrase> is defined.</para>
<para>Therefore, if we assume that
<jbophrase>nu</jbophrase> is the type of abstraction one would expect to be a
<jbophrase>se gasnu</jbophrase>, then the rafsi
<jbophrase role="rafsi">nun</jbophrase> and
<jbophrase role="rafsi">kez</jbophrase> in
<jbophrase>nunctikezgau</jbophrase> are only telling us what we would already have guessed - that the seltau of a
<jbophrase>gasnu</jbophrase> lujvo is an event. If we drop these rafsi out, and use instead the shorter lujvo
@@ -1268,66 +1268,66 @@
<anchor xml:id="c12e13d11"/>
</title>
<para>event r1 causes l1 to be a quantity of liquid of composition l2 under conditions l3</para>
</example>
<para>and would be useful in translating sentences like
<quote>The heat of the sun liquefied the block of ice.</quote></para>
<para>Implicit-abstraction lujvo are a powerful means in the language of rendering quite verbose bridi into succinct and manageable concepts, and increasing the expressive power of the language.</para>
</section>
- <section xml:id="cll_chapter12-section14">
+ <section xml:id="section-anomalous-lujvo">
<title>Anomalous lujvo</title>
<para>Some lujvo that have been coined and actually employed in Lojban writing do not follow the guidelines expressed above, either because the places that are equivalent in the seltau and the tertau are in an unusual position, or because the seltau and tertau are related in a complex way, or both. An example of the first kind is
<jbophrase>jdaselsku</jbophrase>, meaning
<quote>prayer</quote>, which was mentioned in
- <xref linkend="cll_chapter12-section7"/>. The gismu places are:</para>
+ <xref linkend="section-order-of-places"/>. The gismu places are:</para>
<example xml:id="example-random-id-qJEQ">
<title>
<anchor xml:id="c12e14d1"/>
</title>
<para>
<jbophrase>lijda</jbophrase>: l1 is a religion with believers l2 and beliefs l3</para>
<para>
<jbophrase>cusku</jbophrase>: c1 expresses text c2 to audience c3 in medium c4</para>
</example>
<para>and
<jbophrase>selsku</jbophrase>, the tertau of
<jbophrase>jdaselsku</jbophrase>, has the place structure</para>
<example xml:id="example-random-id-qW3w">
<title>
<anchor xml:id="c12e14d2"/>
</title>
<para>s1 is a text expressed by s2 to audience s3 in medium s4</para>
</example>
<para>Now it is easy to see that the l2 and s2 places are equivalent: the believer in the religion (l2) is the one who expresses the prayer (s2). This is not one of the cases for which a place ordering rule has been given in
- <xref linkend="cll_chapter12-section7"/> or
- <xref linkend="cll_chapter12-section13"/>; therefore, for lack of a better rule, we put the tertau places first and the remaining seltau places after them, leading to the place structure:</para>
+ <xref linkend="section-order-of-places"/> or
+ <xref linkend="section-implicit-abstraction"/>; therefore, for lack of a better rule, we put the tertau places first and the remaining seltau places after them, leading to the place structure:</para>
<example xml:id="example-random-id-41dc">
<title>
<anchor xml:id="c12e14d3"/>
</title>
<para>s1 is a prayer expressed by s2=l2 to audience s3 in medium s4 pertaining to religion l1</para>
</example>
<para>The l3 place (the beliefs of the religion) is dependent on the l1 place (the religion) and so is omitted.</para>
<para>We could make this lujvo less messy by replacing it with
<jbophrase>se seljdasku</jbophrase>, where
<jbophrase>seljdasku</jbophrase> is a normal symmetrical lujvo with place structure:</para>
<example xml:id="example-random-id-7Tdb">
<title>
<anchor xml:id="c12e14d4"/>
</title>
<para>c1=l2 religiously expresses prayer c2 to audience c3 in medium s4 pertaining to religion l1</para>
</example>
<para>which, according to the rule expressed in
- <xref linkend="cll_chapter12-section9"/>, can be further expressed as
+ <xref linkend="section-seltau-SE"/>, can be further expressed as
<jbophrase>selseljdasku</jbophrase>. However, there is no need for the ugly
<jbophrase>selsel-</jbophrase> prefix just to get the rules right:
<jbophrase>jdaselsku</jbophrase> is a reasonable, if anomalous, lujvo.</para>
<para>However, there is a further problem with
<jbophrase>jdaselsku</jbophrase>, not resolvable by using
<jbophrase>seljdasku</jbophrase>. No veljvo involving just the two gismu
<jbophrase>lijda</jbophrase> and
<jbophrase>cusku</jbophrase> can fully express the relationship implicit in prayer. A prayer is not just anything said by the adherents of a religion; nor is it even anything said by them acting as adherents of that religion. Rather, it is what they say under the authority of that religion, or using the religion as a medium, or following the rules associated with the religion, or something of the kind. So the veljvo is somewhat elliptical.</para>
<para>As a result, both
<jbophrase>seljdasku</jbophrase> and
@@ -1433,21 +1433,21 @@
<jbophrase>minkemxanpli</jbophrase> respectively.</para>
<para> <indexterm type="general-imported"><primary>latent component</primary></indexterm> Does this make
<jbophrase>xanmi'e</jbophrase> wrong? By no means. But it does mean that there is a latent component to the meaning of
<jbophrase>xanmi'e</jbophrase>, the gismu
<jbophrase>pilno</jbophrase>, which is not explicit in the veljvo. And it also means that, for a place structure derivation that actually makes sense, rather than being ad-hoc, the Lojbanist should probably go through a derivation for
<jbophrase>xancypliminde</jbophrase> or one of the other possibilities that is analogous to the analysis of
<jbophrase>terlantroge'u</jbophrase> above, even if he or she decides to stick with a shorter, more convenient form like
<jbophrase>xanmi'e</jbophrase>. In addition, of course, the possibilities of elliptical lujvo increase their potential ambiguity enormously - an unavoidable fact which should be borne in mind.</para>
</section>
- <section xml:id="cll_chapter12-section15">
+ <section xml:id="section-comparatives">
<title>Comparatives and superlatives</title>
<para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>superlatives</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>comparatives</secondary></indexterm> English has the concepts of
<quote>comparative adjectives</quote> and
<quote>superlative adjectives</quote> which can be formed from other adjectives, either by adding the suffixes
<quote>-er</quote> and
<quote>-est</quote> or by using the words
<quote>more</quote> and
<quote>most</quote>, respectively. The Lojbanic equivalents, which can be made from any brivla, are lujvo with the tertau
@@ -1667,28 +1667,28 @@
<title>
<anchor xml:id="c12e15d14"/>
</title>
<interlinear-gloss>
<jbo>la .ainctain. cu balrai lo'i skegunka</jbo>
<en>Einstein was the greatest of all scientists.</en>
</interlinear-gloss>
</example>
</section>
- <section xml:id="cll_chapter12-section16">
+ <section xml:id="section-gismu-place-structures">
<title>Notes on gismu place structures</title>
<para> <indexterm type="general-imported"><primary>place structure</primary><secondary>gismu</secondary></indexterm> <indexterm type="general-imported"><primary>gismu</primary><secondary>place structures</secondary></indexterm> Unlike the place structures of lujvo, the place structures of gismu were assigned in a far less systematic way through a detailed case-by-case analysis and repeated reviews with associated changes. (The gismu list is now baselined, so no further changes are contemplated.) Nevertheless, certain regularities were imposed both in the choice of places and in the ordering of places which may be helpful to the learner and the lujvo-maker, and which are therefore discussed here.</para>
<para> <indexterm type="general-imported"><primary>gismu</primary><secondary>place structures</secondary><tertiary>rationale</tertiary></indexterm> The choice of gismu places results from the varying outcome of four different pressures: brevity, convenience, metaphysical necessity, and regularity. (These are also to some extent the underlying factors in the lujvo place structures generated by the methods of this chapter.) The implications of each are roughly as follows:</para>
<itemizedlist>
<listitem>
<para>Brevity tends to remove places: the fewer places a gismu has, the easier it is to learn, and the less specific it is. As mentioned in
- <xref linkend="cll_chapter12-section4"/>, a brivla with fewer place structures is less specific, and generality is a virtue in gismu, because they must thoroughly blanket all of semantic space.</para>
+ <xref linkend="section-selecting-places"/>, a brivla with fewer place structures is less specific, and generality is a virtue in gismu, because they must thoroughly blanket all of semantic space.</para>
</listitem>
<listitem>
<para>Convenience tends to increase the number of places: if a concept can be expressed as a place of some existing gismu, there is no need to make another gismu, a lujvo or a fu'ivla for it.</para>
</listitem>
<listitem>
<para>Metaphysical necessity can either increase or decrease places: it is a pressure tending to provide the
<quote>right number</quote> of places. If something is part of the essential nature of a concept, then a place must be made for it; on the other hand, if instances of the concept need not have some property, then this pressure will tend to remove the place.</para>
</listitem>
<listitem>
@@ -1731,21 +1731,21 @@
</title>
<para>
<jbophrase>rinka</jbophrase>: event r1 is the cause of event r2</para>
</example>
<para> <indexterm type="general-imported"><primary>melting</primary></indexterm> The place structure of
<jbophrase>rinka</jbophrase> does not have a place for the agent, the one who causes, as a result of the pressure toward metaphysical necessity. A cause-effect relationship does not have to include an agent: an event (such as snow melting in the mountains) may cause another event (such as the flooding of the Nile) without any human intervention or even knowledge.</para>
<para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>as suppliers of agent place</secondary></indexterm> Indeed, there is a general tendency to omit agent places from most gismu except for a few such as
<jbophrase>gasnu</jbophrase> and
<jbophrase>zukte</jbophrase> which are then used as tertau in order to restore the agent place when needed: see
- <xref linkend="cll_chapter12-section13"/>.</para>
+ <xref linkend="section-implicit-abstraction"/>.</para>
<example xml:id="example-random-id-Atby">
<title>
<anchor xml:id="c12e16d4"/>
</title>
<para>
<jbophrase>cinfo</jbophrase>: c1 is a lion of species/breed c2</para>
</example>
<para> <indexterm type="general-imported"><primary>diversified species</primary></indexterm> <indexterm type="general-imported"><primary>general terms</primary></indexterm> The c2 place of
<jbophrase>cinfo</jbophrase> is provided as a result of the pressure toward regularity. All animal and plant gismu have such an x2 place; although there is in fact only one species of lion, and breeds of lion, though they exist, aren't all that important in talking about lions. The species/breed place must exist for such diversified species as dogs, and for general terms like
diff --git a/todocbook/TODO b/todocbook/TODO
index dd8656e..ed56316 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: Chapters 3 to 11 (they contain FIXMEs, though, mostly about
+Zort: Chapters 3 to 12 (they contain FIXMEs, though, mostly about
index stuff)
Matthew Walton: 3
------
Ignore Chapter 2 for now.
------
If you have any trouble, add a FIXME comment, like so:
commit 52d1388d91264b9156a3273bc30d4b0b7b631e75
Author: Eitan Postavsky <eitanp32@gmail.com>
Date: Mon Jan 10 16:40:22 2011 -0500
Chapter 12: examples (roles and tags).
diff --git a/todocbook/12.xml b/todocbook/12.xml
index 07c8f01..c306197 100644
--- a/todocbook/12.xml
+++ b/todocbook/12.xml
@@ -75,38 +75,34 @@
<quote>wine</quote> is a seltau relative to
<quote>dark</quote>, and the pair of words is a seltau relative to
<quote>sea</quote>. We're talking about the sea, not about wine or color. The other words are there to paint a scene in the listener's mind, in which the real action will occur, and to evoke relations to other sagas of the time similarly describing the sea. Logical inferences about wine or color will be rejected as irrelevant.</para>
<para> <indexterm type="example-imported"><primary>goer-house</primary><secondary>example</secondary></indexterm> As a simple example, consider the rather non-obvious tanru
<jbophrase>klama zdani</jbophrase>, or
<quote>goer-house</quote>. The gismu
<jbophrase>zdani</jbophrase> has two places:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-xcfi">
+ <example xml:id="example-random-id-xcfi">
<title>
<anchor xml:id="c12e2d1"/>
</title>
- <interlinear-gloss>
- <jbo>x1 is a nest/house/lair/den for inhabitant x2</jbo>
- </interlinear-gloss>
+ <para>x1 is a nest/house/lair/den for inhabitant x2</para>
</example>
<para>(but in this chapter we will use simply
<quote>house</quote>, for brevity), and the gismu
<jbophrase>klama</jbophrase> has five:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-zUVg">
+ <example xml:id="example-random-id-zUVg">
<title>
<anchor xml:id="c12e2d2"/>
</title>
- <interlinear-gloss>
- <jbo>x1 goes to destination x2 from origin point x3 via route x4 using means x5</jbo>
- </interlinear-gloss>
+ <para>x1 goes to destination x2 from origin point x3 via route x4 using means x5</para>
</example>
<para>The tanru
<jbophrase>klama zdani</jbophrase> will also have two places, namely those of
<jbophrase>zdani</jbophrase>. Since a
<jbophrase>klama zdani</jbophrase> is a type of
<jbophrase>zdani</jbophrase>, we can assume that all goer-houses - whatever they may be - are also houses.</para>
<para> <indexterm type="example-imported"><primary>dog house</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>tanru</primary><secondary>possible meanings of</secondary></indexterm> <indexterm type="general-imported"><primary>fleas</primary></indexterm> But is knowing the places of the tertau everything that is needed to understand the meaning of a tanru? No. To see why, let us switch to a less unlikely tanru:
<jbophrase>gerku zdani</jbophrase>, literally
<quote>dog house</quote>. A tanru expresses a very loose relation: a
@@ -138,24 +134,22 @@
<jbophrase>gerku zdani</jbophrase>.</para>
<para>As we have seen, no less than five elements are involved in the definition of
<jbophrase>gerku zdani</jbophrase>: the house, the house dweller, the dog, the dog breed (everywhere a dog goes in Lojban, a dog breed follows), and the relationship between the house and the dog. Since tanru are explicitly ambiguous in Lojban, the relationship r cannot be expressed within a tanru (if it could, it wouldn't be a tanru any more!) All the other places, however, can be expressed - thus:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-tUDa">
<title>
<anchor xml:id="c12e2d3"/>
</title>
<interlinear-gloss>
- <jbo>la blabi zdani cu gerku be fa la spot. bei la sankt. berNARD. be'o</jbo>
- <gloss>zdani la bil. klinton.</gloss>
- <gloss>The White House is-a-dog (namely Spot of-breed Saint Bernard)</gloss>
- <gloss>type-of-house-for Bill Clinton.</gloss>
+ <jbo>la blabi zdani cu gerku be fa la spot. bei la sankt. berNARD. be'o zdani la bil. klinton.</jbo>
+ <gloss>The White House is-a-dog (namely Spot of-breed Saint Bernard) type-of-house-for Bill Clinton.</gloss>
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>derogatory terms</primary></indexterm> Not the most elegant sentence ever written in either Lojban or English. Yet if there is any relation at all between Spot and the White House,
<xref linkend="example-random-id-tUDa"/> is arguably true. If we concentrate on just one type of relation in interpreting the tanru
<jbophrase>gerku zdani</jbophrase>, then the meaning of
<jbophrase>gerku zdani</jbophrase> changes. So if we understand
<jbophrase>gerku zdani</jbophrase> as having the same meaning as the English word
<quote>doghouse</quote>, the White House would no longer be a
<jbophrase>gerku zdani</jbophrase> with respect to Spot, because as far as we know Spot does not actually live in the White House, and the White House is not a doghouse (derogatory terms for incumbents notwithstanding).</para>
@@ -188,65 +182,55 @@
<para> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>notation conventions</secondary></indexterm> (The notation introduced casually in
<xref linkend="cll_chapter12-section2"/> will be useful in the rest of this chapter. Rather than using the regular x1, x2, etc. to represent places, we'll use the first letter of the relevant gismu in place of the
<quote>x</quote>, or more than one letter where necessary to resolve ambiguities. Thus, z1 is the first place of
<jbophrase>zdani</jbophrase>, and g2 is the second place of
<jbophrase>gerku</jbophrase>.)</para>
<para> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>explicated walk-through</secondary></indexterm> <indexterm type="general-imported"><primary>new notation</primary></indexterm> The place structure of
<jbophrase>zdani</jbophrase> is given as
<xref linkend="example-random-id-xcfi"/>, but is repeated here using the new notation:</para>
<para> <indexterm type="example-imported"><primary>doghouse</primary><secondary>example</secondary></indexterm> FIXME: TAG SPOT</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-95t5">
+ <example xml:id="example-random-id-95t5">
<title>
<anchor xml:id="c12e3d1"/>
</title>
- <interlinear-gloss>
- <jbo>z1 is a nest/house/lair/den of z2</jbo>
- </interlinear-gloss>
+ <para>z1 is a nest/house/lair/den of z2</para>
</example>
<para>The place structure of
<jbophrase>gerku</jbophrase> is:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-H4ed">
+ <example xml:id="example-random-id-H4ed">
<title>
<anchor xml:id="c12e3d2"/>
</title>
- <interlinear-gloss>
- <jbo>g1 is a dog of breed g2</jbo>
- </interlinear-gloss>
+ <para>g1 is a dog of breed g2</para>
</example>
<para>But z2 is the same as g1; therefore, the tentative place structure for
<jbophrase>gerzda</jbophrase> now becomes:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-VHXr">
+ <example xml:id="example-random-id-VHXr">
<title>
<anchor xml:id="c12e3d3"/>
</title>
- <interlinear-gloss>
- <jbo>z1 is a house for dweller z2 of breed g2</jbo>
- </interlinear-gloss>
+ <para>z1 is a house for dweller z2 of breed g2</para>
</example>
<para>which can also be written</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-MnKf">
+ <example xml:id="example-random-id-MnKf">
<title>
<anchor xml:id="c12e3d4"/>
</title>
- <interlinear-gloss>
- <jbo>z1 is a house for dog g1 of breed g2</jbo>
- </interlinear-gloss>
+ <para>z1 is a house for dog g1 of breed g2</para>
</example>
<para>or more comprehensively</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-Wx42">
+ <example xml:id="example-random-id-Wx42">
<title>
<anchor xml:id="c12e3d5"/>
</title>
- <interlinear-gloss>
- <jbo>z1 is a house for dweller/dog z2=g1 of breed g2</jbo>
- </interlinear-gloss>
+ <para>z1 is a house for dweller/dog z2=g1 of breed g2</para>
</example>
<para>Despite the apparently conclusive nature of
<xref linkend="example-random-id-Wx42"/>, our task is not yet done: we still need to decide whether any of the remaining places should also be eliminated, and what order the lujvo places should appear in. These concerns will be addressed in the remainder of the chapter; but we are now equipped with the terminology needed for those discussions.</para>
</section>
<section xml:id="cll_chapter12-section4">
<title>Selecting places</title>
<para> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>basis of</secondary></indexterm> The set of places of an ordinary lujvo are selected from the places of its component gismu. More precisely, the places of such a lujvo are derived from the set of places of the component gismu by eliminating unnecessary places, until just enough places remain to give an appropriate meaning to the lujvo. In general, including a place makes the concept expressed by a lujvo more general; excluding a place makes the concept more specific, because omitting the place requires assuming a standard value or range of values for it.</para>
<para> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>rationale for standardization</secondary></indexterm> It would be possible to design the place structure of a lujvo from scratch, treating it as if it were a gismu, and working out what arguments contribute to the notion to be expressed by the lujvo. There are two reasons arguing against doing so and in favor of the procedure detailed in this chapter.</para>
<para>The first is that it might be very difficult for a hearer or reader, who has no preconceived idea of what concept the lujvo is intended to convey, to work out what the place structure actually is. Instead, he or she would have to make use of a lujvo dictionary every time a lujvo is encountered in order to work out what a
<jbophrase>se jbopli</jbophrase> or a
@@ -257,108 +241,94 @@
</section>
<section xml:id="cll_chapter12-section5">
<title>Symmetrical and asymmetrical lujvo</title>
<para> <indexterm type="example-imported"><primary>great soldier</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>when first places redundant</secondary></indexterm> <indexterm type="general-imported"><primary>veljvo</primary><secondary>symmetrical</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>symmetrical</secondary></indexterm> A common pattern, perhaps the most common pattern, of lujvo-making creates what is called a
<quote>symmetrical lujvo</quote>. A symmetrical lujvo is one based on a tanru interpretation such that the first place of the seltau is equivalent to the first place of the tertau: each component of the tanru characterizes the same object. As an illustration of this, consider the lujvo
<jbophrase>balsoi</jbophrase>: it is intended to mean
<quote>both great and a soldier</quote>- that is,
<quote>great soldier</quote>, which is the interpretation we would tend to give its veljvo,
<jbophrase>banli sonci</jbophrase>. The underlying gismu place structures are:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-7AFc">
+ <example xml:id="example-random-id-7AFc">
<title>
<anchor xml:id="c12e5d1"/>
</title>
- <interlinear-gloss>
- <jbo>
- <jbophrase>banli</jbophrase>: b1 is great in property b2 by standard b3</jbo>
- <en>
- <jbophrase>sonci</jbophrase>: s1 is a soldier of army s2</en>
- </interlinear-gloss>
+ <para> <jbophrase>banli</jbophrase>: b1 is great in property b2 by standard b3</para>
+ <para> <jbophrase>sonci</jbophrase>: s1 is a soldier of army s2</para>
</example>
<para>In this case the s1 place of
<jbophrase>sonci</jbophrase> is redundant, since it is equivalent to the b1 place of
<jbophrase>banli</jbophrase>. Therefore the place structure of
<jbophrase>balsoi</jbophrase> need not include places for both s1 and b1, as they refer to the same thing. So the place structure of
<jbophrase>balsoi</jbophrase> is at most</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-UtwF">
+ <example xml:id="example-random-id-UtwF">
<title>
<anchor xml:id="c12e5d2"/>
</title>
- <interlinear-gloss>
- <jbo>b1=s1 is a great soldier of army s2 in property b2 by standard b3</jbo>
+ <para>b1=s1 is a great soldier of army s2 in property b2 by standard b3</para>
- </interlinear-gloss>
</example>
<para> <indexterm type="example-imported"><primary>listen attentively</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>when first places redundant plus others</secondary></indexterm> <indexterm type="general-imported"><primary>symmetrical veljvo</primary></indexterm> Some symmetrical veljvo have further equivalent places in addition to the respective first places. Consider the lujvo
<jbophrase>tinju'i</jbophrase>,
<quote>to listen</quote> (
<quote>to hear attentively, to hear and pay attention</quote>). The place structures of the gismu
<jbophrase>tirna</jbophrase> and
<jbophrase>jundi</jbophrase> are:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-rFiE">
+ <example xml:id="example-random-id-rFiE">
<title>
<anchor xml:id="c12e5d3"/>
</title>
- <interlinear-gloss>
- <jbo>
- <jbophrase>tirna</jbophrase>: t1 hears sound t2 against background noise t3</jbo>
+ <para>
+ <jbophrase>tirna</jbophrase>: t1 hears sound t2 against background noise t3</para>
- <en>
- <jbophrase>jundi</jbophrase>: j1 pays attention to j2</en>
- </interlinear-gloss>
+ <para>
+ <jbophrase>jundi</jbophrase>: j1 pays attention to j2</para>
</example>
<para> <indexterm type="general-imported"><primary>background noise</primary></indexterm> and the place structure of the lujvo is:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-EUr1">
+ <example xml:id="example-random-id-EUr1">
<title>
<anchor xml:id="c12e5d4"/>
</title>
- <interlinear-gloss>
- <jbo>j1=t1 listens to j2=t2 against background noise t3</jbo>
+ <para>j1=t1 listens to j2=t2 against background noise t3</para>
- </interlinear-gloss>
</example>
<para>Why so? Because not only is the j1 place (the one who pays attention) equivalent to the t1 place (the hearer), but the j2 place (the thing paid attention to) is equivalent to the t2 place (the thing heard).</para>
<para> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>when first place redundant with non-first</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>asymmetrical</secondary></indexterm> A substantial minority of lujvo have the property that the first place of the seltau (
<jbophrase>gerku</jbophrase> in this case) is equivalent to a place other than the first place of the tertau; such lujvo are said to be
<quote>asymmetrical</quote>. (There is a deliberate parallel here with the terms
<quote>asymmetrical tanru</quote> and
<quote>symmetrical tanru</quote> used in
<xref linkend="chapter-selbri"/>.)</para>
<para> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>effect of "SE"</secondary></indexterm> In principle any asymmetrical lujvo could be expressed as a symmetrical lujvo. Consider
<jbophrase>gerzda</jbophrase>, discussed in
<xref linkend="cll_chapter12-section3"/>, where we learned that the g1 place was equivalent to the z2 place. In order to get the places aligned, we could convert
<jbophrase>zdani</jbophrase> to
<jbophrase>se zdani</jbophrase> (or
<jbophrase>selzda</jbophrase> when expressed as a lujvo). The place structure of
<jbophrase>selzda</jbophrase> is</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-IXoj">
+ <example xml:id="example-random-id-IXoj">
<title>
<anchor xml:id="c12e5d5"/>
</title>
- <interlinear-gloss>
- <jbo>s1 is housed by nest s2</jbo>
- </interlinear-gloss>
+ <para>s1 is housed by nest s2</para>
</example>
<para>and so the three-part lujvo
<jbophrase>gerselzda</jbophrase> would have the place structure</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-KqE4">
+ <example xml:id="example-random-id-KqE4">
<title>
<anchor xml:id="c12e5d6"/>
</title>
- <interlinear-gloss>
- <jbo>s1=g1 is a dog housed in nest s2 of dog breed g2</jbo>
- </interlinear-gloss>
+ <para>s1=g1 is a dog housed in nest s2 of dog breed g2</para>
</example>
<para>However, although
<jbophrase>gerselzda</jbophrase> is a valid lujvo, it doesn't translate
<quote>doghouse</quote>; its first place is the dog, not the doghouse. Furthermore, it is more complicated than necessary;
<jbophrase>gerzda</jbophrase> is simpler than
<jbophrase>gerselzda</jbophrase>.</para>
<para>From the reader's or listener's point of view, it may not always be obvious whether a newly met lujvo is symmetrical or asymmetrical, and if the latter, what kind of asymmetrical lujvo. If the place structure of the lujvo isn't given in a dictionary or elsewhere, then plausibility must be applied, just as in interpreting tanru.</para>
<para> <indexterm type="example-imported"><primary>car goer</primary><secondary>example</secondary></indexterm> The lujvo
<jbophrase>karcykla</jbophrase>, for example, is based on
@@ -370,60 +340,54 @@
<title>
<anchor xml:id="c12e5d7"/>
</title>
<interlinear-gloss>
<jbo>karce: ka1 is a car carrying ka2 propelled by ka3</jbo>
</interlinear-gloss>
</example>
<para>A asymmetrical interpretation of
<jbophrase>karcykla</jbophrase> that is strictly analogous to the place structure of
<jbophrase>gerzda</jbophrase>, equating the kl2 (destination) and ka1 (car) places, would lead to the place structure</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-GgxL">
+ <example xml:id="example-random-id-GgxL">
<title>
<anchor xml:id="c12e5d8"/>
</title>
- <interlinear-gloss>
- <jbo>kl1 goes to car kl2=ka1 which carries ka2 propelled by ka3 from origin kl3</jbo>
- <en>via route kl4 by means of kl5</en>
- </interlinear-gloss>
+ <para>kl1 goes to car kl2=ka1 which carries ka2 propelled by ka3 from origin kl3</para>
+ <para>via route kl4 by means of kl5</para>
</example>
<para>But in general we go about in cars, rather than going to cars, so a far more likely place structure treats the ka1 place as equivalent to the kl5 place, leading to</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-QiHw">
+ <example xml:id="example-random-id-QiHw">
<title>
<anchor xml:id="c12e5d9"/>
</title>
- <interlinear-gloss>
- <jbo>kl1 goes to destination kl2 from origin kl3 via route kl4</jbo>
- <en>by means of car kl5=ka1 carrying ka2 propelled by ka3.</en>
- </interlinear-gloss>
+ <para>kl1 goes to destination kl2 from origin kl3 via route kl4</para>
+ <para>by means of car kl5=ka1 carrying ka2 propelled by ka3.</para>
</example>
<para>instead.</para>
</section>
<section xml:id="cll_chapter12-section6">
<title>Dependent places</title>
<para> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>dependent places</secondary></indexterm> In order to understand which places, if any, should be completely removed from a lujvo place structure, we need to understand the concept of dependent places. One place of a brivla is said to be dependent on another if its value can be predicted from the values of one or more of the other places. For example, the g2 place of
<jbophrase>gerku</jbophrase> is dependent on the g1 place. Why? Because when we know what fits in the g1 place (Spot, let us say, a well-known dog), then we know what fits in the g2 place (
<quote>St. Bernard</quote>, let us say). In other words, when the value of the g1 place has been specified, the value of the g2 place is determined by it. Conversely, since each dog has only one breed, but each breed contains many dogs, the g1 place is not dependent on the g2 place; if we know only that some dog is a St. Bernard, we cannot tell by that fact alone which dog is meant.</para>
<para>For
<jbophrase>zdani</jbophrase>, on the other hand, there is no dependency between the places. When we know the identity of a house-dweller, we have not determined the house, because a dweller may dwell in more than one house. By the same token, when we know the identity of a house, we do not know the identity of its dweller, for a house may contain more than one dweller.</para>
<para> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>dropping dependent seltau places</secondary></indexterm> The rule for eliminating places from a lujvo is that dependent places provided by the seltau are eliminated. Therefore, in
<jbophrase>gerzda</jbophrase> the dependent g2 place is removed from the tentative place structure given in
<xref linkend="example-random-id-Wx42"/>, leaving the place structure:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-zMyY">
+ <example xml:id="example-random-id-zMyY">
<title>
<anchor xml:id="c12e6d1"/>
</title>
- <interlinear-gloss>
- <jbo>z1 is the house dwelt in by dog z2=g1</jbo>
- </interlinear-gloss>
+ <para>z1 is the house dwelt in by dog z2=g1</para>
</example>
<para>Informally put, the reason this has happened - and it happens a lot with seltau places - is that the third place was describing not the doghouse, but the dog who lives in it. The sentence</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-PI6B">
<title>
<anchor xml:id="c12e6d2"/>
</title>
<interlinear-gloss>
<jbo>la mon. rePOS. gerzda la spat.</jbo>
<en>Mon Repos is a doghouse of Spot.</en>
@@ -464,58 +428,51 @@
<en>Mon Repos is a house of Spot, who is a dog of breed St. Bernard.</en>
</interlinear-gloss>
</example>
<para>and in that case, it makes little sense to say</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-yXR0">
<title>
<anchor xml:id="c12e6d6"/>
</title>
<interlinear-gloss>
- <jbo>la mon. rePOS. gerzda la spat. noi ke'a gerku la sankt. berNARD. ku'o</jbo>
- <gloss>la sankt. berNARD.</gloss>
- <gloss>Mon Repos is a doghouse of Spot, who is a dog of breed St. Bernard,</gloss>
-
- <en>of breed St. Bernard.</en>
+ <jbo>la mon. rePOS. gerzda la spat. noi ke'a gerku la sankt. berNARD. ku'o la sankt. berNARD.</jbo>
+ <en>Mon Repos is a doghouse of Spot, who is a dog of breed St. Bernard, of breed St. Bernard.</en>
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>supplementary information</primary></indexterm> employing the over-ample place structure of
<xref linkend="example-random-id-Wx42"/>. The dog breed is redundantly given both in the main selbri and in the relative clause, and (intuitively speaking) is repeated in the wrong place, since the dog breed is supplementary information about the dog, and not about the doghouse.</para>
<para> <indexterm type="example-imported"><primary>beetle</primary><secondary>example</secondary></indexterm> As a further example, take
<jbophrase>cakcinki</jbophrase>, the lujvo for
<quote>beetle</quote>, based on the tanru
<jbophrase>calku cinki</jbophrase>, or
<quote>shell-insect</quote>. The gismu place structures are:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-D0qb">
+ <example xml:id="example-random-id-D0qb">
<title>
<anchor xml:id="c12e6d7"/>
</title>
- <interlinear-gloss>
- <jbo>
- <jbophrase>calku</jbophrase>: ca1 is a shell/husk around ca2 made of ca3</jbo>
- <en>
- <jbophrase>cinki</jbophrase>: ci1 is an insect/arthropod of species ci2</en>
+ <para>
+ <jbophrase>calku</jbophrase>: ca1 is a shell/husk around ca2 made of ca3</para>
+ <para>
+ <jbophrase>cinki</jbophrase>: ci1 is an insect/arthropod of species ci2</para>
- </interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>dropping cross-dependent places</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>cross-dependent places</secondary></indexterm> <indexterm type="general-imported"><primary>cross-dependency</primary></indexterm> <indexterm type="general-imported"><primary>arthropod</primary></indexterm> This example illustrates a cross-dependency between a place of one gismu and a place of the other. The ca3 place is dependent on ci1, because all insects (which fit into ci1) have shells made of chitin (which fits into ca3). Furthermore, ca1 is dependent on ci1 as well, because each insect has only a single shell. And since ca2 (the thing with the shell) is equivalent to ci1 (the insect), the place structure is</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-n7JB">
+ <example xml:id="example-random-id-n7JB">
<title>
<anchor xml:id="c12e6d8"/>
</title>
- <interlinear-gloss>
- <jbo>ci1=ca2 is a beetle of species ci2</jbo>
+ <para>ci1=ca2 is a beetle of species ci2</para>
- </interlinear-gloss>
</example>
<para>with not a single place of
<jbophrase>calku</jbophrase> surviving independently!</para>
<para> <indexterm type="general-imported"><primary>beetles</primary></indexterm> <indexterm type="general-imported"><primary>Coleoptera</primary></indexterm> (Note that there is nothing in this explanation that tells us just why
<jbophrase>cakcinki</jbophrase> means
<quote>beetle</quote> (member of Coleoptera), since all insects in their adult forms have chitin shells of some sort. The answer, which is in no way predictable, is that the shell is a prominent, highly noticeable feature of beetles in particular.)</para>
<para> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>dropping dependent tertau places</secondary></indexterm> What about the dependency of ci2 on ci1? After all, no beetle belongs to more than one species, so it would seem that the ci2 place of
@@ -536,27 +493,25 @@
<para> <indexterm type="example-imported"><primary>school building</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>dropping dependent places</secondary><tertiary>caveat</tertiary></indexterm> <indexterm type="general-imported"><primary>auditoriums</primary></indexterm> <indexterm type="general-imported"><primary>elementary schools</primary></indexterm> <indexterm type="general-imported"><primary>playgrounds</primary></indexterm> <indexterm type="general-imported"><primary>recital rooms</primary></indexterm> Unfortunately, not all dependent places in the seltau can be safely removed: some of them are necessary to interpreting the lujvo's meaning in context. It doesn't matter much to a doghouse what breed of dog inhabits it, but it can make quite a lot of difference to the construction of a school building what kind of school is in it! Music schools need auditoriums and recital rooms, elementary schools need playgrounds, and so on: therefore, the place structure of
<jbophrase>kuldi'u</jbophrase> (from
<jbophrase>ckule dinju</jbophrase>, and meaning
<quote>school building</quote>) needs to be</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-u6Xz">
+ <example xml:id="example-random-id-u6Xz">
<title>
<anchor xml:id="c12e6d9"/>
</title>
- <interlinear-gloss>
- <jbo>d1 is a building housing school c1 teaching subject c3 to audience c4</jbo>
- </interlinear-gloss>
+ <para>d1 is a building housing school c1 teaching subject c3 to audience c4</para>
</example>
<para>even though c3 and c4 are plainly dependent on c1. The other places of
<jbophrase>ckule</jbophrase>, the location (c2) and operators (c5), don't seem to be necessary to the concept
<quote>school building</quote>, and are dependent on c1 to boot, so they are omitted. Again, the need for case-by-case consideration of place structures is demonstrated.</para>
</section>
<section xml:id="cll_chapter12-section7">
<title>Ordering lujvo places.</title>
<para> <indexterm type="general-imported"><primary>lujvo place order</primary></indexterm> So far, we have concentrated on selecting the places to go into the place structure of a lujvo. However, this is only half the story. In using selbri in Lojban, it is important to remember the right order of the sumti. With lujvo, the need to attend to the order of sumti becomes critical: the set of places selected should be ordered in such a way that a reader unfamiliar with the lujvo should be able to tell which place is which.</para>
<para> <indexterm type="example-imported"><primary>prayer</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo place order</primary><secondary>rationale for standardization</secondary></indexterm> If we aim to make understandable lujvo, then, we should make the order of places in the place structure follow some conventions. If this does not occur, very real ambiguities can turn up. Take for example the lujvo
@@ -568,59 +523,53 @@
</title>
<interlinear-gloss>
<jbo>di'e jdaselsku la dong.</jbo>
<gloss>This-utterance is-a-prayer somehow-related-to-Dong.</gloss>
</interlinear-gloss>
</example>
<para> <indexterm type="example-imported"><primary>Dong</primary><secondary>example</secondary></indexterm> we must be able to know if Dong is the person making the prayer, giving the meaning</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-b38f">
+ <example xml:id="example-random-id-b38f">
<title>
<anchor xml:id="c12e7d2"/>
</title>
- <interlinear-gloss>
- <jbo>This is a prayer by Dong</jbo>
+ <para>This is a prayer by Dong</para>
- </interlinear-gloss>
</example>
<para>or is the entity being prayed to, resulting in</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-uL3V">
+ <example xml:id="example-random-id-uL3V">
<title>
<anchor xml:id="c12e7d3"/>
</title>
- <interlinear-gloss>
- <jbo>This is a prayer to Dong</jbo>
+ <para>This is a prayer to Dong</para>
- </interlinear-gloss>
</example>
<para>We could resolve such problems on a case-by-case basis for each lujvo (
<xref linkend="cll_chapter12-section14"/> discusses when this is actually necessary), but case-by-case resolution for run-of-the-mill lujvo makes the task of learning lujvo place structures unmanageable. People need consistent patterns to make sense of what they learn. Such patterns can be found across gismu place structures (see
<xref linkend="cll_chapter12-section16"/>), and are even more necessary in lujvo place structures. Case-by-case consideration is still necessary; lujvo creation is a subtle art, after all. But it is helpful to take advantage of any available regularities.</para>
<para> <indexterm type="example-imported"><primary>great soldier</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo place order</primary><secondary>symmetrical lujvo</secondary></indexterm> <indexterm type="general-imported"><primary>elimination process</primary></indexterm> We use two different ordering rules: one for symmetrical lujvo and one for asymmetrical ones. A symmetrical lujvo like
<jbophrase>balsoi</jbophrase> (from
<xref linkend="cll_chapter12-section5"/>) has the places of its tertau followed by whatever places of the seltau survive the elimination process. For
<jbophrase>balsoi</jbophrase>, the surviving places of
<jbophrase>banli</jbophrase> are b2 and b3, leading to the place structure:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-rv1m">
+ <example xml:id="example-random-id-rv1m">
<title>
<anchor xml:id="c12e7d4"/>
</title>
- <interlinear-gloss>
- <jbo>b1=s1 is a great soldier of army s2 in property b2 by standard b3</jbo>
+ <para>b1=s1 is a great soldier of army s2 in property b2 by standard b3</para>
- </interlinear-gloss>
</example>
<para>just what appears in
<xref linkend="example-random-id-7AFc"/>. In fact, all place structures shown until now have been in the correct order by the conventions of this section, though the fact has been left tacit until now.</para>
<para>The motivation for this rule is the parallelism between the lujvo bridi-schema</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-7juc">
<title>
<anchor xml:id="c12e7d5"/>
</title>
<interlinear-gloss>
<jbo>b1 balsoi s2 b2 b3</jbo>
@@ -642,44 +591,38 @@
<quote>and</quote> when placed between two partial bridi, as explained in
<xref linkend="chapter-connectives"/>.</para>
<para> <indexterm type="example-imported"><primary>veterinarian</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo place order</primary><secondary>asymmetrical lujvo</secondary></indexterm> <indexterm type="general-imported"><primary>animal doctor</primary><secondary>example</secondary></indexterm> Asymmetrical lujvo like
<jbophrase>gerzda</jbophrase>, on the other hand, employ a different rule. The seltau places are inserted not at the end of the place structure, but rather immediately after the tertau place which is equivalent to the first place of the seltau. Consider
<jbophrase>dalmikce</jbophrase>, meaning
<quote>veterinarian</quote>: its veljvo is
<jbophrase>danlu mikce</jbophrase>, or
<quote>animal doctor</quote>. The place structures for those gismu are:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-BqPj">
+ <example xml:id="example-random-id-BqPj">
<title>
<anchor xml:id="c12e7d7"/>
</title>
- <interlinear-gloss>
- <jbo>
- <jbophrase>danlu</jbophrase>: d1 is an animal of species d2</jbo>
- <en>
- <jbophrase>mikce</jbophrase>: m1 is a doctor to patient m2 for ailment m3 using treatment m4</en>
+ <para>
+ <jbophrase>danlu</jbophrase>: d1 is an animal of species d2</para>
+ <para>
+ <jbophrase>mikce</jbophrase>: m1 is a doctor to patient m2 for ailment m3 using treatment m4</para>
- </interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>ailment</primary></indexterm> and the lujvo place structure is:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-WeBW">
+ <example xml:id="example-random-id-WeBW">
<title>
<anchor xml:id="c12e7d8"/>
</title>
- <interlinear-gloss>
- <jbo>m1 is a doctor for animal m2=d1 of species d2 for ailment m3</jbo>
-
- <en>using treatment m4</en>
- </interlinear-gloss>
+ <para>m1 is a doctor for animal m2=d1 of species d2 for ailment m3 using treatment m4</para>
</example>
<para> <indexterm type="general-imported"><primary>animal patient</primary></indexterm> Since the shared place is m2=d1, the animal patient, the remaining seltau place d2 is inserted immediately after the shared place; then the remaining tertau places form the last two places of the lujvo.</para>
</section>
<section xml:id="cll_chapter12-section8">
<title>lujvo with more than two parts.</title>
<para> <indexterm type="example-imported"><primary>tomorrow</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo place order</primary><secondary>based on 3-or-more part veljvo</secondary></indexterm> The theory we have outlined so far is an account of lujvo with two parts. But often lujvo are made containing more than two parts. An example is
<jbophrase>bavlamdei</jbophrase>,
<quote>tomorrow</quote>: it is composed of the rafsi for
@@ -688,141 +631,119 @@
<quote>day</quote>. How does the account we have given apply to lujvo like this?</para>
<para>The best way to approach such lujvo is to continue to classify them as based on binary tanru, the only difference being that the seltau or the tertau or both is itself a lujvo. So it is easiest to make sense of
<jbophrase>bavlamdei</jbophrase> as having two components:
<jbophrase>bavla'i</jbophrase>,
<quote>next</quote>, and
<jbophrase>djedi</jbophrase>. If we know or invent the lujvo place structure for the components, we can compose the new lujvo place structure in the usual way.</para>
<para>In this case,
<jbophrase>bavla'i</jbophrase> is given the place structure</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-aCg7">
+ <example xml:id="example-random-id-aCg7">
<title>
<anchor xml:id="c12e8d1"/>
</title>
- <interlinear-gloss>
- <jbo>b1=l1 is next after b2=l2</jbo>
- </interlinear-gloss>
+ <para>b1=l1 is next after b2=l2</para>
</example>
<para>making it a symmetrical lujvo. We combine this with
<jbophrase>djedi</jbophrase>, which has the place structure:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-Lera">
+ <example xml:id="example-random-id-Lera">
<title>
<anchor xml:id="c12e8d2"/>
</title>
- <interlinear-gloss>
- <jbo>duration d1 is d2 days long (default 1) by standard d3</jbo>
- </interlinear-gloss>
+ <para>duration d1 is d2 days long (default 1) by standard d3</para>
</example>
<para> <indexterm type="general-imported"><primary>anomalous ordering of lujvo places</primary></indexterm> While symmetrical lujvo normally put any trailing tertau places before any seltau places, the day standard is a much less important concept than the day the tomorrow follows, in the definition of
<jbophrase>bavlamdei</jbophrase>. This is an example of how the guidelines presented for selecting and ordering lujvo places are just that, not laws that must be rigidly adhered to. In this case, we choose to rank places in order of relative importance. The resulting place structure is:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-KEwW">
+ <example xml:id="example-random-id-KEwW">
<title>
<anchor xml:id="c12e8d3"/>
</title>
- <interlinear-gloss>
- <jbo>d1=b1=l1 is a day following b2=l2, d2 days later (default 1) by standard d3</jbo>
- </interlinear-gloss>
+ <para>d1=b1=l1 is a day following b2=l2, d2 days later (default 1) by standard d3</para>
</example>
<para> <indexterm type="example-imported"><primary>long-sword</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>medieval weapon</primary></indexterm> Here is another example of a multi-part lujvo:
<jbophrase>cladakyxa'i</jbophrase>, meaning
<quote>long-sword</quote>, a specific type of medieval weapon. The gismu place structures are:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-XpNf">
+ <example xml:id="example-random-id-XpNf">
<title>
<anchor xml:id="c12e8d4"/>
</title>
- <interlinear-gloss>
- <jbo>
- <jbophrase>clani</jbophrase>: c1 is long in direction c2 by standard c3</jbo>
+ <para>
+ <jbophrase>clani</jbophrase>: c1 is long in direction c2 by standard c3</para>
<gloss>
<jbophrase>dakfu</jbophrase>: d1 is a knife for cutting d2 with blade made of d3</gloss>
- <en>
- <jbophrase>xarci</jbophrase>: xa1 is a weapon for use against xa2 by wielder xa3</en>
- </interlinear-gloss>
+ <para>
+ <jbophrase>xarci</jbophrase>: xa1 is a weapon for use against xa2 by wielder xa3</para>
</example>
<para> <indexterm type="general-imported"><primary>sword blade</primary></indexterm> Since
<jbophrase>cladakyxa'i</jbophrase> is a symmetrical lujvo based on
<jbophrase>cladakfu xarci</jbophrase>, and
<jbophrase>cladakfu</jbophrase> is itself a symmetrical lujvo, we can do the necessary analyses all at once. Plainly c1 (the long thing), d1 (the knife), and xa1 (the weapon) are all the same. Likewise, the d2 place (the thing cut) is the same as the xa2 place (the target of the weapon), given that swords are used to cut victims. Finally, the c2 place (direction of length) is always along the sword blade in a longsword, by definition, and so is dependent on c1=d1=xa1. Adding on the places of the remaining gismu in right-to-left order we get:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-eAbF">
+ <example xml:id="example-random-id-eAbF">
<title>
<anchor xml:id="c12e8d5"/>
</title>
- <interlinear-gloss>
- <jbo>xa1=d1=c1 is a long-sword for use against xa2=d2 by wielder xa3,</jbo>
-
- <en>with a blade made of d3, length measured by standard c3.</en>
- </interlinear-gloss>
+ <para>xa1=d1=c1 is a long-sword for use against xa2=d2 by wielder xa3, with a blade made of d3, length measured by standard c3.</para>
</example>
<para>If the last place sounds unimportant to you, notice that what counts legally as a
<quote>sword</quote>, rather than just a
<quote>knife</quote>, depends on the length of the blade (the legal limit varies in different jurisdictions). This fifth place of
<jbophrase>cladakyxa'i</jbophrase> may not often be explicitly filled, but it is still useful on occasion. Because it is so seldom important, it is best that it be last.</para>
</section>
<section xml:id="cll_chapter12-section9">
<title>Eliding SE rafsi from seltau</title>
<para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>dropping SE rafsi</secondary></indexterm> It is common to form lujvo that omit the rafsi based on cmavo of selma'o SE, as well as other cmavo rafsi. Doing so makes lujvo construction for common or useful constructions shorter. Since it puts more strain on the listener who has not heard the lujvo before, the shortness of the word should not necessarily outweigh ease in understanding, especially if the lujvo refers to a rare or unusual concept.</para>
<para> <indexterm type="general-imported"><primary>proposed law</primary></indexterm> Consider as an example the lujvo
<jbophrase>ti'ifla</jbophrase>, from the veljvo
<jbophrase>stidi flalu</jbophrase>, and meaning
<quote>bill, proposed law</quote>. The gismu place structures are:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-n1LH">
+ <example xml:id="example-random-id-n1LH">
<title>
<anchor xml:id="c12e9d1"/>
</title>
- <interlinear-gloss>
- <jbo>
- <jbophrase>stidi</jbophrase>: agent st1 suggests idea/action st2 to audience st3</jbo>
+ <para>
+ <jbophrase>stidi</jbophrase>: agent st1 suggests idea/action st2 to audience st3</para>
<gloss>
<jbophrase>flalu</jbophrase>: f1 is a law specifying f2 for community f3 under conditions f4</gloss>
- <en>by lawgiver f5</en>
- </interlinear-gloss>
+ <para>by lawgiver f5</para>
</example>
<para> <indexterm type="general-imported"><primary>lined up</primary></indexterm> This lujvo does not fit any of our existing molds: it is the second seltau place, st2, that is equivalent to one of the tertau places, namely f1. However, if we understand
<jbophrase>ti'ifla</jbophrase> as an abbreviation for the lujvo
<jbophrase>selti'ifla</jbophrase>, then we get the first places of seltau and tertau lined up. The place structure of
<jbophrase>selti'i</jbophrase> is:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-j98h">
+ <example xml:id="example-random-id-j98h">
<title>
<anchor xml:id="c12e9d2"/>
</title>
- <interlinear-gloss>
- <jbo>
- <jbophrase>selti'i</jbophrase>: idea/action se1 is suggested by agent se2 to audience se3</jbo>
- </interlinear-gloss>
+ <para>
+ <jbophrase>selti'i</jbophrase>: idea/action se1 is suggested by agent se2 to audience se3</para>
</example>
<para>Here we can see that se1 (what is suggested) is equivalent to f1 (the law), and we get a normal symmetrical lujvo. The final place structure is:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-S0n4">
+ <example xml:id="example-random-id-S0n4">
<title>
<anchor xml:id="c12e9d3"/>
</title>
- <interlinear-gloss>
- <jbo>f1=se1 is a bill specifying f2 for community f3 under conditions f4</jbo>
- <en>by suggester se2 to audience/lawgivers f5=se3</en>
- </interlinear-gloss>
+ <para>f1=se1 is a bill specifying f2 for community f3 under conditions f4 by suggester se2 to audience/lawgivers f5=se3</para>
</example>
<para>or, relabeling the places,</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-RM3D">
+ <example xml:id="example-random-id-RM3D">
<title>
<anchor xml:id="c12e9d4"/>
</title>
- <interlinear-gloss>
- <jbo>f1=st2 is a bill specifying f2 for community f3 under conditions f4</jbo>
- <en>by suggester st1 to audience/lawgivers f5=st3</en>
- </interlinear-gloss>
+ <para>f1=st2 is a bill specifying f2 for community f3 under conditions f4 by suggester st1 to audience/lawgivers f5=st3</para>
</example>
<para>where the last place (st3) is probably some sort of legislature.</para>
<para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>abbreviated</secondary></indexterm> Abbreviated lujvo like
<jbophrase>ti'ifla</jbophrase> are more intuitive (for the lujvo-maker) than their more explicit counterparts like
<jbophrase>selti'ifla</jbophrase> (as well as shorter). They don't require the coiner to sit down and work out the precise relation between the seltau and the tertau: he or she can just rattle off a rafsi pair. But should the lujvo get to the stage where a place structure needs to be worked out, then the precise relation does need to be specified. And in that case, such abbreviated lujvo form a trap in lujvo place ordering, since they obscure the most straightforward relation between the seltau and tertau. To give our lujvo-making guidelines as wide an application as possible, and to encourage analyzing the seltau-tertau relation in lujvo, lujvo like
@@ -861,27 +782,25 @@
<title>
<anchor xml:id="c12e10d2"/>
</title>
<interlinear-gloss>
<jbo>la djak. cu se blakanla</jbo>
<gloss>Jack is-the-bearer-of-blue-eyes</gloss>
</interlinear-gloss>
</example>
<para>But look now at the place structure of
<jbophrase>blakanla</jbophrase>: it is a symmetrical lujvo, so the place structure is:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-ncPN">
+ <example xml:id="example-random-id-ncPN">
<title>
<anchor xml:id="c12e10d3"/>
</title>
- <interlinear-gloss>
- <jbo>bl1=k1 is a blue eye of bl2=k2</jbo>
- </interlinear-gloss>
+ <para>bl1=k1 is a blue eye of bl2=k2</para>
</example>
<para>We end up being most interested in talking about the second place, not the first (we talk much more of people than of their eyes), so
<jbophrase>se</jbophrase> would almost always be required.</para>
<para>What is happening here is that we are translating the tertau wrongly, under the influence of English. The English suffix
<quote>-eyed</quote> does not mean
<quote>eye</quote>, but someone with an eye, which is
<jbophrase>selkanla</jbophrase>.</para>
<para>Because we've got the wrong tertau (eliding a
<jbophrase>se</jbophrase> that really should be there), any attempt to accommodate the resulting lujvo into our guidelines for place structure is fitting a square peg in a round hole. Since they can be so misleading, lujvo with SE rafsi elided from the tertau should be avoided in favor of their more explicit counterparts: in this case,
<jbophrase>blaselkanla</jbophrase>.</para>
@@ -896,32 +815,32 @@
<para> <indexterm type="example-imported"><primary>beefsteak</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>beefsteak</primary></indexterm> For example, in
<jbophrase>bakrecpa'o</jbophrase>, meaning
<quote>beefsteak</quote>, the veljvo is</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-TgVR">
<title>
<anchor xml:id="c12e11d1"/>
</title>
<interlinear-gloss>
<jbo>[ke] bakni rectu [ke'e] panlo</jbo>
- <en>( bovine meat ) slice</en>
+ <gloss>( bovine meat ) slice</gloss>
</interlinear-gloss>
</example>
<para> <indexterm type="example-imported"><primary>bovine</primary><secondary>example</secondary></indexterm> because of the usual Lojban left-grouping rule. But there doesn't seem to be much difference between that veljvo and</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-HDBe">
<title>
<anchor xml:id="c12e11d2"/>
</title>
<interlinear-gloss>
<jbo>bakni ke rectu panlo [ke'e]</jbo>
- <en>bovine ( meat slice )</en>
+ <gloss>bovine ( meat slice )</gloss>
</interlinear-gloss>
</example>
<para> <indexterm type="example-imported"><primary>sneak in</primary><secondary>example</secondary></indexterm> <indexterm type="example-imported"><primary>meat slice</primary><secondary>example</secondary></indexterm> On the other hand, the lujvo
<jbophrase>zernerkla</jbophrase>, meaning
<quote>to sneak in</quote>, almost certainly was formed from the veljvo</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-aXrm">
<title>
@@ -992,33 +911,31 @@
<jbophrase>to'e</jbophrase> before it, it's better to leave the result as two words, or else to insert
<jbophrase>ke</jbophrase>, than to just stick the SE or NAhE rafsi on.</para>
<para>It is all right to replace the phrase
<jbophrase>se klama</jbophrase> with
<jbophrase>selkla</jbophrase>, and the places of
<jbophrase>selkla</jbophrase> are exactly those of
<jbophrase>se klama</jbophrase>. But consider the related lujvo
<jbophrase>dzukla</jbophrase>, meaning
<quote>to walk to somewhere</quote>. It is a symmmetrical lujvo, derived from the veljvo
<jbophrase>cadzu klama</jbophrase> as follows:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-4yG0">
+ <example xml:id="example-random-id-4yG0">
<title>
<anchor xml:id="c12e11d7"/>
</title>
- <interlinear-gloss>
- <jbo>
- <jbophrase>cadzu</jbophrase>: c1 walks on surface c2 using limbs c3</jbo>
+ <para>
+ <jbophrase>cadzu</jbophrase>: c1 walks on surface c2 using limbs c3</para>
<gloss>
<jbophrase>klama</jbophrase>: k1 goes to k2 from k3 via route k4 using k5</gloss>
<gloss>
<jbophrase>dzukla</jbophrase>: c1=k1 walks to k2 from k3 via route k4 using limbs k5=c3</gloss>
- <en>on surface c2</en>
- </interlinear-gloss>
+ <para>on surface c2</para>
</example>
<para>We can swap the k1 and k2 places using
<jbophrase>se dzukla</jbophrase>, but we cannot directly make
<jbophrase>se dzukla</jbophrase> into
<jbophrase>seldzukla</jbophrase>, which would represent the veljvo
<jbophrase>selcadzu klama</jbophrase> and plausibly mean something like
<quote>to go to a walking surface</quote>. Instead, we would need
<jbophrase>selkemdzukla</jbophrase>, with an explicit rafsi for
<jbophrase>ke</jbophrase>. Similarly,
<jbophrase>nalbrablo</jbophrase> (from
@@ -1051,94 +968,83 @@
<jbophrase>se ke te</jbophrase>, since there is no need to re-order places in the way that
<jbophrase>se te</jbophrase> provides. (See
<xref linkend="chapter-sumti-tcita"/>.)</para>
</section>
<section xml:id="cll_chapter12-section12">
<title>Abstract lujvo</title>
<para> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>"nu" lujvo</secondary></indexterm> <indexterm type="general-imported"><primary>abstract lujvo</primary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>abstract</secondary></indexterm> The cmavo of NU can participate in the construction of lujvo of a particularly simple and well-patterned kind. Consider that old standard example,
<jbophrase>klama</jbophrase>:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-KEao">
+ <example xml:id="example-random-id-KEao">
<title>
<anchor xml:id="c12e12d1"/>
</title>
- <interlinear-gloss>
- <jbo>k1 comes/goes to k2 from k3 via route k4 by means k5.</jbo>
- </interlinear-gloss>
+ <para>k1 comes/goes to k2 from k3 via route k4 by means k5.</para>
</example>
<para>The selbri
<jbophrase>nu klama [kei]</jbophrase> has only one place, the event-of-going, but the full five places exist implicitly between
<jbophrase>nu</jbophrase> and
<jbophrase>kei</jbophrase>, since a full bridi with all sumti may be placed there. In a lujvo, there is no room for such inside places, and consequently the lujvo
<jbophrase>nunkla</jbophrase> (
<jbophrase role="rafsi">nun-</jbophrase> is the rafsi for
<jbophrase>nu</jbophrase>), needs to have six places:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-m60H">
+ <example xml:id="example-random-id-m60H">
<title>
<anchor xml:id="c12e12d2"/>
</title>
- <interlinear-gloss>
- <jbo>nu1 is the event of k1's coming/going to k2 from k3 via route k4 by means k5.</jbo>
- </interlinear-gloss>
+ <para>nu1 is the event of k1's coming/going to k2 from k3 via route k4 by means k5.</para>
</example>
<para>Here the first place of
<jbophrase>nunklama</jbophrase> is the first and only place of
<jbophrase>nu</jbophrase>, and the other five places have been pushed down by one to occupy the second through the sixth places. Full information on
<jbophrase>nu</jbophrase>, as well as the other abstractors mentioned in this section, is given in
<xref linkend="chapter-abstractions"/>.</para>
<para> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>multi-place abstraction lujvo</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>"ni" lujvo</secondary></indexterm> For those abstractors which have a second place as well, the standard convention is to place this place after, rather than before, the places of the brivla being abstracted. The place structure of
<jbophrase>nilkla</jbophrase>, the lujvo derived from
<jbophrase>ni klama</jbophrase>, is the imposing:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-yURu">
+ <example xml:id="example-random-id-yURu">
<title>
<anchor xml:id="c12e12d3"/>
</title>
- <interlinear-gloss>
- <jbo>ni1 is the amount of k1's coming/going to k2 from k3 via route k4</jbo>
- <en>by means k5, measured on scale ni2.</en>
- </interlinear-gloss>
+ <para>ni1 is the amount of k1's coming/going to k2 from k3 via route k4 by means k5, measured on scale ni2.</para>
</example>
<para>It is not uncommon for abstractors to participate in the making of more complex lujvo as well. For example,
<jbophrase>nunsoidji</jbophrase>, from the veljvo</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-RKcH">
<title>
<anchor xml:id="c12e12d4"/>
</title>
<interlinear-gloss>
<jbo>nu sonci kei djica</jbo>
<gloss>event-of being-a-soldier desirer</gloss>
</interlinear-gloss>
</example>
<para>has the place structure</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-8Nos">
+ <example xml:id="example-random-id-8Nos">
<title>
<anchor xml:id="c12e12d5"/>
</title>
- <interlinear-gloss>
- <jbo>d1 desires the event of (s1 being a soldier of army s2) for purpose d3</jbo>
- </interlinear-gloss>
+ <para>d1 desires the event of (s1 being a soldier of army s2) for purpose d3</para>
</example>
<para>where the d2 place has disappeared altogether, being replaced by the places of the seltau. As shown in
<xref linkend="example-random-id-8Nos"/>, the ordering follows this idea of replacement: the seltau places are inserted at the point where the omitted abstraction place exists in the tertau.</para>
<para>The lujvo
<jbophrase>nunsoidji</jbophrase> is quite different from the ordinary asymmetric lujvo
<jbophrase>soidji</jbophrase>, a
<quote>soldier desirer</quote>, whose place structure is just</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-2VMP">
+ <example xml:id="example-random-id-2VMP">
<title>
<anchor xml:id="c12e12d6"/>
</title>
- <interlinear-gloss>
- <jbo>d1 desires (a soldier of army s2) for purpose d3</jbo>
- </interlinear-gloss>
+ <para>d1 desires (a soldier of army s2) for purpose d3</para>
</example>
<para>A
<jbophrase>nunsoidji</jbophrase> might be someone who is about to enlist, whereas a
<jbophrase>soidji</jbophrase> might be a camp-follower.</para>
<para>One use of abstract lujvo is to eliminate the need for explicit
<jbophrase>kei</jbophrase> in tanru:
<jbophrase>nunkalri gasnu</jbophrase> means much the same as
<jbophrase>nu kalri kei gasnu</jbophrase>, but is shorter. In addition, many English words ending in
<jbophrase>-hood</jbophrase> are represented with
@@ -1194,69 +1100,63 @@
<jbophrase>nu</jbophrase>, however, is extremely important in producing a class of lujvo called
<quote>implicit-abstraction lujvo</quote>.</para>
<para>Let us make a detailed analysis of the lujvo
<jbophrase>nunctikezgau</jbophrase>, meaning
<quote>to feed</quote>. (If you think this lujvo is excessively longwinded, be patient.) The veljvo of
<jbophrase>nunctikezgau</jbophrase> is
<jbophrase>nu citka kei gasnu</jbophrase>. The relevant place structures are:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-bSDW">
+ <example xml:id="example-random-id-bSDW">
<title>
<anchor xml:id="c12e13d1"/>
</title>
- <interlinear-gloss>
- <jbo>
- <jbophrase>nu</jbophrase>: n1 is an event</jbo>
- <gloss>
- <jbophrase>citka</jbophrase>: c1 eats c2</gloss>
- <en>
- <jbophrase>gasnu</jbophrase>: g1 does action/is the agent of event g2</en>
- </interlinear-gloss>
+ <para>
+ <jbophrase>nu</jbophrase>: n1 is an event</para>
+ <para>
+ <jbophrase>citka</jbophrase>: c1 eats c2</para>
+ <para>
+ <jbophrase>gasnu</jbophrase>: g1 does action/is the agent of event g2</para>
</example>
<para>In accordance with the procedure for analyzing three-part lujvo given in
<xref linkend="cll_chapter12-section8"/>, we will first create an intermediate lujvo,
<jbophrase>nuncti</jbophrase>, whose veljvo is
<jbophrase>nu citka [kei]</jbophrase>. By the rules given in
<xref linkend="cll_chapter12-section12"/>,
<jbophrase>nuncti</jbophrase> has the place structure</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-Xhrx">
<title>
<anchor xml:id="c12e13d2"/>
</title>
<interlinear-gloss>
<jbo>n1 is the event of c1 eating c2</jbo>
</interlinear-gloss>
</example>
<para>Now we can transform the veljvo of
<jbophrase>nunctikezgau</jbophrase> into
<jbophrase>nuncti gasnu</jbophrase>. The g2 place (what is brought about by the actor g1) obviously denotes the same thing as n1 (the event of eating). So we can eliminate g2 as redundant, leaving us with a tentative place structure of</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-izvp">
+ <example xml:id="example-random-id-izvp">
<title>
<anchor xml:id="c12e13d3"/>
</title>
- <interlinear-gloss>
- <jbo>g1 is the actor in the event n1=g2 of c1 eating c2</jbo>
- </interlinear-gloss>
+ <para>g1 is the actor in the event n1=g2 of c1 eating c2</para>
</example>
<para>But it is also possible to omit the n1 place itself! The n1 place describes the event brought about; an event in Lojban is described as a bridi, by a selbri and its sumti; the selbri is already known (it's the seltau), and the sumti are also already known (they're in the lujvo place structure). So n1 would not give us any information we didn't already know. In fact, the n1=g2 place is dependent on c1 and c2 jointly - it does not depend on either c1 or c2 by itself. Being dependent and derived from the seltau, it is omissible. So the final place structure of
<jbophrase>nunctikezgau</jbophrase> is:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-9oTP">
+ <example xml:id="example-random-id-9oTP">
<title>
<anchor xml:id="c12e13d4"/>
</title>
- <interlinear-gloss>
- <jbo>g1 is the actor in the event of c1 eating c2</jbo>
- </interlinear-gloss>
+ <para>g1 is the actor in the event of c1 eating c2</para>
</example>
<para>There is one further step that can be taken. As we have already seen with
<jbophrase>balsoi</jbophrase> in
<xref linkend="cll_chapter12-section5"/>, the interpretation of lujvo is constrained by the semantics of gismu and of their sumti places. Now, any asymmetrical lujvo with
<jbophrase>gasnu</jbophrase> as its tertau will involve an event abstraction either implicitly or explicitly, since that is how the g2 place of
<jbophrase>gasnu</jbophrase> is defined.</para>
<para>Therefore, if we assume that
<jbophrase>nu</jbophrase> is the type of abstraction one would expect to be a
<jbophrase>se gasnu</jbophrase>, then the rafsi
@@ -1273,184 +1173,158 @@
<jbophrase>do</jbophrase> as
<quote>bring about an event</quote>; so the seltau must refer to an event,
<jbophrase>nu citka</jbophrase>. The English slang meanings of
<quote>do someone</quote>, namely
<quote>socialize with someone</quote> and
<quote>have sex with someone</quote>, are not relevant to
<jbophrase>gasnu</jbophrase>.)</para>
<para>So we can simply use
<jbophrase>ctigau</jbophrase> with the same place structure as
<jbophrase>nunctikezgau</jbophrase>:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-ITvd">
+ <example xml:id="example-random-id-ITvd">
<title>
<anchor xml:id="c12e13d5"/>
</title>
- <interlinear-gloss>
- <jbo>agent g1 causes c1 to eat c2</jbo>
- <en>g1 feeds c2 to c1.</en>
- </interlinear-gloss>
+ <para>agent g1 causes c1 to eat c2</para>
+ <para>g1 feeds c2 to c1.</para>
</example>
<para>This particular kind of asymmetrical lujvo, in which the seltau serves as the selbri of an abstraction which is a place of the tertau, is called an implicit-abstraction lujvo, because one deduces the presence of an abstraction which is unexpressed (implicit).</para>
<para>To give another example: the gismu
<jbophrase>basti</jbophrase>, whose place structure is</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-3LIm">
+ <example xml:id="example-random-id-3LIm">
<title>
<anchor xml:id="c12e13d6"/>
</title>
- <interlinear-gloss>
- <jbo>b1 replaces b2 in circumstances b3</jbo>
- </interlinear-gloss>
+ <para>b1 replaces b2 in circumstances b3</para>
</example>
<para>can form the lujvo
<jbophrase>basygau</jbophrase>, with the place structure:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-byp8">
+ <example xml:id="example-random-id-byp8">
<title>
<anchor xml:id="c12e13d7"/>
</title>
- <interlinear-gloss>
- <jbo>g1 (agent) replaces b1 with b2 in circumstances b3</jbo>
- </interlinear-gloss>
+ <para>g1 (agent) replaces b1 with b2 in circumstances b3</para>
</example>
<para>where both
<jbophrase>basti</jbophrase> and
<jbophrase>basygau</jbophrase> are translated
<quote>replace</quote> in English, but represent different relations:
<jbophrase>basti</jbophrase> may be used with no mention of any agent doing the replacing.</para>
<para>In addition,
<jbophrase>gasnu</jbophrase>-based lujvo can be built from what we would consider nouns or adjectives in English. In Lojban, everything is a predicate, so adjectives, nouns and verbs are all treated in the same way. This is consistent with the use of similar causative affixes in other languages. For example, the gismu
<jbophrase>litki</jbophrase>, meaning
<quote>liquid</quote>, with the place structure</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-tDsX">
+ <example xml:id="example-random-id-tDsX">
<title>
<anchor xml:id="c12e13d8"/>
</title>
- <interlinear-gloss>
- <jbo>l1 is a quantity of liquid of composition l2 under conditions l3</jbo>
- </interlinear-gloss>
+ <para>l1 is a quantity of liquid of composition l2 under conditions l3</para>
</example>
<para>can give
<jbophrase>likygau</jbophrase>, meaning
<quote>to liquefy</quote>:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-p5Bt">
+ <example xml:id="example-random-id-p5Bt">
<title>
<anchor xml:id="c12e13d9"/>
</title>
- <interlinear-gloss>
- <jbo>g1 (agent) causes l1 to be a quantity of liquid of composition l2</jbo>
- <en>under conditions l3.</en>
- </interlinear-gloss>
+ <para>g1 (agent) causes l1 to be a quantity of liquid of composition l2 under conditions l3.</para>
</example>
<para>While
<jbophrase>likygau</jbophrase> correctly represents
<quote>causes to be a liquid</quote>, a different lujvo based on
<jbophrase>galfi</jbophrase> (meaning
<quote>modify</quote>) may be more appropriate for
<quote>causes to become a liquid</quote>. On the other hand,
<jbophrase>fetsygau</jbophrase> is potentially confusing, because it could mean
<quote>agent in the event of something becoming female</quote> (the implicit-abstraction interpretation) or simply
<quote>female agent</quote> (the parallel interpretation), so using implicit-abstraction lujvo is always accompanied with some risk of being misunderstood.</para>
<para>Many other Lojban gismu have places for event abstractions, and therefore are good candidates for the tertau of an implicit-abstraction lujvo. For example, lujvo based on
<jbophrase>rinka</jbophrase>, with its place structure</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-Pmz8">
+ <example xml:id="example-random-id-Pmz8">
<title>
<anchor xml:id="c12e13d10"/>
</title>
- <interlinear-gloss>
- <jbo>event r1 causes event r2 to occur</jbo>
- </interlinear-gloss>
+ <para>event r1 causes event r2 to occur</para>
</example>
<para>are closely related to those based on
<jbophrase>gasnu</jbophrase>. However,
<jbophrase>rinka</jbophrase> is less generally useful than
<jbophrase>gasnu</jbophrase>, because its r1 place is another event rather than a person:
<jbophrase>lo rinka</jbophrase> is a cause, not a causer. Thus the place structure of
<jbophrase>likyri'a</jbophrase>, a lujvo analogous to
<jbophrase>likygau</jbophrase>, is</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-1HT3">
+ <example xml:id="example-random-id-1HT3">
<title>
<anchor xml:id="c12e13d11"/>
</title>
- <interlinear-gloss>
- <jbo>event r1 causes l1 to be a quantity of liquid</jbo>
- <en>of composition l2 under conditions l3</en>
- </interlinear-gloss>
+ <para>event r1 causes l1 to be a quantity of liquid of composition l2 under conditions l3</para>
</example>
<para>and would be useful in translating sentences like
<quote>The heat of the sun liquefied the block of ice.</quote></para>
<para>Implicit-abstraction lujvo are a powerful means in the language of rendering quite verbose bridi into succinct and manageable concepts, and increasing the expressive power of the language.</para>
</section>
<section xml:id="cll_chapter12-section14">
<title>Anomalous lujvo</title>
<para>Some lujvo that have been coined and actually employed in Lojban writing do not follow the guidelines expressed above, either because the places that are equivalent in the seltau and the tertau are in an unusual position, or because the seltau and tertau are related in a complex way, or both. An example of the first kind is
<jbophrase>jdaselsku</jbophrase>, meaning
<quote>prayer</quote>, which was mentioned in
<xref linkend="cll_chapter12-section7"/>. The gismu places are:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-qJEQ">
+ <example xml:id="example-random-id-qJEQ">
<title>
<anchor xml:id="c12e14d1"/>
</title>
- <interlinear-gloss>
- <jbo>
- <jbophrase>lijda</jbophrase>: l1 is a religion with believers l2 and beliefs l3</jbo>
- <en>
- <jbophrase>cusku</jbophrase>: c1 expresses text c2 to audience c3 in medium c4</en>
- </interlinear-gloss>
+ <para>
+ <jbophrase>lijda</jbophrase>: l1 is a religion with believers l2 and beliefs l3</para>
+ <para>
+ <jbophrase>cusku</jbophrase>: c1 expresses text c2 to audience c3 in medium c4</para>
</example>
<para>and
<jbophrase>selsku</jbophrase>, the tertau of
<jbophrase>jdaselsku</jbophrase>, has the place structure</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-qW3w">
+ <example xml:id="example-random-id-qW3w">
<title>
<anchor xml:id="c12e14d2"/>
</title>
- <interlinear-gloss>
- <jbo>s1 is a text expressed by s2 to audience s3 in medium s4</jbo>
- </interlinear-gloss>
+ <para>s1 is a text expressed by s2 to audience s3 in medium s4</para>
</example>
<para>Now it is easy to see that the l2 and s2 places are equivalent: the believer in the religion (l2) is the one who expresses the prayer (s2). This is not one of the cases for which a place ordering rule has been given in
<xref linkend="cll_chapter12-section7"/> or
<xref linkend="cll_chapter12-section13"/>; therefore, for lack of a better rule, we put the tertau places first and the remaining seltau places after them, leading to the place structure:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-41dc">
+ <example xml:id="example-random-id-41dc">
<title>
<anchor xml:id="c12e14d3"/>
</title>
- <interlinear-gloss>
- <jbo>s1 is a prayer expressed by s2=l2 to audience s3 in medium s4</jbo>
- <en>pertaining to religion l1</en>
- </interlinear-gloss>
+ <para>s1 is a prayer expressed by s2=l2 to audience s3 in medium s4 pertaining to religion l1</para>
</example>
<para>The l3 place (the beliefs of the religion) is dependent on the l1 place (the religion) and so is omitted.</para>
<para>We could make this lujvo less messy by replacing it with
<jbophrase>se seljdasku</jbophrase>, where
<jbophrase>seljdasku</jbophrase> is a normal symmetrical lujvo with place structure:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-7Tdb">
+ <example xml:id="example-random-id-7Tdb">
<title>
<anchor xml:id="c12e14d4"/>
</title>
- <interlinear-gloss>
- <jbo>c1=l2 religiously expresses prayer c2 to audience c3 in medium s4</jbo>
- <en>pertaining to religion l1</en>
- </interlinear-gloss>
+ <para>c1=l2 religiously expresses prayer c2 to audience c3 in medium s4 pertaining to religion l1</para>
</example>
<para>which, according to the rule expressed in
<xref linkend="cll_chapter12-section9"/>, can be further expressed as
<jbophrase>selseljdasku</jbophrase>. However, there is no need for the ugly
<jbophrase>selsel-</jbophrase> prefix just to get the rules right:
<jbophrase>jdaselsku</jbophrase> is a reasonable, if anomalous, lujvo.</para>
<para>However, there is a further problem with
<jbophrase>jdaselsku</jbophrase>, not resolvable by using
<jbophrase>seljdasku</jbophrase>. No veljvo involving just the two gismu
<jbophrase>lijda</jbophrase> and
@@ -1462,84 +1336,74 @@
<xref linkend="chapter-selbri"/>, is
<jbophrase>lange'u</jbophrase>, meaning
<quote>sheepdog</quote>. Clearly a sheepdog is not a dog which is a sheep (the symmetrical interpretation is wrong), nor a dog of the sheep breed (the asymmetrical interpretation is wrong). Indeed, there is simply no overlap in the places of
<jbophrase>lanme</jbophrase> and
<jbophrase>gerku</jbophrase> at all. Rather, the lujvo refers to a dog which controls sheep flocks, a
<jbophrase>terlanme jitro gerku</jbophrase>, the lujvo from which is
<jbophrase>terlantroge'u</jbophrase> with place structure:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-TW5Q">
+ <example xml:id="example-random-id-TW5Q">
<title>
<anchor xml:id="c12e14d5"/>
</title>
- <interlinear-gloss>
- <jbo>g1=j1 is a dog that controls sheep flock l3=j2 made up of sheep l1</jbo>
-
- <en>in activity j3 of dog breed g2</en>
- </interlinear-gloss>
+ <para>g1=j1 is a dog that controls sheep flock l3=j2 made up of sheep l1 in activity j3 of dog breed g2</para>
</example>
<para>based on the gismu place structures</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-CXeL">
+ <example xml:id="example-random-id-CXeL">
<title>
<anchor xml:id="c12e14d6"/>
</title>
- <interlinear-gloss>
- <jbo>
- <jbophrase>lanme</jbophrase>: l1 is a sheep of breed l2 belonging to flock l3</jbo>
- <gloss>
- <jbophrase>gerku</jbophrase>: g1 is a dog of breed g2</gloss>
- <en>
- <jbophrase>jitro</jbophrase>: j1 controls j2 in activity j3</en>
- </interlinear-gloss>
+ <para>
+ <jbophrase>lanme</jbophrase>: l1 is a sheep of breed l2 belonging to flock l3</para>
+ <para>
+ <jbophrase>gerku</jbophrase>: g1 is a dog of breed g2</para>
+ <para>
+ <jbophrase>jitro</jbophrase>: j1 controls j2 in activity j3</para>
</example>
<para>Note that this lujvo is symmetrical between
<jbophrase>lantro</jbophrase> (sheep-controller) and
<jbophrase>gerku</jbophrase>, but
<jbophrase>lantro</jbophrase> is itself an asymmetrical lujvo. The l2 place, the breed of sheep, is removed as dependent on l1. However, the lujvo
<jbophrase>lange'u</jbophrase> is both shorter than
<jbophrase>terlantroge'u</jbophrase> and sufficiently clear to warrant its use: its place structure, however, should be the same as that of the longer lujvo, for which
<jbophrase>lange'u</jbophrase> can be understood as an abbreviation.</para>
<para>Another example is
<jbophrase>xanmi'e</jbophrase>,
<quote>to command by hand, to beckon</quote>. The component place structures are:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-VjbP">
+ <example xml:id="example-random-id-VjbP">
<title>
<anchor xml:id="c12e14d7"/>
</title>
- <interlinear-gloss>
- <jbo>
- <jbophrase>xance</jbophrase>: xa1 is the hand of xa2</jbo>
- <en>
- <jbophrase>minde</jbophrase>: m1 gives commands to m2 to cause m3 to happen</en>
+ <para>
+ <jbophrase>xance</jbophrase>: xa1 is the hand of xa2</para>
+ <para>
+ <jbophrase>minde</jbophrase>: m1 gives commands to m2 to cause m3 to happen</para>
- </interlinear-gloss>
</example>
<para>The relation between the seltau and tertau is close enough for there to be an overlap: xa2 (the person with the hand) is the same as m1 (the one who commands). But interpreting
<jbophrase>xanmi'e</jbophrase> as a symmetrical lujvo with an elided
<jbophrase>sel-</jbophrase> in the seltau, as if from
<jbophrase>se xance minde</jbophrase>, misses the point: the real relation expressed by the lujvo is not just
<quote>one who commands and has a hand</quote>, but
<quote>to command using the hand</quote>. The concept of
<quote>using</quote> suggests the gismu
<jbophrase>pilno</jbophrase>, with place structure</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-sqQN">
+ <example xml:id="example-random-id-sqQN">
<title>
<anchor xml:id="c12e14d8"/>
</title>
- <interlinear-gloss>
- <jbo>p1 uses tool p2 for purpose p3</jbo>
- </interlinear-gloss>
+ <para>p1 uses tool p2 for purpose p3</para>
</example>
<para>Some possible three-part veljvo are (depending on how strictly you want to constrain the veljvo)</para>
<example xml:id="example-random-id-qfe4" role="interlinear-gloss-example">
<title>
<anchor xml:id="c12e14d9"/>
</title>
<interlinear-gloss>
<jbo>[ke] xance pilno [ke'e] minde</jbo>
<gloss>(hand user) type-of commander</gloss>
</interlinear-gloss>
@@ -1588,42 +1452,38 @@
<quote>more</quote> and
<quote>most</quote>, respectively. The Lojbanic equivalents, which can be made from any brivla, are lujvo with the tertau
<jbophrase>zmadu</jbophrase>,
<jbophrase>mleca</jbophrase>,
<jbophrase>zenba</jbophrase>,
<jbophrase>jdika</jbophrase>, and
<jbophrase>traji</jbophrase>. In order to make these lujvo regular and easy to make, certain special guidelines are imposed.</para>
<para>We will begin with lujvo based on
<jbophrase>zmadu</jbophrase> and
<jbophrase>mleca</jbophrase>, whose place structures are:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-mn8T">
+ <example xml:id="example-random-id-mn8T">
<title>
<anchor xml:id="c12e15d1"/>
</title>
- <interlinear-gloss>
- <jbo>
- <jbophrase>zmadu</jbophrase>: z1 is more than z2 in property z3 in quantity z4</jbo>
- <en>
- <jbophrase>mleca</jbophrase>: m1 is less than m2 in property m3 in quantity m4</en>
- </interlinear-gloss>
+ <para>
+ <jbophrase>zmadu</jbophrase>: z1 is more than z2 in property z3 in quantity z4</para>
+ <para>
+ <jbophrase>mleca</jbophrase>: m1 is less than m2 in property m3 in quantity m4</para>
</example>
<para>For example, the concept
<quote>young</quote> is expressed by the gismu
<jbophrase>citno</jbophrase>, with place structure</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-ciaK">
+ <example xml:id="example-random-id-ciaK">
<title>
<anchor xml:id="c12e15d2"/>
</title>
- <interlinear-gloss>
- <jbo>
- <jbophrase>citno</jbophrase>: c1 is young</jbo>
- </interlinear-gloss>
+ <para>
+ <jbophrase>citno</jbophrase>: c1 is young</para>
</example>
<para> <indexterm type="example-imported"><primary>younger</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo place order</primary><secondary>comparatives</secondary></indexterm> The comparative concept
<quote>younger</quote> can be expressed by the lujvo
<jbophrase>citmau</jbophrase> (based on the veljvo
<jbophrase>citno zmadu</jbophrase>, meaning
<quote>young more-than</quote>).</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-GDt1">
<title>
<anchor xml:id="c12e15d3"/>
@@ -1631,28 +1491,26 @@
<interlinear-gloss>
<jbo>mi citmau do lo nanca be li xa</jbo>
<gloss>I am-younger-than you by-years the-number six.</gloss>
<en>I am six years younger than you.</en>
</interlinear-gloss>
</example>
<para>The place structure for
<jbophrase>citmau</jbophrase> is</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-I3Uh">
+ <example xml:id="example-random-id-I3Uh">
<title>
<anchor xml:id="c12e15d4"/>
</title>
- <interlinear-gloss>
- <jbo>z1=c1 is younger than z2=c1 by amount z4</jbo>
+ <para>z1=c1 is younger than z2=c1 by amount z4</para>
- </interlinear-gloss>
</example>
<para>Similarly, in Lojban you can say:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-tJDa">
<title>
<anchor xml:id="c12e15d5"/>
</title>
<interlinear-gloss>
<jbo>do citme'a mi lo nanca be li xa</jbo>
<gloss>You are-less-young-than me by-years the-number six.</gloss>
<en>You are six years less young than me.</en>
@@ -1677,38 +1535,34 @@
<quote>X likes Y more than X likes Z</quote>, or
<quote>X likes Y more than Z likes Y</quote>? Does
<jbophrase>klamau</jbophrase> mean:
<quote>X goes to Y more than to Z</quote>,
<quote>X goes to Y more than Z does</quote>,
<quote>X goes to Y from Z more than from W</quote>, or what?</para>
<para> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>comparative lujvo</secondary></indexterm> <indexterm type="general-imported"><primary>comparative lujvo</primary><secondary>standardized meanings</secondary></indexterm> We answer this concern by putting regularity above any considerations of concept usefulness: by convention, the two things being compared always fit into the first place of the seltau. In that way, each of the different possible interpretations can be expressed by SE-converting the seltau, and making the required place the new first place. As a result, we get the following comparative lujvo place structures:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-eSTr">
+ <example xml:id="example-random-id-eSTr">
<title>
<anchor xml:id="c12e15d6"/>
</title>
- <interlinear-gloss>
- <jbo>
- <jbophrase>nelcymau</jbophrase>: z1, more than z2, likes n2 by amount z4</jbo>
- <gloss>
- <jbophrase>selnelcymau</jbophrase>: z1, more than z2, is liked by n1 in amount z4</gloss>
- <gloss>
- <jbophrase>klamau</jbophrase>: z1, more than z2, goes to k2 from k3 via k4 by means of k5</gloss>
- <gloss>
- <jbophrase>selklamau</jbophrase>: z1, more than z2, is gone to by k1 from k3 via k4</gloss>
- <gloss>by means of k5</gloss>
- <gloss>
- <jbophrase>terklamau</jbophrase>: z1, more than z2, is an origin point from destination k2</gloss>
- <en>for k1's going via k4 by means of k5</en>
- </interlinear-gloss>
+ <para>
+ <jbophrase>nelcymau</jbophrase>: z1, more than z2, likes n2 by amount z4</para>
+ <para>
+ <jbophrase>selnelcymau</jbophrase>: z1, more than z2, is liked by n1 in amount z4</para>
+ <para>
+ <jbophrase>klamau</jbophrase>: z1, more than z2, goes to k2 from k3 via k4 by means of k5</para>
+ <para>
+ <jbophrase>selklamau</jbophrase>: z1, more than z2, is gone to by k1 from k3 via k4 by means of k5</para>
+ <para>
+ <jbophrase>terklamau</jbophrase>: z1, more than z2, is an origin point from destination k2 for k1's going via k4 by means of k5</para>
</example>
<para>(See
<xref linkend="chapter-abstractions"/> for the way in which this problem is resolved when lujvo aren't used.)</para>
<para>The ordering rule places the things being compared first, and the other seltau places following. Unfortunately the z4 place, which expresses by how much one entity exceeds the other, is displaced into a lujvo place whose number is different for each lujvo. For example, while
<jbophrase>nelcymau</jbophrase> has z4 as its fourth place,
<jbophrase>klamau</jbophrase> has it as its sixth place. In any sentence where a difficulty arises, this amount-place can be redundantly tagged with
<jbophrase>vemau</jbophrase> (for
<jbophrase>zmadu</jbophrase>) or
<jbophrase>veme'a</jbophrase> (for
<jbophrase>mleca</jbophrase>) to help make the speaker's intention clear.</para>
@@ -1749,59 +1603,51 @@
<anchor xml:id="c12e15d8"/>
</title>
<interlinear-gloss>
<jbo>mi ca tsaze'a</jbo>
<en>I increase in strength.</en>
</interlinear-gloss>
</example>
<para>Finally, lujvo with a tertau of
<jbophrase>traji</jbophrase> are used to build superlatives. The place structure of
<jbophrase>traji</jbophrase> is</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-N3cU">
+ <example xml:id="example-random-id-N3cU">
<title>
<anchor xml:id="c12e15d9"/>
</title>
- <interlinear-gloss>
- <jbo>t1 is superlative in property t2, being the t3 extremum (largest by default) of set t4</jbo>
- </interlinear-gloss>
+ <para>t1 is superlative in property t2, being the t3 extremum (largest by default) of set t4</para>
</example>
<para>Consider the gismu
<jbophrase>xamgu</jbophrase>, whose place structure is:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-MWdr">
+ <example xml:id="example-random-id-MWdr">
<title>
<anchor xml:id="c12e15d10"/>
</title>
- <interlinear-gloss>
- <jbo>xa1 is good for xa2 by standard xa3</jbo>
- </interlinear-gloss>
+ <para>xa1 is good for xa2 by standard xa3</para>
</example>
<para> <indexterm type="example-imported"><primary>better</primary><secondary>example</secondary></indexterm> The comparative form is
<jbophrase>xagmau</jbophrase>, corresponding to English
<quote>better</quote>, with a place structure (by the rules given above) of</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-pR5R">
+ <example xml:id="example-random-id-pR5R">
<title>
<anchor xml:id="c12e15d11"/>
</title>
- <interlinear-gloss>
- <jbo>z1 is better than z2 for xa2 by standard xa3 in amount z4</jbo>
- </interlinear-gloss>
+ <para>z1 is better than z2 for xa2 by standard xa3 in amount z4</para>
</example>
<para> <indexterm type="general-imported"><primary>lujvo place order</primary><secondary>superlatives</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo place structure</primary><secondary>superlatives</secondary></indexterm> We would expect the place structure of
<jbophrase>xagrai</jbophrase>, the superlative form, to somehow mirror that, given that comparatives and superlatives are comparable concepts, resulting in:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-Cc6J">
+ <example xml:id="example-random-id-Cc6J">
<title>
<anchor xml:id="c12e15d12"/>
</title>
- <interlinear-gloss>
- <jbo>xa1=t1 is the best of the set t4 for xa2 by standard xa3.</jbo>
- </interlinear-gloss>
+ <para>xa1=t1 is the best of the set t4 for xa2 by standard xa3.</para>
</example>
<para>The t2 place in
<jbophrase>traji</jbophrase>, normally filled by a property abstraction, is replaced by the seltau places, and the t3 place specifying the extremum of
<jbophrase>traji</jbophrase> (whether the most or the least, that is) is presumed by default to be
<quote>the most</quote>.</para>
<para> <indexterm type="general-imported"><primary>lujvo place order</primary><secondary>superlatives as exceptions</secondary></indexterm> But the set against which the t1 place of
<jbophrase>traji</jbophrase> is compared is not the t2 place (which would make the place structure of
<jbophrase>traji</jbophrase> fully parallel to that of
@@ -1843,77 +1689,69 @@
</listitem>
<listitem>
<para>Metaphysical necessity can either increase or decrease places: it is a pressure tending to provide the
<quote>right number</quote> of places. If something is part of the essential nature of a concept, then a place must be made for it; on the other hand, if instances of the concept need not have some property, then this pressure will tend to remove the place.</para>
</listitem>
<listitem>
<para>Regularity is a pressure which can also either increase or decrease places. If a gismu has a given place, then gismu which are semantically related to it are likely to have the place also.</para>
</listitem>
</itemizedlist>
<para>Here are some examples of gismu place structures, with a discussion of the pressures operating on them:</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-iu0B">
+ <example xml:id="example-random-id-iu0B">
<title>
<anchor xml:id="c12e16d1"/>
</title>
- <interlinear-gloss>
- <jbo>
- <jbophrase>xekri</jbophrase>: xe1 is black</jbo>
- </interlinear-gloss>
+ <para>
+ <jbophrase>xekri</jbophrase>: xe1 is black</para>
</example>
<para> <indexterm type="general-imported"><primary>color standards</primary></indexterm> Brevity was the most important goal here, reinforced by one interpretation of metaphysical necessity. There is no mention of color standards here, as many people have pointed out; like all color gismu,
<jbophrase>xekri</jbophrase> is explicitly subjective. Objective color standards can be brought in by an appropriate BAI tag such as
<jbophrase>ci'u</jbophrase> (
<quote>in system</quote>; see
<xref linkend="chapter-sumti-tcita"/>) or by making a lujvo.</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-cuYP">
+ <example xml:id="example-random-id-cuYP">
<title>
<anchor xml:id="c12e16d2"/>
</title>
- <interlinear-gloss>
- <jbo>
- <jbophrase>jbena</jbophrase>: j1 is born to j2 at time j3 and location j4</jbo>
- </interlinear-gloss>
+ <para>
+ <jbophrase>jbena</jbophrase>: j1 is born to j2 at time j3 and location j4</para>
</example>
<para>The gismu
<jbophrase>jbena</jbophrase> contains places for time and location, which few other gismu have: normally, the time and place at which something is done is supplied by a tense tag (see
<xref linkend="chapter-tenses"/>). However, providing these places makes
<jbophrase>le te jbena</jbophrase> a simple term for
<quote>birthday</quote> and
<jbophrase>le ve jbena</jbophrase> for
<quote>birthplace</quote>, so these places were provided despite their lack of metaphysical necessity.</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-NTJn">
+ <example xml:id="example-random-id-NTJn">
<title>
<anchor xml:id="c12e16d3"/>
</title>
- <interlinear-gloss>
- <jbo>
- <jbophrase>rinka</jbophrase>: event r1 is the cause of event r2</jbo>
- </interlinear-gloss>
+ <para>
+ <jbophrase>rinka</jbophrase>: event r1 is the cause of event r2</para>
</example>
<para> <indexterm type="general-imported"><primary>melting</primary></indexterm> The place structure of
<jbophrase>rinka</jbophrase> does not have a place for the agent, the one who causes, as a result of the pressure toward metaphysical necessity. A cause-effect relationship does not have to include an agent: an event (such as snow melting in the mountains) may cause another event (such as the flooding of the Nile) without any human intervention or even knowledge.</para>
<para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>as suppliers of agent place</secondary></indexterm> Indeed, there is a general tendency to omit agent places from most gismu except for a few such as
<jbophrase>gasnu</jbophrase> and
<jbophrase>zukte</jbophrase> which are then used as tertau in order to restore the agent place when needed: see
<xref linkend="cll_chapter12-section13"/>.</para>
- <example role="interlinear-gloss-example" xml:id="example-random-id-Atby">
+ <example xml:id="example-random-id-Atby">
<title>
<anchor xml:id="c12e16d4"/>
</title>
- <interlinear-gloss>
- <jbo>
- <jbophrase>cinfo</jbophrase>: c1 is a lion of species/breed c2</jbo>
- </interlinear-gloss>
+ <para>
+ <jbophrase>cinfo</jbophrase>: c1 is a lion of species/breed c2</para>
</example>
<para> <indexterm type="general-imported"><primary>diversified species</primary></indexterm> <indexterm type="general-imported"><primary>general terms</primary></indexterm> The c2 place of
<jbophrase>cinfo</jbophrase> is provided as a result of the pressure toward regularity. All animal and plant gismu have such an x2 place; although there is in fact only one species of lion, and breeds of lion, though they exist, aren't all that important in talking about lions. The species/breed place must exist for such diversified species as dogs, and for general terms like
<jbophrase>cinki</jbophrase> (insect), and are provided for all other animals and plants as a matter of regularity.</para>
<para> <indexterm type="general-imported"><primary>gismu</primary><secondary>place order</secondary><tertiary>rationale</tertiary></indexterm> Less can be said about gismu place structure ordering, but some regularities are apparent. The places tend to appear in decreasing order of psychological saliency or importance. There is an implication within the place structure of
<jbophrase>klama</jbophrase>, for example, that
<jbophrase>lo klama</jbophrase> (the one going) will be talked about more often, and is thus more important, than
--
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.