[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bpfk] dag-cll git updates for Fri Mar 11 19:21:07 EST 2011
commit 9b86c6a4ebd46e9e3c8fd18637bc56cff497308b
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date: Fri Mar 11 15:43:10 2011 -0800
Chapter 18 and 19 tweaks.
diff --git a/todocbook/18.xml b/todocbook/18.xml
index f154ce3..dd7f438 100644
--- a/todocbook/18.xml
+++ b/todocbook/18.xml
@@ -95,21 +95,21 @@
</cmavo-entry>
</cmavo-list>
<para> <indexterm type="lojban-word-imported"><primary>PA selma'o</primary></indexterm> <indexterm type="general-imported"><primary>hundred</primary><secondary>expressing as number</secondary></indexterm> <indexterm type="general-imported"><primary>ten</primary><secondary>expressing as number</secondary></indexterm> <indexterm type="general-imported"><primary>numbers</primary><secondary>as compound cmavo</secondary></indexterm> <indexterm type="general-imported"><primary>digits</primary><secondary>cmavo for</secondary></indexterm> <indexterm type="general-imported"><primary>numbers</primary><secondary>expressing simple</secondary></indexterm> The simplest kind of mekso are numbers, which are cmavo or compound cmavo. There are cmavo for each of the 10 decimal digits, and numbers greater than 9 are made by stringing together the cmavo. Some examples:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-LmPr">
<title>
<anchor xml:id="c18e2d1"/>
</title>
<interlinear-gloss>
<jbo>pa re ci</jbo>
<gloss>one two three</gloss>
- <math>123 ignore</math> <!-- ok -->
+ <math>123</math>
<en>one hundred and twenty three</en>
</interlinear-gloss>
</example>
<example role="interlinear-gloss-example" xml:id="example-random-id-TNjj">
<title>
<anchor xml:id="c18e2d2"/>
</title>
<interlinear-gloss>
<jbo>pa no</jbo>
@@ -2227,70 +2227,68 @@
<valsi>va'a</valsi> in infix form. We would use:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-8Uh9">
<title>
<anchor xml:id="c18e14d1"/>
</title>
<interlinear-gloss>
<jbo>li tu'o va'a ny. du li no vu'u ny.</jbo>
-
-
<gloss>The-number (null) additive-inverse n equals the-number zero minus n.</gloss>
<math>-n = 0 - n</math>
</interlinear-gloss>
</example>
<para> <indexterm type="general-imported"><primary>operands</primary><secondary>too few for infix operation</secondary></indexterm> <indexterm type="general-imported"><primary>null operand</primary><secondary>for infix operations with too few operands</secondary></indexterm> <indexterm type="general-imported"><primary>tu'o</primary><secondary>for infix operations with too few operands</secondary></indexterm> The
<valsi>tu'o</valsi> fulfills the grammatical requirement for a left operand for the infix use of
<valsi>va'a</valsi>, even though semantically none is needed or wanted.</para>
<para> <indexterm type="lojban-word-imported"><primary>gei</primary></indexterm> <indexterm type="general-imported"><primary>exponential notation</primary><secondary>with gei</secondary></indexterm> <indexterm type="general-imported"><primary>scientific notation</primary><secondary>with gei</secondary></indexterm> <indexterm type="general-imported"><primary>gei</primary><secondary>as a binary operator</secondary></indexterm> Finding a suitable example of
<valsi>ge'a</valsi> requires exhibiting a ternary operator, and ternary operators are not common. The operator
<valsi>gei</valsi>, however, has both a binary and a ternary use. As a binary operator, it provides a terse representation of scientific (also called
<quote>exponential</quote>) notation. The first operand of
<valsi>gei</valsi> is the exponent, and the second operand is the mantissa or fraction:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-VjtV">
<title>
<anchor xml:id="c18e14d2"/>
</title>
<interlinear-gloss>
<jbo>li cinonoki'oki'o du li bi gei ci</jbo>
<gloss>The-number three-zero-zero-comma-comma equals the-number eight scientific three.</gloss>
- <math>300,000,000 = 3 × 10</math>
+ <math>300,000,000 = 3 × 10<superscript>8</superscript></math>
</interlinear-gloss>
</example>
<para> <indexterm type="example-imported"><primary>3 ( 10^8</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>gei</primary><secondary>rationale for order of places</secondary></indexterm> <indexterm type="general-imported"><primary>scientific notation</primary><secondary>rationale for order of places</secondary></indexterm> Why are the arguments to
<valsi>gei</valsi> in reverse order from the conventional symbolic notation? So that
<valsi>gei</valsi> can be used in forethought to allow easy specification of a large (or small) imprecise number:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-zmqy">
<title>
<anchor xml:id="c18e14d3"/>
</title>
<interlinear-gloss>
<jbo>gei reno</jbo>
<gloss>(scientific) two-zero</gloss>
- <math>10</math>
+ <math>10 <superscript>20</superscript></math>
</interlinear-gloss>
</example>
<para> <indexterm type="example-imported"><primary>10^20</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>floating point numbers</primary><secondary>expressing</secondary></indexterm> <indexterm type="general-imported"><primary>exponential notation</primary><secondary>with base other than 10</secondary></indexterm> <indexterm type="general-imported"><primary>gei</primary><secondary>as a ternary operator</secondary></indexterm> <indexterm type="general-imported"><primary>operands</primary><secondary>too many for infix operation</secondary></indexterm> <indexterm type="general-imported"><primary>null operator</primary><secondary>for infix operations with too many operands</secondary></indexterm> <indexterm type="general-imported"><primary>ge'a</primary><secondary>for infix operations with too many operands</secondary></indexterm> Note, however, that although 10 is far and away the most common exponent base, it is not the only possible one. The third operand of
<valsi>gei</valsi>, therefore, is the base, with 10 as the default value. Most computers internally store so-called
<quote>floating-point</quote> numbers using 2 as the exponent base. (This has nothing to do with the fact that computers also represent all integers in base 2; the IBM 360 series used an exponent base of 16 for floating point, although each component of the number was expressed in base 2.) Here is a computer floating-point number with a value of 40:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-7nMz">
<title>
<anchor xml:id="c18e14d4"/>
</title>
<interlinear-gloss>
<jbo>papano bi'eju'u re gei pipanopano bi'eju'u re ge'a re</jbo>
<gloss>(one-one-zero base 2) scientific (point-one-zero-one-zero base 2) with-base 2</gloss>
- <math>.1010</math>
+ <math>.1010<subscript>2</subscript> x 2<superscript>110<subscript>2</subscript></superscript></math>
</interlinear-gloss>
</example>
</section>
<section xml:id="section-vectors-matrices">
<title>Vectors and matrices</title>
<para>The following cmavo are discussed in this section:</para>
<cmavo-list>
<cmavo-entry>
<cmavo>jo'i</cmavo>
<selmaho>JOhI</selmaho>
@@ -3124,21 +3122,21 @@
<oldjbophrase>ni'enu'a</oldjbophrase>, which transforms the operator into a matching selbri and then the selbri into an operand.</para>
<para> <indexterm type="lojban-word-imported"><primary>te'u</primary></indexterm> <indexterm type="lojban-word-imported"><primary>ma'o</primary></indexterm> <indexterm type="general-imported"><primary>operator</primary><secondary>converting from operand</secondary></indexterm> <indexterm type="general-imported"><primary>operand</primary><secondary>converting into operator</secondary></indexterm> <indexterm type="general-imported"><primary>conversion of operand into operator</primary></indexterm> To change an operand into an operator, we use the cmavo
<valsi>ma'o</valsi>, already introduced as a means of changing a lerfu string such as
<oldjbophrase>fy.</oldjbophrase> into an operator. In fact,
<valsi>ma'o</valsi> can be followed by any mekso operand, using the elidable terminator
<valsi>te'u</valsi> if necessary.</para>
<para> <indexterm type="general-imported"><primary>ma'o</primary><secondary>potential ambiguity caveat</secondary></indexterm> There is a potential semantic ambiguity in
<oldjbophrase>ma'o fy. [te'u]</oldjbophrase> if
<oldjbophrase>fy.</oldjbophrase> is already in use as a variable: it comes to mean
- <quote>the function whose value is always <quote>f</quote></quote>. However, mathematicians do not normally use the same lerfu words or strings as both functions and variables, so this case should not arise in practice.</para>
+ <quote>the function whose value is always <varname>f</varname></quote>. However, mathematicians do not normally use the same lerfu words or strings as both functions and variables, so this case should not arise in practice.</para>
</section>
<section xml:id="section-four-score-and-seven">
<title>Four score and seven: a mekso problem</title>
<para> <indexterm type="example-imported"><primary>Four score and seven</primary><secondary>example</secondary></indexterm> <indexterm type="example-imported"><primary>Gettysburg Address</primary><secondary>example</secondary></indexterm> <indexterm type="general-imported"><primary>mekso</primary><secondary>and literary translation</secondary></indexterm> Abraham Lincoln's Gettysburg Address begins with the words
<quote>Four score and seven years ago</quote>. This section exhibits several different ways of saying the number
<quote>four score and seven</quote>. (A
diff --git a/todocbook/19.xml b/todocbook/19.xml
index 7cfa2c6..c8316f7 100644
--- a/todocbook/19.xml
+++ b/todocbook/19.xml
@@ -160,21 +160,21 @@
<para> <indexterm type="general-imported"><primary>topic-comment</primary><secondary>description</secondary></indexterm> In Chinese, the normal sentence form is different: a topic is stated, and a comment about it is made. (Japanese also has the concept of a topic, but indicates it by attaching a suffix; other languages also distinguish topics in various ways.) The topic says what the sentence is about:</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-ovFJ">
<title>
<anchor xml:id="c19e4d2"/>
</title>
<interlinear-gloss>
<foreign xml:lang="zh">
zhe<superscript>4</superscript> xiao<superscript>1</superscript>xi<superscript>2</superscript> wo<superscript>3</superscript> zhi<superscript>1</superscript>dao le
</foreign> <!-- FIXME: instead of three spaces, why not a colon? -->
<gloss>this news I know [perfective]</gloss>
- <gloss>As for this news, I knew it.</gloss>
+ <en>As for this news, I knew it.</en>
<en>I've heard this news already.</en>
</interlinear-gloss>
</example>
<para> <indexterm type="lojban-word-imported"><primary>ZOhU selma'o</primary></indexterm> <indexterm type="lojban-word-imported"><primary>zo'u</primary></indexterm> <indexterm type="example-imported"><primary>news</primary><secondary>example</secondary></indexterm> The wide space in the first two versions of
<xref linkend="example-random-id-ovFJ"/> separate the topic (
<quote>this news</quote>) from the comment (
<quote>I know already</quote>).</para>
<para>Lojban uses the cmavo
<valsi>zo'u</valsi> (of selma'o ZOhU) to separate topic (a sumti) from comment (a bridi):</para>
diff --git a/todocbook/TODO b/todocbook/TODO
index d6873d1..e82a9a5 100644
--- a/todocbook/TODO
+++ b/todocbook/TODO
@@ -19,36 +19,20 @@ From IRC:
< vensa> rlpowell: are you aware of the TYPO at the bottm of this CLL page? http://dag.github.com/cll/10/16/
< rlpowell> Heh. I get an internal server error. :)
< rlpowell> Can you paste?
< vensa> subordinate: X TENSE le nu Y -- that's the proper part
< vensa> forethought coordinate: TENSE+gi X gi Y -- thats the bad part pe'i
< rlpowell> What do you think the problem is?
< kebukebu> (They are said to be equivalent)
< vensa> (should be TENSE+gi *Y* gi *X*)
-18.xml:
-
- <math>123 ignore</math> <!-- okely dokely --> -- heh
-
- <math>300,000,000 = 3 × 10</math>
- <math>10</math>
- <math>.1010</math>
- <math>30,000,000 = 3 × 10</math>
- <math>(n + 1)(n + 1) = n</math> -- misisng bits
-
- <quote>the function whose value is always <quote>f</quote> -- needs varname
-
-19.xml:
-
- <gloss>As for this news, I knew it.</gloss> -- en
-
20.xml:
<xref linkend="chapter-attitudinals-section-intensity-scale -- and friends do not agree with the chapter
<xref linkend="chapter-vuho"/> -- should be chapter-relative-clauses-section-vuho
21.xml:
<jbophrase role="letteral">.</jbophrase> -- should be <quote>
commit cf3a778b11c40fbade666f02cb31e85cd96d7d4e
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date: Fri Mar 11 15:21:19 2011 -0800
Chapter 17 tweaks.
diff --git a/todocbook/17.xml b/todocbook/17.xml
index 39f2327..7404945 100644
--- a/todocbook/17.xml
+++ b/todocbook/17.xml
@@ -696,24 +696,24 @@ ty. .ubu vy. xy. .ybu zy.
<example role="interlinear-gloss-example" xml:id="example-random-id-fBfe">
<title>
<anchor xml:id="c17e8d1"/>
</title>
<interlinear-gloss>
<jbo>.y'y.bu .abu ny. vo zy. .ibu vo</jbo>
<en>
<quote>h</quote>
<quote>a</quote>
<quote>n</quote>
- <superscript>4</superscript>
+ 4
<quote>z</quote>
<quote>i</quote>
- <superscript>4</superscript>
+ 4
</en>
</interlinear-gloss>
</example>
<para> <indexterm type="example-imported"><primary>han^{4}zi^{4}</primary></indexterm> <indexterm type="general-imported"><primary>lerfu words with numeric digits</primary><secondary>grammar considerations</secondary></indexterm> <indexterm type="general-imported"><primary>numeric digits in lerfu words</primary><secondary>grammar considerations</secondary></indexterm> The cmavo
<valsi>vo</valsi> is the Lojban digit
<quote>4</quote>. It is grammatical to intersperse digits (of selma'o PA) into a string of lerfu words; as long as the first cmavo is a lerfu word, the whole will be interpreted as a string of lerfu words. In Chinese, the digits can be used to represent tones. Pinyin is more usually written using accent marks, the mechanism for which was explained in
<xref linkend="section-accents"/>.</para>
<para>The Japanese company named
<quote>Mitsubishi</quote> in English is spelled the same way in romaji, and could be spelled out in Lojban thus:</para>
@@ -1894,35 +1894,35 @@ ty. .ubu vy. xy. .ybu zy.
</row>
<row>
<entry>ogonek</entry>
<entry><oldjbophrase>.ogoniek. bu</oldjbophrase></entry>
</row>
<row>
<entry>hacek</entry>
<entry><oldjbophrase>.xatcek. bu</oldjbophrase></entry>
</row>
<row>
- <entry>ligatured fi fi</entry>
+ <entry>ligatured fi</entry>
<entry><oldjbophrase>tei fy. ibu foi</oldjbophrase></entry>
</row>
<row>
<entry>Danish/Latin ae ae</entry>
<entry><oldjbophrase>tei .abu .ebu foi</oldjbophrase></entry>
</row>
<row>
- <entry>Dutch ij ij</entry>
+ <entry>Dutch ij</entry>
<entry><oldjbophrase>tei .ibu jy. foi</oldjbophrase></entry>
</row>
<row>
- <entry>German es-zed es-zed</entry>
+ <entry>German es-zed</entry>
<entry><oldjbophrase>tei sy. zy. foi</oldjbophrase></entry>
</row>
</tbody>
</tgroup>
</informaltable>
</section>
<section xml:id="section-ICAO-alphabet">
<title>Proposed lerfu words for radio communication</title>
<para> <indexterm type="general-imported"><primary>Phonetic Alphabet</primary><secondary>proposed lerfu words for</secondary></indexterm> <indexterm type="general-imported"><primary>ICAO Phonetic Alphabet</primary><secondary>proposed lerfu words for</secondary></indexterm> <indexterm type="general-imported"><primary>noisy environments</primary><secondary>proposed lerfu words for</secondary></indexterm> <indexterm type="general-imported"><primary>radio communication</primary><secondary>proposed lerfu words for</secondary></indexterm> <indexterm type="general-imported"><primary>lerfu words</primary><secondary>proposed for radio communication</secondary></indexterm> <indexterm type="general-imported"><primary>lerfu words</primary><secondary>proposed for noisy environments</secondary></indexterm> There is a set of English words which are used, by international agreement, as lerfu words (for the English alphabet) over the radio, or in noisy situations where the utmost clarity is required. Formally they are known as the
diff --git a/todocbook/TODO b/todocbook/TODO
index af2310f..d6873d1 100644
--- a/todocbook/TODO
+++ b/todocbook/TODO
@@ -19,30 +19,20 @@ From IRC:
< vensa> rlpowell: are you aware of the TYPO at the bottm of this CLL page? http://dag.github.com/cll/10/16/
< rlpowell> Heh. I get an internal server error. :)
< rlpowell> Can you paste?
< vensa> subordinate: X TENSE le nu Y -- that's the proper part
< vensa> forethought coordinate: TENSE+gi X gi Y -- thats the bad part pe'i
< rlpowell> What do you think the problem is?
< kebukebu> (They are said to be equivalent)
< vensa> (should be TENSE+gi *Y* gi *X*)
-17.xml:
-
- <entry>ligatured fi fi</entry> -- and several followig -- doubled
-
- <quote>h</quote>
- <quote>a</quote>
- <quote>n</quote>
- <superscript>4</superscript>
- -- should not be superscript
-
18.xml:
<math>123 ignore</math> <!-- okely dokely --> -- heh
<math>300,000,000 = 3 × 10</math>
<math>10</math>
<math>.1010</math>
<math>30,000,000 = 3 × 10</math>
<math>(n + 1)(n + 1) = n</math> -- misisng bits
--
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.