[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bpfk] dag-cll git updates for Tue Dec 21 13:21:01 EST 2010
commit 4a0de85939db90620a9cd523d5c944efff9e2dd4
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date: Tue Dec 21 09:44:45 2010 -0800
More id tweaking.
diff --git a/todocbook/12.xml b/todocbook/12.xml
index 6b1a899..706dc1e 100644
--- a/todocbook/12.xml
+++ b/todocbook/12.xml
@@ -43,21 +43,21 @@
</interlinear-gloss>
</example>
<para>Although the lujvo
<quote>fagyfesti</quote> is derived from the tanru
<quote>fagri festi</quote>, it is not equivalent in meaning to it. In particular,
<quote>fagyfesti</quote> has a distinct place structure of its own, not the same as that of
<quote>festi</quote>. (In contrast, the tanru does have the same place structure as
<quote>festi</quote>.) The lujvo needs to take account of the places of
<quote>fagri</quote> as well. When a tanru is made into a lujvo, there is no equivalent of
<quote>be ... bei ... be'o</quote>(described in
- <xref linkend="selbri" />) to incorporate sumti into the middle of the lujvo.</para>
+ <xref linkend="chapter-selbri" />) to incorporate sumti into the middle of the lujvo.</para>
<para>So why have lujvo? Primarily to reduce semantic ambiguity. On hearing a tanru, there is a burden on the listener to figure out what the tanru might mean. Adding further terms to the tanru reduces ambiguity in one sense, by providing more information; but it increases ambiguity in another sense, because there are more and more tanru joints, each with an ambiguous significance. Since lujvo, like other brivla, have a fixed place structure and a single meaning, encapsulating a commonly-used tanru into a lujvo relieves the listener of the burden of creative understanding. In addition, lujvo are typically shorter than the corresponding tanru.</para>
<!-- ^^ creative understanding, 273 -->
<indexterm type="general"><primary>creative understanding</primary></indexterm>
<para>There are no absolute laws fixing the place structure of a newly created lujvo. The maker must consider the place structures of all the components of the tanru and then decide which are still relevant and which can be removed. What is said in this chapter represents guidelines, presented as one possible standard, not necessarily complete, and not the only possible standard. There may well be lujvo that are built without regard for these guidelines, or in accordance with entirely different guidelines, should such alternative guidelines someday be developed. The reason for presenting any guidelines at all is so that Lojbanists have a starting point for deciding on a likely place structure - one that others seeing the same word can also arrive at by similar consideration.</para>
<!-- ^^ alternative guidelines, 273 -->
<indexterm type="general"><primary>alternative guidelines</primary></indexterm>
<!-- ^^ absolute laws, 273 -->
<indexterm type="general"><primary>absolute laws</primary></indexterm>
<para>If the tanru includes connective cmavo such as
<quote>bo</quote>,
@@ -70,21 +70,21 @@
<xref linkend="cll_chapter4" />.</para>
</section>
<section xml:id="cll_chapter12-section2">
<title>The meaning of tanru: a necessary detour</title>
<!-- ^^ necessary detour, 274 -->
<indexterm type="general"><primary>necessary detour</primary></indexterm>
<para>The meaning of a lujvo is controlled by - but is not the same as - the meaning of the tanru from which the lujvo was constructed. The tanru corresponding to a lujvo is called its
<quote>veljvo</quote> in Lojban, and since there is no concise English equivalent, that term will be used in this chapter. Furthermore, the left (modifier) part of a tanru will be called the
<quote>seltau</quote>, and the right (modified) part the
<quote>tertau</quote>, following the usage of
- <xref linkend="selbri" />. For brevity, we will speak of the seltau or tertau of a lujvo, meaning of course the seltau or tertau of the veljvo of that lujvo. (If this terminology is confusing, substituting
+ <xref linkend="chapter-selbri" />. For brevity, we will speak of the seltau or tertau of a lujvo, meaning of course the seltau or tertau of the veljvo of that lujvo. (If this terminology is confusing, substituting
<quote>modifier</quote> for
<quote>seltau</quote> and
<quote>modified</quote> for
<quote>tertau</quote> may help.)</para>
<para>The place structure of a tanru is always the same as the place structure of its tertau. As a result, the meaning of the tanru is a modified version of the meaning of the tertau; the tanru will typically, but not always, refer to a subset of the things referred to by the tertau.</para>
<para>The purpose of a tanru is to join concepts together without necessarily focusing on the exact meaning of the seltau. For example, in the
<citation>Iliad</citation>, the poet talks about
<quote>the wine-dark sea</quote>, in which
<!-- ^^ wine-dark sea, 274 -->
<indexterm type="general"><primary>wine-dark sea</primary></indexterm>
@@ -367,21 +367,21 @@
<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>A substantial minority of lujvo have the property that the first place of the seltau (
<quote>gerku</quote> 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
<!-- ^^ asymmetrical tanru, 104; definition, 104 -->
<indexterm type="general"><primary>asymmetrical tanru</primary></indexterm>
<quote>symmetrical tanru</quote> used in
<!-- ^^ symmetrical tanru, 111 -->
<indexterm type="general"><primary>symmetrical tanru</primary></indexterm>
- <xref linkend="selbri" />.)</para>
+ <xref linkend="chapter-selbri" />.)</para>
<para>In principle any asymmetrical lujvo could be expressed as a symmetrical lujvo. Consider
<quote>gerzda</quote>, discussed in
<xref linkend="cll_chapter12-section3" />, where we learned that the g1 place was equivalent to the z2 place. In order to get the places aligned, we could convert
<quote>zdani</quote> to
<quote>se zdani</quote>(or
<quote>selzda</quote> when expressed as a lujvo). The place structure of
<quote>selzda</quote> is</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-IXoj">
<title>
<anchor xml:id="c12e5d5" />
@@ -1666,21 +1666,21 @@
<quote>jdaselsku</quote>, not resolvable by using
<quote>seljdasku</quote>. No veljvo involving just the two gismu
<quote>lijda</quote> and
<quote>cusku</quote> can fully express the relationship implicit in prayer. A prayer is not just anything said by the adherents of a religion; nor is it even anything said by them acting as adherents of that religion. Rather, it is what they say under the authority of that religion, or using the religion as a medium, or following the rules associated with the religion, or something of the kind. So the veljvo is somewhat elliptical.</para>
<para>As a result, both
<quote>seljdasku</quote> and
<quote>jdaselsku</quote> belong to the second class of anomalous lujvo: the veljvo doesn't really supply all that the lujvo requires.</para>
<para>Another example of this kind of anomalous lujvo, drawn from the tanru lists in
<!-- ^^ lists: use of tu'e/tu'u in, 358 -->
<indexterm type="general"><primary>lists</primary></indexterm>
- <xref linkend="selbri" />, is
+ <xref linkend="chapter-selbri" />, is
<quote>lange'u</quote>, meaning
<quote>sheepdog</quote>. Clearly a sheepdog is not a dog which is a sheep (the symmetrical interpretation is wrong), nor a dog of the sheep breed (the asymmetrical interpretation is wrong). Indeed, there is simply no overlap in the places of
<!-- ^^ sheepdog, 290; example, 290 -->
<indexterm type="general"><primary>sheepdog</primary></indexterm>
<!-- ^^ sheep breed, 290 -->
<indexterm type="general"><primary>sheep breed</primary></indexterm>
<quote>lanme</quote> and
<quote>gerku</quote> at all. Rather, the lujvo refers to a dog which controls sheep flocks, a
<quote>terlanme jitro gerku</quote>, the lujvo from which is
<quote>terlantroge'u</quote> with place structure:</para>
diff --git a/todocbook/14.xml b/todocbook/14.xml
index 3fdb7b4..95fd28d 100644
--- a/todocbook/14.xml
+++ b/todocbook/14.xml
@@ -403,21 +403,21 @@
<interlinear-gloss>
<jbo>la djan. nanmu .inaja la djeimyz. ninmu</jbo>
<gloss>John is-not-a-man or James is-a-woman.</gloss>
<gloss>John is a man only if James is a woman.</gloss>
<en>If John is a man, then James is a woman.</en>
</interlinear-gloss>
</example>
<para>The following example illustrates the use of
<quote>se</quote> to, in effect, exchange the two sentences. The normal use of
<quote>se</quote> is to (in effect) transpose places of a bridi, as explained in
- <xref linkend="selbri" />.</para>
+ <xref linkend="chapter-selbri" />.</para>
<example role="interlinear-gloss-example" xml:id="example-random-id-z43X">
<title>
<anchor xml:id="c14e4d11" />
<anchor xml:id="cll_chapter14-section4-example11" />
</title>
<interlinear-gloss>
<jbo>la djan. nanmu .iseju la djeimyz. ninmu</jbo>
<en>Whether or not John is a man, James is a woman.</en>
</interlinear-gloss>
</example>
diff --git a/todocbook/15.xml b/todocbook/15.xml
index dad2551..eb7d7df 100644
--- a/todocbook/15.xml
+++ b/todocbook/15.xml
@@ -666,21 +666,21 @@
<en>I (other-than-walkingly)-go-to the market.</en>
<jbo>mi cadzu na'e klama le zarci</jbo>
<en>I walkingly-(other-than-go-to) the market.</en>
</interlinear-gloss>
</example>
<para>These negations show the default scope of
<quote>na'e</quote> is close-binding on an individual brivla in a tanru.
<!-- ^^ close-binding, 490 -->
<indexterm type="general"><primary>close-binding</primary></indexterm>
<xref linkend="cll_chapter15-section4-example5" /> says that I am going to the market, but in some kind of a non-walking manner. (As with most tanru, there are a few other possible interpretations, but we'll assume this one - see
- <xref linkend="selbri" /> for a discussion of tanru meaning).</para>
+ <xref linkend="chapter-selbri" /> for a discussion of tanru meaning).</para>
<para>In neither
<xref linkend="cll_chapter15-section4-example5" /> nor
<xref linkend="cll_chapter15-section4-example6" /> does the
<quote>na'e</quote> negate the entire selbri. While both sentences contain negations that deny a particular relationship between the sumti, they also have a component which makes a positive claim about such a relationship. This is clearer in
<xref linkend="cll_chapter15-section4-example5" />, which says that I am going, but in a non-walking manner. In
<xref linkend="cll_chapter15-section4-example6" />, we have claimed that the relationship between me and the market in some way involves walking, but is not one of
<quote>going to</quote>(perhaps we are walking around the market, or walking-in-place while at the market).</para>
<para>The
<quote>scale</quote>, or actually the
<quote>set</quote>, implied in Lojban tanru negations is anything which plausibly can be substituted into the tanru. (Plausibility here is interpreted in the same way that answers to a
diff --git a/todocbook/16.xml b/todocbook/16.xml
index d14f2b4..a886c7b 100644
--- a/todocbook/16.xml
+++ b/todocbook/16.xml
@@ -549,21 +549,21 @@
<anchor xml:id="c16e5d6" />
<anchor xml:id="cll_chapter16-section5-example6" />
</title>
<interlinear-gloss>
<jbo>ro da poi prenu cu se batci de poi gerku</jbo>
<en>Every-X which is-a-person is-bitten-by some-Y which is-a-dog.</en>
</interlinear-gloss>
</example>
<para>using the conversion operator
<quote>se</quote>(explained in
- <xref linkend="selbri" />) to change the selbri
+ <xref linkend="chapter-selbri" />) to change the selbri
<quote>batci</quote>(
<quote>bites</quote>) into
<quote>se batci</quote>(
<quote>is bitten by</quote>). The translation given in
<xref linkend="cll_chapter16-section5-example4" /> uses the corresponding strategy in English, since English does not have prenexes (except in strained
<quote>logician's English</quote>). This implies that a sentence with both a universal and an existential variable can't be freely converted with
<!-- ^^ existential variable: in abstraction contrasted with in main bridi, 400; in main bridi contrasted with in abstraction, 400 -->
<indexterm type="general"><primary>existential variable</primary></indexterm>
<!-- ^^ existential: mixed claim with universal, 394 -->
<indexterm type="general"><primary>existential</primary></indexterm>
diff --git a/todocbook/19.xml b/todocbook/19.xml
index 00879ad..45aed6a 100644
--- a/todocbook/19.xml
+++ b/todocbook/19.xml
@@ -645,21 +645,21 @@
<listitem>
<para>a prenex/topic (to modify some previously expressed bridi, see
<xref linkend="cll_chapter16" />)</para>
</listitem>
<listitem>
<para>linked arguments (beginning with
<!-- ^^ linked arguments, 471 -->
<indexterm type="general"><primary>linked arguments</primary></indexterm>
<quote>be</quote> or
<quote>bei</quote> and attached to some previously expressed selbri, often in a description,see
- <xref linkend="selbri" />)</para>
+ <xref linkend="chapter-selbri" />)</para>
</listitem>
</itemizedlist>
<para>At the beginning of a text, the following non-bridi are also permitted:</para>
<itemizedlist>
<listitem>
<para>one or more names (to indicate direct address without
<!-- ^^ direct address, 323 -->
<indexterm type="general"><primary>direct address</primary></indexterm>
<quote>doi</quote>, see
<xref linkend="cll_chapter6" />)</para>
diff --git a/todocbook/20.xml b/todocbook/20.xml
index 7b4b018..5910070 100644
--- a/todocbook/20.xml
+++ b/todocbook/20.xml
@@ -99,21 +99,21 @@
<xref linkend="GAhO" />.</para>
<programlisting xml:space="preserve">
mi ca sanli la drezdn. bi'i la frankfurt.
I [present] stand-on-surface Dresden [interval] Frankfurt.
I am standing between Dresden and Frankfurt.
<!-- ^^ between Dresden and Frankfurt: example, 359, 360, 361 -->
<indexterm type="general"><primary>between Dresden and Frankfurt</primary></indexterm>
</programlisting>
<bridgehead>
<anchor xml:id="BO" /> selma'o BO (
- <xref linkend="three-part-tanru" />,
+ <xref linkend="section-three-part-tanru" />,
<xref linkend="cll_chapter15-section6" />,
<xref linkend="cll_chapter18-section17" />)</bridgehead>
<para>Joins tanru units, binding them together closely. Also used to bind logically or non-logically connected phrases, sentences, etc.
<xref linkend="BO" /> is always high precedence and right-grouping.</para>
<programlisting xml:space="preserve">
ta cmalu nixli bo ckule
That is-a-small type-of (girl type-of school).
That is a small school for girls.
</programlisting>
<bridgehead>
@@ -1013,21 +1013,21 @@
<bridgehead>
<anchor xml:id="SA" /> selma'o SA (
<xref linkend="cll_chapter19-section13" />)</bridgehead>
<para>Erases the previous phrase or sentence.</para>
<programlisting xml:space="preserve">
mi klama sa do klama le zarci
I go, er, you go-to the market.
</programlisting>
<bridgehead>
<anchor xml:id="SE" /> selma'o SE (
- <xref linkend="brivla" />,
+ <xref linkend="section-brivla" />,
<xref linkend="cll_chapter9-section4" />)</bridgehead>
<para>Converts a selbri, rearranging the order of places by exchanging the x1 place with a specified numbered place.</para>
<programlisting xml:space="preserve">
le zarci cu se klama mi
The market is-gone-to by me.
</programlisting>
<para>Also used in constructing connective and modal compound cmavo.</para>
<bridgehead>
<anchor xml:id="SEI" /> selma'o SEI (
<xref linkend="cll_chapter19-section12" />)</bridgehead>
diff --git a/todocbook/5.xml b/todocbook/5.xml
index 515f441..7e5a9ac 100644
--- a/todocbook/5.xml
+++ b/todocbook/5.xml
@@ -1,11 +1,11 @@
-<chapter xml:id="selbri">
+<chapter xml:id="chapter-selbri">
<title><quote>Pretty Little Girls' School</quote>: The Structure Of Lojban selbri</title>
<section xml:id="section-brivla">
<title>Lojban content words: brivla</title>
<para>At the center, logically and often physically, of every Lojban bridi is one or more words which constitute the selbri. A bridi expresses a relationship between things: the selbri specifies which relationship is referred to. The difference between:</para>
<example role="interlinear-gloss-example" xml:id="example-do-mamta-mi">
<title>
<anchor xml:id="c5e1d1" />
<anchor xml:id="cll_chapter5-section1-example1" />
</title>
<interlinear-gloss>
diff --git a/todocbook/README b/todocbook/README
deleted file mode 100644
index eec0d71..0000000
--- a/todocbook/README
+++ /dev/null
@@ -1,85 +0,0 @@
-=======================================================================
- BEGIN ISSUES THAT STILL MATTER AFTER THE CONVERSION IS DONE
-=======================================================================
-
-Everything here should be moved to other documentation at some point.
-
-In:
-
- <example role="interlinear-gloss-example" xml:id="random-id-jig0">
-
-the id is a random string to be used for anchors only, i.e. not for
-humans. It should never be changed or removed. It should follow
-the example around forever (unless the example itself is removed, of
-course).
-
-==================================================================
- END ISSUES THAT STILL MATTER AFTER THE CONVERSION IS DONE
-==================================================================
-
-This directory is used to turn the old HTML many-files stuff into
-dockbook/xml. It's not ever intended to be re-run once it's all
-working properly; the scripts and stuff are still here in case
-something is found that's easier to fix in the HTML and propogate
-through.
-
-Anyways, that's why these instructions on how to build everything
-aren't in a makefile or something.
-
-First pass was done like this:
-
- superglom.sh
-
- merge.sh
-
- xmlto -o html/ html cll.xml 2>&1 | grep -v 'No localization exists for "jbo" or "". Using default "en".'
-
-This resulted in a bunch of files named N.xml, where N is a chapter
-number, and cll.xml as the whole, and html/ with the html version
-thereof (which also proves that it validates).
-
-For the second pass these files were moved to N.xml.orig. The .orig
-files were tweaked by hand somewhat, but most of the processing was
-automatically done by
-
- massage.sh
-
-and its various sub-scripts. This did quote handling, turned the
-<programlisting> example bits into the real example structure we're
-going to use, and gave them random id tags for future use.
-
-massage.sh relies on:
-
- identity.xsl
- insert_ids.pl
- make_examples.xsl
- massage.sh
- random-ids
-
-There is now a
-
- Makefile
-
-to do all the steps to turn the N.xml files into html/. There is
-actually an extra XSLT preprocessing step now. The makefile relies
-on:
-
- docbook2html.css
- docbook2html_config.xsl
- docbook2html_preprocess.xsl
- identity.xsl
-
-The third pass was pretty limited, and was basically just:
-
- make_cmavo.pl
- massage2.sh
-
-(with the .orig trick as above). It create the <cmavo-list>
-entries.
-
-The fourth pass was similarily limited, and was just about the
-index:
-
- make_index.sh
- origcllindex.txt
- TODO-index
diff --git a/todocbook/README-conversion b/todocbook/README-conversion
new file mode 100644
index 0000000..eec0d71
--- /dev/null
+++ b/todocbook/README-conversion
@@ -0,0 +1,85 @@
+=======================================================================
+ BEGIN ISSUES THAT STILL MATTER AFTER THE CONVERSION IS DONE
+=======================================================================
+
+Everything here should be moved to other documentation at some point.
+
+In:
+
+ <example role="interlinear-gloss-example" xml:id="random-id-jig0">
+
+the id is a random string to be used for anchors only, i.e. not for
+humans. It should never be changed or removed. It should follow
+the example around forever (unless the example itself is removed, of
+course).
+
+==================================================================
+ END ISSUES THAT STILL MATTER AFTER THE CONVERSION IS DONE
+==================================================================
+
+This directory is used to turn the old HTML many-files stuff into
+dockbook/xml. It's not ever intended to be re-run once it's all
+working properly; the scripts and stuff are still here in case
+something is found that's easier to fix in the HTML and propogate
+through.
+
+Anyways, that's why these instructions on how to build everything
+aren't in a makefile or something.
+
+First pass was done like this:
+
+ superglom.sh
+
+ merge.sh
+
+ xmlto -o html/ html cll.xml 2>&1 | grep -v 'No localization exists for "jbo" or "". Using default "en".'
+
+This resulted in a bunch of files named N.xml, where N is a chapter
+number, and cll.xml as the whole, and html/ with the html version
+thereof (which also proves that it validates).
+
+For the second pass these files were moved to N.xml.orig. The .orig
+files were tweaked by hand somewhat, but most of the processing was
+automatically done by
+
+ massage.sh
+
+and its various sub-scripts. This did quote handling, turned the
+<programlisting> example bits into the real example structure we're
+going to use, and gave them random id tags for future use.
+
+massage.sh relies on:
+
+ identity.xsl
+ insert_ids.pl
+ make_examples.xsl
+ massage.sh
+ random-ids
+
+There is now a
+
+ Makefile
+
+to do all the steps to turn the N.xml files into html/. There is
+actually an extra XSLT preprocessing step now. The makefile relies
+on:
+
+ docbook2html.css
+ docbook2html_config.xsl
+ docbook2html_preprocess.xsl
+ identity.xsl
+
+The third pass was pretty limited, and was basically just:
+
+ make_cmavo.pl
+ massage2.sh
+
+(with the .orig trick as above). It create the <cmavo-list>
+entries.
+
+The fourth pass was similarily limited, and was just about the
+index:
+
+ make_index.sh
+ origcllindex.txt
+ TODO-index
diff --git a/todocbook/merge.sh b/todocbook/merge.sh
index 4588085..6240a35 100755
--- a/todocbook/merge.sh
+++ b/todocbook/merge.sh
@@ -7,21 +7,22 @@ echo '<?xml version="1.0"?>
<book xmlns:xlink="http://www.w3.org/1999/xlink";>
<!-- THIS FILE IS AUTOGENERATED. DO NOT EDIT OR CHECK IN! -->
' >cll.xml
if [ "$1" == "-t" ]
then
echo "Entering testing mode: will replace all external xrefs in each chapter."
fi
-<chapter xml:id="selbri">
+#<chapter xml:id="chapter-selbri">
+#<section xml:id="section-brivla">
for file in $@
do
cat $file >>cll.xml
done
cp cll.xml cll_preglossary.xml
echo '</book>' >>cll_preglossary.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.