Received: from mail-gy0-f189.google.com ([209.85.160.189])
	by chain.digitalkingdom.org with esmtp (Exim 4.72)
	(envelope-from <bpfk-list+bncCMbnveiNHRDE-s7oBBoEpGpKkQ@googlegroups.com>)
	id 1PVsbA-0005pX-Du; Thu, 23 Dec 2010 13:21:24 -0800
Received: by gyb11 with SMTP id 11sf5998307gyb.16
        for <multiple recipients>; Thu, 23 Dec 2010 13:21:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=googlegroups.com; s=beta;
        h=domainkey-signature:received:mime-version:x-beenthere:received
         :received:received:received:received-spf:received:received:received
         :date:message-id:to:subject:from:x-original-sender
         :x-original-authentication-results:reply-to:precedence:mailing-list
         :list-id:list-post:list-help:list-archive:sender:list-subscribe
         :list-unsubscribe:content-type;
        bh=U+4NkWP83xMCJQJCS7Eg3rCUuewWcNEdnmWdvlHUqtI=;
        b=AnHzY2aNXBZJdlZeJuZjI59qTxLob5cTDVAiwHcyZla7Hd1fJnIpfn2q/VJwCCNWRF
         OOQs9gOgF1HVw8iBPxBydhdPu7vjw7LlczApJzVF6JeIC03DungmPT1L1tqoGBkzTZ3H
         4lKI8UVOPURgisUXudPsIsveXGO1qwGUMR5ZQ=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlegroups.com; s=beta;
        h=mime-version:x-beenthere:received-spf:date:message-id:to:subject
         :from:x-original-sender:x-original-authentication-results:reply-to
         :precedence:mailing-list:list-id:list-post:list-help:list-archive
         :sender:list-subscribe:list-unsubscribe:content-type;
        b=TTTlVgR2OHClkOmhyeP2zpjR2YPG86g7pOKvkFmuOiHNNOnLvZxmuuCUi1B3txHMCX
         UsthcHRy17HjujZHXZeYek++77NR/2YdU+evT3YVODnt8Wk7A/XwSHozbEZ8B0MP7wos
         KOePsURX0i0qF+Q1HZjOM4Ez1QiiTLgUJo3h8=
Received: by 10.90.225.4 with SMTP id x4mr1736agg.39.1293139268211;
        Thu, 23 Dec 2010 13:21:08 -0800 (PST)
MIME-Version: 1.0
X-BeenThere: bpfk-list@googlegroups.com
Received: by 10.231.76.165 with SMTP id c37ls2528512ibk.3.p; Thu, 23 Dec 2010
 13:21:07 -0800 (PST)
Received: by 10.142.44.16 with SMTP id r16mr6369286wfr.47.1293139267553;
        Thu, 23 Dec 2010 13:21:07 -0800 (PST)
Received: by 10.142.44.16 with SMTP id r16mr6369285wfr.47.1293139267526;
        Thu, 23 Dec 2010 13:21:07 -0800 (PST)
Received: from chain.digitalkingdom.org (digitalkingdom.org [173.13.139.234])
        by gmr-mx.google.com with ESMTPS id p40si8516951wfc.2.2010.12.23.13.21.07
        (version=TLSv1/SSLv3 cipher=RC4-MD5);
        Thu, 23 Dec 2010 13:21:07 -0800 (PST)
Received-SPF: pass (google.com: best guess record for domain of nobody@digitalkingdom.org designates 173.13.139.234 as permitted sender) client-ip=173.13.139.234;
Received: from nobody by chain.digitalkingdom.org with local (Exim 4.72)
	(envelope-from <nobody@digitalkingdom.org>)
	id 1PVsaw-0005pI-SH
	for bpfk-list@googlegroups.com; Thu, 23 Dec 2010 13:21:06 -0800
Received: from 128-177-28-49.ip.openhosting.com ([128.177.28.49] helo=oh-www1.lojban.org)
	by chain.digitalkingdom.org with esmtp (Exim 4.72)
	(envelope-from <www-data@oh-www1.lojban.org>)
	id 1PVsat-0005p9-73
	for bpfk@lojban.org; Thu, 23 Dec 2010 13:21:06 -0800
