Cleanup some configuration and add tag files

build/documentation/README.md

@@ -1,5 +1,7 @@
 # Documentation HOWTO
 
+\note For linking to these docs, the doxygen tag file is  `tidy.tags`
+
 **HTML Tidy** provides several types of documentation to suit different purposes. This
 document describes how to generate the following:
 

build/documentation/build_docs.sh

@@ -121,7 +121,7 @@ if [ "$BUILD_API" -eq 1 ]; then
   # - which are then passed to doxygen as stdin (instead of the path to a config.file)
   ( cat "$DOXY_CFG"; \
     echo "PROJECT_NUMBER=$TIDY_VERSION"; \ 
-    echo "HTML_EXTRA_FILES=$OUTP_DIR/quickref.html ./examples/tidy5.cmd.txt"; ) \
+    echo "HTML_EXTRA_FILES=$OUTP_DIR/quickref.html ./examples/tidy5.help.txt ./examples/tidy5.config.txt"; ) \
     | doxygen - > /dev/null
     
     # cleanup

build/documentation/doxygen.cfg

@@ -32,7 +32,7 @@ PROJECT_NAME           = "HTML Tidy"
 # This could be handy for archiving the generated documentation or
 # if some version control system is used.
 
-PROJECT_NUMBER         = 4.9.15
+PROJECT_NUMBER         = version.txt
 
 # Using the PROJECT_BRIEF tag one can provide an optional one line description
 # for a project that appears at the top of each page and should give viewer
@@ -1669,7 +1669,7 @@ TAGFILES               =
 # When a file name is specified after GENERATE_TAGFILE, doxygen will create
 # a tag file that is based on the input files it reads.
 
-GENERATE_TAGFILE       =
+GENERATE_TAGFILE       = tidy.tags
 
 # If the ALLEXTERNALS tag is set to YES all external classes will be listed
 # in the class index. If set to NO only the inherited external classes