I vaguely recall some discussion of an “indexing” project, but find nothing from me re that in this thread. As a user of ABoK, I’ve continually been annoyed that the Index has page #s vice item/prg. #s :: for a book that is largely a series of #'d paragraphs, giving a pg.# suffers from not only being needlessly inexact but potentially incomplete (i.e., if some index’d term occurs on more that one #'d prg on the page, a reader reaching one occurrence will not know to look for others).
MY indexing project thus was to convert all pg.#s to prg./entity #s (with maybe some exceptions as needed where “pg.<#>” could be given so to point out that THIS one is for a page (such things might occur in the front pages).
And … to get more helpful in the citations :: group them by relevance, this grouping maybe shown w/font difference or punctuation-separator. Some places where “clove hitch” occurs though indeed having that index’d term might have virtually no significance to the knot.
IMO, such a work is done as text, not spreadsheet. ABoK’s Index
is 70 lines deep for 12pp (nearly full) = 840 lines --a number likely
to grow with new indexing finding more. (E.g., I’ve found a further
4 occurrences of “clove hitch” to the already large Index’s number.
(Fortunately, most items have but a couple/few occurrences!))
OW, no : I don’t want nearly 2_000 topics to bother with!
I’m thinking of a maybe 15-40pp printing I can stuff in
the back of my ABoK; or which resides e-wise to be
Search’d. (Alas, my unaided eyes don’t so well see
ABoK’s Index’s fine print. )
And “each knot” in my scheme has rather
simple information --not a Topic’s worth.