Awesome

Font-Validator

Font Validator is a tool for testing fonts prior to release. It was initially developed by Microsoft, to ensure that fonts meet Microsoft's high quality standards and perform exceptionally well on Microsoft's platform.

In 2015 the source code was published under the MIT license (see release discussion)

Usage

FontVal.exe is the GUI, and FontValidator.exe shows usage and example if run without arguments; both should be self-explanatory. We provide all-in-one native command-line binaries, FontValidator, for Mac OS X and Linux, as of Release 2.1.1. Georg Seifert contributed a friendly GUI wrapper for Mac around the command-line tool.

The GUI's built-in help requires a CHM viewer, which defaults to chmsee on GNU+Linux, or via env variable MONO_HELP_VIEWER

The GUI on X11/mono needs the env variable MONO_WINFORMS_XIM_STYLE=disabled set to work around Bug 28047 - Forms on separare threads -- Fatal errors/crashes

Binary Downloads

Since Release 2.0, binaries (*.dmg for Mac OS X, *-bin-net2.zip or *-bin-net4.zip for MS .NET/mono) are available from Binary Downloads. From Release 2.1 onwards, gpg-signed binaries for Ubuntu Linux are also available. There is an additional and simplified location for Binary downloads at the Releases link above this page.

Please consider donating to the effort, if you use the binaries.

Building from source

Loading FValidator.sln at the top level into Microsoft Visual Studio 2008+ (Express) by double-clicking it, followed by selecting the the relevant menu entries in the GUI, or running MSbuild on the command line with MS VS2008+, should do. For Mono-based instructions, see Build Instructions

A few dependent parts, either difficult to build or external, or have different build requirements, such as the FreeType backends, SharpFont, the CHM doc, are pre-built and deposited in the bin directory.

Status

The FontVal 2.2 Roadmap.

As of Release 2.0 (July 18 2016), all the withheld parts not released by Microsoft were re-implemented. Release 2.0 run well on non-windows, and is substantially faster also. Existing users of the increasingly dated 1.0 release from 2003 are encouraged to upgrade. There are a number of known disagreements and issues which are gradually being filed and addressed. README-hybrid.txt is now of historical interests only.

Release 2.1 is considered to fully supercede the proprietary 1.0 feature-wise and functionality-wise.

The DSIG test (DSIG_VerifySignature) does not validate trusted certificate chain yet.
Many post-2nd (i.e. 2009) edition changes, such as CBLC/CBDT and other new tables.
Very few post-3rd (i.e. 2015) edition changes are implemented.

See also README-extra.txt for a list of other interesting or non-essential tasks.