Received: from www-data by oh-www1.lojban.org with local (Exim 4.72)
	(envelope-from <www-data@oh-www1.lojban.org>)
	id 1PVsar-0005Q6-UJ
	for bpfk@lojban.org; Thu, 23 Dec 2010 16:21:01 -0500
Date: Thu, 23 Dec 2010 16:21:01 -0500
Message-Id: <E1PVsar-0005Q6-UJ@oh-www1.lojban.org>
To: bpfk@lojban.org
Subject: [bpfk] dag-cll git updates for Thu Dec 23 16:21:01 EST 2010
From: www-data <www-data@oh-www1.lojban.org>
X-Original-Sender: www-data@oh-www1.lojban.org
X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com:
 best guess record for domain of nobody@digitalkingdom.org designates
 173.13.139.234 as permitted sender) smtp.mail=nobody@digitalkingdom.org
Reply-To: bpfk-list@googlegroups.com
Precedence: list
Mailing-list: list bpfk-list@googlegroups.com; contact bpfk-list+owners@googlegroups.com
List-ID: <bpfk-list.googlegroups.com>
List-Post: <http://groups.google.com/group/bpfk-list/post?hl=en_US>, <mailto:bpfk-list@googlegroups.com>
List-Help: <http://groups.google.com/support/?hl=en_US>, <mailto:bpfk-list+help@googlegroups.com>
List-Archive: <http://groups.google.com/group/bpfk-list?hl=en_US>
Sender: bpfk-list@googlegroups.com
List-Subscribe: <http://groups.google.com/group/bpfk-list/subscribe?hl=en_US>, <mailto:bpfk-list+subscribe@googlegroups.com>
List-Unsubscribe: <http://groups.google.com/group/bpfk-list/subscribe?hl=en_US>,
 <mailto:bpfk-list+unsubscribe@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Length: 6818

commit ad6589119709cb5c2ee2aef3a8e775d661514eb5
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date:   Thu Dec 23 13:17:07 2010 -0800

    More documentation updates.

diff --git a/todocbook/TODO b/todocbook/TODO
index 1f3e2e7..f621c03 100644
--- a/todocbook/TODO
+++ b/todocbook/TODO
@@ -109,36 +109,40 @@ Also, use <jbophrase valid="false">...</jbophrase> for na gendra and
 change it, or think it's actually correct in some particular place,
 post to the BPFK list.
 
  ------
 
 If an example/interlinear-gloss consists solely of English, replace
 the <interlinear-gloss>...</interlinear-gloss> with <para>...</para>
 
  ------
 
+    YOU CAN SKIP THIS PART; it's easy to check for it later on, even
+    in parts that have theoretically already been reviewed.
+
 Deal with index entries already in the text, like these:
 
     <example role="interlinear-gloss-example" xml:id="random-id-UMjE">
       <title>
         <anchor xml:id="c5e1d5" />
       </title>
       <interlinear-gloss>
         <jbo>ta blotrskunri</jbo>
         <gloss>That is-a-(boat)-schooner.</gloss>
 <!-- ^^   schooner: example, 83 -->
 <indexterm><primary>schooner</primary></indexterm>
         <en>That is a schooner.</en>
       </interlinear-gloss>
     </example>
 
-There are several steps:
+There are several steps for single-entry situations like this;
+multi-entry situations are something else again.
 
 1.  Add a <secondary> tag as appropriate.  In this case, "example".
 
 2.  Move it to somewhere that seems aesthetically pleasing, is
 accepted by docbook (try running "make" to check), and is very near
 the text in question.  For examples, this is just after the title.
 Just inside a <para> (move the actual text after the <indexterm>) is
 often a good choice.
   
   YOU MAY NEED A COPY OF THE RED BOOK to do this part effectively,
@@ -169,27 +173,69 @@ with all other instances removed.  To find them, try:
 or similar.
 
 Please use *exactly* that
 <indexterm><primary>[item]</primary><secondary>example</secondary></indexterm>
 format for examples, as we might want to automatically munge it
 later.
 
 4.  Make sure that all the *other* options listed for the keyword
 exist somewhere.  For example, given:
 
