Received: from mail-pz0-f61.google.com ([209.85.210.61])
	by chain.digitalkingdom.org with esmtp (Exim 4.72)
	(envelope-from <bpfk-list+bncCMbnveiNHRDVls_oBBoEex2GDA@googlegroups.com>)
	id 1PVtXE-0006Yb-Qz; Thu, 23 Dec 2010 14:21:24 -0800
Received: by pzk9 with SMTP id 9sf315031pzk.16
        for <multiple recipients>; Thu, 23 Dec 2010 14:21:15 -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=CG/5EFylkjrjQq1u18n9PVZq+fGwiO3cuYzWEHn6pMU=;
        b=GfMN8fyx4NUNQ7xjgobywx/oBdUNSAb48qe+eDoCAlQU5CF/8I7jeQ5V8XCdQY9LH0
         Mal+Xrge7cZkZFdiqK6PZQ7eK2RxZQUglwFQsJsTfW7YUyQlto3nKlKKvjeKTwTHMFYH
         /J5MRNZ9rD3YwvIeAGlPjEc4VGbRZNBxK4Z0c=
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=tBtgOEZUD9r7QSbXysuyXtfpkMT/UnjLJLz+JXWUlYuGfHE7cmaTFIh1lDNN+S41xf
         Qs1un84Ddyz6Aj1w/i0DPyBqv/ofSd85kHXHkcq0bxJ6q+EKDm9lqyymi6PW6CxUFSkh
         /URNRd4VLXWwEt0ZxiKcqN2LNf8MYNEqE4z2c=
Received: by 10.143.26.28 with SMTP id d28mr464267wfj.0.1293142869403;
        Thu, 23 Dec 2010 14:21:09 -0800 (PST)
MIME-Version: 1.0
X-BeenThere: bpfk-list@googlegroups.com
Received: by 10.142.249.41 with SMTP id w41ls12510570wfh.1.p; Thu, 23 Dec 2010
 14:21:08 -0800 (PST)
Received: by 10.142.177.1 with SMTP id z1mr6516964wfe.2.1293142868845;
        Thu, 23 Dec 2010 14:21:08 -0800 (PST)
Received: by 10.142.177.1 with SMTP id z1mr6516963wfe.2.1293142868822;
        Thu, 23 Dec 2010 14:21:08 -0800 (PST)
Received: from chain.digitalkingdom.org (digitalkingdom.org [173.13.139.234])
        by gmr-mx.google.com with ESMTPS id p40si8569308wfc.2.2010.12.23.14.21.08
        (version=TLSv1/SSLv3 cipher=RC4-MD5);
        Thu, 23 Dec 2010 14:21:08 -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 1PVtX2-0006YF-1T
	for bpfk-list@googlegroups.com; Thu, 23 Dec 2010 14:21:08 -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 1PVtWy-0006Y4-OA
	for bpfk@lojban.org; Thu, 23 Dec 2010 14:21:07 -0800
Received: from www-data by oh-www1.lojban.org with local (Exim 4.72)
	(envelope-from <www-data@oh-www1.lojban.org>)
	id 1PVtWx-0006b9-DX
	for bpfk@lojban.org; Thu, 23 Dec 2010 17:21:03 -0500
Date: Thu, 23 Dec 2010 17:21:03 -0500
Message-Id: <E1PVtWx-0006b9-DX@oh-www1.lojban.org>
To: bpfk@lojban.org
Subject: [bpfk] dag-cll git updates for Thu Dec 23 17:21:03 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: 3155

commit 0f4c004539068ad1101f7cbc3a7fc2654afe45b6
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date:   Thu Dec 23 14:01:29 2010 -0800

    don't touch the index bits.

diff --git a/todocbook/TODO b/todocbook/TODO
index f621c03..8a6b49f 100644
--- a/todocbook/TODO
+++ b/todocbook/TODO
@@ -71,20 +71,23 @@ 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.
 
  ------
 
+ DO NOT TOUCH THE INDEX ENTRIES RIGHT NOW.  I think I've found a way
+ to automate 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).
 
  ------
@@ -109,20 +112,23 @@ 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>
 
  ------
 
+  DO NOT TOUCH THE INDEX ENTRIES RIGHT NOW.  I think I've found a
+  way to automate them.
+
     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>
@@ -175,20 +181,23 @@ 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:
 
  ------
 
+  DO NOT TOUCH THE INDEX ENTRIES RIGHT NOW.  I think I've found a
+  way to automate them.
+
     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>
 
 The problem is that just because the automated inclusion of that

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