[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bpfk] dag-cll git updates for Tue Nov 2 22:21:01 EDT 2010
commit 0ed1c92bca6a14be67cf67eaf21310727731d78d
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date: Tue Nov 2 18:59:58 2010 -0700
Chapter 17 updates to align with the book. Note that section 20 was
significantly rearranged, but not in this diff.
diff --git a/17/11/index.html b/17/11/index.html
index c3df4fc..36244d8 100644
--- a/17/11/index.html
+++ b/17/11/index.html
@@ -66,21 +66,21 @@ Note the “boi” here to separate the lerfu strings “fy” and “xy”.
x sub k
</pre>
<ul>
<li>A lerfu string as quantifier (enclosed in “vei ... ve'o” parentheses):</li>
</ul>
<pre>
<a id="e6" name="e6">11.6)</a> vei ny. [ve'o] lo prenu
(“n”) persons
</pre>
<p>The parentheses are required because “ny. lo prenu” would be two separate sumti, “ny.” and “lo prenu”. In general, any mathematical expression other than a simple number must be in parentheses when used as a quantifier; the right parenthesis mark, the cmavo “ve'o”, can usually be elided.</p>
-<p>All the examples above have exhibited single lerfu words rather than lerfu strings, in accordance with the conventions of ordinary mathematics. A longer lerfu string would still be treated as a single variable or function name: in Lojban, “.abu by. cy.” is not the multiplication “a × b × c” but is the variable “abc”. (Of course, a local convention could exist that made the value of a variable like “abc”, with a multi-lerfu-word name, equal to the values of the variables “a”, “b”, and “c” multiplied together.)</p>
+<p>All the examples above have exhibited single lerfu words rather than lerfu strings, in accordance with the conventions of ordinary mathematics. A longer lerfu string would still be treated as a single variable or function name: in Lojban, “.abu by. cy.” is not the multiplication “a × b × c” but is the variable “abc”. (Of course, a local convention could be employed that made the value of a variable like “abc”, with a multi-lerfu-word name, equal to the values of the variables “a”, “b”, and “c” multiplied together.)</p>
<p>There is a special rule about shift words in mathematical text: shifts within mathematical expressions do not affect lerfu words appearing outside mathematical expressions, and vice versa.</p>
<hr />
<div class="nav">
<div class="nav-prev">
<div class="nav-section-link-prev"><a href="../../17/10/">Previous</a></div>
<div class="nav-section-name">References to lerfu</div>
</div>
<div class="nav-next">
<div class="nav-section-link-next"><a href="../../17/12/">Next</a></div>
<div class="nav-section-name">Acronyms</div>
diff --git a/17/13/index.html b/17/13/index.html
index 2c7eaa6..56be8f7 100644
--- a/17/13/index.html
+++ b/17/13/index.html
@@ -18,36 +18,36 @@
<div class="nav-section-link-next"><a href="../../17/14/">Next</a></div>
<div class="nav-section-name">List of all auxiliary lerfu-word cmavo</div>
</div>
<div class="nav-title">
<div class="nav-title-title">As Easy As A-B-C? The Lojban Letteral System And Its Uses</div>
<div class="nav-title-link"><a href="../../">The Lojban Reference Grammar</a></div>
</div>
</div>
<hr />
<h3>13. Computerized character codes</h3>
-<p>Since the first application of computers to non-numerical information, character sets have existed, mapping numbers (called “character codes”) into selected lerfu, digits, and punctuation marks (collectively called “characters”). Historically, these character sets have only covered the English alphabet and a few selected punctuation marks. International efforts are now underway to create a unified character set that can represent essentially all the characters in essentially all the world’s writing systems. Lojban can take advantage of these encoding schemes by using the cmavo “se'e” (of selma'o BY). This cmavo is conventionally followed by digit cmavo of selma'o PA representing the character code, and the whole string indicates a single character in some computerized character set:</p>
+<p>Since the first application of computers to non-numerical information, character sets have existed, mapping numbers (called “character codes”) into selected lerfu, digits, and punctuation marks (collectively called “characters”). Historically, these character sets have only covered the English alphabet and a few selected punctuation marks. International efforts have now created Unicode, a unified character set that can represent essentially all the characters in essentially all the world’s writing systems. Lojban can take advantage of these encoding schemes by using the cmavo “se'e” (of selma'o BY). This cmavo is conventionally followed by digit cmavo of selma'o PA representing the character code, and the whole string indicates a single character in some computerized character set:</p>
<pre>
<a id="e1" name="e1">13.1)</a> me'o se'ecixa cu lerfu la .asycy'i'is.
loi merko rupnu
The-expression [code] 36 is-a-letteral in-set ASCII
for-the-mass-of American currency-units.
The character code 36 in ASCII represents American dollars.
“$” represents American dollars.
</pre>
Understanding <a href="../13/#e1">Example 13.1</a> depends on knowing the value in the ASCII character set (one of the simplest and oldest) of the “$” character. Therefore, the “se'e” convention is only intelligible to those who know the underlying character set. For precisely specifying a particular character, however, it has the advantages of unambiguity and (relative) cultural neutrality, and therefore Lojban provides a means for those with access to descriptions of such character sets to take advantage of them.
<p>As another example, the Unicode character set (also known as ISO 10646) represents the international symbol of peace, an inverted trident in a circle, using the base-16 value 262E. In a suitable context, a Lojbanist may say:</p>
<pre>
<a id="e2" name="e2">13.2)</a> me'o se'erexarerei sinxa le ka panpi
the-expression [code] 262E is-a-sign-of the quality-of being-at-peace
</pre>
-When a “se'e” string appears in running discourse, some metalinguistic convention must specify whether the number is base 10 (as above) or some other base, and which character set is in use.
+When a “se'e” string appears in running discourse, some metalinguistic convention must specify whether the number is base 10 or some other base, and which character set is in use.
<hr />
<div class="nav">
<div class="nav-prev">
<div class="nav-section-link-prev"><a href="../../17/12/">Previous</a></div>
<div class="nav-section-name">Acronyms</div>
</div>
<div class="nav-next">
<div class="nav-section-link-next"><a href="../../17/14/">Next</a></div>
<div class="nav-section-name">List of all auxiliary lerfu-word cmavo</div>
</div>
commit 433c665fe0ecb06ae0f3dfd3bf37a2dfa44a6ebf
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date: Tue Nov 2 18:29:29 2010 -0700
Updating chapter 16 to the red book; also one minor clarifying
insertion.
diff --git a/16/11/index.html b/16/11/index.html
index ce8dab2..72c0d7e 100644
--- a/16/11/index.html
+++ b/16/11/index.html
@@ -59,21 +59,21 @@ when converted to the external negation form produces:
<a id="e7" name="e7">11.7)</a> naku roda poi verba cu klama su'ode poi ckule
It is false that all children go to some school(s).
</pre>
In <a href="../11/#e5">Example 11.5</a>, we moved the negation boundary rightward across the quantifier of “de”, forcing us to invert it. In <a href="../11/#e7">Example 11.7</a> we moved the negation boundary across the quantifier of “da”, forcing us to invert it instead. <a href="../11/#e6">Example 11.6</a> merely switched the selbri and the negation boundary, with no effect on the quantifiers.
<p>The same rules apply if you rearrange the sentence so that the quantifier crosses an otherwise fixed negation. You can’t just convert the selbri of <a href="../11/#e4">Example 11.4</a> and rearrange the sumti to produce</p>
<pre>
<a id="e8" name="e8">11.8)</a> su'ode poi ckule ku'o naku se klama roda poi verba
Some schools aren’t gone-to-by every child.
</pre>
-or rather, <a href="../11/#e8">Example 11.8</a> means something completely different from <a href="../11/#e4">Example 11.4</a>. Conversion with “se” under “naku” negation is not symmetric; not all sumti are treated identically, and some sumti are not invariant under conversion. These complications would make Lojban much harder to learn (just as their corresponding natural language constructs are difficult to learn). Thus, internal negation with “naku” is considered an advanced technique, used to achieve stylistic compatibility with natural languages.
+or rather, <a href="../11/#e8">Example 11.8</a> means something completely different from <a href="../11/#e4">Example 11.4</a>. Conversion with “se” under “naku” negation is not symmetric; not all sumti are treated identically, and some sumti are not invariant under conversion. Thus, internal negation with “naku” is considered an advanced technique, used to achieve stylistic compatibility with natural languages.
<p>It isn’t always easy to see which quantifiers have to be inverted in a sentence. <a href="../11/#e4">Example 11.4</a> is identical in meaning to:</p>
<pre>
<a id="e9" name="e9">11.9)</a> su'o verba naku klama su'o ckule
Some children don’t go-to some school.
</pre>
but in <a href="../11/#e9">Example 11.9</a>, the bound variables “da” and “de” have been hidden.
<p>It is trivial to export an internal bridi negation expressed with “na” to the prenex, as we saw in <a href="../9/">Section 9</a>; you just move it to the left end of the prenex. In comparison, it is non-trivial to export a “naku” to the prenex because of the quantifiers. The rules for exporting “naku” require that you export all of the quantified variables (implicit or explicit) along with “naku”, and you must export them from left to right, in the same order that they appear in the sentence. Thus <a href="../11/#e4">Example 11.4</a> goes into prenex form as:</p>
<pre>
<a id="e10" name="e10">11.10)</a> su'oda poi verba ku'o naku
su'ode poi ckule zo'u da klama de
diff --git a/16/12/index.html b/16/12/index.html
index d8e8fe5..e1bcbe8 100644
--- a/16/12/index.html
+++ b/16/12/index.html
@@ -63,22 +63,22 @@ The “ga” and “gi”, meaning “either-or”, have become “ge” and “
And by dividing the bridi with logically connected selbri into two bridi,
<pre>
<a id="e7" name="e7">12.7)</a> naku zo'u ge la djein. le zarci cu dzukla
gi la djein. le zarci cu bajrykla
It-is-false-that: both (Jane to-the market walks)
and (Jane to-the market runs).
</pre>
is the result.
<p>At this expanded level, we apply DeMorgan’s Law to distribute the negation in the prenex across both sentences, to get</p>
<pre>
-<a id="e8" name="e8">12.8)</a> ga la djein. le zarci cu na dzukla
- gi la djein. le zarci cu na bajrykla
+<a id="e8" name="e8">12.8)</a> ga la djein. le zarci na dzukla
+ gi la djein. le zarci na bajrykla
Either Jane to-the market [false] walks,
or Jane to-the market [false] runs.
</pre>
which is the same as
<pre>
<a id="e9" name="e9">12.9)</a> ganai la djein. le zarci cu dzukla
ginai la djein. le zarci cu bajrykla
If Jane to-the market walks,
then Jane to-the market [false] runs.
If Jane walks to the market, then she doesn’t run.
diff --git a/16/13/index.html b/16/13/index.html
index 7ab5ac5..de59827 100644
--- a/16/13/index.html
+++ b/16/13/index.html
@@ -24,21 +24,21 @@
</div>
</div>
<hr />
<h3>13. selbri variables</h3>
<p>In addition to the variables “da”, “de”, and “di” that we have seen so far, which function as sumti and belong to selma'o KOhA, there are three corresponding variables “bu'a”, “bu'e”, and “bu'i” which function as selbri and belong to selma'o GOhA. These new variables allow existential or universal claims which are about the relationships between objects rather than the objects themselves. We will start with the usual silly examples; the literal translation will represent “bu'a”, “bu'e” and “bu'i” with F, G, and H respectively.</p>
<pre>
<a id="e1" name="e1">13.1)</a> su'o bu'a zo'u la djim. bu'a la djan.
For-at-least-one relationship-F : Jim stands-in-relationship-F to-John.
There’s some relationship between Jim and John.
</pre>
-<p>The translations of <a href="../13/#e1">Example 13.1</a> show how unidiomatic selbri variables are in English; Lojban sentences like <a href="../13/#e1">Example 13.1</a> need to be totally reworded in English. Furthermore, when a selbri variable appears in the prenex, it is necessary to precede it with a quantifier such as “su'o”; it is ungrammatical to just say “bu'a zo'u”. This rule is necessary because only sumti can appear in the prenex, and “su'o bu'a” is technically a sumti — in fact, an indefinite description like “re nanmu”, since “bu'a” is grammatically equivalent to a brivla like “nanmu”. However, indefinite descriptions involving the bu'a-series cannot be imported from the prenex.</p>
+<p>The translations of <a href="../13/#e1">Example 13.1</a> show how unidiomatic selbri variables are in English; Lojban sentences like <a href="../13/#e1">Example 13.1</a> need to be totally reworded in English. Furthermore, when a selbri variable appears in the prenex, it is necessary to precede it with a quantifier such as “su'o”; it is ungrammatical to just say “bu'a zo'u”. This rule is necessary because only sumti can appear in the prenex, and “su'o bu'a” is technically a sumti — in fact, it is an indefinite description like “re nanmu”, since “bu'a” is grammatically equivalent to a brivla like “nanmu”. However, indefinite descriptions involving the bu'a-series cannot be imported from the prenex.</p>
<p>When the prenex is omitted, the preceding number has to be omitted too:</p>
<pre>
<a id="e2" name="e2">13.2)</a> la djim. bu'a la djan.
Jim stands-in-at-least-one-relationship to-John.
</pre>
As a result, if the number before the variable is anything but “su'o”, the prenex is required:
<pre>
<a id="e3" name="e3">13.3)</a> ro bu'a zo'u la djim. bu'a la djan.
For-every relationship-F : Jim stands-in-relationship-F to-John.
Every relationship exists between Jim and John.
diff --git a/16/9/index.html b/16/9/index.html
index 6059098..212d9ff 100644
--- a/16/9/index.html
+++ b/16/9/index.html
@@ -116,21 +116,21 @@ which is negated by:
<pre>
<a id="e14" name="e14">9.14)</a> naku noda rode zo'u da prami de
It is false that: there is no X that, for every Y, X loves Y.
It is false that there is nobody who loves everything.
</pre>
<p>We can simplify <a href="../9/#e14">Example 9.14</a> by transforming the prenex. To move the negation phrase within the prenex, we must first expand the “no” quantifier. Thus “for no x” means the same thing as “it is false for some x”, and the corresponding Lojban “noda” can be replaced by “naku su'oda”. Making this substitution, we get:</p>
<pre>
<a id="e15" name="e15">9.15)</a> naku naku su'oda rode zo'u da prami de
It is false that it is false that: for an X, for every Y: X loves Y.
</pre>
-Adjacent double negation boundaries in the prenex can be dropped, so this means the same as:
+Adjacent pairs of negation boundaries in the prenex can be dropped, so this means the same as:
<pre>
<a id="e16" name="e16">9.16)</a> su'oda rode zo'u da prami de
There is an X such that, for every Y, X loves Y.
At least one person loves everything.
</pre>
which is clearly the desired contradiction of <a href="../9/#e13">Example 9.13</a>.
<p>The interactions between quantifiers and negation mean that you cannot eliminate double negatives that are not adjacent. You must first move the negation phrases so that they are adjacent, inverting any quantifiers they cross, and then the double negative can be eliminated.</p>
<hr />
<div class="nav">
<div class="nav-prev">
--
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.