[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bpfk] dag-cll git updates for Thu Dec 23 17:21:03 EST 2010
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.