From 40611db90e31b06763dc0989b5e51c99a1a64080 Mon Sep 17 00:00:00 2001
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Date: Sun, 31 Dec 2023 15:35:54 +1300
Subject: [PATCH] First vesrion

---
 utilities/utDoc.md | 107 +++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 107 insertions(+)

diff --git a/utilities/utDoc.md b/utilities/utDoc.md
index a099036..48e5a43 100644
--- a/utilities/utDoc.md
+++ b/utilities/utDoc.md
@@ -1 +1,108 @@
+## The book6 utilities
+
+### makeBook
+
+This program is applied to the entire book6 directory
+whenever significant changes have been made. The reader 
+is assumed to have carefully read the 
+[Chapter Template](https://github.com/becarpenter/book6/blob/main/99.%20Chapter%20Template/99.%20Chapter%20Template.md)
+chapter.
+
+__makeBook__'s functions include:
+
+ - Update the global contents (`Contents.md`) to reflect the actual chapter contents.
+
+ - Update the individual chapter files (`./ChapterName/ChapterName.md`) to correspond to the global contents.
+
+ - Create any missing section files (`./ChapterName/SectionName.md`).
+
+ - Reconcile discrepancies between the global contents, the chapter
+contents, and the actual section files. (Not all discrepancies can
+be automatically reconciled - __makeBook__ will issue a warning if it
+detects such a case).
+
+ - Resolve any raw citations (`{{something}}` or `{{{something}}}`)
+into a complete markdown link (`[something](URL)`).
+
+ - Create and insert internal links (from a chapter file to the
+individual sections, from each section to its predecessor and
+successor, etc.)
+
+ - Reformat markdown text if appropriate.
+
+After updating a section, especially if adding a new citation
+with `{{ }}` or `{{{ }}}`, it's appropriate to run __makeBook.py__ 
+(Python 3; requires _tkinter_; uses _mdformat_ if installed).
+
+To make changes other than just updating an existing section, 
+also see [chapterReorg](./chapterReorg.md).
+
+__makeBook__ works roughly as follows, using a _tkinter_ GUI, not
+standard input.
+
+1. Request name of _book6_ directory from user. Normally this
+will be the local copy of the GitHub repo.
+
+2. Determine whether automatic checking of RFC existence is
+possible. If __makeBook__ cannot access a recent copy of the RFC
+index, this checking is impossible and it logs a warning.
+
+3. Determine whether automatic checking of I-D existence is
+possible. If __makeBook__ cannot access the current I-D index,
+this checking is impossible and book6 logs a warning.
+
+4. Read in the existing main contents (_Contents.md_).
+
+5. Convert any plain text chapter names to links.
+
+6. Scan main contents and create any missing chapter directories
+and blank chapter files, build a chapter list, extract
+section lists for each chapter, and add any missing section
+names to the main contents.
+
+7. For each chapter:
+
+7.1 If there is a remaining discrepancy between
+the list of sections in the main contents and the section
+files actually present, log a warning that __makeBook__ must
+be run again to resolve it. Also log a warning if there is
+an uppercase/lowercase discrepancy (which really needs
+manual fixing).
+
+7.2 Create and initialize any missing section files.
+
+7.3 If anything in the chapter file has changed during
+steps 7.1 and 7.2 , write it back.
+
+7.4 For each section in the chapter:
+
+7.4.1 Read in the markdown file, update internal links
+if necessary, expand any `{{ }}` or `{{{ }}}` citations
+as markdown links (but log a warning if this fails).
+
+7.4.2. If anything in the section file has changed during
+step 7.4.1, write it back.
+
+7.5. Read in the chapter markdown file (again),
+expand any `{{ }}` or `{{{ }}}` citations as markdown links
+(but log a warning if this fails), and write it back
+if necessary.
+
+8. Finally, write back the main contents.
+
+Note that expanding citations is done by the function
+_expand_cites()_ which is straightforward but tedious
+to describe.
+
+__makeBook__ issues warnings to standard output but also
+to the file _makeBook.log_ in the main book directory.
+This log should always be checked after a run!
+
+
+### makeIndex
+
 TBD
+
+### RFCbib6
+
+TBD
\ No newline at end of file