•Config file - (Pro, Std, Lite) Each time you run HTML Validator, it attempts to automatically load a configuration file. The configuration file contains information about the tags, tag attributes, and attribute values that can be used as well as rules about how they can be used. It also contains compatibility, deprecation, style, and other helpful information. The default configuration file should be specified here with a full pathname such as "C:\Program Files\HTMLValidator140\htmlvalV140.cfg". The file should end in a ".cfg" extension and is created by pressing the Save Config or Save Config As button in the Configuration Editor.
•User functions - (Pro, Std, Lite) Specify an optional ".cfg" file (which is a plain text file with UTF-8 encoding) with user-defined functions to supplement the configuration file. This allows a high degree of user customizations that are not lost due to program updates that update the configuration file. See the Special Functions topic page for more information about the functions that can be specified in this file. By default, no file is specified and this option is blank. (New v10.9912)
•User functions 2 - (Pro, Std, Lite) Like the above User functions option, but allows for a 2nd user function file to easily be used at the same time. (New v10.9931)
•Automatically save any configuration file changes without prompting - (Pro, Std, Lite) Check this box if you always want to save any changes to the configuration without prompting if you want to do so. Otherwise you are asked to save the configuration if it has changed and you attempt to exit the program or load a new configuration. This option is not enabled by default.
•Enable potentially destructive functions like writeFile() - (Pro, Std, Lite) Check this box to enable potentially destructive functions (like writeFile() and deleteFile()) that allow for more capability but that may also be used mistakenly or maliciously to do damage, like delete files.This option is not enabled by default. (New v11.9942)
•It allows an even higher level of user customizations based on the special functions that are allowed & defined in the file.
•The file is simply a normal text file with UTF-8 encoding, and can be easily shared with others and edited in most text editors.
•To reload a 'user functions' file after changes, reload the configuration. The 'user functions' file is only processed when a configuration is loaded.
•The customizations are not lost and do not have to be redone when doing program updates that update & replace the normal config file.
•'User functions' files are supported in v11.00 and above, in the professional and enterprise editions.
NOTE: The configuration must be reloaded in order for any changes in the user function file(s) to take affect.
NOTE: The 'user functions' file is a text file that is loaded using UTF-8 encoding.