[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bpfk] dag-cll git updates for Fri May 6 17:21:06 EDT 2011
commit 7c64936dc38f11476d01992195c9a7eeb75f1417
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date: Fri May 6 14:07:33 2011 -0700
Fixed the examples.
diff --git a/todocbook/12.xml b/todocbook/12.xml
index e37dc4b..1bbb5fa 100644
--- a/todocbook/12.xml
+++ b/todocbook/12.xml
@@ -72,21 +72,21 @@
<para> <indexterm type="general-imported"><primary>tanru</primary><secondary>purpose</secondary></indexterm> <indexterm type="general-imported"><primary>wine-dark sea</primary></indexterm> The purpose of a tanru is to join concepts together without necessarily focusing on the exact meaning of the seltau. For example, in the
<citetitle>Iliad</citetitle>, the poet talks about
<quote>the wine-dark sea</quote>, in which
<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>
+<indexterm type="general"><primary>goer-house</primary><secondary>example</secondary></indexterm>
As a simple example, consider the rather non-obvious tanru
<oldjbophrase>klama zdani</oldjbophrase>, or
<quote>goer-house</quote>. The gismu
<valsi>zdani</valsi> has two places:</para>
<example xml:id="example-random-id-xcfi">
<title>
<anchor xml:id="c12e2d1"/>
</title>
@@ -101,21 +101,21 @@
</title>
<para><definition>x1 goes to destination x2 from origin point x3 via route x4 using means x5</definition></para>
</example>
<para>The tanru
<oldjbophrase>klama zdani</oldjbophrase> will also have two places, namely those of
<valsi>zdani</valsi>. Since a
<oldjbophrase>klama zdani</oldjbophrase> is a type of
<valsi>zdani</valsi>, 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"><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:
<oldjbophrase>gerku zdani</oldjbophrase>, literally
<quote>dog house</quote>. A tanru expresses a very loose relation: a
<oldjbophrase>gerku zdani</oldjbophrase> is a house that has something to do with some dog or dogs. What the precise relation might be is left unstated. Thus, the meaning of
<oldjbophrase>lo gerku zdani</oldjbophrase> can include all of the following: houses occupied by dogs, houses shaped by dogs, dogs which are also houses (e.g. houses for fleas), houses named after dogs, and so on. All that is essential is that the place structure of
<valsi>zdani</valsi> continues to apply.</para>
@@ -127,37 +127,37 @@
<valsi>zdani</valsi> and some place of
<valsi>gerku</valsi>. It doesn't matter which places, because if there's a relationship between some place of
<valsi>zdani</valsi> and any place of
<valsi>gerku</valsi>, then that relationship can be compounded with the relationship between the places of
<valsi>gerku</valsi>- namely,
<valsi>gerku</valsi> itself – to reach any of the other
<valsi>gerku</valsi> places. Thus, if the relationship turns out to be between z2 and g2, we can still state r in terms of z1 and g1:
<quote>the relationship involves the dog g1, whose breed has to do with the occupant of the house z1</quote>.</para>
<para>
-<indexterm type="example-imported"><primary>Bill Clinton</primary><secondary>example</secondary></indexterm>
Doubtless to the relief of the reader, here's an illustration. We want to find out whether the White House (the one in which the U. S. President lives, that is) counts as a
<oldjbophrase>gerku zdani</oldjbophrase>. We go through the five variables. The White House is the z1. It houses Bill Clinton as z2, as of this writing, so it counts as a
<valsi>zdani</valsi>. Let's take a dog – say, Spot (g1). Spot has to have a breed; let's say it's a Saint Bernard (g2). Now, the White House counts as a
<oldjbophrase>gerku zdani</oldjbophrase> if there is any relationship (r) at all between the White House and Spot. (We'll choose the g1 and z1 places to relate by r; we could have chosen any other pair of places, and simply gotten a different relationship.)</para>
<para> <indexterm type="general-imported"><primary>Chelsea Clinton</primary></indexterm> The sky is the limit for r; it can be as complicated as
<quote>The other day, g1 (Spot) chased Socks, who is owned by Chelsea Clinton, who is the daughter of Bill Clinton, who lives in z1 (the White House)</quote> or even worse. If no such r can be found, well, you take another dog, and keep going until no more dogs can be found. Only then can we say that the White House cannot fit into the first place of
<oldjbophrase>gerku zdani</oldjbophrase>.</para>
<para>As we have seen, no less than five elements are involved in the definition of
<oldjbophrase>gerku zdani</oldjbophrase>: 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"/>
+ <indexterm type="example"><primary>Bill Clinton</primary><secondary>example</secondary></indexterm>
</title>
<interlinear-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
<oldjbophrase>gerku zdani</oldjbophrase>, then the meaning of
@@ -193,25 +193,20 @@
<valsi>gerku</valsi>. 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="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
<valsi>zdani</valsi>, and g2 is the second place of
<valsi>gerku</valsi>.)</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
<valsi>zdani</valsi> 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>
<anchor xml:id="c12e3d1"/>
</title>
<para><definition>z1 is a nest/house/lair/den of z2</definition></para>
</example>
<para>The place structure of
<valsi>gerku</valsi> is:</para>
<example xml:id="example-random-id-H4ed">
<title>
@@ -231,20 +226,21 @@
<example xml:id="example-random-id-MnKf">
<title>
<anchor xml:id="c12e3d4"/>
</title>
<para><definition>z1 is a house for dog g1 of breed g2</definition></para>
</example>
<para>or more comprehensively</para>
<example xml:id="example-random-id-Wx42">
<title>
<anchor xml:id="c12e3d5"/>
+ <indexterm type="example"><primary>doghouse</primary><secondary>example</secondary></indexterm>
</title>
<para><definition>z1 is a house for dweller/dog z2=g1 of breed g2</definition></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="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>
@@ -252,52 +248,51 @@
<oldjbophrase>se jbopli</oldjbophrase> or a
<oldjbophrase>te klagau</oldjbophrase> 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="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="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
<oldjbophrase>balsoi</oldjbophrase>: 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,
<oldjbophrase>banli sonci</oldjbophrase>. The underlying gismu place structures are:</para>
<example xml:id="example-random-id-7AFc">
<title>
<anchor xml:id="c12e5d1"/>
+ <indexterm type="example"><primary>great soldier</primary><secondary>example</secondary></indexterm>
</title>
<para><definition> <valsi>banli</valsi>: b1 is great in property b2 by standard b3</definition></para>
<para><definition> <valsi>sonci</valsi>: s1 is a soldier of army s2</definition></para>
</example>
<para>In this case the s1 place of
<valsi>sonci</valsi> is redundant, since it is equivalent to the b1 place of
<valsi>banli</valsi>. Therefore the place structure of
<oldjbophrase>balsoi</oldjbophrase> need not include places for both s1 and b1, as they refer to the same thing. So the place structure of
<oldjbophrase>balsoi</oldjbophrase> is at most</para>
<example xml:id="example-random-id-UtwF">
<title>
<anchor xml:id="c12e5d2"/>
</title>
<para><definition>b1=s1 is a great soldier of army s2 in property b2 by standard b3</definition></para>
</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
<oldjbophrase>tinju'i</oldjbophrase>,
<quote>to listen</quote> (
<quote>to hear attentively, to hear and pay attention</quote>). The place structures of the gismu
<valsi>tirna</valsi> and
<valsi>jundi</valsi> are:</para>
<example xml:id="example-random-id-rFiE">
<title>
@@ -306,20 +301,21 @@
<para><definition>
<valsi>tirna</valsi>: t1 hears sound t2 against background noise t3</definition></para>
<para><definition>
<valsi>jundi</valsi>: j1 pays attention to j2</definition></para>
</example>
<para> <indexterm type="general-imported"><primary>background noise</primary></indexterm> and the place structure of the lujvo is:</para>
<example xml:id="example-random-id-EUr1">
<title>
<anchor xml:id="c12e5d4"/>
+ <indexterm type="example"><primary>listen attentively</primary><secondary>example</secondary></indexterm>
</title>
<para><definition>j1=t1 listens to j2=t2 against background noise t3</definition></para>
</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 (
<valsi>gerku</valsi> 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
@@ -349,21 +345,20 @@
</example>
<para>However, although
<oldjbophrase>gerselzda</oldjbophrase> 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;
<oldjbophrase>gerzda</oldjbophrase> is simpler than
<oldjbophrase>gerselzda</oldjbophrase>.</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
<oldjbophrase>karcykla</oldjbophrase>, for example, is based on
<oldjbophrase>karce klama</oldjbophrase>, or
<quote>car goer</quote>. The place structure of
<valsi>karce</valsi> is:</para>
<example xml:id="example-random-id-S7W3">
<title>
<anchor xml:id="c12e5d7"/>
@@ -376,20 +371,21 @@
<example xml:id="example-random-id-GgxL">
<title>
<anchor xml:id="c12e5d8"/>
</title>
<para><definition>kl1 goes to car kl2=ka1 which carries ka2 propelled by ka3 from origin kl3 via route kl4 by means of kl5</definition></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 xml:id="example-random-id-QiHw">
<title>
<anchor xml:id="c12e5d9"/>
+ <indexterm type="example"><primary>car goer</primary><secondary>example</secondary></indexterm>
</title>
<para><definition>kl1 goes to destination kl2 from origin kl3 via route kl4 by means of car kl5=ka1 carrying ka2 propelled by ka3.</definition></para>
</example>
<para>instead.</para>
</section>
<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
@@ -412,26 +408,26 @@
<anchor xml:id="c12e6d2"/>
</title>
<interlinear-gloss>
<jbo>la mon. rePOS. gerzda la spat.</jbo>
<natlang>Mon Repos is a doghouse of Spot.</natlang>
</interlinear-gloss>
</example>
<para>
-<indexterm type="example-imported"><primary>Mon Repos</primary><secondary>example</secondary></indexterm>
really means</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-73x9">
<title>
<anchor xml:id="c12e6d3"/>
+ <indexterm type="example"><primary>Mon Repos</primary><secondary>example</secondary></indexterm>
</title>
<interlinear-gloss>
<jbo>la mon. rePOS. zdani la spat. noi gerku</jbo>
<natlang>Mon Repos is a house of Spot, who is a dog.</natlang>
</interlinear-gloss>
</example>
<para>since that is the interpretation we have given
<oldjbophrase>gerzda</oldjbophrase>. But that in turn means</para>
<para> <indexterm type="general-imported"><primary>unspecified breed</primary><secondary>example</secondary></indexterm> FIXME: TAG SPOT</para>
@@ -465,21 +461,20 @@
<interlinear-gloss>
<jbo>la mon. rePOS. gerzda la spat. noi ke'a gerku la sankt. berNARD. ku'o la sankt. berNARD.</jbo>
<natlang>Mon Repos is a doghouse of Spot, who is a dog of breed St. Bernard, of breed St. Bernard.</natlang>
</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
<oldjbophrase>cakcinki</oldjbophrase>, the lujvo for
<quote>beetle</quote>, based on the tanru
<oldjbophrase>calku cinki</oldjbophrase>, or
<quote>shell-insect</quote>. The gismu place structures are:</para>
<example xml:id="example-random-id-D0qb">
<title>
<anchor xml:id="c12e6d7"/>
@@ -488,20 +483,21 @@
<valsi>calku</valsi>: ca1 is a shell/husk around ca2 made of ca3</para>
<para>
<valsi>cinki</valsi>: ci1 is an insect/arthropod of species ci2</para>
</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 xml:id="example-random-id-n7JB">
<title>
<anchor xml:id="c12e6d8"/>
+ <indexterm type="example"><primary>beetle</primary><secondary>example</secondary></indexterm>
</title>
<para><definition>ci1=ca2 is a beetle of species ci2</definition></para>
</example>
<para>with not a single place of
<valsi>calku</valsi> 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
<oldjbophrase>cakcinki</oldjbophrase> 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>
@@ -517,104 +513,108 @@
<valsi>klama</valsi> tertau into a
<valsi>litru</valsi> or
<valsi>cliva</valsi> concept, for example: these gismu differ in their number of arguments, and suppressing places of
<valsi>klama</valsi> in a lujvo doesn't make any sense if the resulting modified place structure is that of
<valsi>litru</valsi> or
<valsi>cliva</valsi>.</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="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
<oldjbophrase>kuldi'u</oldjbophrase> (from
<oldjbophrase>ckule dinju</oldjbophrase>, and meaning
<quote>school building</quote>) needs to be</para>
<example xml:id="example-random-id-u6Xz">
<title>
<anchor xml:id="c12e6d9"/>
+ <indexterm type="example"><primary>school building</primary><secondary>example</secondary></indexterm>
</title>
<para><definition>d1 is a building housing school c1 teaching subject c3 to audience c4</definition></para>
</example>
<para>even though c3 and c4 are plainly dependent on c1. The other places of
<valsi>ckule</valsi>, 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="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
<oldjbophrase>jdaselsku</oldjbophrase>, meaning
<quote>prayer</quote>. In the sentence</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-FfWn">
<title>
<anchor xml:id="c12e7d1"/>
+ <indexterm type="example"><primary>prayer</primary><secondary>example</secondary></indexterm>
+ <indexterm type="example"><primary>Dong</primary><secondary>example</secondary></indexterm>
</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 xml:id="example-random-id-b38f">
<title>
<anchor xml:id="c12e7d2"/>
+ <indexterm type="example"><primary>prayer</primary><secondary>example</secondary></indexterm>
+ <indexterm type="example"><primary>Dong</primary><secondary>example</secondary></indexterm>
</title>
<para>This is a prayer by Dong</para>
</example>
<para>or is the entity being prayed to, resulting in</para>
<example xml:id="example-random-id-uL3V">
<title>
<anchor xml:id="c12e7d3"/>
+ <indexterm type="example"><primary>prayer</primary><secondary>example</secondary></indexterm>
+ <indexterm type="example"><primary>Dong</primary><secondary>example</secondary></indexterm>
</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="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
<oldjbophrase>balsoi</oldjbophrase> (from
<xref linkend="section-symmetrical-asymmetrical"/>) has the places of its tertau followed by whatever places of the seltau survive the elimination process. For
<oldjbophrase>balsoi</oldjbophrase>, the surviving places of
<valsi>banli</valsi> are b2 and b3, leading to the place structure:</para>
<example xml:id="example-random-id-rv1m">
<title>
<anchor xml:id="c12e7d4"/>
+ <indexterm type="example"><primary>great soldier</primary><secondary>example</secondary></indexterm>
</title>
<para><definition>b1=s1 is a great soldier of army s2 in property b2 by standard b3</definition></para>
</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"/>
@@ -633,21 +633,20 @@
<jbo>b1 sonci s2 gi'e banli b2 b3</jbo>
<gloss>b1 is-a-soldier of-army-s2 and is-great in-property-b2 by-standard-b3</gloss>
</interlinear-gloss>
</example>
<para>where
<valsi>gi'e</valsi> is the Lojban word for
<quote>and</quote> when placed between two partial bridi, as explained in
<xref linkend="section-compound-bridi"/>.</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
<oldjbophrase>gerzda</oldjbophrase>, 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
<oldjbophrase>dalmikce</oldjbophrase>, meaning
<quote>veterinarian</quote>: its veljvo is
<oldjbophrase>danlu mikce</oldjbophrase>, or
<quote>animal doctor</quote>. The place structures for those gismu are:</para>
<example xml:id="example-random-id-BqPj">
@@ -659,31 +658,31 @@
<para>
<valsi>mikce</valsi>: m1 is a doctor to patient m2 for ailment m3 using treatment m4</para>
</example>
<para> <indexterm type="general-imported"><primary>ailment</primary></indexterm> and the lujvo place structure is:</para>
<example xml:id="example-random-id-WeBW">
<title>
<anchor xml:id="c12e7d8"/>
+ <indexterm type="example"><primary>veterinarian</primary><secondary>example</secondary></indexterm>
</title>
<para><definition>m1 is a doctor for animal m2=d1 of species d2 for ailment m3 using treatment m4</definition></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="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
<oldjbophrase>bavlamdei</oldjbophrase>,
<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
<oldjbophrase>bavlamdei</oldjbophrase> as having two components:
@@ -707,26 +706,26 @@
<anchor xml:id="c12e8d2"/>
</title>
<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
<oldjbophrase>bavlamdei</oldjbophrase>. 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 xml:id="example-random-id-KEwW">
<title>
<anchor xml:id="c12e8d3"/>
+ <indexterm type="example"><primary>tomorrow</primary><secondary>example</secondary></indexterm>
</title>
<para><definition>d1=b1=l1 is a day following b2=l2, d2 days later (default 1) by standard d3</definition></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:
<oldjbophrase>cladakyxa'i</oldjbophrase>, meaning
<quote>long-sword</quote>, a specific type of medieval weapon. The gismu place structures are:</para>
<example xml:id="example-random-id-XpNf">
<title>
<anchor xml:id="c12e8d4"/>
</title>
@@ -738,20 +737,21 @@
<valsi>xarci</valsi>: xa1 is a weapon for use against xa2 by wielder xa3</para>
</example>
<para> <indexterm type="general-imported"><primary>sword blade</primary></indexterm> Since
<oldjbophrase>cladakyxa'i</oldjbophrase> is a symmetrical lujvo based on
<oldjbophrase>cladakfu xarci</oldjbophrase>, and
<oldjbophrase>cladakfu</oldjbophrase> 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 xml:id="example-random-id-eAbF">
<title>
<anchor xml:id="c12e8d5"/>
+ <indexterm type="example"><primary>long-sword</primary><secondary>example</secondary></indexterm>
</title>
<para><definition>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.</definition></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
<oldjbophrase>cladakyxa'i</oldjbophrase> 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="section-seltau-SE">
<title>Eliding SE rafsi from seltau</title>
@@ -815,31 +815,31 @@
<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,
<oldjbophrase>posydji</oldjbophrase> describes a type of
<valsi>djica</valsi>,
<oldjbophrase>gerzda</oldjbophrase> describes a type of
<valsi>zdani</valsi>, and so on. What is certain is that
<oldjbophrase>gerzda</oldjbophrase> does not describe a
<oldjbophrase>se zdani</oldjbophrase>- 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
<oldjbophrase>blakanla</oldjbophrase> (from
<oldjbophrase>blanu kanla</oldjbophrase>, meaning
<quote>blue eye</quote>). But immediately we are in trouble: we cannot say</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-Kyq2">
<title>
<anchor xml:id="c12e10d1"/>
+ <indexterm type="example"><primary>blue-eyed</primary><secondary>example</secondary></indexterm>
</title>
<interlinear-gloss>
<jbo>la djak. cu blakanla</jbo>
<gloss>Jack is-a-blue-eye</gloss>
</interlinear-gloss>
</example>
<para>because Jack is not an eye,
<valsi>kanla</valsi>, but someone with an eye,
<oldjbophrase>se kanla</oldjbophrase>. At best we can say</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-3IKp">
@@ -871,63 +871,65 @@
</section>
<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
<valsi>ke</valsi> and
<valsi>ke'e</valsi>, the cmavo used to structure and group tanru. We can usually get away with this, because the interpretation of the tertau with
<valsi>ke</valsi> and
<valsi>ke'e</valsi> 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
<oldjbophrase>bakrecpa'o</oldjbophrase>, meaning
<quote>beefsteak</quote>, the veljvo is</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-TgVR">
<title>
<anchor xml:id="c12e11d1"/>
+ <indexterm type="example"><primary>beefsteak</primary><secondary>example</secondary></indexterm>
</title>
<interlinear-gloss>
<jbo>[ke] bakni rectu [ke'e] panlo</jbo>
<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"/>
+ <indexterm type="example"><primary>bovine</primary><secondary>example</secondary></indexterm>
+ <indexterm type="example"><primary>meat slice</primary><secondary>example</secondary></indexterm>
</title>
<interlinear-gloss>
<jbo>bakni ke rectu panlo [ke'e]</jbo>
<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
+
+On the other hand, the lujvo
<oldjbophrase>zernerkla</oldjbophrase>, 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>
<anchor xml:id="c12e11d3"/>
+ <indexterm type="example"><primary>sneak in</primary><secondary>example</secondary></indexterm>
</title>
<interlinear-gloss>
<jbo>zekri ke nenri klama [ke'e]</jbo>
<gloss>crime ( inside go )</gloss>
<natlang>to go within, criminally</natlang>
</interlinear-gloss>
</example>
<para>because the alternative,</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-xAYJ">
<title>
@@ -935,53 +937,46 @@
</title>
<interlinear-gloss>
<jbo>[ke] zekri nenri [ke'e] klama</jbo>
<gloss>(crime inside) go</gloss>
</interlinear-gloss>
</example>
<para>doesn't make much sense. (To go to the inside of a crime? To go into a place where it is criminal to be inside – an interpretation almost identical with
<xref linkend="example-random-id-aXrm"/> anyway?)</para>
<para>
-<indexterm type="example-imported"><primary>shellfish</primary><secondary>example</secondary></indexterm>
<indexterm type="general-imported"><primary>shellfish</primary></indexterm> There are cases, however, where omitting a KE or KEhE rafsi can produce another lujvo, equally useful. For example,
<oldjbophrase>xaskemcakcurnu</oldjbophrase> means
<quote>oceanic shellfish</quote>, and has the veljvo</para>
- <para>
-
-<indexterm type="example-imported"><primary>shell worm</primary><secondary>example</secondary></indexterm>
-
- FIXME: TAG SPOT</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-0W5t">
<title>
<anchor xml:id="c12e11d5"/>
+ <indexterm type="example"><primary>shell worm</primary><secondary>example</secondary></indexterm>
+ <indexterm type="example"><primary>shellfish</primary><secondary>example</secondary></indexterm>
</title>
<interlinear-gloss>
<jbo>xamsi ke calku curnu</jbo>
<gloss>ocean type-of (shell worm)</gloss>
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>invertebrate</primary></indexterm> (
<quote>worm</quote> in Lojban refers to any invertebrate), but
<oldjbophrase>xasycakcurnu</oldjbophrase> has the veljvo</para>
- <para>
-
-<indexterm type="example-imported"><primary>ocean shell</primary><secondary>example</secondary></indexterm>
- FIXME: TAG SPOT</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-HEjn">
<title>
<anchor xml:id="c12e11d6"/>
+ <indexterm type="example"><primary>ocean shell</primary><secondary>example</secondary></indexterm>
</title>
<interlinear-gloss>
<jbo>[ke] xamsi calku [ke'e] curnu</jbo>
<gloss>(ocean shell) type-of worm</gloss>
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>clamshells</primary></indexterm> <indexterm type="general-imported"><primary>parasitic worms</primary><secondary>example</secondary></indexterm> and might refer to the parasitic worms that infest clamshells.</para>
@@ -1553,44 +1548,45 @@
<valsi>citno</valsi>, with place structure</para>
<example xml:id="example-random-id-ciaK">
<title>
<anchor xml:id="c12e15d2"/>
</title>
<para>
<valsi>citno</valsi>: 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
<oldjbophrase>citmau</oldjbophrase> (based on the veljvo
<oldjbophrase>citno zmadu</oldjbophrase>, meaning
<quote>young more-than</quote>).</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-GDt1">
<title>
+ <indexterm type="example"><primary>younger</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c12e15d3"/>
</title>
<interlinear-gloss>
<jbo>mi citmau do lo nanca be li xa</jbo>
<gloss>I am-younger-than you by-years the-number six.</gloss>
<natlang>I am six years younger than you.</natlang>
</interlinear-gloss>
</example>
<para>The place structure for
<oldjbophrase>citmau</oldjbophrase> is</para>
<example xml:id="example-random-id-I3Uh">
<title>
+ <indexterm type="example"><primary>younger</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c12e15d4"/>
</title>
<para><definition>z1=c1 is younger than z2=c1 by amount z4</definition></para>
</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>
@@ -1703,27 +1699,27 @@
<para>Consider the gismu
<valsi>xamgu</valsi>, whose place structure is:</para>
<example xml:id="example-random-id-MWdr">
<title>
<anchor xml:id="c12e15d10"/>
</title>
<para><definition>xa1 is good for xa2 by standard xa3</definition></para>
</example>
<para>
-<indexterm type="example-imported"><primary>better</primary><secondary>example</secondary></indexterm>
The comparative form is
<oldjbophrase>xagmau</oldjbophrase>, corresponding to English
<quote>better</quote>, with a place structure (by the rules given above) of</para>
<example xml:id="example-random-id-pR5R">
<title>
+ <indexterm type="example"><primary>better</primary><secondary>example</secondary></indexterm>
<anchor xml:id="c12e15d11"/>
</title>
<para><definition>z1 is better than z2 for xa2 by standard xa3 in amount z4</definition></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
<oldjbophrase>xagrai</oldjbophrase>, the superlative form, to somehow mirror that, given that comparatives and superlatives are comparable concepts, resulting in:</para>
<example xml:id="example-random-id-Cc6J">
<title>
<anchor xml:id="c12e15d12"/>
--
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.