Reenable automatic tagging

Adds a Dockerfile that builds the project, and a drone pipeline to push
the docker image to the docker hub.

.drone.yml

@@ -0,0 +1,12 @@
+kind: pipeline
+name: default
+
+steps:
+- name: docker
+  image: plugins/docker
+  settings:
+    repo: egraven/tidy-html5
+    username: egraven
+    autotag: true
+    password:
+      from_secret: DOCKER_TOKEN

.github/workflows/api_test.yml

@@ -0,0 +1,95 @@
+################################################################################
+# Test LibTidy Public API (via Swift SwLibTidy).
+#
+# Because SwLibTidy wraps nearly 100% of LibTidy's API, it's a great candidate
+# for testing LibTidy via a high-level, easy to write and understand tests.
+#
+#   - This is a Public API test of LibTidy. It does not test the console
+#     application, is not a unit test, and is not an output regression test.
+#
+#   - Build on multiple operating systems, once the runners are equipped with
+#     Swift.
+#
+################################################################################
+
+name: API Test via SwLibTidy
+
+on:
+  push:
+    paths:
+      - 'src/**'
+      - 'include/**'
+      - '.github/workflows/**'
+  pull_request:
+    paths:
+      - 'src/**'
+      - 'include/**'
+      - '.github/workflows/**'
+
+jobs:
+
+  test_library_api:
+    runs-on: ${{ matrix.os }}
+    strategy:
+      fail-fast: false
+      matrix:
+        include:
+
+         ############################################################
+         # Ubuntu latest is a normal build with nothing special that
+         # really need be done.
+         # Note: currently disabled because some tests need to be
+         #   refactored to avoid using macOS specific library calls.
+         ############################################################
+#          - os: ubuntu-latest
+#            name: Ubuntu
+
+         ############################################################
+         # On macOS, we'll build both architectures.
+         # Note: this is the currently only enabled runner, and I'm
+         #   comfortable with it. This exercises nearly all of
+         #   HTML Tidy's library API, which should be platform
+         #   agnostic.
+         ############################################################
+         - os: macOS-latest
+           name: macOS
+
+         ############################################################
+         # The standard Windows build is perfectly vanilla, and as
+         # of now is using MSVC 19.
+         # Note: currently disabled because some tests need to be
+         #   refactored to avoid using macOS specific library calls,
+         #   but mostly because the Windows runners aren't set up
+         #   yet for running Swift code.
+         ############################################################
+#          - os: windows-latest
+#            name: MSVC
+           
+    steps:
+
+    ############################################################
+    # Checkout the Swift testing repository.
+    ############################################################
+    - name: Checkout SwLibTidy
+      uses: actions/checkout@v2
+      with:
+        repository: htacg/SwLibTidy
+
+
+    ############################################################
+    # Checkout the Tidy repository as Source/CLibTidy
+    ############################################################
+    - name: Checkout this repository
+      uses: actions/checkout@v2
+      with:
+        path: ${{github.workspace}}/Sources/CLibTidy
+
+
+    ############################################################
+    # Perform swift test
+    # Note: Github truncates the in-browser log. If you want
+    #   to see everything, look for the Raw Logs button.
+    ############################################################
+    - name: Swift Test
+      run: |
+        swift test

.github/workflows/build_and_test.yml

@@ -0,0 +1,183 @@
+################################################################################
+# Build and Test tidy on the latest versions of all of the major platforms.
+#
+#   - Build on multiple operating systems, and where possible, multiple
+#     architectures. On Windows, we will also build and test mingw in
+#     addition to MSVC.
+#
+#   - Report the version number for each binary that is built.
+#
+#   - Run each binary against the regression test suite.
+#
+################################################################################
+
+name: Build and Test
+
+on:
+  push:
+    paths:
+      - 'src/**'
+      - 'include/**'
+      - '.github/workflows/**'
+      - 'CMakeLists.txt'
+    branches:
+      - 'master'
+      - 'next'
+  pull_request:
+    paths:
+      - 'src/**'
+      - 'include/**'
+      - '.github/workflows/**'
+      - 'CMakeLists.txt'
+
+jobs:
+
+  build_and_test:
+    runs-on: ${{ matrix.os }}
+    strategy:
+      fail-fast: false
+      matrix:
+        include:
+
+         ############################################################
+         # Ubuntu latest is a normal build with nothing special that
+         # really need be done.
+         ############################################################
+         - os: ubuntu-latest
+           name: Standard
+           cmake_command: "cmake ../.. -DCMAKE_BUILD_TYPE=Release"
+           build_command: "cmake --build . --config Release"
+           vers_command: "./tidy --version"
+           test_command: "ruby test.rb test"
+
+         ############################################################
+         # On macOS, we'll build both architectures.
+         ############################################################
+         - os: macOS-latest
+           name: X86_64 & Arm64
+           cmake_command: "cmake ../.. -DCMAKE_BUILD_TYPE=Release '-DCMAKE_OSX_ARCHITECTURES=x86_64;arm64'"
+           build_command: "cmake --build . --config Release"
+           vers_command: "./tidy --version"
+           test_command: "ruby test.rb test"
+
+         ############################################################
+         # The standard Windows build is perfectly vanilla, and as
+         # of now is using MSVC 19.
+         ############################################################
+         - os: windows-latest
+           name: MSVC
+           cmake_command: "cmake ../.. -DCMAKE_BUILD_TYPE=Release"
+           build_command: "cmake --build . --config Release"
+           vers_command: "./tidy.exe --version"
+           test_command: "ruby test.rb test"
+
+         ############################################################
+         # We'll also build using MinGW on Windows, because it's
+         # always nice to support FOSS toolchains. While we could
+         # do this another way, we'll use the windows-2016 runner
+         # to distinguish it from the windows-latest runner.
+         ############################################################
+         - os: windows-2016
+           name: MinGW
+           cmake_command: "cmake ../.. -DCMAKE_BUILD_TYPE=Release -G 'MinGW Makefiles'"
+           build_command: "cmake --build . --config Release"
+           vers_command: "./tidy --version"
+           test_command: "ruby test.rb test"
+
+         ############################################################
+         # We'll also build using Cygwin on Windows, because even
+         # Windows people sometimes dislike Windows. While we could
+         # do this another way, we'll use the windows-2019 runner to
+         # distinguish it from the windows-latest runner.
+         # Note: only the `tidy` target will be built (without the
+         # man page) for this runner, because xltproc has issues
+         # loading files in the virtual environment. The man page
+         # is tested and builds perfectly fine on real installs.
+         ############################################################
+         - os: windows-2019
+           name: Cygwin
+           cmake_command: "cmake ../.. -DCMAKE_BUILD_TYPE=Release"
+           build_command: "cmake --build . --target tidy --config Release"
+           vers_command: "./tidy --version"
+           test_command: "ruby test.rb test"
+
+    steps:
+
+    ############################################################
+    # Checkput the repository.
+    ############################################################
+    - uses: actions/checkout@v2
+
+    ############################################################
+    # Install MinGW-w64 if needed for the current runner.
+    ############################################################
+    - name: Install MinGW-w64
+      if: ${{matrix.os == 'windows-2016'}}
+      uses: egor-tensin/setup-mingw@v2
+      with:
+        platform: x64
+
+    ############################################################
+    # Install Cygwin if needed for the current runner.
+    ############################################################
+    - name: Install Cygwin
+      if: ${{matrix.os == 'windows-2019'}}
+      uses: egor-tensin/setup-cygwin@v3
+      with:
+        platform: x64
+        packages: make gcc-core gcc-g++ cmake
+
+    ############################################################
+    # Cmake and Make the project.
+    ############################################################
+    - name: Build
+      working-directory: ${{github.workspace}}/build/cmake
+      run: |
+        ${{matrix.cmake_command}}
+        ${{matrix.build_command}}
+
+    ############################################################
+    # Windows MSVC is the only oddball here; why does it
+    # install the binary into a subfolder, unlike all of the
+    # other builds? Let's make everything else easier by
+    # relocating it to the same spot as all the other build
+    # locations.
+    ############################################################
+    - name: Move the MSVC exe to someplace sensible
+      if: ${{matrix.os == 'windows-latest'}}
+      run: |
+        move-item -path "${{github.workspace}}/build/cmake/Release/tidy.exe" -destination "${{github.workspace}}/build/cmake/"
+
+    ############################################################
+    # Just so that a human can make a quick sanity check.
+    ############################################################
+    - name: Show Version
+      working-directory: ${{github.workspace}}/build/cmake
+      run: |
+        ${{matrix.vers_command}}
+
+    ############################################################
+    # Install Ruby for running our regression tests. It's quite
+    # nice that this package is generic enough to work on all
+    # of the different runners.
+    ############################################################
+    - uses: ruby/setup-ruby@v1
+      with:
+        ruby-version: 2.7
+        bundler-cache: true
+
+    ############################################################
+    # Ensure that dependencies are met.
+    ############################################################
+    - name: Bundle Install
+      working-directory: ${{github.workspace}}/regression_testing
+      run: |
+        bundle install
+
+    ############################################################
+    # Finally, check for regressions.
+    ############################################################
+    - name: Run Regression Test
+      working-directory: ${{github.workspace}}/regression_testing
+      run: |
+        ${{matrix.test_command}}

.github/workflows/publish_linux+windows.yml

@@ -0,0 +1,211 @@
+################################################################################
+# Build Release Packages for Major Platforms 
+#
+#   - Builds release packages on multiple operating systems.
+#
+#   - Some packages may have to be supplemented with manually-built releases
+#     to account for code-signing and/or notarization requirements.
+#
+################################################################################
+
+name: Publish Linux+Windows
+
+on:
+  release:
+    types: [published]
+  workflow_dispatch:
+    inputs:
+      tag:
+        required: true
+        description: "Specify a ref (tag, branch, or sha) to build. If you specify a tag and a release exists, then artifacts will be attached to it."
+
+jobs:
+
+  publish_packages:
+    runs-on: ${{ matrix.os }}
+    strategy:
+      fail-fast: false
+      matrix:
+        include:
+
+         ############################################################
+         # Ubuntu latest is a normal build.
+         # Package building requires rpm in order to generate
+         # .rpm packages. The runner already includes this by
+         # default.
+         ############################################################
+         - os: ubuntu-latest
+           name: Standard
+           cmake_command: "cmake ../.. -DCMAKE_BUILD_TYPE=Release"
+           build_command: "cmake --build . --config Release --target package"
+           sha_command: "sha256sum"
+           stat_command: "stat"
+           artifacts: "tidy-%s-Linux-64bit.deb tidy-%s-Linux-64bit.rpm"
+
+
+         ############################################################
+         # We won't actually build macOS, because CMake is broken.
+         # We have a separate build script for macOS that's better
+         # than CMake's results anyway.
+         ############################################################
+         #- os: macOS-latest
+         #  name: X86_64 & Arm64
+         #  cmake_command: "cmake ../.. -DCMAKE_BUILD_TYPE=Release '-DCMAKE_OSX_ARCHITECTURES=x86_64;arm64'"
+         #  build_command: "cmake --build . --config Release --target package"
+         #  sha_command: "shasum -a 256"
+         #  stat_command: "gstat"
+         #  artifacts: "tidy-%s-macOS-x86_64+arm64.pkg"
+
+
+         ############################################################
+         # The standard Windows build is using MSVC 19 as of now.
+         # Package building requires nsis and wixtoolset, both of
+         # which can be installed via choco, which is already
+         # installed. Note: looks like wixtoolset is already
+         # installed.
+         ############################################################
+         - os: windows-latest
+           name: MSVC
+           cmake_command: "cmake ../.. -DCMAKE_BUILD_TYPE=Release"
+           build_command: "cmake --build . --config Release --target package"
+           sha_command: "sha256sum"
+           stat_command: "stat"
+           artifacts: "tidy-%s-win64.exe tidy-%s-win64.msi tidy-%s-win64.zip"
+                        
+
+    steps:
+
+
+    ############################################################
+    # Install Windows Pre-Requisites
+    ############################################################
+    - name: Install Windows Requirements
+      if: ${{matrix.os == 'windows-latest'}}
+      run: |
+        choco install nsis -y
+
+
+    ############################################################
+    # Install macOS Pre-Requisites
+    ############################################################
+    - name: Install macOS Requirements
+      if: ${{matrix.os == 'macOS-latest'}}
+      run: |
+        brew install coreutils
+
+
+    ############################################################
+    # Checkput the repository.
+    ############################################################
+    - name: Checkout Self
+      uses: actions/checkout@v2
+
+
+    ############################################################
+    # Get the version number. The output isn't available until
+    # we exit this step.
+    ############################################################
+    - name: Get Tidy Version
+      id: getversion
+      working-directory: ${{github.workspace}}
+      shell: bash
+      run: | 
+        echo "::set-output name=version::$(head -1 version.txt)"
+
+        
+    ############################################################
+    # Print the version number, which is now available from
+    # the previous step.
+    ############################################################
+    - name: Print Tidy Version
+      shell: bash
+      run: | 
+        echo "Tidy version is ${{ steps.getversion.outputs.version }}."
+    
+
+    ############################################################
+    # Configure and Build
+    ############################################################
+    - name: Configure and Build
+      working-directory: ${{github.workspace}}/build/cmake
+      shell: bash
+      run: |
+        ${{matrix.cmake_command}}
+        ${{matrix.build_command}}
+
+
+    ############################################################
+    # Move Files and Make Checksums
+    ############################################################
+    - name: Move Files and Make Checksums
+      working-directory: ${{github.workspace}}/build/cmake
+      shell: bash
+      run: |
+        ls -al
+        mkdir artifacts
+        array="${{matrix.artifacts}}"
+        for i in ${array[@]}; do
+          filename=$(printf "$i\n" ${{ steps.getversion.outputs.version }})
+          ${{matrix.sha_command}} "$filename" > "artifacts/${filename}.sha256"
+          mv "$filename" "artifacts/"
+        done
+
+
+    ############################################################
+    # Build Manifest Partials for binaries.html-tidy.org
+    ############################################################
+    - name: Build Manifest Partials
+      working-directory: ${{github.workspace}}/build/cmake/artifacts
+      shell: bash
+      run: |
+        ls -al
+        manifest="../binaries-partial.yml"
+        touch "${manifest}"
+        for filename in *.*[^sha256]; do
+            filesize=$(numfmt --to=si --suffix=B $(wc -c < ${filename}))
+            modified=$(${{matrix.stat_command}} -c %y "${filename}" | cut -d'.' -f1)
+            modified="${modified//-//}"
+            sha256=$(${{matrix.sha_command}} "${filename}" | awk '{print $1}')
+            echo "    - filename: ${filename}" >> "${manifest}"
+            echo "      filesize: ${filesize}" >> "${manifest}"
+            echo "      modified: ${modified}" >> "${manifest}"
+            echo "      describe: ''"          >> "${manifest}"
+            echo "      sha256: ${sha256}"     >> "${manifest}"
+            echo ""                            >> "${manifest}"
+        done;
+        cat "${manifest}"
+
+
+    ############################################################
+    # Release the artifacts (existing tag specified)
+    ############################################################
+    - name: Release to Existing Tag
+      if: ${{github.event.inputs.tag}}
+      uses: softprops/action-gh-release@v1
+      env:
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      with:
+        tag_name: "${{github.event.inputs.tag}}"
+        files: "${{github.workspace}}/build/cmake/artifacts/*"
+
+
+    ############################################################
+    # Release the artifacts (done via release)
+    ############################################################
+    - name: Release via Publish Release
+      if: ${{!github.event.inputs.tag}}
+      uses: softprops/action-gh-release@v1
+      env:
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      with:
+        files: "${{github.workspace}}/build/cmake/artifacts/*"
+
+
+    ############################################################
+    # Post the manifest to the run results.
+    ############################################################
+    - name: Post the Manifest
+      uses: actions/upload-artifact@v2
+      with:
+        name: "partials_for_website-${{matrix.os}}.yml"
+        path: ${{github.workspace}}/build/cmake/binaries-partial.yml

.github/workflows/publish_macos.yml

@@ -0,0 +1,135 @@
+################################################################################
+# Build a macOS Installer and Disk Image
+#
+# Although CMake generates macOS installers, it's kind of inflexible and sucks
+# a little bit. We can do better, as well as sign and notarize the image as
+# well. What's worse is, they're currently broken and don't work at all.
+################################################################################
+
+name: Publish macOS
+
+on:
+  release:
+    types: [published]
+  workflow_dispatch:
+    inputs:
+      tag:
+        required: true
+        description: "Specify a ref (tag, branch, or sha) to build. If you specify a tag and a release exists, then artifacts will be attached to it."
+
+jobs:
+
+  publish_packages:
+    runs-on: macOS-latest
+    env:
+        APPLE_DEVELOPER_ID_INSTALLER: ${{ secrets.APPLE_DEVELOPER_ID_INSTALLER }}
+        APPLE_DEVELOPER_ID_INSTALLER_PW: ${{ secrets.APPLE_DEVELOPER_ID_INSTALLER_PW }}
+        APPLE_DEVELOPER_ID_APPLICATION: ${{ secrets.APPLE_DEVELOPER_ID_APPLICATION }}
+        APPLE_DEVELOPER_ID_APPLICATION_PW: ${{ secrets.APPLE_DEVELOPER_ID_APPLICATION_PW }}
+        MACOS_PRODUCTSIGN_ID: ${{ secrets.APPLE_DEVELOPER_PRODUCTSIGN_ID }}
+        MACOS_CODESIGN_ID: ${{ secrets.APPLE_DEVELOPER_CODESIGN_ID }}
+        APPLE_ID: ${{ secrets.APPLE_ID }}
+        APPLE_APP_SPECIFIC_PASSWORD: ${{ secrets.APPLE_APP_SPECIFIC_PASSWORD }}
+    steps:
+
+
+    ############################################################
+    # Checkout the Tidy repository as tidy-html5.
+    #   If the user chooses a ref that doesn't exist, we
+    #   fail.
+    ############################################################
+    - name: Checkout this repository
+      uses: actions/checkout@v2
+      with:
+        path: ${{github.workspace}}/tidy-html5
+        ref: ${{github.event.inputs.tag}}
+
+
+    ############################################################
+    # Install Required Packages
+    ############################################################
+    - name: Install Requirements
+      shell: bash
+      run: | 
+        brew install ImageMagick
+        brew install libmagic
+        brew install create-dmg
+        brew install coreutils
+
+
+    ############################################################
+    # Checkout the Installer repository as tidy-mac-installer.
+    ############################################################
+    - name: Checkout tidy-mac-installer
+      uses: actions/checkout@v2
+      with:
+        repository: htacg/tidy-mac-installer
+        ref: master
+        path: ${{github.workspace}}/tidy-mac-installer
+
+
+    ############################################################
+    # Configure the environment for code-signing.
+    #   For local environment compatibility, we'll still
+    #   sign in the script; this just gives us the environment
+    #   on the runner.
+    ############################################################
+    - name: Codesign Setup
+      working-directory: ${{github.workspace}}/tidy-mac-installer
+      shell: bash
+      run: |
+        security create-keychain -p password1234 build.keychain 
+        security default-keychain -s build.keychain
+        security unlock-keychain -p password1234 build.keychain
+        echo "${APPLE_DEVELOPER_ID_INSTALLER}" | base64 --decode > "certificate.p12"
+        security import "certificate.p12" -k build.keychain -P ${APPLE_DEVELOPER_ID_INSTALLER_PW} -T /usr/bin/codesign -T /usr/bin/productsign
+        echo "${APPLE_DEVELOPER_ID_APPLICATION}" | base64 --decode > "certificate.p12"
+        security import "certificate.p12" -k build.keychain -P ${APPLE_DEVELOPER_ID_APPLICATION_PW} -T /usr/bin/codesign -T /usr/bin/productsign
+        security set-key-partition-list -S apple-tool:,apple:,codesign:,productsign: -s -k password1234 build.keychain
+
+
+    ############################################################
+    # Run the build script.
+    ############################################################
+    - name: Run the Build Script
+      id: build_script
+      working-directory: ${{github.workspace}}/tidy-mac-installer
+      shell: bash
+      run: | 
+        ./build_installer_image.sh
+
+
+    ############################################################
+    # Release the artifacts (existing tag specified)
+    ############################################################
+    - name: Release to Existing Tag
+      if: ${{github.event.inputs.tag}}
+      uses: softprops/action-gh-release@v1
+      env:
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      with:
+        tag_name: "${{github.event.inputs.tag}}"
+        files: "${{github.workspace}}/tidy-mac-installer/build/artifacts/*"
+
+
+    ############################################################
+    # Release the artifacts (done via release)
+    ############################################################
+    - name: Release via Publish Release
+      if: ${{!github.event.inputs.tag}}
+      uses: softprops/action-gh-release@v1
+      env:
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      with:
+        files: "${{github.workspace}}/tidy-mac-installer/build/artifacts/*"
+
+
+    ############################################################
+    # Post the manifest to the run results.
+    ############################################################
+    - name: Post the Dmg Artifact
+      uses: actions/upload-artifact@v2
+      with:
+        name: "partials_for_website-macos.yml"
+        path: "${{github.workspace}}/tidy-mac-installer/build/binaries-partial.yml"
+

.gitignore

@@ -6,6 +6,7 @@
 *.user
 *.suo
 *.sdf
+/test
 /test/testall.log
 /test/tmp/
 /test/tmp2/
@@ -15,3 +16,4 @@ temp*
 .DS_Store
 .idea
 *.old
+/regression_testing/cases/*-results/

CMakeLists.txt

@@ -1,32 +1,65 @@
-# CMakeLists.txt - 20150402 - 20150130 - 20140801 - for github htacg/tidy-html5
-# Prepare for changing the name to 'tidy'
-cmake_minimum_required (VERSION 2.8.8)
+##############################################################################
+# @file CMakeLists.txt
+# Build executables, static and dylibs, packages, build systems, etc., for
+# HTML Tidy.
+#
+# Read this file or use cmake-gui (Windows) or ccmake (everything else) for
+# guided build.
+#
+# @author  Geoff McLane [ubuntu@geoffair.info]
+# @author  HTACG, et al (consult git log)
+#
+# @copyright
+#          Copyright (c) 1998-2017 HTACG
+# @copyright
+#          See tidy.h for license.
+#
+# @date    Consult git log.
+##############################################################################
+
+cmake_minimum_required (VERSION 2.8.12)
 
 set(LIB_NAME tidy)
+set(LIBTIDY_DESCRIPTION "${LIB_NAME} - HTML syntax checker")
+set(LIBTIDY_URL "https://www.html-tidy.org")
 
 project (${LIB_NAME})
 
-# ### NOTE: *** Adjust version.txt when required ***
-# read 'version' file into a variable (stripping any newlines or spaces)
-# 20150609: Revert to supplying BOTH version and date, as we had back in Jan 2015
-# NOTE: Both version and date MUST be DOT separated, in two lines.
+
+#################################################
+# Setup
+#################################################
+
+#------------------------------------------------------------------------
+# Release Information
+#   Release version and date are found in `version.txt`; update *that*
+#   file when required. It will be read into variable `versionFile`
+#   (stripping any newlines or spaces). This file must be formatted into
+#   two lines: the dot-separated MAJOR.MINOR.POINT version, followed by
+#   the date separated YEAR.MONTH.DAY release date.
+#------------------------------------------------------------------------
 file(READ version.txt versionFile)
+
 if (NOT versionFile)
     message(FATAL_ERROR "Unable to determine libtidy version. version.txt file is missing.")
 endif()
+
 string(STRIP "${versionFile}" VERSION_TEXT)
 string(REGEX REPLACE "(.*)[\r\n|\n](.*)" "\\1" LIBTIDY_VERSION ${VERSION_TEXT})
 string(REGEX REPLACE "(.*)[\r\n|\n](.*)" "\\2" LIBTIDY_DATE ${VERSION_TEXT})
-# establish version number
+
+# Establish version number
 if (LIBTIDY_VERSION)
     string(REPLACE "." ";" VERSION_LIST ${LIBTIDY_VERSION})
     list(GET VERSION_LIST 0 TIDY_MAJOR_VERSION)
     list(GET VERSION_LIST 1 TIDY_MINOR_VERSION)
     list(GET VERSION_LIST 2 TIDY_POINT_VERSION)
+    set(TIDY_SO_VERSION "${TIDY_MAJOR_VERSION}${TIDY_MINOR_VERSION}")
 else ()
     message(FATAL_ERROR "*** FAILED to get a VERSION from version.txt!")
-endif ()    
-# establish version date
+endif ()   
+ 
+# Establish version date
 if (LIBTIDY_DATE)
     string(REPLACE "." ";" DATE_LIST ${LIBTIDY_DATE})
     list(GET DATE_LIST 0 tidy_YEAR)
@@ -36,16 +69,127 @@ else ()
     message(FATAL_ERROR "*** FAILED to get a DATE from version.txt!")
 endif ()
 
-# BY default, BOTH library types build, Allow turning OFF shared if not neede
-set( LIB_TYPE STATIC )  # set default static
-option( BUILD_SHARED_LIB "Set OFF to NOT build shared library"    ON  )
-option( BUILD_TAB2SPACE  "Set ON to build utility app, tab2space" OFF )
-option( BUILD_SAMPLE_CODE "Set ON to build the sample code"       OFF )
+# Establish SOVERSION. Tidy uses a weird form of semantic versioning,
+# wherein even minor versions are stable versions with SONAMEs, and
+# odd minor versions are `next` versions that should NOT be released,
+# are NOT stable, and should NOT have a valid SONAME.
+if (TIDY_SO_VERSION)
+    math(EXPR NO_SONAME "${TIDY_SO_VERSION} % 2")
+    if ( NO_SONAME EQUAL 0)
+        message("-> TIDY_SO_VERSION = ${TIDY_SO_VERSION}. This is an EVEN (stable) release.")
+    else ()
+        message("-> TIDY_SO_VERSION = ${TIDY_SO_VERSION}. This is an ODD (development) release.")
+    endif ()
+else ()
+    message(FATAL_ERROR "*** FAILED to build a TIDY_SO_VERSION!")
+endif ()
+
+
+#------------------------------------------------------------------------
+# Library Types and Linking
+#   By default, *both* static and dynamic library types are built. The
+#   shared library can be turned off if not needed. The console program
+#   can be configured for static linking or dynamic linking.
+#------------------------------------------------------------------------
+set( LIB_TYPE STATIC )  # set default message
+
+option( BUILD_SHARED_LIB "Set OFF to NOT build shared library"     ON  )
+
+# Issue #326 - Allow linkage choice of console app tidy
+option( TIDY_CONSOLE_SHARED "Set ON to link with shared(DLL) lib." OFF )
+
+if (TIDY_CONSOLE_SHARED)
+    if (NOT BUILD_SHARED_LIB)
+        message(FATAL_ERROR "Enable shared build for this tidy linkage!")
+    endif ()
+endif ()
+
+
+#------------------------------------------------------------------------
+# Miscellaneous Options
+#------------------------------------------------------------------------
+option( BUILD_TAB2SPACE     "Set ON to build utility app, tab2space"  OFF )
+option( BUILD_SAMPLE_CODE   "Set ON to build the sample code"         OFF )
+option( TIDY_COMPAT_HEADERS "Set ON to include compatibility headers" OFF )
+
+
+#------------------------------------------------------------------------
+# Man Page
+#   Allow building with non-default man page directory.
+#------------------------------------------------------------------------
 if (NOT MAN_INSTALL_DIR)
     set(MAN_INSTALL_DIR share/man/man1)
 endif ()
-option( BUILD_DOCUMENTATION "Set ON to build the documentation"   OFF )
 
+
+#------------------------------------------------------------------------
+# Localization
+#   Allow building without extra language support.
+#------------------------------------------------------------------------
+option( SUPPORT_LOCALIZATIONS "Set OFF to build without additional languages." ON )
+
+if (SUPPORT_LOCALIZATIONS)
+    add_definitions ( -DSUPPORT_LOCALIZATIONS=1 )
+else ()
+    add_definitions ( -DSUPPORT_LOCALIZATIONS=0 )
+endif ()
+
+
+#------------------------------------------------------------------------
+# Console Application
+#   Allow building without console support, which mostly prevents
+#   console strings from existing in the library. Note that this will
+#   prevent the console application from being built, since it can't be
+#   linked.
+#------------------------------------------------------------------------
+option( SUPPORT_CONSOLE_APP "Set OFF to build libraries only without console application support." ON )
+
+if (SUPPORT_CONSOLE_APP)
+    add_definitions ( -DSUPPORT_CONSOLE_APP=1 )
+else ()
+    add_definitions ( -DSUPPORT_CONSOLE_APP=0 )
+endif ()
+
+
+#------------------------------------------------------------------------
+# Diagnostics
+#   Enable building with logs, some memory diagnostics.
+#------------------------------------------------------------------------
+option( ENABLE_DEBUG_LOG    "Set ON to output debugging messages."          OFF )
+option( ENABLE_ALLOC_DEBUG  "Set ON to output node allocation diagnostics." OFF )
+option( ENABLE_MEMORY_DEBUG "Set ON to output some memory diagnostics."     OFF )
+
+if ( ENABLE_DEBUG_LOG )
+    add_definitions( -DENABLE_DEBUG_LOG )
+    message(STATUS "*** Debug Logging is enabled.")  
+else ()
+    message(STATUS "*** Debug Logging is NOT enabled.")  
+endif ()
+
+if (ENABLE_ALLOC_DEBUG)
+    add_definitions ( -DDEBUG_ALLOCATION )  # see lexer.c for details
+    message(STATUS "*** Note, lexer.c node allocation diagnostics are ON")
+endif ()
+    
+if (ENABLE_MEMORY_DEBUG)
+    add_definitions ( -DDEBUG_MEMORY )  # see alloc.c for details
+    message(STATUS "*** Note, alloc.c memory diagnostics are ON")
+endif ()
+    
+if (WIN32)
+    option( ENABLE_CRTDBG_MEMORY "Set ON to enable the Windows CRT debug library." OFF )
+    
+    if (ENABLE_CRTDBG_MEMORY)
+        add_definitions ( -D_CRTDBG_MAP_ALLOC )  # see tidy.c for details
+        message(STATUS "*** Note, tidy.c Windows CRT memory debug is ON")
+    endif ()
+endif ()
+
+
+#------------------------------------------------------------------------
+# Complier Flags
+#   Setup other compiler-specific and platform-specific compiler flags.
+#------------------------------------------------------------------------
 if(CMAKE_COMPILER_IS_GNUCXX)
     set( WARNING_FLAGS -Wall )
 endif(CMAKE_COMPILER_IS_GNUCXX)
@@ -55,20 +199,16 @@ if (CMAKE_CXX_COMPILER_ID STREQUAL "Clang")
 endif() 
 
 if(WIN32 AND MSVC)
-    # turn off various warnings
-    set(WARNING_FLAGS "${WARNING_FLAGS} /wd4996")
+    # C4996: The compiler encountered a deprecated declaration.
     # C4090: 'function' : different 'const' qualifiers
     # C4244: '=' : conversion from '__int64' to 'uint', possible loss of data
     # C4267: 'function' : conversion from 'size_t' to 'uint', possible loss of data
-    # foreach(warning 4244 4251 4267 4275 4290 4786 4305)
-    foreach(warning 4090 4244 4267)
+    foreach(warning 4996 4090 4244 4267)
         set(WARNING_FLAGS "${WARNING_FLAGS} /wd${warning}")
     endforeach()
+    
     set( MSVC_FLAGS "-DNOMINMAX -D_USE_MATH_DEFINES -D_CRT_SECURE_NO_WARNINGS -D_SCL_SECURE_NO_WARNINGS -D__CRT_NONSTDC_NO_WARNINGS" )
-    # if (${MSVC_VERSION} EQUAL 1600)
-    #    set( MSVC_LD_FLAGS "/FORCE:MULTIPLE" )
-    # endif (${MSVC_VERSION} EQUAL 1600)
-    # set( NOMINMAX 1 )
+
     # to distinguish between debug and release lib in windows
     set( CMAKE_DEBUG_POSTFIX "d" ) # little effect in unix
 else()
@@ -79,25 +219,113 @@ set( CMAKE_C_FLAGS "${CMAKE_C_FLAGS} ${WARNING_FLAGS} ${MSVC_FLAGS} -D_REENTRANT
 set( CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} ${WARNING_FLAGS} ${MSVC_FLAGS} -D_REENTRANT" )
 set( CMAKE_EXE_LINKER_FLAGS "${CMAKE_EXE_LINKER_FLAGS} ${MSVC_LD_FLAGS}" )
 
-add_definitions ( -DHAVE_CONFIG_H )
-add_definitions ( -DSUPPORT_UTF16_ENCODINGS=1 )
-add_definitions ( -DSUPPORT_ASIAN_ENCODINGS=1 )
-add_definitions ( -DSUPPORT_ACCESSIBILITY_CHECKS=1 )
+
+#------------------------------------------------------------------------
+# Static Windows Runtime
+#   Option to statically link to the Windows runtime. Maybe only 
+#   applies to WIN32/MSVC.
+#------------------------------------------------------------------------
+if (MSVC)
+    option( USE_STATIC_RUNTIME "Set ON to change /MD(DLL) to /MT(static)" OFF )
+    if (USE_STATIC_RUNTIME)
+        set(CompilerFlags
+            CMAKE_CXX_FLAGS
+            CMAKE_CXX_FLAGS_DEBUG
+            CMAKE_CXX_FLAGS_RELEASE
+            CMAKE_C_FLAGS
+            CMAKE_C_FLAGS_DEBUG
+            CMAKE_C_FLAGS_RELEASE
+            )
+        foreach(CompilerFlag ${CompilerFlags})
+            string(REPLACE "/MD" "/MT" ${CompilerFlag} "${${CompilerFlag}}")
+        endforeach()    
+        message(STATUS "Using /MT STATIC runtime")
+    else ()
+        message(STATUS "Using /MD DYNAMIC runtime")
+    endif ()
+endif ()
+
+
+#------------------------------------------------------------------------
+# Macro Values
+#   These additional macros are set in Tidy's source code. It is *very*
+#   seldom that you would ever have to change any of these in order to
+#   achieve a functioning build.
+#------------------------------------------------------------------------
 add_definitions ( -DLIBTIDY_VERSION="${LIBTIDY_VERSION}" )
 add_definitions ( -DRELEASE_DATE="${tidy_YEAR}/${tidy_MONTH}/${tidy_DAY}" )
-add_definitions ( -DRC_NUMBER="RC1" )
 
-# Issue #188 - Support user items in platform.h
-if (TIDY_CONFIG_FILE)
-    add_definitions( -DTIDY_CONFIG_FILE="${TIDY_CONFIG_FILE}" )
+# Optionally specify an extra version point for pre-release/debug versions.
+if (TIDY_RC_NUMBER)
+    add_definitions ( -DRC_NUMBER="${TIDY_RC_NUMBER}" )
 endif ()
-if (TIDY_USER_CONFIG_FILE)
-    add_definitions( -DTIDY_USER_CONFIG_FILE="${TIDY_USER_CONFIG_FILE}" )
+
+# If your OS doesn't have native ISO2022 support, then build with this flag.
+if (NO_NATIVE_ISO2022_SUPPORT)
+    add_definitions ( -DNO_NATIVE_ISO2022_SUPPORT=1 )
 endif ()
-if (SUPPORT_GETPWNAM)
+
+# If your OS doesn't have library function access(), build with this flag.
+if (NO_ACCESS_SUPPORT)
+    add_definitions ( -DNO_ACCESS_SUPPORT=1 )
+endif ()
+
+# Delete me? Not used in Tidy source!
+add_definitions ( -DHAVE_CONFIG_H ) 
+
+
+#------------------------------------------------------------------------
+# Runtime Configuration File Support
+#   By default on Unix-like systems when building for the console program,
+#   support runtime configuration files in /etc/ and in ~/. To prevent this,
+#   set ENABLE_CONFIG_FILES to NO. Specify -DTIDY_CONFIG_FILE and/or 
+#   -DTIDY_USER_CONFIG_FILE to override the default paths in tidyplatform.h.
+# @note: this section refactored to support #584.
+#------------------------------------------------------------------------
+if ( UNIX AND SUPPORT_CONSOLE_APP )
+
+  option ( ENABLE_CONFIG_FILES "Set to OFF to disable Tidy runtime configuration file support" ON )
+
+    # All Unixes support getpwnam(); undef'd in tidyplatform.h if necessary.
     add_definitions( -DSUPPORT_GETPWNAM=1 )
+
+else ()
+
+  option ( ENABLE_CONFIG_FILES "Set to ON to enable Tidy runtime configuration file support" OFF )
+  
+  if ( SUPPORT_GETPWNAM )
+    add_definitions( -DSUPPORT_GETPWNAM=1 )
+  endif ()
+  
 endif ()
 
+if ( ENABLE_CONFIG_FILES )
+
+    message(STATUS "*** Building support for runtime configuration files.")
+
+    add_definitions( -DTIDY_ENABLE_CONFIG_FILES )
+    
+    # define a default here so we can pass to XSL.
+    if ( NOT TIDY_CONFIG_FILE )
+        set( TIDY_CONFIG_FILE "/etc/tidy.conf" )
+    endif ()
+
+    # define a default here so we can pass to XSL.
+    if ( NOT TIDY_USER_CONFIG_FILE )
+        set( TIDY_USER_CONFIG_FILE "~/.tidyrc" )
+    endif ()
+
+    # do *not* add these unless ENABLE_CONFIG_FILES!
+    add_definitions( -DTIDY_CONFIG_FILE="${TIDY_CONFIG_FILE}" )
+    add_definitions( -DTIDY_USER_CONFIG_FILE="${TIDY_USER_CONFIG_FILE}" )
+
+endif ()
+  
+
+#------------------------------------------------------------------------
+# Shared Library
+#   Setup whether or not we will build the shared library.
+#------------------------------------------------------------------------
 if(BUILD_SHARED_LIB)
    set(LIB_TYPE SHARED)
    message(STATUS "*** Also building DLL library ${LIB_TYPE}, version ${LIBTIDY_VERSION}, date ${LIBTIDY_DATE}")
@@ -105,26 +333,39 @@ else()
    message(STATUS "*** Only building static library ${LIB_TYPE}, version ${LIBTIDY_VERSION}, date ${LIBTIDY_DATE}")
 endif()
 
+
+#################################################
+# Build
+#################################################
+
+#------------------------------------------------------------------------
+# File Locations and File Lists
+#   Setup whether or not we will build the shared library.
+#------------------------------------------------------------------------
 include_directories ( "${PROJECT_SOURCE_DIR}/include" "${PROJECT_SOURCE_DIR}/src" )
 
-##############################################################################
-### tidy library
-# file locations
 set ( SRCDIR src )
 set ( INCDIR include )
-# file lists
+
 set ( CFILES
         ${SRCDIR}/access.c       ${SRCDIR}/attrs.c        ${SRCDIR}/istack.c
         ${SRCDIR}/parser.c       ${SRCDIR}/tags.c         ${SRCDIR}/entities.c
-        ${SRCDIR}/lexer.c        ${SRCDIR}/pprint.c       ${SRCDIR}/charsets.c ${SRCDIR}/clean.c
-        ${SRCDIR}/localize.c     ${SRCDIR}/config.c       ${SRCDIR}/alloc.c
-        ${SRCDIR}/attrask.c      ${SRCDIR}/attrdict.c     ${SRCDIR}/attrget.c
-        ${SRCDIR}/buffio.c       ${SRCDIR}/fileio.c       ${SRCDIR}/streamio.c
-        ${SRCDIR}/tagask.c       ${SRCDIR}/tmbstr.c       ${SRCDIR}/utf8.c
-        ${SRCDIR}/tidylib.c      ${SRCDIR}/mappedio.c     ${SRCDIR}/gdoc.c )
+        ${SRCDIR}/lexer.c        ${SRCDIR}/pprint.c       ${SRCDIR}/charsets.c
+        ${SRCDIR}/clean.c        ${SRCDIR}/message.c      ${SRCDIR}/config.c
+        ${SRCDIR}/alloc.c        ${SRCDIR}/attrdict.c     ${SRCDIR}/buffio.c
+        ${SRCDIR}/fileio.c       ${SRCDIR}/streamio.c     ${SRCDIR}/tagask.c
+        ${SRCDIR}/tmbstr.c       ${SRCDIR}/utf8.c         ${SRCDIR}/tidylib.c
+        ${SRCDIR}/mappedio.c     ${SRCDIR}/gdoc.c         ${SRCDIR}/language.c
+        ${SRCDIR}/messageobj.c   ${SRCDIR}/sprtf.c )
+        
 set ( HFILES
         ${INCDIR}/tidyplatform.h ${INCDIR}/tidy.h         ${INCDIR}/tidyenum.h
         ${INCDIR}/tidybuffio.h )
+
+if (TIDY_COMPAT_HEADERS)
+    set ( HFILES ${HFILES}      ${INCDIR}/buffio.h        ${INCDIR}/platform.h )
+endif ()
+
 set ( LIBHFILES
         ${SRCDIR}/access.h       ${SRCDIR}/attrs.h        ${SRCDIR}/attrdict.h ${SRCDIR}/charsets.h
         ${SRCDIR}/clean.h        ${SRCDIR}/config.h       ${SRCDIR}/entities.h
@@ -132,64 +373,121 @@ set ( LIBHFILES
         ${SRCDIR}/mappedio.h     ${SRCDIR}/message.h      ${SRCDIR}/parser.h
         ${SRCDIR}/pprint.h       ${SRCDIR}/streamio.h     ${SRCDIR}/tags.h
         ${SRCDIR}/tmbstr.h       ${SRCDIR}/utf8.h         ${SRCDIR}/tidy-int.h
-        ${SRCDIR}/version.h      ${SRCDIR}/gdoc.h  )
-if (MSVC)
-    list(APPEND CFILES ${SRCDIR}/sprtf.c)
-    list(APPEND LIBHFILES ${SRCDIR}/sprtf.h)
+        ${SRCDIR}/version.h      ${SRCDIR}/gdoc.h         ${SRCDIR}/language.h
+        ${SRCDIR}/language_en.h  ${SRCDIR}/sprtf.h )
+  
+
+#------------------------------------------------------------------------
+# Target Locations
+#------------------------------------------------------------------------
+if (NOT LIB_INSTALL_DIR)
+    set(LIB_INSTALL_DIR lib${LIB_SUFFIX})
 endif ()
-#######################################
-# Always build the STATIC library
+
+if (NOT BIN_INSTALL_DIR)
+    set(BIN_INSTALL_DIR bin)
+endif ()
+
+if (NOT INCLUDE_INSTALL_DIR)
+    set(INCLUDE_INSTALL_DIR include)
+endif ()
+
+
+#------------------------------------------------------------------------
+# Static Library
+#   The static library always builds.
+#------------------------------------------------------------------------
 set(name tidy-static)
 add_library ( ${name} STATIC ${CFILES} ${HFILES} ${LIBHFILES} )
-set_target_properties( ${name} PROPERTIES 
-    OUTPUT_NAME ${LIB_NAME}s
-    )
-list ( APPEND add_LIBS ${name} )
+if (WIN32)
+    set_target_properties( ${name} PROPERTIES 
+                           OUTPUT_NAME ${LIB_NAME}_static ) 
+else ()
+    set_target_properties( ${name} PROPERTIES 
+                           OUTPUT_NAME ${LIB_NAME} )
+
+endif ()
+if (NOT TIDY_CONSOLE_SHARED) # user wants default static linkage
+    list ( APPEND add_LIBS ${name} )
+endif ()    
 install(TARGETS ${name}
-        RUNTIME DESTINATION bin
-        ARCHIVE DESTINATION lib
-        LIBRARY DESTINATION lib
+        RUNTIME DESTINATION ${BIN_INSTALL_DIR}
+        ARCHIVE DESTINATION ${LIB_INSTALL_DIR}
+        LIBRARY DESTINATION ${LIB_INSTALL_DIR}
         )
-install( FILES ${HFILES} DESTINATION include )
-########################################
-# if user option still on
+install( FILES ${HFILES} DESTINATION ${INCLUDE_INSTALL_DIR} )
+
+#------------------------------------------------------------------------
+# Dynamic Library
+#   If the user option is still on.
+#------------------------------------------------------------------------
 if (BUILD_SHARED_LIB)
     set(name tidy-share)
+    if (UNIX AND APPLE)
+        set(CMAKE_MACOSX_RPATH 1)
+    endif ()
     add_library ( ${name} SHARED ${CFILES} ${HFILES} ${LIBHFILES} )
     set_target_properties( ${name} PROPERTIES 
-                                    OUTPUT_NAME ${LIB_NAME} )
+                                   OUTPUT_NAME ${LIB_NAME} )
     set_target_properties( ${name} PROPERTIES
                                    VERSION   ${LIBTIDY_VERSION}
-                                   SOVERSION ${TIDY_MAJOR_VERSION} )
+                                   SOVERSION ${TIDY_SO_VERSION}
+                                   NO_SONAME ${NO_SONAME} )
     set_target_properties( ${name} PROPERTIES 
-                                   COMPILE_FLAGS "-DBUILD_SHARED_LIB" )
-    set_target_properties( ${name} PROPERTIES 
-                                   COMPILE_FLAGS "-DBUILDING_SHARED_LIB" )
+                                   COMPILE_FLAGS "-DBUILD_SHARED_LIB -DBUILDING_SHARED_LIB")
     install(TARGETS ${name}
-        RUNTIME DESTINATION bin
-        ARCHIVE DESTINATION lib
-        LIBRARY DESTINATION lib
+        RUNTIME DESTINATION ${BIN_INSTALL_DIR}
+        ARCHIVE DESTINATION ${LIB_INSTALL_DIR}
+        LIBRARY DESTINATION ${LIB_INSTALL_DIR}
         )
-endif ()                               
-
-##########################################################
-### main executable - linked with STATIC library
-set(name ${LIB_NAME})
-set ( BINDIR console )
-add_executable( ${name} ${BINDIR}/tidy.c )
-target_link_libraries( ${name} ${add_LIBS} )
-if (MSVC)
-    set_target_properties( ${name} PROPERTIES DEBUG_POSTFIX d )
+    if(MSVC)
+        install(FILES $<TARGET_PDB_FILE:tidy-share> DESTINATION ${LIB_INSTALL_DIR} OPTIONAL)
+    endif()
+    if (TIDY_CONSOLE_SHARED) # user wants shared/dll linkage
+        list ( APPEND add_LIBS ${name} )
+    endif ()    
 endif ()
-install (TARGETS ${name} DESTINATION bin)
 
+
+#------------------------------------------------------------------------
+# Main Executable
+#   The main executable will be linked with either the static or the
+#   shared library.
+#------------------------------------------------------------------------
+if (SUPPORT_CONSOLE_APP)
+    set(name ${LIB_NAME})
+    set ( BINDIR console )
+    add_executable( ${name} ${BINDIR}/tidy.c )
+    target_link_libraries( ${name} ${add_LIBS} )
+    if (MSVC)
+        set_target_properties( ${name} PROPERTIES DEBUG_POSTFIX d )
+    endif ()
+    if (APPLE)
+        string(TIMESTAMP CURRENT_YEAR "%Y")
+        configure_file(
+            ${CMAKE_CURRENT_SOURCE_DIR}/console/Info.plist.in 
+            ${CMAKE_CURRENT_BINARY_DIR}/Info.plist
+        )
+        target_link_options(${name} PRIVATE LINKER:-sectcreate,__TEXT,__info_plist,Info.plist)
+    endif ()
+    if (NOT TIDY_CONSOLE_SHARED)
+        set_target_properties( ${name} PROPERTIES 
+                                       COMPILE_FLAGS "-DTIDY_STATIC" )
+    endif ()
+    install (TARGETS ${name} DESTINATION bin)
+endif ()
+
+
+#------------------------------------------------------------------------
+# Miscellaneous Targets
+#------------------------------------------------------------------------
 if (BUILD_TAB2SPACE)
     set(name tab2space)
     add_executable( ${name} ${BINDIR}/tab2space.c )
     if (MSVC)
         set_target_properties( ${name} PROPERTIES DEBUG_POSTFIX d )
     endif ()
-    # no INSTALL of this 'local' tool
+    # no INSTALL of this 'local' tool - use depreciated
 endif ()
 
 if (BUILD_SAMPLE_CODE)
@@ -203,136 +501,117 @@ if (BUILD_SAMPLE_CODE)
     # no INSTALL of this 'local' sample
 endif ()
 
-#==========================================================
+
+#################################################
 # Create man pages
-#==========================================================
-if (UNIX)
+#################################################
+
+if (UNIX AND SUPPORT_CONSOLE_APP)
     find_program( XSLTPROC_FOUND xsltproc )
     if (XSLTPROC_FOUND)
         ## NOTE: man name must match exe ie currently `${LIB_NAME}.1` not `tidy.1`
         ## also could use `manpath` command output to determine target install path
         set(TIDY_MANFILE ${LIB_NAME}.1)
         message(STATUS "*** Generating man ${TIDY_MANFILE} custom commands...")
-        set(TIDY1XSL ${CMAKE_SOURCE_DIR}/build/documentation/tidy1.xsl)
-        set(TIDYHELP ${CMAKE_BINARY_DIR}/tidy-help.xml)
-        set(TIDYCONFIG ${CMAKE_BINARY_DIR}/tidy-config.xml)
-        add_custom_target(man ALL DEPENDS "${CMAKE_BINARY_DIR}/${LIB_NAME}")
+        set(TIDY1XSL ${CMAKE_CURRENT_BINARY_DIR}/tidy1.xsl)
+        set(TIDYHELP ${CMAKE_CURRENT_BINARY_DIR}/tidy-help.xml)
+        set(TIDYCONFIG ${CMAKE_CURRENT_BINARY_DIR}/tidy-config.xml)
+        add_custom_target(man ALL DEPENDS "${CMAKE_CURRENT_BINARY_DIR}/${LIB_NAME}")
+        
+        ## Populate the @VARIABLES@ in the input file.
+        configure_file(
+            ${CMAKE_CURRENT_SOURCE_DIR}/man/tidy1.xsl.in
+            ${TIDY1XSL}
+        )
  
-        # run built EXE to generate xml output 
+        # Run the built EXE to generate xml output .
         add_custom_command(
             TARGET man
-            COMMAND ${CMAKE_BINARY_DIR}/${LIB_NAME} -xml-help > ${TIDYHELP}
+            COMMAND ${CMAKE_CURRENT_BINARY_DIR}/${LIB_NAME} -xml-help > ${TIDYHELP}
             COMMENT "Generate ${TIDYHELP}"
             VERBATIM
         )
 
-        # run built EXE to generate more xml output 
+        # Run the built EXE to generate more xml output.
         add_custom_command(
             TARGET man
-            COMMAND ${CMAKE_BINARY_DIR}/${LIB_NAME} -xml-config > ${TIDYCONFIG}
+            COMMAND ${CMAKE_CURRENT_BINARY_DIR}/${LIB_NAME} -xml-config > ${TIDYCONFIG}
             COMMENT "Generate ${TIDYCONFIG}"
             VERBATIM
         )
 
-        # run xsltproc to generate the install files..
+        # Run xsltproc to generate the install files.
         add_custom_command(
             TARGET man
             DEPENDS ${TIDYHELP}
-            COMMAND xsltproc ARGS ${TIDY1XSL} ${TIDYHELP} > ${CMAKE_BINARY_DIR}/${TIDY_MANFILE}
+            COMMAND xsltproc ARGS ${TIDY1XSL} ${TIDYHELP} > ${CMAKE_CURRENT_BINARY_DIR}/${TIDY_MANFILE}
             COMMENT "Generate ${TIDY_MANFILE}"
             VERBATIM
         )
 
-        install(FILES ${CMAKE_BINARY_DIR}/${TIDY_MANFILE} DESTINATION ${MAN_INSTALL_DIR})
-        
-        if (BUILD_DOCUMENTATION)
-            find_program( DOXYGEN_FOUND doxygen )
-            if (DOXYGEN_FOUND)
-                set( WRK_DIR ${CMAKE_SOURCE_DIR}/documentation )
-                set( EXP_DIR ${WRK_DIR}/examples )
-                set( OUT_DIR ${WRK_DIR}/temp )
-                set( DXY_DIR ${WRK_DIR}/temp/tidylib_api )
-                set( DXY_CFG ${WRK_DIR}/temp_doxygen.cfg )
-                file( READ ${WRK_DIR}/doxygen.cfg PARAMS )
-                set( PARAMS "${PARAMS}PROJECT_NUMBER=${LIBTIDY_VERSION}\n" )
-                set( PARAMS "${PARAMS}GENERATE_TAGFILE=${DXY_DIR}/tidy.tags\n" )
-                set( PARAMS "${PARAMS}HTML_EXTRA_FILES=${EXP_DIR}/tidy5.help.txt ${EXP_DIR}/tidy5.config.txt\n" )    
-                set( PARAMS "${PARAMS}# eof\n" )
-                file( WRITE ${DXY_CFG} ${PARAMS} )
-                file( MAKE_DIRECTORY ${OUT_DIR} )
-                add_custom_target( documentation ALL )
-                #=========================================
-                # Generate files.
-                #=========================================
-                add_custom_command(
-                    TARGET documentation
-                    COMMENT "Build Documentation"
-                    VERBATIM
-                    WORKING_DIRECTORY ${WRK_DIR}
-                    COMMAND xsltproc ARGS quickref.xsl ${TIDYCONFIG} > ${OUT_DIR}/quickref.html
-                    COMMAND xsltproc ARGS quickref.include.xsl ${TIDYCONFIG} > ${EXP_DIR}/quickref_include.html # delete later
-                    COMMAND ${CMAKE_BINARY_DIR}/${LIB_NAME} -h > ${EXP_DIR}/tidy5.help.txt # delete later
-                    COMMAND ${CMAKE_BINARY_DIR}/${LIB_NAME} -help-config > ${EXP_DIR}/tidy5.config.txt   # delete later
-                    COMMAND cp ARGS ../LICENSE.md ${EXP_DIR}  # delete later
-                    )
-                #=========================================
-                # Run Doxygen.
-                #=========================================
-                add_custom_command(
-                    TARGET documentation
-                    COMMENT "Run Doxygen"
-                    VERBATIM
-                    WORKING_DIRECTORY ${WRK_DIR}
-                    COMMAND cat ${DXY_CFG} | doxygen - > /dev/null      
-                    )
-                #=========================================
-                # Cleanup.
-                #=========================================
-                add_custom_command(
-                    TARGET documentation
-                    COMMENT "Cleanup"
-                    VERBATIM
-                    WORKING_DIRECTORY ${WRK_DIR}
-                    COMMAND rm ${EXP_DIR}/quickref_include.html
-                    COMMAND rm ${EXP_DIR}/tidy5.help.txt
-                    COMMAND rm ${EXP_DIR}/tidy5.config.txt
-                    COMMAND rm ${EXP_DIR}/LICENSE.md
-                    )
-                install(CODE "MESSAGE(\"Build output can be found in ${OUT_DIR}.\")")
-            else ()
-                message(STATUS "*** NOTE: doxygen NOT FOUND! Can NOT generate documentation.")
-            endif ()
-        endif ()
+        install(FILES ${CMAKE_CURRENT_BINARY_DIR}/${TIDY_MANFILE} DESTINATION ${MAN_INSTALL_DIR})
+
     else ()
         message(STATUS "*** NOTE: xsltproc NOT FOUND! Can NOT generate man page.")
         message(STATUS "*** You need to install xsltproc in your system.")
     endif ()
 endif ()
 
-##########################################################
-### Create MSI,EXE, DMG, DEB/RPM
-### TODO: Check each of these builds
-##########################################################
+
+#################################################
+# Create MSI,EXE, DMG, DEB/RPM
+#   TODO: Check each of these builds
+#################################################
+
 set(BITNESS 32)
 if(CMAKE_SIZEOF_VOID_P EQUAL 8)
   set(BITNESS 64)
 endif()
+
+
+#------------------------------------------------------------------------
+# System Runtime Libraries
+#   Need to ensure that system DLLs get included in a binary 
+#   distribution, but since it can miss some - seems incomplete - make
+#   optional.
+#------------------------------------------------------------------------
+option( ADD_SYSTEM_RUNTIMES "Set ON to include system runtime DLLS in distribution" OFF )
+if (MSVC AND ADD_SYSTEM_RUNTIMES)
+    if (NOT DEFINED CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_NO_WARNINGS)
+      # Visual Studio Express does include redistributable components so
+      # squelch the warning.
+      set (CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_NO_WARNINGS ON)
+    endif ()
+    set (CMAKE_INSTALL_DEBUG_LIBRARIES OFF)
+    include (InstallRequiredSystemLibraries)
+endif ()
+
+
+#------------------------------------------------------------------------
+# Windows
+#   MSI - this needs WiX Tooset installed and a path to candle.exe
+#   EXE - this needs NSIS tools to be in path
+# Everything Else
+#   RPM required to build RPM's, and might not be installed by default.
+#------------------------------------------------------------------------
 if (WIN32)
-    # MSI - this needs WiX Tooset installed and a path to candle.exe
-    # EXE - this needs NSIS tools to be in path
     set(CPACK_GENERATOR "NSIS;WIX;ZIP")
     set(CPACK_SOURCE_GENERATOR "ZIP")
     set(CPACK_WIX_UPGRADE_GUID "D809598A-B513-4752-B268-0BAC403B00E4")
 elseif ( ${CMAKE_SYSTEM_NAME} MATCHES "Darwin" )
-    set(CPACK_GENERATOR "PackageMake")
+    set(CPACK_GENERATOR "productbuild")
     set(CPACK_SOURCE_GENERATOR "TGZ")
 else ()
     set(CPACK_GENERATOR "DEB;RPM")
     set(CPACK_SOURCE_GENERATOR "TGZ")
 endif ()
 
+
+#------------------------------------------------------------------------
+# General
+#------------------------------------------------------------------------
 set(CPACK_PACKAGE_NAME "${LIB_NAME}")
-set(CPACK_PACKAGE_DESCRIPTION_SUMMARY "${LIB_NAME} - HTML syntax checker")
+set(CPACK_PACKAGE_DESCRIPTION_SUMMARY "${LIBTIDY_DESCRIPTION}")
 set(CPACK_PACKAGE_VENDOR "HTML Tidy Advocacy Community Group")
 set(CPACK_PACKAGE_CONTACT "maintainer@htacg.org")
 
@@ -340,24 +619,83 @@ set(CPACK_PACKAGE_VERSION ${LIBTIDY_VERSION})
 set(CPACK_PACKAGE_VERSION_MAJOR "${TIDY_MAJOR_VERSION}")
 set(CPACK_PACKAGE_VERSION_MINOR "${TIDY_MINOR_VERSION}")
 set(CPACK_PACKAGE_VERSION_PATCH "${TIDY_POINT_VERSION}")
-set(CPACK_PACKAGE_DESCRIPTION_FILE "${CMAKE_SOURCE_DIR}/README.html")
+set(CPACK_PACKAGE_DESCRIPTION_FILE "${CMAKE_CURRENT_SOURCE_DIR}/README/README.html")
 
-set(CPACK_RESOURCE_FILE_LICENSE "${CMAKE_SOURCE_DIR}/LICENSE.txt")
-set(CPACK_RESOURCE_FILE_README "${CMAKE_SOURCE_DIR}/README.html")
-set(CPACK_RESOURCE_FILE_WELCOME "${CMAKE_SOURCE_DIR}/README.html")
 
-## debian config
-set(CPACK_DEBIAN_PACKAGE_MAINTAINER ${CPACK_PACKAGE_CONTACT})
-set(CPACK_DEBIAN_PACKAGE_HOMEPAGE "http://www.html-tidy.org/")
-#set(CPACK_DEBIAN_PACKAGE_DEPENDS "libc")
-set(CPACK_DEBIAN_PACKAGE_SECTION "Libraries")
-
-set(CPACK_SOURCE_IGNORE_FILES "${CMAKE_SOURCE_DIR}/test/;${CMAKE_SOURCE_DIR}/build/;${CMAKE_SOURCE_DIR}/.git/")
-
-if (NOT WIN32 AND NOT APPLE)
-set( CPACK_PACKAGE_FILE_NAME "${LIB_NAME}-${CPACK_PACKAGE_VERSION}-${BITNESS}bit" )
+#------------------------------------------------------------------------
+# Windows: it looks like only the LICENSE.txt file is used by Windows,
+#   for either package type (.exe and .msi).
+# Linux: none of the files are shown publicly by default when installing
+#   from a .deb or .rpm.
+# Mac: cannot show HTML; need RTF. CPACK_RESOURCE_FILE_WELCOME isn't
+#   needed.
+#------------------------------------------------------------------------
+if (APPLE)
+    set(CPACK_RESOURCE_FILE_LICENSE "${CMAKE_CURRENT_SOURCE_DIR}/build/macos/Installer-License.rtf")
+    set(CPACK_RESOURCE_FILE_README "${CMAKE_CURRENT_SOURCE_DIR}/build/macos/Installer-Introduction.rtf")
+else ()
+    set(CPACK_RESOURCE_FILE_LICENSE "${CMAKE_CURRENT_SOURCE_DIR}/README/LICENSE.txt")
+    set(CPACK_RESOURCE_FILE_README "${CMAKE_CURRENT_SOURCE_DIR}/README/README.html")
+    set(CPACK_RESOURCE_FILE_WELCOME "${CMAKE_CURRENT_SOURCE_DIR}/README/README.html")
 endif ()
 
+
+#------------------------------------------------------------------------
+# Debian
+#------------------------------------------------------------------------
+set(CPACK_DEBIAN_PACKAGE_MAINTAINER ${CPACK_PACKAGE_CONTACT})
+set(CPACK_DEBIAN_PACKAGE_HOMEPAGE ${LIBTIDY_URL})
+set(CPACK_DEBIAN_PACKAGE_SECTION "Libraries")
+set(CPACK_SOURCE_IGNORE_FILES "${PROJECT_SOURCE_DIR}/build" )
+
+
+#------------------------------------------------------------------------
+# RPM config
+#------------------------------------------------------------------------
+set(CPACK_RPM_EXCLUDE_FROM_AUTO_FILELIST_ADDITION "/usr/share/man" "/usr/share/man/man1")
+set(CPACK_SOURCE_IGNORE_FILES "${CMAKE_CURRENT_SOURCE_DIR}/test/;${CMAKE_CURRENT_SOURCE_DIR}/build/;${CMAKE_CURRENT_SOURCE_DIR}/.git/")
+
+
+#------------------------------------------------------------------------
+# Package name configuration
+#   The default is LIB_NAME-CPACK_PACKAGE_VERSION-CMAKE_SYSTEM_NAME,
+#   but we want to include system name for Unixes, and correct the
+#   system name on Apple targets.
+#------------------------------------------------------------------------
+if (UNIX AND NOT APPLE)
+    set(CPACK_PACKAGE_FILE_NAME "${LIB_NAME}-${CPACK_PACKAGE_VERSION}-${CMAKE_SYSTEM_NAME}-${BITNESS}bit")
+endif ()
+if (APPLE AND NOT IOS)
+    if (CMAKE_OSX_ARCHITECTURES)
+        set(CPACK_PACKAGE_FILE_NAME "${LIB_NAME}-${CPACK_PACKAGE_VERSION}-macOS-${CMAKE_OSX_ARCHITECTURES}")
+        string(REPLACE ";" "+" CPACK_PACKAGE_FILE_NAME "${CPACK_PACKAGE_FILE_NAME}")
+    else ()
+        set(CPACK_PACKAGE_FILE_NAME "${LIB_NAME}-${CPACK_PACKAGE_VERSION}-macOS-${BITNESS}bit")
+    endif ()
+endif ()
+if (IOS)
+    set(CPACK_PACKAGE_FILE_NAME "${LIB_NAME}-${CPACK_PACKAGE_VERSION}-iOS-${BITNESS}bit")
+endif ()
+
+
+#------------------------------------------------------------------------
+# Build the Package
+#------------------------------------------------------------------------
 include(CPack)
 
+
+#------------------------------------------------------------------------
+# pkg-config
+#------------------------------------------------------------------------
+configure_file(
+    "${CMAKE_CURRENT_SOURCE_DIR}/${LIB_NAME}.pc.cmake.in"
+    "${CMAKE_CURRENT_BINARY_DIR}/${LIB_NAME}.pc"
+    @ONLY
+    )
+    
+install(FILES
+    "${CMAKE_CURRENT_BINARY_DIR}/${LIB_NAME}.pc"
+    DESTINATION "${LIB_INSTALL_DIR}/pkgconfig"
+    )
+
 # eof

Dockerfile

@@ -0,0 +1,15 @@
+FROM debian:stable-slim AS builder
+RUN apt-get update -y && \
+	apt-get install -y git cmake make build-essential gcc
+
+WORKDIR /build
+COPY . .
+
+RUN cd build/cmake
+RUN cmake /build -DCMAKE_BUILD_TYPE=Release 
+RUN make
+RUN make install
+
+FROM debian:stable-slim AS runtime
+COPY --from=builder /usr/local/bin/tidy /usr/local/bin/tidy
+ENTRYPOINT [ "/usr/local/bin/tidy" ]

LICENSE.txt

@@ -1,45 +0,0 @@
-
-  Copyright (c) 1998-2015 World Wide Web Consortium
-  (Massachusetts Institute of Technology, European Research 
-  Consortium for Informatics and Mathematics, Keio University).
-  All Rights Reserved.
-
-  Contributing Author(s):
-
-     Dave Raggett <dsr@w3.org>
-
-  The contributing author(s) would like to thank all those who
-  helped with testing, bug fixes and suggestions for improvements. 
-  This wouldn't have been possible without your help.
-
-  COPYRIGHT NOTICE:
- 
-  This software and documentation is provided "as is," and
-  the copyright holders and contributing author(s) make no
-  representations or warranties, express or implied, including
-  but not limited to, warranties of merchantability or fitness
-  for any particular purpose or that the use of the software or
-  documentation will not infringe any third party patents,
-  copyrights, trademarks or other rights. 
-
-  The copyright holders and contributing author(s) will not be held
-  liable for any direct, indirect, special or consequential damages
-  arising out of any use of the software or documentation, even if
-  advised of the possibility of such damage.
-
-  Permission is hereby granted to use, copy, modify, and distribute
-  this source code, or portions hereof, documentation and executables,
-  for any purpose, without fee, subject to the following restrictions:
-
-  1. The origin of this source code must not be misrepresented.
-  2. Altered versions must be plainly marked as such and must
-     not be misrepresented as being the original source.
-  3. This Copyright notice may not be removed or altered from any
-     source or altered source distribution.
- 
-  The copyright holders and contributing author(s) specifically
-  permit, without fee, and encourage the use of this source code
-  as a component for supporting the Hypertext Markup Language in
-  commercial products. If you use this source code in a product,
-  acknowledgment is not required but would be appreciated.
-

README.html

@@ -1,124 +0,0 @@
-<!DOCTYPE html>
-<html>
- <head>
-  <meta charset="UTF-8">
-  <title>
-  HTML Tidy with HTML5 support
-  </title>
-  <style>
-  h1 {
-    background-color: #6495ed;
-  }
-  code {
-    background-color: #e0ffff;
-  }
-  div {
-    background-color: #b0c4de;
-  }
-  </style>
- </head>
- <body>
-  <h1>
-   HTML Tidy with HTML5 support
-  </h1>
-  <h2>
-   Prerequisites
-  </h2>
-  <ol>
-   <li>
-    <p>
-     git - http://git-scm.com/book/en/v2/Getting-Started-Installing-Git
-    </p>
-   </li>
-   <li>
-    <p>
-     cmake - http://www.cmake.org/download/
-    </p>
-   </li>
-   <li>
-    <p>
-     appropriate build tools for the platform
-    </p>
-   </li>
-  </ol>
-  <p>
-   CMake comes in two forms - command line and gui. Some installations only install one or the
-   other, but sometimes both. The build commands below are only for the command line use.
-  </p>
-  <p>
-   Also the actual build tools vary for each platform. But that is one of the great features of
-   cmake, it can generate variuous 'native' build files. Running cmake without any parameters will
-   list the generators available on that platform. For sure one of the common ones is "Unix
-   Makefiles", which needs autotools make installed, but many other generators are supported.
-  </p>
-  <p>
-   In windows cmake offers various versions of MSVC. Again below only the command line use of MSVC
-   is shown, but the tidy solution (*.sln) file can be loaded into the MSVC IDE, and the building
-   done in there.
-  </p>
-  <h2>
-   Build the tidy library and command line tool
-  </h2>
-  <ol>
-   <li>
-    <p>
-     <code>cd build/cmake</code>
-    </p>
-   </li>
-   <li>
-    <p>
-     <code>cmake ../.. [-DCMAKE_INSTALL_PREFIX=/path/for/install]</code>
-    </p>
-   </li>
-   <li>
-    <p>
-     Windows: <code>cmake --build . --config Release</code>
-     <br>
-     Unix/OS X: <code>make</code>
-    </p>
-   </li>
-   <li>
-    <p>
-     Install, if desired:
-     <br>
-     Windows: <code>cmake --build . --config Release --target INSTALL</code>
-     <br>
-     Unix/OS X: <code>[sudo] make install</code>
-    </p>
-   </li>
-  </ol>
-  <p>
-   By default cmake sets the install path to /usr/local in unix. If you wanted the binary in say
-   /usr/bin instead, then in 2. above use -DCMAKE<em>INSTALL</em>PREFIX=/usr
-  </p>
-  <p>
-   In windows the default install is to C:\Program Files\tidy5, or C:/Program Files (x86)/tidy5,
-   which is not very useful. After the build the tidy[n].exe is in the Release directory, and can
-   be copied to any directory in your PATH environment variable, for global use.
-  </p>
-  <p>
-   If you need the tidy library built as a 'shared' (DLL) library, then in 2. add the command
-   -DBUILD<em>SHARED</em>LIB:BOOL=ON. This option is OFF by default, so the static library is
-   built and linked with the command line tool for convenience.
-  </p>
-  <h2>
-   History
-  </h2>
-  <p>
-   This repository should be considered canonical for HTML Tidy as of 2015-January-15.
-  </p>
-  <ul>
-   <li>
-    <p>
-     This repository originally transferred from <a href=
-     "http://w3c.github.com/tidy-html5/">w3c.github.com/tidy-html5</a>.
-    </p>
-   </li>
-   <li>
-    <p>
-     First moved to Github from <a href="http://tidy.sourceforge.net">tidy.sourceforge.net</a>.
-    </p>
-   </li>
-  </ul>
- </body>
-</html>

README.md

@@ -1,56 +1,104 @@
-# HTML Tidy with HTML5 support
+[![Build Status](https://drone.data.coop/api/badges/emelie/tidy-html5/status.svg?ref=refs/heads/next)](https://drone.data.coop/emelie/tidy-html5)
 
-## Prerequisites
+## Forked from [https://github.com/htacg/tidy-html5](https://github.com/htacg/tidy-html5)
 
-  1. git - http://git-scm.com/book/en/v2/Getting-Started-Installing-Git
+# HTACG HTML Tidy
+
+All other READMEs and related materials can be found in [README/][100]. Although all of our materials should be linked in this README, be sure to check this directory for documents we’ve not yet added to this document.
+
+## Building HTML Tidy
+
+  - For build instructions please see [README/BUILD.md][115].
   
-  2. cmake - http://www.cmake.org/download/
+## Branches and Versions
+
+Learn about which branches are available, which branch you should use, and how HTML Tidy’s versioning scheme works.
+
+  - Learn about version numbering in [README/VERSION.md][160].
+  - Learn about our repository branches in [README/BRANCHES.md][110].
   
-  3. appropriate build tools for the platform
-  
-CMake comes in two forms - command line and gui. Some installations only install one or the other, but sometimes both. The build commands below are only for the command line use.
+## Contributing and Development Guides
 
-Also the actual build tools vary for each platform. But that is one of the great features of cmake, it can generate variuous 'native' build files. Running cmake without any parameters will list the generators available on that platform. For sure one of the common ones is "Unix Makefiles", which needs autotools make installed, but many other generators are supported.
+We gladly accept PRs! Read about some of our contribution guidelines, and check out some of the additional explanatory documents that will aid your understanding of how to accomplish certain things in HTML Tidy.
 
-In windows cmake offers various versions of MSVC. Again below only the command line use of MSVC is shown, but the tidy solution (*.sln) file can be loaded into the MSVC IDE, and the building done in there.
+### General Contribution Guidelines
+
+These are some general guidelines that will help you help us when it comes to making your own contributions to HTML Tidy.
+
+  - Learn about our contributing guidelines in [README/CONTRIBUTING.md][125].
+  - Understand HTML Tidy’s source code style in [README/CODESTYLE.md][120].
+
+### Adding Features Guides
+
+When you’re ready to add a great new feature, these write-ups may be useful.
+
+  - Learn how to add new element attributes to HTML Tidy by reading [README/ATTRIBUTES.md][105].
+  - Discover how to add new tags to Tidy in [README/TAGS.md][130].
+  - If you want to add new messages to Tidy, read [README/MESSAGE.md][150].
+  - Configuration options can be added according to [README/OPTIONS.md][155].
+  - Pull Requests must pass all existing regression tests, or you must change existing regression test expectations with a good explanation. New features require that you add new regression tests. See [README/TESTING.md][165] for more details.
+
+### Language Localization Guides
+
+Tidy supports localization, and welcomes translations into various languages. Please read up on how to localize HTML Tidy.
+
+ - The general README for localizing can be found in [README/LOCALIZE.md][140].
+ - And [localize/README.md][145] contains specific instructions for localizing.
 
 
-## Build the tidy library and command line tool
+## Other Important Links
 
-  1. `cd build/cmake`
+ - site: [https://www.html-tidy.org/][4]
+ - source: [https://github.com/htacg/tidy-html5][5]
+ - binaries: [https://binaries.html-tidy.org][6]
+ - bugs: [https://github.com/htacg/tidy-html5/issues][7]
+ - list: [https://lists.w3.org/Archives/Public/html-tidy/][8]
+ - api and quickref: [https://api.html-tidy.org/][9]
+ - Wikidata: [https://www.wikidata.org/wiki/Q1566084][10]
 
-  2. `cmake ../.. [-DCMAKE_INSTALL_PREFIX=/path/for/install]`
+  [4]: https://www.html-tidy.org/
+  [5]: https://github.com/htacg/tidy-html5
+  [6]: https://binaries.html-tidy.org
+  [7]: https://github.com/htacg/tidy-html5/issues
+  [8]: https://lists.w3.org/Archives/Public/html-tidy/
+  [9]: https://api.html-tidy.org/
+  [10]: https://www.wikidata.org/wiki/Q1566084
 
-  3. Windows:  `cmake --build . --config Release`  
-     Unix/OS X: `make`
-
-  4. Install, if desired:  
-     Windows: `cmake --build . --config Release --target INSTALL`  
-     Unix/OS X: `[sudo] make install`
-
-By default cmake sets the install path to /usr/local in unix. If you wanted the binary in say /usr/bin instead, then in 2. above use -DCMAKE_INSTALL_PREFIX=/usr
-
-Also, in unix if you want to build the release library without any debug `assert` in the code then add `-DCMAKE_BUILD_TYPE=Release` in step 2. This adds a `-DNDEBUG` macro to the compile switches. This is normally added in windows build for the `Release` config.
-
-In windows the default install is to C:\Program Files\tidy5, or C:/Program Files (x86)/tidy5, which is  not very useful. After the build the tidy[n].exe is in the Release directory, and can be copied to any directory in your PATH environment variable, for global use.
-
-If you do **not** need the tidy library built as a 'shared' (DLL) library, then in 2. add the command -DBUILD_SHARED_LIB:BOOL=OFF. This option is ON by default. The static library is always built and linked with the command line tool for convenience in windows, and so the binary can be run as part of the man page build without the shared library being installed in unix.
-
-## Prebuilt Binaries
-
-An attempt is being made to publish pre-built binaries to http://www.htacg.org/binaries - This is still a work in progress, but getting there..
 
 ## History
 
-This repository should be considered canonical for HTML Tidy as of 2015-January-15.
+This repository should be considered canonical for HTML Tidy starting from 2015-January-15.
 
- - This repository originally transferred from [w3c.github.com/tidy-html5][1].
+ - This repository originally transferred from [w3c.github.com/tidy-html5][20], then redirected to the current site, but now dead.
  
- - First moved to Github from [tidy.sourceforge.net][2].
+ - First moved to Github from [tidy.sourceforge.net][21]. Note, this site is kept only for historic reasons, and is not now well maintained.
+
+**Tidy is the granddaddy of HTML tools, with support for modern standards.** Have fun...
+
+  [20]: https://w3c.github.com/tidy-html5/
+  [21]: http://tidy.sourceforge.net
 
 
-   [1]: http://w3c.github.com/tidy-html5/
+## License
 
-   [2]: http://tidy.sourceforge.net
+HTML Tidy and LibTidy are free and open source software with a permissive license.
 
-; eof
+ - You can read the complete license in [README/LICENSE.md][135].
+
+
+
+  [100]: README/
+  [105]: README/ATTRIBUTES.md
+  [110]: README/BRANCHES.md
+  [115]: README/BUILD.md
+  [120]: README/CODESTYLE.md
+  [125]: README/CONTRIBUTING.md
+  [130]: README/TAGS.md
+  [135]: README/LICENSE.md
+  [140]: README/LOCALIZE.md
+  [145]: localize/README.md
+  [150]: README/MESSAGE.md
+  [155]: README/OPTIONS.md
+  [160]: README/VERSION.md
+  [165]: README/TESTING.md
+ 

README/API_AND_NAMESPACE.md

@@ -0,0 +1,104 @@
+# The `LibTidy` API and Namespacing
+
+## Introduction
+
+If you're just getting started working with `LibTidy`, some of the design choices may seem overwhelming if you're not a seasoned C veteran. Hopefully this article will give a decent overview, encouraging you to explore and contribute to the `LibTidy` code.
+
+This article will discuss briefly:
+
+- How `LibTidy` achieves namespacing in C
+
+- Explanations for some of the bizzarre, do-nothing macros.
+
+- Opaque types
+
+- How to add new functions to the `LibTidy` API.
+
+
+# Namespacing
+
+The C language does not support built in namespacing, but it is subject to namespace collision, especially when a library is statically linked. `LibTidy` tries to get around this by making a compromise between human-readable names and making the names random enough to avoid a collision.
+
+As you browse Tidy's code, you'll notice many uses of a macro function – `TY_()` – applied to the function names of non-static functions. The preprocessor thus resolves all of these function names to `prvTidyFunction`, thus ensuring a clear namespace and avoiding the possibility of collisions (unless some other library has thoughtlessly borrowed our prefix for the same). For example, `TY_(getNextOptionPick)` will resolve to `prvTidygetNextOptionPick` when compiled.
+
+Of course, `static` functions are immune to the issue of namespace pollution, so in general you will really only use this technique for functions that must be accessible from outside of your new file, such as functions that you want to expose to the API.
+
+
+# Macros for documentation
+
+`TIDY_EXPORT` and `TIDY_CALL` are defined to be `NULL`, i.e., when compiled they resolve to nothing. These are used exclusively for documenting functions that are part of the API defined in `tidy.h` and the implementation in `tidylib.c`. For example, in `tidy.h`:
+
+~~~
+TIDY_EXPORT TidyIterator TIDY_CALL getWindowsLanguageList();
+~~~
+
+The `TIDY_EXPORT` call clearly indicates that this function prototype is meant to be exported from the API, and `TIDY_CALL` clearly indicates that the function is called from within `LibTidy`.
+
+Although this makes things obvious from the documentation perspective, the truth is a little murkier. In some environments one might define `TIDY_EXPORT` and `TIDY_CALL` differently in order to control compiler behavior, especially in environments that have special requirements for dynamic libraries. In general, though, you shouldn't have to worry about this.
+
+The preferred use of pointer operators when documenting with macros is this:
+
+~~~
+const tidyLocaleMapItem* TIDY_CALL getNextWindowsLanguage( TidyIterator* iter )
+~~~
+
+…instead of this:
+
+~~~
+const tidyLocaleMapItem TIDY_CALL *getNextWindowsLanguage( TidyIterator* iter )
+~~~
+
+
+# External types are opaque
+
+In several spots the source code indicates that a particular structure is "opaque." This simply means that API users cannot see inside of them, and they have to depend on accessor functions to gain access to the sweet fruit that is within. This is a design choice that makes `LibTidy` highly portable and makes it accessible to multitudes of other languages that can communicate with a C API.
+
+Take `tidyDoc` for example, as it's the most fundamental datatype within `LibTidy`. As an API user, you can have a reference to a `tidyDoc`, and you're going to pass it around a lot to accessor functions (such as `tidyCleanAndRepair`), and you know that it contains lots of good stuff, but you're not allowed to peek inside of it unless an accessor function is provided. Think of it as a token that you pass around, and nothing more.
+
+Internally, the type is cast to a native C structure of type `tidyDocImpl`, and so if you decide to become a Tidy developer, you have the choice to access the item fully.
+
+If you extend Tidy's API, it's important to respect this design choice, even if only writing functionality for the console application (which is, of course, simply an implementor of `LibTidy`).
+
+
+# How to add new functions to `LibTidy`
+
+All of the information above is useful for anyone who wants to browse Tidy's source code, or use the API, or understand Tidy better, but it all comes together nicely when you want to extend the API. This quick lesson will show you how to do so, using `tidyLocalizedString()` as an example.
+
+## Behind the scenes
+
+The first thing we need to do is have the internal version of the function that we want to add. Tidy has a module that handles localization: `language.h/c`. In the header is where we define the interface to LibTidy, which should be namespaced according to the discussion above. We can declare:
+
+~~~
+ctmbstr TY_(tidyLocalizedString)( uint messageType );
+~~~
+
+…and of course implement it in the `.c` file.
+
+Now you have a decision to make: if you plan to use this function internally, you're going to have to import the header into other modules that require the function. This can lead to painful compile-time consequences. However since we want to expose this particular function to the API, it will be visible within `TidyLib`, so we can use the public API internally, too.
+
+## The API
+
+Once implemented, we want a pretty, public-facing name for our `tidyLocalizedString()` function, which appropriately is `tidyLocalizedString()`. Add the declaration to `tidy.h`:
+
+~~~
+TIDY_EXPORT ctmbstr TIDY_CALL tidyLocalizedString( uint messageType );
+~~~
+
+…and now the publicly exposed interface knows that your function exists. All that's left to do is add the `language.h` header to `tidylib.c`, and then implement it there:
+
+~~~
+ctmbstr TIDY_CALL tidyLocalizedString( uint messageType )
+{
+    return TY_(tidyLocalizedString)( messageType );
+}
+~~~
+
+Congratulations, you can now expose new functionality to the API.
+
+## API functions for opaque types
+
+For a more complicated example that demonstrates how to use opaque types (and also the `TidyIterator` type) have a look at the implementation of `getWindowsLanguageList()`, and its partners `*getNextWindowsLanguage()`, `TidyLangWindowsName()`, and `TidyLangPosixName()`. These demonstrate how to:
+
+  - implement iteration for structures with multiple records.
+  - write a function in `tidylib.c` that converts between the exposed, opaque type and the internal, implementation type.
+  - further reinforce how functionality is added to the API.

README/ATTRIBUTES.md

@@ -0,0 +1,26 @@
+# Tidy Element Attributes
+
+This is about adding a **new** HTML attribute to one or more HTML tags, i.e., a new attribute such as `attribute=value`.
+
+Tidy’s large number of attributes are supported via number of files:
+
+  - `tidyenum.h` is where you first define a new attribute in order to give it an internal value.
+  - `attrs.c` is where you give a unique **string** name to the attribute, as well as a **function** to verify the **value**.
+  - `attrdict.c` further refines the definition of your attribute, specifying which version(s) of HTML support this attribute.
+  - `tags.c`, finally, determines which tags support the attribute, in the `tag_defs[]` table.
+
+So, to add a new `attribute=value`, on one or more existing tags, consists of the following simple steps -
+
+ 1. `tidyenum.h` - Give the attribute an internal name, like `TidyAttr_XXXX`, and thus a value. Please try to keep this enumeration in alphabetical order.
+
+ 2. `attrs.c` - Assign the string value of the attribute. Of course this must be unique. And then assign a `function` to verify the attribute value. There are already a considerable number of defined functions to verify specific attribute values, but maybe this new attribute requires a new function, so that should be written, and defined.
+ 
+ 3. `attrdict.c` - If this attribute only relates to specific tags, then it should be added to their list. There are some general attributes that are allowed on every, or most tags, so this new attribute and value should be added accordingly.
+ 
+ 4. `tags.c` - Now the new attribute will be verified for each tag it is associated with in the `tag_defs[]` table. Like for example the `<button ...>`, `{ TidyTag_BUTTON, ...` has `&TY_(W3CAttrsFor_BUTTON)[0]` assigned.
+
+So, normally, just changing 3 files, `tidyenum.h`, `attrs.c`, and `attrdict.c`, will already adjust `tags.c` to accept a new `attribute=value` for any tag, or all tags. Simple...
+
+Now, one could argue that this is not the **best** way to verify every attribute and value, for every tag, but that is a moot point - that is how Tidy does it!
+
+; eof 20170205

README/BRANCHES.md

@@ -0,0 +1,28 @@
+# HTML Tidy Branches
+
+## About Branches
+
+Starting with **HTML Tidy** 5.4.0, HTACG will adopt a new branch management strategy utilizing **master** as the _release branch_, and **next** as the active development branch.
+
+As described thoroughly in our [VERSION.md](VERSION.md) document, this means that **master** will always consist of an even-numbered minor version, and activity will remain relatively quiet unless we backport a critical bug fix from **next**.
+
+The **next** branch, then will host the majority of our development activity, and any contributions and PR’s should be against this branch. This means that **next** will always consist of an odd minor version number.
+
+
+## About Versioning
+
+You can read the specifics about version numbers in our [VERSION.md](VERSION.md) document.
+
+
+## FAQs
+
+### Which version or branch should I choose?
+
+As described above, the branch is very strongly correlated with the version. If you require a stable API and relatively stable output and don’t require the features and enhancements of an odd-numbered **next** version, then you should stick to **master**, even-numbered versions.
+
+On the other hand if you are primarily a console application user, then the API isn’t likely as important to you, and you probably want the latest and greatest. If this describes you, you probably want to at least try out **next**.
+
+If you are developing for Tidy, then you _definitely_ want to stick to **next**, even for bug fixes meant for **master**. If it’s a critical enough bug fix, then one of our friendly team will back-port the fix to **master**.
+
+
+

README/BUILD.md

@@ -0,0 +1,91 @@
+# HTACG HTML Tidy
+
+## Prerequisites
+
+  1. git - [https://git-scm.com/book/en/v2/Getting-Started-Installing-Git][1]
+  
+  2. cmake - [https://cmake.org/download/][2]
+  
+  3. appropriate build tools for the platform
+  
+  4. the [xsltproc][3] tool is required to build and install the `tidy.1` man page on Unix-like platforms.
+  
+CMake comes in two forms - command line and GUI. Some installations only install one or the other, but sometimes both. The build commands below are only for command line use.
+
+Also the actual build tools vary for each platform. But that is one of the great features of CMake, it can generate various 'native' build files. Running `cmake --help` should list the generators available on that platform. For sure one of the common ones is "Unix Makefiles", which needs autotools make installed, but many other generators are supported.
+
+In Windows CMake offers various versions for MSVC. Again below only the command line use of MSVC is shown, but the tidy solution (*.sln) file can be loaded into the MSVC IDE, and the building done in there.
+
+
+## Build the tidy library and command line tool
+
+### macOS/Linux/Unix
+
+~~~
+    cd build/cmake
+    cmake ../.. -DCMAKE_BUILD_TYPE=Release [-DCMAKE_INSTALL_PREFIX=/path/for/install]
+    make
+    [sudo] make install
+~~~
+
+### macOS (multi-architecture)
+
+~~~
+    cd build/cmake
+    cmake ../.. -DCMAKE_BUILD_TYPE=Release "-DCMAKE_OSX_ARCHITECTURES=x86_64;arm64"
+    make
+    [sudo] make install
+~~~
+
+### Windows
+
+~~~
+    cd build/cmake
+    cmake ../.. -DCMAKE_BUILD_TYPE=Release [-DCMAKE_INSTALL_PREFIX=/path/for/install]
+    cmake --build . --config Release
+    cmake --build . --config Release --target INSTALL
+~~~
+
+### Build options
+
+By default cmake sets the install path to `/usr/local/bin` in Unix. If you wanted the binary in say `/usr/bin` instead, then in the second step, use `-DCMAKE_INSTALL_PREFIX=/usr`.
+
+Also, in Unix if you want to build the release library without any debug `assert` in the code then add `-DCMAKE_BUILD_TYPE=Release` in the second step. This adds a `-DNDEBUG` macro to the compile switches. This is normally added in windows build for the `Release` config.
+
+In Windows the default install is to `C:\Program Files\tidy`, or `C:/Program Files (x86)/tidy`, which is  not very useful. After the build the `tidy.exe` is in the `Release` directory, and can be copied to any directory in your `PATH` environment variable for global use.
+
+On macOS, you can build for both Intel and Apple Silicon by adding "-DCMAKE_OSX_ARCHITECTURES=x86_64;arm64" in the second step.
+
+If you do **not** need the tidy library built as a 'shared' (DLL) library, then in the second step add the command `-DBUILD_SHARED_LIB:BOOL=OFF`. This option is **ON** by default. The static library is always built and linked with the command line tool for convenience in Windows, and so the binary can be run as part of the man page build without the shared library being installed in unix.
+
+See the `CMakeLists.txt` file for other CMake **options** offered.
+
+## Build the tidy packages
+
+  1. `cd build/cmake`
+
+  2. `cmake ../.. -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/usr`
+
+  3. Unix/OS X: `make package`
+
+## Build PHP with the tidy-html5 library
+
+Before PHP 7.1, due to API changes in the PHP source, `buffio.h` needs to be renamed to `tidybuffio.h` in the file `ext/tidy/tidy.c` in PHP's source.
+
+That is - prior to configuring PHP run this in the PHP source directory:
+~~~
+sed -i 's/buffio.h/tidybuffio.h/' ext/tidy/*.c
+~~~
+
+And then continue with (just an example here, use your own PHP config options):
+
+~~~
+./configure --with-tidy=/usr/local
+make
+make test
+make install
+~~~
+
+  [1]: https://git-scm.com/book/en/v2/Getting-Started-Installing-Git
+  [2]: https://cmake.org/download/
+  [3]: http://xmlsoft.org/XSLT/xsltproc2.html

README/CHANGELOG.md

@@ -0,0 +1,246 @@
+# Changelog
+
+## [5.8.0](https://github.com/htacg/tidy-html5/tree/5.8.0) (2021-07-10)
+
+[Full Changelog](https://github.com/htacg/tidy-html5/compare/5.6.0...5.8.0)
+
+**Fixed bugs:**
+
+- Details open, Value added to Attribute [\#925](https://github.com/htacg/tidy-html5/issues/925)
+- Fix handling of percent symbols in CheckLength validation routine [\#910](https://github.com/htacg/tidy-html5/issues/910)
+- What is the true purpose and use case of the --bare option? [\#896](https://github.com/htacg/tidy-html5/issues/896)
+- Warning about missing \</summary\> [\#895](https://github.com/htacg/tidy-html5/issues/895)
+- DecodeMacRoman\(\) is missing an upper bounds check before indexing into Mac2Unicode array [\#891](https://github.com/htacg/tidy-html5/issues/891)
+- Can't disable wrap [\#858](https://github.com/htacg/tidy-html5/issues/858)
+- Recursion limit exceeded [\#850](https://github.com/htacg/tidy-html5/issues/850)
+- template tag should be allowed in head [\#836](https://github.com/htacg/tidy-html5/issues/836)
+- tag\_defs + AdjustTags\(\) and ResetTags\(\) during parsing is not thread-safe \(tags.c\) [\#816](https://github.com/htacg/tidy-html5/issues/816)
+- Unexpected parsing with uppercase DOCTYPE [\#815](https://github.com/htacg/tidy-html5/issues/815)
+- bugfix for messageobj.c for windows vc++ [\#800](https://github.com/htacg/tidy-html5/issues/800)
+- Tidy 5.7.20 GetSurrogatePair can use uninitialised value processing malformed entity refs [\#798](https://github.com/htacg/tidy-html5/issues/798)
+- regression tests fail if /etc/tidy.conf or ~/.tidyrc exists [\#778](https://github.com/htacg/tidy-html5/issues/778)
+- AddByte allocAmt overflows for large input files [\#761](https://github.com/htacg/tidy-html5/issues/761)
+- --strict-tags-attributes no doesn't ignore \<td align\> [\#729](https://github.com/htacg/tidy-html5/issues/729)
+- "Too many title elements in \<title\>" should say "Too many title elements in \<head\>" [\#692](https://github.com/htacg/tidy-html5/issues/692)
+- Tidy 5.6.0 on Mac says Not a file when file is not writeable [\#681](https://github.com/htacg/tidy-html5/issues/681)
+- Tidy fails if html contains a section \<!\[endif\]—\> [\#487](https://github.com/htacg/tidy-html5/issues/487)
+- "Malformed" Word 2000 sequence may cause Tidy to skip document content [\#462](https://github.com/htacg/tidy-html5/issues/462)
+- Change open tag to Boolean [\#932](https://github.com/htacg/tidy-html5/pull/932) (@arrmo)
+- Is \#729 - Show 'warnings' in all td cases [\#928](https://github.com/htacg/tidy-html5/pull/928) (@geoffmcl)
+- Issue \#692 - too many titles [\#927](https://github.com/htacg/tidy-html5/pull/927) (@geoffmcl)
+- Is. \#681 - read-only files, and dirs [\#926](https://github.com/htacg/tidy-html5/pull/926) (@geoffmcl)
+- Free attributes before return NULL [\#899](https://github.com/htacg/tidy-html5/pull/899) (@ltx2018)
+- Is. \#896 - make 'bear' docs match code [\#898](https://github.com/htacg/tidy-html5/pull/898) (@geoffmcl)
+- Correction for issue-895 [\#897](https://github.com/htacg/tidy-html5/pull/897) (@arrmo)
+- fix memleak in GetTokenFromStream [\#884](https://github.com/htacg/tidy-html5/pull/884) (@ltx2018)
+- Protect against NULL in PruneSection. [\#853](https://github.com/htacg/tidy-html5/pull/853) (@esclim)
+- Is \#815 - Use case-insensitive test 'html' [\#832](https://github.com/htacg/tidy-html5/pull/832) (@geoffmcl)
+- Is. \#761 - just deal with the 'uint' wrap [\#830](https://github.com/htacg/tidy-html5/pull/830) (@geoffmcl)
+- Tidy 5.7.20 crashes if allocator replaced [\#797](https://github.com/htacg/tidy-html5/issues/797)
+- --mute should suppress non-zero exit code [\#794](https://github.com/htacg/tidy-html5/issues/794)
+- Seems tidy.c has sprung a leak [\#791](https://github.com/htacg/tidy-html5/issues/791)
+- Cannot handle read-only html files \(possibly regression?\) [\#789](https://github.com/htacg/tidy-html5/issues/789)
+- setlocale\( LC\_ALL, ""\) changes the locale for the entire application [\#770](https://github.com/htacg/tidy-html5/issues/770)
+- mute in ~/.tidyrc runs fine but triggers exit\(1\) [\#752](https://github.com/htacg/tidy-html5/issues/752)
+- Duplicate IDs are not detected if the ID has an uppercase letter [\#726](https://github.com/htacg/tidy-html5/issues/726)
+- Tidy gets confused with a \<span\> around a block element [\#709](https://github.com/htacg/tidy-html5/issues/709)
+- Tidy seems to get confused by HTML strings in JavaScript blocks. [\#700](https://github.com/htacg/tidy-html5/issues/700)
+- tidy indent+wrap breaks \<pre\> formatting [\#697](https://github.com/htacg/tidy-html5/issues/697)
+- -export-config creates invalid configuration file [\#679](https://github.com/htacg/tidy-html5/issues/679)
+- Segmentation Fault [\#656](https://github.com/htacg/tidy-html5/issues/656)
+- Maybe a problem with some vsnprintf implementations? [\#655](https://github.com/htacg/tidy-html5/issues/655)
+- Why is libtidy complaining \<data\> isn’t approved by W3C? [\#649](https://github.com/htacg/tidy-html5/issues/649)
+- Is. \#791 - free some allocations [\#809](https://github.com/htacg/tidy-html5/pull/809) (@geoffmcl)
+- Issue 726 upper case anchors [\#731](https://github.com/htacg/tidy-html5/pull/731) (@geoffmcl)
+- Is \#673 - Revert 350f7b4 and 86e62db AdjustConfig logic [\#705](https://github.com/htacg/tidy-html5/pull/705) (@geoffmcl)
+- Issue \#655 - Fix unsafe use of output buffer as input param [\#662](https://github.com/htacg/tidy-html5/pull/662) (@geoffmcl)
+- Issue \#656 - protect against NULL node set in loop [\#661](https://github.com/htacg/tidy-html5/pull/661) (@geoffmcl)
+
+**Closed issues:**
+
+- No NPM? [\#960](https://github.com/htacg/tidy-html5/issues/960)
+- Where can I find the list of known tags? [\#958](https://github.com/htacg/tidy-html5/issues/958)
+- fix non-standard static library name [\#952](https://github.com/htacg/tidy-html5/issues/952)
+- Lot of config options; but where are the defaults specified [\#948](https://github.com/htacg/tidy-html5/issues/948)
+- Any Windows Binaries for 5.7.28, just like 5.6? [\#947](https://github.com/htacg/tidy-html5/issues/947)
+- Setup continuous integration and testing [\#944](https://github.com/htacg/tidy-html5/issues/944)
+- Linux binaries for latest releases [\#939](https://github.com/htacg/tidy-html5/issues/939)
+- Outdated warnings [\#938](https://github.com/htacg/tidy-html5/issues/938)
+- Umlauts/special characters not converted to correct html entities [\#936](https://github.com/htacg/tidy-html5/issues/936)
+- tidy hanging [\#935](https://github.com/htacg/tidy-html5/issues/935)
+- Tidy catches repeated attributes, but misses identical ids [\#924](https://github.com/htacg/tidy-html5/issues/924)
+- drop-empty-elements is not removing empty Table elements [\#923](https://github.com/htacg/tidy-html5/issues/923)
+- Tag "main" is shown as error [\#922](https://github.com/htacg/tidy-html5/issues/922)
+- Unexpected parsing a tag in table [\#919](https://github.com/htacg/tidy-html5/issues/919)
+- beginner on windows -- tidy reports: document: "a0.htm" is not a file! -- But it is [\#918](https://github.com/htacg/tidy-html5/issues/918)
+- tidy says this misplaced \</dl\> is OK [\#917](https://github.com/htacg/tidy-html5/issues/917)
+- Tidy can't deal with \<中文\> XML tags [\#913](https://github.com/htacg/tidy-html5/issues/913)
+- Support extended color names in HTML 5 [\#908](https://github.com/htacg/tidy-html5/issues/908)
+- Unknown type uint trying to use the shared lib. [\#906](https://github.com/htacg/tidy-html5/issues/906)
+- \</select\> ending tag missing [\#904](https://github.com/htacg/tidy-html5/issues/904)
+- SVG attributes flagged as proprietary [\#903](https://github.com/htacg/tidy-html5/issues/903)
+- tidy-mark option is not working [\#901](https://github.com/htacg/tidy-html5/issues/901)
+- Need help controlling output [\#894](https://github.com/htacg/tidy-html5/issues/894)
+- Say how to deal with XHTML input [\#893](https://github.com/htacg/tidy-html5/issues/893)
+- Help output refers to a non-existent -options option [\#892](https://github.com/htacg/tidy-html5/issues/892)
+- Tidy gets confused with u tags and underline styles [\#890](https://github.com/htacg/tidy-html5/issues/890)
+- how to forbid auto insert tag? [\#889](https://github.com/htacg/tidy-html5/issues/889)
+- Incorrectly changing — to - \(emdash \[alt 0151\]\) to hypens. [\#885](https://github.com/htacg/tidy-html5/issues/885)
+- html-tidy site does not work with https [\#883](https://github.com/htacg/tidy-html5/issues/883)
+- Use with TextPad 8 [\#882](https://github.com/htacg/tidy-html5/issues/882)
+- Translation: TidyKeepTabs [\#880](https://github.com/htacg/tidy-html5/issues/880)
+- \<img\> proprietary attribute "loading" [\#879](https://github.com/htacg/tidy-html5/issues/879)
+- Versioning seems a bit off [\#877](https://github.com/htacg/tidy-html5/issues/877)
+- --quote-ampersand yes doesn't work [\#876](https://github.com/htacg/tidy-html5/issues/876)
+- Convert spaces to non-breaking space [\#875](https://github.com/htacg/tidy-html5/issues/875)
+- Tidy 5.6.0 mangled html / php code. [\#872](https://github.com/htacg/tidy-html5/issues/872)
+- Even with -utf8 tidy replaces UTF8 code U+00A0 into numeric entity &\#160; [\#871](https://github.com/htacg/tidy-html5/issues/871)
+- http-equiv metas should trigger helpful upgrade messages [\#868](https://github.com/htacg/tidy-html5/issues/868)
+- HTML Tidy website does not render propertly when using HTTPS [\#867](https://github.com/htacg/tidy-html5/issues/867)
+- \[-Wignored-qualifiers\] warning in tidy [\#866](https://github.com/htacg/tidy-html5/issues/866)
+- Wrong character encoding [\#863](https://github.com/htacg/tidy-html5/issues/863)
+- Missing semicolon after html entity sometimes returns generic 'unknown entity' warning instead of specific 'missing semicolon' [\#862](https://github.com/htacg/tidy-html5/issues/862)
+- Warning: unescaped & or unknown entity "&P" when encoding as utf-8 [\#861](https://github.com/htacg/tidy-html5/issues/861)
+- Tidy output clutter [\#857](https://github.com/htacg/tidy-html5/issues/857)
+- Trailing backspace removed [\#856](https://github.com/htacg/tidy-html5/issues/856)
+- Only wrap at tags [\#854](https://github.com/htacg/tidy-html5/issues/854)
+- ENABLE\_DEBUG\_LOG is ignored on Windows [\#852](https://github.com/htacg/tidy-html5/issues/852)
+- Kill off alphabetical ordering clause for publicly-exposed enum defs [\#851](https://github.com/htacg/tidy-html5/issues/851)
+- For Sublime Text 3 [\#849](https://github.com/htacg/tidy-html5/issues/849)
+- \<li\> tags skipped in tidy result shown on screen [\#847](https://github.com/htacg/tidy-html5/issues/847)
+- man page missing header causing appending to XML discussion [\#846](https://github.com/htacg/tidy-html5/issues/846)
+- \<input type="file"\> needs name= [\#845](https://github.com/htacg/tidy-html5/issues/845)
+- Expose node-\>last in the public API [\#844](https://github.com/htacg/tidy-html5/issues/844)
+- Support EJS? [\#842](https://github.com/htacg/tidy-html5/issues/842)
+- Tidy 5.2 cleaned up curly quotes but 5.6 doesn't [\#841](https://github.com/htacg/tidy-html5/issues/841)
+- Jekyll headings removed [\#840](https://github.com/htacg/tidy-html5/issues/840)
+- Should tidy allow an empty title element? [\#839](https://github.com/htacg/tidy-html5/issues/839)
+- Missing tags for 5.7.\* [\#834](https://github.com/htacg/tidy-html5/issues/834)
+- Python binding? [\#826](https://github.com/htacg/tidy-html5/issues/826)
+- Self-closing tags are not correctly recognized [\#813](https://github.com/htacg/tidy-html5/issues/813)
+- Different output when parsing HTML [\#790](https://github.com/htacg/tidy-html5/issues/790)
+- Continuously fuzzing tidy-html5 with OSS-Fuzz [\#788](https://github.com/htacg/tidy-html5/issues/788)
+- I18N isn't working \(mostly\) via changing the environment variables [\#783](https://github.com/htacg/tidy-html5/issues/783)
+- 5.6.0 and breakage with php-tidy [\#780](https://github.com/htacg/tidy-html5/issues/780)
+- Tidy needs a changelog [\#776](https://github.com/htacg/tidy-html5/issues/776)
+- TidyNodeGetText returns text with a new line appended [\#775](https://github.com/htacg/tidy-html5/issues/775)
+- Breaks microseconds after call tidy\_repair\_string [\#771](https://github.com/htacg/tidy-html5/issues/771)
+- Typos in language\_en.h, etc [\#765](https://github.com/htacg/tidy-html5/issues/765)
+- Document accessibility priority numbers better [\#756](https://github.com/htacg/tidy-html5/issues/756)
+- Xcode not working with tidylib [\#751](https://github.com/htacg/tidy-html5/issues/751)
+- Intent-To-Package: Snaps are Universal Linux Packages [\#748](https://github.com/htacg/tidy-html5/issues/748)
+- Can't parse UTF16 html string [\#744](https://github.com/htacg/tidy-html5/issues/744)
+- libtidy.so.5 has removed symbols between 5.2.0 and 5.6.0, but kept SONAME [\#743](https://github.com/htacg/tidy-html5/issues/743)
+- Tidy 5.7.16 -\> empty result [\#740](https://github.com/htacg/tidy-html5/issues/740)
+- Crash with malformed \<meta\> tag [\#739](https://github.com/htacg/tidy-html5/issues/739)
+- bug\(encoding\): non-ASCII characters in configuration file [\#737](https://github.com/htacg/tidy-html5/issues/737)
+- Improve documentation re: wrap-script-literals [\#736](https://github.com/htacg/tidy-html5/issues/736)
+- feature\_request\(validation\): “preserve-entities yes” by default [\#732](https://github.com/htacg/tidy-html5/issues/732)
+- Tidy emits warnings that aren't in order [\#696](https://github.com/htacg/tidy-html5/issues/696)
+- Option to disable tidy code fixing option [\#693](https://github.com/htacg/tidy-html5/issues/693)
+- tidy change html view when deal with white-space:pre tag [\#685](https://github.com/htacg/tidy-html5/issues/685)
+- CLI option to stop insertion/deletion of tags [\#682](https://github.com/htacg/tidy-html5/issues/682)
+- Tidy does not strip leading and trailing spaces in HTML href [\#678](https://github.com/htacg/tidy-html5/issues/678)
+- Use tidy with json  custom attributes on  custom components [\#677](https://github.com/htacg/tidy-html5/issues/677)
+- \[Question\] How to use tidy for multiple files? [\#668](https://github.com/htacg/tidy-html5/issues/668)
+- How to run a test-kit from terminal? [\#667](https://github.com/htacg/tidy-html5/issues/667)
+- Dependency on DLLs not Documented [\#666](https://github.com/htacg/tidy-html5/issues/666)
+- tidylib.c fails to compile on Visual Studio 2010 [\#665](https://github.com/htacg/tidy-html5/issues/665)
+- Minify HTML [\#628](https://github.com/htacg/tidy-html5/issues/628)
+- Do not insert newlines into TEXT when wrapping! [\#625](https://github.com/htacg/tidy-html5/issues/625)
+- Configuration Options "cleanup" [\#609](https://github.com/htacg/tidy-html5/issues/609)
+- Next Release 5.6.0 [\#600](https://github.com/htacg/tidy-html5/issues/600)
+- anchor-as-name: false replaces name attribute of a form tag with id attribute [\#571](https://github.com/htacg/tidy-html5/issues/571)
+- Why does tidy format the '\<' and '\>' numeric operator? [\#485](https://github.com/htacg/tidy-html5/issues/485)
+- span with display: inline-block is treated as inline [\#448](https://github.com/htacg/tidy-html5/issues/448)
+- wrap-php multiple lines [\#437](https://github.com/htacg/tidy-html5/issues/437)
+- Option to always encode double ampersands [\#827](https://github.com/htacg/tidy-html5/issues/827)
+- \[ENH\] Add meta options to disable/enable cleanup and repair option [\#819](https://github.com/htacg/tidy-html5/issues/819)
+- --vertical-space yes adds too much after comment [\#811](https://github.com/htacg/tidy-html5/issues/811)
+- Line breaking on "|"  [\#810](https://github.com/htacg/tidy-html5/issues/810)
+- Installs library in /usr/local/lib/lib instead of /usr/local/lib [\#807](https://github.com/htacg/tidy-html5/issues/807)
+- Publishing in VS2015 - System.DllNotFoundException [\#804](https://github.com/htacg/tidy-html5/issues/804)
+- can not fix script async Attr to async="async" [\#799](https://github.com/htacg/tidy-html5/issues/799)
+- Feature Request: Omit boilerplate [\#795](https://github.com/htacg/tidy-html5/issues/795)
+- html conversion to xml leaves many tags unclosed [\#792](https://github.com/htacg/tidy-html5/issues/792)
+- NppTidy 5.6.0 quickref.html link broken - please fix [\#787](https://github.com/htacg/tidy-html5/issues/787)
+- Redundant blank lines when printing -help [\#781](https://github.com/htacg/tidy-html5/issues/781)
+- --css-prefix option no longer adds a hyphen to its built classes [\#777](https://github.com/htacg/tidy-html5/issues/777)
+- Build error on Android \(Termux\): unknown type name 'ulong' [\#773](https://github.com/htacg/tidy-html5/issues/773)
+- alter default config file processing [\#772](https://github.com/htacg/tidy-html5/issues/772)
+- Tidy output going to stderr [\#763](https://github.com/htacg/tidy-html5/issues/763)
+- --tidy-mark no inserts blank line [\#760](https://github.com/htacg/tidy-html5/issues/760)
+- tidy -access: \<doctype\> NOT missing [\#758](https://github.com/htacg/tidy-html5/issues/758)
+- type qualifiers ignored on function return type \[-Werror=ignored-qualifiers\] [\#746](https://github.com/htacg/tidy-html5/issues/746)
+- tidy dies on unexpected character [\#745](https://github.com/htacg/tidy-html5/issues/745)
+- tidy 5.6.0 warning `inserting missing 'title' element` appears in php-only files [\#728](https://github.com/htacg/tidy-html5/issues/728)
+- bug\(build\): tidyBufAppend\(&buf1, d-\>def, strlen\(d-\>def\)\); [\#721](https://github.com/htacg/tidy-html5/issues/721)
+- Allow specify ranges of code that do not get checked [\#720](https://github.com/htacg/tidy-html5/issues/720)
+- README/CONTRIBUTING.md [\#718](https://github.com/htacg/tidy-html5/issues/718)
+- tidy's error messages should include filename somewhere [\#713](https://github.com/htacg/tidy-html5/issues/713)
+- Tidy does not complain about valign in \<tr\>, \<th\> or \<td\> [\#711](https://github.com/htacg/tidy-html5/issues/711)
+- tidy converts '&' in query parameters \(&aen=true =\> &amp;aen=true\) in relative paths [\#710](https://github.com/htacg/tidy-html5/issues/710)
+- TidyHtml not working properly in C++ [\#707](https://github.com/htacg/tidy-html5/issues/707)
+- Unescaped `&` emitted despite using \*\*output-xhtml\*\* key bindings in 5.6.0 in PHP bindings [\#704](https://github.com/htacg/tidy-html5/issues/704)
+- How to ignore specific warnings [\#699](https://github.com/htacg/tidy-html5/issues/699)
+- Mention the need for a `:` before options' value in the configuration file [\#698](https://github.com/htacg/tidy-html5/issues/698)
+- Tidy 5.6.0 -\> bug with pre tag [\#690](https://github.com/htacg/tidy-html5/issues/690)
+- Is there any way to remove inline styles? [\#689](https://github.com/htacg/tidy-html5/issues/689)
+- feature request\(safari\): Pinned Tab Icons support [\#686](https://github.com/htacg/tidy-html5/issues/686)
+- Adopt Cygwin tidy package [\#680](https://github.com/htacg/tidy-html5/issues/680)
+- Clarification on releases / release tarballs missing [\#676](https://github.com/htacg/tidy-html5/issues/676)
+- --fix-uri no does not turn off check [\#675](https://github.com/htacg/tidy-html5/issues/675)
+- Unexpected behavior of 'add-xml-space' setting when used with 'wrap' =\> 0 and saveBuffer is called twice in tidy-html5 5.6.0 [\#673](https://github.com/htacg/tidy-html5/issues/673)
+- show-body-only [\#672](https://github.com/htacg/tidy-html5/issues/672)
+- Tidy deletes empty tags [\#669](https://github.com/htacg/tidy-html5/issues/669)
+- unbalanced \#endif's [\#663](https://github.com/htacg/tidy-html5/issues/663)
+- Feature request: option to replace inline styles with classes + `<style>` tag styles [\#638](https://github.com/htacg/tidy-html5/issues/638)
+- Windows 32-bit XP Release [\#568](https://github.com/htacg/tidy-html5/issues/568)
+- Release an updated HTML::Tidy perl library [\#562](https://github.com/htacg/tidy-html5/issues/562)
+- \<Script\> tag gets removed [\#528](https://github.com/htacg/tidy-html5/issues/528)
+- Word filtered html doesn't convert accents to utf8 [\#512](https://github.com/htacg/tidy-html5/issues/512)
+- option to ignore attribute-errors if attribute contains pseudo-elements [\#505](https://github.com/htacg/tidy-html5/issues/505)
+- Allow \<div\> inside \<pre\> [\#479](https://github.com/htacg/tidy-html5/issues/479)
+
+**Merged pull requests:**
+
+- Fixes \#743. [\#966](https://github.com/htacg/tidy-html5/pull/966) (@balthisar)
+- Fixed merge conflict; fixed non-build issue on macOS. RC for testing. [\#965](https://github.com/htacg/tidy-html5/pull/965) (@balthisar)
+- README.md: add Wikidata link [\#961](https://github.com/htacg/tidy-html5/pull/961) (@vitaly-zdanevich)
+- Fix issues with user-specified settings changing [\#959](https://github.com/htacg/tidy-html5/pull/959) (@balthisar)
+- Automated Testing [\#957](https://github.com/htacg/tidy-html5/pull/957) (@balthisar)
+- simple fix for the range of the condition. [\#953](https://github.com/htacg/tidy-html5/pull/953) (@ihsinme)
+- Add muted and playsinline video attributes for HTML5. [\#949](https://github.com/htacg/tidy-html5/pull/949) (@drichardson)
+- Add German Language [\#943](https://github.com/htacg/tidy-html5/pull/943) (@balthisar)
+- Link macOS console application with required plist [\#942](https://github.com/htacg/tidy-html5/pull/942) (@balthisar)
+- Is. \#839 -  new message for 'blank' title [\#930](https://github.com/htacg/tidy-html5/pull/930) (@geoffmcl)
+- Support extended color names in HTML 5 validation [\#914](https://github.com/htacg/tidy-html5/pull/914) (@cqcallaw)
+- Fix percentage validation in CheckLength [\#912](https://github.com/htacg/tidy-html5/pull/912) (@cqcallaw)
+- Add SVG paint attributes [\#907](https://github.com/htacg/tidy-html5/pull/907) (@cqcallaw)
+- Is. \#879: add loading attribute for img, iframe [\#902](https://github.com/htacg/tidy-html5/pull/902) (@sidvishnoi)
+- COMPILE\_FLAGS property only once per target, avoid overwriting. [\#886](https://github.com/htacg/tidy-html5/pull/886) (@SvenPStarFinanz)
+- Complete pt\_br translation [\#881](https://github.com/htacg/tidy-html5/pull/881) (@hugotiburtino)
+- Support the \<slot\> tag [\#848](https://github.com/htacg/tidy-html5/pull/848) (@lhchavez)
+- Issue \#437 - re-use of 'wrap-php' option [\#645](https://github.com/htacg/tidy-html5/pull/645) (@geoffmcl)
+- Change "tidyLocalMapItem" to "tidyLocaleMapItem" [\#829](https://github.com/htacg/tidy-html5/pull/829) (@MrSorcus)
+- added OS \_\_ANDROID\_\_ in tidyplatform.h [\#823](https://github.com/htacg/tidy-html5/pull/823) (@naveedpash)
+- Update BRANCHES.md [\#793](https://github.com/htacg/tidy-html5/pull/793) (@SConaway)
+- Is. \#783 - Fix language detection [\#785](https://github.com/htacg/tidy-html5/pull/785) (@Lin-Buo-Ren)
+- Is. \#781 - Drop redundant blank lines in -help [\#782](https://github.com/htacg/tidy-html5/pull/782) (@Lin-Buo-Ren)
+- Issue 649 adding tag \<data\> [\#769](https://github.com/htacg/tidy-html5/pull/769) (@AntoniosHadji)
+- Issue 752 [\#764](https://github.com/htacg/tidy-html5/pull/764) (@geoffmcl)
+- PHP ≥ 7.1.0 recognizes tidy-html5 [\#762](https://github.com/htacg/tidy-html5/pull/762) (@cmb69)
+- Fix typo [\#753](https://github.com/htacg/tidy-html5/pull/753) (@Lin-Buo-Ren)
+- Fix extra const modifier [\#747](https://github.com/htacg/tidy-html5/pull/747) (@drizt)
+- Is \#721 - cast away some gcc warnings [\#722](https://github.com/htacg/tidy-html5/pull/722) (@geoffmcl)
+- Doc nits [\#717](https://github.com/htacg/tidy-html5/pull/717) (@ler762)
+- Is \#709 - Improve message if 'implict' [\#714](https://github.com/htacg/tidy-html5/pull/714) (@geoffmcl)
+- Make global attribute `dir` accept auto as well. [\#712](https://github.com/htacg/tidy-html5/pull/712) (@doronbehar)
+- Is \#697 - Add NOWRAP to print of pre tag [\#708](https://github.com/htacg/tidy-html5/pull/708) (@geoffmcl)
+- Is \#700 - change script parsing if in html5 mode [\#703](https://github.com/htacg/tidy-html5/pull/703) (@geoffmcl)
+- Issue 698 - docs update [\#702](https://github.com/htacg/tidy-html5/pull/702) (@geoffmcl)
+- Is \#686 - Add attr COLOR to W3CAttrsFor\_LINK [\#701](https://github.com/htacg/tidy-html5/pull/701) (@geoffmcl)
+- Issue 679 [\#695](https://github.com/htacg/tidy-html5/pull/695) (@geoffmcl)
+- Issue 663 - fixes for Haiku port [\#664](https://github.com/htacg/tidy-html5/pull/664) (@geoffmcl)
+
+\* *This Changelog was automatically generated by [github_changelog_generator](https://github.com/github-changelog-generator/github-changelog-generator)*

README/CODESTYLE.md

@@ -0,0 +1,27 @@
+# HTML Tidy Code Style
+
+The source code of **libTidy** and console app **tidy** mostly follow the preferences of the original maintainers. Perhaps some of these decisions were arbitrary and based on their sense of aesthetics at the time, but it is good to have all the code looking the same even if it is not exactly what everyone would prefer.
+
+Developers adding code to HTML Tidy are urged to try to follow the existing code style. Code that does not follow these conventions may be accepted, but may be modified as time goes by to best fit the “Tidy Style.”
+
+There has been a suggestion of using available utilities to make the style consistent, like [Uncrustify](https://github.com/uncrustify/uncrustify) - see [issue #245](https://github.com/htacg/tidy-html5/issues/245), and maybe others.
+
+Others have suggested the [AStyle](http://astyle.sourceforge.net/) formatting program with say `-taOHUKk3 -M8` arguments, to conform, but there are a few bugs in AStyle.
+
+But again, these and other tools may not produce code that everybody agrees with, and are presently not formally used in Tidy!
+
+#### Known Conventions
+
+From reading of the Tidy source, some things are self evident,  in no particular order...
+
+ - Use of 4-space indenting, and no tabs.
+ - No C++ single line comments using `//`.
+ - The opening `{` is indented on the next newline.
+ - While the maximum code line length varies, generally long `if`, `while`, ... statements are wrapped to newlines.
+ - Pointer operators in declarations must precede any macro documentation, e.g, `const tidyLocaleMapItem* TIDY_CALL getNextWindowsLanguage( TidyIterator* iter )` instead of `const tidyLocaleMapItem TIDY_CALL *getNextWindowsLanguage( TidyIterator* iter )` in case `TIDY_CALL` is defined.
+
+
+
+Look forward to this document being filled out in detail...
+
+Date: 20150904

README/CONTRIBUTING.md

@@ -0,0 +1,99 @@
+# Contributing to HTML Tidy
+
+So you want to contribute to Tidy? Fantastic! Here's a brief overview on how best to do so.
+
+### Support request
+
+If you are having trouble running console `Tidy`, or using the `LibTidy` API in your own project, then maybe the best places to get help is either via a comment in [Tidy Issues](https://github.com/htacg/tidy-html5/issues), or on the [Tidy Mail Archive](https://lists.w3.org/Archives/Public/html-tidy/) list.
+
+And please do a **search** using different **key** words - see [searching](https://help.github.com/articles/searching-issues-and-pull-requests/) - to make sure it is **not** a duplicate. If something similar has been discussed before, but you still feel this is **different**, then add that related reference in your post...
+
+In either place please start with a short subject to describe the issue. If it involves running Tidy on an html file, or if it’s an API question, make sure to include:
+
+  - the version: `$ tidy -v`
+  - what was the configuration used
+  - a small sample input
+  - the output
+  - the _expected_ output
+  - some sample code (if an API question).
+  
+This information will make replication of your issue much simpler for us.
+
+If you do add sample HTML input, then it can also be very helpful if that sample **passes** the W3C [validator](https://validator.w3.org/#validate_by_upload). Tidy attempts to follow all current W3C standards.
+
+If you are able to build tidy from [source](https://github.com/htacg/tidy-html5) (requires [CMake](https://cmake.org/download/)), and you can find the problem in the source code, then read on about how you can create a Pull Request (“PR”) to share your code and ideas.
+
+
+### What to change
+
+Here are some examples of things you might want to make a PR for:
+
+ - New features
+ - Bug fixes
+ - Inefficient blocks of code
+ - Memory problems
+ - Language translations
+
+If you have a more deeply-rooted problem with how the program is built or some of the stylistic decisions made in the code, it is best to [create an issue](https://github.com/htacg/tidy-html5/issues/new) before putting the effort into a pull request. The same goes for new features - it might be best to check the project's direction, existing pull requests, and currently open and closed issues first.
+
+Concerning the “Tidy Code Style,” checkout [CODESTYLE.md](CODESTYLE.md), but looking at existing code is the best way to get a good feel for the patterns we use.
+
+
+### Using Git appropriately
+
+ 1. Fork tidy to your own github account. Use top right `Fork` icon.
+ 2. Optional: Generate a SSH Key, and add it to your `https://github.com/<name>` settings, SSH and GPG keys
+ 3. Clone your own fork - `$ git clone git@github.com:<name>/tidy-html5.git [tidy-fork]` Or using `https`.
+ 4. Create a branch - `$ cd tidy-fork; $ git checkout -b <branch-name>`
+ 5. Edit, and commit your changes to this `branch` of your fork.
+ 6. Test your changes, and if appropriate run [regression](https://github.com/htacg/tidy-html5-tests/blob/next/README/RUNTESTS.md) tests.
+ 7. Publish the branch - `$ git push -u origin <branch-name.` - to your remote fork.
+ 8. Create a [Pull Request](https://help.github.com/articles/about-pull-requests/), a **PR**, here.
+ 9. Watch for comments, acceptance.
+
+Item 2., SSH Key, is optional, and only required if you want to use `clone git@github.com...`. And if you generate the ssh without a `passphrase`, things like `git push` can be done without a password. Just convenience. Alternatively you can use the `HTTPS` protocol...
+
+Concerning 5., editing and committing your changes, **generally** it is better to `commit` changes often, adding an appropriate commit message to each, like `$ git commit -m "Is. #NNN - reason for change" <file[s]>`. This also aids in the **PR** review. 
+
+But the situation varies. Like adding say an option, which can mean several files have to be edited, where it is likely appropriate to combine a considerable number of edits into one commit. There can be no hard and fast rules on this.
+
+Please note, if you want to change **multiple** things that don't depend on each other, use **different** `branches`, and make sure you check the `next` branch back out, before making more changes in a **new** branch name. That way we can take in each **change** separately, otherwise Github will **combine** all your branch commits into one **PR**. 
+
+See below on keeping your forks `next` fully in sync with here, called `upstream` - **this is important**.
+
+```
+$ git remote add upstream git@github.com:htacg/tidy-html5.git # once only
+$ git checkout next
+$ git status
+$ git stash # if not clean
+$ git fetch upstream
+$ git rebase upstream/next
+$ git stash pop # if required, and fix conflicts
+$ git push      # update the fork next
+```
+
+This has to be repeated for other branches, too. `$ git checkout <your-branch>`, `$ git rebase next`, fix conflict, if any, and `$ git push`, for **each** branch. It is **not** fun to keep multiple `branches` fully up-to-date with an active `upstream`...
+
+Of course, the **regression** tests, 6., are really only if you have made `code` changes, but it is a good habit to get into. As can be seen the `tests` are in a **separate** repo, so you must also clone that, or **fork** and clone that, to be able to present a **PR**. This is best done in the same `root` folder where where you cloned `tidy-html5`, and your `tidy-fork`. See [RUNTESTS.md](https://github.com/htacg/tidy-html5-tests/blob/next/README/RUNTESTS.md).
+
+In brief, for unix, to use your potentially **new** `tidy-fork` tidy executable -
+
+```
+$ git clone git@github.com:htacg/tidy-html5-tests.git
+$ cd tidy-html5-tests/tools-sh
+$ ./testall.sh ../../tidy-fork/build/cmake/tidy
+$ diff -u ../cases/testbase-expects ../cases/testbase-results
+```
+
+Use folder `tools-cmd` for windows. Run `alltest.bat --help`. 
+
+If the `tests` shows a different exit value, or there are differences between the `expects` and `results`, these **must** be studied, and checked, very carefully. There may be cases where the **new** `results` are correct, in which case a simultaneous **PR** for the forked `tests` **must** be created to match your forked source **PR**.
+
+Do **NOT** change either the root `version.txt` here, nor the `cases/_version.txt` in `tests`. This will be handled by the person that does the **PR** merge. To differentiate your modified `tidy` there is a cmake option, like `-DTIDY_RC_NUMBER=I123`, which will appear in `tidy -v` as `5.7.16.I123`. The number can be anything, but using the relevant issue value is a good choice.
+
+Add an `issue` if you need further **help**... thanks...
+
+### Help Tidy Get Better
+
+It goes without saying **all help is appreciated**. We need to work together to make Tidy better!
+

README/LICENSE.md

@@ -2,11 +2,24 @@
 
 ## HTML parser and pretty printer
 
-Copyright (c) 1998-2003 World Wide Web Consortium
+Copyright (c) 1998-2016 World Wide Web Consortium
 (Massachusetts Institute of Technology, European Research 
 Consortium for Informatics and Mathematics, Keio University).
 All Rights Reserved.
 
+Additional contributions (c) 2001-2016 University of Toronto, Terry Teague, 
+@geoffmcl, HTACG, and others.
+
+### Contributing Author(s):
+
+  Dave Raggett <dsr@w3.org>
+
+The contributing author(s) would like to thank all those who
+helped with testing, bug fixes and suggestions for improvements. 
+This wouldn't have been possible without your help.
+
+## COPYRIGHT NOTICE:
+
 This software and documentation is provided "as is," and
 the copyright holders and contributing author(s) make no
 representations or warranties, express or implied, including

README/LICENSE.txt

@@ -0,0 +1,50 @@
+# HTML Tidy
+
+## HTML parser and pretty printer
+
+Copyright (c) 1998-2016 World Wide Web Consortium
+(Massachusetts Institute of Technology, European Research 
+Consortium for Informatics and Mathematics, Keio University).
+All Rights Reserved.
+
+Additional contributions (c) 2001-2016 University of Toronto, Terry Teague, 
+@geoffmcl, HTACG, and others.
+
+### Contributing Author(s):
+
+  Dave Raggett <dsr@w3.org>
+
+The contributing author(s) would like to thank all those who
+helped with testing, bug fixes and suggestions for improvements. 
+This wouldn't have been possible without your help.
+
+## COPYRIGHT NOTICE:
+
+This software and documentation is provided "as is," and
+the copyright holders and contributing author(s) make no
+representations or warranties, express or implied, including
+but not limited to, warranties of merchantability or fitness
+for any particular purpose or that the use of the software or
+documentation will not infringe any third party patents,
+copyrights, trademarks or other rights. 
+
+The copyright holders and contributing author(s) will not be held
+liable for any direct, indirect, special or consequential damages
+arising out of any use of the software or documentation, even if
+advised of the possibility of such damage.
+
+Permission is hereby granted to use, copy, modify, and distribute
+this source code, or portions hereof, documentation and executables,
+for any purpose, without fee, subject to the following restrictions:
+
+1. The origin of this source code must not be misrepresented.
+2. Altered versions must be plainly marked as such and must
+not be misrepresented as being the original source.
+3. This Copyright notice may not be removed or altered from any
+source or altered source distribution.
+
+The copyright holders and contributing author(s) specifically
+permit, without fee, and encourage the use of this source code
+as a component for supporting the Hypertext Markup Language in
+commercial products. If you use this source code in a product,
+acknowledgement is not required but would be appreciated.

README/LOCALIZE.md

@@ -0,0 +1,19 @@
+# Localize HTML Tidy
+
+HTML Tidy is used worldwide but is not very friendly to non-English speakers.
+The latest versions of HTML Tidy and `libtidy` now support other languages and
+regional variations, but we need your help to make it accessible to these users
+by using your knowledge of other languages to make Tidy better.
+
+Help us translate HTML Tidy into another language and as part of our project
+team you will certainly earn the admiration of fellow Tidy users worldwide.
+
+
+## How to Contribute
+
+All READMEs (including [instructions][2] on how to localize Tidy) and related 
+materials can be found in [localize][1].
+
+ [1]: ../localize
+ [2]: ../localize/README.md
+ 

README/MESSAGES.md

@@ -0,0 +1,41 @@
+# Message System
+
+Tidy has a quite complex warning/error report and footnote messaging system, but most of this complexity is completely hidden away from you in order to make adding messages as simple as possible. This particular README instructs you how to add a new warning/error report to **libTidy**.
+
+First assign the message a **key** value. This is done in `tidyenum.h`, in one of the two enumerations that are listed there.
+
+ 1. `tidyStrings` - starts with the value `TIDYSTRINGS_FIRST = 500`, and it must be first. This is the list of all strings available in Tidy with the exception of strings provided by other enumerations. **However** don't modify this enum directly. You'll modify a preprocessor macro instead.
+ 
+ 2. `TidyOptionId` - You probably won't need this unless you're adding new options, and there's another readme for that.
+ 
+ 3. `TidyConfigCategory` - You probably won't need this, either, unless you're adding a whole new category for options.
+ 
+ 4. `TidyReportLevel` - And you probably won't need this, either.
+
+All enum values are only ever used by name within **libTidy** (and incidentally, should only ever be used by name in your client applications; never trust the value!), so feel free to enter new strings in English alphabetical order (this helps us audit all of the strings from time to time). 
+
+As mentioned above, `tidyStrings` messages must be defined in one of the existing macros named like `FOREACH_...(FN)`, such as `FOREACH_DIALOG_MSG(FN)`. These macros ensure that another data structure used for localization and key lookup is updated automatically any time strings are added or removed, thus limiting the possibility of developer error.
+
+
+## Step 1
+
+So in this case I want to add 3 warning messages: `BAD_SURROGATE_PAIR`, `BAD_SURROGATE_TAIL`, and `BAD_SURROGATE_LEAD`. Because these are error reports, they belong in the `tidyStrings` enum, and they fit into nicely into the macro beginning `FOREACH_REPORT_MSG(FN)`. Add the message key values into this macro, ensuring they are nested in the `FN()` syntax.
+
+
+## Step 2
+
+The next step is adding a `format` string to `language_en.h`. This string may later be translated to various supported language strings, but even if you wish to support another language, it’s critical that you add the message format string to `language_en.h`, which serves as the base language for `LibTidy`.
+
+Where to add this seems a bit of a mess, but in general things are grouped by where they're used in `libTidy`, and often in alphabetical order within those groups. Here I've added them in alphabetical order in the section where all of the other report messages are.
+
+Depending on which of the output routines you use (consult `message.c`) you may be able to use parameters such as `%u` and `%s` in your format strings. The available data is currently limited to the available message output routines. Please don't use `printf` for message output within **libTidy**.
+
+Note that Tidy doesn't currently support numbered `printf` parameters; parameters will be consumed in the order the report output function calls them.
+
+## Step 3
+
+The last step — hopefully — is adding the message key to the `dispatchTable[]` structure in `message.c`. This structure determines the `TidyReportLevel` (report severity) and message formatter (how to print the message). Then whenever you issue the report with `TY_(Report)()` or one of the existing convenience report functions, the correct message formatter will be used for the parameters that you specify.
+
+Please read the source code in `message.c` for help on how to choose a message formatter, or how to modify one of the existing message formatters if you need to accommodate a new function signature for your report.
+
+eof;

README/OPTIONS.md

@@ -0,0 +1,134 @@
+# Tidy Config Options
+
+Tidy supports a quite large number of configuration options. The full list can be output using `-help-config`. This will show the option to be used either on the command line or in a configuration file, the type of option, and the value(s) that can be used. The current default value for each option can be seen using `-show-config`.
+
+The options can also be listed in xml format. `-xml-help` will output each option plus a description. `-xml-config` will not only output the option and a description, but will include the type, default and examples. These xml outputs are used, with the aid of `xsltproc` and `doxygen`, to generate the [API Documentation](https://api.html-tidy.org/).
+
+These options can also be used by application linking with `libtidy`. For each option there is a `TidyOptionId` enumeration in the `tidyenum.h` file, and get/set functions for each option type.
+
+This file indicates how to add a new option to tidy, here adding an option `TidyEscapeScripts`. In essence it consists of 4 steps:
+
+ 1. Add the option `ID` to `tidyenum.h`.
+ 2. Add to the `table` `TidyOptionImpl option_defs[]` in `config.c`
+ 3. Add the id, with a `description` to `language_en.h`
+ 4. Use the option in the code.
+ 
+#### 1. Option ID
+
+In `tidyenum.h` the `TidyOptionId` can be in any order, but please try to keep things alphabetical, and keep in mind that `N_TIDY_OPTIONS` must remain the last. Choosing the id name can be any string, but by convention it will commence with `Tidy` followed by brief descriptive text.
+
+Naturally it can not be the same as any existing option. That is, it must be unique. And it will be followed by a brief descriptive special doxygen formatted comment. So for this new option I have chosen -
+
+~~~
+  TidyEscapeScripts,       /**< Escape items that look like closing tags */
+~~~
+
+#### 2. Table Definition
+
+In `config.c`, added in `TidyOptionImpl option_defs[]`. Again it can be in any order, but normally a new option would be added just before the last `N_TIDY_OPTIONS`, which must remain the last.
+
+The structure definition of the table entries is simple -
+
+~~~
+struct _tidy_option
+{
+    TidyOptionId        id;
+    TidyConfigCategory  category;   /* put 'em in groups */
+    ctmbstr             name;       /* property name */
+    TidyOptionType      type;       /* string, int or bool */
+    ulong               dflt;       /* default for TidyInteger and TidyBoolean */
+    ParseProperty*      parser;     /* parsing method, read-only if NULL */
+    PickListItems*      pickList;   /* pick list */
+    ctmbstr             pdflt;      /* default for TidyString */
+};
+~~~
+
+Naturally it will commence with the above chosen unique `id`.
+
+The `category` will be one of this enumeration -
+
+~~~
+typedef enum
+{
+  TidyMarkup,          /**< Markup options: (X)HTML version, etc */
+  TidyDiagnostics,     /**< Diagnostics */
+  TidyPrettyPrint,     /**< Output layout */
+  TidyEncoding,        /**< Character encodings */
+  TidyMiscellaneous,   /**< File handling, message format, etc. */
+  TidyInternalCategory /**< Option is internal only. */
+} TidyConfigCategory;
+~~~
+
+Care, each of these enumeration strings have been equated to 2 uppercase letters. If you feel there should be another `category` or group then this can be discussed, and added.
+
+The `name` can be anything, but should try to be somewhat descriptive of the option. Again this string must be unique. It should be lowercase alphanumeric characters, and can contain a `-` separator. Remember this is the name places on the command line, or in a configuration file to set the option.
+
+The `type` is one of the following enumeration items -
+
+~~~
+typedef enum
+{
+  TidyString,          /**< String */
+  TidyInteger,         /**< Integer or enumeration */
+  TidyBoolean          /**< Boolean flag */
+} TidyOptionType;
+~~~
+
+Care, each of these enumeration strings have been equated to two uppercase letters. If you feel there should be another `type` then this can be discussed, but would require other additional things. And also note the `TidyTriState` is the same as a `TidyInteger` except uses its own parser.
+
+The next item is the `default` value for a boolean, tristate or integer. Note tidy set `no=0` and `yes=1` as its own `Bool` enumeration.
+
+There are a number of `parser` for the options. Likewise a number of `pickList`. Find another option similar to your new option and use the same values. The `parser` is the function that parses config file or command line text input, and the `picklist` constitutes the canonical values for the option. Some types of values logically don't have picklists, such as strings or pure integers.
+
+Presently no options have the final `default` string, and it is left out of the table. The compiler will add a NULL.
+
+The final table entry added. Note in here the spacing has been compressed, but in the actual code the current column settings should be maintained if possible -
+
+~~~
+  { TidyEscapeScripts, PP, "escape-scripts", BL, yes, ParseBool, boolPicks[, NULL] }, /* 20160227 - Issue #348 */
+~~~
+
+#### 3. Option Description
+
+In `language_en.h`, in the section labelled **Options Documentation**. Please try to keep this in alphabetical order.
+
+Each entry is a structure with 3 members -
+~~~
+typedef struct languageDictionaryEntry {
+    uint key;
+    uint pluralForm;
+    ctmbstr value;
+} languageDictionaryEntry;
+~~~
+
+The `key` is the option `ID`; The `pluralForm` is not used for options, and should be `0`; The `value` is the description string.
+
+Some care has to be taken with the description string. The only html allowed here is `<code>...</code>`, `<var>...</var>`, `<em>...</em>`, `<strong>...</strong>`, and `<br/>`. Entities, tags, attributes, etc., should be enclosed in `<code>...</code>`. Option values should be enclosed in `<var>...</var>`. It's very important that `<br/>` be self-closing! This string is processed to build the API documentation.
+
+This is the description added for this new option.
+
+~~~
+    {
+      TidyEscapeScripts,          0,
+        "This option causes items that look like closing tags, like <code>&lt;/g</code> to be "
+        "escaped to <code>&lt;\\/g</code>. Set this option to 'no' if you do not want this."
+    },
+~~~
+
+#### 4. Use in Code
+
+This can be added anywhere in the code to change the current code action. While the testing of the option depends on the option type, the most common is `cfgBool( doc, id )`. Here is an example of where this new option is used -
+
+~~~
+    /*\ if javascript insert backslash before / 
+     *  Issue #348 - Add option, escape-scripts, to skip
+    \*/
+    if ((TY_(IsJavaScript)(container)) && cfgBool(doc, TidyEscapeScripts))
+    {
+~~~
+
+#### Summary
+
+That's about it. Just 4 places. Obviously the best idea it to search for an existing option `ID`, and follow where it is all defined and used, and copy that. It is not difficult.
+
+; eof 20160310

README/README.html

@@ -0,0 +1,57 @@
+<h1 id="htacghtmltidy">HTACG HTML Tidy</h1>
+
+<h2 id="prerequisites">Prerequisites</h2>
+
+<ol>
+<li><p>git - <a href="https://git-scm.com/book/en/v2/Getting-Started-Installing-Git">https://git-scm.com/book/en/v2/Getting-Started-Installing-Git</a></p></li>
+<li><p>cmake - <a href="https://cmake.org/download/">https://cmake.org/download/</a></p></li>
+<li><p>appropriate build tools for the platform</p></li>
+<li><p>the <a href="http://xmlsoft.org/XSLT/xsltproc2.html">xsltproc</a> tool is required to build and install the <code>tidy.1</code> man page on Unix-like platforms.</p></li>
+</ol>
+
+<p>CMake comes in two forms - command line and GUI. Some installations only install one or the other, but sometimes both. The build commands below are only for command line use.</p>
+
+<p>Also the actual build tools vary for each platform. But that is one of the great features of CMake, it can generate various &#8216;native&#8217; build files. Running <code>cmake --help</code> should list the generators available on that platform. For sure one of the common ones is &#8220;Unix Makefiles&#8221;, which needs autotools make installed, but many other generators are supported.</p>
+
+<p>In Windows CMake offers various versions for MSVC. Again below only the command line use of MSVC is shown, but the tidy solution (*.sln) file can be loaded into the MSVC IDE, and the building done in there.</p>
+
+<h2 id="buildthetidylibraryandcommandlinetool">Build the tidy library and command line tool</h2>
+
+<ol>
+<li><p><code>cd build/cmake</code></p></li>
+<li><p><code>cmake ../.. -DCMAKE_BUILD_TYPE=Release [-DCMAKE_INSTALL_PREFIX=/path/for/install]</code></p></li>
+<li><p>Windows: <code>cmake --build . --config Release</code><br/>
+ Unix/OS X: <code>make</code></p></li>
+<li><p>Install, if desired:<br/>
+ Windows: <code>cmake --build . --config Release --target INSTALL</code><br/>
+ Unix/OS X: <code>[sudo] make install</code></p></li>
+</ol>
+
+<p>By default cmake sets the install path to <code>/usr/local/bin</code> in Unix. If you wanted the binary in say <code>/usr/bin</code> instead, then in 2. above use <code>-DCMAKE_INSTALL_PREFIX=/usr</code>.</p>
+
+<p>Also, in Unix if you want to build the release library without any debug <code>assert</code> in the code then add <code>-DCMAKE_BUILD_TYPE=Release</code> in step 2. This adds a <code>-DNDEBUG</code> macro to the compile switches. This is normally added in windows build for the <code>Release</code> config.</p>
+
+<p>In Windows the default install is to <code>C:\Program Files\tidy</code>, or <code>C:/Program Files (x86)/tidy</code>, which is not very useful. After the build the <code>tidy.exe</code> is in the <code>Release</code> directory, and can be copied to any directory in your <code>PATH</code> environment variable for global use.</p>
+
+<p>If you do <strong>not</strong> need the tidy library built as a &#8216;shared&#8217; (DLL) library, then in 2. add the command <code>-DBUILD_SHARED_LIB:BOOL=OFF</code>. This option is <strong>ON</strong> by default. The static library is always built and linked with the command line tool for convenience in Windows, and so the binary can be run as part of the man page build without the shared library being installed in unix.</p>
+
+<p>See the <code>CMakeLists.txt</code> file for other CMake <strong>options</strong> offered.</p>
+
+<h2 id="buildphpwiththetidy-html5library">Build PHP with the tidy-html5 library</h2>
+
+<p>Due to API changes in the PHP source, <code>buffio.h</code> needs to be renamed to <code>tidybuffio.h</code> in the file <code>ext/tidy/tidy.c</code> in PHP&#8217;s source.</p>
+
+<p>That is - prior to configuring PHP run this in the PHP source directory:
+<code>
+sed -i 's/buffio.h/tidybuffio.h/' ext/tidy/*.c
+</code></p>
+
+<p>And then continue with (just an example here, use your own PHP config options):</p>
+
+<pre><code>./configure --with-tidy=/usr/local
+make
+make test
+make install
+</code></pre>
+
+<p>; eof</p>

README/RELEASE.md

@@ -0,0 +1,186 @@
+HTML Tidy Release Process Single Point Lesson (SPL)
+===================================================
+
+Purpose
+-------
+This lesson documents how to release a new, officially released version of HTML Tidy. Following the steps in this SPL ensures consistency between releases and results in a predictable experience for the end users of HTML Tidy.
+
+
+Definition
+----------
+HTACG HTML Tidy is a library and console application, and the release process is intended to officially designate a point of stability, where "stability" is ABI and API stability. "Stability" is represented by an even minor version number, and "released" means the HTACG has published and made available an even minor version number version of HTML Tidy.
+
+Due to the number of platforms and language bindings which have adopted HTML Tidy, we are highly dependent on package managers to track the latest release versions of HTML Tidy, and release it on these other platforms. We cannot maintain distributions and language bindings for your favorite operating system or language package manager.
+
+
+Release Process Overview
+------------------------
+The release process consists largely of the following steps:
+
+### Lead up:
+
+ - Create the next release milestone on Github if not already done.
+ - Decide on PR's to include in the release, bumping version.txt, accordingly.
+ - Decide on any show-stopper outstanding issues, and action them.
+ - Change milestone of all excluded-this-time issues to the next milestone, or to indefinite.
+ - Decide target date for release.
+
+### Release:
+
+- Update the version number to the next release version, e.g., from 5.5.xx to 5.6.0.
+- Generate a change log.
+- Push this change to `next`.
+- Merge this branch to `master`.
+- Tag the release on `master`.
+- Update the version number of the `next` branch to the next development version, e.g., from 5.8.0 to 5.9.0. At this point, both versions are identical except for the version number.
+- Generate the API documentation for `next`.
+- Generate the API documentation for `master`.
+- Update the https://api.html-tidy.org/ website with the new API documentation.
+- Update the https://www.html-tidy.org/ website with the new release version.
+- Update the https://binaries.html-tidy.org/ website.
+- Push all of the changes.
+- Build binaries.
+- Create a Github release per the Git tag created above.
+- Post the binaries in the release.
+
+
+Release Steps in Detail
+--------------------------
+
+### Update the version number to the next release version
+
+In the `next` branch, modify the `version.txt` file to the next release version, for example, 5.8.0, and set the date.
+
+
+### Generate a change log
+
+If necessary, install the `github_changelog_generator`. This requires that you have a Ruby environment on your computer, which you probably do because the regression tests require it.
+
+~~~
+gem install github_changelog_generator
+~~~
+
+You’ll also need a Github personal access token in order for the tool to pull information from Github. You can acquire one [here](https://github.com/settings/tokens).
+
+Generate the change log like so:
+
+~~~
+github_changelog_generator -u htacg -p tidy-html5 \
+   --token [github_access_token] \
+   --since-tag 5.6.0 \
+   --usernames-as-github-logins \
+   --future-release 5.8.0 \
+   -o README/CHANGELOG.md
+~~~
+
+**Important**: the `--since-tag` value should be the git tag of the previous release, because we're only interested in the changes since then. The `--future-release` value should be the git tag that you _will apply_ (but have not yet) for this release.
+
+
+### Commit this change to `next`
+
+~~~
+git add .
+git commit -m 'Releasing HTML Tidy 5.8.0'
+~~~
+
+
+### Merge this branch to `master`
+
+~~~
+git checkout master
+git merge next
+~~~
+
+
+### Tag the release on `master`
+
+~~~
+git tag -a 5.8.0 -m "HTML Tidy version 5.8.0"
+~~~
+
+
+### Update the version number of the `next` branch
+
+For example, from from 5.8.0 to 5.9.0. At this point, both versions are identical except for the version number. Edit the `version.txt` file to make this change, and then
+commit it to the repository.
+
+### Generate the API documentation for `next`
+
+First, build the `next` binary in `build/cmake`, so that API documentation tools have a correct version of HTML Tidy to work with. Perform a `git clean -xdf` in this directory prior to building for good measure.
+
+After building, `cd` to the correct directory and build the documentation:
+
+~~~
+cd html-tidy.org.api/tidy-html5-doxygen
+./build_docs.sh
+~~~
+
+Then in the `html-tidy.org.api/tidy-html5-doxygen/output` directory, rename the resulting directory and file to `tidylib_api_next/` and `quickref_next.html`, and move them into `html-tidy.org.api/tidy/`.
+
+
+### Generate the API documentation for `master`
+
+First, checkout `master` build the binary in `build/cmake`, so that API documentation tools have a correct version of HTML Tidy to work with. Perform a `git clean -xdf` in this directory prior to building for good measure.
+
+After building, `cd` to the correct directory and build the documentation:
+
+~~~
+cd html-tidy.org.api/tidy-html5-doxygen
+./build_docs.sh
+~~~
+
+Move the resulting directory and file into `html-tidy.org.api/tidy/` directly.
+
+### Update the https://api.html-tidy.org/ website with the new API documentation
+
+Check the copyright dates in `_includes/footer.md`.
+
+~~~
+cd html-tidy.org.api/
+git add .
+git commit -m "Added API documentation for master and next."
+git push
+~~~
+
+### Update the https://www.html-tidy.org/ website with the new release version
+
+Check the copyright dates in `_includes/footer.md`.
+
+Update `html-tidy.org/homepage/_posts/1970-01-01-htmltidy.md` for the current release version and release year.
+
+~~~
+cd html-tidy.org/
+git add .
+git commit -m "Added API documentation for master and next."
+git push
+~~~
+
+
+### Push all of the changes
+
+Back in `tidy-html5/`
+
+~~~
+git checkout master
+git push
+git push origin <tag_name>
+git checkout next
+git push
+~~~
+
+
+### Build binaries
+
+This is OS specific.
+
+### Create a Github release per the Git tag created above
+
+Do this on Github.
+
+### Post the binaries in the release
+
+Post the binaries here.
+
+### Update the https://binaries.html-tidy.org/ website
+
+Modify the files to point to the binaries in the Github releases.

README/TAGS.md

@@ -0,0 +1,19 @@
+# Tidy HTML Elements
+
+This is about adding a new HTML **tag**.
+
+Tidy tries to support all **tags** supported by the W3C. To add a new supported **tag**, the definition begins in `tidyenum.h`, to give it a value. Then it is added to the `tag_defs[]` table in `tags.c`, where it is given a unique string, supported html versions, attributes support, and a bit `type`.
+
+Note, there are a group of configuration options to add **tags** not yet approved by the W3C. These are [new-blocklevel-tags](https://api.html-tidy.org/tidy/quickref_next.html#new-blocklevel-tags), [new-empty-tags](https://api.html-tidy.org/tidy/quickref_next.html#new-empty-tags), [new-inline-tags](https://api.html-tidy.org/tidy/quickref_next.html#new-inline-tags). and [new-pre-tags](https://api.html-tidy.org/tidy/quickref_next.html#new-pre-tags). This provides a way to extend the `tag_defs[]` table just for that tidy session.
+
+So, adding a new HTML **tag** consists of the following simple steps:
+
+ 1. `tidyenum.h` - Give the element an internal name, like `TidyTag_XXXX`, and thus a value. Please keep this list in alphabetical order.
+
+ 2. `tags.c` - Add a line to the `tag_defs[]` table. This assigns the unique string value of the element. Then the html versions that support the element, a pointer to the attributes supported by that elelment, and a bit field of the elements characteristics, inline, block, etc.
+ 
+So, just changing 2 files, `tidyenum.h` and `tags.c`, and libTidy will now support that element, tag, as W3C approved. Simple... And at times, there is some case for adding **tags** that are still in the `Working Draft` stage, especially when there has been wide spread support in the community, even before it reaches `REC` stage.
+
+Now, one could argue that this is not the **best** way to verify every attribute and value, for every tag, but that is a moot point - that is how tidy does it!
+
+; eof 20170205

README/TESTING.md

@@ -0,0 +1,72 @@
+# Testing
+
+It‘s critical that changes you introduce do not cause regressions, i.e., that
+Tidy’s output remains consistent with the introduction of your changes, except
+for very specific circumstances.
+
+Additionally, changes that you introduce to Tidy must usually be accompanied by
+one or more test cases demonstrating the new feature or changed behavior.
+
+Both of these concerns can be addressed with the Tidy repository’s automated
+regression testing features, which are enabled by Github Actions. Any pull
+request you make will automatically test your PR against the existing set of
+test cases, and any failures are prima facie grounds for rejecting the PR. 
+
+You _must_ test your changes locally using the tools and test cases provided in
+the `regression_testing/` directory prior to submitting a PR, including adding
+test cases to this directory as needed.
+
+
+## Changes to Existing Output
+
+If your changes affect existing output, it’s critical to understand _why_, and
+if necessary, regenerate the `-expects` files so that the regression testing
+tool will pass with your new changes. These `-expects` changes, of course,
+become part of your Pull Request, and will be subject to review and conversation
+in the Pull Request thread.
+
+If you do cause such regressions, please be prepared to defend why they are
+needed.
+
+## New Tests
+
+If you’re adding new features to Tidy, code reviewers need to be able to see the
+intended effect of your changes via some type of demonstration. As such, please
+write at least one test case in `github-cases` and put the expected results in
+`github-expects`. These also constitute a part of your Pull Request, and more
+importantly, will become part of the standard regression testing suite once the
+PR is merged.
+
+Try to keep your test case(s) as succinct as possible, and do try to put some HTML
+comments in the file explaining the purpose of the test case, and if applicable,
+the Github issue and/or PR number.
+
+Note that the files generated in `github-results` for your new test cases are
+suitable for use in `github-expects` when you are satisfied with the results.
+
+A sample `case-123a@0.html` might represent issue #123, test **a** in a series
+of multiple tests for this issue number, expecting Tidy exit code 0, and might
+look something like this:
+
+```
+<!DOCTYPE html>
+<html>
+<!--
+This test case represents HTML Tidy issue #123, and demonstrates
+the use of new feature #xxx. Tidy should exit with status code 0.
+The reason this change is needed is because WHATWG suddently
+determined that a standards change #yyyy impacts us because of zzz.
+ -->
+<head>
+<title>Case #123a</title>
+</head>
+<p>The quick brown fox jumps over the lazy dog.<//p>
+<body>
+</body>
+</html>
+```
+
+
+## Regression Testing Specifics
+
+The regression testing mechanism is described more fully in [regression_testing/README.md](../regression_testing/README.md).

README/VERSION.md

@@ -0,0 +1,103 @@
+# HTML Tidy Versioning
+
+This document provides an explanation of how to interpret HTML Tidy’s version number, e.g. from command line output as a result of `tidy -v`, and also addresses the role of the file `version.txt` in Tidy’s build process.
+
+## Background
+
+**HTML Tidy** uses a modified version of [Semantic Versioning](https://semver.org/), and so it’s important to understand what the version number of **HTML Tidy** means to you, and how it might impact your workflow.
+
+When you execute `tidy -v` on the command line, you might see responses such as:
+
+~~~
+HTML Tidy for Mac OS X version 5.1.24
+HTML Tidy for Mac OS X version 5.2.0
+HTML Tidy for Mac OS X version 5.3.15
+HTML Tidy for Mac OS X version 5.4.0
+HTML Tidy for Mac OS X version 5.5.1
+~~~
+
+_Obviously_ 5.5.1 is higher than 5.2.0, right? This might lead you to consider replacing your stable installations of **HTML Tidy** 5.2.0 across the board in your production process, but this might lead you to trouble. A little word about the meaning of our version numbers might help clear things up.
+
+## Major, Minor, Patch
+
+### Major
+
+When HTACG assumed responsibility of **HTML Tidy** from previous maintainers, we immediately declared that the first release would be version 5.0, in honor of finally being able to offer modern HTML5 support.
+
+Barring some major, monumental, massive change to Tidy, or the [release of HTML6](https://blog.whatwg.org/html-is-the-new-html5), **HTML Tidy** will probably be major version 5 forever. Maybe future maintainers will want to be trendy and release **HTML Tidy 2025**, but that’s for them to decide.
+
+### Minor
+
+The minor version tells a lot more about the true version of Tidy that you have, but even so it’s not a simple matter that 5 > 2 and must be better. The minor number indicates **HTML Tidy** _release versions_ or _development versions_.
+
+- **even numbered minor versions** indicate released versions of **HTML Tidy**. We provide binaries for releases, API documentation, and full support including cherry picking bug fixes back to them. In standard parlance, _released_ versions are _stable_ versions, meaning that the API is stable and you can generally expect Tidy’s output to be the same (other than as a result of bug fixes). 
+
+- **odd numbered minor versions** are development versions, or as is considered in many contexts _bleeding edge_ or _next_ versions. HTACG do not provide binaries, and API documentation is not usually up to date, but you do have access to the latest bug fixes, newest features, and knowledge of where Tidy is going. The downside, though, is that we make absolutely no guarantees that:
+
+  - Output remains the same as in previous release versions.
+  - Output remains the same as in earlier patch versions in the same development series.
+  - Configuration options may be added.
+  - Configuration options may be deleted.
+  - Parts of the C API may be added or deleted without warning.
+  - In short, development versions are bleeding edge and likely to be unstable (in the API sense -- we try never commit code that will crash).
+
+### Patch
+
+The patch indicates the latest version of the current minor version number. As with minor version numbers, there is some variation in their meaning:
+
+- **patches for even numbered minor versions** indicate whether the latest supported update for that released version. In general, we hope that the patch number remains at 0 forever, e.g., 5.2.0. However if we do backport one or more bug fixes, you might see, e.g., 5.2.1.
+
+- **patches for odd numbered minor versions** indicate our progress in committing code that changes some aspect of **HTML Tidy**’s operation, such as the output it generates or a bug fix. Because **git** offers robust commit logging of its own, we won't generally bump the patch number for things such as documenting code, converting tabs to space, or even simplifying some piece of logic. You’ll see that lots of good things are happening if the patch number is really large, e.g., 5.7.289!
+
+
+## Development
+
+### The `version.txt` File
+
+The **libTidy** version is controlled by the contents of `version.txt` in the root.
+
+This file consists of two lines of dot (.) separated items. The first being the **major**, **minor**, and **patch** version values, and the second string is a date. Example:
+
+~~~
+5.3.15
+2017.01.29
+~~~
+
+When **CMake** is run, this file is read and two macros are added to the compile flags:
+
+~~~
+add_definitions ( -DLIBTIDY_VERSION="${LIBTIDY_VERSION}" )
+add_definitions ( -DRELEASE_DATE="${tidy_YEAR}/${tidy_MONTH}/${tidy_DAY}" )
+~~~
+
+And in `CMakeLists.txt` there is the possibility to define another macro, when and if required:
+
+~~~
+# add_definitions ( -DRC_NUMBER="D231" )
+~~~
+
+These macros are put in `static const char` strings in **libTidys**’s internal- only `src/version.h` file:
+
+~~~
+static const char TY_(release_date)[] = RELEASE_DATE;
+#ifdef RC_NUMBER
+static const char TY_(library_version)[] = LIBTIDY_VERSION "." RC_NUMBER;
+#else
+static const char TY_(library_version)[] = LIBTIDY_VERSION;
+#endif
+~~~
+
+These strings are returned respectively by the **libTidy** API functions:
+
+~~~
+TIDY_EXPORT ctmbstr TIDY_CALL     tidyLibraryVersion(void);
+TIDY_EXPORT ctmbstr TIDY_CALL     tidyReleaseDate(void);
+~~~
+
+### Git branches
+
+Starting with HTML Tidy 5.4.0 release, our branching scheme aligns nicely with our version numbering scheme. Please consult [BRANCHES.md](BRANCHES.md).
+
+
+Updated: 20170210  
+   Date: 20150904

build/cmake/.gitignore

@@ -29,4 +29,9 @@ _CPack_Packages/*
 *.wixobj
 tidy
 libtidy*
-
+tidy1.xsl
+tidy.pc
+*.vcproj
+.pkg
+Info.plist
+*.pkg

build/cmake/build-api.sh

@@ -0,0 +1,89 @@
+#!/bin/sh
+#< build-api.sh - 20151020 - build the API documentation for publishing...
+BN=`basename $0`
+TMPSRC="../.."
+TMPFIL="$TMPSRC/version.txt"
+if [ ! -f "$TMPFIL" ]; then
+    echo "Can NOT locate $TMPFIL! *** FIX ME ***"
+    exit 1
+fi
+echo "$BN: Read file $TMPFIL"
+ls -l $TMPFIL
+
+TMPCNT=0
+while read LINE; do
+    if [ "$TMPCNT" = "0" ]; then
+        TMPVER="$LINE"
+    fi
+    TMPCNT=`expr $TMPCNT + 1`
+done <$TMPFIL
+#TMPVER=$(<$TMPFIL)
+#TMPVER=$(cat $TMPFIL)
+
+echo "$BN: Version $TMPVER"
+TMPZIP="tidylib_api-$TMPVER.zip"
+
+ask()
+{
+    pause
+    if [ ! "$?" = "0" ]; then
+        exit 1
+    fi
+}
+
+TMPDIR="../../documentation/temp"
+TMPZFIL="../../documentation/$TMPZIP"
+
+if [ -f "$TMPZFIL" ]; then
+    ls -l $TMPZFIL
+    echo "$BN: WARNING: Current ZIP will be overwritten!"
+    echo "$BN: DO you want to continue?"
+    ask
+fi
+
+TMPFIL="build-me.sh"
+if [ ! -x "$TMPFIL" ]; then
+    echo "$BN: Can NOT locate '$TMPFIL'! *** FIX ME ***"
+    echo "$BN: This is a simple build script, that accepts parameters..."
+    exit 1
+fi
+
+if [ -d "$TMPDIR" ]; then
+    echo "$BN: Directory '$TMPDIR' will be deleted prior the documentation build..."
+fi
+
+./$TMPFIL -DBUILD_DOCUMENTATION:BOOL=YES
+if [ ! "$?" = "0" ]; then
+    echo "$BN: The running of $TMPFIL failed! ????"
+    exit 1
+fi
+
+if [ -d "$TMPDIR" ]; then
+    echo "$BN: Deleting '$TMPDIR'..."
+    cd $TMPDIR
+    rm -rf *
+    cd -
+fi
+
+echo "$BN: Doing 'make documentation'..."
+make documentation
+
+if [ -d "$TMPDIR" ]; then
+    echo "$BN: Generated a new '$TMPDIR'..."
+    if [ -f "$TMPZFIL" ]; then
+        rm -fv $TMPZFIL
+    fi
+    cd $TMPDIR
+    echo "$BN: Generating ../$TMPZIP..."
+    zip -r ../$TMPZIP * >/dev/null
+    ls -l ../$TMPZIP
+    cd -
+else
+    echo "$BN: WARNING '$TMPDIR' not generated!"
+    exit 1
+fi
+
+exit 0
+
+# eof
+

build/cmake/build-bins.bat

@@ -1,3 +1,16 @@
 @setlocal
+@set TMPLOG=bldlog-p.txt
 
-cmake --build . --config Release --target PACKAGE
+@echo Running: 'cmake --build . --config Release --target PACKAGE' out to %TMPLOG%
+@echo Running: 'cmake --build . --config Release --target PACKAGE' > %TMPLOG%
+cmake --build . --config Release --target PACKAGE >> %TMPLOG%
+@if ERRORLEVEL 1 goto ISERR
+@echo Build package done... see %TMPLOG%
+@endlocal
+@exit /b 0
+
+:ISERR
+@endlocal
+@exit /b 1
+
+@REM eof

build/cmake/build-me.bat

@@ -1,27 +1,37 @@
 @setlocal
 
 @set TMPVER=1
-@set TMPPRJ=tidy5
+@set TMPPRJ=tidy
 @set TMPSRC=..\..
 @set TMPBGN=%TIME%
-@set TMPINS=..\..\..\software
-@set DOTINST=0
+@set TMPINS=D:\Projects\3rdParty
 @set TMPLOG=bldlog-1.txt
+@set DOPAUSE=1
+@set TMPGEN=Visual Studio 16 2019
+@set TMPBR=next
+@set TMPINDBG=0
 
-@set TMPOPTS=-DCMAKE_INSTALL_PREFIX=%TMPINS%
+@set TMPOPTS=-G "%TMPGEN%" -A Win32
+@set TMPOPTS=%TMPOPTS% -DCMAKE_INSTALL_PREFIX=%TMPINS%
 @set TMPOPTS=%TMPOPTS% -DBUILD_SHARED_LIB=ON
 
 :RPT
 @if "%~1x" == "x" goto GOTCMD
-@set TMPOPTS=%TMPOPTS% %1
+@if "%~1x" == "NOPAUSEx" (
+    @set DOPAUSE=0
+) else (
+    @set TMPOPTS=%TMPOPTS% %1
+)
 @shift
 @goto RPT
 :GOTCMD
 
 @call chkmsvc %TMPPRJ%
-@call chkbranch master
+@if "%TMPBR%x" == "x" goto DNBR
+@call chkbranch %TMPBR%
+:DNBR
 
-@echo Build %DATE% %TIME% > %TMPLOG%
+@echo Build %TMPPRJ% 32-bits %DATE% %TIME%, in %CD%, to  %TMPLOG% > %TMPLOG%
 
 @if NOT EXIST %TMPSRC%\nul goto NOSRC
 
@@ -34,51 +44,70 @@
 
 @if NOT EXIST %TMPSRC%\CMakeLists.txt goto NOCM
 
-cmake %TMPSRC% %TMPOPTS% >> %TMPLOG% 2>&1
+@echo Doing: 'cmake %TMPSRC% %TMPOPTS%'
+@echo Doing: 'cmake %TMPSRC% %TMPOPTS%' >> %TMPLOG% 2>&1
+@cmake %TMPSRC% %TMPOPTS% >> %TMPLOG% 2>&1
 @if ERRORLEVEL 1 goto ERR1
 
-cmake --build . --config Debug  >> %TMPLOG% 2>&1
+@echo Doing: 'cmake --build . --config Debug'
+@echo Doing: 'cmake --build . --config Debug'  >> %TMPLOG% 2>&1
+@cmake --build . --config Debug  >> %TMPLOG% 2>&1
 @if ERRORLEVEL 1 goto ERR2
 
-cmake --build . --config Release  >> %TMPLOG% 2>&1
+@echo Doing: 'cmake --build . --config Release'
+@echo Doing: 'cmake --build . --config Release'  >> %TMPLOG% 2>&1
+@cmake --build . --config Release  >> %TMPLOG% 2>&1
 @if ERRORLEVEL 1 goto ERR3
 
 @fa4 "***" %TMPLOG%
 @call elapsed %TMPBGN%
 @echo Appears a successful build... see %TMPLOG%
-
-@if "%DOTINST%x" == "0x" goto DNTINST
-@echo Building installation zips... moment...
-@call build-zips Debug
-@call build-zips Release
-@echo Done installation zips...
-:DNTINST
-
+@echo Note install location %TMPINS%
+@if "%TMPINDBG%x" == "1x" (
+@echo Will install Debug and Release
+) else {
+@echo Will only install Release
+)
 @echo.
-@REM echo No install at this time, but there is a updexe.bat to copy the EXE to c:\MDOS...
-@REM goto END
-
-@echo Continue with install? Only Ctrl+c aborts...
 
+@REM ##############################################
+@REM Check if should continue with install
+@REM ##############################################
+@if "%DOPAUSE%x" == "0x" goto DOINST
+@choice /? >nul 2>&1
+@if ERRORLEVEL 1 goto NOCHOICE
+@choice /D N /T 10 /M "Pausing for 10 seconds. Def=N"
+@if ERRORLEVEL 2 goto GOTNO
+@goto DOINST
+:NOCHOICE
+@echo Appears OS does not have the 'choice' command!
+@ask *** CONTINUE with install? *** Only y continues
+@if ERRORLEVEL 2 goto NOASK
+@if ERRORLEVEL 1 goto DOINST
+@echo Skipping install to %TMPINST% at this time...
+@echo.
+@goto END
+:NOASK
+@echo 'ask' utility not found in path...
+@echo.
+@echo *** CONTINUE with install? *** Only Ctrl+c aborts...
+@echo.
 @pause
 
-cmake --build . --config Debug  --target INSTALL >> %TMPLOG% 2>&1
+:DOINST
+@echo Proceeding with INSTALL...
+@echo.
+@if NOT "%TMPINDBG%x" == "1x" goto DNDBGIN
+@echo Doing: 'cmake --build . --config Debug  --target INSTALL'
+@echo Doing: 'cmake --build . --config Debug  --target INSTALL' >> %TMPLOG% 2>&1
+@cmake --build . --config Debug  --target INSTALL >> %TMPLOG% 2>&1
 @if ERRORLEVEL 1 goto ERR4
-@REM if EXIST install_manifest.txt (
-@REM copy install_manifest.txt install_manifest_dbg.txt >nul
-@REM echo. >> %TMPINS%/installed.txt
-@REM echo = %TMPRJ% Debug install %DATE% %TIME% >> %TMPINS%/installed.txt
-@REM type install_manifest.txt >> %TMPINS%/installed.txt
-@REM )
+:DNDBGIN
 
-cmake --build . --config Release  --target INSTALL >> %TMPLOG% 2>&1
+@echo Doing: 'cmake --build . --config Release  --target INSTALL'
+@echo Doing: 'cmake --build . --config Release  --target INSTALL' >> %TMPLOG% 2>&1
+@cmake --build . --config Release  --target INSTALL >> %TMPLOG% 2>&1
 @if ERRORLEVEL 1 goto ERR5
-@REM if EXIST install_manifest.txt (
-@REM copy install_manifest.txt install_manifest_rel.txt >nul
-@REM echo. >> %TMPINS%/installed.txt
-@REM echo = %TMPRJ% Release install %DATE% %TIME% >> %TMPINS%/installed.txt
-@REM type install_manifest.txt >> %TMPINS%/installed.txt
-@REM )
 
 @fa4 " -- " %TMPLOG%
 
@@ -87,6 +116,12 @@ cmake --build . --config Release  --target INSTALL >> %TMPLOG% 2>&1
 
 @goto END
 
+:GOTNO
+@echo.
+@echo No install at this time, but there may be an updexe.bat to copy the EXE to c:\MDOS...
+@echo.
+@goto END
+
 :NOSRC
 @echo Can NOT locate source %TMPSRC%! *** FIX ME ***
 @echo Can NOT locate source %TMPSRC%! *** FIX ME *** >> %TMPLOG%

build/cmake/cmake-clean.sh

@@ -0,0 +1,25 @@
+#!/bin/sh
+#< cmake-clean.sh for tidy - remove tidylib...
+
+FILES="libtidy*"
+TMPCNT=0
+
+for f in $FILES; do
+    TMPCNT=`expr $TMPCNT + 1`
+    echo "$TMPCNT: File $f"
+done
+
+echo "Will delete the above $TMPCNT files ater a 5 seconds sleep!"
+
+sleep 5
+
+echo "Deleting the above $TMPCNT files!"
+
+for f in $FILES; do
+    rm -fv $f
+done
+
+echo "all done..."
+
+# eof
+

build/cmake/cmake-clean.txt

@@ -26,4 +26,5 @@ libtidy.so.5
 libtidy.so.5.0.0
 tidy.1
 _CPack_Packages
-
+tidy1.xsl
+tidy.pc

build/cmake/gen-html.sh

@@ -0,0 +1,139 @@
+#!/bin/sh
+#< gen-html.sh 2021/03/26, from gen-html.bat
+BN=`basename $0`
+
+ask()
+{
+	pause
+	if [ ! "$?" = "0" ]; then
+		exit 1
+	fi
+}
+
+# @REM Build HTML from log of 'version.txt'
+# @REM Versify the tools used
+echo "$BN: Doing: 'verhist.pl -? >/dev/null'"
+verhist.pl -? >/dev/null
+if [ ! "$?" = "0" ]; then
+    echo "Unable to run 'verhist.pl'! *** FIX ME ***"
+    exit 1
+fi
+echo "$BN: Doing: 'emailobfuscate.pl -? >/dev/null'"
+emailobfuscate.pl -? >/dev/null
+if [ ! "$?" = "0" ]; then
+    echo "Unable to run 'emailobfuscate.pl'! *** FIX ME ***"
+    exit 1
+fi
+
+TMPFIL1="../../version.txt"
+if [ ! -f "$TMPFIL1" ]; then
+    echo "Can NOT locate $TMPFIL1, in $(pwd) - *** FIX ME ***"
+    exit 1
+fi
+
+echo "$BN: Doing: 'dirmin $TMPFIL1'"
+ls -l "$TMPFIL1"
+
+# TMPVER=$(cat $TMPFIL1)
+TMPCNT=0
+while read -r a; do
+	TMPCNT=`expr $TMPCNT + 1`;
+	if [ ! -z "$a" ]; then
+		echo "$TMPCNT: '$a'"
+		if [ "$TMPCNT" = "1" ]; then
+			export TMPVER="$a";
+		fi
+		break;
+	fi
+done < $TMPFIL1
+
+echo "Current version '$TMPVER' ..."
+TMPLOG1="../../../temp-$TMPVER.log"
+TMPLOG2="../../../temp2-$TMPVER.log"
+TMPLOG3="../../../temp3-$TMPVER.log"
+
+if [ ! -f "$TMPLOG1" ]; then
+echo "$BN: Doing: 'git log -p $TMPFIL1 > $TMPLOG1'"
+git log -p $TMPFIL1 > $TMPLOG1
+if [ ! -f "$TMPLOG1" ]; then
+echo "Gen of $TMPLOG1 FAILED! *** FIX ME ***"
+exit 1
+fi
+fi
+
+echo "$BN: Got log 1 '$TMPLOG1' ..."
+ls -l "$TMPLOG1"
+
+if [ ! -f "$TMPLOG2" ]; then
+echo "$BN: Doing: 'verhist.pl $TMPLOG1 -o $TMPLOG2'"
+verhist.pl $TMPLOG1 -o $TMPLOG2
+if [ ! -f "$TMPLOG2" ]; then
+echo "Gen of $TMPLOG2 FAILED! *** FIX ME ***"
+exit 1
+fi
+fi
+
+echo "$BN: Got log 2 '$TMPLOG2' ..."
+ls -l $TMPLOG2
+
+TMPV="$1"
+if [ -z "$TMPV" ]; then
+echo "Give the cut-off version, like 5.6.0, to continue.."
+exit 1
+fi
+
+echo "$BN: Doing: 'grep $TMPV $TMPLOG2'"
+grep $TMPV $TMPLOG2
+if [ ! "$?" = "0" ]; then
+echo "Failed to find '$TMPV'... check the file '$TMPLOG2'"
+exit 1
+fi
+
+TMPD="$2"
+if [ -z "$TMPD" ]; then
+echo "Give the DATE of the cut-off, like 'Sat Nov 25 14:50:00 2017 +0100', to continue..."
+exit 1
+fi
+
+if [ ! -f "$TMPLOG3" ]; then
+echo "$BN: Doing: 'git log "--decorate=full" "--since=$TMPD" > $TMPLOG3'"
+git log "--decorate=full" "--since=$TMPD" > $TMPLOG3
+if [ ! -f "$TMPLOG3" ]; then
+echo "Failed to generate 'git log ...' - *** FIX ME ***"
+exit 1
+fi
+fi
+
+echo "$BN: Got log 3 '$TMPLOG3' ..."
+ls -l "$TMPLOG3"
+
+# @REM at last generate the release HTML
+
+TMPHTM="../../../temp-$TMPVER.html"
+if [ ! -f "$TMPHTM" ]; then
+echo "$BN: Doing: 'emailobfuscate.pl $TMPLOG3 -o $TMPHTM -a $TMPVER -i'"
+emailobfuscate.pl $TMPLOG3 -o $TMPHTM -a $TMPVER -i
+if [ ! -f "$TMPHTM" ]; then
+echo "FAILED to generate $TMPHTM! *** FIX ME ***"
+exit 1
+fi
+fi
+
+echo "$BN: Got HTML file '$TMPHTM' ..."
+ls -l "$TMPHTM"
+
+echo "$BN: Generation appears ok, check file '$TMPHTM' in browser..."
+### start $TMPHTM
+TMPVFIL="../../README/verhist.log"
+if [ ! -f "$TMPVFIL" ]; then
+    echo ""
+    echo "$BN: *** WARNING *** - Missing existing '$TMPVFIL'"
+    echo ""
+fi
+echo ""
+echo "$BN: Is all OK, final actions, for release are -"
+echo "copy $TMPLOG2 to $TMPVFIL - push this to repo..."
+echo "copy $TMPHTM to the binaries repo..."
+echo ""
+
+# @REM eof

build/cmake/pub-bins.bat

@@ -2,16 +2,12 @@
 @set TMPWV=win32
 @set TMPSRC=../..
 @set TMPNAME=tidy
-
 @set TMPFIL=%TMPSRC%\version.txt
 @if NOT EXIST %TMPFIL% goto NOFIL
 @set /p TMPVER=<%TMPFIL%
 @set DOPAUSE=pause
-@echo Version %TMPVER%
 
-if "%1x" == "NOPAUSEx" (
-    set DOPAUSE=echo No pause requested...
-)
+@echo Version %TMPVER%
 
 @set TMPBIN=F:\Projects\tidy-bins
 @set TMPBINS=%TMPBIN%\binaries
@@ -22,17 +18,30 @@ if "%1x" == "NOPAUSEx" (
 @echo This is a NEW installation in %TMPDD%
 :GOTDST
 
+@if "%1x" == "NOPAUSEx" (
+@set DOPAUSE=echo No pause requested...
+)
+
+@echo Will publish...
+@set TMPCNT=0
 @set TMPFIL1=%TMPNAME%-%TMPVER%-%TMPWV%.exe
 @set TMPFIL2=%TMPNAME%-%TMPVER%-%TMPWV%.msi
 @set TMPFIL3=%TMPNAME%-%TMPVER%-%TMPWV%.zip
-@if NOT EXIST %TMPFIL1% goto NOFIL1
-@if NOT EXIST %TMPFIL2% goto NOFIL2
-@if NOT EXIST %TMPFIL3% goto NOFIL3
-@echo.
-@echo Will publish...
+@if EXIST %TMPFIL1% (
 @echo %TMPFIL1%
+@set /A TMPCNT+=1
+)
+@if EXIST %TMPFIL2% (
 @echo %TMPFIL2%
+@set /A TMPCNT+=1
+)
+@if EXIST %TMPFIL3% (
 @echo %TMPFIL3%
+@set /A TMPCNT+=1
+)
+@if "%TMPCNT%x" == "0x" goto NOPUB
+@echo.
+@echo Will publish %TMPCNT% files to %TMPDD%
 @echo.
 @echo *** CONTINUE?%
 @%DOPAUSE%
@@ -42,18 +51,25 @@ if "%1x" == "NOPAUSEx" (
 @if NOT EXIST %TMPDD%\nul goto NODST
 )
 
+@if EXIST %TMPFIL1% (
 @set TMPSRC=%TMPFIL1%
 @set TMPDST=%TMPDD%\%TMPFIL1%
 @call :CHKCOPY
+)
+
+@if EXIST %TMPFIL2% (
 @set TMPSRC=%TMPFIL2%
 @set TMPDST=%TMPDD%\%TMPFIL2%
 @call :CHKCOPY
+)
+
+@if EXIST %TMPFIL3% (
 @set TMPSRC=%TMPFIL3%
 @set TMPDST=%TMPDD%\%TMPFIL3%
 @call :CHKCOPY
-
+)
 @echo.
-@echo Maybe time to run 'gentidyyml %TMPBIN%'
+@echo If done all bins, WIN32, WIN64, linux, ... maybe time to run 'gentidyyml %TMPBIN%'
 @echo.
 
 @goto END
@@ -85,26 +101,20 @@ copy %TMPSRC% %TMPDST%
 @echo.
 @goto :EOF
 
+
+
 :NODST
 @echo Error: Unable to create %TMPDD%
 @goto END
 
+:NOPUB
+@echo Appears no files to PUBLISH!
 :NOFIL1
 @echo Can NOT locate %TMPFIL1%! *** FIX ME ***
-@goto CHKBB
-
 :NOFIL2
 @echo Can NOT locate %TMPFIL2%! *** FIX ME ***
-@goto CHKBB
-
 :NOFIL3
 @echo Can NOT locate %TMPFIL3%! *** FIX ME ***
-@goto CHKBB
-
-:CHKBB
-@echo.
-@echo Have you run build-bins.bat?
-@echo.
 @goto END
 
 

build/cmake/pub-bins.sh

@@ -11,11 +11,15 @@ fi
 echo "$BN: Read file $TMPFIL"
 ls -l $TMPFIL
 
-# while read LINE; do
-#    TMPVER="$LINE"
-#done <$TMPFIL
+TMPCNT=0
+while read LINE; do
+    if [ "$TMPCNT" = "0" ]; then
+        TMPVER="$LINE"
+    fi
+    TMPCNT=`expr $TMPCNT + 1`
+done <$TMPFIL
 #TMPVER=$(<$TMPFIL)
-TMPVER=$(cat $TMPFIL)
+#TMPVER=$(cat $TMPFIL)
 
 echo "$BN: Version $TMPVER"
 
@@ -28,20 +32,22 @@ ask()
 }
 
 
-TMPBIN="$HOME/projects/html_tidy/tidy-bin"
+TMPBIN="$HOME/projects/html_tidy/binaries"
 TMPBINS="$TMPBIN/binaries"
 if [ ! -d "$TMPBINS" ]; then
     echo "$BN: Can NOT location '$TMPBINS'! *** FIX ME ***"
     exit 1
 fi
 TMPDD="$TMPBINS/tidy-$TMPVER"
-if [ ! -d "$TMPDD" ]; then 
     echo ""
+if [ -d "$TMPDD" ]; then 
+    echo "$BN: Destination is $TMPDD"
+else
     echo "$BN: This is a NEW installation in $TMPDD"
 fi
 
-TMPFIL1="tidy5-$TMPVER-$TMPWV.deb"
-TMPFIL2="tidy5-$TMPVER-$TMPWV.rpm"
+TMPFIL1="tidy-$TMPVER-$TMPWV.deb"
+TMPFIL2="tidy-$TMPVER-$TMPWV.rpm"
 if [ ! -f "$TMPFIL1" ]; then
     echo "$BN: $TMPFIL1 does not exits"
     echo "$BN: Have you run '[sudo] make package'?"
@@ -56,6 +62,11 @@ echo ""
 echo "$BN: Will publish..."
 echo "$TMPFIL1"
 echo "$TMPFIL2"
+if [ ! -d "$TMPDD" ]; then 
+    echo "$BN: Will create dir $TMPDD"
+else
+    echo "$BN: Destination $TMPDD"
+fi
 echo ""
 echo "$BN: *** CONTINUE? ***"
 ask

build/cmake/rentidy.sh

@@ -0,0 +1,39 @@
+#!/bin/sh
+#< rentidy.sh - 20160201
+BN=`basename $0`
+
+ask()
+{
+    pause
+    if [ ! "$?" = "0" ]; then
+        exit 1
+    fi
+}
+
+TMPEXE="/usr/bin/tidy"
+if [ ! -f "$TMPEXE" ]; then
+    echo "$BN: Can not locate '$TMPEXE'"
+    exit 1
+fi
+# tidy -v
+$TMPEXE -v
+if [ ! "$?" = "0" ]; then
+    echo "$BN: Can not run $TMPEXE!"
+    exit 1
+fi
+TMPVER=`$TMPEXE -v | awk '{ print $6 }'`
+# echo "$BN: Version $TMPVER"
+TMPFIL2="$TMPEXE-$TMPVER"
+if [ -f "$TMPFIL2" ]; then
+    echo "$BN: New name already exists!"
+    exit 1
+fi
+echo "$BN: Rename $TMPEXE to $TMPFIL2?"
+
+ask
+
+sudo mv $TMPEXE $TMPFIL2
+
+
+# eof
+

build/cmake/updexe.bat

@@ -1,8 +1,8 @@
 @setlocal
 @REM copy the EXE into C:\MDOS, IFF changed
 @set TMPDIR=C:\MDOS
-@set TMPFIL1=tidy5.exe
-@set TMPFIL2=tidy5-32.exe
+@set TMPFIL1=tidy.exe
+@set TMPFIL2=tidy32.exe
 @set TMPSRC=Release\%TMPFIL1%
 @if NOT EXIST %TMPSRC% goto ERR1
 @echo Current source %TMPSRC%

build/documentation/.gitignore

@@ -1,12 +0,0 @@
-
-# file created during build_docs 
-# = tidy5 -h > tidy5.cmd.txt
-examples/tidy5.*.txt
-
-# The license file needs to copies to examples for \include
-examples/LICENSE.md
-
-# file generates from xsl
-examples/quickref_include.html
-
-

build/documentation/DoxygenLayout.xml

@@ -1,198 +0,0 @@
-<doxygenlayout version="1.0">
-  <!-- Generated by doxygen 1.8.9.1 -->
-  <!-- Navigation index tabs for HTML output -->
-  <navindex>
-    <tab type="mainpage" visible="yes" title="Tidy Home"/>
-    <tab type="pages" visible="yes" title="Pages" intro=""/>
-    <tab type="modules" visible="yes" title="" intro=""/>
-    <tab type="namespaces" visible="yes" title="">
-      <tab type="namespacelist" visible="yes" title="" intro=""/>
-      <tab type="namespacemembers" visible="yes" title="" intro=""/>
-    </tab>
-    <tab type="classes" visible="yes" title="">
-      <tab type="classlist" visible="yes" title="" intro=""/>
-      <tab type="classindex" visible="$ALPHABETICAL_INDEX" title=""/> 
-      <tab type="hierarchy" visible="yes" title="" intro=""/>
-      <tab type="classmembers" visible="yes" title="" intro=""/>
-    </tab>
-    <tab type="files" visible="yes" title="">
-      <tab type="filelist" visible="yes" title="" intro=""/>
-      <tab type="globals" visible="yes" title="" intro=""/>
-    </tab>
-    <tab type="examples" visible="yes" title="" intro=""/>
-    <tab type="user" url="https://github.com/htacg/tidy-html5/issues" title="Bugs &amp; Issues"/>
-    <tab type="user" url="https://github.com/htacg/tidy-html5" title="github"/>
-    <tab type="user" url="http://www.htacg.org/" title="htacg.org"/>
-    <tab type="user" url="http://www.html-tidy.org/" title="html-tidy.org"/>
-  </navindex>
-
-  <!-- Layout definition for a class page -->
-  <class>
-    <briefdescription visible="yes"/>
-    <includes visible="$SHOW_INCLUDE_FILES"/>
-    <inheritancegraph visible="$CLASS_GRAPH"/>
-    <collaborationgraph visible="$COLLABORATION_GRAPH"/>
-    <memberdecl>
-      <nestedclasses visible="yes" title=""/>
-      <publictypes title=""/>
-      <services title=""/>
-      <interfaces title=""/>
-      <publicslots title=""/>
-      <signals title=""/>
-      <publicmethods title=""/>
-      <publicstaticmethods title=""/>
-      <publicattributes title=""/>
-      <publicstaticattributes title=""/>
-      <protectedtypes title=""/>
-      <protectedslots title=""/>
-      <protectedmethods title=""/>
-      <protectedstaticmethods title=""/>
-      <protectedattributes title=""/>
-      <protectedstaticattributes title=""/>
-      <packagetypes title=""/>
-      <packagemethods title=""/>
-      <packagestaticmethods title=""/>
-      <packageattributes title=""/>
-      <packagestaticattributes title=""/>
-      <properties title=""/>
-      <events title=""/>
-      <privatetypes title=""/>
-      <privateslots title=""/>
-      <privatemethods title=""/>
-      <privatestaticmethods title=""/>
-      <privateattributes title=""/>
-      <privatestaticattributes title=""/>
-      <friends title=""/>
-      <related title="" subtitle=""/>
-      <membergroups visible="yes"/>
-    </memberdecl>
-    <detaileddescription title=""/>
-    <memberdef>
-      <inlineclasses title=""/>
-      <typedefs title=""/>
-      <enums title=""/>
-      <services title=""/>
-      <interfaces title=""/>
-      <constructors title=""/>
-      <functions title=""/>
-      <related title=""/>
-      <variables title=""/>
-      <properties title=""/>
-      <events title=""/>
-    </memberdef>
-    <allmemberslink visible="yes"/>
-    <usedfiles visible="$SHOW_USED_FILES"/>
-    <authorsection visible="yes"/>
-  </class>
-
-  <!-- Layout definition for a namespace page -->
-  <namespace>
-    <briefdescription visible="yes"/>
-    <memberdecl>
-      <nestednamespaces visible="yes" title=""/>
-      <constantgroups visible="yes" title=""/>
-      <classes visible="yes" title=""/>
-      <typedefs title=""/>
-      <enums title=""/>
-      <functions title=""/>
-      <variables title=""/>
-      <membergroups visible="yes"/>
-    </memberdecl>
-    <detaileddescription title=""/>
-    <memberdef>
-      <inlineclasses title=""/>
-      <typedefs title=""/>
-      <enums title=""/>
-      <functions title=""/>
-      <variables title=""/>
-    </memberdef>
-    <authorsection visible="yes"/>
-  </namespace>
-
-  <!-- Layout definition for a file page -->
-  <file>
-    <briefdescription visible="yes"/>
-    <includes visible="$SHOW_INCLUDE_FILES"/>
-    <includegraph visible="$INCLUDE_GRAPH"/>
-    <includedbygraph visible="$INCLUDED_BY_GRAPH"/>
-    <sourcelink visible="yes"/>
-    <memberdecl>
-      <classes visible="yes" title=""/>
-      <namespaces visible="yes" title=""/>
-      <constantgroups visible="yes" title=""/>
-      <defines title=""/>
-      <typedefs title=""/>
-      <enums title=""/>
-      <functions title=""/>
-      <variables title=""/>
-      <membergroups visible="yes"/>
-    </memberdecl>
-    <detaileddescription title=""/>
-    <memberdef>
-      <inlineclasses title=""/>
-      <defines title=""/>
-      <typedefs title=""/>
-      <enums title=""/>
-      <functions title=""/>
-      <variables title=""/>
-    </memberdef>
-    <authorsection/>
-  </file>
-
-  <!-- Layout definition for a group page -->
-  <group>
-    <briefdescription visible="yes"/>
-    <groupgraph visible="$GROUP_GRAPHS"/>
-    <memberdecl>
-      <nestedgroups visible="yes" title=""/>
-      <dirs visible="yes" title=""/>
-      <files visible="yes" title=""/>
-      <namespaces visible="yes" title=""/>
-      <classes visible="yes" title=""/>
-      <defines title=""/>
-      <typedefs title=""/>
-      <enums title=""/>
-      <enumvalues title=""/>
-      <functions title=""/>
-      <variables title=""/>
-      <signals title=""/>
-      <publicslots title=""/>
-      <protectedslots title=""/>
-      <privateslots title=""/>
-      <events title=""/>
-      <properties title=""/>
-      <friends title=""/>
-      <membergroups visible="yes"/>
-    </memberdecl>
-    <detaileddescription title=""/>
-    <memberdef>
-      <pagedocs/>
-      <inlineclasses title=""/>
-      <defines title=""/>
-      <typedefs title=""/>
-      <enums title=""/>
-      <enumvalues title=""/>
-      <functions title=""/>
-      <variables title=""/>
-      <signals title=""/>
-      <publicslots title=""/>
-      <protectedslots title=""/>
-      <privateslots title=""/>
-      <events title=""/>
-      <properties title=""/>
-      <friends title=""/>
-    </memberdef>
-    <authorsection visible="yes"/>
-  </group>
-
-  <!-- Layout definition for a directory page -->
-  <directory>
-    <briefdescription visible="yes"/>
-    <directorygraph visible="yes"/>
-    <memberdecl>
-      <dirs visible="yes"/>
-      <files visible="yes"/>
-    </memberdecl>
-    <detaileddescription title=""/>
-  </directory>
-</doxygenlayout>

build/documentation/README.md

@@ -1,105 +0,0 @@
-Documentation HOWTO                 {#docs_howto}
-========================
-Instructions for generating documentation
-
-\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:
-
-- `tidylib_api/` (directory)
-
- - This collection of documents describes the **TidyLib** API and is generated from the
-   comments and code in the **Tidy** source code.
-   
-- `quickref.html`
-
- - This document provides a nice, readable HTML document describing all of the options and
-   settings that you can use with **Tidy** and internally in **TidyLib**.
-   
-- `tidy.1`
-
- - This document is a Mac/Linux/Unix standard `man` page.
- 
- 
-## The easy way
-
-In this directory you can find the shell script `build_docs.sh`, and that will build all
-of the documentation into the `temp/` directory (i.e., `{tidy}/build/documentation/temp`).
-
-Please note these prerequisites:
-
-- It's a Mac/Linux/Unix shell script.
-- Doxygen is required to generate the API documentation.
-- xsltproc is required to generate the man page and the `quickref.html` file.
-
-If you prefer to understand how to do this manually (for example, for integration into
-other scripts, build systems, or IDEs), read on.
-
-
-## Manually
-
- 
-### `tidylib_api/` (directory)
-
-If you want to build the API documentation you must have [doxygen][1] installed.
-You can clone the [repository from github][2] if it is not currently installed.
-
-Building as simple as:
-
-~~~
-cd {tidy}/build/documentation/
-doxygen doxygen.cfg
-~~~
-
-This will result in a document set in `{tidy}/build/documentation/temp/tidylib_api`,
-where you can find the main `index.html` file.
-
-
-### `quickref.html`
-
-Note that these instructions require the standard `xsltproc` utility to build the file,
-but any XSLT processor of your choice should work, too.
-
-- `tidy -xml-config > "tidy-config.xml"`
-
- - This uses your up-to-date version of **Tidy** to generate an XML file containing all
-   of **Tidy**’s built-in settings and their descriptions. This file is only temporary,
-   as it will be transformed in the next step.
-
-- `xsltproc "quickref.xsl" "tidy-config.xml" > "quickref.html"`
-
- - This examples uses the `xsltproc` command to transform `tidy-config.xml` using the
-   rules in the `quickref.xsl` stylesheet, and output it to `quickref.html`.
-   
-
-
-### `tidy.1`
-
-Note that these instructions require the standard `xsltproc` utility to build the file,
-but any XSLT processor of your choice should work, too.
-
-- `tidy -xml-config > "tidy-config.xml"`
-
- - This uses your up-to-date version of **Tidy** to generate an XML file containing all
-   of **Tidy**’s built-in settings and their descriptions. This file is only temporary,
-   as it will be transformed in the third step.
-
-- `tidy -xml-help > "tidy-help.xml"`
-
- - This uses your up-to-date version of **Tidy** to generate an XML file containing all
-   of **Tidy**’s built-in help information. This file is only temporary,
-   as it will be transformed in the next step.
-
-- `xsltproc "tidy1.xsl" "tidy-help.xml" > "tidy.1"`
-
- - This examples uses the `xsltproc` command to transform `tidy-help.xml` using the
-   rules in the `tidy1.xsl` stylesheet, and output it to `tidy.1`.
-   
-   \note Note that `tidy1.xls` includes the file `tidy-config.xml` as part of the stylesheet,
-   and so although it does not appear in the command invocation, it is indeed required.
-
-
-
- [1]: http://www.stack.nl/~dimitri/doxygen/
- [2]: https://github.com/doxygen/doxygen

build/documentation/build_docs.sh

@@ -1,152 +0,0 @@
-#!/bin/sh
-
-# See cat << HEREDOC for file description.
-
-
-# Set this to the complete path of the tidy for which you want to generate
-# documentation. Relative path is okay. You shouldn't have to change this
-# too often if your compiler always puts tidy in the same place.
-
-TIDY_PATH="../cmake/tidy5"         # Current directory.
-
-TIDY_VERSION=`cat ../../version.txt`
-
-
-cat << HEREDOC
-
-  Build 'tidy.1', which is a man page suitable for installation
-  in all Unix-like operating systems. This script will build
-  it, but not install it.
-  
-  Build 'quickref.html'. This is distributed with the
-  the Tidy source code and also used on Tidy's website.
-  Be sure to distribute it with 'quickref.css' as well.
-
-  Build the 'tidylib_api' directory, which contains a website
-  with the documentation for TidyLib’s headers.
-  
-  These files will be built into '{current_dir}/temp'.
-  
-HEREDOC
-
-
-# Output and flags' declarations.
-DOXY_CFG="doxygen.cfg"
-OUTP_DIR="temp"
-BUILD_XSLT=1
-BUILD_API=1
-
-
-##
-# Ensure the output dir exists.
-##
-if [ ! -d "$OUTP_DIR" ]; then
-	mkdir $OUTP_DIR
-fi
-
-
-##
-# Preflight
-##
-
-# Check for a valid tidy.
-if [ ! -x "$TIDY_PATH" ]; then
-  BUILD_XSLT=0
-  echo "- '$TIDY_PATH' not found. You should set TIDY_PATH in this script."
-fi
-
-# Check for xsltproc dependency.
-hash xsltproc 2>/dev/null || { echo "- xsltproc not found. You require an XSLT processor."; BUILD_XSLT=0; }
-
-
-##
-# Build 'quickref.html' and 'tidy.1'.
-##
-
-if [ "$BUILD_XSLT" -eq 1 ]; then
-	# Use the designated tidy to get its config and help.
-	# These temporary files will be cleaned up later.
-	$TIDY_PATH -xml-config > "tidy-config.xml"
-	$TIDY_PATH -xml-help > "tidy-help.xml"
-
-	# 'quickref.html'
-	xsltproc "quickref.xsl" "tidy-config.xml" > "$OUTP_DIR/quickref.html"
-	xsltproc "quickref.include.xsl" "tidy-config.xml" > ./examples/quickref_include.html
-
-	# 'tidy.1'
-	xsltproc "tidy1.xsl" "tidy-help.xml" > "$OUTP_DIR/tidy.1"
-
-	# Cleanup - Note: to avoid issues with the tidy1.xsl finding the tidy-config.xml
-	# document, they are created and read from the source directory instead of temp.
-	rm "tidy-config.xml"
-	rm "tidy-help.xml"
-	
-	echo "'quickref.html' and 'tidy.1' have been built.\n"
-else
-  echo "* tidy.1 was skipped because not all dependencies were satisfied."
-fi
-
-
-##
-# Preflight
-##
-
-# Check for the doxygen.cfg file.
-if [ ! -f "$DOXY_CFG" ]; then
-  BUILD_API=0
-  echo "- 'DOXY_CFG' not found. It is required to configure doxygen."
-fi
-
-# Check for doxygen dependency.
-hash doxygen 2>/dev/null || { echo "- doxygen not found. This script requires doxygen."; BUILD_XSLT=0; }
-
-
-##
-# Build the doxygen project.
-##
-
-if [ "$BUILD_API" -eq 1 ]; then
-  echo "The following is doxygen's stderr output. It doesn't indicate errors with this script:\n"
-  
-  # echo the output of tidy5 --help so we can include
-  $TIDY_PATH -h > "./examples/tidy5.help.txt"
-  $TIDY_PATH -help-config > "./examples/tidy5.config.txt"
-  
-  
-  ## copy license file to examples for includsing
-  cp ../../LICENSE.md ./examples/
-  
-  ## this lot 
-  # - echos and catches outputs the doxygen config
-  # - overwrites some vars but appending some to config an end
-  # - 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 "GENERATE_TAGFILE=$OUTP_DIR/tidylib_api/tidy.tags"; \
-    echo "HTML_EXTRA_FILES= ./examples/tidy5.help.txt ./examples/tidy5.config.txt"; ) \
-    | doxygen - > /dev/null
-    
-    # cleanup
-    rm "./examples/tidy5.help.txt"
-    rm "./examples/tidy5.config.txt"
-    rm "./examples/LICENSE.md"
-    
-    ## create zip file of docs
-    cd $OUTP_DIR;
-    #zip  -r "tidy-docs-$TIDY_VERSION.zip" ./tidylib_api
-    
-    
-    
-    
-  echo "\nTidyLib API documentation has been built."
-else
-  echo "* $OUTP_DIR/tidylib_api/ was skipped because not all dependencies were satisfied."
-fi
-
-
-##
-# Done
-##
-
-echo "\nDone.\n"
-

build/documentation/examples/example.1.c

@@ -1,49 +0,0 @@
-
-
-#include <tidy.h>;
-#include <buffio.h>;
-#include <stdio.h>;
-#include <errno.h>;
-
-int main(int argc, char **argv )
-{
-    const char* input = "<title>Hello</title><p>World!";
-    TidyBuffer output = {0};
-    TidyBuffer errbuf = {0};
-    int rc = -1;
-    Bool ok;
-
-    // Initialize "document"
-    TidyDoc tdoc = tidyCreate();
-    printf( "Tidying:\t%s\n", input );
-
-    // Convert to XHTML
-    ok = tidyOptSetBool( tdoc, TidyXhtmlOut, yes );  
-    if ( ok )
-        rc = tidySetErrorBuffer( tdoc, &errbuf );    // Capture diagnostics
-    if ( rc >= 0 )
-        rc = tidyParseString( tdoc, input );         // Parse the input
-    if ( rc >= 0 )
-        rc = tidyCleanAndRepair( tdoc );             // Tidy it up!
-    if ( rc >= 0 )
-        rc = tidyRunDiagnostics( tdoc );             // Kvetch
-    if ( rc > 1 )                                    // If error, force output.
-        rc = ( tidyOptSetBool(tdoc, TidyForceOutput, yes) ? rc : -1 );
-    if ( rc >= 0 )
-        rc = tidySaveBuffer( tdoc, &output );        // Pretty Print
-
-    if ( rc >= 0 )
-    {
-    if ( rc > 0 )
-        printf( "\nDiagnostics:\n\n%s", errbuf.bp );
-    printf( "\nAnd here is the result:\n\n%s", output.bp );
-    }
-    else
-        printf( "A severe error (%d) occurred.\n", rc );
-
-    tidyBufFree( &output );
-    tidyBufFree( &errbuf );
-    tidyRelease( tdoc );
-    return rc;
-}
-

build/documentation/examples/example_config.txt

@@ -1,22 +0,0 @@
-// sample config file for HTML tidy
-indent: auto
-indent-spaces: 2
-wrap: 72
-markup: yes
-output-xml: no
-input-xml: no
-show-warnings: yes
-numeric-entities: yes
-quote-marks: yes
-quote-nbsp: yes
-quote-ampersand: no
-break-before-br: no
-uppercase-tags: no
-uppercase-attributes: no
-char-encoding: latin1
-new-inline-tags: cfif, cfelse, math, mroot,
-  mrow, mi, mn, mo, msqrt, mfrac, msubsup, munderover,
-  munder, mover, mmultiscripts, msup, msub, mtext,
-  mprescripts, mtable, mtr, mtd, mth
-new-blocklevel-tags: cfoutput, cfquery
-new-empty-tags: cfelse

build/documentation/pages/main_page.dox

@@ -1,52 +0,0 @@
-/*!
-
-\mainpage Tidy home
-
-\note The repository <a href="https://github.com/htacg/tidy-html5">github.com/htacg/tidy-html5</a> and this documentation should be considered  canonical for HTML Tidy as of 2015-January-15. See \ref history
-
-
-\b Tidy corrects and cleans up HTML content by fixing markup errors such as mismatched, misnested and missing tags, missing end "/" tags, missing quotations et all, eg:
-
-
-\code{.html}
-<h1><hr>heading</h1>
-<h2>sub<hr>heading</h2>
-<a href="#refs">References<a>
-\endcode
-is converted to
-\code{.html}
-<hr>
-<h1>heading</h1>
-<h2>sub</h2>
-<hr>
-<h2>heading</h2>
-<a href="#refs">References</a>
-\endcode
-
-
-<h4>This project has two parts:</h4>
-
--  \ref tidylib 
-        - a C static or dynamic library that developers can integrate into their applications 
-          in order to bring all of Tidy’s power to your favorite tools. 
-        
--  \ref tidy_cmd 
-        - a console application built on \ref tidylib for Mac OS X, Linux, Windows, UNIX, and more. 
-
-\section content Contents
-- \ref quick_ref
-- \ref tidy_cmd
-  - \ref tidy_quickstart
-  - \ref tidy_config
-  - \ref featured_options
-  - \ref tidy_scripting
-- \ref tidylib
-  - <a href="modules.html">Modules</a>
-- \ref building_tidy
--\ref docs_howto
-- \subpage history
-- \subpage license    
-- \ref todo    
-    
-
-*/

build/documentation/pages/page_building.dox

@@ -1,98 +0,0 @@
-/*!
-
-
-\page building_tidy Building Tidy
-
-How to compile and install Tidy from source code.
-
-\tableofcontents
-  
-\section Prerequisites
-
- - \b git - <a href="http://git-scm.com/book/en/v2/Getting-Started-Installing-Git">git-scm.com/book/en/v2/Getting-Started-Installing-Git</a>
- - \b cmake - <a href="http://www.cmake.org/download/">cmake.org/download/</a>
- - Appropriate build tools for the platform
-
-CMake comes in two forms - command line and gui. Some installations only install one or the other, but sometimes both. The build 
-commands below are only for the command line use.
-
-Also the actual build tools vary for each platform. But that is one of the great features of cmake, it can generate 
-variuous 'native' build files. Running cmake without any parameters will list the generators 
-available on that platform. For sure one of the common ones is "Unix Makefiles", which needs autotools 
-make installed, but many other generators are supported.
-
-In windows cmake offers various versions of MSVC. Again below only the command line use of MSVC is shown, but the 
-tidy solution (*.sln) file can be loaded into the MSVC IDE, and the building done in there.
-
-\section get_source Get the source code
-
-Tidy’s sourcecode can be found at <a href="https://github.com/htacg/tidy-html5">github.com/htacg/tidy-html5</a>. There are sometimes 
-several branches, but in general `master` is the most recently updated version. 
-
-\note Note that as “cutting edge,” it may have bugs or other 
-unstable behavior. If you prefer a stable, officially released version, be sure to have a look 
-at Releases on the github page.
-
-In general you can use the <b>Download ZIP</b> button on the github page to download the most recent version of a branch. If you prefer 
-Git then you can  clone the repository to a working machine with:
-
-
-\code{.sh}
-git clone git@github.com:htacg/tidy-html5.git
-\endcode
-
-\section compile Compile
-
-<h4>Enter the `build/cmake` directory</h4>
-\code{.sh}
-# *nix
-cd {your-tidy-html5-directory}/build/cmake
-
-# windows
-cd {your-tidy-html5-directory}\build\cmake
-\endcode
-
-<h4>Configure the build</h4>
-\code{.sh}
-# *nix
-cmake ../../ [-DCMAKE_INSTALL_PREFIX=/path/for/install]
-
-# windows
-cmake ..\..\ 
-\endcode
-By default cmake sets the install path to `/usr/local` in unix. 
-
-If you wanted the binary in say `/usr/bin` instead, then use `-DCMAKE_INSTALL_PREFIX=/usr`
-
-On windows the default install is to `C:\Program Files\tidy5`, or `C:/Program Files (x86)/tidy5`, which is not very useful. After 
-the build the `tidy[n].exe` is in the `Release\` directory, and can be copied to any directory in your `PATH` environment variable, for global use.
-
-If you need the tidy library built as a 'shared' (DLL) library, then in add the command `-DBUILD_SHARED_LIB:BOOL=ON`. 
-This option is `OFF` by default, so the static library is built and linked with the command line tool for convenience.
-
-
-<h4>Compile</h4>
-\code{.sh}
-# *nix
-make
-
-# windows
-cmake --build . --config Release
-\endcode
-
-
-\section compileOnstall Install
-Install the applicatio and library with
-
-\code{.sh}
-# *nix
-[sudo] make install
-
-# windows
-cmake --build . --config Release --target INSTALL
-\endcode
-
-
-
-
-*/

build/documentation/pages/page_featured_options.dox

@@ -1,146 +0,0 @@
-/*!
-
-
-\page featured_options Featured Options
-
-Overview of popular features and problems
-
-\tableofcontents
-
-\section indenting Indenting output for readability
-
-Indenting the source markup of an HTML document makes the markup easier to read. Tidy can indent the 
-markup for an HTML document while recognizing elements whose contents should not be indented. In the 
-example below, Tidy indents the output while preserving the formatting of the `<pre>` element:
-
-Input:
-\code{.html}
-<html>
- <head>
- <title>Test document</title>
- </head>
- <body>
- <p>This example shows how Tidy can indent output while preserving
- formatting of particular elements.</p>
-
- <pre>This is
- <em>genuine
-       preformatted</em>
-    text
- </pre>
- </body>
- </html>
- \endcode 
- 
- Output:
-\code{.html}
-<html>
-    <head>
-        <title>Test document</title>
-    </head>
-
-    <body>
-        <p>This example shows how Tidy can indent output while preserving
-        formatting of particular elements.</p>
-<pre>
-This is
-<em>genuine
-       preformatted</em>
-   text
-</pre>
-    </body>
-</html>
-\endcode 
-
-Tidy’s indenting behavior is not perfect and can sometimes cause your output to be rendered by browsers in a different way than the input. You can 
-avoid unexpected indenting-related rendering problems by setting `indent:no` or `indent:auto` in a config file.
-
-\note 
-    <b>Preserving original indenting not possible</b><br><br>
-    Tidy is not capable of preserving the original indenting of the markup from the input it receives. That’s because Tidy starts by 
-    building a clean parse tree from the input, and that parse tree doesn’t contain any information about the original indenting. Tidy then 
-    pretty-prints the parse tree using the current config settings. Trying to preserve the original 
-    indenting from the input would interact badly with the repair operations needed to build a clean parse tree, and would considerably complicate the code.
-
-    
-\section encodings Encodings and character references
-
-Tidy defaults to assuming you want output to be encoded in `UTF-8`. But Tidy offers you a choice of other 
-character encodings: `US ASCII`, `ISO Latin-1`, and the `ISO 2022` family of 7 bit encodings.
-
-Tidy doesn’t yet recognize the use of the HTML `<meta>` element for specifying the character encoding.
-
-The full set of HTML character references are defined. Cleaned-up output uses named character references for characters when appropriate. Otherwise, 
-characters outside the normal range are output as numeric character references.
-
-\section accessibility Accessibility
-
-Tidy offers advice on potential accessibility problems for people using non-graphical browsers.
-
-\section cleaning_presentational Cleaning up presentational markup
-
-Some tools generate HTML with presentational elements such as `<font>`, `<nobr>`, and `<center>`. Tidy’s -clean option will replace those elements with `<style>` elements and CSS.
-
-Some HTML documents rely on the presentational effects of `<p>` start tags that are not followed by any content. Tidy deletes 
-such `<p>` tags (as well as any headings that don’t have content). So do not use `<p>` tags simply for 
-adding vertical whitespace; instead use CSS, or the `<br>` element. However, note that 
-Tidy won’t discard `<p>` tags that are followed by any non-breaking space (that is, the \code&nbsp;\endcode named character reference).
-
-\section new_tags Teaching Tidy about new tags
-
-You can teach Tidy about new tags by declaring them in the configuration file, the syntax is:
-\code
-new-inline-tags: tag1, tag2, tag3
-new-empty-tags: tag1, tag2, tag3
-new-blocklevel-tags: tag1, tag2, tag3
-new-pre-tags: tag1, tag2, tag3
-\endcode
-The same tag can be defined as \b empty and as \b inline, or as \b empty and as \b block.
-
-These declarations can be combined to define a new empty inline or empty block element, but you are not advised to 
-declare tags as being both \b inline and \b block.
-
-Note that the new tags can only appear where Tidy expects inline or block-level tags respectively. That means you can’t place new 
-tags within the document head or other contexts with restricted content models.
-
-
-\section ignoring_scripting Ignoring PHP, ASP, and JSTE instructions
-
-Tidy will gracefully ignore many cases of PHP, ASP, and JSTE instructions within element content and as replacements for attributes, 
-and preserve them as-is in output; for example:
-
-\code{.php}
-<option <% if rsSchool.Fields("ID").Value
-  = session("sessSchoolID")
-  then Response.Write("selected") %>
-  value='<%=rsSchool.Fields("ID").Value%>'>
-  <%=rsSchool.Fields("Name").Value%>
-  (<%=rsSchool.Fields("ID").Value%>)
-</option>
-\endcode
-
-But note that Tidy may report missing attributes when those are “hidden” within the PHP, ASP, or JSTE code. If you use 
-PHP, ASP, or JSTE code to create a start tag, but place the end tag explicitly in the HTML markup, Tidy 
-won’t be able to match them up, and will delete the end tag. In that case you are advised to make the 
-start tag explicit and to use PHP, ASP, or JSTE code for just the attributes; for example:
-\code{.php}
-<a href="<%=random.site()%>">do you feel lucky?</a>
-\endcode
-
-Tidy can also get things wrong if the PHP, ASP, or JSTE code includes quotation marks; for example:
-\code{.php}
-value="<%=rsSchool.Fields("ID").Value%>"
-\endcode
-
-Tidy will see the quotation mark preceding ID as ending the attribute value, and proceed to complain about what follows.
-
-Tidy allows you to control whether line wrapping on spaces within PHP, ASP, and JSTE instructions is 
-enabled; see the `wrap-php`, `wrap-asp`, and `wrap-jste` config options.
-
-
-\section correcting_xml Correcting well-formedness errors in XML markup
-Tidy can help you to correct well-formedness errors in XML markup. Tidy doesn’t yet recognize all XML features, 
-though; for example, it doesn’t understand CDATA sections or DTD subsets.
-
-
-*/

build/documentation/pages/page_history.dox

@@ -1,54 +0,0 @@
-/*!
-
-
-\page history History
-
-Once upon a time....
-
-<p><strong>HTML Tidy</strong> was created by the <a href="http://www.w3.org/">W3C’s</a> own  <a href="http://www.w3.org/People/Raggett/">Dave Raggett</a> back in the
-dawn of the Internet age. His original Internet page is still available and
-gives a sense of the early history: <a href="http://www.w3.org/People/Raggett/tidy/">Clean up your Web pages with HTML TIDY</a>.</p>
-
-<p>Satisfied with his work Dave passed the torch to a dedicated group of
-maintainers at <a href="http://tidy.sourceforge.net/">tidy.sourceforge.net</a> where the important tasks of turning
-<strong>Tidy</strong> into a C library and keeping up with developing standards was
-performed.</p>
-
-<p>W3C members took a renewed interest in <strong>Tidy</strong> in 2011 and forked the
-project to <a href="https://github.com/w3c/tidy-html5">github</a> (now redirects to this project), where it featured
-compatibility with HTML5 via a <a href="https://lists.w3.org/Archives/Public/www-archive/2011Nov/0007.html">key contribution</a> from one of the SourceForge
-key members.</p>
-
-<p>In 2015 a group of concerned developers, users, and software integrators formed
-<a href="http://www.htacg.org">HTACG</a> with the goal of revitalizing <strong>Tidy</strong>, which had fallen into a
-non-maintained state. As a W3C Community Group, HTACG was deemed worthy by the
-W3C, and W3C passed ownership of their project to HTACG, where it is currently
-being developed and prepped for a new, stable, and modern release.</p>
-
-<p>HTACG is also working diligently with the SourceForge maintainers in an effort
-to harmonize <strong>HTML Tidy</strong> into a single, stable, solid release once again.</p>
-
-
-\code
-                                                                                      
-  +-----------------------------+                                                     
-  | w3.org/People/Raggett/tidy/ |                                                     
-  ++-------------+--------------+                                                     
-   |             |                                                                    
-   |             |    +----------------------+                                        
-   |             +--> |tidy.sourceforge.net  |                                        
-   |                  +------------------+---+                                        
-   |                                     |                                            
-   |       +--------------------+------+ | Soon                                       
-   +-->    | github.com/w3c/tidy|html5 | |                                            
-           +-+------------------+------+ |                                            
-             |                           |                                            
-             |                           |    +-------------------------------+       
-             |                           +->  | You are here:                 |       
-             |                                | github.com/htacg/tidy-html5   |       
-             +----------------------------->  +----------------------+--------+       
-                                                                                      
-\endcode
-
-
-*/

build/documentation/pages/page_license.dox

@@ -1,14 +0,0 @@
-/*!
-
-
-\page license License
-
-License and Legal
-
-<pre>
-\htmlinclude LICENSE.md
-</pre>
-
-
-
-*/

build/documentation/pages/page_quickref.dox

@@ -1,12 +0,0 @@
-/*!
-
-\page quick_ref Quick Ref
-
-Quick reference generated from the tidy command
-
-
-
-\htmlinclude quickref_include.html
-
-
-*/

build/documentation/pages/page_tidy.dox

@@ -1,18 +0,0 @@
-/*!
-
-Running the tidy command
-
-\page tidy_cmd tidy command
-
-  - \subpage tidy_quickstart
-  - \subpage tidy_config
-  - \subpage featured_options
-  - \subpage tidy_scripting
-  
-<pre>
-\htmlinclude tidy5.help.txt
-</pre>
-
-
-
-*/

build/documentation/pages/page_tidy_config.dox

@@ -1,46 +0,0 @@
-/*!
-
-\page tidy_config Configuration
-
-Configuration settings and files
-
-\tableofcontents
-
-To get a list of all configuration settings, see \ref config_options below or use:
-\code{.sh}
-tidy -help-config
-\endcode
-
-\section using_config Using a configuration file
-
-The most convenient way to configure Tidy is by using separate configuration file.
-
-Assuming you have created a Tidy configuration file named `myconfig.txt` (the name and extension don’t matter), you can instruct Tidy to use it via the 
-command line option `-config myconfig.txt` for example:
-
-\code {.sh}
-tidy -config myconfig.txt file1.html file2.html
-\endcode
-
-Alternatively, you can name the default config file via the environment 
-variable named `HTML_TIDY`, the value of which is the absolute path for the config file.
-
-You can also set config options on the command line by preceding the name of the option 
-immediately (no intervening space) with the string “--”; for example:
-
-\code {.sh}
-tidy --break-before-br true --show-warnings false
-\endcode
-
-You can find documentation for full set of configuration options on the \ref quick_ref page.
-
-\section example_config Example Configuration File
-
-\include example_config.txt
-
-\section config_options Config Options
-<pre>
-\htmlinclude tidy5.config.txt
-</pre>
-
-*/

build/documentation/pages/page_tidy_quickstart.dox

@@ -1,71 +0,0 @@
-/*!
-
-\page tidy_quickstart tidy command quickstart
-
-\tableofcontents
-
-This is the syntax for invoking Tidy from the command line:
-\code{.sh}
-tidy [[options] filename]
-\endcode
-
-Tidy defaults to reading from standard input, so if you run Tidy without specifying the filename argument, it will just sit there waiting for input to read.
-
-Tidy defaults to writing to standard output. So you can pipe output from Tidy to other programs, as well as pipe output from other programs to Tidy. You can page through the output from Tidy by piping it to a pager, e.g.:
-\code{.sh}
-tidy file.html | less
-\endcode
-
-\section out_file Output to file
-
-To have Tidy write its output to a file instead, either use the
-\code{.sh}
--o filename 
-or 
--output filename
-\endcode
-option, or redirect standard output to the file. For example:
-\code{.sh}
-tidy -o output.html index.html
-tidy -output output.html index.html
-tidy index.html > output.html
-\endcode
-
-All the above run Tidy on the file `index.html` and write the output to the file `output.html`, while writing any error messages to standard error.
-
-\section out_error Error output
-
-Tidy defaults to writing its error messages to standard error (that is, to the console where you’re running Tidy). To page through the error messages along with the 
-output, redirect standard error to standard output, and pipe it to your pager:
-\code{.sh}
-tidy index.html 2>&1 | less
-\endcode
-To have Tidy write the errors to a file instead, either use 
-\code{.sh}
--f filename 
-or 
--file filename
-\endcode
-option, or redirect standard error to a file:
-\code{.sh}
-tidy -o output.html -f errs.txt index.html
-tidy index.html > output.html 2> errs.txt
-\endcode
-
-Both the above run Tidy on the file `index.html` and writes the output to the file `output.html`, while writing any error messages to the `file errs.txt`.
-
-Writing the error messages to a file is especially useful if the file you are checking has many errors; reading them from a file instead of the console 
-or pager can make it easier to review them.
-
-\section out_modify Modify / Overwrite
-You can use the or `-m` or `-modify` option to modify (in-place) the contents of the input file you are checking; that is, to overwrite those contents with the output from Tidy. For example:
-
-\code{.sh}
-tidy -f errs.txt -m index.html
-\endcode
-That runs Tidy on the file `index.html`, modifying it in place and writing the error messages to the file `errs.txt`.
-
-\warning If you use the `-m` option, you should first ensure that you have a backup copy of your file.
-
-
-*/

build/documentation/pages/page_tidy_scripting.dox

@@ -1,31 +0,0 @@
-/*!
-
-\page tidy_scripting Running tidy in scripts
-
-If you want to run Tidy from a Perl, bash, or other scripting language you may find it of value to inspect the result returned 
-by Tidy when it exits: 
-
-- \b 0 = if everything is fine
-- \b 1 = if there were warnings and 
-- \b 2 = if there were errors. 
-
-\section perl_example_script Example Perl script
-
-\code{.pl}
-if (close(TIDY) == 0) {
-  my $exitcode = $? >> 8;
-  if ($exitcode == 1) {
-    printf STDERR "tidy issued warning messages\n";
-  } elsif ($exitcode == 2) {
-    printf STDERR "tidy issued error messages\n";
-  } else {
-    die "tidy exited with code: $exitcode\n";
-  }
-} else {
-  printf STDERR "tidy detected no errors\n";
-}
-\endcode
-
-
-
-*/

build/documentation/pages/page_tidylib.dox

@@ -1,53 +0,0 @@
-/*!
-
-
-
-\page tidylib tidylib
-
-About the tidylib C library and code
-
-\tableofcontents
-
-\section about_tidylib TidyLib  features
-
-- easy to integrate. Because of the near universal adoption of C linkage, a C interface may be called from a great number of programming languages.
-
-- designed to use opaque types in the public interface. This allows the application to just pass an integer around and the need to transform data types in different languages is minimized. As a results it’s straight-forward to write very thin library wrappers for C++, Pascal, and COM/ATL.
-
-- eats its own dogfood. HTML Tidy links directly to TidyLib.
-
-- is Thread Safe and Re-entrant. Because there are many uses for HTML Tidy - from content validation, content scraping, conversion to XHTML - it was important to make TidyLib run reasonably well within server applications as well as client side.
-
--  uses adaptable I/O. As part of the larger integration strategy it was decided to fully abstract all I/O. This means a (relatively) clean separation between character encoding processing and shovelling bytes back and forth. Internally, the library reads from sources and writes to sinks. This abstraction is used for both markup and configuration “files”. Concrete implementations are provided for file and memory I/O, and new sources and sinks may be provided via the public interface.
-
-\section return_code Return codes
-
-It’s important to understand that API functions that return an integer almost universally adhere to the following convention:
-
-- \b 0 == \b Success
-    - Good to go.
-- \b 1 == \b Warnings, but no errors
-   - Check the error buffer or track error messages for details.
-- \b 2 == \b Errors (and maybe warnings)
-  - By default, Tidy will not produce output. You can force output with the TidyForceOutput option. As with warnings, check error buffer or track error messages for details.
-- <b>< 0</b> == <b>Severe error</b>
-  - Usually value equals `-errno`. See errno.h.
-
-Also, by default, warning and error messages are sent to stderr. You can redirect diagnostic 
-output using either tidySetErrorFile() or tidySetErrorBuffer(). See  tidy.h for details.
-
-
-\section app_notes Application Notes
-
-Of course, there are functions to parse and save both markup and configuration files. For the adventurous, it is possible to create new input sources and output sinks. For example, a URL source could pull the markup from a given URL.
-
-It is also worth remembering that an application may instantiate any number of document and buffer objects. They are fairly cheap to initialize and destroy (just memory allocation and zeroing, really), so they may be created and destroyed locally, as needed. There is no problem keeping them around a while for keeping state. For example, a server app might keep a global document as a master configuration. As documents are parsed, they can copy their configuration data from the master instance. See tidyOptCopyConfig(). If the master copy is initialized at startup, no synchronization is necessary.
-
-
-\section example_hello tidylib example
-
-\include example.1.c
-
-
-
-*/

build/documentation/pages/page_todo.dox

@@ -1,14 +0,0 @@
-/*!
-
-
-\page todo Todo List
-
-The todo list.
-
-\note If this page is empty, then there are no todo items flagged in source.
-
-\xrefitem todo "Todo" "Todo List" 
-
-
-
-*/

build/documentation/quickref.include.xsl

@@ -1,244 +0,0 @@
-<?xml version="1.0"?>
-<!--
-    For generating the `quickref.html` web page from output of
-    `tidy -xml-config`
-
-    (c) 2005 (W3C) MIT, ERCIM, Keio University
-    See tidy.h for the copyright notice.
-
-    Written by Charles Reitzel and Jelks Cabaniss
-
--->
-
-<xsl:stylesheet version="1.0"
-                xmlns="http://www.w3.org/1999/xhtml"
-                xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
-
-<xsl:output method="xml" indent="yes"
-     encoding="us-ascii"
-     omit-xml-declaration="yes"
-     />
-
-<xsl:template match="/">
-
-    <a name="qtop"></a>
-    <h2 id="top">Option Groups</h2>
-    <ul>
-        <li><a class="h3" href="#MarkupHeader">HTML, XHTML, XML</a></li>
-        <li><a class="h3" href="#DiagnosticsHeader">Diagnostics</a></li>
-        <li><a class="h3" href="#PrettyPrintHeader">Pretty Print</a></li>
-        <li><a class="h3" href="#EncodingHeader">Character Encoding</a></li>
-        <li><a class="h3" href="#MiscellaneousHeader">Miscellaneous</a></li>
-    </ul>
-    <xsl:call-template name="link-section" />
-
-    <xsl:call-template name="detail-section" />
-
-</xsl:template>
-
-
-<!-- Named Templates: -->
-
-<xsl:template name="link-section">
-  <table summary="Tidy Options Quick Reference Header Section" border="0"
-  cellpadding="3" cellspacing="0" class="quickref">
-    <colgroup>
-      <col width="33%" />
-      <col width="33%" />
-      <col width="33%" />
-    </colgroup>
-    <xsl:call-template name="links">
-      <xsl:with-param name="class">markup</xsl:with-param>
-      <xsl:with-param name="header">HTML, XHTML, XML</xsl:with-param>
-      <xsl:with-param name="headerID">MarkupHeader</xsl:with-param>
-    </xsl:call-template>
-    <xsl:call-template name="links">
-      <xsl:with-param name="class">diagnostics</xsl:with-param>
-      <xsl:with-param name="header">Diagnostics</xsl:with-param>
-      <xsl:with-param name="headerID">DiagnosticsHeader</xsl:with-param>
-    </xsl:call-template>
-    <xsl:call-template name="links">
-      <xsl:with-param name="class">print</xsl:with-param>
-      <xsl:with-param name="header">Pretty Print</xsl:with-param>
-      <xsl:with-param name="headerID">PrettyPrintHeader</xsl:with-param>
-    </xsl:call-template>
-    <xsl:call-template name="links">
-      <xsl:with-param name="class">encoding</xsl:with-param>
-      <xsl:with-param name="header">Character Encoding</xsl:with-param>
-      <xsl:with-param name="headerID">EncodingHeader</xsl:with-param>
-    </xsl:call-template>
-    <xsl:call-template name="links">
-      <xsl:with-param name="class">misc</xsl:with-param>
-      <xsl:with-param name="header">Miscellaneous</xsl:with-param>
-      <xsl:with-param name="headerID">MiscellaneousHeader</xsl:with-param>
-    </xsl:call-template>
-  </table>
-</xsl:template>
-
-
-<xsl:template name="detail-section">
-  <table summary="Tidy Options Quick Reference Detail Section" border="0"
-    cellpadding="3" cellspacing="0">
-    <xsl:call-template name="reference">
-      <xsl:with-param name="class">markup</xsl:with-param>
-      <xsl:with-param name="header">HTML, XHTML, XML</xsl:with-param>
-      <xsl:with-param name="headerID">MarkupReference</xsl:with-param>
-    </xsl:call-template>
-    <xsl:call-template name="reference">
-      <xsl:with-param name="class">diagnostics</xsl:with-param>
-      <xsl:with-param name="header">Diagnostics</xsl:with-param>
-      <xsl:with-param name="headerID">DiagnosticsReference</xsl:with-param>
-    </xsl:call-template>
-    <xsl:call-template name="reference">
-      <xsl:with-param name="class">print</xsl:with-param>
-      <xsl:with-param name="header">Pretty Print</xsl:with-param>
-      <xsl:with-param name="headerID">PrettyPrintReference</xsl:with-param>
-    </xsl:call-template>
-    <xsl:call-template name="reference">
-      <xsl:with-param name="class">encoding</xsl:with-param>
-      <xsl:with-param name="header">Character Encoding</xsl:with-param>
-      <xsl:with-param name="headerID">EncodingReference</xsl:with-param>
-    </xsl:call-template>
-    <xsl:call-template name="reference">
-      <xsl:with-param name="class">misc</xsl:with-param>
-      <xsl:with-param name="header">Miscellaneous</xsl:with-param>
-      <xsl:with-param name="headerID">MiscellaneousReference</xsl:with-param>
-    </xsl:call-template>
-  </table>
-</xsl:template>
-
-
-<xsl:template name="links">
-  <xsl:param name="class"/>
-  <xsl:param name="header"/>
-  <xsl:param name="headerID"/>
-  <tr valign="bottom">
-    <td class="h3" colspan="2" id="{$headerID}">
-      <xsl:value-of select="$header"/> Options</td>
-    <td valign="top" class="h3top"><a href="#qtop" class="h3topa">Top</a></td>
-  </tr>
-  <xsl:call-template name="ClassHeaders" />
-  <xsl:for-each select="/config/option[@class=$class]">
-    <xsl:sort select="name" order="ascending" />
-    <tr>
-      <td class="qrow"><a href="#{name}"><xsl:value-of select="name"/></a></td>
-      <td class="qrow"><xsl:apply-templates select="type"/></td>
-      <td class="qrow"><xsl:choose>
-            <xsl:when test="string-length(default) &gt; 0 ">
-              <xsl:apply-templates select="default" />
-            </xsl:when>
-            <xsl:otherwise>
-              <strong>-</strong>
-            </xsl:otherwise>
-        </xsl:choose>
-      </td>
-    </tr>
-  </xsl:for-each>
-  <tr valign="bottom">
-    <td colspan="3">&#160;</td>
-  </tr>
-</xsl:template>
-
-
-<xsl:template name="reference">
-  <xsl:param name="class"/>
-  <xsl:param name="header"/>
-  <xsl:param name="headerID"/>
-
-  <tr>
-    <td colspan="3">&#160;</td>
-  </tr>
-  <tr valign="bottom">
-    <td valign="top" colspan="3" class="h2" id="{$headerID}">
-       <h2 class="qh2"><xsl:value-of select="$header"/></h2> 
-    </td>
-  </tr>
-  
-
-  <xsl:for-each select="/config/option[@class=$class]">
-    <xsl:sort select="name" order="ascending" />
-    <tr>
-      <td  valign="top" id="{name}" colspan="2" class="qoptiontitletd">
-        <h4 class="qoptiontitle"><xsl:value-of select="name"/></h4>
-      </td>
-      <td class="tabletitlelink" valign="top" align="right">
-          <a href="#qtop">Top</a>
-      </td>
-    </tr>
-    <tr>
-        <td valign="top" class="qlabel">Type:</td>
-        <td  class="qvalu"><xsl:value-of select="type"/></td>
-    </tr>
-    <tr>
-        <td valign="top" class="qlabel">Default:</td>
-        <td class="qvalu">
-            <xsl:choose>
-              <xsl:when test="string-length(default) &gt; 0">
-                <xsl:apply-templates select="default" />
-              </xsl:when>
-              <xsl:otherwise>-</xsl:otherwise>
-            </xsl:choose>
-        </td>
-    </tr>
-    <tr>
-        <td valign="top" class="qlabel">Example:</td>
-        <td class="qvalu">
-            <xsl:choose>
-              <xsl:when test="string-length(example) &gt; 0">
-                <xsl:apply-templates select="example"/>
-              </xsl:when>
-              <xsl:otherwise>-</xsl:otherwise>
-            </xsl:choose>
-      </td>
-    </tr>
-   
-    <xsl:choose>
-        <xsl:when test="seealso">
-        <tr>
-            <td valign="top" class="qlabel">See Also:</td>
-            <td  valign="top" class="qvalu">
-                <xsl:for-each select="seealso">
-                  <a href="#{.}"><xsl:apply-templates select="." /></a>
-                  <xsl:if test="position() != last()">, </xsl:if>
-                </xsl:for-each>
-            </td>
-        </tr>
-        </xsl:when>
-    </xsl:choose>
-     
-    <tr>
-        <td></td>
-        <td colspan="1" class="qdescription"><xsl:apply-templates select="description"/></td>
-    </tr>
-
-
-    
-    <tr>
-      <td>&#160;</td>
-    </tr>
-  </xsl:for-each>
-</xsl:template>
-
-<xsl:template name="ClassHeaders">
-      <tr>
-        <td class="tabletitle">Option</td>
-        <td class="tabletitle">Type</td>
-        <td class="tabletitle">Default</td>
-      </tr>
-</xsl:template>
-
-<xsl:template name="Stylesheet">
-	<style type="text/css">
-	/* no style */
-	</style>
-</xsl:template>
-
-
-<!-- Regular Templates: -->
-<xsl:template match="a | code | em | strong | br">
-    <xsl:element name="{local-name(.)}">
-        <xsl:copy-of select="@* | node()" />
-    </xsl:element>
-</xsl:template>
-
-</xsl:stylesheet>

build/documentation/quickref.xsl

@@ -1,574 +0,0 @@
-<?xml version="1.0"?>
-<!--
-    For generating the `quickref.html` web page from output of
-    `tidy -xml-config`
-
-    (c) 2005 (W3C) MIT, ERCIM, Keio University
-    See tidy.h for the copyright notice.
-
-    Written by Charles Reitzel and Jelks Cabaniss
-
--->
-
-<xsl:stylesheet version="1.0"
-                xmlns="http://www.w3.org/1999/xhtml"
-                xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
-
-<xsl:output method="xml" indent="yes"
-     encoding="us-ascii"
-     omit-xml-declaration="yes"
-     doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"
-     doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd" />
-
-<xsl:template match="/">
-  <html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml">
-  <head>
-    <title>HTML Tidy Configuration Options Quick Reference</title>
-	<xsl:call-template name="Stylesheet" />
-  </head>
-
-  <body>
-    <h1 id="top">Quick Reference</h1>
-
-    <h2>HTML Tidy Configuration Options</h2>
-
-    <p>Version: <xsl:value-of select="config/@version" /></p>
-
-    <p><a class="h3" href="#MarkupHeader">HTML, XHTML, XML</a><br />
-     <a class="h3" href="#DiagnosticsHeader">Diagnostics</a><br />
-     <a class="h3" href="#PrettyPrintHeader">Pretty Print</a><br />
-     <a class="h3" href="#EncodingHeader">Character Encoding</a><br />
-     <a class="h3" href="#MiscellaneousHeader">Miscellaneous</a></p>
-
-    <xsl:call-template name="link-section" />
-
-    <xsl:call-template name="detail-section" />
-
-  </body>
-  </html>
-</xsl:template>
-
-
-<!-- Named Templates: -->
-
-<xsl:template name="link-section">
-  <table summary="Tidy Options Quick Reference Header Section" border="0"
-  cellpadding="3" cellspacing="0">
-    <colgroup>
-      <col width="33%" />
-      <col width="33%" />
-      <col width="33%" />
-    </colgroup>
-    <xsl:call-template name="links">
-      <xsl:with-param name="class">markup</xsl:with-param>
-      <xsl:with-param name="header">HTML, XHTML, XML</xsl:with-param>
-      <xsl:with-param name="headerID">MarkupHeader</xsl:with-param>
-    </xsl:call-template>
-    <xsl:call-template name="links">
-      <xsl:with-param name="class">diagnostics</xsl:with-param>
-      <xsl:with-param name="header">Diagnostics</xsl:with-param>
-      <xsl:with-param name="headerID">DiagnosticsHeader</xsl:with-param>
-    </xsl:call-template>
-    <xsl:call-template name="links">
-      <xsl:with-param name="class">print</xsl:with-param>
-      <xsl:with-param name="header">Pretty Print</xsl:with-param>
-      <xsl:with-param name="headerID">PrettyPrintHeader</xsl:with-param>
-    </xsl:call-template>
-    <xsl:call-template name="links">
-      <xsl:with-param name="class">encoding</xsl:with-param>
-      <xsl:with-param name="header">Character Encoding</xsl:with-param>
-      <xsl:with-param name="headerID">EncodingHeader</xsl:with-param>
-    </xsl:call-template>
-    <xsl:call-template name="links">
-      <xsl:with-param name="class">misc</xsl:with-param>
-      <xsl:with-param name="header">Miscellaneous</xsl:with-param>
-      <xsl:with-param name="headerID">MiscellaneousHeader</xsl:with-param>
-    </xsl:call-template>
-  </table>
-</xsl:template>
-
-
-<xsl:template name="detail-section">
-  <table summary="Tidy Options Quick Reference Detail Section" border="0"
-    cellpadding="3" cellspacing="0">
-    <xsl:call-template name="reference">
-      <xsl:with-param name="class">markup</xsl:with-param>
-      <xsl:with-param name="header">HTML, XHTML, XML</xsl:with-param>
-      <xsl:with-param name="headerID">MarkupReference</xsl:with-param>
-    </xsl:call-template>
-    <xsl:call-template name="reference">
-      <xsl:with-param name="class">diagnostics</xsl:with-param>
-      <xsl:with-param name="header">Diagnostics</xsl:with-param>
-      <xsl:with-param name="headerID">DiagnosticsReference</xsl:with-param>
-    </xsl:call-template>
-    <xsl:call-template name="reference">
-      <xsl:with-param name="class">print</xsl:with-param>
-      <xsl:with-param name="header">Pretty Print</xsl:with-param>
-      <xsl:with-param name="headerID">PrettyPrintReference</xsl:with-param>
-    </xsl:call-template>
-    <xsl:call-template name="reference">
-      <xsl:with-param name="class">encoding</xsl:with-param>
-      <xsl:with-param name="header">Character Encoding</xsl:with-param>
-      <xsl:with-param name="headerID">EncodingReference</xsl:with-param>
-    </xsl:call-template>
-    <xsl:call-template name="reference">
-      <xsl:with-param name="class">misc</xsl:with-param>
-      <xsl:with-param name="header">Miscellaneous</xsl:with-param>
-      <xsl:with-param name="headerID">MiscellaneousReference</xsl:with-param>
-    </xsl:call-template>
-  </table>
-</xsl:template>
-
-
-<xsl:template name="links">
-  <xsl:param name="class"/>
-  <xsl:param name="header"/>
-  <xsl:param name="headerID"/>
-  <tr valign="bottom">
-    <td class="h3" colspan="2" id="{$headerID}">
-      <xsl:value-of select="$header"/> Options</td>
-    <td valign="top"><a href="#top">Top</a></td>
-  </tr>
-  <xsl:call-template name="ClassHeaders" />
-  <xsl:for-each select="/config/option[@class=$class]">
-    <xsl:sort select="name" order="ascending" />
-    <tr>
-      <td><a href="#{name}"><xsl:value-of select="name"/></a></td>
-      <td><xsl:apply-templates select="type"/></td>
-      <td><xsl:choose>
-            <xsl:when test="string-length(default) &gt; 0 ">
-              <xsl:apply-templates select="default" />
-            </xsl:when>
-            <xsl:otherwise>
-              <strong>-</strong>
-            </xsl:otherwise>
-        </xsl:choose>
-      </td>
-    </tr>
-  </xsl:for-each>
-  <tr valign="bottom">
-    <td colspan="3">&#160;</td>
-  </tr>
-</xsl:template>
-
-
-<xsl:template name="reference">
-  <xsl:param name="class"/>
-  <xsl:param name="header"/>
-  <xsl:param name="headerID"/>
-
-  <tr>
-    <td>&#160;</td>
-  </tr>
-  <tr valign="bottom">
-    <td valign="top" colspan="2" class="h2" id="{$headerID}">
-       <xsl:value-of select="$header"/> Options Reference
-    </td>
-  </tr>
-  <tr>
-    <td>&#160;</td>
-  </tr>
-
-  <xsl:for-each select="/config/option[@class=$class]">
-    <xsl:sort select="name" order="ascending" />
-    <tr>
-      <td class="tabletitle" valign="top" id="{name}">
-        <xsl:value-of select="name"/>
-      </td>
-      <td class="tabletitlelink" valign="top" align="right">
-      <a href="#top">Top</a></td>
-    </tr>
-    <tr>
-      <td valign="top">Type: <strong><xsl:value-of
-        select="type"/></strong><br />
-
-        <xsl:choose>
-          <xsl:when test="string-length(default) &gt; 0">
-            Default: <strong><xsl:apply-templates select="default" /></strong>
-          </xsl:when>
-          <xsl:otherwise>
-            Default: <strong>-</strong>
-          </xsl:otherwise>
-        </xsl:choose>
-
-        <xsl:choose>
-          <xsl:when test="string-length(example) &gt; 0">
-            <br />Example: <strong><xsl:apply-templates
-                select="example"/></strong>
-          </xsl:when>
-          <xsl:otherwise>
-            <br />Example: <strong>-</strong>
-          </xsl:otherwise>
-        </xsl:choose>
-      </td>
-      <td align="right" valign="top">
-        <xsl:for-each select="seealso">
-          <a href="#{.}"><xsl:apply-templates select="." /></a>
-          <xsl:if test="position() != last()">
-            <br />
-          </xsl:if>
-        </xsl:for-each>
-      </td>
-    </tr>
-
-    <tr>
-      <td colspan="2"><xsl:apply-templates select="description"/></td>
-    </tr>
-
-    <tr>
-      <td>&#160;</td>
-    </tr>
-  </xsl:for-each>
-</xsl:template>
-
-<xsl:template name="ClassHeaders">
-      <tr>
-        <td class="tabletitle">Option</td>
-        <td class="tabletitle">Type</td>
-        <td class="tabletitle">Default</td>
-      </tr>
-</xsl:template>
-
-<xsl:template name="Stylesheet">
-	<style type="text/css">
-		/* 1st Style ignored by Netscape */
-		td.dummy, font.dummy, .dummy, a:link.dummy, a:visited.dummy, a:active.dummy
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 16pt;
-		color: #336699;
-		text-decoration: none;
-		font-weight: normal
-		}
-
-		body
-		{
-		margin-left: 10%;
-		margin-right: 10%;
-		font-family: sans-serif;
-		background-color: #FFFFFF
-		}
-
-		/* Blue TITLE */
-		td.title, font.title, .title, a:link.title, a:visited.title, a:active.title
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 16pt;
-		color: #336699;
-		text-decoration: none;
-		font-weight: normal
-		}
-
-		/* BODY TEXT */
-		td.text, font.text, .text, a:link.text, a:visited.text, a:active.text
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 9pt;
-		color: #000000;
-		text-decoration: none;
-		font-weight: normal
-		}
-
-		/* BOLD BODY TEXT */
-		td.textbold, font.textbold, .textbold, a:link.textbold, a:visited.textbold, a:active.textbold
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 9pt;
-		color: #000000;
-		text-decoration: none;
-		font-weight: bold
-		}
-
-		/* BOLD BODY TEXT LINK WITH UNDERLINE*/
-		td.textboldlink, font.textboldlink, .textboldlink, a:link.textboldlink, a:visited.textboldlink, a:active.textboldlink
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 9pt;
-		color: #000000;
-		font-weight: bold
-		}
-
-		/* SMALL BODY TEXT */
-		td.smtext, font.smtext, .smtext, a:link.smtext, a:visited.smtext, a:active.smtext
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 8pt;
-		color: #000000;
-		text-decoration: none;
-		font-weight: normal
-		}
-
-		/* SMALL BOLD BODY TEXT */
-		td.smtextbold, font.smtextbold, .smtextbold, a:link.smtextbold, a:visited.smtextbold, a:active.smtextbold
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 8pt;
-		color: #000000;
-		text-decoration: none;
-		font-weight: bold
-		}
-
-		/* TITLES
-		td.title, font.title, .title, a:link.title, a:visited.title, a:active.title
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 12pt;
-		color: #CC3300;
-		text-decoration: none;
-		font-weight: bold
-		}
-		*/
-
-		/* SUBTITLES */
-		td.subtitle, font.subtitle, .subtitle, a:link.subtitle, a:visited.subtitle, a:active.subtitle
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 11pt;
-		color: #000000;
-		text-decoration: none;
-		font-weight: bold
-		}
-
-		/* LEGAL TEXT */
-		td.legal, font.legal, .legal, a:link.legal, a:visited.legal, a:active.legal
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 8pt;
-		color: #000000;
-		text-decoration: none;
-		font-weight: normal
-		}
-
-		td.legallink, font.legallink, .legallink, a:link.legallink, a:visited.legallink, a:active.legallink
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 8pt;
-		color: #CC3300;
-		font-weight: normal
-		}
-
-		/* RED TEXT */
-		td.textred, font.textred, .textred, a:link.textred, a:visited.textred, a:active.textred
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 10pt;
-		color: #CC3300;
-		text-decoration: none;
-		font-weight: normal
-		}
-
-		/* RED TEXT BOLD*/
-		td.textredbold, font.textredbold, .textredbold, a:link.textredbold, a:visited.textredbold, a:active.textredbold
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 10pt;
-		color: #CC3300;
-		text-decoration: none;
-		font-weight: bold
-		}
-
-		/* LINKS */
-		td.link, font.link, .link, a:link.link, a:visited.link, a:active.link
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 10pt;
-		color: #3366CC;
-		font-weight: normal
-		}
-
-		td.tabletitlelink, font.tabletitlelink, .tabletitlelink, a:link.tabletitlelink, a:visited.tabletitlelink, a:active.tabletitlelink
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 10pt;
-		background-color: #e9e9d3;
-		color: #000000;
-		}
-
-		/* TABLE TITLES */
-		td.tabletitle, font.tabletitle, .tabletitle, a:link.tabletitle, a:visited.tabletitle, a:active.tabletitle
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 10pt;
-		color: #336699;
-		background-color: #e9e9d3;
-		/* text-decoration: none; */
-		font-weight: bold
-		}
-
-		/* TABLE CELL */
-		td.cell, tr.cell, font.cell, .cell, a:link.cell, a:visited.cell, a:active.cell
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 12pt;
-		color: #000000;
-		font-weight: normal;
-		/* background-color: #e9e9d3 */
-		background-color: #f5f5f5
-		}
-
-		/* SHADED TABLE CELL */
-		td.shaded, tr.shaded, font.shaded, .shaded, a:link.shaded, a:visited.shaded, a:active.shaded
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 12pt;
-		color: #000000;
-		font-weight: normal;
-		background-color: #f5f5f5
-		}
-
-		/* GLOSSARY TERM */
-		td.term, font.term, .term, a:link.term, a:visited.term, a:active.term
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 10pt;
-		font-style: normal;
-		color: #000000;
-		text-decoration: none;
-		font-weight: normal
-		}
-
-		/* ELEMENT TAGS */
-		ul
-		{
-		font-family: Arial, Helvetica, sans-serif;
-		font-size: 10pt;
-		font-style: normal;
-		font-weight: normal
-		}
-		li
-		{
-		font-family: Arial, Helvetica, sans-serif;
-		font-size: 10pt;
-		font-style: normal;
-		font-weight: normal
-		}
-
-		a:link.h1, a:visited.h1, .h1
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 12pt;
-		color: #0066CC
-		}
-		a:active.h1
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 12pt;
-		font-weight: bold;
-		color: #0066CC
-		}
-		h1
-		{
-		margin-left: -8%;
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 12pt;
-		color: #0066CC
-		}
-
-		.h2
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 11pt;
-		/* font-weight: bold; */
-		color: #000000
-		}
-
-		h2
-		{
-		margin-left: -4%;
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 11pt;
-		/* font-weight: bold; */
-		color: #000000
-		}
-
-		A:link.h3, A:visited.h3, .h3
-		{  font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 10pt;
-		color: #000000;
-		font-weight: bold
-		}
-
-		A:active.h3
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 10pt;
-		color: #000000;
-		font-weight: bold
-		}
-
-		h3
-		{
-		margin-left: -4%;
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 10pt;
-		font-weight: bold;
-		color: #000000
-		}
-
-		h4
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 9pt;
-		font-weight: bold;
-		color: #000000
-		}
-
-		.code, A:active.code, A:link.code, A:visited.code
-		{
-		font-family: "Courier New", Courier, monospace;
-		}
-
-		.abstract
-		{
-			font-style : italic;
-		}
-
-		p
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 10pt;
-		font-style: normal
-		}
-
-		td
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 10pt;
-		font-style: normal
-		}
-
-		/* LINKS */
-		a:link, a:active
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 10pt;
-		color: #3366CC;
-		font-weight: normal
-		}
-
-		a:visited
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 10pt;
-		color: #333366;
-		font-weight: normal
-		}
-
-		code {
-		  /* use browser/user default for `font-family` */
-		  font-weight: bold;
-		  color: brown;
-		  background: transparent;
-		}
-	</style>
-</xsl:template>
-
-
-<!-- Regular Templates: -->
-<xsl:template match="a | code | em | strong | br">
-    <xsl:element name="{local-name(.)}">
-        <xsl:copy-of select="@* | node()" />
-    </xsl:element>
-</xsl:template>
-
-</xsl:stylesheet>

build/documentation/style.css

@@ -1,304 +0,0 @@
-
-body {
-    background-color: #efefef;
-}
-
-#titlearea {
-    background-image: url(http://www.html-tidy.org/assets/images/green-abstract-background.jpg);
-    background-size: cover;
-}
-
-#projectname {
-    font-family: sans-serif;
-    font-size: 22pt; 
-    margin: 0 0 0 0;
-    margin-left: 150px;
-    padding: 2px 0px;
-    color: white;
-}
-
-#projectnumber {
-    font-size: 12pt; 
-}
-
-#projectbrief {
-    font-family: sans-serif;
-    font-size: 10pt; 
-    color: #dddddd;
-    margin-left: 150px;
-}
-
-
-.contents h1 {
-    font-size: 15pt;
-    font-family: monospace;
-    color: #4D4D74;
-    font-weight: bold;
-    border-left: none;
-    border-top: none;
-    border-bottom: 2px solid #cccccc;
-    margin: 30px 0px 10px 0px;
-    padding: 5px 0 5px 10px;
-}
-.contents h2 {
-    font-size: 12pt;
-    font-family: monospace;
-    color: #4D4D74;
-    font-weight: bold;
-    border-top: none;
-    border-bottom: 1px solid #dddddd;
-    margin: 20px 20% 20px 0px;
-    padding: 2px 0 2px 10px;
-}
-
-
-
-.contents p {
-    line-height: 130%;
-    font-size: 11pt;
-    font-family: sans-serif;
-    margin: 10px 20% 15px 10px;
-    padding: 0px;
-}
-
-.contents ul{
-    list-style-type: disc;
-    font-size: 11pt;
-    margin: 5px 20% 5px 40px;
-    padding: 0px;
-    line-height: 140%;
-}
-.contents ul ul{
-    list-style-type: circle;
-    margin-left: 30px;
-}
-.contents li{
-    padding: 2px 0 2px 0;
-    margin: 0;
-    ssbackground-color: pink;
-}
-
-.contents .textblock{
-    font-size: 10pt;
-    margin: 10px 50px 10px 50px;
-    line-height: 140%;
-}
-.contents .textblock code{
-    font-family: monospace;
-    font-size: 9pt;
-}
-.contents .todo{
-    font-size: 11pt;
-    margin: 10px 10% 20px 30px;
-}
-.contents .bug{
-    font-size: 11pt;
-    margin: 10px 10% 20px 30px;
-}
-
-dl
-{
-        padding: 0 0 0 10px;
-}
-
-/* dl.note, dl.warning, dl.attention, dl.pre, dl.post, dl.invariant, dl.deprecated, dl.todo, dl.test, dl.bug */
-dl.section
-{
-    margin-left: 0px;
-    padding-left: 0px;
-}
-
-dl.note
-{
-        margin: 5px 10% 5px 30px;
-        padding: 10px;
-        border-left: 4px solid;
-        border-color: #D0C000;
-        background-color: #FFFAC5;
-        border-radius: 10px;
-}
-
-ul dl.note{
-    margin-right: 0;
-}
-
-dl.warning, dl.attention
-{
-        margin: 5px 10% 5px 30px;
-        padding: 10px;
-        border-left: 4px solid;
-        border-color: #FF909F;
-        background-color: #FFE1E5;
-        border-radius: 10px;
-}
-
-dl.pre, dl.post, dl.invariant
-{
-        margin-left:-7px;
-        padding-left: 3px;
-        border-left:4px solid;
-        border-color: #00D000;
-}
-
-dl.deprecated
-{
-        margin: 5px 10% 5px 30px;
-        padding: 10px;
-        border-left:4px solid #B10BBF;
-        background-color: #FBC9FF;
-        border-radius: 10px;
-}
-
-dl.todo
-{
-        margin: 5px 10% 5px 30px;
-        padding: 10px;
-        border-left:4px solid #00C0E0;
-        background-color:  #DCFAFF ;
-        border-radius: 10px;
-}
-dl.bug
-{
-        margin: 5px 10% 5px 30px;
-        padding: 10px;
-        border-left:4px solid red;
-        background-color:  #FFC3B9 ;
-        border-radius: 10px;
-}
-dl.test
-{
-        margin-left:-7px;
-        padding-left: 3px;
-        border-left:4px solid;
-        border-color: #3030E0;
-}
-
-dl.bug
-{
-        margin-left:-7px;
-        padding-left: 3px;
-        border-left:4px solid;
-        border-color: #C08050;
-}
-
-
-
-dl.section dd {
-    margin-bottom: 6px;
-}
-
-
-
-table.directory tr {
-    border-bottom: 1px solid #cccccc !important;
-}
-
-table.directory  tr:hover {
-    background-color: #F6FF88 !important;
-}
-
-
-table.directory  td  {
-    padding: 5px;
-    font-family: sans-serif;
-}
-
-/*****************************************************/
-/* Quickref */
-table.quickref {
-    font-size: 9pt;
-    font-family: monospace;
-}
-table.quickref tr:hover{
-    background-color: #F6FF88;
-}
-table.quickref td.qrow {
-    border-bottom: 1px solid #cccccc !important;
-}
-table td.h2 {
-    padding: 0;
-    margin: 0;
-}
-.qh2 {
-    background-color: #333333;
-    color: #eeeeee !important;
-    padding: 10px;
-    border-radius: 5px;
-    border: none;
-    margin: 0;
-    padding: 8px;
-    font-size: 15pt;
-    width: 100%;
-    
-}
-table td.h3 {
-    background-color: #333333;
-    color: #eeeeee;
-    padding: 8px;
-    border-top-left-radius: 8px;
-}
-table td.h3top {
-    background-color: #333333;
-    padding: 8px;
-    border-top-right-radius: 8px;
-    text-align: right;
-    font-size: 8pt;
-}
-table td.h3top a{
-       color: #dddddd !important;
-}
-.h3topssssa {
-    color: #333333;
-}
-
-
-table td.tabletitle {
-    background-color: #cccccc;
-    font-size: 8pt;
-}
-
-td.tabletitlelink {
-    font-size: 8pt;
-}
-td.qoptiontitletd {
- padding: 0;
- margin: 0;
-}
-h4.qoptiontitle {
-    background-color: #bbbbbb;
-    font-size: 11pt;
-    font-weight: bold;
-    font-family: monospace;
-    padding: 5px 5px 5px 10px;
-    margin: 0;
-    border-top-left-radius: 5px;
-    border-top-right-radius: 5px;
-}
-
-
-.qlabel {
-    text-align: right;
-    font-size: 9pt;
-    width: 80px;
-    border-bottom: 1px solid #bbbbbb;
-
-    background-color: #dddddd;
-    font-family: sans-serif;
-}
-.qvalu {
-    font-size: 9pt;
-    font-weight: bold;
-    border-bottom: 1px solid #bbbbbb;
-    font-family: monospace;
-    border-left: 1px solid #bbbbbb;
-}
-
-.qdescription {
-    font-size: 11pt;
-    color: #333333;
-    margin: 0;
-    padding: 5px;
-    line-height: 140%;
-    border-left: 1px solid #bbbbbb;
-    border-bottom: 1px solid #bbbbbb;
-}

build/documentation/tidy1.xsl

@@ -1,448 +0,0 @@
-<?xml version="1.0"?>
-<!--
-    For generating the `tidy.1` man page from the
-    output of `tidy -xml-help` and `tidy -xml-config`
-
-    (c) 2005-2007 (W3C) MIT, ERCIM, Keio University
-    See tidy.h for the copyright notice.
-
-    Written by Jelks Cabaniss and Arnaud Desitter
-
--->
-<xsl:stylesheet version="1.0"
-                xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
-
-<xsl:strip-space elements="description" />
-
-<xsl:output method="text" />
-
-<!--
-    The default template match is to the document passed on the
-    command line to the XSLT processor, currently "tidy-help.xml".
-    For the detailed config options section however, the template
-    match is to the file "tidy-config.xml".  This is captured in
-    the $CONFIG variable, declared here:
--->
-
-<xsl:variable name="CONFIG" select="document('../cmake/tidy-config.xml')"/>
-
-
-<!-- Main Template: -->
-
-<xsl:template match="/">
-   <xsl:call-template name="header-section" />
-   <xsl:call-template name="cmdline-section" />
-   <xsl:call-template name="config-section" />
-   <xsl:call-template name="manpage-see-also-section" />
-</xsl:template>
-
-
-<!-- Named Templates: -->
-
-
-<xsl:template name="header-section">
-  <xsl:text/>.\" tidy man page for the HTML Tidy
-.TH TIDY 1 "<xsl:value-of select="cmdline/@version" />" "HTML Tidy" "<xsl:value-of select="cmdline/@version" />"
-</xsl:template>
-
-
-<xsl:template name="cmdline-section">
-.\" disable hyphenation
-.nh
-.\" disable justification (adjust text to left margin only)
-.ad l
-.SH NAME
-\fBtidy\fR - check, correct, and pretty-print HTML(5) files
-.SH SYNOPSIS
-\fBtidy\fR [option ...] [file ...] [option ...] [file ...]
-.SH DESCRIPTION
-Tidy reads HTML, XHTML, and XML files and writes cleaned-up markup.  For HTML variants, it detects, reports, and corrects many common coding errors and strives to produce visually equivalent markup that is both conformant to the HTML specifications and that works in most browsers.
-.LP
-A common use of Tidy is to convert plain HTML to XHTML.  For generic XML files, Tidy is limited to correcting basic well-formedness errors and pretty printing.
-.LP
-If no input file is specified, Tidy reads the standard input.  If no output file is specified, Tidy writes the tidied markup to the standard output.  If no error file is specified, Tidy writes messages to the standard error.
-For command line options that expect a numerical argument, a default is assumed if no meaningful value can be found. 
-.SH OPTIONS
-<xsl:call-template name="show-cmdline-options" />
-.SH USAGE
-.LP
-Use \fB--\fR\fIoptionX valueX\fR for the detailed configuration option "optionX" with argument "valueX".  See also below under \fBDetailed Configuration Options\fR as to how to conveniently group all such options in a single config file.
-.LP
-Input/Output default to stdin/stdout respectively. Single letter options apart from \fB-f\fR and \fB-o\fR may be combined as in:
-.LP
-.in 1i
-\fBtidy -f errs.txt -imu foo.html\fR
-.SH ENVIRONMENT
-.TP
-.B HTML_TIDY
-Name of the default configuration file.  This should be an absolute path, since you will probably invoke \fBtidy\fR from different directories.  The value of HTML_TIDY will be parsed after the compiled-in default (defined with -DTIDY_CONFIG_FILE), but before any of the files specified using \fB-config\fR.
-.SH "EXIT STATUS"
-.IP 0
-All input files were processed successfully.
-.IP 1
-There were warnings.
-.IP 2
-There were errors.
-</xsl:template>
-
-
-<xsl:template name="config-section">
-.SH ______________________________
-.SH "  "
-.SH "DETAILED CONFIGURATION OPTIONS"
-This section describes the Detailed (i.e., "expanded") Options, which may be specified by preceding each option with \fB--\fR at the command line, followed by its desired value, OR by placing the options and values in a configuration file, and telling tidy to read that file with the \fB-config\fR standard option.
-.SH SYNOPSIS
-\fBtidy --\fR\fIoption1 \fRvalue1 \fB--\fIoption2 \fRvalue2 [standard options ...]
-.br
-\fBtidy -config \fIconfig-file \fR[standard options ...]
-.SH WARNING
-The options detailed here do not include the "standard" command-line options (i.e., those preceded by a single '\fB-\fR') described above in the first section of this man page.
-.SH DESCRIPTION
-A list of options for configuring the behavior of Tidy, which can be passed either on the command line, or specified in a configuration file.
-.LP
-A Tidy configuration file is simply a text file, where each option
-is listed on a separate line in the form
-.LP
-.in 1i
-\fBoption1\fR: \fIvalue1\fR
-.br
-\fBoption2\fR: \fIvalue2\fR
-.br
-etc.
-.LP
-The permissible values for a given option depend on the option's \fBType\fR.  There are five types: \fIBoolean\fR, \fIAutoBool\fR, \fIDocType\fR, \fIEnum\fR, and \fIString\fR. Boolean types allow any of \fIyes/no, y/n, true/false, t/f, 1/0\fR.  AutoBools allow \fIauto\fR in addition to the values allowed by Booleans.  Integer types take non-negative integers.  String types generally have no defaults, and you should provide them in non-quoted form (unless you wish the output to contain the literal quotes).
-.LP
-Enum, Encoding, and DocType "types" have a fixed repertoire of items; consult the \fIExample\fR[s] provided below for the option[s] in question.
-.LP
-You only need to provide options and values for those whose defaults you wish to override, although you may wish to include some already-defaulted options and values for the sake of documentation and explicitness.
-.LP
-Here is a sample config file, with at least one example of each of the five Types:
-.LP
-\fI
-    // sample Tidy configuration options
-    output-xhtml: yes
-    add-xml-decl: no
-    doctype: strict
-    char-encoding: ascii
-    indent: auto
-    wrap: 76
-    repeated-attributes: keep-last
-    error-file: errs.txt
-\fR
-.LP
-Below is a summary and brief description of each of the options. They are listed alphabetically within each category.  There are five categories: \fIHTML, XHTML, XML\fR options, \fIDiagnostics\fR options, \fIPretty Print\fR options, \fICharacter Encoding\fR options, and \fIMiscellaneous\fR options.
-.LP
-.SH OPTIONS
-<xsl:call-template name="show-config-options" />
-</xsl:template>
-
-
-<xsl:template name="show-cmdline-options">
-.SS File manipulation
-  <xsl:call-template name="cmdline-detail">
-     <xsl:with-param name="category">file-manip</xsl:with-param>
-  </xsl:call-template>
-.SS Processing directives
-  <xsl:call-template name="cmdline-detail">
-     <xsl:with-param name="category">process-directives</xsl:with-param>
-  </xsl:call-template>
-.SS Character encodings
-  <xsl:call-template name="cmdline-detail">
-     <xsl:with-param name="category">char-encoding</xsl:with-param>
-  </xsl:call-template>
-.SS Miscellaneous
-  <xsl:call-template name="cmdline-detail">
-     <xsl:with-param name="category">misc</xsl:with-param>
-  </xsl:call-template>
-</xsl:template>
-
-
-<xsl:template name="cmdline-detail">
-<!--
-For each option in one of the 3 categories/classes, provide its
-    1. names
-    2. description
-    3. equivalent configuration option
--->
-  <xsl:param name="category" />
-    <xsl:for-each select='/cmdline/option[@class=$category]'>
-<xsl:text>
-.TP
-</xsl:text>
-       <xsl:call-template name="process-names" />
-       <xsl:text>
-</xsl:text>
-       <xsl:apply-templates select="description" />
-       <xsl:text>
-</xsl:text>
-       <xsl:call-template name="process-eqconfig" />
-    </xsl:for-each>
-</xsl:template>
-
-
-<xsl:template name="process-names">
-<!-- Used only in the cmdline section -->
-  <xsl:for-each select="name">
-    <xsl:text />\fB<xsl:value-of select="." />\fR<xsl:text />
-    <xsl:if test="position() != last()">
-      <xsl:text>, </xsl:text>
-    </xsl:if>
-  </xsl:for-each>
-</xsl:template>
-
-
-<xsl:template name="process-eqconfig">
-<!-- Used only in the cmdline section -->
-  <xsl:if test="string-length(eqconfig) &gt; 0">
-   <xsl:for-each select="eqconfig">
-     <xsl:text>(\fI</xsl:text>
-     <xsl:value-of select="." />
-     <xsl:text>\fR)</xsl:text>
-   </xsl:for-each>
-  </xsl:if>
-</xsl:template>
-
-
-<xsl:template name="show-config-options">
-<!-- Used only in the cmdline section -->
-.SS HTML, XHTML, XML options:
-  <xsl:call-template name="config-detail">
-     <xsl:with-param name="category">markup</xsl:with-param>
-  </xsl:call-template>
-.SS Diagnostics options:
-  <xsl:call-template name="config-detail">
-     <xsl:with-param name="category">diagnostics</xsl:with-param>
-  </xsl:call-template>
-.SS Pretty Print options:
-  <xsl:call-template name="config-detail">
-     <xsl:with-param name="category">print</xsl:with-param>
-  </xsl:call-template>
-.SS Character Encoding options:
-  <xsl:call-template name="config-detail">
-     <xsl:with-param name="category">encoding</xsl:with-param>
-  </xsl:call-template>
-.SS Miscellaneous options:
-  <xsl:call-template name="config-detail">
-     <xsl:with-param name="category">misc</xsl:with-param>
-  </xsl:call-template>
-</xsl:template>
-
-
-<!--
-    Note that any templates called implicitly or explicitly
-    from the "config-detail" template below will match on
-    the document referred to by the $CONFIG variable, i.e.,
-    the file "tidy-config.xml", created by running
-
-        tidy -xml-config > tidy-config.xml
-
-    The $CONFIG variable is set at the top level of this
-    stylesheet.
--->
-
-<xsl:template name="config-detail">
-<!--
-For each option in one of the 5 categories/classes, provide its
-    1. name
-    2. type
-    3. default (if any)
-    4. example (if any)
-    5. seealso (if any)
-    6. description
--->
-  <xsl:param name="category" />
-    <xsl:for-each select='$CONFIG/config/option[@class=$category]'>
-       <xsl:sort select="name" order="ascending" />
-.TP
-\fB<xsl:apply-templates select="name" />\fR
-
-Type:    \fI<xsl:apply-templates select="type" />\fR
-.br
-<xsl:call-template name="provide-default" />
-.br
-<xsl:call-template name="provide-example" />
-<xsl:text>
-
-</xsl:text>
-<xsl:apply-templates select="description" />
-<xsl:call-template name="seealso" />
-    </xsl:for-each>
-</xsl:template>
-
-
-<!-- Used only in the config options section: -->
-<xsl:template name="seealso">
-  <xsl:if test="seealso">
-     <xsl:text>
-
-</xsl:text>
-.rj 1
-\fBSee also\fR: <xsl:text />
-    <xsl:for-each select="seealso">
-      <xsl:text />\fI<xsl:value-of select="." />\fR<xsl:text />
-      <xsl:if test="position() != last()">
-        <xsl:text>, </xsl:text>
-      </xsl:if>
-    </xsl:for-each>
-  </xsl:if>
-</xsl:template>
-
-
-<!-- Used only in the config options section: -->
-<xsl:template name="provide-default">
-<!--
-Picks up the default from the XML.  If the `default` element
-doesn't exist, or it's empty, a single '-' is provided.
--->
-  <xsl:choose>
-    <xsl:when test="string-length(default) &gt; 0 ">
-      <xsl:text />Default: \fI<xsl:apply-templates
-        select="default" />\fR<xsl:text />
-    </xsl:when>
-    <xsl:otherwise>
-      <xsl:text />Default: \fI-\fR<xsl:text />
-    </xsl:otherwise>
-  </xsl:choose>
-</xsl:template>
-
-
-<!-- Used only in the config options section: -->
-<xsl:template name="provide-example">
-<!--
-By default, doesn't output examples for String types (mirroring the
-quickref page).  But for *any* options in the XML instance that
-have an `example` child, that example will be used in lieu of a
-stylesheet-provided one. (Useful e.g. for `repeated-attributes`).
--->
-  <xsl:choose>
-    <xsl:when test="string-length(example) &gt; 0">
-      <xsl:text />Example: \fI<xsl:apply-templates
-          select="example" />\fR<xsl:text />
-    </xsl:when>
-    <xsl:otherwise>
-      <xsl:text />Default: \fI-\fR<xsl:text />
-    </xsl:otherwise>
-  </xsl:choose>
-</xsl:template>
-
-
-<!-- Called from the templates below matching `code`, `em`, `strong`: -->
-<xsl:template name="escape-backslash">
-<!--
-Since backslashes are "special" to the *roff processors used
-to generate man pages, we need to escape backslash characters
-appearing in content with another backslash.
--->
-  <xsl:choose>
-    <xsl:when test="contains(.,'\')">
-      <xsl:value-of select=
-        "concat( substring-before(.,'\'), '\\', substring-after(.,'\') )" />
-    </xsl:when>
-    <xsl:otherwise>
-      <xsl:apply-templates />
-    </xsl:otherwise>
-  </xsl:choose>
-</xsl:template>
-
-
-<!-- Appears at the bottom of the man page: -->
-<xsl:template name="manpage-see-also-section">
-.SH SEE ALSO
-For more information about HTML Tidy:
-.RS 4
-.LP
-http://www.html-tidy.org/
-.RE
-.LP
-For more information on HTML:
-.RS 4
-.LP
-\fBHTML: Edition for Web Authors\fR (the latest HTML specification)
-.br
-http://dev.w3.org/html5/spec-author-view
-.LP
-\fBHTML: The Markup Language\fR (an HTML language reference)
-.br
-http://dev.w3.org/html5/markup/
-.RE
-.LP
-For bug reports and comments:
-.RS 4
-.LP
-https://github.com/htacg/tidy-html5/issues/
-.RE
-.LP
-Or send questions and comments to \fBpublic-htacg@w3.org\fR.
-.LP
-Validate your HTML documents using the \fBW3C Nu Markup Validator\fR:
-.RS 4
-.LP
-http://validator.w3.org/nu/
-.RE
-.SH AUTHOR
-\fBTidy\fR was written by \fBDave Raggett\fR &lt;dsr@w3.org&gt;, and subsequently maintained by a team at http://tidy.sourceforge.net/,
-and now maintained by \fBHTACG\fR (http://www.htacg.org).
-.LP
-The sources for \fBHTML Tidy\fR are available at https://github.com/htacg/tidy-html5/ under the MIT Licence.
-</xsl:template>
-
-
-<!-- Regular Templates: -->
-
-
-<xsl:template match="description">
-   <xsl:apply-templates />
-</xsl:template>
-
-<xsl:template match="a">
-   <xsl:apply-templates />
-   <xsl:text /> at \fI<xsl:value-of select="@href" />\fR<xsl:text />
-</xsl:template>
-
-<xsl:template match="code | em">
-   <xsl:text />\fI<xsl:call-template name="escape-backslash" />\fR<xsl:text />
-</xsl:template>
-
-<xsl:template match="br">
-   <xsl:text>
-.br
-</xsl:text>
-</xsl:template>
-
-<xsl:template match="strong">
-   <xsl:text />\fB<xsl:call-template name="escape-backslash" />\fR<xsl:text />
-</xsl:template>
-
-
-<!--
-The following templates
-  a) normalize whitespace, primarily necessary for `description`
-  b) do so without stripping possible whitespace surrounding `code`
-  d) strip leading and trailing whitespace in 'description` and `code`
-(courtesy of Ken Holman on the XSL-list):
--->
-
-<xsl:template match="text()[preceding-sibling::node() and
-                             following-sibling::node()]">
-   <xsl:variable name="ns" select="normalize-space(concat('x',.,'x'))"/>
-   <xsl:value-of select="substring( $ns, 2, string-length($ns) - 2 )" />
-</xsl:template>
-
-<xsl:template match="text()[preceding-sibling::node() and
-                             not( following-sibling::node() )]">
-   <xsl:variable name="ns" select="normalize-space(concat('x',.))"/>
-   <xsl:value-of select="substring( $ns, 2, string-length($ns) - 1 )" />
-</xsl:template>
-
-<xsl:template match="text()[not( preceding-sibling::node() ) and
-                             following-sibling::node()]">
-   <xsl:variable name="ns" select="normalize-space(concat(.,'x'))"/>
-   <xsl:value-of select="substring( $ns, 1, string-length($ns) - 1 )" />
-</xsl:template>
-
-<xsl:template match="text()[not( preceding-sibling::node() ) and
-                             not( following-sibling::node() )]">
-   <xsl:value-of select="normalize-space(.)"/>
-</xsl:template>
-
-</xsl:stylesheet>

build/macos/Installer-Introduction.rtf

@@ -0,0 +1,37 @@
+{\rtf1\ansi\ansicpg1252\cocoartf2580
+\cocoatextscaling0\cocoaplatform0{\fonttbl\f0\fswiss\fcharset0 Helvetica-Bold;\f1\fswiss\fcharset0 Helvetica;\f2\fswiss\fcharset0 Helvetica-Oblique;
+\f3\fmodern\fcharset0 Courier;}
+{\colortbl;\red255\green255\blue255;}
+{\*\expandedcolortbl;;}
+\paperw11905\paperh16837\margl1440\margr1440\vieww25720\viewh15920\viewkind0
+\pard\tx720\tx1440\tx2160\tx2880\tx3600\tx4320\tx5040\tx5760\tx6480\tx7200\tx7920\tx8640\pardirnatural\qc\partightenfactor0
+
+\f0\b\fs36 \cf0 HTACG HTML Tidy for macOS
+\fs24 \
+\
+
+\fs28 https://www.html-tidy.org
+\f1\b0\fs24 \
+\pard\tx720\tx1440\tx2160\tx2880\tx3600\tx4320\tx5040\tx5760\tx6480\tx7200\tx7920\tx8640\pardirnatural\partightenfactor0
+\cf0 \
+Installer will install 
+\f2\i HTML Tidy
+\f1\i0  for macOS.\
+\
+This version is much newer than the version supplied by Apple, which is only recent as of October 2006. This version of 
+\f2\i HTML Tidy
+\f1\i0  supports HTML5, which is probably the most important thing. Additionally it supports a lot of extended attributes and other things that have made their way into HTML since 2006.\
+\
+It will not replace the built in version of 
+\f2\i HTML Tidy
+\f1\i0  included in macOS, but it will act as a replacement by default.\
+\
+\pard\tx720\tx1440\tx2160\tx2880\tx3600\tx4320\tx5040\tx5760\tx6480\tx7200\tx7920\tx8640\pardirnatural\partightenfactor0
+
+\f0\b \cf0 Important note
+\f1\b0 \
+\
+This installer places files into 
+\f3 /usr/local/
+\f1  which is the correct location for Unix files such as this. Normally macOS allows the installer to access this directory, but early upgrade-installed versions of macOS 10.11 El Capitan prevented this. If the installer fails and you are still running El Capitan, please ensure that you are using the latest point release of that operating system.\
+}

build/macos/Installer-License.rtf

@@ -0,0 +1,34 @@
+{\rtf1\ansi\ansicpg1252\cocoartf2580
+\cocoatextscaling0\cocoaplatform0{\fonttbl\f0\fswiss\fcharset0 Helvetica;\f1\fswiss\fcharset0 Helvetica-Bold;}
+{\colortbl;\red255\green255\blue255;}
+{\*\expandedcolortbl;;}
+\paperw11900\paperh16840\margl1440\margr1440\vieww11740\viewh11980\viewkind0
+\pard\tx720\tx1440\tx2160\tx2880\tx3600\tx4320\tx5040\tx5760\tx6480\tx7200\tx7920\tx8640\pardirnatural\partightenfactor0
+
+\f0\fs24 \cf0 Copyright \'a9 1998-2008 World Wide Web Consortium (Massachusetts Institute of Technology, European Research Consortium for Informatics and Mathematics, Keio University). All Rights Reserved.\
+\
+Contributing Author(s):\
+	Dave Raggett <dsr@w3.org>\
+\
+The contributing author(s) would like to thank all those who helped with testing, bug fixes and suggestions for improvements. This wouldn't have been possible without your help.\
+\
+
+\f1\b COPYRIGHT NOTICE:
+\f0\b0 \
+ \
+This software and documentation is provided "as is," and the copyright holders and contributing author(s) make no representations or warranties, express or implied, including but not limited to, warranties of merchantability or fitness for any particular purpose or that the use of the software or documentation will not infringe any third party patents, copyrights, trademarks or other rights. \
+\
+The copyright holders and contributing author(s) will not be held liable for any direct, indirect, special or consequential damages arising out of any use of the software or documentation, even if advised of the possibility of such damage.\
+\
+Permission is hereby granted to use, copy, modify, and distribute this source code, or portions hereof, documentation and executables, for any purpose, without fee, subject to the following restrictions:\
+\
+1. The origin of this source code must not be misrepresented.\
+2. Altered versions must be plainly marked as such and must not be misrepresented as being the original source.\
+3. This Copyright notice may not be removed or altered from any source or altered source distribution.\
+ \
+The copyright holders and contributing author(s) specifically permit, without fee, and encourage the use of this source code as a component for supporting the Hypertext Markup Language in commercial products. If you use this source code in a product, acknowledgment is not required but would be appreciated.\
+\
+Created 2001-05-20 by Charles Reitzel\
+Updated 2002-07-01 by Charles Reitzel - 1st Implementation\
+Updated 2021-04-28 by others subjected to this same license.\
+}

build/win64/.gitignore

@@ -20,3 +20,6 @@ install_manifest.txt
 *.msi
 _CPack_Packages/*
 dir
+*.VC.db
+.vs/*
+tidy.pc

build/win64/build-bins.bat

@@ -1,3 +1,16 @@
 @setlocal
+@set TMPLOG=bldlog-p.txt
 
-cmake --build . --config Release --target PACKAGE
+@echo Running: 'cmake --build . --config Release --target PACKAGE' out to %TMPLOG%
+@echo Running: 'cmake --build . --config Release --target PACKAGE' > %TMPLOG%
+cmake --build . --config Release --target PACKAGE >> %TMPLOG%
+@if ERRORLEVEL 1 goto ISERR
+@echo Build package done... see %TMPLOG%
+@endlocal
+@exit /b 0
+
+:ISERR
+@endlocal
+@exit /b 1
+
+@REM eof

build/win64/build-me-v14.bat

@@ -0,0 +1,202 @@
+@setlocal
+@REM 20170702 - Check branch
+@set TMPBR=next
+@REM 20161002 - Change to msvc140 build
+@set VCVERS=14
+@set GENERATOR=Visual Studio %VCVERS% Win64
+@REM 20160324 - Change to relative, and use choice
+@set TMPPRJ=tidy
+@echo Build %TMPPRJ% project, in 64-bits
+@set TMPLOG=bldlog-1.txt
+@set BLDDIR=%CD%
+@set TMPROOT=..\..\..
+@set SET_BAT=%ProgramFiles(x86)%\Microsoft Visual Studio %VCVERS%.0\VC\vcvarsall.bat
+@if NOT EXIST "%SET_BAT%" goto NOBAT
+@REM if NOT EXIST %TMPROOT%\nul goto NOROOT
+@set TMPSRC=..\..
+@if NOT EXIST %TMPSRC%\CMakeLists.txt goto NOCM
+@set DOPAUSE=1
+
+@if /I "%PROCESSOR_ARCHITECTURE%" EQU "AMD64" (
+@set TMPINST=%TMPROOT%\software.x64
+) ELSE (
+ @if /I "%PROCESSOR_ARCHITECTURE%" EQU "x86_64" (
+@set TMPINST=%TMPROOT%\software.x64
+ ) ELSE (
+@echo ERROR: Appears 64-bit is NOT available... aborting...
+@goto ISERR
+ )
+)
+@if NOT EXIST %TMPINST%\nul goto NOINST
+
+@echo Doing build output to %TMPLOG%
+@echo Doing build output to %TMPLOG% > %TMPLOG%
+
+@echo Doing: 'call "%SET_BAT%" %PROCESSOR_ARCHITECTURE%'
+@echo Doing: 'call "%SET_BAT%" %PROCESSOR_ARCHITECTURE%' >> %TMPLOG%
+@call "%SET_BAT%" %PROCESSOR_ARCHITECTURE% >> %TMPLOG% 2>&1
+@if ERRORLEVEL 1 goto ERR0
+@REM call setupqt64
+@cd %BLDDIR%
+
+@REM :DNARCH
+
+@REM ############################################
+@REM NOTE: SPECIAL INSTALL LOCATION
+@REM Adjust to suit your environment
+@REM ##########################################
+@REM set TMPINST=F:\Projects\software.x64
+@set TMPOPTS=-DCMAKE_INSTALL_PREFIX=%TMPINST%
+@set TMPOPTS=%TMPOPTS% -G "%GENERATOR%"
+@REM set TMPOPTS=%TMPOPTS% -DTIDY_CONFIG_FILE="C:\MDOS\tidy5.cfg"
+@REM set TMPOPTS=%TMPOPTS% -DTIDY_USER_CONFIG_FILE="C:\MDOS\tidy5.cfg"
+@set TMPOPTS=%TMPOPTS% -DBUILD_SHARED_LIB:BOOL=OFF
+
+:RPT
+@if "%~1x" == "x" goto GOTCMD
+@if "%~1x" == "NOPAUSEx" (
+    @set DOPAUSE=0
+) else (
+    @set TMPOPTS=%TMPOPTS% %1
+)
+@shift
+@goto RPT
+:GOTCMD
+
+@call chkmsvc %TMPPRJ%
+@call chkbranch %TMPBR%
+@if ERRORLEVEL 1 goto BADBR
+:GOTBR
+
+@echo Begin %DATE% %TIME%, output to %TMPLOG%
+@echo Begin %DATE% %TIME% >> %TMPLOG%
+
+@echo Doing: 'cmake %TMPSRC% %TMPOPTS%'
+@echo Doing: 'cmake %TMPSRC% %TMPOPTS%' >> %TMPLOG%
+@cmake %TMPSRC% %TMPOPTS% >> %TMPLOG% 2>&1
+@if ERRORLEVEL 1 goto ERR1
+
+@echo Doing: 'cmake --build . --config debug'
+@echo Doing: 'cmake --build . --config debug' >> %TMPLOG%
+@cmake --build . --config debug >> %TMPLOG%
+@if ERRORLEVEL 1 goto ERR2
+
+@echo Doing: 'cmake --build . --config release'
+@echo Doing: 'cmake --build . --config release' >> %TMPLOG%
+@cmake --build . --config release >> %TMPLOG% 2>&1
+@if ERRORLEVEL 1 goto ERR3
+:DNREL
+
+@echo Appears a successful build
+@echo Note install location %TMPINST%
+@echo.
+
+@REM ##############################################
+@REM Check if should continue with install
+@REM ##############################################
+@if "%DOPAUSE%x" == "0x" goto DOINST
+@choice /? >nul 2>&1
+@if ERRORLEVEL 1 goto NOCHOICE
+@choice /D N /T 10 /M "Pausing for 10 seconds. Def=N"
+@if ERRORLEVEL 2 goto GOTNO
+@goto DOINST
+:NOCHOICE
+@echo Appears OS does not have the 'choice' command!
+@ask *** CONTINUE with install? *** Only y continues
+@if ERRORLEVEL 2 goto NOASK
+@if ERRORLEVEL 1 goto DOINST
+@echo Skipping install to %TMPINST% at this time...
+@echo.
+@goto END
+:NOASK
+@echo 'ask' utility not found in path...
+@echo.
+@echo *** CONTINUE with install? *** Only Ctrl+c aborts...
+@echo.
+@pause
+
+:DOINST
+@echo Proceeding with INSTALL...
+@echo.
+@REM cmake -P cmake_install.cmake
+@echo Doing: 'cmake --build . --config debug --target INSTALL'
+@echo Doing: 'cmake --build . --config debug --target INSTALL' >> %TMPLOG%
+@cmake --build . --config debug --target INSTALL >> %TMPLOG% 2>&1
+
+@echo Doing: 'cmake --build . --config release --target INSTALL'
+@echo Doing: 'cmake --build . --config release --target INSTALL' >> %TMPLOG%
+@cmake --build . --config release --target INSTALL >> %TMPLOG% 2>&1
+
+@fa4 " -- " %TMPLOG%
+
+@echo Done build and install of %TMPPRJ%...
+
+@goto END
+
+:GOTNO
+@echo.
+@echo No install at this time, but there may be an updexe.bat to copy the EXE to c:\MDOS...
+@echo.
+@goto END
+
+:NOBAT
+@echo Can NOT locate MSVC setup batch "%SET_BAT%"! *** FIX ME ***
+@goto ISERR
+
+@REM :NOROOT
+@REM @echo Can NOT locate %TMPROOT%! *** FIX ME ***
+@REM @goto ISERR
+
+:NOCM
+@echo Can NOT locate %TMPSRC%\CMakeLists.txt! *** FIX ME ***
+@goto ISERR
+
+:NOINST
+@echo Can NOT locate directory %TMPINST%! *** FIX ME ***
+@goto ISERR
+
+:ERR0
+@echo MSVC 10 setup error
+@goto ISERR
+
+:ERR1
+@echo cmake config, generation error
+@goto ISERR
+
+:ERR2
+@echo debug build error
+@goto ISERR
+
+:ERR3
+@fa4 "mt.exe : general error c101008d:" %TMPLOG% >nul
+@if ERRORLEVEL 1 goto ERR32
+:ERR33
+@echo release build error
+@goto ISERR
+:ERR32
+@echo Stupid error... trying again...
+@echo Doing: 'cmake --build . --config release'
+@echo Doing: 'cmake --build . --config release' >> %TMPLOG%
+@cmake --build . --config release >> %TMPLOG% 2>&1
+@if ERRORLEVEL 1 goto ERR33
+@goto DNREL
+
+:BADBR
+@call git checkout %TMPBR%
+@call chkbranch %TMPBR%
+@if ERRORLEVEL 1 goto BADBR2
+@goto GOTBR
+:BADBR2
+@call shwbranch
+@echo Not on correct branch %TMPBR%
+@goto ISERR
+
+:ISERR
+@endlocal
+@exit /b 1
+
+:END
+@endlocal
+@exit /b 0
+
+@REM eof

build/win64/build-me.bat

@@ -1,83 +1,87 @@
 @setlocal
+
+@set TMPVER=1
 @set TMPPRJ=tidy
-@echo Build %TMPPRJ% project, in 64-bits
+@set TMPSRC=..\..
+@set TMPBGN=%TIME%
+@set TMPINS=D:\Projects\3rdParty.x64
 @set TMPLOG=bldlog-1.txt
-@set BLDDIR=%CD%
-@set TMPROOT=F:\Projects
-@set SET_BAT=%ProgramFiles(x86)%\Microsoft Visual Studio 10.0\VC\vcvarsall.bat
-@if NOT EXIST "%SET_BAT%" goto NOBAT
-@if NOT EXIST %TMPROOT%\nul goto NOROOT
-@set TMPSRC=%TMPROOT%\tidy-html5
-@if NOT EXIST %TMPSRC%\CMakeLists.txt goto NOCM
+@set DOPAUSE=1
+@set TMPGEN=Visual Studio 16 2019
+@set TMPBR=next
+@set TMPINDBG=1
 
-@if /I "%PROCESSOR_ARCHITECTURE%" EQU "AMD64" (
-@set TMPINST=%TMPROOT%\software.x64
-) ELSE (
- @if /I "%PROCESSOR_ARCHITECTURE%" EQU "x86_64" (
-@set TMPINST=%TMPROOT%\software.x64
- ) ELSE (
-@echo ERROR: Appears 64-bit is NOT available... aborting...
-@goto ISERR
- )
-)
-@if NOT EXIST %TMPINST%\nul goto NOINST
-
-@echo Doing build output to %TMPLOG%
-@echo Doing build output to %TMPLOG% > %TMPLOG%
-
-@echo Doing: 'call "%SET_BAT%" %PROCESSOR_ARCHITECTURE%'
-@echo Doing: 'call "%SET_BAT%" %PROCESSOR_ARCHITECTURE%' >> %TMPLOG%
-@call "%SET_BAT%" %PROCESSOR_ARCHITECTURE% >> %TMPLOG% 2>&1
-@if ERRORLEVEL 1 goto ERR0
-@REM call setupqt64
-@cd %BLDDIR%
-
-:DNARCH
-
-@REM ############################################
-@REM NOTE: SPECIAL INSTALL LOCATION
-@REM Adjust to suit your environment
-@REM ##########################################
-@REM set TMPINST=F:\Projects\software.x64
-@set TMPOPTS=-DCMAKE_INSTALL_PREFIX=%TMPINST%
-@set TMPOPTS=%TMPOPTS% -G "Visual Studio 10 Win64"
-@REM set TMPOPTS=%TMPOPTS% -DTIDY_CONFIG_FILE="C:\MDOS\tidy5.cfg"
-@REM set TMPOPTS=%TMPOPTS% -DTIDY_USER_CONFIG_FILE="C:\MDOS\tidy5.cfg"
+@set TMPOPTS=-G "%TMPGEN%" -A x64
+@set TMPOPTS=%TMPOPTS% -DCMAKE_INSTALL_PREFIX=%TMPINS%
+@set TMPOPTS=%TMPOPTS% -DBUILD_SHARED_LIB=ON
 
 :RPT
 @if "%~1x" == "x" goto GOTCMD
-@set TMPOPTS=%TMPOPTS% %1
+@if "%~1x" == "NOPAUSEx" (
+    @set DOPAUSE=0
+) else (
+    @set TMPOPTS=%TMPOPTS% %1
+)
 @shift
 @goto RPT
 :GOTCMD
 
 @call chkmsvc %TMPPRJ%
+@if "%TMPBR%x" == "x" goto DNBR
+@call chkbranch %TMPBR%
+@if ERRORLEVEL 1 goto BAD_BR
+:DNBR
 
-@echo Begin %DATE% %TIME%, output to %TMPLOG%
-@echo Begin %DATE% %TIME% >> %TMPLOG%
+@echo Build %TMPPRJ% 64-bits %DATE% %TIME%, in %CD%, to  %TMPLOG% > %TMPLOG%
 
-@echo Doing: 'cmake %TMPSRC% %TMPOPTS%'
-@echo Doing: 'cmake %TMPSRC% %TMPOPTS%' >> %TMPLOG%
-@cmake %TMPSRC% %TMPOPTS% >> %TMPLOG% 2>&1
+@if NOT EXIST %TMPSRC%\nul goto NOSRC
+
+@echo Build source %TMPSRC%... all output to build log %TMPLOG%
+@echo Build source %TMPSRC%... all output to build log %TMPLOG% >> %TMPLOG%
+
+@if EXIST build-cmake.bat (
+@call build-cmake >> %TMPLOG%
+)
+
+@if NOT EXIST %TMPSRC%\CMakeLists.txt goto NOCM
+
+@echo Doing: 'cmake -S %TMPSRC% %TMPOPTS%'
+@echo Doing: 'cmake -S %TMPSRC% %TMPOPTS%' >> %TMPLOG% 2>&1
+@cmake -S %TMPSRC% %TMPOPTS% >> %TMPLOG% 2>&1
 @if ERRORLEVEL 1 goto ERR1
 
-@echo Doing: 'cmake --build . --config debug'
-@echo Doing: 'cmake --build . --config debug' >> %TMPLOG%
-@cmake --build . --config debug >> %TMPLOG%
+@echo Doing: 'cmake --build . --config Debug'
+@echo Doing: 'cmake --build . --config Debug'  >> %TMPLOG% 2>&1
+@cmake --build . --config Debug  >> %TMPLOG% 2>&1
 @if ERRORLEVEL 1 goto ERR2
 
-@echo Doing: 'cmake --build . --config release'
-@echo Doing: 'cmake --build . --config release' >> %TMPLOG%
-@cmake --build . --config release >> %TMPLOG% 2>&1
+@echo Doing: 'cmake --build . --config Release'
+@echo Doing: 'cmake --build . --config Release'  >> %TMPLOG% 2>&1
+@cmake --build . --config Release  >> %TMPLOG% 2>&1
 @if ERRORLEVEL 1 goto ERR3
-:DNREL
 
-@echo Appears a successful build
+@fa4 "***" %TMPLOG%
+@call elapsed %TMPBGN%
+@echo Appears a successful build... see %TMPLOG%
+@echo Note install location %TMPINS%
+@if "%TMPINDBG%x" == "1x" (
+@echo Will install Debug and Release
+) else (
+@echo Will only install Release
+)
 @echo.
-@REM echo No INSTALL configured at this time
-@REM goto END
 
-@echo Note install location %TMPINST%
+@REM ##############################################
+@REM Check if should continue with install
+@REM ##############################################
+@if "%DOPAUSE%x" == "0x" goto DOINST
+@choice /? >nul 2>&1
+@if ERRORLEVEL 1 goto NOCHOICE
+@choice /D N /T 10 /M "Pausing for 10 seconds. Def=N"
+@if ERRORLEVEL 2 goto GOTNO
+@goto DOINST
+:NOCHOICE
+@echo Appears OS does not have the 'choice' command!
 @ask *** CONTINUE with install? *** Only y continues
 @if ERRORLEVEL 2 goto NOASK
 @if ERRORLEVEL 1 goto DOINST
@@ -85,69 +89,99 @@
 @echo.
 @goto END
 :NOASK
-@echo ask not found in path...
-@echo *** CONTINUE with install? *** Only y continues
+@echo 'ask' utility not found in path...
+@echo.
+@echo *** CONTINUE with install? *** Only Ctrl+c aborts...
+@echo.
 @pause
 
 :DOINST
-@REM cmake -P cmake_install.cmake
-@echo Doing: 'cmake --build . --config debug --target INSTALL'
-@echo Doing: 'cmake --build . --config debug --target INSTALL' >> %TMPLOG%
-@cmake --build . --config debug --target INSTALL >> %TMPLOG% 2>&1
+@echo Proceeding with INSTALL...
+@echo.
+@if NOT "%TMPINDBG%x" == "1x" goto DNDBGIN
+@if EXIST install_manifest.txt @del install_manifest.txt
+@echo Doing: 'cmake --build . --config Debug  --target INSTALL'
+@echo Doing: 'cmake --build . --config Debug  --target INSTALL' >> %TMPLOG% 2>&1
+@cmake --build . --config Debug  --target INSTALL >> %TMPLOG% 2>&1
+@if ERRORLEVEL 1 goto ERR4
+@if EXIST install_manifest.txt (
+    @copy install_manifest.txt install_manifest_debug.txt >nul
+    @call add2installs install_manifest.txt -o %TMPINS%\install_manifest.txt >> %TMPLOG%
+)
+:DNDBGIN
 
-@echo Doing: 'cmake --build . --config release --target INSTALL'
-@echo Doing: 'cmake --build . --config release --target INSTALL' >> %TMPLOG%
-@cmake --build . --config release --target INSTALL >> %TMPLOG% 2>&1
+@if EXIST install_manifest.txt @del install_manifest.txt
+@echo Doing: 'cmake --build . --config Release  --target INSTALL'
+@echo Doing: 'cmake --build . --config Release  --target INSTALL' >> %TMPLOG% 2>&1
+@cmake --build . --config Release  --target INSTALL >> %TMPLOG% 2>&1
+@if ERRORLEVEL 1 goto ERR5
+@if EXIST install_manifest.txt (
+    @copy install_manifest.txt install_manifest_release.txt >nul
+    @call add2installs install_manifest.txt -o %TMPINS%\install_manifest.txt >> %TMPLOG%
+)
 
 @fa4 " -- " %TMPLOG%
 
-@echo Done build and install of %TMPPRJ%...
+@call elapsed %TMPBGN%
+@echo All done... see %TMPLOG%
 
 @goto END
 
-:NOBAT
-@echo Can NOT locate MSVC setup batch "%SET_BAT%"! *** FIX ME ***
+:BAD_BR
+@echo Try to do 'git checkout %TMPBR%'
+@git checkout %TMPBR% >> %TMPLOG% 2>&1
+@call chkbranch %TMPBR%
+@if ERRORLEVEL 1 goto NO_BR
+@goto DNBR
+:NO_BR
+@echo.
+@echo Unable to check out %TMPBR%! *** FIX ME ***
+@echo.
 @goto ISERR
 
-:NOROOT
-@echo Can NOT locate %TMPROOT%! *** FIX ME ***
+:GOTNO
+@echo.
+@echo No install at this time, but there may be an updexe.bat to copy the EXE to c:\MDOS...
+@echo.
+@goto END
+
+:NOSRC
+@echo Can NOT locate source %TMPSRC%! *** FIX ME ***
+@echo Can NOT locate source %TMPSRC%! *** FIX ME *** >> %TMPLOG%
 @goto ISERR
 
 :NOCM
-@echo Can NOT locate %TMPSRC%\CMakeLists.txt! *** FIX ME ***
-@goto ISERR
-
-:NOINST
-@echo Can NOT locate directory %TMPINST%! *** FIX ME ***
-@goto ISERR
-
-:ERR0
-@echo MSVC 10 setup error
+@echo Can NOT locate %TMPSRC%\CMakeLists.txt!
+@echo Can NOT locate %TMPSRC%\CMakeLists.txt! >> %TMPLOG%
 @goto ISERR
 
 :ERR1
-@echo cmake config, generation error
+@echo cmake configuration or generations ERROR
+@echo cmake configuration or generations ERROR >> %TMPLOG%
 @goto ISERR
 
 :ERR2
-@echo debug build error
+@echo ERROR: Cmake build Debug FAILED!
+@echo ERROR: Cmake build Debug FAILED! >> %TMPLOG%
 @goto ISERR
 
 :ERR3
-@fa4 "mt.exe : general error c101008d:" %TMPLOG% >nul
-@if ERRORLEVEL 1 goto ERR32
-:ERR33
-@echo release build error
+@echo ERROR: Cmake build Release FAILED!
+@echo ERROR: Cmake build Release FAILED! >> %TMPLOG%
+@goto ISERR
+
+:ERR4
+@echo ERROR: Install Debug FAILED!
+@echo ERROR: Install Debug  FAILED! >> %TMPLOG%
+@goto ISERR
+
+:ERR5
+@echo ERROR: Install Release FAILED!
+@echo ERROR: Install Release  FAILED! >> %TMPLOG%
 @goto ISERR
-:ERR32
-@echo Stupid error... trying again...
-@echo Doing: 'cmake --build . --config release'
-@echo Doing: 'cmake --build . --config release' >> %TMPLOG%
-@cmake --build . --config release >> %TMPLOG% 2>&1
-@if ERRORLEVEL 1 goto ERR33
-@goto DNREL
 
 :ISERR
+@echo See %TMPLOG% for details...
 @endlocal
 @exit /b 1
 

build/win64/gen-html.bat

@@ -0,0 +1,93 @@
+@setlocal
+@REM Build HTML from log of 'version.txt'
+@REM Versify the tools used
+@call verhist -? >nul
+@if ERRORLEVEL 1 (
+@echo Unable to run 'verhist.pl'! *** FIX ME ***
+@exit /b 1
+)
+@call emailobfuscate -? >nul
+@if ERRORLEVEL 1 (
+@echo Unable to run 'emailobfuscate.pl'! *** FIX ME ***
+@exit /b 1
+)
+
+@set TMPFIL1=..\..\version.txt
+@if NOT EXIST %TMPFIL1% (
+@echo Can NOT locate %TMPFIL1%, in %CD% - *** FIX ME ***
+@exit /b 1
+)
+
+@call dirmin %TMPFIL1%
+
+@set /P TMPVER=<%TMPFIL1%
+
+@echo Current version '%TMPVER%' ...
+@set TMPLOG1=..\..\..\temp-%TMPVER%.log
+@set TMPLOG2=..\..\..\temp2-%TMPVER%.log
+@set TMPLOG3=..\..\..\temp3-%TMPVER%.log
+
+@if EXIST %TMPLOG1% goto GOTL1
+@call git log -p %TMPFIL1% > %TMPLOG1%
+@if NOT EXIST %TMPLOG1% (
+@echo Gen of %TMPLOG1% FAILED! *** FIX ME ***
+@exit /b 1
+)
+:GOTL1
+@echo Got log 1 '%TMPLOG1%' ...
+@call dirmin %TMPLOG1%
+
+@if EXIST %TMPLOG2% goto GOTL2
+@call verhist %TMPLOG1% -o %TMPLOG2%
+@if EXIST %TMPLOG2% goto GOTL2
+@echo Gen of %TMPLOG2% FAILED! *** FIX ME ***
+@exit /b 1
+:GOTL2
+@echo Got log 2 '%TMPLOG2%' ...
+@call dirmin %TMPLOG2%
+
+@set TMPV=%1
+@if "%TMPV%x" == "x" (
+@echo Give the cut-off version, like 5.6.0, to continue..
+@exit /b 1
+)
+
+@echo Doing: 'call grep %TMPV% %TMPLOG2%' ...
+@call grep %TMPV% %TMPLOG2%
+@if ERRORLEVEL 1 (
+@echo Failed to find '%TMPV%'... check the file '%TMPLOG2%'
+@exit /b 1
+)
+
+@set TMPD=%~2
+@if "%TMPD%x" == "x" (
+@echo Give the DATE of the cut-off, like 'Sat Nov 25 14:50:00 2017 +0100', to continue...
+@exit /b 1
+)
+
+@if EXIST %TMPLOG3% goto GOTL3
+@call git log "--decorate=full" "--since=%TMPD%" > %TMPLOG3%
+@if EXIST %TMPLOG3% goto GOTL3
+@echo Failed to generate 'git log ...' - *** FIX ME ***
+@exit /b 1
+:GOTL3
+@echo Got log 3 '%TMPLOG3%' ...
+@call dirmin %TMPLOG3%
+
+@REM at last generate the release HTML
+
+@set TMPHTM=..\..\..\temp-%TMPVER%.html
+@if EXIST %TMPHTM% goto GOTL4
+@call emailobfuscate %TMPLOG3% -o %TMPHTM% -a %TMPVER% -i
+@if EXIST %TMPHTM% goto GOTL4
+@echo FAILED to generate %TMPHTM%! *** FIX ME ***
+@exit /b 1
+:GOTL4
+@echo Got HTML '%TMPHTM%' ...
+@call dirmin %TMPHTM%
+
+@REM All success - check image
+@call start %TMPHTM%
+
+@REM eof
+

build/win64/pub-bins.bat

@@ -1,4 +1,5 @@
 @setlocal
+@set TMPWV=win64
 @set TMPSRC=../..
 @set TMPNAME=tidy
 @set TMPFIL=%TMPSRC%\version.txt
@@ -21,17 +22,26 @@
 @set DOPAUSE=echo No pause requested...
 )
 
-@set TMPFIL1=%TMPNAME%-%TMPVER%-win64.exe
-@set TMPFIL2=%TMPNAME%-%TMPVER%-win64.msi
-@set TMPFIL3=%TMPNAME%-%TMPVER%-win64.zip
-@if NOT EXIST %TMPFIL1% goto NOFIL1
-@if NOT EXIST %TMPFIL2% goto NOFIL2
-@if NOT EXIST %TMPFIL3% goto NOFIL3
-@echo.
 @echo Will publish...
+@set TMPCNT=0
+@set TMPFIL1=%TMPNAME%-%TMPVER%-%TMPWV%.exe
+@set TMPFIL2=%TMPNAME%-%TMPVER%-%TMPWV%.msi
+@set TMPFIL3=%TMPNAME%-%TMPVER%-%TMPWV%.zip
+@if EXIST %TMPFIL1% (
 @echo %TMPFIL1%
+@set /A TMPCNT+=1
+)
+@if EXIST %TMPFIL2% (
 @echo %TMPFIL2%
+@set /A TMPCNT+=1
+)
+@if EXIST %TMPFIL3% (
 @echo %TMPFIL3%
+@set /A TMPCNT+=1
+)
+@if "%TMPCNT%x" == "0x" goto NOPUB
+@echo.
+@echo Will publish %TMPCNT% files to %TMPDD%
 @echo.
 @echo *** CONTINUE?%
 @%DOPAUSE%
@@ -41,18 +51,25 @@
 @if NOT EXIST %TMPDD%\nul goto NODST
 )
 
+@if EXIST %TMPFIL1% (
 @set TMPSRC=%TMPFIL1%
 @set TMPDST=%TMPDD%\%TMPFIL1%
 @call :CHKCOPY
+)
+
+@if EXIST %TMPFIL2% (
 @set TMPSRC=%TMPFIL2%
 @set TMPDST=%TMPDD%\%TMPFIL2%
 @call :CHKCOPY
+)
+
+@if EXIST %TMPFIL3% (
 @set TMPSRC=%TMPFIL3%
 @set TMPDST=%TMPDD%\%TMPFIL3%
 @call :CHKCOPY
-
+)
 @echo.
-@echo Maybe time to run 'gentidyyml %TMPBIN%'
+@echo If done all bins, WIN32, WIN64, linux, ... maybe time to run 'gentidyyml %TMPBIN%'
 @echo.
 
 @goto END
@@ -88,16 +105,14 @@ copy %TMPSRC% %TMPDST%
 
 :NODST
 @echo Error: Unable to create %TMPDD%
+@goto END
 
-
+:NOPUB
+@echo Appears no files to PUBLISH!
 :NOFIL1
 @echo Can NOT locate %TMPFIL1%! *** FIX ME ***
-@goto END
-
 :NOFIL2
 @echo Can NOT locate %TMPFIL2%! *** FIX ME ***
-@goto END
-
 :NOFIL3
 @echo Can NOT locate %TMPFIL3%! *** FIX ME ***
 @goto END

console/Info.plist.in

@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
+<plist version="1.0">
+<dict>
+        <key>CFBundleDisplayName</key>
+        <string>HTML Tidy</string>
+        <key>CFBundleIdentifier</key>
+        <string>org.htacg.html-tidy.tidy5</string>
+        <key>CFBundleInfoDictionaryVersion</key>
+        <string>6.0</string>
+        <key>CFBundleShortVersionString</key>
+        <string>@LIBTIDY_VERSION@</string>
+        <key>CFBundleVersion</key>
+        <string>@LIBTIDY_DATE@</string>
+        <key>NSHumanReadableCopyright</key>
+        <string>©@CURRENT_YEAR@ HTACG and Contributors</string>
+</dict>
+</plist>

documentation/DoxygenLayout.xml

@@ -1,198 +0,0 @@
-<doxygenlayout version="1.0">
-  <!-- Generated by doxygen 1.8.9.1 -->
-  <!-- Navigation index tabs for HTML output -->
-  <navindex>
-    <tab type="mainpage" visible="yes" title="Tidy Home"/>
-    <tab type="pages" visible="yes" title="Pages" intro=""/>
-    <tab type="modules" visible="yes" title="" intro=""/>
-    <tab type="namespaces" visible="yes" title="">
-      <tab type="namespacelist" visible="yes" title="" intro=""/>
-      <tab type="namespacemembers" visible="yes" title="" intro=""/>
-    </tab>
-    <tab type="classes" visible="yes" title="">
-      <tab type="classlist" visible="yes" title="" intro=""/>
-      <tab type="classindex" visible="$ALPHABETICAL_INDEX" title=""/> 
-      <tab type="hierarchy" visible="yes" title="" intro=""/>
-      <tab type="classmembers" visible="yes" title="" intro=""/>
-    </tab>
-    <tab type="files" visible="yes" title="">
-      <tab type="filelist" visible="yes" title="" intro=""/>
-      <tab type="globals" visible="yes" title="" intro=""/>
-    </tab>
-    <tab type="examples" visible="yes" title="" intro=""/>
-    <tab type="user" url="https://github.com/htacg/tidy-html5/issues" title="Bugs &amp; Issues"/>
-    <tab type="user" url="https://github.com/htacg/tidy-html5" title="github"/>
-    <tab type="user" url="http://www.htacg.org/" title="htacg.org"/>
-    <tab type="user" url="http://www.html-tidy.org/" title="html-tidy.org"/>
-  </navindex>
-
-  <!-- Layout definition for a class page -->
-  <class>
-    <briefdescription visible="yes"/>
-    <includes visible="$SHOW_INCLUDE_FILES"/>
-    <inheritancegraph visible="$CLASS_GRAPH"/>
-    <collaborationgraph visible="$COLLABORATION_GRAPH"/>
-    <memberdecl>
-      <nestedclasses visible="yes" title=""/>
-      <publictypes title=""/>
-      <services title=""/>
-      <interfaces title=""/>
-      <publicslots title=""/>
-      <signals title=""/>
-      <publicmethods title=""/>
-      <publicstaticmethods title=""/>
-      <publicattributes title=""/>
-      <publicstaticattributes title=""/>
-      <protectedtypes title=""/>
-      <protectedslots title=""/>
-      <protectedmethods title=""/>
-      <protectedstaticmethods title=""/>
-      <protectedattributes title=""/>
-      <protectedstaticattributes title=""/>
-      <packagetypes title=""/>
-      <packagemethods title=""/>
-      <packagestaticmethods title=""/>
-      <packageattributes title=""/>
-      <packagestaticattributes title=""/>
-      <properties title=""/>
-      <events title=""/>
-      <privatetypes title=""/>
-      <privateslots title=""/>
-      <privatemethods title=""/>
-      <privatestaticmethods title=""/>
-      <privateattributes title=""/>
-      <privatestaticattributes title=""/>
-      <friends title=""/>
-      <related title="" subtitle=""/>
-      <membergroups visible="yes"/>
-    </memberdecl>
-    <detaileddescription title=""/>
-    <memberdef>
-      <inlineclasses title=""/>
-      <typedefs title=""/>
-      <enums title=""/>
-      <services title=""/>
-      <interfaces title=""/>
-      <constructors title=""/>
-      <functions title=""/>
-      <related title=""/>
-      <variables title=""/>
-      <properties title=""/>
-      <events title=""/>
-    </memberdef>
-    <allmemberslink visible="yes"/>
-    <usedfiles visible="$SHOW_USED_FILES"/>
-    <authorsection visible="yes"/>
-  </class>
-
-  <!-- Layout definition for a namespace page -->
-  <namespace>
-    <briefdescription visible="yes"/>
-    <memberdecl>
-      <nestednamespaces visible="yes" title=""/>
-      <constantgroups visible="yes" title=""/>
-      <classes visible="yes" title=""/>
-      <typedefs title=""/>
-      <enums title=""/>
-      <functions title=""/>
-      <variables title=""/>
-      <membergroups visible="yes"/>
-    </memberdecl>
-    <detaileddescription title=""/>
-    <memberdef>
-      <inlineclasses title=""/>
-      <typedefs title=""/>
-      <enums title=""/>
-      <functions title=""/>
-      <variables title=""/>
-    </memberdef>
-    <authorsection visible="yes"/>
-  </namespace>
-
-  <!-- Layout definition for a file page -->
-  <file>
-    <briefdescription visible="yes"/>
-    <includes visible="$SHOW_INCLUDE_FILES"/>
-    <includegraph visible="$INCLUDE_GRAPH"/>
-    <includedbygraph visible="$INCLUDED_BY_GRAPH"/>
-    <sourcelink visible="yes"/>
-    <memberdecl>
-      <classes visible="yes" title=""/>
-      <namespaces visible="yes" title=""/>
-      <constantgroups visible="yes" title=""/>
-      <defines title=""/>
-      <typedefs title=""/>
-      <enums title=""/>
-      <functions title=""/>
-      <variables title=""/>
-      <membergroups visible="yes"/>
-    </memberdecl>
-    <detaileddescription title=""/>
-    <memberdef>
-      <inlineclasses title=""/>
-      <defines title=""/>
-      <typedefs title=""/>
-      <enums title=""/>
-      <functions title=""/>
-      <variables title=""/>
-    </memberdef>
-    <authorsection/>
-  </file>
-
-  <!-- Layout definition for a group page -->
-  <group>
-    <briefdescription visible="yes"/>
-    <groupgraph visible="$GROUP_GRAPHS"/>
-    <memberdecl>
-      <nestedgroups visible="yes" title=""/>
-      <dirs visible="yes" title=""/>
-      <files visible="yes" title=""/>
-      <namespaces visible="yes" title=""/>
-      <classes visible="yes" title=""/>
-      <defines title=""/>
-      <typedefs title=""/>
-      <enums title=""/>
-      <enumvalues title=""/>
-      <functions title=""/>
-      <variables title=""/>
-      <signals title=""/>
-      <publicslots title=""/>
-      <protectedslots title=""/>
-      <privateslots title=""/>
-      <events title=""/>
-      <properties title=""/>
-      <friends title=""/>
-      <membergroups visible="yes"/>
-    </memberdecl>
-    <detaileddescription title=""/>
-    <memberdef>
-      <pagedocs/>
-      <inlineclasses title=""/>
-      <defines title=""/>
-      <typedefs title=""/>
-      <enums title=""/>
-      <enumvalues title=""/>
-      <functions title=""/>
-      <variables title=""/>
-      <signals title=""/>
-      <publicslots title=""/>
-      <protectedslots title=""/>
-      <privateslots title=""/>
-      <events title=""/>
-      <properties title=""/>
-      <friends title=""/>
-    </memberdef>
-    <authorsection visible="yes"/>
-  </group>
-
-  <!-- Layout definition for a directory page -->
-  <directory>
-    <briefdescription visible="yes"/>
-    <directorygraph visible="yes"/>
-    <memberdecl>
-      <dirs visible="yes"/>
-      <files visible="yes"/>
-    </memberdecl>
-    <detaileddescription title=""/>
-  </directory>
-</doxygenlayout>

documentation/README.md

@@ -1,6 +0,0 @@
-Documentation
-=============
-
-This directory does _not_ contain documentation for HTML Tidy. It consists of files used for generating documentation for HTML Tidy.
-
-Please consult the main README file for more information.

documentation/examples/example.1.c

@@ -1,49 +0,0 @@
-
-
-#include <tidy.h>;
-#include <tidybuffio.h>;
-#include <stdio.h>;
-#include <errno.h>;
-
-int main(int argc, char **argv )
-{
-    const char* input = "<title>Hello</title><p>World!";
-    TidyBuffer output = {0};
-    TidyBuffer errbuf = {0};
-    int rc = -1;
-    Bool ok;
-
-    // Initialize "document"
-    TidyDoc tdoc = tidyCreate();
-    printf( "Tidying:\t%s\n", input );
-
-    // Convert to XHTML
-    ok = tidyOptSetBool( tdoc, TidyXhtmlOut, yes );  
-    if ( ok )
-        rc = tidySetErrorBuffer( tdoc, &errbuf );    // Capture diagnostics
-    if ( rc >= 0 )
-        rc = tidyParseString( tdoc, input );         // Parse the input
-    if ( rc >= 0 )
-        rc = tidyCleanAndRepair( tdoc );             // Tidy it up!
-    if ( rc >= 0 )
-        rc = tidyRunDiagnostics( tdoc );             // Kvetch
-    if ( rc > 1 )                                    // If error, force output.
-        rc = ( tidyOptSetBool(tdoc, TidyForceOutput, yes) ? rc : -1 );
-    if ( rc >= 0 )
-        rc = tidySaveBuffer( tdoc, &output );        // Pretty Print
-
-    if ( rc >= 0 )
-    {
-    if ( rc > 0 )
-        printf( "\nDiagnostics:\n\n%s", errbuf.bp );
-    printf( "\nAnd here is the result:\n\n%s", output.bp );
-    }
-    else
-        printf( "A severe error (%d) occurred.\n", rc );
-
-    tidyBufFree( &output );
-    tidyBufFree( &errbuf );
-    tidyRelease( tdoc );
-    return rc;
-}
-

documentation/examples/example_config.txt

@@ -1,22 +0,0 @@
-// sample config file for HTML tidy
-indent: auto
-indent-spaces: 2
-wrap: 72
-markup: yes
-output-xml: no
-input-xml: no
-show-warnings: yes
-numeric-entities: yes
-quote-marks: yes
-quote-nbsp: yes
-quote-ampersand: no
-break-before-br: no
-uppercase-tags: no
-uppercase-attributes: no
-char-encoding: latin1
-new-inline-tags: cfif, cfelse, math, mroot,
-  mrow, mi, mn, mo, msqrt, mfrac, msubsup, munderover,
-  munder, mover, mmultiscripts, msup, msub, mtext,
-  mprescripts, mtable, mtr, mtd, mth
-new-blocklevel-tags: cfoutput, cfquery
-new-empty-tags: cfelse

documentation/pages/main_page.dox

@@ -1,52 +0,0 @@
-/*!
-
-\mainpage Tidy home
-
-\note The repository <a href="https://github.com/htacg/tidy-html5">github.com/htacg/tidy-html5</a> and this documentation should be considered  canonical for HTML Tidy as of 2015-January-15. See \ref history
-
-
-\b Tidy corrects and cleans up HTML content by fixing markup errors such as mismatched, misnested and missing tags, missing end "/" tags, missing quotations et all, eg:
-
-
-\code{.html}
-<h1><hr>heading</h1>
-<h2>sub<hr>heading</h2>
-<a href="#refs">References<a>
-\endcode
-is converted to
-\code{.html}
-<hr>
-<h1>heading</h1>
-<h2>sub</h2>
-<hr>
-<h2>heading</h2>
-<a href="#refs">References</a>
-\endcode
-
-
-<h4>This project has two parts:</h4>
-
--  \ref tidylib 
-        - a C static or dynamic library that developers can integrate into their applications 
-          in order to bring all of Tidy’s power to your favorite tools. 
-        
--  \ref tidy_cmd 
-        - a console application built on \ref tidylib for Mac OS X, Linux, Windows, UNIX, and more. 
-
-\section content Contents
-- \ref quick_ref
-- \ref tidy_cmd
-  - \ref tidy_quickstart
-  - \ref tidy_config
-  - \ref featured_options
-  - \ref tidy_scripting
-- \ref tidylib
-  - <a href="modules.html">Modules</a>
-- \ref building_tidy
--\ref docs_howto
-- \subpage history
-- \subpage license    
-- \ref todo    
-    
-
-*/

documentation/pages/page_building.dox

@@ -1,98 +0,0 @@
-/*!
-
-
-\page building_tidy Building Tidy
-
-How to compile and install Tidy from source code.
-
-\tableofcontents
-  
-\section Prerequisites
-
- - \b git - <a href="http://git-scm.com/book/en/v2/Getting-Started-Installing-Git">git-scm.com/book/en/v2/Getting-Started-Installing-Git</a>
- - \b cmake - <a href="http://www.cmake.org/download/">cmake.org/download/</a>
- - Appropriate build tools for the platform
-
-CMake comes in two forms - command line and gui. Some installations only install one or the other, but sometimes both. The build 
-commands below are only for the command line use.
-
-Also the actual build tools vary for each platform. But that is one of the great features of cmake, it can generate 
-variuous 'native' build files. Running cmake without any parameters will list the generators 
-available on that platform. For sure one of the common ones is "Unix Makefiles", which needs autotools 
-make installed, but many other generators are supported.
-
-In windows cmake offers various versions of MSVC. Again below only the command line use of MSVC is shown, but the 
-tidy solution (*.sln) file can be loaded into the MSVC IDE, and the building done in there.
-
-\section get_source Get the source code
-
-Tidy’s sourcecode can be found at <a href="https://github.com/htacg/tidy-html5">github.com/htacg/tidy-html5</a>. There are sometimes 
-several branches, but in general `master` is the most recently updated version. 
-
-\note Note that as “cutting edge,” it may have bugs or other 
-unstable behavior. If you prefer a stable, officially released version, be sure to have a look 
-at Releases on the github page.
-
-In general you can use the <b>Download ZIP</b> button on the github page to download the most recent version of a branch. If you prefer 
-Git then you can  clone the repository to a working machine with:
-
-
-\code{.sh}
-git clone git@github.com:htacg/tidy-html5.git
-\endcode
-
-\section compile Compile
-
-<h4>Enter the `build/cmake` directory</h4>
-\code{.sh}
-# *nix
-cd {your-tidy-html5-directory}/build/cmake
-
-# windows
-cd {your-tidy-html5-directory}\build\cmake
-\endcode
-
-<h4>Configure the build</h4>
-\code{.sh}
-# *nix
-cmake ../../ [-DCMAKE_INSTALL_PREFIX=/path/for/install]
-
-# windows
-cmake ..\..\ 
-\endcode
-By default cmake sets the install path to `/usr/local` in unix. 
-
-If you wanted the binary in say `/usr/bin` instead, then use `-DCMAKE_INSTALL_PREFIX=/usr`
-
-On windows the default install is to `C:\Program Files\tidy5`, or `C:/Program Files (x86)/tidy5`, which is not very useful. After 
-the build the `tidy[n].exe` is in the `Release\` directory, and can be copied to any directory in your `PATH` environment variable, for global use.
-
-If you need the tidy library built as a 'shared' (DLL) library, then in add the command `-DBUILD_SHARED_LIB:BOOL=ON`. 
-This option is `OFF` by default, so the static library is built and linked with the command line tool for convenience.
-
-
-<h4>Compile</h4>
-\code{.sh}
-# *nix
-make
-
-# windows
-cmake --build . --config Release
-\endcode
-
-
-\section compileOnstall Install
-Install the applicatio and library with
-
-\code{.sh}
-# *nix
-[sudo] make install
-
-# windows
-cmake --build . --config Release --target INSTALL
-\endcode
-
-
-
-
-*/

documentation/pages/page_featured_options.dox

@@ -1,146 +0,0 @@
-/*!
-
-
-\page featured_options Featured Options
-
-Overview of popular features and problems
-
-\tableofcontents
-
-\section indenting Indenting output for readability
-
-Indenting the source markup of an HTML document makes the markup easier to read. Tidy can indent the 
-markup for an HTML document while recognizing elements whose contents should not be indented. In the 
-example below, Tidy indents the output while preserving the formatting of the `<pre>` element:
-
-Input:
-\code{.html}
-<html>
- <head>
- <title>Test document</title>
- </head>
- <body>
- <p>This example shows how Tidy can indent output while preserving
- formatting of particular elements.</p>
-
- <pre>This is
- <em>genuine
-       preformatted</em>
-    text
- </pre>
- </body>
- </html>
- \endcode 
- 
- Output:
-\code{.html}
-<html>
-    <head>
-        <title>Test document</title>
-    </head>
-
-    <body>
-        <p>This example shows how Tidy can indent output while preserving
-        formatting of particular elements.</p>
-<pre>
-This is
-<em>genuine
-       preformatted</em>
-   text
-</pre>
-    </body>
-</html>
-\endcode 
-
-Tidy’s indenting behavior is not perfect and can sometimes cause your output to be rendered by browsers in a different way than the input. You can 
-avoid unexpected indenting-related rendering problems by setting `indent:no` or `indent:auto` in a config file.
-
-\note 
-    <b>Preserving original indenting not possible</b><br><br>
-    Tidy is not capable of preserving the original indenting of the markup from the input it receives. That’s because Tidy starts by 
-    building a clean parse tree from the input, and that parse tree doesn’t contain any information about the original indenting. Tidy then 
-    pretty-prints the parse tree using the current config settings. Trying to preserve the original 
-    indenting from the input would interact badly with the repair operations needed to build a clean parse tree, and would considerably complicate the code.
-
-    
-\section encodings Encodings and character references
-
-Tidy defaults to assuming you want output to be encoded in `UTF-8`. But Tidy offers you a choice of other 
-character encodings: `US ASCII`, `ISO Latin-1`, and the `ISO 2022` family of 7 bit encodings.
-
-Tidy doesn’t yet recognize the use of the HTML `<meta>` element for specifying the character encoding.
-
-The full set of HTML character references are defined. Cleaned-up output uses named character references for characters when appropriate. Otherwise, 
-characters outside the normal range are output as numeric character references.
-
-\section accessibility Accessibility
-
-Tidy offers advice on potential accessibility problems for people using non-graphical browsers.
-
-\section cleaning_presentational Cleaning up presentational markup
-
-Some tools generate HTML with presentational elements such as `<font>`, `<nobr>`, and `<center>`. Tidy’s -clean option will replace those elements with `<style>` elements and CSS.
-
-Some HTML documents rely on the presentational effects of `<p>` start tags that are not followed by any content. Tidy deletes 
-such `<p>` tags (as well as any headings that don’t have content). So do not use `<p>` tags simply for 
-adding vertical whitespace; instead use CSS, or the `<br>` element. However, note that 
-Tidy won’t discard `<p>` tags that are followed by any non-breaking space (that is, the \code&nbsp;\endcode named character reference).
-
-\section new_tags Teaching Tidy about new tags
-
-You can teach Tidy about new tags by declaring them in the configuration file, the syntax is:
-\code
-new-inline-tags: tag1, tag2, tag3
-new-empty-tags: tag1, tag2, tag3
-new-blocklevel-tags: tag1, tag2, tag3
-new-pre-tags: tag1, tag2, tag3
-\endcode
-The same tag can be defined as \b empty and as \b inline, or as \b empty and as \b block.
-
-These declarations can be combined to define a new empty inline or empty block element, but you are not advised to 
-declare tags as being both \b inline and \b block.
-
-Note that the new tags can only appear where Tidy expects inline or block-level tags respectively. That means you can’t place new 
-tags within the document head or other contexts with restricted content models.
-
-
-\section ignoring_scripting Ignoring PHP, ASP, and JSTE instructions
-
-Tidy will gracefully ignore many cases of PHP, ASP, and JSTE instructions within element content and as replacements for attributes, 
-and preserve them as-is in output; for example:
-
-\code{.php}
-<option <% if rsSchool.Fields("ID").Value
-  = session("sessSchoolID")
-  then Response.Write("selected") %>
-  value='<%=rsSchool.Fields("ID").Value%>'>
-  <%=rsSchool.Fields("Name").Value%>
-  (<%=rsSchool.Fields("ID").Value%>)
-</option>
-\endcode
-
-But note that Tidy may report missing attributes when those are “hidden” within the PHP, ASP, or JSTE code. If you use 
-PHP, ASP, or JSTE code to create a start tag, but place the end tag explicitly in the HTML markup, Tidy 
-won’t be able to match them up, and will delete the end tag. In that case you are advised to make the 
-start tag explicit and to use PHP, ASP, or JSTE code for just the attributes; for example:
-\code{.php}
-<a href="<%=random.site()%>">do you feel lucky?</a>
-\endcode
-
-Tidy can also get things wrong if the PHP, ASP, or JSTE code includes quotation marks; for example:
-\code{.php}
-value="<%=rsSchool.Fields("ID").Value%>"
-\endcode
-
-Tidy will see the quotation mark preceding ID as ending the attribute value, and proceed to complain about what follows.
-
-Tidy allows you to control whether line wrapping on spaces within PHP, ASP, and JSTE instructions is 
-enabled; see the `wrap-php`, `wrap-asp`, and `wrap-jste` config options.
-
-
-\section correcting_xml Correcting well-formedness errors in XML markup
-Tidy can help you to correct well-formedness errors in XML markup. Tidy doesn’t yet recognize all XML features, 
-though; for example, it doesn’t understand CDATA sections or DTD subsets.
-
-
-*/

documentation/pages/page_history.dox

@@ -1,54 +0,0 @@
-/*!
-
-
-\page history History
-
-Once upon a time....
-
-<p><strong>HTML Tidy</strong> was created by the <a href="http://www.w3.org/">W3C’s</a> own  <a href="http://www.w3.org/People/Raggett/">Dave Raggett</a> back in the
-dawn of the Internet age. His original Internet page is still available and
-gives a sense of the early history: <a href="http://www.w3.org/People/Raggett/tidy/">Clean up your Web pages with HTML TIDY</a>.</p>
-
-<p>Satisfied with his work Dave passed the torch to a dedicated group of
-maintainers at <a href="http://tidy.sourceforge.net/">tidy.sourceforge.net</a> where the important tasks of turning
-<strong>Tidy</strong> into a C library and keeping up with developing standards was
-performed.</p>
-
-<p>W3C members took a renewed interest in <strong>Tidy</strong> in 2011 and forked the
-project to <a href="https://github.com/w3c/tidy-html5">github</a> (now redirects to this project), where it featured
-compatibility with HTML5 via a <a href="https://lists.w3.org/Archives/Public/www-archive/2011Nov/0007.html">key contribution</a> from one of the SourceForge
-key members.</p>
-
-<p>In 2015 a group of concerned developers, users, and software integrators formed
-<a href="http://www.htacg.org">HTACG</a> with the goal of revitalizing <strong>Tidy</strong>, which had fallen into a
-non-maintained state. As a W3C Community Group, HTACG was deemed worthy by the
-W3C, and W3C passed ownership of their project to HTACG, where it is currently
-being developed and prepped for a new, stable, and modern release.</p>
-
-<p>HTACG is also working diligently with the SourceForge maintainers in an effort
-to harmonize <strong>HTML Tidy</strong> into a single, stable, solid release once again.</p>
-
-
-\code
-                                                                                      
-  +-----------------------------+                                                     
-  | w3.org/People/Raggett/tidy/ |                                                     
-  ++-------------+--------------+                                                     
-   |             |                                                                    
-   |             |    +----------------------+                                        
-   |             +--> |tidy.sourceforge.net  |                                        
-   |                  +------------------+---+                                        
-   |                                     |                                            
-   |       +--------------------+------+ | Soon                                       
-   +-->    | github.com/w3c/tidy|html5 | |                                            
-           +-+------------------+------+ |                                            
-             |                           |                                            
-             |                           |    +-------------------------------+       
-             |                           +->  | You are here:                 |       
-             |                                | github.com/htacg/tidy-html5   |       
-             +----------------------------->  +----------------------+--------+       
-                                                                                      
-\endcode
-
-
-*/

documentation/pages/page_license.dox

@@ -1,14 +0,0 @@
-/*!
-
-
-\page license License
-
-License and Legal
-
-<pre>
-\htmlinclude LICENSE.md
-</pre>
-
-
-
-*/

documentation/pages/page_quickref.dox

@@ -1,12 +0,0 @@
-/*!
-
-\page quick_ref Quick Ref
-
-Quick reference generated from the tidy command
-
-
-
-\htmlinclude quickref_include.html
-
-
-*/

documentation/pages/page_tidy.dox

@@ -1,18 +0,0 @@
-/*!
-
-Running the tidy command
-
-\page tidy_cmd tidy command
-
-  - \subpage tidy_quickstart
-  - \subpage tidy_config
-  - \subpage featured_options
-  - \subpage tidy_scripting
-  
-<pre>
-\htmlinclude tidy5.help.txt
-</pre>
-
-
-
-*/

documentation/pages/page_tidy_config.dox

@@ -1,46 +0,0 @@
-/*!
-
-\page tidy_config Configuration
-
-Configuration settings and files
-
-\tableofcontents
-
-To get a list of all configuration settings, see \ref config_options below or use:
-\code{.sh}
-tidy -help-config
-\endcode
-
-\section using_config Using a configuration file
-
-The most convenient way to configure Tidy is by using separate configuration file.
-
-Assuming you have created a Tidy configuration file named `myconfig.txt` (the name and extension don’t matter), you can instruct Tidy to use it via the 
-command line option `-config myconfig.txt` for example:
-
-\code {.sh}
-tidy -config myconfig.txt file1.html file2.html
-\endcode
-
-Alternatively, you can name the default config file via the environment 
-variable named `HTML_TIDY`, the value of which is the absolute path for the config file.
-
-You can also set config options on the command line by preceding the name of the option 
-immediately (no intervening space) with the string “--”; for example:
-
-\code {.sh}
-tidy --break-before-br true --show-warnings false
-\endcode
-
-You can find documentation for full set of configuration options on the \ref quick_ref page.
-
-\section example_config Example Configuration File
-
-\include example_config.txt
-
-\section config_options Config Options
-<pre>
-\htmlinclude tidy5.config.txt
-</pre>
-
-*/

documentation/pages/page_tidy_quickstart.dox

@@ -1,71 +0,0 @@
-/*!
-
-\page tidy_quickstart tidy command quickstart
-
-\tableofcontents
-
-This is the syntax for invoking Tidy from the command line:
-\code{.sh}
-tidy [[options] filename]
-\endcode
-
-Tidy defaults to reading from standard input, so if you run Tidy without specifying the filename argument, it will just sit there waiting for input to read.
-
-Tidy defaults to writing to standard output. So you can pipe output from Tidy to other programs, as well as pipe output from other programs to Tidy. You can page through the output from Tidy by piping it to a pager, e.g.:
-\code{.sh}
-tidy file.html | less
-\endcode
-
-\section out_file Output to file
-
-To have Tidy write its output to a file instead, either use the
-\code{.sh}
--o filename 
-or 
--output filename
-\endcode
-option, or redirect standard output to the file. For example:
-\code{.sh}
-tidy -o output.html index.html
-tidy -output output.html index.html
-tidy index.html > output.html
-\endcode
-
-All the above run Tidy on the file `index.html` and write the output to the file `output.html`, while writing any error messages to standard error.
-
-\section out_error Error output
-
-Tidy defaults to writing its error messages to standard error (that is, to the console where you’re running Tidy). To page through the error messages along with the 
-output, redirect standard error to standard output, and pipe it to your pager:
-\code{.sh}
-tidy index.html 2>&1 | less
-\endcode
-To have Tidy write the errors to a file instead, either use 
-\code{.sh}
--f filename 
-or 
--file filename
-\endcode
-option, or redirect standard error to a file:
-\code{.sh}
-tidy -o output.html -f errs.txt index.html
-tidy index.html > output.html 2> errs.txt
-\endcode
-
-Both the above run Tidy on the file `index.html` and writes the output to the file `output.html`, while writing any error messages to the `file errs.txt`.
-
-Writing the error messages to a file is especially useful if the file you are checking has many errors; reading them from a file instead of the console 
-or pager can make it easier to review them.
-
-\section out_modify Modify / Overwrite
-You can use the or `-m` or `-modify` option to modify (in-place) the contents of the input file you are checking; that is, to overwrite those contents with the output from Tidy. For example:
-
-\code{.sh}
-tidy -f errs.txt -m index.html
-\endcode
-That runs Tidy on the file `index.html`, modifying it in place and writing the error messages to the file `errs.txt`.
-
-\warning If you use the `-m` option, you should first ensure that you have a backup copy of your file.
-
-
-*/

documentation/pages/page_tidy_scripting.dox

@@ -1,31 +0,0 @@
-/*!
-
-\page tidy_scripting Running tidy in scripts
-
-If you want to run Tidy from a Perl, bash, or other scripting language you may find it of value to inspect the result returned 
-by Tidy when it exits: 
-
-- \b 0 = if everything is fine
-- \b 1 = if there were warnings and 
-- \b 2 = if there were errors. 
-
-\section perl_example_script Example Perl script
-
-\code{.pl}
-if (close(TIDY) == 0) {
-  my $exitcode = $? >> 8;
-  if ($exitcode == 1) {
-    printf STDERR "tidy issued warning messages\n";
-  } elsif ($exitcode == 2) {
-    printf STDERR "tidy issued error messages\n";
-  } else {
-    die "tidy exited with code: $exitcode\n";
-  }
-} else {
-  printf STDERR "tidy detected no errors\n";
-}
-\endcode
-
-
-
-*/

documentation/pages/page_tidylib.dox

@@ -1,53 +0,0 @@
-/*!
-
-
-
-\page tidylib tidylib
-
-About the tidylib C library and code
-
-\tableofcontents
-
-\section about_tidylib TidyLib  features
-
-- easy to integrate. Because of the near universal adoption of C linkage, a C interface may be called from a great number of programming languages.
-
-- designed to use opaque types in the public interface. This allows the application to just pass an integer around and the need to transform data types in different languages is minimized. As a results it’s straight-forward to write very thin library wrappers for C++, Pascal, and COM/ATL.
-
-- eats its own dogfood. HTML Tidy links directly to TidyLib.
-
-- is Thread Safe and Re-entrant. Because there are many uses for HTML Tidy - from content validation, content scraping, conversion to XHTML - it was important to make TidyLib run reasonably well within server applications as well as client side.
-
--  uses adaptable I/O. As part of the larger integration strategy it was decided to fully abstract all I/O. This means a (relatively) clean separation between character encoding processing and shovelling bytes back and forth. Internally, the library reads from sources and writes to sinks. This abstraction is used for both markup and configuration “files”. Concrete implementations are provided for file and memory I/O, and new sources and sinks may be provided via the public interface.
-
-\section return_code Return codes
-
-It’s important to understand that API functions that return an integer almost universally adhere to the following convention:
-
-- \b 0 == \b Success
-    - Good to go.
-- \b 1 == \b Warnings, but no errors
-   - Check the error buffer or track error messages for details.
-- \b 2 == \b Errors (and maybe warnings)
-  - By default, Tidy will not produce output. You can force output with the TidyForceOutput option. As with warnings, check error buffer or track error messages for details.
-- <b>< 0</b> == <b>Severe error</b>
-  - Usually value equals `-errno`. See errno.h.
-
-Also, by default, warning and error messages are sent to stderr. You can redirect diagnostic 
-output using either tidySetErrorFile() or tidySetErrorBuffer(). See  tidy.h for details.
-
-
-\section app_notes Application Notes
-
-Of course, there are functions to parse and save both markup and configuration files. For the adventurous, it is possible to create new input sources and output sinks. For example, a URL source could pull the markup from a given URL.
-
-It is also worth remembering that an application may instantiate any number of document and buffer objects. They are fairly cheap to initialize and destroy (just memory allocation and zeroing, really), so they may be created and destroyed locally, as needed. There is no problem keeping them around a while for keeping state. For example, a server app might keep a global document as a master configuration. As documents are parsed, they can copy their configuration data from the master instance. See tidyOptCopyConfig(). If the master copy is initialized at startup, no synchronization is necessary.
-
-
-\section example_hello tidylib example
-
-\include example.1.c
-
-
-
-*/

documentation/pages/page_todo.dox

@@ -1,14 +0,0 @@
-/*!
-
-
-\page todo Todo List
-
-The todo list.
-
-\note If this page is empty, then there are no todo items flagged in source.
-
-\xrefitem todo "Todo" "Todo List" 
-
-
-
-*/

documentation/quickref.include.xsl

@@ -1,244 +0,0 @@
-<?xml version="1.0"?>
-<!--
-    For generating the `quickref.html` web page from output of
-    `tidy -xml-config`
-
-    (c) 2005 (W3C) MIT, ERCIM, Keio University
-    See tidy.h for the copyright notice.
-
-    Written by Charles Reitzel and Jelks Cabaniss
-
--->
-
-<xsl:stylesheet version="1.0"
-                xmlns="http://www.w3.org/1999/xhtml"
-                xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
-
-<xsl:output method="xml" indent="yes"
-     encoding="us-ascii"
-     omit-xml-declaration="yes"
-     />
-
-<xsl:template match="/">
-
-    <a name="qtop"></a>
-    <h2 id="top">Option Groups</h2>
-    <ul>
-        <li><a class="h3" href="#MarkupHeader">HTML, XHTML, XML</a></li>
-        <li><a class="h3" href="#DiagnosticsHeader">Diagnostics</a></li>
-        <li><a class="h3" href="#PrettyPrintHeader">Pretty Print</a></li>
-        <li><a class="h3" href="#EncodingHeader">Character Encoding</a></li>
-        <li><a class="h3" href="#MiscellaneousHeader">Miscellaneous</a></li>
-    </ul>
-    <xsl:call-template name="link-section" />
-
-    <xsl:call-template name="detail-section" />
-
-</xsl:template>
-
-
-<!-- Named Templates: -->
-
-<xsl:template name="link-section">
-  <table summary="Tidy Options Quick Reference Header Section" border="0"
-  cellpadding="3" cellspacing="0" class="quickref">
-    <colgroup>
-      <col width="33%" />
-      <col width="33%" />
-      <col width="33%" />
-    </colgroup>
-    <xsl:call-template name="links">
-      <xsl:with-param name="class">markup</xsl:with-param>
-      <xsl:with-param name="header">HTML, XHTML, XML</xsl:with-param>
-      <xsl:with-param name="headerID">MarkupHeader</xsl:with-param>
-    </xsl:call-template>
-    <xsl:call-template name="links">
-      <xsl:with-param name="class">diagnostics</xsl:with-param>
-      <xsl:with-param name="header">Diagnostics</xsl:with-param>
-      <xsl:with-param name="headerID">DiagnosticsHeader</xsl:with-param>
-    </xsl:call-template>
-    <xsl:call-template name="links">
-      <xsl:with-param name="class">print</xsl:with-param>
-      <xsl:with-param name="header">Pretty Print</xsl:with-param>
-      <xsl:with-param name="headerID">PrettyPrintHeader</xsl:with-param>
-    </xsl:call-template>
-    <xsl:call-template name="links">
-      <xsl:with-param name="class">encoding</xsl:with-param>
-      <xsl:with-param name="header">Character Encoding</xsl:with-param>
-      <xsl:with-param name="headerID">EncodingHeader</xsl:with-param>
-    </xsl:call-template>
-    <xsl:call-template name="links">
-      <xsl:with-param name="class">misc</xsl:with-param>
-      <xsl:with-param name="header">Miscellaneous</xsl:with-param>
-      <xsl:with-param name="headerID">MiscellaneousHeader</xsl:with-param>
-    </xsl:call-template>
-  </table>
-</xsl:template>
-
-
-<xsl:template name="detail-section">
-  <table summary="Tidy Options Quick Reference Detail Section" border="0"
-    cellpadding="3" cellspacing="0">
-    <xsl:call-template name="reference">
-      <xsl:with-param name="class">markup</xsl:with-param>
-      <xsl:with-param name="header">HTML, XHTML, XML</xsl:with-param>
-      <xsl:with-param name="headerID">MarkupReference</xsl:with-param>
-    </xsl:call-template>
-    <xsl:call-template name="reference">
-      <xsl:with-param name="class">diagnostics</xsl:with-param>
-      <xsl:with-param name="header">Diagnostics</xsl:with-param>
-      <xsl:with-param name="headerID">DiagnosticsReference</xsl:with-param>
-    </xsl:call-template>
-    <xsl:call-template name="reference">
-      <xsl:with-param name="class">print</xsl:with-param>
-      <xsl:with-param name="header">Pretty Print</xsl:with-param>
-      <xsl:with-param name="headerID">PrettyPrintReference</xsl:with-param>
-    </xsl:call-template>
-    <xsl:call-template name="reference">
-      <xsl:with-param name="class">encoding</xsl:with-param>
-      <xsl:with-param name="header">Character Encoding</xsl:with-param>
-      <xsl:with-param name="headerID">EncodingReference</xsl:with-param>
-    </xsl:call-template>
-    <xsl:call-template name="reference">
-      <xsl:with-param name="class">misc</xsl:with-param>
-      <xsl:with-param name="header">Miscellaneous</xsl:with-param>
-      <xsl:with-param name="headerID">MiscellaneousReference</xsl:with-param>
-    </xsl:call-template>
-  </table>
-</xsl:template>
-
-
-<xsl:template name="links">
-  <xsl:param name="class"/>
-  <xsl:param name="header"/>
-  <xsl:param name="headerID"/>
-  <tr valign="bottom">
-    <td class="h3" colspan="2" id="{$headerID}">
-      <xsl:value-of select="$header"/> Options</td>
-    <td valign="top" class="h3top"><a href="#qtop" class="h3topa">Top</a></td>
-  </tr>
-  <xsl:call-template name="ClassHeaders" />
-  <xsl:for-each select="/config/option[@class=$class]">
-    <xsl:sort select="name" order="ascending" />
-    <tr>
-      <td class="qrow"><a href="#{name}"><xsl:value-of select="name"/></a></td>
-      <td class="qrow"><xsl:apply-templates select="type"/></td>
-      <td class="qrow"><xsl:choose>
-            <xsl:when test="string-length(default) &gt; 0 ">
-              <xsl:apply-templates select="default" />
-            </xsl:when>
-            <xsl:otherwise>
-              <strong>-</strong>
-            </xsl:otherwise>
-        </xsl:choose>
-      </td>
-    </tr>
-  </xsl:for-each>
-  <tr valign="bottom">
-    <td colspan="3">&#160;</td>
-  </tr>
-</xsl:template>
-
-
-<xsl:template name="reference">
-  <xsl:param name="class"/>
-  <xsl:param name="header"/>
-  <xsl:param name="headerID"/>
-
-  <tr>
-    <td colspan="3">&#160;</td>
-  </tr>
-  <tr valign="bottom">
-    <td valign="top" colspan="3" class="h2" id="{$headerID}">
-       <h2 class="qh2"><xsl:value-of select="$header"/></h2> 
-    </td>
-  </tr>
-  
-
-  <xsl:for-each select="/config/option[@class=$class]">
-    <xsl:sort select="name" order="ascending" />
-    <tr>
-      <td  valign="top" id="{name}" colspan="2" class="qoptiontitletd">
-        <h4 class="qoptiontitle"><xsl:value-of select="name"/></h4>
-      </td>
-      <td class="tabletitlelink" valign="top" align="right">
-          <a href="#qtop">Top</a>
-      </td>
-    </tr>
-    <tr>
-        <td valign="top" class="qlabel">Type:</td>
-        <td  class="qvalu"><xsl:value-of select="type"/></td>
-    </tr>
-    <tr>
-        <td valign="top" class="qlabel">Default:</td>
-        <td class="qvalu">
-            <xsl:choose>
-              <xsl:when test="string-length(default) &gt; 0">
-                <xsl:apply-templates select="default" />
-              </xsl:when>
-              <xsl:otherwise>-</xsl:otherwise>
-            </xsl:choose>
-        </td>
-    </tr>
-    <tr>
-        <td valign="top" class="qlabel">Example:</td>
-        <td class="qvalu">
-            <xsl:choose>
-              <xsl:when test="string-length(example) &gt; 0">
-                <xsl:apply-templates select="example"/>
-              </xsl:when>
-              <xsl:otherwise>-</xsl:otherwise>
-            </xsl:choose>
-      </td>
-    </tr>
-   
-    <xsl:choose>
-        <xsl:when test="seealso">
-        <tr>
-            <td valign="top" class="qlabel">See Also:</td>
-            <td  valign="top" class="qvalu">
-                <xsl:for-each select="seealso">
-                  <a href="#{.}"><xsl:apply-templates select="." /></a>
-                  <xsl:if test="position() != last()">, </xsl:if>
-                </xsl:for-each>
-            </td>
-        </tr>
-        </xsl:when>
-    </xsl:choose>
-     
-    <tr>
-        <td></td>
-        <td colspan="1" class="qdescription"><xsl:apply-templates select="description"/></td>
-    </tr>
-
-
-    
-    <tr>
-      <td>&#160;</td>
-    </tr>
-  </xsl:for-each>
-</xsl:template>
-
-<xsl:template name="ClassHeaders">
-      <tr>
-        <td class="tabletitle">Option</td>
-        <td class="tabletitle">Type</td>
-        <td class="tabletitle">Default</td>
-      </tr>
-</xsl:template>
-
-<xsl:template name="Stylesheet">
-	<style type="text/css">
-	/* no style */
-	</style>
-</xsl:template>
-
-
-<!-- Regular Templates: -->
-<xsl:template match="a | code | em | strong | br">
-    <xsl:element name="{local-name(.)}">
-        <xsl:copy-of select="@* | node()" />
-    </xsl:element>
-</xsl:template>
-
-</xsl:stylesheet>

documentation/quickref.xsl

@@ -1,574 +0,0 @@
-<?xml version="1.0"?>
-<!--
-    For generating the `quickref.html` web page from output of
-    `tidy -xml-config`
-
-    (c) 2005 (W3C) MIT, ERCIM, Keio University
-    See tidy.h for the copyright notice.
-
-    Written by Charles Reitzel and Jelks Cabaniss
-
--->
-
-<xsl:stylesheet version="1.0"
-                xmlns="http://www.w3.org/1999/xhtml"
-                xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
-
-<xsl:output method="xml" indent="yes"
-     encoding="us-ascii"
-     omit-xml-declaration="yes"
-     doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"
-     doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd" />
-
-<xsl:template match="/">
-  <html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml">
-  <head>
-    <title>HTML Tidy Configuration Options Quick Reference</title>
-	<xsl:call-template name="Stylesheet" />
-  </head>
-
-  <body>
-    <h1 id="top">Quick Reference</h1>
-
-    <h2>HTML Tidy Configuration Options</h2>
-
-    <p>Version: <xsl:value-of select="config/@version" /></p>
-
-    <p><a class="h3" href="#MarkupHeader">HTML, XHTML, XML</a><br />
-     <a class="h3" href="#DiagnosticsHeader">Diagnostics</a><br />
-     <a class="h3" href="#PrettyPrintHeader">Pretty Print</a><br />
-     <a class="h3" href="#EncodingHeader">Character Encoding</a><br />
-     <a class="h3" href="#MiscellaneousHeader">Miscellaneous</a></p>
-
-    <xsl:call-template name="link-section" />
-
-    <xsl:call-template name="detail-section" />
-
-  </body>
-  </html>
-</xsl:template>
-
-
-<!-- Named Templates: -->
-
-<xsl:template name="link-section">
-  <table summary="Tidy Options Quick Reference Header Section" border="0"
-  cellpadding="3" cellspacing="0">
-    <colgroup>
-      <col width="33%" />
-      <col width="33%" />
-      <col width="33%" />
-    </colgroup>
-    <xsl:call-template name="links">
-      <xsl:with-param name="class">markup</xsl:with-param>
-      <xsl:with-param name="header">HTML, XHTML, XML</xsl:with-param>
-      <xsl:with-param name="headerID">MarkupHeader</xsl:with-param>
-    </xsl:call-template>
-    <xsl:call-template name="links">
-      <xsl:with-param name="class">diagnostics</xsl:with-param>
-      <xsl:with-param name="header">Diagnostics</xsl:with-param>
-      <xsl:with-param name="headerID">DiagnosticsHeader</xsl:with-param>
-    </xsl:call-template>
-    <xsl:call-template name="links">
-      <xsl:with-param name="class">print</xsl:with-param>
-      <xsl:with-param name="header">Pretty Print</xsl:with-param>
-      <xsl:with-param name="headerID">PrettyPrintHeader</xsl:with-param>
-    </xsl:call-template>
-    <xsl:call-template name="links">
-      <xsl:with-param name="class">encoding</xsl:with-param>
-      <xsl:with-param name="header">Character Encoding</xsl:with-param>
-      <xsl:with-param name="headerID">EncodingHeader</xsl:with-param>
-    </xsl:call-template>
-    <xsl:call-template name="links">
-      <xsl:with-param name="class">misc</xsl:with-param>
-      <xsl:with-param name="header">Miscellaneous</xsl:with-param>
-      <xsl:with-param name="headerID">MiscellaneousHeader</xsl:with-param>
-    </xsl:call-template>
-  </table>
-</xsl:template>
-
-
-<xsl:template name="detail-section">
-  <table summary="Tidy Options Quick Reference Detail Section" border="0"
-    cellpadding="3" cellspacing="0">
-    <xsl:call-template name="reference">
-      <xsl:with-param name="class">markup</xsl:with-param>
-      <xsl:with-param name="header">HTML, XHTML, XML</xsl:with-param>
-      <xsl:with-param name="headerID">MarkupReference</xsl:with-param>
-    </xsl:call-template>
-    <xsl:call-template name="reference">
-      <xsl:with-param name="class">diagnostics</xsl:with-param>
-      <xsl:with-param name="header">Diagnostics</xsl:with-param>
-      <xsl:with-param name="headerID">DiagnosticsReference</xsl:with-param>
-    </xsl:call-template>
-    <xsl:call-template name="reference">
-      <xsl:with-param name="class">print</xsl:with-param>
-      <xsl:with-param name="header">Pretty Print</xsl:with-param>
-      <xsl:with-param name="headerID">PrettyPrintReference</xsl:with-param>
-    </xsl:call-template>
-    <xsl:call-template name="reference">
-      <xsl:with-param name="class">encoding</xsl:with-param>
-      <xsl:with-param name="header">Character Encoding</xsl:with-param>
-      <xsl:with-param name="headerID">EncodingReference</xsl:with-param>
-    </xsl:call-template>
-    <xsl:call-template name="reference">
-      <xsl:with-param name="class">misc</xsl:with-param>
-      <xsl:with-param name="header">Miscellaneous</xsl:with-param>
-      <xsl:with-param name="headerID">MiscellaneousReference</xsl:with-param>
-    </xsl:call-template>
-  </table>
-</xsl:template>
-
-
-<xsl:template name="links">
-  <xsl:param name="class"/>
-  <xsl:param name="header"/>
-  <xsl:param name="headerID"/>
-  <tr valign="bottom">
-    <td class="h3" colspan="2" id="{$headerID}">
-      <xsl:value-of select="$header"/> Options</td>
-    <td valign="top"><a href="#top">Top</a></td>
-  </tr>
-  <xsl:call-template name="ClassHeaders" />
-  <xsl:for-each select="/config/option[@class=$class]">
-    <xsl:sort select="name" order="ascending" />
-    <tr>
-      <td><a href="#{name}"><xsl:value-of select="name"/></a></td>
-      <td><xsl:apply-templates select="type"/></td>
-      <td><xsl:choose>
-            <xsl:when test="string-length(default) &gt; 0 ">
-              <xsl:apply-templates select="default" />
-            </xsl:when>
-            <xsl:otherwise>
-              <strong>-</strong>
-            </xsl:otherwise>
-        </xsl:choose>
-      </td>
-    </tr>
-  </xsl:for-each>
-  <tr valign="bottom">
-    <td colspan="3">&#160;</td>
-  </tr>
-</xsl:template>
-
-
-<xsl:template name="reference">
-  <xsl:param name="class"/>
-  <xsl:param name="header"/>
-  <xsl:param name="headerID"/>
-
-  <tr>
-    <td>&#160;</td>
-  </tr>
-  <tr valign="bottom">
-    <td valign="top" colspan="2" class="h2" id="{$headerID}">
-       <xsl:value-of select="$header"/> Options Reference
-    </td>
-  </tr>
-  <tr>
-    <td>&#160;</td>
-  </tr>
-
-  <xsl:for-each select="/config/option[@class=$class]">
-    <xsl:sort select="name" order="ascending" />
-    <tr>
-      <td class="tabletitle" valign="top" id="{name}">
-        <xsl:value-of select="name"/>
-      </td>
-      <td class="tabletitlelink" valign="top" align="right">
-      <a href="#top">Top</a></td>
-    </tr>
-    <tr>
-      <td valign="top">Type: <strong><xsl:value-of
-        select="type"/></strong><br />
-
-        <xsl:choose>
-          <xsl:when test="string-length(default) &gt; 0">
-            Default: <strong><xsl:apply-templates select="default" /></strong>
-          </xsl:when>
-          <xsl:otherwise>
-            Default: <strong>-</strong>
-          </xsl:otherwise>
-        </xsl:choose>
-
-        <xsl:choose>
-          <xsl:when test="string-length(example) &gt; 0">
-            <br />Example: <strong><xsl:apply-templates
-                select="example"/></strong>
-          </xsl:when>
-          <xsl:otherwise>
-            <br />Example: <strong>-</strong>
-          </xsl:otherwise>
-        </xsl:choose>
-      </td>
-      <td align="right" valign="top">
-        <xsl:for-each select="seealso">
-          <a href="#{.}"><xsl:apply-templates select="." /></a>
-          <xsl:if test="position() != last()">
-            <br />
-          </xsl:if>
-        </xsl:for-each>
-      </td>
-    </tr>
-
-    <tr>
-      <td colspan="2"><xsl:apply-templates select="description"/></td>
-    </tr>
-
-    <tr>
-      <td>&#160;</td>
-    </tr>
-  </xsl:for-each>
-</xsl:template>
-
-<xsl:template name="ClassHeaders">
-      <tr>
-        <td class="tabletitle">Option</td>
-        <td class="tabletitle">Type</td>
-        <td class="tabletitle">Default</td>
-      </tr>
-</xsl:template>
-
-<xsl:template name="Stylesheet">
-	<style type="text/css">
-		/* 1st Style ignored by Netscape */
-		td.dummy, font.dummy, .dummy, a:link.dummy, a:visited.dummy, a:active.dummy
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 16pt;
-		color: #336699;
-		text-decoration: none;
-		font-weight: normal
-		}
-
-		body
-		{
-		margin-left: 10%;
-		margin-right: 10%;
-		font-family: sans-serif;
-		background-color: #FFFFFF
-		}
-
-		/* Blue TITLE */
-		td.title, font.title, .title, a:link.title, a:visited.title, a:active.title
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 16pt;
-		color: #336699;
-		text-decoration: none;
-		font-weight: normal
-		}
-
-		/* BODY TEXT */
-		td.text, font.text, .text, a:link.text, a:visited.text, a:active.text
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 9pt;
-		color: #000000;
-		text-decoration: none;
-		font-weight: normal
-		}
-
-		/* BOLD BODY TEXT */
-		td.textbold, font.textbold, .textbold, a:link.textbold, a:visited.textbold, a:active.textbold
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 9pt;
-		color: #000000;
-		text-decoration: none;
-		font-weight: bold
-		}
-
-		/* BOLD BODY TEXT LINK WITH UNDERLINE*/
-		td.textboldlink, font.textboldlink, .textboldlink, a:link.textboldlink, a:visited.textboldlink, a:active.textboldlink
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 9pt;
-		color: #000000;
-		font-weight: bold
-		}
-
-		/* SMALL BODY TEXT */
-		td.smtext, font.smtext, .smtext, a:link.smtext, a:visited.smtext, a:active.smtext
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 8pt;
-		color: #000000;
-		text-decoration: none;
-		font-weight: normal
-		}
-
-		/* SMALL BOLD BODY TEXT */
-		td.smtextbold, font.smtextbold, .smtextbold, a:link.smtextbold, a:visited.smtextbold, a:active.smtextbold
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 8pt;
-		color: #000000;
-		text-decoration: none;
-		font-weight: bold
-		}
-
-		/* TITLES
-		td.title, font.title, .title, a:link.title, a:visited.title, a:active.title
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 12pt;
-		color: #CC3300;
-		text-decoration: none;
-		font-weight: bold
-		}
-		*/
-
-		/* SUBTITLES */
-		td.subtitle, font.subtitle, .subtitle, a:link.subtitle, a:visited.subtitle, a:active.subtitle
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 11pt;
-		color: #000000;
-		text-decoration: none;
-		font-weight: bold
-		}
-
-		/* LEGAL TEXT */
-		td.legal, font.legal, .legal, a:link.legal, a:visited.legal, a:active.legal
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 8pt;
-		color: #000000;
-		text-decoration: none;
-		font-weight: normal
-		}
-
-		td.legallink, font.legallink, .legallink, a:link.legallink, a:visited.legallink, a:active.legallink
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 8pt;
-		color: #CC3300;
-		font-weight: normal
-		}
-
-		/* RED TEXT */
-		td.textred, font.textred, .textred, a:link.textred, a:visited.textred, a:active.textred
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 10pt;
-		color: #CC3300;
-		text-decoration: none;
-		font-weight: normal
-		}
-
-		/* RED TEXT BOLD*/
-		td.textredbold, font.textredbold, .textredbold, a:link.textredbold, a:visited.textredbold, a:active.textredbold
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 10pt;
-		color: #CC3300;
-		text-decoration: none;
-		font-weight: bold
-		}
-
-		/* LINKS */
-		td.link, font.link, .link, a:link.link, a:visited.link, a:active.link
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 10pt;
-		color: #3366CC;
-		font-weight: normal
-		}
-
-		td.tabletitlelink, font.tabletitlelink, .tabletitlelink, a:link.tabletitlelink, a:visited.tabletitlelink, a:active.tabletitlelink
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 10pt;
-		background-color: #e9e9d3;
-		color: #000000;
-		}
-
-		/* TABLE TITLES */
-		td.tabletitle, font.tabletitle, .tabletitle, a:link.tabletitle, a:visited.tabletitle, a:active.tabletitle
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 10pt;
-		color: #336699;
-		background-color: #e9e9d3;
-		/* text-decoration: none; */
-		font-weight: bold
-		}
-
-		/* TABLE CELL */
-		td.cell, tr.cell, font.cell, .cell, a:link.cell, a:visited.cell, a:active.cell
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 12pt;
-		color: #000000;
-		font-weight: normal;
-		/* background-color: #e9e9d3 */
-		background-color: #f5f5f5
-		}
-
-		/* SHADED TABLE CELL */
-		td.shaded, tr.shaded, font.shaded, .shaded, a:link.shaded, a:visited.shaded, a:active.shaded
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 12pt;
-		color: #000000;
-		font-weight: normal;
-		background-color: #f5f5f5
-		}
-
-		/* GLOSSARY TERM */
-		td.term, font.term, .term, a:link.term, a:visited.term, a:active.term
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 10pt;
-		font-style: normal;
-		color: #000000;
-		text-decoration: none;
-		font-weight: normal
-		}
-
-		/* ELEMENT TAGS */
-		ul
-		{
-		font-family: Arial, Helvetica, sans-serif;
-		font-size: 10pt;
-		font-style: normal;
-		font-weight: normal
-		}
-		li
-		{
-		font-family: Arial, Helvetica, sans-serif;
-		font-size: 10pt;
-		font-style: normal;
-		font-weight: normal
-		}
-
-		a:link.h1, a:visited.h1, .h1
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 12pt;
-		color: #0066CC
-		}
-		a:active.h1
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 12pt;
-		font-weight: bold;
-		color: #0066CC
-		}
-		h1
-		{
-		margin-left: -8%;
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 12pt;
-		color: #0066CC
-		}
-
-		.h2
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 11pt;
-		/* font-weight: bold; */
-		color: #000000
-		}
-
-		h2
-		{
-		margin-left: -4%;
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 11pt;
-		/* font-weight: bold; */
-		color: #000000
-		}
-
-		A:link.h3, A:visited.h3, .h3
-		{  font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 10pt;
-		color: #000000;
-		font-weight: bold
-		}
-
-		A:active.h3
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 10pt;
-		color: #000000;
-		font-weight: bold
-		}
-
-		h3
-		{
-		margin-left: -4%;
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 10pt;
-		font-weight: bold;
-		color: #000000
-		}
-
-		h4
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 9pt;
-		font-weight: bold;
-		color: #000000
-		}
-
-		.code, A:active.code, A:link.code, A:visited.code
-		{
-		font-family: "Courier New", Courier, monospace;
-		}
-
-		.abstract
-		{
-			font-style : italic;
-		}
-
-		p
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 10pt;
-		font-style: normal
-		}
-
-		td
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 10pt;
-		font-style: normal
-		}
-
-		/* LINKS */
-		a:link, a:active
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 10pt;
-		color: #3366CC;
-		font-weight: normal
-		}
-
-		a:visited
-		{
-		font-family: Arial, Helvetica, "Trebuchet MS", sans-serif;
-		font-size: 10pt;
-		color: #333366;
-		font-weight: normal
-		}
-
-		code {
-		  /* use browser/user default for `font-family` */
-		  font-weight: bold;
-		  color: brown;
-		  background: transparent;
-		}
-	</style>
-</xsl:template>
-
-
-<!-- Regular Templates: -->
-<xsl:template match="a | code | em | strong | br">
-    <xsl:element name="{local-name(.)}">
-        <xsl:copy-of select="@* | node()" />
-    </xsl:element>
-</xsl:template>
-
-</xsl:stylesheet>

documentation/style.css

@@ -1,304 +0,0 @@
-
-body {
-    background-color: #efefef;
-}
-
-#titlearea {
-    background-image: url(http://www.html-tidy.org/assets/images/green-abstract-background.jpg);
-    background-size: cover;
-}
-
-#projectname {
-    font-family: sans-serif;
-    font-size: 22pt; 
-    margin: 0 0 0 0;
-    margin-left: 150px;
-    padding: 2px 0px;
-    color: white;
-}
-
-#projectnumber {
-    font-size: 12pt; 
-}
-
-#projectbrief {
-    font-family: sans-serif;
-    font-size: 10pt; 
-    color: #dddddd;
-    margin-left: 150px;
-}
-
-
-.contents h1 {
-    font-size: 15pt;
-    font-family: monospace;
-    color: #4D4D74;
-    font-weight: bold;
-    border-left: none;
-    border-top: none;
-    border-bottom: 2px solid #cccccc;
-    margin: 30px 0px 10px 0px;
-    padding: 5px 0 5px 10px;
-}
-.contents h2 {
-    font-size: 12pt;
-    font-family: monospace;
-    color: #4D4D74;
-    font-weight: bold;
-    border-top: none;
-    border-bottom: 1px solid #dddddd;
-    margin: 20px 20% 20px 0px;
-    padding: 2px 0 2px 10px;
-}
-
-
-
-.contents p {
-    line-height: 130%;
-    font-size: 11pt;
-    font-family: sans-serif;
-    margin: 10px 20% 15px 10px;
-    padding: 0px;
-}
-
-.contents ul{
-    list-style-type: disc;
-    font-size: 11pt;
-    margin: 5px 20% 5px 40px;
-    padding: 0px;
-    line-height: 140%;
-}
-.contents ul ul{
-    list-style-type: circle;
-    margin-left: 30px;
-}
-.contents li{
-    padding: 2px 0 2px 0;
-    margin: 0;
-    ssbackground-color: pink;
-}
-
-.contents .textblock{
-    font-size: 10pt;
-    margin: 10px 50px 10px 50px;
-    line-height: 140%;
-}
-.contents .textblock code{
-    font-family: monospace;
-    font-size: 9pt;
-}
-.contents .todo{
-    font-size: 11pt;
-    margin: 10px 10% 20px 30px;
-}
-.contents .bug{
-    font-size: 11pt;
-    margin: 10px 10% 20px 30px;
-}
-
-dl
-{
-        padding: 0 0 0 10px;
-}
-
-/* dl.note, dl.warning, dl.attention, dl.pre, dl.post, dl.invariant, dl.deprecated, dl.todo, dl.test, dl.bug */
-dl.section
-{
-    margin-left: 0px;
-    padding-left: 0px;
-}
-
-dl.note
-{
-        margin: 5px 10% 5px 30px;
-        padding: 10px;
-        border-left: 4px solid;
-        border-color: #D0C000;
-        background-color: #FFFAC5;
-        border-radius: 10px;
-}
-
-ul dl.note{
-    margin-right: 0;
-}
-
-dl.warning, dl.attention
-{
-        margin: 5px 10% 5px 30px;
-        padding: 10px;
-        border-left: 4px solid;
-        border-color: #FF909F;
-        background-color: #FFE1E5;
-        border-radius: 10px;
-}
-
-dl.pre, dl.post, dl.invariant
-{
-        margin-left:-7px;
-        padding-left: 3px;
-        border-left:4px solid;
-        border-color: #00D000;
-}
-
-dl.deprecated
-{
-        margin: 5px 10% 5px 30px;
-        padding: 10px;
-        border-left:4px solid #B10BBF;
-        background-color: #FBC9FF;
-        border-radius: 10px;
-}
-
-dl.todo
-{
-        margin: 5px 10% 5px 30px;
-        padding: 10px;
-        border-left:4px solid #00C0E0;
-        background-color:  #DCFAFF ;
-        border-radius: 10px;
-}
-dl.bug
-{
-        margin: 5px 10% 5px 30px;
-        padding: 10px;
-        border-left:4px solid red;
-        background-color:  #FFC3B9 ;
-        border-radius: 10px;
-}
-dl.test
-{
-        margin-left:-7px;
-        padding-left: 3px;
-        border-left:4px solid;
-        border-color: #3030E0;
-}
-
-dl.bug
-{
-        margin-left:-7px;
-        padding-left: 3px;
-        border-left:4px solid;
-        border-color: #C08050;
-}
-
-
-
-dl.section dd {
-    margin-bottom: 6px;
-}
-
-
-
-table.directory tr {
-    border-bottom: 1px solid #cccccc !important;
-}
-
-table.directory  tr:hover {
-    background-color: #F6FF88 !important;
-}
-
-
-table.directory  td  {
-    padding: 5px;
-    font-family: sans-serif;
-}
-
-/*****************************************************/
-/* Quickref */
-table.quickref {
-    font-size: 9pt;
-    font-family: monospace;
-}
-table.quickref tr:hover{
-    background-color: #F6FF88;
-}
-table.quickref td.qrow {
-    border-bottom: 1px solid #cccccc !important;
-}
-table td.h2 {
-    padding: 0;
-    margin: 0;
-}
-.qh2 {
-    background-color: #333333;
-    color: #eeeeee !important;
-    padding: 10px;
-    border-radius: 5px;
-    border: none;
-    margin: 0;
-    padding: 8px;
-    font-size: 15pt;
-    width: 100%;
-    
-}
-table td.h3 {
-    background-color: #333333;
-    color: #eeeeee;
-    padding: 8px;
-    border-top-left-radius: 8px;
-}
-table td.h3top {
-    background-color: #333333;
-    padding: 8px;
-    border-top-right-radius: 8px;
-    text-align: right;
-    font-size: 8pt;
-}
-table td.h3top a{
-       color: #dddddd !important;
-}
-.h3topssssa {
-    color: #333333;
-}
-
-
-table td.tabletitle {
-    background-color: #cccccc;
-    font-size: 8pt;
-}
-
-td.tabletitlelink {
-    font-size: 8pt;
-}
-td.qoptiontitletd {
- padding: 0;
- margin: 0;
-}
-h4.qoptiontitle {
-    background-color: #bbbbbb;
-    font-size: 11pt;
-    font-weight: bold;
-    font-family: monospace;
-    padding: 5px 5px 5px 10px;
-    margin: 0;
-    border-top-left-radius: 5px;
-    border-top-right-radius: 5px;
-}
-
-
-.qlabel {
-    text-align: right;
-    font-size: 9pt;
-    width: 80px;
-    border-bottom: 1px solid #bbbbbb;
-
-    background-color: #dddddd;
-    font-family: sans-serif;
-}
-.qvalu {
-    font-size: 9pt;
-    font-weight: bold;
-    border-bottom: 1px solid #bbbbbb;
-    font-family: monospace;
-    border-left: 1px solid #bbbbbb;
-}
-
-.qdescription {
-    font-size: 11pt;
-    color: #333333;
-    margin: 0;
-    padding: 5px;
-    line-height: 140%;
-    border-left: 1px solid #bbbbbb;
-    border-bottom: 1px solid #bbbbbb;
-}

documentation/tidy1.xsl

@@ -1,448 +0,0 @@
-<?xml version="1.0"?>
-<!--
-    For generating the `tidy.1` man page from the
-    output of `tidy -xml-help` and `tidy -xml-config`
-
-    (c) 2005-2007 (W3C) MIT, ERCIM, Keio University
-    See tidy.h for the copyright notice.
-
-    Written by Jelks Cabaniss and Arnaud Desitter
-
--->
-<xsl:stylesheet version="1.0"
-                xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
-
-<xsl:strip-space elements="description" />
-
-<xsl:output method="text" />
-
-<!--
-    The default template match is to the document passed on the
-    command line to the XSLT processor, currently "tidy-help.xml".
-    For the detailed config options section however, the template
-    match is to the file "tidy-config.xml".  This is captured in
-    the $CONFIG variable, declared here:
--->
-
-<xsl:variable name="CONFIG" select="document('tidy-config.xml')"/>
-
-
-<!-- Main Template: -->
-
-<xsl:template match="/">
-   <xsl:call-template name="header-section" />
-   <xsl:call-template name="cmdline-section" />
-   <xsl:call-template name="config-section" />
-   <xsl:call-template name="manpage-see-also-section" />
-</xsl:template>
-
-
-<!-- Named Templates: -->
-
-
-<xsl:template name="header-section">
-  <xsl:text/>.\" tidy man page for the HTML Tidy
-.TH TIDY 1 "<xsl:value-of select="cmdline/@version" />" "HTML Tidy" "<xsl:value-of select="cmdline/@version" />"
-</xsl:template>
-
-
-<xsl:template name="cmdline-section">
-.\" disable hyphenation
-.nh
-.\" disable justification (adjust text to left margin only)
-.ad l
-.SH NAME
-\fBtidy\fR - check, correct, and pretty-print HTML(5) files
-.SH SYNOPSIS
-\fBtidy\fR [option ...] [file ...] [option ...] [file ...]
-.SH DESCRIPTION
-Tidy reads HTML, XHTML, and XML files and writes cleaned-up markup.  For HTML variants, it detects, reports, and corrects many common coding errors and strives to produce visually equivalent markup that is both conformant to the HTML specifications and that works in most browsers.
-.LP
-A common use of Tidy is to convert plain HTML to XHTML.  For generic XML files, Tidy is limited to correcting basic well-formedness errors and pretty printing.
-.LP
-If no input file is specified, Tidy reads the standard input.  If no output file is specified, Tidy writes the tidied markup to the standard output.  If no error file is specified, Tidy writes messages to the standard error.
-For command line options that expect a numerical argument, a default is assumed if no meaningful value can be found. 
-.SH OPTIONS
-<xsl:call-template name="show-cmdline-options" />
-.SH USAGE
-.LP
-Use \fB--\fR\fIoptionX valueX\fR for the detailed configuration option "optionX" with argument "valueX".  See also below under \fBDetailed Configuration Options\fR as to how to conveniently group all such options in a single config file.
-.LP
-Input/Output default to stdin/stdout respectively. Single letter options apart from \fB-f\fR and \fB-o\fR may be combined as in:
-.LP
-.in 1i
-\fBtidy -f errs.txt -imu foo.html\fR
-.SH ENVIRONMENT
-.TP
-.B HTML_TIDY
-Name of the default configuration file.  This should be an absolute path, since you will probably invoke \fBtidy\fR from different directories.  The value of HTML_TIDY will be parsed after the compiled-in default (defined with -DTIDY_CONFIG_FILE), but before any of the files specified using \fB-config\fR.
-.SH "EXIT STATUS"
-.IP 0
-All input files were processed successfully.
-.IP 1
-There were warnings.
-.IP 2
-There were errors.
-</xsl:template>
-
-
-<xsl:template name="config-section">
-.SH ______________________________
-.SH "  "
-.SH "DETAILED CONFIGURATION OPTIONS"
-This section describes the Detailed (i.e., "expanded") Options, which may be specified by preceding each option with \fB--\fR at the command line, followed by its desired value, OR by placing the options and values in a configuration file, and telling tidy to read that file with the \fB-config\fR standard option.
-.SH SYNOPSIS
-\fBtidy --\fR\fIoption1 \fRvalue1 \fB--\fIoption2 \fRvalue2 [standard options ...]
-.br
-\fBtidy -config \fIconfig-file \fR[standard options ...]
-.SH WARNING
-The options detailed here do not include the "standard" command-line options (i.e., those preceded by a single '\fB-\fR') described above in the first section of this man page.
-.SH DESCRIPTION
-A list of options for configuring the behavior of Tidy, which can be passed either on the command line, or specified in a configuration file.
-.LP
-A Tidy configuration file is simply a text file, where each option
-is listed on a separate line in the form
-.LP
-.in 1i
-\fBoption1\fR: \fIvalue1\fR
-.br
-\fBoption2\fR: \fIvalue2\fR
-.br
-etc.
-.LP
-The permissible values for a given option depend on the option's \fBType\fR.  There are five types: \fIBoolean\fR, \fIAutoBool\fR, \fIDocType\fR, \fIEnum\fR, and \fIString\fR. Boolean types allow any of \fIyes/no, y/n, true/false, t/f, 1/0\fR.  AutoBools allow \fIauto\fR in addition to the values allowed by Booleans.  Integer types take non-negative integers.  String types generally have no defaults, and you should provide them in non-quoted form (unless you wish the output to contain the literal quotes).
-.LP
-Enum, Encoding, and DocType "types" have a fixed repertoire of items; consult the \fIExample\fR[s] provided below for the option[s] in question.
-.LP
-You only need to provide options and values for those whose defaults you wish to override, although you may wish to include some already-defaulted options and values for the sake of documentation and explicitness.
-.LP
-Here is a sample config file, with at least one example of each of the five Types:
-.LP
-\fI
-    // sample Tidy configuration options
-    output-xhtml: yes
-    add-xml-decl: no
-    doctype: strict
-    char-encoding: ascii
-    indent: auto
-    wrap: 76
-    repeated-attributes: keep-last
-    error-file: errs.txt
-\fR
-.LP
-Below is a summary and brief description of each of the options. They are listed alphabetically within each category.  There are five categories: \fIHTML, XHTML, XML\fR options, \fIDiagnostics\fR options, \fIPretty Print\fR options, \fICharacter Encoding\fR options, and \fIMiscellaneous\fR options.
-.LP
-.SH OPTIONS
-<xsl:call-template name="show-config-options" />
-</xsl:template>
-
-
-<xsl:template name="show-cmdline-options">
-.SS File manipulation
-  <xsl:call-template name="cmdline-detail">
-     <xsl:with-param name="category">file-manip</xsl:with-param>
-  </xsl:call-template>
-.SS Processing directives
-  <xsl:call-template name="cmdline-detail">
-     <xsl:with-param name="category">process-directives</xsl:with-param>
-  </xsl:call-template>
-.SS Character encodings
-  <xsl:call-template name="cmdline-detail">
-     <xsl:with-param name="category">char-encoding</xsl:with-param>
-  </xsl:call-template>
-.SS Miscellaneous
-  <xsl:call-template name="cmdline-detail">
-     <xsl:with-param name="category">misc</xsl:with-param>
-  </xsl:call-template>
-</xsl:template>
-
-
-<xsl:template name="cmdline-detail">
-<!--
-For each option in one of the 3 categories/classes, provide its
-    1. names
-    2. description
-    3. equivalent configuration option
--->
-  <xsl:param name="category" />
-    <xsl:for-each select='/cmdline/option[@class=$category]'>
-<xsl:text>
-.TP
-</xsl:text>
-       <xsl:call-template name="process-names" />
-       <xsl:text>
-</xsl:text>
-       <xsl:apply-templates select="description" />
-       <xsl:text>
-</xsl:text>
-       <xsl:call-template name="process-eqconfig" />
-    </xsl:for-each>
-</xsl:template>
-
-
-<xsl:template name="process-names">
-<!-- Used only in the cmdline section -->
-  <xsl:for-each select="name">
-    <xsl:text />\fB<xsl:value-of select="." />\fR<xsl:text />
-    <xsl:if test="position() != last()">
-      <xsl:text>, </xsl:text>
-    </xsl:if>
-  </xsl:for-each>
-</xsl:template>
-
-
-<xsl:template name="process-eqconfig">
-<!-- Used only in the cmdline section -->
-  <xsl:if test="string-length(eqconfig) &gt; 0">
-   <xsl:for-each select="eqconfig">
-     <xsl:text>(\fI</xsl:text>
-     <xsl:value-of select="." />
-     <xsl:text>\fR)</xsl:text>
-   </xsl:for-each>
-  </xsl:if>
-</xsl:template>
-
-
-<xsl:template name="show-config-options">
-<!-- Used only in the cmdline section -->
-.SS HTML, XHTML, XML options:
-  <xsl:call-template name="config-detail">
-     <xsl:with-param name="category">markup</xsl:with-param>
-  </xsl:call-template>
-.SS Diagnostics options:
-  <xsl:call-template name="config-detail">
-     <xsl:with-param name="category">diagnostics</xsl:with-param>
-  </xsl:call-template>
-.SS Pretty Print options:
-  <xsl:call-template name="config-detail">
-     <xsl:with-param name="category">print</xsl:with-param>
-  </xsl:call-template>
-.SS Character Encoding options:
-  <xsl:call-template name="config-detail">
-     <xsl:with-param name="category">encoding</xsl:with-param>
-  </xsl:call-template>
-.SS Miscellaneous options:
-  <xsl:call-template name="config-detail">
-     <xsl:with-param name="category">misc</xsl:with-param>
-  </xsl:call-template>
-</xsl:template>
-
-
-<!--
-    Note that any templates called implicitly or explicitly
-    from the "config-detail" template below will match on
-    the document referred to by the $CONFIG variable, i.e.,
-    the file "tidy-config.xml", created by running
-
-        tidy -xml-config > tidy-config.xml
-
-    The $CONFIG variable is set at the top level of this
-    stylesheet.
--->
-
-<xsl:template name="config-detail">
-<!--
-For each option in one of the 5 categories/classes, provide its
-    1. name
-    2. type
-    3. default (if any)
-    4. example (if any)
-    5. seealso (if any)
-    6. description
--->
-  <xsl:param name="category" />
-    <xsl:for-each select='$CONFIG/config/option[@class=$category]'>
-       <xsl:sort select="name" order="ascending" />
-.TP
-\fB<xsl:apply-templates select="name" />\fR
-
-Type:    \fI<xsl:apply-templates select="type" />\fR
-.br
-<xsl:call-template name="provide-default" />
-.br
-<xsl:call-template name="provide-example" />
-<xsl:text>
-
-</xsl:text>
-<xsl:apply-templates select="description" />
-<xsl:call-template name="seealso" />
-    </xsl:for-each>
-</xsl:template>
-
-
-<!-- Used only in the config options section: -->
-<xsl:template name="seealso">
-  <xsl:if test="seealso">
-     <xsl:text>
-
-</xsl:text>
-.rj 1
-\fBSee also\fR: <xsl:text />
-    <xsl:for-each select="seealso">
-      <xsl:text />\fI<xsl:value-of select="." />\fR<xsl:text />
-      <xsl:if test="position() != last()">
-        <xsl:text>, </xsl:text>
-      </xsl:if>
-    </xsl:for-each>
-  </xsl:if>
-</xsl:template>
-
-
-<!-- Used only in the config options section: -->
-<xsl:template name="provide-default">
-<!--
-Picks up the default from the XML.  If the `default` element
-doesn't exist, or it's empty, a single '-' is provided.
--->
-  <xsl:choose>
-    <xsl:when test="string-length(default) &gt; 0 ">
-      <xsl:text />Default: \fI<xsl:apply-templates
-        select="default" />\fR<xsl:text />
-    </xsl:when>
-    <xsl:otherwise>
-      <xsl:text />Default: \fI-\fR<xsl:text />
-    </xsl:otherwise>
-  </xsl:choose>
-</xsl:template>
-
-
-<!-- Used only in the config options section: -->
-<xsl:template name="provide-example">
-<!--
-By default, doesn't output examples for String types (mirroring the
-quickref page).  But for *any* options in the XML instance that
-have an `example` child, that example will be used in lieu of a
-stylesheet-provided one. (Useful e.g. for `repeated-attributes`).
--->
-  <xsl:choose>
-    <xsl:when test="string-length(example) &gt; 0">
-      <xsl:text />Example: \fI<xsl:apply-templates
-          select="example" />\fR<xsl:text />
-    </xsl:when>
-    <xsl:otherwise>
-      <xsl:text />Default: \fI-\fR<xsl:text />
-    </xsl:otherwise>
-  </xsl:choose>
-</xsl:template>
-
-
-<!-- Called from the templates below matching `code`, `em`, `strong`: -->
-<xsl:template name="escape-backslash">
-<!--
-Since backslashes are "special" to the *roff processors used
-to generate man pages, we need to escape backslash characters
-appearing in content with another backslash.
--->
-  <xsl:choose>
-    <xsl:when test="contains(.,'\')">
-      <xsl:value-of select=
-        "concat( substring-before(.,'\'), '\\', substring-after(.,'\') )" />
-    </xsl:when>
-    <xsl:otherwise>
-      <xsl:apply-templates />
-    </xsl:otherwise>
-  </xsl:choose>
-</xsl:template>
-
-
-<!-- Appears at the bottom of the man page: -->
-<xsl:template name="manpage-see-also-section">
-.SH SEE ALSO
-For more information about HTML Tidy:
-.RS 4
-.LP
-http://www.html-tidy.org/
-.RE
-.LP
-For more information on HTML:
-.RS 4
-.LP
-\fBHTML: Edition for Web Authors\fR (the latest HTML specification)
-.br
-http://dev.w3.org/html5/spec-author-view
-.LP
-\fBHTML: The Markup Language\fR (an HTML language reference)
-.br
-http://dev.w3.org/html5/markup/
-.RE
-.LP
-For bug reports and comments:
-.RS 4
-.LP
-https://github.com/htacg/tidy-html5/issues/
-.RE
-.LP
-Or send questions and comments to \fBpublic-htacg@w3.org\fR.
-.LP
-Validate your HTML documents using the \fBW3C Nu Markup Validator\fR:
-.RS 4
-.LP
-http://validator.w3.org/nu/
-.RE
-.SH AUTHOR
-\fBTidy\fR was written by \fBDave Raggett\fR &lt;dsr@w3.org&gt;, and subsequently maintained by a team at http://tidy.sourceforge.net/,
-and now maintained by \fBHTACG\fR (http://www.htacg.org).
-.LP
-The sources for \fBHTML Tidy\fR are available at https://github.com/htacg/tidy-html5/ under the MIT Licence.
-</xsl:template>
-
-
-<!-- Regular Templates: -->
-
-
-<xsl:template match="description">
-   <xsl:apply-templates />
-</xsl:template>
-
-<xsl:template match="a">
-   <xsl:apply-templates />
-   <xsl:text /> at \fI<xsl:value-of select="@href" />\fR<xsl:text />
-</xsl:template>
-
-<xsl:template match="code | em">
-   <xsl:text />\fI<xsl:call-template name="escape-backslash" />\fR<xsl:text />
-</xsl:template>
-
-<xsl:template match="br">
-   <xsl:text>
-.br
-</xsl:text>
-</xsl:template>
-
-<xsl:template match="strong">
-   <xsl:text />\fB<xsl:call-template name="escape-backslash" />\fR<xsl:text />
-</xsl:template>
-
-
-<!--
-The following templates
-  a) normalize whitespace, primarily necessary for `description`
-  b) do so without stripping possible whitespace surrounding `code`
-  d) strip leading and trailing whitespace in 'description` and `code`
-(courtesy of Ken Holman on the XSL-list):
--->
-
-<xsl:template match="text()[preceding-sibling::node() and
-                             following-sibling::node()]">
-   <xsl:variable name="ns" select="normalize-space(concat('x',.,'x'))"/>
-   <xsl:value-of select="substring( $ns, 2, string-length($ns) - 2 )" />
-</xsl:template>
-
-<xsl:template match="text()[preceding-sibling::node() and
-                             not( following-sibling::node() )]">
-   <xsl:variable name="ns" select="normalize-space(concat('x',.))"/>
-   <xsl:value-of select="substring( $ns, 2, string-length($ns) - 1 )" />
-</xsl:template>
-
-<xsl:template match="text()[not( preceding-sibling::node() ) and
-                             following-sibling::node()]">
-   <xsl:variable name="ns" select="normalize-space(concat(.,'x'))"/>
-   <xsl:value-of select="substring( $ns, 1, string-length($ns) - 1 )" />
-</xsl:template>
-
-<xsl:template match="text()[not( preceding-sibling::node() ) and
-                             not( following-sibling::node() )]">
-   <xsl:value-of select="normalize-space(.)"/>
-</xsl:template>
-
-</xsl:stylesheet>

experimental/TidyNodeIter.c

@@ -18,21 +18,21 @@ Node *nextTidyNode( TidyNodeIter *pThis )
 {
     if (NULL == pThis->pCurrent)
     {
-        // just starting out, initialize
+        /* just starting out, initialize */
         pThis->pCurrent = pThis->pTop->content;
     }
     else if (NULL != pThis->pCurrent->content)
     {
-        // the next element, if any, is my first-born child
+        /* the next element, if any, is my first-born child */
         pThis->pCurrent = pThis->pCurrent->content;
     }
     else 
     {
-        // no children, I guess my next younger brother inherits the throne.
+        /* no children, I guess my next younger brother inherits the throne. */
         while (   NULL == pThis->pCurrent->next
                && pThis->pTop != pThis->pCurrent->parent )
         {
-            //  no siblings, do any of my ancestors have younger sibs?
+            /* no siblings, do any of my ancestors have younger sibs? */
             pThis->pCurrent = pThis->pCurrent->parent;
         }
         pThis->pCurrent = pThis->pCurrent->next;

experimental/httpio.c

@@ -76,7 +76,7 @@ int parseURL( HTTPInputSource *pHttp, tmbstr url )
             if (!pHttp->nPort)
                 return -1;
         }
-        else                      /* or just a misformed port number */
+        else                      /* or just a malformed port number */
             return -1;
     }
     else

experimental/httpio.h

@@ -19,7 +19,7 @@
 TIDY_STRUCT
 typedef struct _HTTPInputSource
 {
-    TidyInputSource tis;    //  This declaration must be first and must not be changed!
+    TidyInputSource tis; /* This declaration must be first and must not be changed! */
 
     tmbstr pHostName;
     tmbstr pResource;

include/buffio.h

@@ -0,0 +1,17 @@
+/** @file buffio.h - Deprecated compatibility header. Use tidybuffio.h
+**
+** @deprecated This compatibility header is deprecated and 
+** should be replaced by tidybuffio.h. This header will be removed!
+**
+*/
+
+#ifdef __GNUC__
+#warning "FIXME: Using compatibility tidy header (buffio.h) that will go away! Use tidybuffio.h"
+#endif
+#ifdef _MSC_VER
+#pragma message("WARNING: ** FIXME ** Using compatibility tidy header (buffio.h) that will go away! Use tidybuffio.h")
+#endif
+
+#include "tidybuffio.h"
+
+

include/module.modulemap

@@ -0,0 +1,7 @@
+module CLibTidy {
+    header "tidy.h"
+    header "tidybuffio.h"
+    header "tidyenum.h"
+    header "tidyplatform.h"
+    export *
+}

include/platform.h

@@ -0,0 +1,15 @@
+/** @file platform.h - Deprecated compatibility header. Use tidyplatform.h
+**
+** @deprecated This compatibility header is deprecated and 
+** should be replaced by tidyplatform.h. This header will be removed!
+**
+*/
+#ifdef __GNUC__
+#warning "FIXME: Using compatibility tidy header (platform.h) that will go away!"
+#endif
+#ifdef _MSC_VER
+#pragma message("WARNING: ** FIXME ** Using compatibility tidy header (platform.h) that will go away! Use tidyplatform.h")
+#endif
+
+#include "tidyplatform.h"
+