[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bpfk] dag-cll git updates for Fri Feb 18 14:21:07 EST 2011



commit 27816455e35a74d1cbb26b1593b1797b5c7ef4ba
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date:   Fri Feb 18 10:41:51 2011 -0800

    Chapter 9 tweaks.

diff --git a/todocbook/9.xml b/todocbook/9.xml
index 7e3ba36..5918d7a 100644
--- a/todocbook/9.xml
+++ b/todocbook/9.xml
@@ -1262,30 +1262,32 @@
     <para>which doesn't require the extra 
     <valsi>vau</valsi>; all sumti before a conjunction of bridi-tails are shared.</para>
     <para> <indexterm type="general-imported"><primary>operand modal connection</primary></indexterm>  <indexterm type="general-imported"><primary>modal operand connection</primary></indexterm> Finally, mathematical operands can be modally connected.</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-J2T5">
       <title>
         <anchor xml:id="c9e8d10"/>
       </title>
       <interlinear-gloss>
         <jbo>li ny. du li vo .ini'ibo li ny. du li re su'i re</jbo>
         <gloss>the number n = the-number 4. Entailed-by the-number n = the-number 2 + 2.</gloss>
+        <en>n = 4 because n = 2 + 2.</en>
       </interlinear-gloss>
     </example>
     <para>can be reduced to:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-Mfe4">
       <title>
         <anchor xml:id="c9e8d11"/>
       </title>
       <interlinear-gloss>
         <jbo>li ny. du li ni'igi vei re su'i re [ve'o] gi vo</jbo>
-        <gloss>the-number = the-number because ( 2 + 2 ) therefore 4.</gloss>
+        <gloss>the-number n = the-number because ( 2 + 2 ) therefore 4.</gloss>
+        <en>n is 2 + 2, and is thus 4.</en>
       </interlinear-gloss>
     </example>
     <para>The cmavo 
     <valsi>vei</valsi> and 
     <valsi>ve'o</valsi> represent mathematical parentheses, and are required so that 
     <oldjbophrase>ni'igi</oldjbophrase> affects more than just the immediately following operand, namely the first 
     <valsi>re</valsi>. (The right parenthesis, 
     <valsi>ve'o</valsi>, is an elidable terminator.) As usual, no English translation does 
     <xref linkend="example-random-id-Mfe4"/> justice.</para>
     <para> <indexterm type="general-imported"><primary>modal connectives</primary><secondary>fi'o prohibited in</secondary></indexterm>  <indexterm type="general-imported"><primary>fi'o</primary><secondary>restriction on use</secondary></indexterm> Note: Due to restrictions on the Lojban parsing algorithm, it is not possible to form modal connectives using the 
diff --git a/todocbook/TODO b/todocbook/TODO
index 6b6d9d9..d24873c 100644
--- a/todocbook/TODO
+++ b/todocbook/TODO
@@ -8,90 +8,20 @@ WRT rafsi:  <rafsi type="prefix">man</rafsi> seems best
   Will that suck for <member><jbophrase role="rafsi">ger</jbophrase><jbophrase role="rafsi">-zda</jbophrase></member> ?
 
   Let alone       <member><jbophrase
   role="rafsi">logj</jbophrase><jbophrase
   role="rafsi">-bang</jbophrase><jbophrase
   role="rafsi">-girz</jbophrase></member>
 
 Handling chapter 2: why don't we just require that the number of sub-entries matches?
   Also: maybe rename jbo/gloss for this purpose, or introduce roles.
 
-9.xml
-
-  <gloss>the-number = the-number because ( 2 + 2 ) theref ore 4.</gloss> -- needs an "n" before the =
-
-  Do we want to auto-generate the BAI list at the end of Chapter 9
-  from jbovlaste?  Probably not for v1.1; for v2 maybe just say
-  "read the dict"?
-
-  <entry>with</entry>
-  <entry>property</entry>
-
-  <entry>as a</entry>
-  <entry>standard for</entry>
-
-  <entry>as a</entry>
-  <entry>part of</entry>
-
-  <entry>as a</entry>
-  <entry>limit of</entry>
-
-  <entry>as a</entry>
-  <entry>method for</entry>
-
-  <entry>on the same date</entry>
-  <entry>as</entry> -- one entry
-
-  <entry>from source as an origin of</entry>
-  <entry>pertained to by concerning</entry> -- should almost
-  certainly be two entries; check and add to errata
-
-  <gloss>For-every X: X is-a-goer-to the store if-and-onl y-if is-a-walker-on the field.</gloss>
-  -- should be: "For-every X: X is-a-goer-to the store if-and-only-if it is-a-walker-on the field." (but check errata page)
-
-@@ -1463,7 +1463,7 @@
-         <anchor xml:id="c9e10d1"/>
-       </title>
-       <interlinear-gloss>
--        <jbo>la .apasionatas. poi se cusku la .artr. rubnstain. cu se nelci mi</jbo>
-+        <jbo>la .apasionatas. ku poi se cusku la .artr. rubnstain. cu se nelci mi</jbo>
-         <gloss>The Appassionata which is-expressed-by Arthur Rubinstein is-liked-by me.</gloss>
-
-       </interlinear-gloss>
-@@ -1473,7 +1473,7 @@
-         <anchor xml:id="c9e10d2"/>
-       </title>
-       <interlinear-gloss>
--        <jbo>la .apasionatas. noi se finti la betovn. cu se nelci mi</jbo>
-+        <jbo>la .apasionatas. ku noi se finti la betovn. cu se nelci mi</jbo>
-         <gloss>The Appassionata, which is-created-by Beethoven, is-liked-by me.</gloss>
-
-
-@@ -1502,7 +1502,7 @@
-         <anchor xml:id="c9e10d3"/>
-       </title>
-       <interlinear-gloss>
--        <jbo>la .apasionatas pe la .artr. rubnstain. se nelci mi</jbo>
-+        <jbo>la .apasionatas. ku pe la .artr. rubnstain. se nelci mi</jbo>
-         <gloss>The Appassionata of Arthur Rubinstein is-liked-by me.</gloss>
-
-       </interlinear-gloss>
-@@ -1512,7 +1512,7 @@
-         <anchor xml:id="c9e10d4"/>
-       </title>
-       <interlinear-gloss>
--        <jbo>la .apasionatas ne la betovn. se nelci mi</jbo>
-+        <jbo>la .apasionatas. ku ne la betovn. se nelci mi</jbo>
-         <gloss>The Appassionata, which is of Beethoven, is-liked-by me.</gloss>
-
--- and others
-
 10.xml
 
   <jbo>mi cu pu klama le zarci mi pu klama le zarci</jbo> --
   doubled up
 
   <place-structure>
     Left of a place above me, the man bites the dog.
   </place-structure>
   [snip others]
   <place-structure>

commit aa68dad89ca4d67209b73277a02ccd156e43ba65
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date:   Fri Feb 18 10:23:30 2011 -0800

    Very minor chapter 8 tweak.

diff --git a/todocbook/8.xml b/todocbook/8.xml
index 52c3833..f91dde9 100644
--- a/todocbook/8.xml
+++ b/todocbook/8.xml
@@ -1417,22 +1417,21 @@
       <interlinear-gloss>
         <jbo>le prenu poi ke'a goi ko'a zo'u ko'a zvati le kumfa poi ke'a goi ko'e zo'u ko'a zbasu ke'a cu masno</jbo>
         <gloss>The man who (IT = it1 : it1 is-in the room which (IT = it2 : it1 built it2) is-slow.</gloss>
       </interlinear-gloss>
     </example>
     <para>
       <xref linkend="example-random-id-5TuF"/> is more verbose than 
       <xref linkend="example-random-id-8RdM"/>, but may be clearer, since it explicitly spells out the two 
       <valsi>ke'a</valsi> cmavo, each on its own level, and assigns them to the assignable cmavo 
       <valsi>ko'a</valsi> and 
-      <valsi>ko'e</valsi> (explained in Chapter 
-    <xref linkend="section-koha-broda-series"/>).</para>
+      <valsi>ko'e</valsi> (explained in <xref linkend="section-koha-broda-series"/>).</para>
   </section>
   <section xml:id="section-relative-clause-cmavo-summary">
     <title>Index of relative clause cmavo</title>
     <para> <indexterm type="general-imported"><primary>relative clauses</primary><secondary>list of cmavo for</secondary></indexterm> Relative clause introducers (selma'o NOI):</para>
     <cmavo-list>
       <cmavo-entry>
         <cmavo>noi</cmavo>
         <description>incidental clauses</description>
       </cmavo-entry>
       <cmavo-entry>
diff --git a/todocbook/TODO b/todocbook/TODO
index c945b35..6b6d9d9 100644
--- a/todocbook/TODO
+++ b/todocbook/TODO
@@ -8,28 +8,20 @@ WRT rafsi:  <rafsi type="prefix">man</rafsi> seems best
   Will that suck for <member><jbophrase role="rafsi">ger</jbophrase><jbophrase role="rafsi">-zda</jbophrase></member> ?
 
   Let alone       <member><jbophrase
   role="rafsi">logj</jbophrase><jbophrase
   role="rafsi">-bang</jbophrase><jbophrase
   role="rafsi">-girz</jbophrase></member>
 
 Handling chapter 2: why don't we just require that the number of sub-entries matches?
   Also: maybe rename jbo/gloss for this purpose, or introduce roles.
 
-8.xml
-
-      <jbophrase>ko'e</jbophrase> (explained in Chapter
-    <xref linkend="chapter-anaphoric-cmavo-section-koha-broda-s
-  eries"/>).</para>
-  
-  -- double chapter
-
 9.xml
 
   <gloss>the-number = the-number because ( 2 + 2 ) theref ore 4.</gloss> -- needs an "n" before the =
 
   Do we want to auto-generate the BAI list at the end of Chapter 9
   from jbovlaste?  Probably not for v1.1; for v2 maybe just say
   "read the dict"?
 
   <entry>with</entry>
   <entry>property</entry>

commit a489bb05e1646cdd4d07775fb30e86d1f8373ff0
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date:   Fri Feb 18 10:21:00 2011 -0800

    Tweaks to chapter 7.

diff --git a/todocbook/7.xml b/todocbook/7.xml
index 6b1011c..e661b2f 100644
--- a/todocbook/7.xml
+++ b/todocbook/7.xml
@@ -1546,21 +1546,25 @@
         <gloss>I love you [reciprocity] [x1 of this bridi].</gloss>        
       </interlinear-gloss>
     </example>
     <para>again involves the x1 and x2 places.</para>
     <para> <indexterm type="general-imported"><primary>soi</primary><secondary>use in expressing reciprocity</secondary></indexterm>  <indexterm type="general-imported"><primary>reciprocity</primary><secondary>expressing with soi</secondary></indexterm> Of course, other places can be involved, and other sumti may be used in place of vo'a-series cmavo, provided those other sumti can be reasonably understood as referring to the same things mentioned in the bridi proper. Here are several examples that mean the same thing:</para>
     <example role="interlinear-gloss-example" xml:id="example-random-id-rqNJ">
       <title>
         <anchor xml:id="c7e8d5"/>
       </title>
       <interlinear-gloss>
-        <jbo>mi bajykla ti ta soi vo'e mi bajykla ti ta soi vo'e vo'i soi vo'e vo'i mi bajykla ti ta</jbo>
+        <!-- FIXME: I bet this looks bad; this isn't quite an
+             interlinear gloss situation -->
+        <jbo>mi bajykla ti ta soi vo'e</jbo>
+        <jbo>mi bajykla ti ta soi vo'e vo'i</jbo>
+        <jbo>soi vo'e vo'i mi bajykla ti ta</jbo>
         <gloss>I runningly-go to this from that and vice versa (to that from this).</gloss>
       </interlinear-gloss>
     </example>
     <para> <indexterm type="lojban-word-imported"><primary>SEhU selma'o</primary></indexterm>  <indexterm type="lojban-word-imported"><primary>se'u</primary></indexterm>  <indexterm type="general-imported"><primary>se'u</primary><secondary>elidability considerations</secondary></indexterm>  <indexterm type="general-imported"><primary>se'u</primary><secondary>as elidable terminator for soi</secondary></indexterm> The elidable terminator for 
     <valsi>soi</valsi> is 
     <valsi>se'u</valsi> (selma'o SEhU), which is normally needed only if there is just one sumti after the 
     <valsi>soi</valsi>, and the 
     <valsi>soi</valsi> construction is not at the end of the bridi. Constructions using 
     <valsi>soi</valsi> are free modifiers, and as such can go almost anywhere. Here is an example where 
     
@@ -1923,32 +1927,44 @@
     
     <valsi>du</valsi> lacks: the standard of equality.</para>
   </section>
   <section xml:id="section-anaphoric-rafsi">
     <title>lujvo based on pro-sumti</title>
     <para> <indexterm type="general-imported"><primary>pro-sumti</primary><secondary>rafsi for</secondary></indexterm>  <indexterm type="general-imported"><primary>rafsi</primary><secondary>based on pro-sumti</secondary></indexterm> There exist rafsi allocated to a few cmavo of selma'o KOhA, but they are rarely used. (See 
     <xref linkend="section-koha-summary"/> for a complete list.) The obvious way to use them is as internal sumti, filling in an appropriate place of the gismu or lujvo to which they are attached; as such, they usually stand as the first rafsi in their lujvo.</para>
     <para> <!-- FIXME: this indexterm has nowhere to go --><indexterm type="example-imported"><primary>you-talk</primary><secondary>example</secondary></indexterm>  <indexterm type="general-imported"><primary>pro-sumti rafsi</primary><secondary>effect of on place structure of lujvo</secondary></indexterm>  <indexterm type="general-imported"><primary>lujvo</primary><secondary>pro-sumti rafsi effect on place structure of</secondary></indexterm> Thus 
     <oldjbophrase>donta'a</oldjbophrase>, meaning 
     <quote>you-talk</quote>, would be interpreted as 
-    
     <oldjbophrase>tavla be do</oldjbophrase>, and would have the place structure</para>
+
+    <example role="interlinear-gloss-example" xml:id="example-random-id-unmV">
+      <title>
+        <anchor xml:id="c7e15d1"/>
+      </title>
     <place-structure>t1 talks to you about subject t3 in language t4</place-structure>
+    </example>
     <para>since <varname>t2</varname> (the addressee) is already known to be 
     <valsi>do</valsi>.</para>
     <para> <!-- FIXME: this indexterm has nowhere to go --><indexterm type="example-imported"><primary>you-cmavo</primary><secondary>example</secondary></indexterm> On the other hand, the lujvo 
     <oldjbophrase>donma'o</oldjbophrase>, literally 
     <quote>you-cmavo</quote>, which means 
     
     <quote>a second person personal pronoun</quote>, would be interpreted as 
     <oldjbophrase>cmavo be zo do</oldjbophrase>, and have the place structure:</para>
+
+    <example role="interlinear-gloss-example" xml:id="example-random-id-H5NB">
+      <title>
+        <anchor xml:id="c7e15d2"/>
+      </title>
     <place-structure>c1 is a second person pronoun in language c4</place-structure>
+    </example>
+
     <para>since both the <varname>c2</varname> place (the grammatical class) and the <varname>c3</varname> place (the meaning) are obvious from the context 
     <valsi>do</valsi>.</para>
     <para> <indexterm type="lojban-word-imported"><primary>fo'a</primary></indexterm>  <indexterm type="general-imported"><primary>pro-sumti rafsi</primary><secondary>anticipated use of for abbreviating inconvenient forms</secondary></indexterm> An anticipated use of rafsi for cmavo in the 
     
     <valsi>fo'a</valsi> series is to express lujvo which can't be expressed in a convenient rafsi form, because they are too long to express, or are formally inconvenient (fu'ivla, cmene, and so forth.) An example would be:</para>
     
     
     
     <example role="interlinear-gloss-example" xml:id="example-random-id-tH6w">
       <title>
diff --git a/todocbook/TODO b/todocbook/TODO
index 9ea991a..c945b35 100644
--- a/todocbook/TODO
+++ b/todocbook/TODO
@@ -8,42 +8,20 @@ WRT rafsi:  <rafsi type="prefix">man</rafsi> seems best
   Will that suck for <member><jbophrase role="rafsi">ger</jbophrase><jbophrase role="rafsi">-zda</jbophrase></member> ?
 
   Let alone       <member><jbophrase
   role="rafsi">logj</jbophrase><jbophrase
   role="rafsi">-bang</jbophrase><jbophrase
   role="rafsi">-girz</jbophrase></member>
 
 Handling chapter 2: why don't we just require that the number of sub-entries matches?
   Also: maybe rename jbo/gloss for this purpose, or introduce roles.
 
-7.xml:
-
-  <jbo>mi bajykla ti ta soi vo'e mi bajykla ti ta soi vo'e vo'i soi vo'e vo'i mi bajykla ti ta</jbo> -- needs to be 2
-  
-  <en>I runningly-go to this from that and vice versa.</en|          <en>I run to this from that and vice versa.</en> 
-  -- that's a change; not on the errata list
-
-    <place-structure>t1 talks to you about subject t3 in langua
-  ge t4</place-structure>
-    <para>since <varname>t2</varname> (the addressee) is alread
-  y known to be
-
-      <place-structure>c1 is a second person pronoun in language
-  c4</place-structure>
-    <para>since both the <varname>c2</varname> place (the gramm
-  atical class) and the <varname>c3</varname> place (the meaning)
- are obvious from the context
-
-  -- used to be examples!  That's bad!
-
-  <xref linkend="chapter-abstractions-"/> -- bad
-
 8.xml
 
       <jbophrase>ko'e</jbophrase> (explained in Chapter
     <xref linkend="chapter-anaphoric-cmavo-section-koha-broda-s
   eries"/>).</para>
   
   -- double chapter
 
 9.xml
 

-- 
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.