tidy-html5/build/documentation
2015-03-08 13:48:02 +08:00
..
examples Split up pages into seperate files for easier nav, added description to home and a configuration page 2015-03-05 23:28:52 +00:00
pages fix missing links 2015-03-08 04:37:35 +00:00
.gitignore Use new quickref.include.xsl to format html for \htmlinclude 2015-03-06 04:08:08 +00:00
build_docs.sh Bash doesn't like the extra space after the slash. 2015-03-08 13:48:02 +08:00
doxygen.cfg Fix up docs merge 2015-03-08 04:34:17 +00:00
DoxygenLayout.xml Add tableofcontents and generally nitpick things 2015-03-06 07:02:47 +00:00
quickref.include.xsl tidy quickref and other nitpicking docs 2015-03-06 06:38:57 +00:00
quickref.xsl Moved htmldoc to build/documentation 2015-02-14 12:12:15 +08:00
README.md tidy quickref and other nitpicking docs 2015-03-06 06:38:57 +00:00
style.css add history diagram and style to directory tables 2015-03-06 07:38:16 +00:00
tidy1.xsl Moved htmldoc to build/documentation 2015-02-14 12:12:15 +08:00

Documentation 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 installed. You can clone the repository from github 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 Tidys 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 Tidys 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 Tidys 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.