+ ------
+
+    YOU CAN SKIP THIS PART; it's easy to check for it later on, even
+    in parts that have theoretically already been reviewed.
+
+Multi-entry index situations are a whole different kettle of fish.
+Here's an example:
+
   <!-- ^^   tanru grouping: complex, 87; effect of tanru inversion on, 96; guheks compared with jeks, 350; three-part, 85; with bo, 87; with ke, 88; with ke and bo, 88 -->
+  <indexterm><primary>schooner</primary></indexterm>
 
-that all 7 of those entries actually have referents somewhere in the text.
+The problem is that just because the automated inclusion of that
+indexterm was inserted in this particular place, which presumably is
+near where one of the 7 entries listed there is supposed to actually
+point to, that doesn't mean that any of the *other* entries got
+inserted in the right place.  That means that
 
-  YOU MAY NEED A COPY OF THE RED BOOK to do this part effectively,
-  because you should be tagging the same bits of text as it is
-  (along with others if you wish).
+  <!-- ^^   tanru grouping: complex, 87; effect of tanru inversion on, 96; guheks compared with jeks, 350; three-part, 85; with bo, 87; with ke, 88; with ke and bo, 88 -->
+  <indexterm><primary>schooner</primary></indexterm>
+
+needs to be turned into *all of*:
+
+  <indexterm><primary>tanru grouping</primary><secondary>complex</secondary></indexterm>
+
+  <indexterm><primary>tanru grouping</primary><secondary>effect of tanru inversion on</secondary></indexterm>
+
+  <indexterm><primary>tanru grouping</primary><secondary>guheks compared with jeks</secondary></indexterm>
+
+  <indexterm><primary>tanru grouping</primary><secondary>three-part</secondary></indexterm>
+
+  <indexterm><primary>tanru grouping</primary><secondary>with bo</secondary></indexterm>
+
+  <indexterm><primary>tanru grouping</primary><secondary>with ke</secondary></indexterm>
+
+  <indexterm><primary>tanru grouping</primary><secondary>with ke and bo</secondary></indexterm>
+
+And each of those needs to be placed in some appropriate place in
+the text, where "appropriate" means "in about the same place as it
+currently is in the red book", *and* all instances of the original
+bits, i.e.:
+
+  <!-- ^^   tanru grouping: complex, 87; effect of tanru inversion on, 96; guheks compared with jeks, 350; three-part, 85; with bo, 87; with ke, 88; with ke and bo, 88 -->
+  <indexterm><primary>schooner</primary></indexterm>
+
+need to be removed.
+
+YOU NEED A COPY OF THE RED BOOK to do this part effectively, because
+you should be tagging the same bits of text as it is (along with
+others if you wish).
 
  ------
 
 NON-CHATPER work: Add index entries based on TODO-index.  Pick a
 point in the middle somewhere, please, and *especially* for this
 work, check in often.
 
 You will almost certainly need a physical copy of the red book to do
 this effectively.
 

commit ab38eb14afe26f58f6c11b68447f29c0e9a019ce
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date:   Thu Dec 23 12:26:05 2010 -0800

    Doc update.

diff --git a/todocbook/TODO b/todocbook/TODO
index e46702e..1f3e2e7 100644
--- a/todocbook/TODO
+++ b/todocbook/TODO
@@ -61,20 +61,28 @@ example has an obvious title, but it's much less important there, so
 not worth spending time on for the first pass.
 
 The important thing here is that *NOTHING* mentions a fixed number!
 *NOWHERE* in the docbook should *ANYTHING* be aware that it is in
 chapter 20 or section 7 or anything like that.  This is to give us
 the freedom to move things around later.
 
 Numeric-based stuff will all be autogenerated during processing,
 based on the current state of the docs.
 
+THERE IS ONE EXCEPTION: DO NOT change anchors that are two or three
+pairs of letters and numbers, like this:
+
+  <anchor xml:id="c5e1d5" />
+
+They are going to be needed down the road to provide backwards
+compatability.  Don't touch them.
+
  ------
 
 With the caveat that indexterm entries for examples should look
 exactly like this:
 
 <indexterm><primary>[item]</primary><secondary>example</secondary></indexterm>
 
 , do feel free to add index entries where they seem useful.  It's
 unlikely that we can ever have a too-thorough index (and it's a lot
 easier to cut the thing down than to grow it anyways).

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