OurData.xml

<helpitems xmlns="urn:helpgen">
<item
    helpID="A0500"
    atom="DSIG_A_UNUSUAL_TTC_TABLE_LAYOUT"
    linkTitle="DSIG table specification"
    specLink="http://www.microsoft.com/typography/otspec/dsig.htm"
    shortDesc="Cannot cope with unusual ttc table layout"
    fwLinkID="10341"
    tableName="DSIG">
    <problem>Cannot cope with unusual ttc table layout</problem>
</item>

<item
    helpID="A1113"
    atom="GERR_VAL_FAILURE"
    linkTitle="glyf table specification"
    specLink="http://www.microsoft.com/typography/otspec/glyf.htm"
    shortDesc="Test failed because of unhandled exception"
    fwLinkID="10348"
    tableName="glyf">
    <problem>Unused in either 1.0.1286.23890 or 1.1.3359.19055</problem>
</item>

<item
    helpID="A2100"
    atom="OS_2_A_CodePageNotInstalled"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#cpr"
    shortDesc="A range in the ulCodePageRange field cannot be validated because a code page is not installed"
    fwLinkID="10381"
    tableName="OS/2">
    <problem>This message does not indicate there is an error in the font. To validate the codepage compliance of a font, all codepages covered by the font must be installed on the testing system.&lt;BR&gt;&lt;BR&gt;To install additional codepages in Windows, do the following:&lt;OL&gt;&lt;LI&gt;Go to Control Panel.&lt;/LI&gt;&lt;LI&gt;Choose Regional and Language Options.&lt;/LI&gt;&lt;LI&gt;Click the Advanced tab.&lt;/LI&gt;&lt;LI&gt;In the Codepage Conversion Tables list, select the codepages you wish to install. You will need to have your Windows installation disk available.&lt;/LI&gt;&lt;/OL&gt;

    &lt;p&gt;This message is not used and should not be seen from 2015 onwards with FontVal 2.0 .
  </problem>
</item>

<item
    helpID="A6000"
    atom="_rast_A_ExceptionUnhandled"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="An exception occurred during rasterization testing"
    fwLinkID="10368"
    tableName="Application">
    <problem>The rasterization testing cannot be continued due to an error in the font. Before completing rasterization testing, you will need to identify and fix this error, using details provided.&lt;BR&gt;&lt;BR&gt;If exception errors continue after you have changed the font data, please contact the Microsoft Typography group.

&lt;p&gt;
This message can happen on MS Windows with FontVal 2.0 when testing fonts within non-English file names,
with the detail &quot; Cannot marshal: Encountered unmappable character. &quot;
This is a known limitation of SharpFont on Windows ( https://github.com/Robmaister/SharpFont/issues/89 ).
Try renaming or copy the file with an English name and re-test.

&lt;p&gt;
Bitmap-only fonts, such as Apple Color Emoji.ttf, which are designed for only some specific pixel sizes,
may result in
&quot; FreeType error: Invalid pixel size. &quot;
when testing for sizes which they are not designed for.
Under this circumstance, this message is harmless and can be ignored.
The older FontVal 1.0 and 1.1 shows &quot; Secure Rasterizer error: Function out of range &quot; as well as E6016 &quot;FDEF out of range&quot;
for Apple Color Emoji.ttf.
That may or may not be related.

&lt;p&gt;
In the old FontVal 1.0, error A6000,
&quot;Secure Rasterizer error: Function out of range&quot; can accompany E6016 &quot;FDEF out of range&quot;,
A6000 &quot;Secure Rasterizer error: TrueType stack overflow&quot; can accompany E6045 &quot;Stack Overflow&quot;,
A6000 &quot;Secure Rasterizer error: Storage index out of range&quot; can accompany E6047 &quot;Storage index out of range&quot;,
depending on where the E6016, E6045 and E6047 errors happen. Font designers should address these other errors first.

&lt;p&gt;
Running FontVal 1.0 (and perhaps 2.0 too) under wine can occasionally result in error A6000, &quot;Attempted to read or write protected memory. This is often an indication that other memory is corrupt.&quot; . This is intermittent and a problem with wine. Users should simply re-run.
</problem>
</item>

<item
    helpID="E0001"
    atom="_GEN_E_EOFError"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Unexpected End of File"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="E0003"
    atom="_GEN_E_InvalidFontFile"
    linkTitle="details about OpenType files"
    specLink="WARNING: field missing"
    shortDesc="The file was not recognized as a valid OpenType font file"
    fwLinkID="10363"
    tableName="offset">
    <problem>The Validator did not find a valid 4-byte sfnt version label in the offset table. The allowable values are '0100' (font contains TrueType outlines), 'OTTO' (font contains CFF data), or 'ttcf' (TrueType Collection file).</problem>
</item>

<item
    helpID="E0004"
    atom="_GEN_E_OffsetExceedsTableLength"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Read error: offset exceeds length of the table"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="E0005"
    atom="_GEN_E_ReadError"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Error reading file"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="E0006"
    atom="_GEN_E_UserCanceled"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Font Validation was canceled by the user"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="E0010"
    atom="_OFFSET_E_entrySelector"
    linkTitle="details about OpenType files"
    specLink="http://www.microsoft.com/typography/otspec/otff.htm"
    shortDesc="The entrySelector field is invalid"
    fwLinkID="10363"
    tableName="offset">
    <problem>The value of the entrySelector field must equal Log2(maximum power of 2&amp;LT;=numTables). Regenerate this font.</problem>
</item>

<item
    helpID="E0011"
    atom="_OFFSET_E_InvalidSFNT"
    linkTitle="details about OpenType files"
    specLink="http://www.microsoft.com/typography/otspec/otff.htm"
    shortDesc="The sfnt field is invalid"
    fwLinkID="10363"
    tableName="offset">
    <problem>The sfnt field may have a value of either 1.0 (indicating that TrueType outlines are in the font) or 'OTTO' (indicating CFF data is in the font). The Apple specification for TrueType fonts allows for 'true' and 'typ1' for sfnt version. These version tags should not be used for fonts which contain OpenType tables.</problem>
</item>

<item
    helpID="E0012"
    atom="_OFFSET_E_numTables"
    linkTitle="details about OpenType files"
    specLink="http://www.microsoft.com/typography/otspec/otff.htm"
    shortDesc="The numTables field is zero"
    fwLinkID="10363"
    tableName="offset">
    <problem>The numTables field must equal the number of tables in the font. At a minimum there are eight required tables in a TrueType font. Regenerate this font.</problem>
</item>

<item
    helpID="E0013"
    atom="_OFFSET_E_rangeShift"
    linkTitle="details about OpenType files"
    specLink="http://www.microsoft.com/typography/otspec/otff.htm"
    shortDesc="The rangeShift field is invalid"
    fwLinkID="10363"
    tableName="offset">
    <problem>The value of the rangeShift field must equal (numTables) x 16 - (searchRange). Regenerate this font.</problem>
</item>

<item
    helpID="E0014"
    atom="_OFFSET_E_searchRange"
    linkTitle="details about OpenType files"
    specLink="http://www.microsoft.com/typography/otspec/otff.htm"
    shortDesc="The searchRange field is invalid"
    fwLinkID="10363"
    tableName="offset">
    <problem>The value of the searchRange field must equal (maximum power of 2&amp;LT;=numTables)x16. Regenerate this font.</problem>
</item>

<item
    helpID="E0020"
    atom="_FONT_E_MissingRequiredTable"
    linkTitle="details about OpenType files"
    specLink="http://www.microsoft.com/typography/otspec/otff.htm"
    shortDesc="Required table is missing"
    fwLinkID="10363"
    tableName="General">
    <problem>A minimum of eight tables are required in a valid TrueType font: cmap, head, hhea, hmtx, maxp, name, OS/2, and post.&lt;BR&gt;&lt;BR&gt;If TrueType data is present in the font, then the following tables are also required: cvt, fpgm, glyf, loca, and prep. If CFF data is in the font, then both the CFF and VORG tables need to be present.&lt;BR&gt;&lt;BR&gt;Microsoft also requires that the DSIG table be present in fonts delivered by vendors to Microsoft.&lt;BR&gt;&lt;BR&gt;Microsoft further recommends that the gasp table be present in all fonts.To learn more about these recommendations, see the &lt;A TARGET=&quot;top&quot; HREF=&quot;http://go.microsoft.com/fwlink?LinkID=10456&quot;&gt;Hinting and Production Guidelines Specification&lt;/A&gt;.</problem>
</item>
<!--
    A commented out stale entry "W7003 / _FONT_W_MissingRequiredTable"
    was removed in c2f1f1e7fda7d79e3e16dba682545e0c727c140d
-->

<item
    helpID="E0030"
    atom="_DE_E_ChecksumError"
    linkTitle="details about OpenType files"
    specLink="http://www.microsoft.com/typography/otspec/otff.htm"
    shortDesc="Directory Entry checksum error"
    fwLinkID="10363"
    tableName="Table Directory">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E0031"
    atom="_DE_E_DuplicateTag"
    linkTitle="details about OpenType files"
    specLink="http://www.microsoft.com/typography/otspec/otff.htm"
    shortDesc="Directory Entry contains a duplicate tag"
    fwLinkID="10363"
    tableName="Table Directory">
    <problem>Each tag in the Table Directory refers to a single table, feature, or language within the font. All tag names used must be unique within the font.</problem>
</item>

<item
    helpID="E0032"
    atom="_DE_E_LengthZero"
    linkTitle="details about OpenType files"
    specLink="http://www.microsoft.com/typography/otspec/otff.htm"
    shortDesc="Directory Entry length is 0"
    fwLinkID="10363"
    tableName="Table Directory">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E0033"
    atom="_DE_E_OffsetPastEOF"
    linkTitle="details about OpenType files"
    specLink="http://www.microsoft.com/typography/otspec/otff.htm"
    shortDesc="Directory Entry offset points past EOF"
    fwLinkID="10363"
    tableName="Table Directory">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E0034"
    atom="_DE_E_OffsetZero"
    linkTitle="details about OpenType files"
    specLink="http://www.microsoft.com/typography/otspec/otff.htm"
    shortDesc="Directory Entry offset is 0"
    fwLinkID="10363"
    tableName="Table Directory">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E0035"
    atom="_DE_E_OverlappingTable"
    linkTitle="details about OpenType files"
    specLink="http://www.microsoft.com/typography/otspec/otff.htm"
    shortDesc="Directory Entry overlaps another table"
    fwLinkID="10363"
    tableName="Table Directory">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E0036"
    atom="_DE_E_TableEndPastEOF"
    linkTitle="details about OpenType files"
    specLink="http://www.microsoft.com/typography/otspec/otff.htm"
    shortDesc="Directory Entry offset plus length past EOF"
    fwLinkID="10363"
    tableName="Table Directory">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E0037"
    atom="_DE_E_TagName"
    linkTitle="details about OpenType files"
    specLink="http://www.microsoft.com/typography/otspec/otff.htm"
    shortDesc="The directory entry tag name is invalid"
    fwLinkID="10363"
    tableName="Table Directory">
    <problem>All tag names consist of four characters. Names with less than four characters are allowed if followed by the necessary trailing spaces. All tag names defined within a font (including table names, feature tags, and language tags) must be composed of printing characters represented by ASCII values 32-126.</problem>
</item>

<item
    helpID="E0038"
    atom="_DE_E_TagsAscending"
    linkTitle="details about OpenType files"
    specLink="http://www.microsoft.com/typography/otspec/otff.htm"
    shortDesc="The directory entry tags are not in ascending order"
    fwLinkID="10363"
    tableName="Table Directory">
    <problem>Entries in the table directory must be sorted in ascending order by tag name. Rebuild this font.</problem>
</item>

<item
    helpID="E0039"
    atom="_DE_E_TagZero"
    linkTitle="details about OpenType files"
    specLink="http://www.microsoft.com/typography/otspec/otff.htm"
    shortDesc="Directory Entry tag is 0"
    fwLinkID="10363"
    tableName="Table Directory">
    <problem>All tag names consist of four characters. Names with less than four characters are allowed if followed by the necessary trailing spaces. All tag names defined within a font (including table names, feature tags, and language tags) must be composed of printing characters represented by ASCII values 32-126.</problem>
</item>

<item
    helpID="E0040"
    atom="_Table_E_DataOverlap"
    linkTitle="details about OpenType files"
    specLink="http://www.microsoft.com/typography/otspec/otff.htm"
    shortDesc="The data overlaps existing data"
    fwLinkID="10363"
    tableName="Table">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E0041"
    atom="_Table_E_Exception"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="An exception occurred preventing completion of table validation"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="E0042"
    atom="_Table_E_Invalid"
    linkTitle="details about OpenType files"
    specLink="http://www.microsoft.com/typography/otspec/otff.htm"
    shortDesc="The table is invalid"
    fwLinkID="10363"
    tableName="Table">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E0051"
    atom="_TEST_E_TableMissing"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Cannot perform test, a needed table is missing!"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="E0300"
    atom="cmap_E_DuplicateSubtables"
    linkTitle="cmap table specification"
    specLink="http://www.microsoft.com/typography/otspec/cmap.htm"
    shortDesc="A duplicate subtable was found"
    fwLinkID="10339"
    tableName="cmap">
    <problem>Although cmap tables may include multiple subtables, duplicate subtables are unnecessary. Identify and remove the duplicate subtable, using a cmap editing tool.</problem>
</item>

<item
    helpID="E0301"
    atom="cmap_E_f0_length"
    linkTitle="cmap table specification"
    specLink="http://www.microsoft.com/typography/otspec/cmap.htm"
    shortDesc="The subtable is fmt 0, but the length is not 262"
    fwLinkID="10339"
    tableName="cmap">
    <problem>A format 0 cmap subtable indicates the Apple standard character to glyph index mapping table, which maps only 256 characters. The total table length, including the glyphIDArray, should always be 262 bytes. This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E0302"
    atom="cmap_E_f12_SortOrder"
    linkTitle="cmap table specification"
    specLink="http://www.microsoft.com/typography/otspec/cmap.htm"
    shortDesc="The groups are not sorted by ascending startCharCode"
    fwLinkID="10339"
    tableName="cmap">
    <problem>The ranges of character codes in a format 12 cmap subtable must be ordered by startCount (the starting character code of each range).</problem>
</item>

<item
    helpID="E0303"
    atom="cmap_E_f12_StartCode_GT_EndCode"
    linkTitle="cmap table specification"
    specLink="http://www.microsoft.com/typography/otspec/cmap.htm"
    shortDesc="The startCharCode is greater than the endCharCode"
    fwLinkID="10339"
    tableName="cmap">
    <problem>Each endCharCode must be greater in value than the startCharCode for that specific group of characters. A group's endCharCode must be less than the startCharCode of the following group (if any).</problem>
</item>

<item
    helpID="E0304"
    atom="cmap_E_f4_EndCodeOrder"
    linkTitle="cmap table specification"
    specLink="http://www.microsoft.com/typography/otspec/cmap.htm"
    shortDesc="The endCode array is not in ascending order"
    fwLinkID="10339"
    tableName="cmap">
    <problem>Due to the way arrays of character codes are searched, the endCode array in a format 4 cmap subtable must be in ascending order. Regenerate this font.</problem>
</item>

<item
    helpID="E0305"
    atom="cmap_E_f4_entrySelector"
    linkTitle="cmap table specification"
    specLink="http://www.microsoft.com/typography/otspec/cmap.htm"
    shortDesc="The entrySelector field does not equal the calculated value"
    fwLinkID="10339"
    tableName="cmap">
    <problem>The entrySelector value in format 4 cmap subtables must equal log2(searchRange/2). Regenerate this font.</problem>
</item>

<item
    helpID="E0306"
    atom="cmap_E_f4_FinalEndCode"
    linkTitle="cmap table specification"
    specLink="http://www.microsoft.com/typography/otspec/cmap.htm"
    shortDesc="The final value in the endCode array is not 0xffff"
    fwLinkID="10339"
    tableName="cmap">
    <problem>For a character code search to terminate properly, the final endCode value in each array must be 0xFFFF. At a minimum, a segment must include the single character code OxFFFF, which may be mapped to missingGlyph. Regenerate this font.</problem>
</item>

<item
    helpID="E0307"
    atom="cmap_E_f4_idDeltaNeg"
    linkTitle="cmap table specification"
    specLink="http://www.microsoft.com/typography/otspec/cmap.htm"
    shortDesc="The idRangeOffset is 0 and idDelta + startCode is negative"
    fwLinkID="10339"
    tableName="cmap">
    <problem>The idDelta value added to the character code offset should correspond to the mapped glyph index, when the idRangeOffset is 0. Regenerate this font.</problem>
</item>

<item
    helpID="E0308"
    atom="cmap_E_f4_idRangeOffset"
    linkTitle="cmap table specification"
    specLink="http://www.microsoft.com/typography/otspec/cmap.htm"
    shortDesc="The idRangeOffset indexes past the end of the subtable"
    fwLinkID="10339"
    tableName="cmap">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E0309"
    atom="cmap_E_f4_rangeShift"
    linkTitle="cmap table specification"
    specLink="http://www.microsoft.com/typography/otspec/cmap.htm"
    shortDesc="The rangeShift field does not equal the calculated value"
    fwLinkID="10339"
    tableName="cmap">
    <problem>The rangeShift field must equal (2 * segCount - searchRange). Regenerate this font.</problem>
</item>

<item
    helpID="E0310"
    atom="cmap_E_f4_reservedPad"
    linkTitle="cmap table specification"
    specLink="http://www.microsoft.com/typography/otspec/cmap.htm"
    shortDesc="The reservedPad field is not 0"
    fwLinkID="10339"
    tableName="cmap">
    <problem>The reservedPad field should have a value of 0. Regenerate this font.</problem>
</item>

<item
    helpID="E0311"
    atom="cmap_E_f4_searchRange"
    linkTitle="cmap table specification"
    specLink="http://www.microsoft.com/typography/otspec/cmap.htm"
    shortDesc="The searchRange field does not equal the calculated value"
    fwLinkID="10339"
    tableName="cmap">
    <problem>The searchRange value in format 4 cmap subtables must equal (2 * largest power of 2 &amp;LT;=segCount). Regenerate this font.</problem>
</item>

<item
    helpID="E0312"
    atom="cmap_E_f4_segCountX2"
    linkTitle="cmap table specification"
    specLink="http://www.microsoft.com/typography/otspec/cmap.htm"
    shortDesc="The segCountX2 field is not even"
    fwLinkID="10339"
    tableName="cmap">
    <problem>The segCountX2 value must equal (2 * number of segments of contiguous ranges of character codes). Regenerate this font.</problem>
</item>

<item
    helpID="E0313"
    atom="cmap_E_f4_StartCode_GT_EndCode"
    linkTitle="cmap table specification"
    specLink="http://www.microsoft.com/typography/otspec/cmap.htm"
    shortDesc="The startCode is greater than the endCode"
    fwLinkID="10339"
    tableName="cmap">
    <problem>Each segment of contiguous character codes in format 4 cmap subtables are described by a startCode and endCode. The startCode should indicate the starting character code for each segment; the endCode should indicate the ending character code for each segment. The segments should be sorted in order of increasing endCode values.</problem>
</item>

<item
    helpID="E0314"
    atom="cmap_E_Mapping"
    linkTitle="cmap table specification"
    specLink="http://www.microsoft.com/typography/otspec/cmap.htm"
    shortDesc="A character maps to an invalid glyphID"
    fwLinkID="10339"
    tableName="cmap">
    <problem>The glyphID referenced in the cmap subtable does not exist. The glyph may have been removed without the cmap being updated. To correct the problem, add the desired glyph to the font, then map the glyph to the proper character code using a cmap edit tool.</problem>
</item>

<item
    helpID="E0315"
    atom="cmap_E_SubtableLength_eot"
    linkTitle="cmap table specification"
    specLink="http://www.microsoft.com/typography/otspec/cmap.htm"
    shortDesc="The subtable length points past the end of the table"
    fwLinkID="10339"
    tableName="cmap">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E0316"
    atom="cmap_E_SubtableLength_zero"
    linkTitle="cmap table specification"
    specLink="http://www.microsoft.com/typography/otspec/cmap.htm"
    shortDesc="The subtable length is zero"
    fwLinkID="10339"
    tableName="cmap">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E0317"
    atom="cmap_E_SubtableOffset_eot"
    linkTitle="cmap table specification"
    specLink="http://www.microsoft.com/typography/otspec/cmap.htm"
    shortDesc="The subtable offset points past the end of the table"
    fwLinkID="10339"
    tableName="cmap">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E0318"
    atom="cmap_E_SubtableOffset_zero"
    linkTitle="cmap table specification"
    specLink="http://www.microsoft.com/typography/otspec/cmap.htm"
    shortDesc="The subtable offset is zero"
    fwLinkID="10339"
    tableName="cmap">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E0319"
    atom="cmap_E_SubtableOverlap"
    linkTitle="cmap table specification"
    specLink="http://www.microsoft.com/typography/otspec/cmap.htm"
    shortDesc="Overlapping subtables were found"
    fwLinkID="10339"
    tableName="cmap">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E0320"
    atom="cmap_E_SubtableSortOrder"
    linkTitle="cmap table specification"
    specLink="http://www.microsoft.com/typography/otspec/cmap.htm"
    shortDesc="The subtables are not in the correct order"
    fwLinkID="10339"
    tableName="cmap">
    <problem>The cmap subtables (and their header entries) must be sorted first by platform ID, then by platform-specific encoding ID, and then by the version field in the corresponding subtable. Regenerate this font.</problem>
</item>

<item
    helpID="E0321"
    atom="cmap_E_SubtableValidFormat"
    linkTitle="cmap table specification"
    specLink="http://www.microsoft.com/typography/otspec/cmap.htm"
    shortDesc="The subtable's format number is invalid"
    fwLinkID="10339"
    tableName="cmap">
    <problem>The valid cmap subtable formats are: 0 (byte encoding table); 2 (high-byte mapping through table); 4 (segment mapping to delta values); 6 (trimmed table mapping); 8 (mixed 16-bit and 32-bit coverage); 10 (trimmed array); and 12 (segmented coverage). Regenerate this font.</problem>
</item>

<item
    helpID="E0322"
    atom="cmap_E_version"
    linkTitle="cmap table specification"
    specLink="http://www.microsoft.com/typography/otspec/cmap.htm"
    shortDesc="The table version number is not 0"
    fwLinkID="10339"
    tableName="cmap">
    <problem>Version 0 is the only version of the cmap table currently defined. Correct this field using a table editing tool.</problem>
</item>

<item
    helpID="E0323"
    atom="cmap_E_NonMacSubtableLanguage"
    linkTitle="cmap table specification"
    specLink="WARNING: field missing"
    shortDesc="A non-mac subtable has a non-zero language value"
    fwLinkID="10339"
    tableName="cmap">
    <problem>This field must be set to zero for all cmap subtables whose platform IDs are other than Macintosh (platform ID 1). Correct this field using a cmap editing tool.</problem>
</item>

<item
    helpID="E0324"
    atom="cmap_E_f12_EndCode_GT_10FFFF"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The last endCharCode is greater than 0x10ffff"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="E0330"
    atom="cmap_E_f14_VarSelector"
    linkTitle="cmap table specification"
    specLink="WARNING: field missing"
    shortDesc="Illegal variation selector"
    fwLinkID="10339"
    tableName="cmap">
    <problem>The set of legal variation selectors is U+E0100-U+E01EF and U+FE00-U+FE0F and </problem>
</item>

<item
    helpID="E0331"
    atom="cmap_E_f14_VarSelector_Order"
    linkTitle="cmap table specification"
    specLink="WARNING: field missing"
    shortDesc="Variation Selectors not in ascendering order"
    fwLinkID="10339"
    tableName="cmap">
    <problem>Variation Selector Records must be sorted in increasing order of 'varSelector'.</problem>
</item>

<item
    helpID="E0332"
    atom="cmap_E_f14_VarSelector_Duplicate"
    linkTitle="cmap table specification"
    specLink="WARNING: field missing"
    shortDesc="More than one record for a given variation selector"
    fwLinkID="10339"
    tableName="cmap">
    <problem>No two records may have the same 'varSelector'.</problem>
</item>

<item
    helpID="E0333"
    atom="cmap_E_f14_CodePoint"
    linkTitle="cmap table specification"
    specLink="WARNING: field missing"
    shortDesc="Illegal Unicode code point value"
    fwLinkID="10339"
    tableName="cmap">
    <problem>Unicode code points must be between U+0000 and U+10FFFF, inclusive</problem>
</item>

<item
    helpID="E0334"
    atom="cmap_E_f14_DefaultUVS_Sort"
    linkTitle="cmap table specification"
    specLink="WARNING: field missing"
    shortDesc="Default UVS table value ranges overlap or out of order"
    fwLinkID="10339"
    tableName="cmap">
    <problem>The Unicode Value Ranges of a Default UVS Table must be sorted in increasing order of 'startUnicodeValue'. The ranges must not overlap, i.e., ('startUnicodeValue' + 'additionalCount') must be last than the 'startUnicodeValue' of the following range (if any).</problem>
</item>

<item
    helpID="E0335"
    atom="cmap_E_f14_LastCode_GT_FFFFFF"
    linkTitle="cmap table specification"
    specLink="WARNING: field missing"
    shortDesc="Default UVS table startUnicodeValue + additionalCount greater than 0xFFFFFF"
    fwLinkID="10339"
    tableName="cmap">
    <problem>The ('startUnicodeValue' + 'additionalCount') of a given Unicode Value Range of a Default UVS Table must not exceed 0xFFFFFF</problem>
</item>

<item
    helpID="E0336"
    atom="cmap_E_f14_NonDefaultUVS_Sort"
    linkTitle="cmap table specification"
    specLink="WARNING: field missing"
    shortDesc="Non-Default UVS table value ranges overlap or out of order"
    fwLinkID="10339"
    tableName="cmap">
    <problem>The UVS Mappings of a Non-Default UVS Table must be sorted in increasing order of 'unicodeValue'. No two mappings in this table may have the same 'unicodeValue' values.</problem>
</item>

<item
    helpID="E0337"
    atom="cmap_E_f14_GlyphID_Range"
    linkTitle="cmap table specification"
    specLink="WARNING: field missing"
    shortDesc="GlyphID in Non-Default UVS table greater than number of glyphs in the font"
    fwLinkID="10339"
    tableName="cmap">
    <problem>A 'unicodeValue' in a UVS Mapping in a Non-Default UVS Table has been mapped to a glyphID that is greater than or equal to the number of glyphs in the font.</problem>
</item>

<item
    helpID="E0338"
    atom="cmap_E_f14_DefaultUVS_EOT"
    linkTitle="cmap table specification"
    specLink="WARNING: field missing"
    shortDesc="Default UVS table offset out of range of table"
    fwLinkID="10339"
    tableName="cmap">
    <problem>The offset to a Default UVS table is outside the bounds of the Format 14 subtable. 
&lt;p&gt;
This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file;
 a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E0339"
    atom="cmap_E_f14_NonDefaultUVS_EOT"
    linkTitle="cmap table specification"
    specLink="WARNING: field missing"
    shortDesc="Non-Default UVS table offset out of range of table"
    fwLinkID="10339"
    tableName="cmap">
    <problem>The offset to a Non-Default UVS table is outside the bounds of the Format 14 subtable. 
&lt;p&gt;
This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E0340"
    atom="name_E_NoFormat14"
    linkTitle="name table specification"
    specLink="WARNING: field missing"
    shortDesc="A name record specifies using the Unicode Variation Sequences cmap subtable (Format 14)"
    fwLinkID="10361"
    tableName="name">
    <problem>Unicode platform ID 0, encoding ID 5 (Unicode Variation Sequences) can be used for encodings in the 'cmap' table but not for strings in the 'name' table.</problem>
</item>

<item
    helpID="E0341"
    atom="cmap_E_f14_NonDefaultUVS_TooSmall"
    linkTitle="cmap table specification"
    specLink="WARNING: field missing"
    shortDesc="Non-Default UVS table offset out of range of offset tables"
    fwLinkID="10339"
    tableName="cmap">
    <problem>The offset to a Non-Default UVS table is within the Format 14 header or variation selector records.
&lt;p&gt;
This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E0342"
    atom="cmap_E_f14_DefaultUVS_TooSmall"
    linkTitle="cmap table specification"
    specLink="WARNING: field missing"
    shortDesc="Default UVS table offset out of range of offset tables"
    fwLinkID="10339"
    tableName="cmap">
    <problem>The offset to a Default UVS table is within the Format 14 header or variation selector records.
&lt;p&gt;
This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E0343"
    atom="cmap_E_f14_OverlappingMaps"
    linkTitle="cmap table specification"
    specLink="WARNING: field missing"
    shortDesc="Overlapping of Format 14 tables"
    fwLinkID="10339"
    tableName="cmap">
    <problem>Two tables overlap indicating corrupted data. The tables could be either non-default or default UVS tables or both.
&lt;p&gt;
This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font. </problem>
</item>

<item
    helpID="E0400"
    atom="cvt_E_length_odd"
    linkTitle="cvt table specification"
    specLink="http://www.microsoft.com/typography/otspec/cvt.htm"
    shortDesc="The length of the cvt table is not an even number of bytes"
    fwLinkID="10340"
    tableName="cvt">
    <problem>The length of the table must be an integral number of FWORD units. Recreate the cvt table using a hinting tool.</problem>
</item>

<item
    helpID="E0500"
    atom="DSIG_E_Formats"
    linkTitle="DSIG table specification"
    specLink="http://www.microsoft.com/typography/otspec/dsig.htm"
    shortDesc="A signature block is not in format 1"
    fwLinkID="10341"
    tableName="DSIG">
    <problem>Version 1 (0x00000001) is the only version of the DSIG table currently defined. Correct this field using a table editing tool; or obtain a font signing tool that creates valid DSIG tables.</problem>
</item>

<item
    helpID="E0501"
    atom="DSIG_E_Reserved"
    linkTitle="DSIG table specification"
    specLink="http://www.microsoft.com/typography/otspec/dsig.htm"
    shortDesc="A signature block contains a reserved value that is not zero"
    fwLinkID="10341"
    tableName="DSIG">
    <problem>The two bytes at the beginning of each signature block are both reserved fields and should both be set to 0. Sign the font again using a tool that sets these bytes correctly.</problem>
</item>

<item
    helpID="E0502"
    atom="DSIG_E_VerifySignature"
    linkTitle="DSIG table specification"
    specLink="http://www.microsoft.com/typography/otspec/dsig.htm"
    shortDesc="The digital signature of the file did not verify"
    fwLinkID="10341"
    tableName="DSIG">
    <problem>The digital signature is not valid, or the file does not match the digital signature. This may indicate that the contents of the font file were altered after the font was signed, or the signature is not current, or a non-matching DSIG table has been appended to the font.&lt;BR&gt;&lt;BR&gt;Although the enforcement of signatures is an administrative policy issue, Microsoft recommends that, to promote file integrity, all fonts be digitally signed. Resign the font, or contact the font vendor for a valid version of the font.</problem>
</item>

<item
    helpID="E0600"
    atom="EBDT_E_version"
    linkTitle="EBDT table specification"
    specLink="http://www.microsoft.com/typography/otspec/ebdt.htm"
    shortDesc="The version is not 0x00020000"
    fwLinkID="10342"
    tableName="EBDT">
    <problem>Version 0x00020000 is the only version of the EBDT table currently defined. Correct this field using a table editing tool.</problem>
</item>

<item
    helpID="E0601"
    atom="EBDT_E_TableDependency"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The EBLC table is not present"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="E0602"
    atom="EBDT_E_GlyphImageData"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The glyph image data is invalid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="E0700"
    atom="EBLC_E_bitDepth"
    linkTitle="EBLC table specification"
    specLink="http://www.microsoft.com/typography/otspec/eblc.htm"
    shortDesc="the bitDepth field is not a valid value"
    fwLinkID="10343"
    tableName="EBLC">
    <problem>The Microsoft rasterizer v.1.7 or greater supports the following bitDepth values: 1 (black/white), 2 (4 levels of gray), 4 (16 levels of gray), and 8 (256 levels of gray). Change this value using a table editing tool or an embedded bitmap editor.</problem>
</item>

<item
    helpID="E0701"
    atom="EBLC_E_indexSubTableArrayOffset"
    linkTitle="EBLC table specification"
    specLink="http://www.microsoft.com/typography/otspec/eblc.htm"
    shortDesc="The indexSubTableArrayOffset field is not in a valid range"
    fwLinkID="10343"
    tableName="EBLC">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E0702"
    atom="EBLC_E_version"
    linkTitle="EBLC table specification"
    specLink="http://www.microsoft.com/typography/otspec/eblc.htm"
    shortDesc="The version is not 0x00020000"
    fwLinkID="10343"
    tableName="EBLC">
    <problem>Version 0x00020000 is the only version of the EBLC table currently defined. Correct this field using a table editing tool.</problem>
</item>

<item
    helpID="E0703"
    atom="EBLC_E_TableDependency"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The EBDT table is not present"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="E0704"
    atom="EBLC_E_BitmapSizeTableIndexOrder"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Bitmap size table start index is larger than the end index value"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="E0705"
    atom="EBLC_E_indexSubTables"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The index subtable is not valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="E0706"
    atom="EBLC_E_numSizes"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The number of sizes requires more space than available in the EBLC table."
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="E0800"
    atom="EBSC_E_TableLength"
    linkTitle="EBSC table specification"
    specLink="http://www.microsoft.com/typography/otspec/ebsc.htm"
    shortDesc="The table length does not equal the calculated value"
    fwLinkID="10344"
    tableName="EBSC">
    <problem>The table length does not correspond to the number of sizes (strikes) covered and the bitmapScaleTable required for each. Rebuild and add the bitmap tables using an embedded bitmap editing tool.</problem>
</item>

<item
    helpID="E0801"
    atom="EBSC_E_version"
    linkTitle="EBSC table specification"
    specLink="http://www.microsoft.com/typography/otspec/ebsc.htm"
    shortDesc="The version is not 0x00020000"
    fwLinkID="10344"
    tableName="EBSC">
    <problem>Version 0x00020000 is the only version of the EBSC table currently defined. Correct this field using a table editing tool or an embedded bitmap embedding tool that uses the correct version value.</problem>
</item>

<item
    helpID="E0802"
    atom="EBSC_E_TableDependency"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Other required bitmap tables are not present"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="E0803"
    atom="EBSC_E_StrikeSizeNoEBLC"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Could not verify substitute bitmap strikes because EBLC is not present"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="E0804"
    atom="EBSC_E_StrikeSize"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Substitute bitmap strike is not in font"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="E1000"
    atom="gasp_E_rangeGaspBehavior"
    linkTitle="gasp table specification"
    specLink="http://www.microsoft.com/typography/otspec/gasp.htm"
    shortDesc="Some rangeGaspBehavior fields contain invalid flags"
    fwLinkID="10346"
    tableName="gasp">
    <problem>The four currently defined flags for rangeGaspBehavior include: GASP_DOGRAY (0x0002, use grayscale rendering); GASP_GRIDFIT (0x0001, use gridfitting); GASP_DOGRAY|GASP_GRIDFIT (0x0003, use both grayscale rendering and gridfitting); neither (0x0004). Correct the values using a table editing tool.</problem>
</item>

<item
    helpID="E1001"
    atom="gasp_E_Sentinel"
    linkTitle="gasp table specification"
    specLink="http://www.microsoft.com/typography/otspec/gasp.htm"
    shortDesc="The gaspRange array does not have a 0xFFFF sentinel"
    fwLinkID="10346"
    tableName="gasp">
    <problem>The last record should use 0xFFFF as a sentinel value for rangeMaxPPEM and should describe the behavior desired at all sizes larger than the previous record's upper limit. If the only entry in 'gasp' is the 0xFFFF sentinel value, the behavior described will be used for all sizes. Correct the gasp table using a table editing tool that builds the table properly.</problem>
</item>

<item
    helpID="E1002"
    atom="gasp_E_SortOrder"
    linkTitle="gasp table specification"
    specLink="http://www.microsoft.com/typography/otspec/gasp.htm"
    shortDesc="The gaspRange array is not in sorted order"
    fwLinkID="10346"
    tableName="gasp">
    <problem>The records in the gaspRange[] array must be sorted in order of increasing rangeMaxPPEM value. Correct the table using a table editor that builds the gasp table properly.</problem>
</item>

<item
    helpID="E1003"
    atom="gasp_E_Version"
    linkTitle="gasp table specification"
    specLink="http://www.microsoft.com/typography/otspec/gasp.htm"
    shortDesc="The version number is not valid"
    fwLinkID="10346"
    tableName="gasp">
    <problem>Version 0 and 1 are the only versions of the gasp table currently defined. Correct this field using a table editing tool.</problem>
</item>

<item
    helpID="E1100"
    atom="glyf_E_CompositeAmbigousTransform"
    linkTitle="glyf table specification"
    specLink="http://www.microsoft.com/typography/otspec/glyf.htm"
    shortDesc="Component's transform is ambigously defined"
    fwLinkID="10348"
    tableName="glyf">
    <problem>When defining composite components of composite glyphs, bits 3 (WE_HAVE_A_SCALE), 6 (WE_HAVE_AN_X_AND_Y_SCALE), and 7 (WE_HAVE_A_TWO_BY_TWO) should be mutually exclusive. This error indicates that more than one of these bits is set.</problem>
</item>

<item
    helpID="E1101"
    atom="glyf_E_ExceptionUnhandeled"
    linkTitle="glyf table specification"
    specLink="http://www.microsoft.com/typography/otspec/glyf.htm"
    shortDesc="An exception occurred during glyph validation or loading of one of its components"
    fwLinkID="10348"
    tableName="glyf">
    <problem>This error indicates that the validating process for a specific glyph failed and the validation for that glyph has been stopped. Validation then continues on the next glyph. Please report this error to the Microsoft Typography group.</problem>
</item>

<item
    helpID="E1102"
    atom="glyf_E_UnableToStartValidation"
    linkTitle="glyf table specification"
    specLink="http://www.microsoft.com/typography/otspec/glyf.htm"
    shortDesc="Unable  to start validation of 'glyf' table"
    fwLinkID="10348"
    tableName="glyf">
    <problem>The Font Validator will be unable to start glyph validation if one of the following conditions is present: unable to open the font file, unable to get font from file, missing glyf table, missing loca table, incorrect loca format, or incorrect number of loca entries.</problem>
</item>

<item
    helpID="E1200"
    atom="hdmx_E_DeviceRecordPadBytes_nonzero"
    linkTitle="hdmx table specification"
    specLink="http://www.microsoft.com/typography/otspec/hdmx.htm"
    shortDesc="The DeviceRecord padding bytes are not 0"
    fwLinkID="10351"
    tableName="hdmx">
    <problem>Each DeviceRecord must be padded with 0's to make it long word aligned. Use a tool such as Microsoft's CacheTT to recalculate and build this table.</problem>
</item>

<item
    helpID="E1201"
    atom="hdmx_E_DuplicateDeviceRecords"
    linkTitle="hdmx table specification"
    specLink="http://www.microsoft.com/typography/otspec/hdmx.htm"
    shortDesc="There are duplicate DeviceRecords"
    fwLinkID="10351"
    tableName="hdmx">
    <problem>Use a tool such as Microsoft's CacheTT to recalculate and build this table.</problem>
</item>

<item
    helpID="E1202"
    atom="hdmx_E_Rasterizer"
    linkTitle="hdmx table specification"
    specLink="http://www.microsoft.com/typography/otspec/hdmx.htm"
    shortDesc="The hdmx widths can't be validated due to an error while rasterizing the glyphs, likely a hinting instruction error"
    fwLinkID="10351"
    tableName="hdmx">
    <problem>Metrics affected by hints can only be validated at runtime. Therefore, this error is typically generated when the Font Validator uses the rasterizer to execute the hinting instructions contained in the font. The detail of this error message may or may not refer to the glyph that is associated with the bad hinting code, depending on how the overflow or other rasterizing error was encountered. For example, in the case of a stack overflow, the problem may be due to hinting instructions for a previous glyph not having been properly removed from the stack. To perform detailed checks of hinting instructions, select rasterization testing in the Font Validator, or use a tool such as Microsoft's Flint or VTT.</problem>
</item>

<item
    helpID="E1203"
    atom="hdmx_E_SizeofDeviceRecord_alignment"
    linkTitle="hdmx table specification"
    specLink="http://www.microsoft.com/typography/otspec/hdmx.htm"
    shortDesc="The SizeofDeviceRecord is not long aligned"
    fwLinkID="10351"
    tableName="hdmx">
    <problem>SizeofDeviceRecord is a LONG value and should be padded in order to be long aligned. Use a tool such as Microsoft's CacheTT to recalculate and build this table.</problem>
</item>

<item
    helpID="E1204"
    atom="hdmx_E_SizeofDeviceRecord_numGlyphs"
    linkTitle="hdmx table specification"
    specLink="http://www.microsoft.com/typography/otspec/hdmx.htm"
    shortDesc="The SizeofDeviceRecord doesn't match the calculated value"
    fwLinkID="10351"
    tableName="hdmx">
    <problem>There is a discrepancy between the number of glyphs specified and the size of the DeviceRecord. Use a tool such as Microsoft's CacheTT to recalculate and build this table.</problem>
</item>

<item
    helpID="E1205"
    atom="hdmx_E_SortedOrder"
    linkTitle="hdmx table specification"
    specLink="http://www.microsoft.com/typography/otspec/hdmx.htm"
    shortDesc="The DeviceRecords are not sorted in ascending order"
    fwLinkID="10351"
    tableName="hdmx">
    <problem>DeviceRecords in the hdmx table should be sorted by pixel size. Use a tool such as Microsoft's CacheTT to recalculate and build this table.</problem>
</item>

<item
    helpID="E1206"
    atom="hdmx_E_Version"
    linkTitle="hdmx table specification"
    specLink="http://www.microsoft.com/typography/otspec/hdmx.htm"
    shortDesc="The version number is not 0"
    fwLinkID="10351"
    tableName="hdmx">
    <problem>Version 0 is the only version of the hdmx table currently defined. Use a tool such as Microsoft's CacheTT to recalculate and build this table.</problem>
</item>

<item
    helpID="E1207"
    atom="hdmx_E_Widths"
    linkTitle="hdmx table specification"
    specLink="http://www.microsoft.com/typography/otspec/hdmx.htm"
    shortDesc="The hdmx width doesn't match the calculated width"
    fwLinkID="10351"
    tableName="hdmx">
    <problem>The hdmx width (the pixel width of a glyph in ppem) does not match the value calculated by the current version of the rasterizer. These values may not match if glyphs have been updated but the hdmx table has not yet been recalculated (using a tool such as Microsoft's CacheTT). This problem may also occur if the hdmx table was generated using a previous version of the rasterizer, or another tool that performs the width calculations differently. To make the values match, use the latest version of CacheTT to calculate the cached values using the current rasterizer. However, you may not want to change these values if there are concerns about the way text in legacy documents might reflow.</problem>
</item>

<item
    helpID="E1208"
    atom="hdmx_E_TableLength"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The table length is incorrect"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="E1209"
    atom="hdmx_E_NumDeviceRecords_neg"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The number of device records is negative"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="E1300"
    atom="head_E_created_invalid"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="The created time is not valid"
    fwLinkID="10352"
    tableName="head">
    <problem>The time the font was created should be a 64-bit integer that equals the number of seconds since midnight, January 1, 1904. Use a table editing tool to correct this value.</problem>
</item>

<item
    helpID="E1301"
    atom="head_E_flags_bit14"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="Reserved bit 14 of the flags field is set"
    fwLinkID="10352"
    tableName="head">
    <problem>Bit 14 of the flags field is reserved and should be set to 0. Use a table editing tool to correct this value.</problem>
</item>

<item
    helpID="E1302"
    atom="head_E_flags_bit15"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="Reserved bit 15 of the flags field is set"
    fwLinkID="10352"
    tableName="head">
    <problem>Bit 15 of the flags field is reserved and should be set to 0. Use a table editing tool to correct this value.</problem>
</item>

<item
    helpID="E1303"
    atom="head_E_flags_bit4_0_hdmx"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="Non-linear scaling flag (bit 4) is clear, but hdmx table is present"
    fwLinkID="10352"
    tableName="head">
    <problem>Setting bit 4 of the flags field to clear indicates that the advance width of glyphs will scale linearly because hinting instructions will not alter the advance widths.. The presence of the hdmx table indicates that the advance width of glyphs within this font may be affected by hinting instructions. Set this bit to indicate that the advance widths might not scale linearly.</problem>
</item>

<item
    helpID="E1304"
    atom="head_E_flags_bit4_0_LTSH"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="Non-linear scaling flag (bit 4) is clear, but LTSH table is present"
    fwLinkID="10352"
    tableName="head">
    <problem>Setting bit 4 of the flags field to clear indicates that the advance width of glyphs will scale linearly because hinting instructions will not alter the advance widths. If this is so, then no LTSH table is needed in the font. The presence of the LTSH table indicates that the advance width of glyphs within this font may be affected by hinting instructions. Set this bit to indicate that the advance widths might not scale linearly.</problem>
</item>

<item
    helpID="E1305"
    atom="head_E_FontChecksum"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="Font checksum is incorrect"
    fwLinkID="10352"
    tableName="head">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E1306"
    atom="head_E_fontDirectionHint"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="The fontDirectionHint is not in the range -2..2"
    fwLinkID="10352"
    tableName="head">
    <problem>Allowable settings for the fontDirectionHint field range from -2 to 2. Correct this value using a tool that builds valid head tables.</problem>
</item>

<item
    helpID="E1307"
    atom="head_E_glyphDataFormat"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="The glyphDataFormat value is not 0"
    fwLinkID="10352"
    tableName="head">
    <problem>The only currently defined value for this field is 0. Correct this value using a tool that builds valid head tables.</problem>
</item>

<item
    helpID="E1308"
    atom="head_E_indexToLocFormat_match"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="The indexToLocFormat value does not match the loca table"
    fwLinkID="10352"
    tableName="head">
    <problem>This value should be set to indicate which version, long or short, of the loca table is being used. A value of 0 indicates the loca table uses short offsets, a value of 1 indicates long offsets.</problem>
</item>

<item
    helpID="E1309"
    atom="head_E_indexToLocFormat_range"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="The indexToLocFormat value is not 0 or 1"
    fwLinkID="10352"
    tableName="head">
    <problem>This value should be set to indicate which version, long or short, of the loca table is being used. A value of 0 indicates the loca table uses short offsets, a value of 1 indicates long offsets. Ensure that the tool you are using to edit this font is setting this value correctly.</problem>
</item>

<item
    helpID="E1310"
    atom="head_E_lowestRecPPEM_zero"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="The lowestRecPPEM value is zero"
    fwLinkID="10352"
    tableName="head">
    <problem>This value should indicate the smallest size (in pixels) at which the font is readable. The lowestRecPPEM value should be an indicator of the level at which the font is hinted. Use a head table editor to correct this value.</problem>
</item>

<item
    helpID="E1311"
    atom="head_E_macStyleBold_subfamily"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="The macStyle bold bit doesn't match the name table's font subfamily string"
    fwLinkID="10352"
    tableName="head">
    <problem>There is a discrepancy between the setting of the bold bit of the macStyle field and the Subfamily name field in the name table. There are several places within the font file that the typeface may be characterized as 'Regular,' 
'Bold,' 'Italic,' 'Condensed,' etc. Font designers should encode this information consistently
throughout the font. Font clients use the information to:&lt;BR&gt;
&lt;UL&gt;
&lt;LI&gt;organize related typefaces into families (i.e., Arial Narrow, Arial, Arial Bold, Arial 

Expanded...)&lt;/LI&gt;
&lt;LI&gt;use appropriate names when enumerating typefaces to the user
&lt;LI&gt;obtain a font from the system according to certain attributes (weight, style, width)&lt;/LI&gt;
&lt;/UL&gt;
The fields related to encoding this information exist in several different tables:
&lt;UL&gt;
&lt;LI&gt;In the name table, Name ID strings (family name, subfamily name, full-font name, preferred 

family grouping, and preferred subfamily grouping)&lt;/LI&gt;
&lt;LI&gt;In the OS/2 table, usWeightClass, usWidthClass, PANOSE(tm), and fsSelection.&lt;/LI&gt;
&lt;LI&gt;In the head table, macStyle bits&lt;/LI&gt;
&lt;/UL&gt;
Correct this data using a table editing tool.&lt;BR&gt;For examples of how to use these various fields, see these &lt;A TARGET=&quot;top&quot;  HREF=&quot;http://go.microsoft.com/fwlink?LinkID=10455&quot;&gt;name string examples&lt;/A&gt;.&lt;BR&gt;</problem>
</item>

<item
    helpID="E1312"
    atom="head_E_macStyleBold0_OS2"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="The macStyle bold bit is clear, but the OS/2 fsSelection bold bit is set"
    fwLinkID="10352"
    tableName="head">
    <problem>The setting of the macStyle bold bit indicates the font is not bold, but the fsSelection bits in the OS/2 table indicate the font is bold. The fsSelection bits are used over the macStyle bits in Windows.&lt;BR&gt;There are several places within the font file that the typeface may be characterized as 'Regular,' 

'Bold,' 'Italic,' 'Condensed,' etc. Font designers should encode this information consistently 

throughout the font. Font clients use the information to:&lt;BR&gt;
&lt;UL&gt;
&lt;LI&gt;organize related typefaces into families (i.e., Arial Narrow, Arial, Arial Bold, Arial 

Expanded...)&lt;/LI&gt;
&lt;LI&gt;use appropriate names when enumerating typefaces to the user
&lt;LI&gt;obtain a font from the system according to certain attributes (weight, style, width)&lt;/LI&gt;
&lt;/UL&gt;
The fields related to encoding this information exist in several different tables:
&lt;UL&gt;
&lt;LI&gt;In the name table, Name ID strings (family name, subfamily name, full-font name, preferred 

family grouping, and preferred subfamily grouping)&lt;/LI&gt;
&lt;LI&gt;In the OS/2 table, usWeightClass, usWidthClass, PANOSE(tm), and fsSelection.&lt;/LI&gt;
&lt;LI&gt;In the head table, macStyle bits&lt;/LI&gt;
&lt;/UL&gt;
Correct this data using a table editing tool.&lt;BR&gt;For examples of how to use these various fields, see these &lt;A TARGET=&quot;top&quot;  HREF=&quot;http://go.microsoft.com/fwlink?LinkID=10455&quot;&gt;name string examples&lt;/A&gt;.&lt;BR&gt;</problem>
</item>

<item
    helpID="E1313"
    atom="head_E_macStyleBold1_OS2"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="The macStyle bold bit is set, but the OS/2 fsSelection bold bit is clear"
    fwLinkID="10352"
    tableName="head">
    <problem>The setting of the macStyle bold bit indicates the font is bold, but the fsSelection field in the OS/2 table indicates the font is not bold. The fsSelection bits are used over the macStyle bits in Windows.&lt;BR&gt;There are several places within the font file that the typeface may be characterized as 'Regular,' 

'Bold,' 'Italic,' 'Condensed,' etc. Font designers should encode this information consistently 

throughout the font. Font clients use the information to:&lt;BR&gt;
&lt;UL&gt;
&lt;LI&gt;organize related typefaces into families (i.e., Arial Narrow, Arial, Arial Bold, Arial 

Expanded...)&lt;/LI&gt;
&lt;LI&gt;use appropriate names when enumerating typefaces to the user
&lt;LI&gt;obtain a font from the system according to certain attributes (weight, style, width)&lt;/LI&gt;
&lt;/UL&gt;
The fields related to encoding this information exist in several different tables:
&lt;UL&gt;
&lt;LI&gt;In the name table, Name ID strings (family name, subfamily name, full-font name, preferred 

family grouping, and preferred subfamily grouping)&lt;/LI&gt;
&lt;LI&gt;In the OS/2 table, usWeightClass, usWidthClass, PANOSE(tm), and fsSelection.&lt;/LI&gt;
&lt;LI&gt;In the head table, macStyle bits&lt;/LI&gt;
&lt;/UL&gt;
Correct this data using a table editing tool.&lt;BR&gt;For examples of how to use these various fields, see these &lt;A TARGET=&quot;top&quot;  HREF=&quot;http://go.microsoft.com/fwlink?LinkID=10455&quot;&gt;name string examples&lt;/A&gt;.&lt;BR&gt;</problem>
</item>

<item
    helpID="E1314"
    atom="head_E_macStyleItal_subfamily"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="The macStyle italic bit doesn't match the name table's font subfamily string"
    fwLinkID="10352"
    tableName="head">
    <problem>There is a discrepancy between the setting of the italic bit of the macStyle field and the Subfamily name field in the name table. There are several places within the font file that the typeface may be characterized as 'Regular,' 

'Bold,' 'Italic,' 'Condensed,' etc. Font designers should encode this information consistently 

throughout the font. Font clients use the information to:&lt;BR&gt;
&lt;UL&gt;
&lt;LI&gt;organize related typefaces into families (i.e., Arial Narrow, Arial, Arial Bold, Arial 

Expanded...)&lt;/LI&gt;
&lt;LI&gt;use appropriate names when enumerating typefaces to the user
&lt;LI&gt;obtain a font from the system according to certain attributes (weight, style, width)&lt;/LI&gt;
&lt;/UL&gt;
The fields related to encoding this information exist in several different tables:
&lt;UL&gt;
&lt;LI&gt;In the name table, Name ID strings (family name, subfamily name, full-font name, preferred 

family grouping, and preferred subfamily grouping)&lt;/LI&gt;
&lt;LI&gt;In the OS/2 table, usWeightClass, usWidthClass, PANOSE(tm), and fsSelection.&lt;/LI&gt;
&lt;LI&gt;In the head table, macStyle bits&lt;/LI&gt;
&lt;/UL&gt;
Correct this data using a table editing tool.&lt;BR&gt;For examples of how to use these various fields, see these &lt;A TARGET=&quot;top&quot;  HREF=&quot;http://go.microsoft.com/fwlink?LinkID=10455&quot;&gt;name string examples&lt;/A&gt;.&lt;BR&gt;</problem>
</item>

<item
    helpID="E1315"
    atom="head_E_macStyleItal0_OS2"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="The macStyle italic bit is clear, but the OS/2 fsSelection italic bit is set"
    fwLinkID="10352"
    tableName="head">
    <problem>The setting of the macStyle italic bit indicates the font is not italic, but the fsSelection bits in the OS/2 table indicate the font is italic. The fsSelection bits are used over the macStyle bits in Windows.&lt;BR&gt;There are several places within the font file that the typeface may be characterized as 'Regular,' 

'Bold,' 'Italic,' 'Condensed,' etc. Font designers should encode this information consistently 

throughout the font. Font clients use the information to:&lt;BR&gt;
&lt;UL&gt;
&lt;LI&gt;organize related typefaces into families (i.e., Arial Narrow, Arial, Arial Bold, Arial 

Expanded...)&lt;/LI&gt;
&lt;LI&gt;use appropriate names when enumerating typefaces to the user
&lt;LI&gt;obtain a font from the system according to certain attributes (weight, style, width)&lt;/LI&gt;
&lt;/UL&gt;
The fields related to encoding this information exist in several different tables:
&lt;UL&gt;
&lt;LI&gt;In the name table, Name ID strings (family name, subfamily name, full-font name, preferred 

family grouping, and preferred subfamily grouping)&lt;/LI&gt;
&lt;LI&gt;In the OS/2 table, usWeightClass, usWidthClass, PANOSE(tm), and fsSelection.&lt;/LI&gt;
&lt;LI&gt;In the head table, macStyle bits&lt;/LI&gt;
&lt;/UL&gt;
Correct this data using a table editing tool.&lt;BR&gt;For examples of how to use these various fields, see these &lt;A TARGET=&quot;top&quot;  HREF=&quot;http://go.microsoft.com/fwlink?LinkID=10455&quot;&gt;name string examples&lt;/A&gt;.&lt;BR&gt;</problem>
</item>

<item
    helpID="E1316"
    atom="head_E_macStyleItal0_post"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="The macStyle italic bit is clear, but the post table italic angle is nonzero"
    fwLinkID="10352"
    tableName="head">
    <problem>The setting of the macStyle italic bit indicates the font is not italic, but the italicAngle field in the post table suggests the font is slanted. Correct these encodings using a table editing tool.</problem>
</item>

<item
    helpID="E1317"
    atom="head_E_macStyleItal1_OS2"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="The macStyle italic bit is set, but the OS/2 fsSelection italic bit is clear"
    fwLinkID="10352"
    tableName="head">
    <problem>The setting of the macStyle italic bit indicates the font is italic, but the fsSelection bits in the OS/2 table indicate the font is not italic. The fsSelection bits are used over the macStyle bits in Windows.&lt;BR&gt;There are several places within the font file that the typeface may be characterized as 'Regular,' 

'Bold,' 'Italic,' 'Condensed,' etc. Font designers should encode this information consistently 

throughout the font. Font clients use the information to:&lt;BR&gt;
&lt;UL&gt;
&lt;LI&gt;organize related typefaces into families (i.e., Arial Narrow, Arial, Arial Bold, Arial 

Expanded...)&lt;/LI&gt;
&lt;LI&gt;use appropriate names when enumerating typefaces to the user
&lt;LI&gt;obtain a font from the system according to certain attributes (weight, style, width)&lt;/LI&gt;
&lt;/UL&gt;
The fields related to encoding this information exist in several different tables:
&lt;UL&gt;
&lt;LI&gt;In the name table, Name ID strings (family name, subfamily name, full-font name, preferred 

family grouping, and preferred subfamily grouping)&lt;/LI&gt;
&lt;LI&gt;In the OS/2 table, usWeightClass, usWidthClass, PANOSE(tm), and fsSelection.&lt;/LI&gt;
&lt;LI&gt;In the head table, macStyle bits&lt;/LI&gt;
&lt;/UL&gt;
Correct this data using a table editing tool.&lt;BR&gt;For examples of how to use these various fields, see these &lt;A TARGET=&quot;top&quot;  HREF=&quot;http://go.microsoft.com/fwlink?LinkID=10455&quot;&gt;name string examples&lt;/A&gt;.&lt;BR&gt;</problem>
</item>

<item
    helpID="E1318"
    atom="head_E_macStyleItal1_post"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="The macStyle italic bit is set, but the post table italic angle is zero"
    fwLinkID="10352"
    tableName="head">
    <problem>The setting of the macStyle italic bit indicates the font is italic, but the italicAngle field in the post table suggests the font is upright. Correct these encodings using a table editing tool.</problem>
</item>

<item
    helpID="E1319"
    atom="head_E_MagicNumber"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="The magic number is not 0x5f0f3cf5"
    fwLinkID="10352"
    tableName="head">
    <problem>0x5f0f3cf5 is the specified value for the magicNumber.</problem>
</item>

<item
    helpID="E1320"
    atom="head_E_modified_invalid"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="The modified time is not valid"
    fwLinkID="10352"
    tableName="head">
    <problem>The time the font was created should be a 64-bit integer that equals the number of seconds since midnight, January 1, 1904. Use a table editing tool to correct this value.</problem>
</item>

<item
    helpID="E1321"
    atom="head_E_TableLength"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="Table length is not 54 bytes"
    fwLinkID="10352"
    tableName="head">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E1322"
    atom="head_E_TableVersion"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="The table version number is not 0x00010000"
    fwLinkID="10352"
    tableName="head">
    <problem>Version 0x00010000 is the only version of the hhea table currently defined. Correct this field using a table editing tool.</problem>
</item>

<item
    helpID="E1323"
    atom="head_E_unitsPerEM_GT16384"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="The unitsPerEm is greater than 16384"
    fwLinkID="10352"
    tableName="head">
    <problem>The allowable range for the unitsPerEm value of a font is 16 - 16384 (for Windows) and 64 - 16384 (for Macintosh). For performance reasons, it is preferable to use a value that is a power of 2.</problem>
</item>

<item
    helpID="E1324"
    atom="head_E_unitsPerEm_LT16"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="The unitsPerEm is less than 16"
    fwLinkID="10352"
    tableName="head">
    <problem>The allowable range for the unitsPerEm value of a font is 16 - 16384 (for Windows) and 64 - 16384 (for Macintosh). For performance reasons, it is preferable to use a value that is a power of 2.</problem>
</item>

<item
    helpID="E1325"
    atom="head_E_xMax_glyf"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="The xMax value does not match the maximum glyph xMax"
    fwLinkID="10352"
    tableName="head">
    <problem>The bounding box values should be computed using only glyphs that have contours. Glyphs with no contours should be ignored when identifying max and min values.&lt;BR&gt;&lt;BR&gt;This error may indicate that the font is corrupted, or that the head table in the font was not updated after additional glyphs were added and the font should be regenerated.</problem>
</item>

<item
    helpID="E1326"
    atom="head_E_xMin_glyf"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="The xMin value does not match the minimum glyph xMin"
    fwLinkID="10352"
    tableName="head">
    <problem>The bounding box values should be computed using only glyphs that have contours. Glyphs with no contours should be ignored when identifying max and min values.&lt;BR&gt;&lt;BR&gt;This error may indicate that the font is corrupted, or that the head table in the font was not updated after additional glyphs were added and the font should be regenerated.</problem>
</item>

<item
    helpID="E1327"
    atom="head_E_xMin_GT_xMax"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="xMin is greater than xMax"
    fwLinkID="10352"
    tableName="head">
    <problem>The bounding box values should be computed using only glyphs that have contours. Glyphs with no contours should be ignored when identifying max and min values.&lt;BR&gt;&lt;BR&gt;This error may indicate that the font is corrupted and must be regenerated using a font building tool.</problem>
</item>

<item
    helpID="E1328"
    atom="head_E_yMax_glyf"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="The yMax value does not match the maximum glyph yMax"
    fwLinkID="10352"
    tableName="head">
    <problem>This value should represent the extreme of all the glyphs in the font. Correct this value using a table editing tool or a tool that creates valid head tables.</problem>
</item>

<item
    helpID="E1329"
    atom="head_E_yMin_glyf"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="The yMin value does not match the minimum glyph yMin"
    fwLinkID="10352"
    tableName="head">
    <problem>This value should represent the extreme of all the glyphs in the font. Correct this value using a table editing tool or a tool that creates valid head tables.</problem>
</item>

<item
    helpID="E1330"
    atom="head_E_yMin_GT_yMax"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="yMin is greater than yMax"
    fwLinkID="10352"
    tableName="head">
    <problem>The bounding box values should be computed using only glyphs that have contours. Glyphs with no contours should be ignored when identifying max and min values.&lt;BR&gt;&lt;BR&gt;This error may indicate that the font is corrupted and must be regenerated using a font building tool.</problem>
</item>

<item
    helpID="E1400"
    atom="hhea_E_advanceWidthMax"
    linkTitle="hhea table specification"
    specLink="http://www.microsoft.com/typography/otspec/hhea.htm"
    shortDesc="The advanceWidthMax field does not equal the calculated value"
    fwLinkID="10353"
    tableName="hhea">
    <problem>The value of the advanceWidthMax field should equal the maximum advance width in stored in the hmtx table.</problem>
</item>

<item
    helpID="E1401"
    atom="hhea_E_metricDataFormat"
    linkTitle="hhea table specification"
    specLink="http://www.microsoft.com/typography/otspec/hhea.htm"
    shortDesc="The metricDataFormat field is not set to zero"
    fwLinkID="10353"
    tableName="hhea">
    <problem>Format 0 is the only currently defined format for the metricDataFormat.</problem>
</item>

<item
    helpID="E1402"
    atom="hhea_E_minLeftSideBearing"
    linkTitle="hhea table specification"
    specLink="http://www.microsoft.com/typography/otspec/hhea.htm"
    shortDesc="The minLeftSideBearing field does not equal the calculated value"
    fwLinkID="10353"
    tableName="hhea">
    <problem>The value of the minLeftSideBearing field should equal the minimum left side bearing value listed in the hmtx table for glyphs with contours. Glyphs with no contours should be ignored.</problem>
</item>

<item
    helpID="E1403"
    atom="hhea_E_minRightSideBearing"
    linkTitle="hhea table specification"
    specLink="http://www.microsoft.com/typography/otspec/hhea.htm"
    shortDesc="The minRightSideBearing field does not equal the calculated value"
    fwLinkID="10353"
    tableName="hhea">
    <problem>The value of the minRightSideBearing field should equal Min(aw - lsb - (xMax - xMin)). Only glyphs with contours should be used when making this calculation. Glyphs with no contours should be ignored.</problem>
</item>

<item
    helpID="E1404"
    atom="hhea_E_numberOfHMetrics"
    linkTitle="hhea table specification"
    specLink="http://www.microsoft.com/typography/otspec/hhea.htm"
    shortDesc="The numberOfHMetrics value is not consistent with the length of the hmtx table"
    fwLinkID="10353"
    tableName="hhea">
    <problem>The numberOfHMetrics field must have a value that reflects the number of HMetric entries in the hmtx table. An HMetric entry consists of paired advance width and left side bearing values for a glyph. If the font is monospaced, Microsoft recommends that there be three long-metric entries in the hmtx table, followed by the short metric (lsb) entries. The last long-metric entry in the hmtx table applies to all subsequent glyphs.&lt;BR&gt;&lt;BR&gt;Ensure that the tool you are using is updating the value in the hhea table after compressing entries from long-metrics format to short-metrics.</problem>
</item>

<item
    helpID="E1405"
    atom="hhea_E_reserved1"
    linkTitle="hhea table specification"
    specLink="http://www.microsoft.com/typography/otspec/hhea.htm"
    shortDesc="Reserved field # 1 is non-zero"
    fwLinkID="10353"
    tableName="hhea">
    <problem>This byte is reserved and should have a value of zero.</problem>
</item>

<item
    helpID="E1406"
    atom="hhea_E_reserved2"
    linkTitle="hhea table specification"
    specLink="http://www.microsoft.com/typography/otspec/hhea.htm"
    shortDesc="Reserved field # 2 is non-zero"
    fwLinkID="10353"
    tableName="hhea">
    <problem>This byte is reserved and should have a value of zero.</problem>
</item>

<item
    helpID="E1407"
    atom="hhea_E_reserved3"
    linkTitle="hhea table specification"
    specLink="http://www.microsoft.com/typography/otspec/hhea.htm"
    shortDesc="Reserved field # 3 is non-zero"
    fwLinkID="10353"
    tableName="hhea">
    <problem>This byte is reserved and should have a value of zero.</problem>
</item>

<item
    helpID="E1408"
    atom="hhea_E_reserved4"
    linkTitle="hhea table specification"
    specLink="http://www.microsoft.com/typography/otspec/hhea.htm"
    shortDesc="Reserved field # 4 is non-zero"
    fwLinkID="10353"
    tableName="hhea">
    <problem>This byte is reserved and should have a value of zero.</problem>
</item>

<item
    helpID="E1409"
    atom="hhea_E_version"
    linkTitle="hhea table specification"
    specLink="http://www.microsoft.com/typography/otspec/hhea.htm"
    shortDesc="The table version number is not 0x00010000"
    fwLinkID="10353"
    tableName="hhea">
    <problem>Version 0x00010000 is the only version of the hhea table currently defined. Correct this field using a table editing tool.</problem>
</item>

<item
    helpID="E1410"
    atom="hhea_E_xMaxExtent"
    linkTitle="hhea table specification"
    specLink="http://www.microsoft.com/typography/otspec/hhea.htm"
    shortDesc="The xMaxExtent field does not equal the calculated value"
    fwLinkID="10353"
    tableName="hhea">
    <problem>The value of the xMaxExtent field should equal Max(lsb + (xMax - xMin)). This value should be computed using only glyphs that have contours. Glyphs with no contours should be ignored.</problem>
</item>

<item
    helpID="E1411"
    atom="hhea_E_caretSlopeAngle_italicAngle"
    linkTitle="hhea table specification"
    specLink="WARNING: field missing"
    shortDesc="The caretSlopeRise/caretSlopeRun angle does not match the post.italicAngle"
    fwLinkID="10353"
    tableName="hhea">
    <problem>The angle of the caret should equal the italicAngle of the font so that the insertion point nests well between glyphs. There are cases where these values will not be exactly equal, due to rounding -- but they should be as close as possible. Correct the italicAngle or the caretSlopeRise/Run values to be consistent.</problem>
</item>

<item
    helpID="E1412"
    atom="hhea_E_caretSlopeRunNonZero_italicAngle"
    linkTitle="hhea table specification"
    specLink="WARNING: field missing"
    shortDesc="The caretSlopeRun is nonzero, but the post.italicAngle is zero"
    fwLinkID="10353"
    tableName="hhea">
    <problem>The angle of the caret should equal the italicAngle of the font so that the insertion point nests well between glyphs. There are cases where these values will not be exactly equal, due to rounding -- but they should be as close as possible. Correct the italicAngle or the caretSlopeRise/Run values to be consistent.</problem>
</item>

<item
    helpID="E1413"
    atom="hhea_E_caretSlopeRunZero_italicAngle"
    linkTitle="hhea table specification"
    specLink="WARNING: field missing"
    shortDesc="The caretSlopeRun is zero, but the post.italicAngle is nonzero"
    fwLinkID="10353"
    tableName="hhea">
    <problem>The angle of the caret should equal the italicAngle of the font so that the insertion point nests well between glyphs. There are cases where these values will not be exactly equal, due to rounding -- but they should be as close as possible. Correct the italicAngle or the caretSlopeRise/Run values to be consistent.</problem>
</item>

<item
    helpID="E1414"
    atom="hhea_E_AscenderPositive"
    linkTitle="hhea table specification"
    specLink="WARNING: field missing"
    shortDesc="The Ascender value must be greater than zero"
    fwLinkID="10353"
    tableName="hhea">
    <problem>The Ascender value should be specified as a positive value, representing the distance above the baseline of the highest ascender. The ascender, descender, and linegap values are Apple specific.</problem>
</item>

<item
    helpID="E1415"
    atom="hhea_E_DescenderNegative"
    linkTitle="hhea table specification"
    specLink="WARNING: field missing"
    shortDesc="The Descender value must be less than zero"
    fwLinkID="10353"
    tableName="hhea">
    <problem>The Descender value should be specified as a negative value, representing the distance below the baseline of the lowest descender. The ascender, descender, and linegap values are Apple specific.</problem>
</item>

<item
    helpID="E1500"
    atom="hmtx_E_TableSize"
    linkTitle="hmtx table specification"
    specLink="http://www.microsoft.com/typography/otspec/hmtx.htm"
    shortDesc="The size of the table does not match the calculated size"
    fwLinkID="10354"
    tableName="hmtx">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E1600"
    atom="kern_E_Format0_entrySelector"
    linkTitle="kern table specification"
    specLink="http://www.microsoft.com/typography/otspec/kern.htm"
    shortDesc="The subtable's entrySelector value does not match the calculated value"
    fwLinkID="10357"
    tableName="kern">
    <problem>The entrySelector value, rangeShift value, and searchRange value are used to conduct an efficient binary search of the kerning list. The entrySelector value should equal log2(largest power of two&amp;LT;=the number of kerning pair entries).</problem>
</item>

<item
    helpID="E1601"
    atom="kern_E_Format0_rangeShift"
    linkTitle="kern table specification"
    specLink="http://www.microsoft.com/typography/otspec/kern.htm"
    shortDesc="The subtable's rangeShift value does not match the calculated value"
    fwLinkID="10357"
    tableName="kern">
    <problem>The entrySelector value, rangeShift value, and searchRange value are used to conduct an efficient binary search of the kerning list. The rangeShift value should equal (the number of kerning pair entries)-(largest power of 2&amp;LT;=(the number of kerning pair entries)*(size of an entry in bytes).</problem>
</item>

<item
    helpID="E1602"
    atom="kern_E_Format0_searchRange"
    linkTitle="kern table specification"
    specLink="http://www.microsoft.com/typography/otspec/kern.htm"
    shortDesc="The subtable's searchRange value does not match the calculated value"
    fwLinkID="10357"
    tableName="kern">
    <problem>The entrySelector value, rangeShift value, and searchRange value are used to conduct an efficient binary search of the kerning list. The searchRange should equal the largest power of 2&amp;LT;=(the number of kerning pair entries)*(size of an entry in bytes).</problem>
</item>

<item
    helpID="E1603"
    atom="kern_E_NumSubTables"
    linkTitle="kern table specification"
    specLink="http://www.microsoft.com/typography/otspec/kern.htm"
    shortDesc="The number of subtables is 0"
    fwLinkID="10357"
    tableName="kern">
    <problem>The kern table should contain a single kerning pair subtable, using format 0 or 2. Format 2 is not supported by Windows. If more than one subtable is used, Windows will only use the first format 0 subtable found.</problem>
</item>

<item
    helpID="E1604"
    atom="kern_E_ReservedCoverageBits"
    linkTitle="kern table specification"
    specLink="http://www.microsoft.com/typography/otspec/kern.htm"
    shortDesc="A subtable has reserved coverage bits that are set"
    fwLinkID="10357"
    tableName="kern">
    <problem>Bits 4-7 of the coverage field are reserved and should all be set to 0.</problem>
</item>

<item
    helpID="E1605"
    atom="kern_E_SubtableFormats"
    linkTitle="kern table specification"
    specLink="http://www.microsoft.com/typography/otspec/kern.htm"
    shortDesc="A subtable was found which was not 0 or 2"
    fwLinkID="10357"
    tableName="kern">
    <problem>The kern table should contain a single kerning pair subtable, using either format 0 or format 2 (signifying two-dimensional array of kern values by class). Windows supports only format 0 of the kern table. Use a kern editing tool to properly create the kern table.</problem>
</item>

<item
    helpID="E1606"
    atom="kern_E_SubtableLength"
    linkTitle="kern table specification"
    specLink="http://www.microsoft.com/typography/otspec/kern.htm"
    shortDesc="The subtable's length did not match the calculated length"
    fwLinkID="10357"
    tableName="kern">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E1607"
    atom="kern_E_TableVersion"
    linkTitle="kern table specification"
    specLink="http://www.microsoft.com/typography/otspec/kern.htm"
    shortDesc="The table version was not 0"
    fwLinkID="10357"
    tableName="kern">
    <problem>Version 0 is the only version of the kern table currently defined. Correct this field using a table editing tool, or a kern editor that creates a valid kern table.</problem>
</item>

<item
    helpID="E1608"
    atom="kern_E_SubTableExtendsPastEOT"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The subtable extends past the end of the table"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="E1609"
    atom="kern_E_Format0_GlyphIDs"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="A glyph id is invalid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="E1610"
    atom="kern_E_Format0_Values"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The kerning value is invalid "
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="E1611"
    atom="kern_E_Format0_GlyphIdInCmap"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="A kern pair has a glyph ID that is not mapped in the cmap table"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="E1700"
    atom="loca_E_Format"
    linkTitle="loca table specification"
    specLink="http://www.microsoft.com/typography/otspec/loca.htm"
    shortDesc="Incorrect format of loca"
    fwLinkID="10358"
    tableName="loca">
    <problem>There are two defined formats for the loca table: using short offsets (0) and using long offsets (1). This format value is stored in the head table in the indexToLocFormat field. This error will be reported if this field does not equal 0 or 1.</problem>
</item>

<item
    helpID="E1701"
    atom="loca_E_NumEntries"
    linkTitle="loca table specification"
    specLink="http://www.microsoft.com/typography/otspec/loca.htm"
    shortDesc="The number of entries is not equal (maxp.numGlyphs + 1)"
    fwLinkID="10358"
    tableName="loca">
    <problem>The number of entries in the loca table should be the same as the number of glyphs specified in the maxp table, +1 (In order to compute the length of the last glyph element, there is an extra entry after the last valid index.)&lt;BR&gt;&lt;BR&gt;Regenerate the loca table with an outline editing tool.</problem>
</item>

<item
    helpID="E1702"
    atom="loca_E_OffsetsIncreasing"
    linkTitle="loca table specification"
    specLink="http://www.microsoft.com/typography/otspec/loca.htm"
    shortDesc="The entries are not sorted in ascending order"
    fwLinkID="10358"
    tableName="loca">
    <problem>The offsets to the locations of the glyphs in the font should be sorted in ascending order. These offset values are relative to the beginning of the glyphData table.</problem>
</item>

<item
    helpID="E1703"
    atom="loca_E_OffsetWithinGlyfRange"
    linkTitle="loca table specification"
    specLink="http://www.microsoft.com/typography/otspec/loca.htm"
    shortDesc="Loca entry points outside the glyf range"
    fwLinkID="10358"
    tableName="loca">
    <problem>There is an entry in the loca table that points outside the range(s) of glyf data. This may happen if the loca table has not been updated to reflect the removal of the final glyph(s) from a font.</problem>
</item>

<item
    helpID="E1800"
    atom="LTSH_E_numGlyphs"
    linkTitle="LTSH table specification"
    specLink="http://www.microsoft.com/typography/otspec/LTSH.htm"
    shortDesc="The numGlyphs field does not equal maxp.numGlyphs"
    fwLinkID="10359"
    tableName="LTSH">
    <problem>Recreate the LTSH table so that the numGlyphs value equals the number of glyphs specified in the maxp table, and that there are yPel values defined for every glyph in the font. The yPel value specifies the ppem for each glyph at which the scaling becomes linear</problem>
</item>

<item
    helpID="E1801"
    atom="LTSH_E_Rasterizer"
    linkTitle="LTSH table specification"
    specLink="http://www.microsoft.com/typography/otspec/LTSH.htm"
    shortDesc="The LTSH yPel values can't be validated due to an error while rasterizing the glyphs, likely a hinting instruction error"
    fwLinkID="10359"
    tableName="LTSH">
    <problem>Metrics affected by hints can only be validated at runtime. Therefore, this error is typically generated when the Font Validator uses the rasterizer to execute the hinting instructions contained in the font. The detail of this error message may or may not refer to the glyph that is associated with the bad hinting code, depending on how the overflow or other rasterizing error was encountered. For example, in the case of a stack overflow, the problem may be due to hinting instructions for a previous glyph not having been properly removed from the stack. To perform detailed checks of hinting instructions, select rasterization testing in the Font Validator, or use a tool such as Microsoft's Flint or VTT.</problem>
</item>

<item
    helpID="E1802"
    atom="LTSH_E_TableLength"
    linkTitle="LTSH table specification"
    specLink="http://www.microsoft.com/typography/otspec/LTSH.htm"
    shortDesc="The calculated table length does not match the actual table length"
    fwLinkID="10359"
    tableName="LTSH">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E1803"
    atom="LTSH_E_version"
    linkTitle="LTSH table specification"
    specLink="http://www.microsoft.com/typography/otspec/LTSH.htm"
    shortDesc="The version number is not 0"
    fwLinkID="10359"
    tableName="LTSH">
    <problem>Version 0 is the only version of the LTSH table currently defined. Correct this field using a table editing tool, or use a tool such as CacheTT that calculates LTSH values and creates this table properly.</problem>
</item>

<item
    helpID="E1804"
    atom="LTSH_E_yPels"
    linkTitle="LTSH table specification"
    specLink="http://www.microsoft.com/typography/otspec/LTSH.htm"
    shortDesc="The LTSH yPel value doesn't match the calculated value"
    fwLinkID="10359"
    tableName="LTSH">
    <problem>The yPel value, the ppem for each glyph at which the scaling becomes linear, does not match the value calculated by the current version of the rasterizer. These values may not match if the LTSH table was generated using a previous version of the rasterizer, or another tool that performs the yPel calculations differently. To make the values match, use the latest version of CacheTT to calculate the cached values using the current rasterizer. However, you may not want to change these values if there are concerns about the way text in legacy documents might reflow.</problem>
</item>

<item
    helpID="E1900"
    atom="maxp_E_Calculation"
    linkTitle="maxp table specification"
    specLink="http://www.microsoft.com/typography/otspec/maxp.htm"
    shortDesc="The value doesn't match the calculated value"
    fwLinkID="10360"
    tableName="maxp">
    <problem>The discrepancy noted in this warning message can be corrected by a font hinting tool or font editing tool that automatically builds the maxp table. Although many of the maxp values will be blank in unhinted fonts, the full table is still required.</problem>
</item>

<item
    helpID="E1901"
    atom="maxp_E_LENGTH_0_5"
    linkTitle="maxp table specification"
    specLink="http://www.microsoft.com/typography/otspec/maxp.htm"
    shortDesc="Table version is 0x00005000 but the table is not 6 bytes long"
    fwLinkID="10360"
    tableName="maxp">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E1902"
    atom="maxp_E_LENGTH_1_0"
    linkTitle="maxp table specification"
    specLink="http://www.microsoft.com/typography/otspec/maxp.htm"
    shortDesc="Table version is 1.0 but the table is not 32 bytes long"
    fwLinkID="10360"
    tableName="maxp">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E1903"
    atom="maxp_E_NumGlyphsMatchLoca"
    linkTitle="maxp table specification"
    specLink="http://www.microsoft.com/typography/otspec/maxp.htm"
    shortDesc="The numGlyphs value doesn't match the number of entries in the loca array"
    fwLinkID="10360"
    tableName="maxp">
    <problem>The number of entries in the loca table should be the same as the number of glyphs specified in the maxp table, +1 (In order to compute the length of the last glyph element, there is an extra entry after the last valid index.)&lt;BR&gt;&lt;BR&gt;Regenerate the loca table with an outline editing tool.</problem>
</item>

<item
    helpID="E1904"
    atom="maxp_E_VERSION_0_5_glyf"
    linkTitle="maxp table specification"
    specLink="http://www.microsoft.com/typography/otspec/maxp.htm"
    shortDesc="Table version is 0x00005000 but font contains a glyf table"
    fwLinkID="10360"
    tableName="maxp">
    <problem>Version 0x00005000 of the maxp table is used only for fonts containing CFF data stored in the CFF table, not TrueType outlines stored in a glyf table. Either remove the CFF data in the font and change the version to 0x00010000, or remove the glyf table and keep the version number as is. Correct this field using a table editing tool. Note that Microsoft requires that only one outline format be stored in a font.</problem>
</item>

<item
    helpID="E1905"
    atom="maxp_E_VERSION_0_5_NOCFF"
    linkTitle="maxp table specification"
    specLink="http://www.microsoft.com/typography/otspec/maxp.htm"
    shortDesc="Table version is 0x00005000 but font does not contain the required CFF table"
    fwLinkID="10360"
    tableName="maxp">
    <problem>Version 0x00005000 of the maxp table is used only for fonts containing CFF data stored in the CFF table, not TrueType outlines stored in a glyf table. Either add the CFF data in the font and leave the version number as is or change the version number to 0x00010000 to reflect the presence of the glyf table (with TrueType outlines). Correct this field using a table editing tool. Note that Microsoft requires that only one outline format be stored in a font.</problem>
</item>

<item
    helpID="E1906"
    atom="maxp_E_VERSION_1_0_CFF"
    linkTitle="maxp table specification"
    specLink="http://www.microsoft.com/typography/otspec/maxp.htm"
    shortDesc="Table version is 1.0 but font contains a CFF table"
    fwLinkID="10360"
    tableName="maxp">
    <problem>Version 0x00010000 of the maxp table is used only for fonts containing TrueType outlines stored in a glyf table, not for fonts containing CFF data in a CFF table. Either remove the CFF data in the font and change and leave the version as is, or remove the glyf table and change the version number to 0x00005000. Correct this field using a table editing tool. Note that Microsoft requires that only one outline format be stored in a font.</problem>
</item>

<item
    helpID="E1907"
    atom="maxp_E_VERSION_1_0_NOglyf"
    linkTitle="maxp table specification"
    specLink="http://www.microsoft.com/typography/otspec/maxp.htm"
    shortDesc="Table version is 1.0 but font does not contain the required glyf table"
    fwLinkID="10360"
    tableName="maxp">
    <problem>Version 0x00010000 of the maxp table is used only for fonts containing TrueType outlines stored in a glyf table, not for fonts containing CFF data in a CFF table. Either add a glyf table to the font and keep the version number as is, or change the version number to 0x00005000 to reflect the presence of CFF data in the font. Correct this field using a table editing tool. Note that Microsoft requires that only one outline format be stored in a font.</problem>
</item>

<item
    helpID="E1908"
    atom="maxp_E_VERSION_INVALID"
    linkTitle="maxp table specification"
    specLink="http://www.microsoft.com/typography/otspec/maxp.htm"
    shortDesc="Table version must be either 0x00005000 or 0x00010000"
    fwLinkID="10360"
    tableName="maxp">
    <problem>Version 0x00005000 and Version 0x00010000 are the only two versions of the maxp table currently defined. Version 0x00005000 indicates a font file containing CFF data stored in a CFF table; Version 0x00010000 indicates a font file containing TrueType outline data in a glyf table. Note that Microsoft requires that only one type of outline data be used in each font.</problem>
</item>

<item
    helpID="E2000"
    atom="name_E_FormatSelector"
    linkTitle="name table specification"
    specLink="http://www.microsoft.com/typography/otspec/name.htm"
    shortDesc="The format selector field is not 0"
    fwLinkID="10361"
    tableName="name">
    <problem>0 is the only specified value for the format field.</problem>
</item>

<item
    helpID="E2001"
    atom="name_E_MSLanguageID"
    linkTitle="name table specification"
    specLink="http://www.microsoft.com/typography/otspec/name.htm"
    shortDesc="The Language ID is not valid"
    fwLinkID="10361"
    tableName="name">
    <problem>The Locale (Language) ID used within one or more NameRecords is not a currently specified Locale ID. For a complete list of Locale ID's, see the &lt;A TARGET=&quot;top&quot; HREF=&quot;http://go.microsoft.com/fwlink?LinkID=10461&quot;&gt;Locale ID chart.&lt;/A&gt;</problem>
</item>

<item
    helpID="E2002"
    atom="name_E_NameRecordsSorted"
    linkTitle="name table specification"
    specLink="http://www.microsoft.com/typography/otspec/name.htm"
    shortDesc="The NameRecords array is not in sorted order"
    fwLinkID="10361"
    tableName="name">
    <problem>The NameRecords array must be sorted by platform ID, then platform-specific ID, then language ID, and then by name.</problem>
</item>

<item
    helpID="E2003"
    atom="name_E_NoMacPlatform"
    linkTitle="name table specification"
    specLink="http://www.microsoft.com/typography/otspec/name.htm"
    shortDesc="The table doesn't contain strings for Mac platform"
    fwLinkID="10361"
    tableName="name">
    <problem>Name strings are required for both platforms. Use a table editing tool to add name strings for Windows.</problem>
</item>

<item
    helpID="E2004"
    atom="name_E_NoMSPlatform"
    linkTitle="name table specification"
    specLink="http://www.microsoft.com/typography/otspec/name.htm"
    shortDesc="The table doesn't contain strings for Microsoft platform"
    fwLinkID="10361"
    tableName="name">
    <problem>Name strings are required for both platforms. Use a table editing tool to add name strings for Windows.</problem>
</item>

<item
    helpID="E2005"
    atom="name_E_PlatformSpecificEncoding"
    linkTitle="name table specification"
    specLink="http://www.microsoft.com/typography/otspec/name.htm"
    shortDesc="The Platform Specific Encoding ID is out of range"
    fwLinkID="10361"
    tableName="name">
    <problem>For Platform 0 (Unicode) the following Encoding ID's are valid:&lt;BR&gt;&lt;BR&gt;      &lt;TABLE bgColor=#f0f0f0 width=460&gt;
        &lt;TBODY&gt;
        &lt;TR&gt;
          &lt;TD bgColor=#c0c0c0 class=tab width=&quot;10%&quot;&gt;Encoding&amp;nbsp;ID&lt;/TD&gt;
          &lt;TD bgColor=#c0c0c0 class=tab width=&quot;90%&quot;&gt;Description&lt;/TD&gt;&lt;/TR&gt;
        &lt;TR&gt;
          &lt;TD class=tab vAlign=top&gt;0&lt;/TD&gt;
          &lt;TD class=tab vAlign=top&gt;Unicode 1.0 semantics&lt;/TD&gt;&lt;/TR&gt;
        &lt;TR&gt;
          &lt;TD class=tab vAlign=top&gt;1&lt;/TD&gt;
          &lt;TD class=tab vAlign=top&gt;Unicode 1.1 semantics&lt;/TD&gt;&lt;/TR&gt;
        &lt;TR&gt;
          &lt;TD class=tab vAlign=top&gt;2&lt;/TD&gt;
          &lt;TD class=tab vAlign=top&gt;ISO 10646:1993 semantics&lt;/TD&gt;&lt;/TR&gt;
        &lt;TR&gt;
          &lt;TD class=tab vAlign=top&gt;3&lt;/TD&gt;
          &lt;TD class=tab vAlign=top&gt;Unicode 2.0 and onwards semantics, Unicode BMP only.&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;
          &lt;TD class=tab vAlign=top&gt;4&lt;/TD&gt;
          &lt;TD class=tab vAlign=top&gt;Unicode 2.0 and onwards semantics, Unicode full repertoire.&lt;/TD&gt;&lt;/TR&gt;
&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;BR&gt;&lt;BR&gt;For Platform 3 (Microsoft) the following Encoding ID's are valid:&lt;BR&gt;&lt;BR&gt;      &lt;TABLE bgColor=#f0f0f0 width=460&gt;
        &lt;TBODY&gt;
        &lt;TR&gt;
          &lt;TD bgColor=#c0c0c0 class=tab width=&quot;33%&quot;&gt;Platform ID&lt;/TD&gt;
          &lt;TD bgColor=#c0c0c0 class=tab width=&quot;33%&quot;&gt;Encoding ID&lt;/TD&gt;
          &lt;TD bgColor=#c0c0c0 class=tab width=&quot;33%&quot;&gt;Description&lt;/TD&gt;&lt;/TR&gt;
        &lt;TR&gt;
          &lt;TD class=tab vAlign=top&gt;3&lt;/TD&gt;
          &lt;TD class=tab vAlign=top&gt;0&lt;/TD&gt;
          &lt;TD class=tab vAlign=top&gt;Symbol&lt;/TD&gt;&lt;/TR&gt;
        &lt;TR&gt;
          &lt;TD class=tab vAlign=top&gt;3&lt;/TD&gt;
          &lt;TD class=tab vAlign=top&gt;1&lt;/TD&gt;
          &lt;TD class=tab vAlign=top&gt;Unicode BMP only&lt;/TD&gt;&lt;/TR&gt;
        &lt;TR&gt;
          &lt;TD class=tab vAlign=top&gt;3&lt;/TD&gt;
          &lt;TD class=tab vAlign=top&gt;2&lt;/TD&gt;
          &lt;TD class=tab vAlign=top&gt;ShiftJIS&lt;/TD&gt;&lt;/TR&gt;
        &lt;TR&gt;
          &lt;TD class=tab vAlign=top&gt;3&lt;/TD&gt;
          &lt;TD class=tab vAlign=top&gt;3&lt;/TD&gt;
          &lt;TD class=tab vAlign=top&gt;PRC&lt;/TD&gt;&lt;/TR&gt;
        &lt;TR&gt;
          &lt;TD class=tab vAlign=top&gt;3&lt;/TD&gt;
          &lt;TD class=tab vAlign=top&gt;4&lt;/TD&gt;
          &lt;TD class=tab vAlign=top&gt;Big5&lt;/TD&gt;&lt;/TR&gt;
        &lt;TR&gt;
          &lt;TD class=tab vAlign=top&gt;3&lt;/TD&gt;
          &lt;TD class=tab vAlign=top&gt;5&lt;/TD&gt;
          &lt;TD class=tab vAlign=top&gt;Wansung&lt;/TD&gt;&lt;/TR&gt;
        &lt;TR&gt;
          &lt;TD class=tab vAlign=top&gt;3&lt;/TD&gt;
          &lt;TD class=tab vAlign=top&gt;6&lt;/TD&gt;
          &lt;TD class=tab vAlign=top&gt;Johab&lt;/TD&gt;&lt;/TR&gt;
        &lt;TR&gt;
          &lt;TD class=tab vAlign=top&gt;3&lt;/TD&gt;
          &lt;TD class=tab vAlign=top&gt;7&lt;/TD&gt;
          &lt;TD class=tab vAlign=top&gt;Reserved&lt;/TD&gt;&lt;/TR&gt;
        &lt;TR&gt;
          &lt;TD class=tab vAlign=top&gt;3&lt;/TD&gt;
          &lt;TD class=tab vAlign=top&gt;8&lt;/TD&gt;
          &lt;TD class=tab vAlign=top&gt;Reserved&lt;/TD&gt;&lt;/TR&gt;
        &lt;TR&gt;
          &lt;TD class=tab vAlign=top&gt;3&lt;/TD&gt;
          &lt;TD class=tab vAlign=top&gt;9&lt;/TD&gt;
          &lt;TD class=tab vAlign=top&gt;Reserved&lt;/TD&gt;&lt;/TR&gt;
        &lt;TR&gt;
          &lt;TD class=tab vAlign=top&gt;3&lt;/TD&gt;
          &lt;TD class=tab vAlign=top&gt;10&lt;/TD&gt;
          &lt;TD class=tab vAlign=top&gt;Unicode full repertoire&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;</problem>
</item>

<item
    helpID="E2006"
    atom="name_E_Postscript_chars"
    linkTitle="name table specification"
    specLink="http://www.microsoft.com/typography/otspec/name.htm"
    shortDesc="The PostScript string contains an illegal character"
    fwLinkID="10361"
    tableName="name">
    <problem>When translated to ASCII, this name string must contain only characters that are in the printable ASCII subset, codes 33 through 126, except for the 10 characters: '[', ']', '(', ')', '{', '}', '&amp;LT;', '&amp;GT;', '/', '%'.</problem>
</item>

<item
    helpID="E2007"
    atom="name_E_Postscript_length"
    linkTitle="name table specification"
    specLink="http://www.microsoft.com/typography/otspec/name.htm"
    shortDesc="The PostScript string is longer than 63 characters"
    fwLinkID="10361"
    tableName="name">
    <problem>The PostScript name strings may not be longer than 63 characters.</problem>
</item>

<item
    helpID="E2008"
    atom="name_E_Postscript_missing"
    linkTitle="name table specification"
    specLink="http://www.microsoft.com/typography/otspec/name.htm"
    shortDesc="The PostScript string is not present for both required platforms"
    fwLinkID="10361"
    tableName="name">
    <problem>OpenType fonts that include a PostScript name for the font must include names for Platform 1 Encoding 0 (Mac) and Platform 3 Encoding 1 (Microsoft)</problem>
</item>

<item
    helpID="E2009"
    atom="name_E_Postscript_unequal"
    linkTitle="name table specification"
    specLink="http://www.microsoft.com/typography/otspec/name.htm"
    shortDesc="The Mac PostScript string does not match the Microsoft PostScript string"
    fwLinkID="10361"
    tableName="name">
    <problem>OpenType fonts which include a PostScript name (name ID 6) should include both Microsoft and Macintosh PostScript names, as follows:&lt;BR&gt;&lt;BR&gt;

Platform: 1 [Macintosh]; Platform-specific encoding: 0 [Roman]; Language: 0 [English]. 
&lt;BR&gt;&lt;BR&gt;Platform: 3 [Microsoft]; Platform-specific encoding: 1 [Unicode]; Language: 0x409 [English (American)].&lt;BR&gt;&lt;BR&gt;
When translated to ASCII, these two name strings must be identical; no longer than 63 characters; and restricted to the printable ASCII subset, codes 33 through 126, except for the 10 characters: '[', ']', '(', ')', '{', '}', '&amp;LT;', '&amp;GT;', '/', '%'.</problem>
</item>

<item
    helpID="E2010"
    atom="name_E_ReservedNameID"
    linkTitle="name table specification"
    specLink="http://www.microsoft.com/typography/otspec/name.htm"
    shortDesc="A name record is using a reserved Name ID"
    fwLinkID="10361"
    tableName="name">
    <problem>Name ID's 0-20 are pre-defined; Name ID's 21-255, inclusive, are reserved for future standard names; Name ID's 256-32767, inclusive, are reserved for font-specific names such as those referenced by a font's layout features.</problem>
</item>

<item
    helpID="E2011"
    atom="name_E_StringsWithinTable"
    linkTitle="name table specification"
    specLink="http://www.microsoft.com/typography/otspec/name.htm"
    shortDesc="A string extends past the end of the table"
    fwLinkID="10361"
    tableName="name">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E2012"
    atom="name_E_UnicodeLength"
    linkTitle="name table specification"
    specLink="http://www.microsoft.com/typography/otspec/name.htm"
    shortDesc="The length of the unicode string is not an even # of bytes"
    fwLinkID="10361"
    tableName="name">
    <problem>Check that the Platform ID is correctly specified for this name record, or recreate the record using double-byte unicode values.</problem>
</item>

<item
    helpID="E2013"
    atom="name_E_VersionStringFormat"
    linkTitle="name table specification"
    specLink="http://www.microsoft.com/typography/otspec/name.htm"
    shortDesc="The version string is not formatted correctly"
    fwLinkID="10361"
    tableName="name">
    <problem>The version string must contain a number in the following form: one or more digits (0-9) of value less than 65,535, followed by a period, followed by one or more digits of value less than 65,535. Any character other than a digit will terminate the minor number. A character such as &quot;;&quot; is helpful to delineate the number from additional pieces of version information.
The first version number listed in the string as noted can be used by installation software to compare font versions. Note that some installers may require the string to start with the word &quot;Version&quot; followed by a space and then the version number as above.</problem>
</item>

<item
    helpID="E2014"
    atom="name_E_VersionStringNotFound"
    linkTitle="name table specification"
    specLink="http://www.microsoft.com/typography/otspec/name.htm"
    shortDesc="No Microsoft unicode version strings were found"
    fwLinkID="10361"
    tableName="name">
    <problem>Name strings are required for both platforms. Use a table editing tool to add name strings for Windows.</problem>
</item>

<item
    helpID="E2015"
    atom="name_E_sample"
    linkTitle="name table specification"
    specLink="http://www.microsoft.com/typography/otspec/name.htm"
    shortDesc="The sample string contains a character that is not mapped in the font"
    fwLinkID="10361"
    tableName="name">
    <problem>All characters in the sample string must exist in the font. Remove the non-existent character from the sample string.</problem>
</item>

<item
    helpID="E2100"
    atom="OS_2_E_fsSelection_subfamily"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#fss"
    shortDesc="A bit in the fsSelection field doesn't match the name table's font subfamily string"
    fwLinkID="10384"
    tableName="OS/2">
    <problem>There are several places within the font file that the typeface may be characterized as 'Regular,' 

'Bold,' 'Italic,' 'Condensed,' etc. Font designers should encode this information consistently 

throughout the font. Font clients use the information to:&lt;BR&gt;
&lt;UL&gt;
&lt;LI&gt;organize related typefaces into families (i.e., Arial Narrow, Arial, Arial Bold, Arial 

Expanded...)&lt;/LI&gt;
&lt;LI&gt;use appropriate names when enumerating typefaces to the user
&lt;LI&gt;obtain a font from the system according to certain attributes (weight, style, width)&lt;/LI&gt;
&lt;/UL&gt;
The fields related to encoding this information exist in several different tables:
&lt;UL&gt;
&lt;LI&gt;In the name table, Name ID strings (family name, subfamily name, full-font name, preferred 

family grouping, and preferred subfamily grouping)&lt;/LI&gt;
&lt;LI&gt;In the OS/2 table, usWeightClass, usWidthClass, fsSelection, and PANOSE(tm)&lt;/LI&gt;
&lt;LI&gt;In the head table, macStyle bits&lt;/LI&gt;
&lt;/UL&gt;
Correct this data using a table editing tool.&lt;BR&gt;For examples of how to use these various fields, see these &lt;A TARGET=&quot;top&quot;  HREF=&quot;http://go.microsoft.com/fwlink?LinkID=10455&quot;&gt;name string examples&lt;/A&gt;.&lt;BR&gt;</problem>
</item>

<item
    helpID="E2101"
    atom="OS_2_E_fsSelection_undefbits"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#fss"
    shortDesc="There are undefined bits set in fsSelection field"
    fwLinkID="10384"
    tableName="OS/2">
    <problem>Of the 2-byte fsSelection field, only bits 0-6 are defined. All remaining undefined bits must be set to 0.</problem>
</item>

<item
    helpID="E2102"
    atom="OS_2_E_fsTypeReserved"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#fst"
    shortDesc="The fsType field contains reserved bits that are not zero"
    fwLinkID="10385"
    tableName="OS/2">
    <problem>Bits 0, 4-7, and 10-15 of the fsType field are reserved and must be set to 0.</problem>
</item>

<item
    helpID="E2103"
    atom="OS_2_E_Panose_bArmStyle"
    linkTitle="PANOSE specification"
    specLink="http://www.panose.com/hardware/pan2.asp"
    shortDesc="PANOSE(tm) byte 7, ArmStyle &gt; 11"
    fwLinkID="0"
    tableName="OS/2">
    <problem>PANOSE(tm) values are important for font clients that want to substitute a font when a specified font is not reliably available. PANOSE values should be carefully assigned to ensure adequate font mapping. PANOSE values are fully described in the reference noted below.</problem>
</item>

<item
    helpID="E2104"
    atom="OS_2_E_Panose_bContrast"
    linkTitle="PANOSE specification"
    specLink="http://www.panose.com/hardware/pan2.asp"
    shortDesc="PANOSE(tm) byte 5, Contrast &gt; 9"
    fwLinkID="0"
    tableName="OS/2">
    <problem>PANOSE(tm) values are important for font clients that must substitute a font when a specified font is not reliably available. PANOSE values should be carefully assigned to ensure adequate font mapping. PANOSE values are fully described in the reference noted below.</problem>
</item>

<item
    helpID="E2105"
    atom="OS_2_E_Panose_bFamilyType"
    linkTitle="PANOSE specification"
    specLink="http://www.panose.com/hardware/pan2.asp"
    shortDesc="PANOSE(tm) byte 1, FamilyType &gt; 5"
    fwLinkID="0"
    tableName="OS/2">
    <problem>PANOSE(tm) values are important for font clients that must substitute a font when a specified font is not reliably available. PANOSE values should be carefully assigned to ensure adequate font mapping. PANOSE values are fully described in the reference noted below.</problem>
</item>

<item
    helpID="E2106"
    atom="OS_2_E_Panose_bLetterform"
    linkTitle="PANOSE specification"
    specLink="http://www.panose.com/hardware/pan2.asp"
    shortDesc="PANOSE(tm) byte 8, Letterform &gt; 15"
    fwLinkID="0"
    tableName="OS/2">
    <problem>PANOSE(tm) values are important for font clients that must substitute a font when a specified font is not reliably available. PANOSE values should be carefully assigned to ensure adequate font mapping. PANOSE values are fully described in the reference noted below.</problem>
</item>

<item
    helpID="E2107"
    atom="OS_2_E_Panose_bMidline"
    linkTitle="PANOSE specification"
    specLink="http://www.panose.com/hardware/pan2.asp"
    shortDesc="PANOSE(tm) byte 9, Midline &gt; 13"
    fwLinkID="0"
    tableName="OS/2">
    <problem>PANOSE(tm) values are important for font clients that must substitute a font when a specified font is not reliably available. PANOSE values should be carefully assigned to ensure adequate font mapping. PANOSE values are fully described in the reference noted below.</problem>
</item>

<item
    helpID="E2108"
    atom="OS_2_E_Panose_bProportion"
    linkTitle="PANOSE specification"
    specLink="http://www.panose.com/hardware/pan2.asp"
    shortDesc="PANOSE(tm) byte 4, Proportion &gt; 9"
    fwLinkID="0"
    tableName="OS/2">
    <problem>PANOSE(tm) values are important for font clients that must substitute a font when a specified font is not reliably available. PANOSE values should be carefully assigned to ensure adequate font mapping. PANOSE values are fully described in the reference noted below.</problem>
</item>

<item
    helpID="E2109"
    atom="OS_2_E_Panose_bSerifStyle"
    linkTitle="PANOSE specification"
    specLink="http://www.panose.com/hardware/pan2.asp"
    shortDesc="PANOSE(tm) byte 2, SerifStyle &gt; 15"
    fwLinkID="0"
    tableName="OS/2">
    <problem>PANOSE(tm) values are important for font clients that must substitute a font when a specified font is not reliably available. PANOSE values should be carefully assigned to ensure adequate font mapping. PANOSE values are fully described in the reference noted below.</problem>
</item>

<item
    helpID="E2110"
    atom="OS_2_E_Panose_bStrokeVariation"
    linkTitle="PANOSE specification"
    specLink="http://www.panose.com/hardware/pan2.asp"
    shortDesc="PANOSE(tm) byte 6, StrokeVariation &gt; 10"
    fwLinkID="0"
    tableName="OS/2">
    <problem>PANOSE(tm) values are important for font clients that must substitute a font when a specified font is not reliably available. PANOSE values should be carefully assigned to ensure adequate font mapping. PANOSE values are fully described in the reference noted below.</problem>
</item>

<item
    helpID="E2111"
    atom="OS_2_E_Panose_bWeight"
    linkTitle="PANOSE specification"
    specLink="http://www.panose.com/hardware/pan2.asp"
    shortDesc="PANOSE(tm) byte 3, Weight &gt; 11"
    fwLinkID="0"
    tableName="OS/2">
    <problem>PANOSE(tm) values are important for font clients that must substitute a font when a specified font is not reliably available. PANOSE values should be carefully assigned to ensure adequate font mapping.  PANOSE values are fully described in the reference noted below.</problem>
</item>

<item
    helpID="E2112"
    atom="OS_2_E_Panose_bXHeight"
    linkTitle="PANOSE specification"
    specLink="http://www.panose.com/hardware/pan2.asp"
    shortDesc="PANOSE(tm) byte 10, XHeight &gt; 7"
    fwLinkID="0"
    tableName="OS/2">
    <problem>PANOSE(tm) values are important for font clients that must substitute a font when a specified font is not reliably available. PANOSE values should be carefully assigned to ensure adequate font mapping. PANOSE values are fully described in the reference noted below.</problem>
</item>

<item
    helpID="E2113"
    atom="OS_2_E_RangeBitSet"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#ur"
    shortDesc="A unicode range was indicated in ulUnicodeRange, but the font has no characters in that range"
    fwLinkID="10397"
    tableName="OS/2">
    <problem>This error may appear if an incorrect unicode range bit was set, or if there has been a change to the characters within the font after the range bit was set. Use a table-editing tool to change the ulUnicodeRange value to reflect the character coverage of the font.</problem>
</item>

<item
    helpID="E2114"
    atom="OS_2_E_reg_bold"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#fss"
    shortDesc="The fsSelection field has both the Regular and Bold bits set"
    fwLinkID="10384"
    tableName="OS/2">
    <problem>If bit 6 is set, indicating standard weight/style for the font, then bits 0-5 must be clear. Otherwise, the behavior of the font is undefined.</problem>
</item>

<item
    helpID="E2115"
    atom="OS_2_E_reg_ital"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#fss"
    shortDesc="The fsSelection field has both the Regular and Italic bits set"
    fwLinkID="10384"
    tableName="OS/2">
    <problem>If bit 6 is set, indicating standard weight/style for the font, then bits 0-5 must be clear. Otherwise, the behavior of the font is undefined.</problem>
</item>

<item
    helpID="E2116"
    atom="OS_2_E_ReservedBitSet_CodePage"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#cpr"
    shortDesc="A reserved bit is set in a ulCodePageRange field"
    fwLinkID="10381"
    tableName="OS/2">
    <problem>The following bits in the ulCodePageRange field are reserved and must be set to 0: bits 9-15, 22-28, 32-47</problem>
</item>

<item
    helpID="E2117"
    atom="OS_2_E_ReservedBitSet_Unicode"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#ur"
    shortDesc="A reserved bit is set in a ulUnicodeRange field"
    fwLinkID="10397"
    tableName="OS/2">
    <problem>The following bits in the ulUnicodeRange field are reserved and must be set to 0: bits 8, 12, 14, 27, 58, 84-127.</problem>
</item>

<item
    helpID="E2118"
    atom="OS_2_E_sCapHeight"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#ch"
    shortDesc="The sCapHeight field is zero, but the U+0048 character is mapped to a glyf"
    fwLinkID="10380"
    tableName="OS/2">
    <problem>This sCapHeight field should specify the distance between the baseline and the approximate height of uppercase letters measured in FUnits. This value would normally be specified by a type designer but in situations where that is not possible, for example when a legacy font is being converted, the value may be set equal to the top of the unscaled and unhinted glyph bounding box of the glyph encoded at U+0048 (LATIN CAPITAL LETTER H).&lt;BR&gt;&lt;BR&gt;The field should be set to 0 only if no glyph is encoded in this position.</problem>
</item>

<item
    helpID="E2119"
    atom="OS_2_E_sFamilyClass_classID_reserved"
    linkTitle="IBM font class guidelines"
    specLink="http://www.microsoft.com/typography/otspec/ibmfc.htm"
    shortDesc="sFamilyClass class ID is reserved"
    fwLinkID="10355"
    tableName="OS/2">
    <problem>Class ID's 6, 11, 13, and 14 are reserved for future use.</problem>
</item>

<item
    helpID="E2120"
    atom="OS_2_E_sFamilyClass_ClassID_undefined"
    linkTitle="IBM font class guidelines"
    specLink="http://www.microsoft.com/typography/otspec/ibmfc.htm"
    shortDesc="sFamilyClass class ID is undefined"
    fwLinkID="10355"
    tableName="OS/2">
    <problem>Only Family Class ID's 0 through 14 are defined (with several of those reserved).&lt;BR&gt;&lt;BR&gt;The font class and font subclass are registered values assigned by IBM to each font family. This parameter is intended for use in selecting an alternate font when the requested font is not available. The font class is the most general and the font subclass is the most specific.</problem>
</item>

<item
    helpID="E2121"
    atom="OS_2_E_sFamilyClass_subclassID_undefined"
    linkTitle="IBM font class guidelines"
    specLink="http://www.microsoft.com/typography/otspec/ibmfc.htm"
    shortDesc="sFamilyClass subclass ID is undefined"
    fwLinkID="10355"
    tableName="OS/2">
    <problem>Defined, non-reserved family classes only have subclasses with defined values of 0-15 (with some of those subclasses being reserved).&lt;BR&gt;&lt;BR&gt;The font class and font subclass are registered values assigned by IBM to each font family. This parameter is intended for use in selecting an alternate font when the requested font is not available. The font class is the most general and the font subclass is the most specific.</problem>
</item>

<item
    helpID="E2122"
    atom="OS_2_E_SurrogatesBitClear"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#ur"
    shortDesc="The surrogates bit (bit #57) is clear in the ulUnicodeRange, but the cmap contains a surrogates encoding"
    fwLinkID="10397"
    tableName="OS/2">
    <problem>The surrogates bit should be set if there is at least one codepoint beyond the Basic Multilingual Plane that is supported by the font.</problem>
</item>

<item
    helpID="E2123"
    atom="OS_2_E_SurrogatesBitSet"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#ur"
    shortDesc="The surrogates bit (bit #57) is set in the ulUnicodeRange, but the cmap doesn't contain a surrogates encoding"
    fwLinkID="10397"
    tableName="OS/2">
    <problem>Setting the surrogates bit implies that there is at least one codepoint beyond the Basic Multilingual Plane that is supported by this font.</problem>
</item>

<item
    helpID="E2124"
    atom="OS_2_E_sxHeight"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#xh"
    shortDesc="The sxHeight field is zero, but the U+0078 character is mapped to a glyf"
    fwLinkID="10401"
    tableName="OS/2">
    <problem>If a glyph is encoded in the position of U+0078 (LATIN SMALL LETTER X), then the sxHeight field should be set equal to the top of the unscaled and unhinted glyph bounding box of the glyph (in FUnits).</problem>
</item>

<item
    helpID="E2125"
    atom="OS_2_E_SymbolBitClear"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#cpr"
    shortDesc="The font contains a 3,0 cmap, but the CodePageRange bit #31 (symbol character set) is clear"
    fwLinkID="10381"
    tableName="OS/2">
    <problem>The CodePageRange bits are used to specify the code pages encompassed by the font file in the 'cmap' subtable for platform 3, encoding ID 1 (Microsoft platform). If the font file is encoding ID 0, then the Symbol Character Set bit (31) should be set.&lt;BR&gt;&lt;BR&gt;If the symbol bit is set, and the font file contains a 'cmap' subtable for platform of 3 and encoding ID of 1, then all of the characters in the Unicode range 0xF000 - 0xF0FF (inclusive) will be used to enumerate the symbol character set. If the bit is not set, any characters present in that range will not be enumerated as a symbol character set.</problem>
</item>

<item
    helpID="E2126"
    atom="OS_2_E_SymbolBitSet"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#cpr"
    shortDesc="The font doesn't contain a 3,0 cmap and doesn't contain characters mapped to the 0xf000-0xf0ff range, but the CodePageRange bit #31 (symbol character set) is set"
    fwLinkID="10381"
    tableName="OS/2">
    <problem>If the symbol bit is set, and the font file contains a 'cmap' subtable for platform of 3 and encoding ID of 1, then all of the characters in the Unicode range 0xF000 - 0xF0FF (inclusive) will be used to enumerate the symbol character set. If the bit is not set, any characters present in that range will not be enumerated as a symbol character set.</problem>
</item>

<item
    helpID="E2127"
    atom="OS_2_E_TableLength"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#ver"
    shortDesc="The table length does not match the expected length for this version"
    fwLinkID="10398"
    tableName="OS/2">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E2128"
    atom="OS_2_E_usBreakChar_notmapped"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#bc"
    shortDesc="The usBreakChar is not mapped to a glyf"
    fwLinkID="10379"
    tableName="OS/2">
    <problem>The break character is used to separate words and justify text. Most fonts specify 'space' as the break character.</problem>
</item>

<item
    helpID="E2129"
    atom="OS_2_E_usDefaultChar_notmapped"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#dc"
    shortDesc="The usDefaultChar field is nonzero, but the character is not mapped to a glyf"
    fwLinkID="10382"
    tableName="OS/2">
    <problem>Whenever a request is made for a character that is not in the font, Windows provides this default character. If the value of this field is zero, glyph ID 0 is to be used for the default character. If the value of this field is non-zero, then the value of the field indicates the Unicode encoding of the glyph that Windows uses as the default character. This specified glyph must exist in the font.</problem>
</item>

<item
    helpID="E2130"
    atom="OS_2_E_usFirstCharIndex"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#fci"
    shortDesc="The usFirstCharIndex is not valid"
    fwLinkID="10383"
    tableName="OS/2">
    <problem>The minimum Unicode index (character code) in this font, according to the cmap subtable for platform ID 3 and platform- specific encoding ID 0 or 1. For most fonts supporting Win-ANSI or other character sets, this value would be 0x0020. This field cannot represent supplementary character values (codepoints greater than 0xFFFF). Fonts that support supplementary characters should set the value in this field to 0xFFFF if the minimum index value is a supplementary character.</problem>
</item>

<item
    helpID="E2131"
    atom="OS_2_E_usLastCharIndex"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#lci"
    shortDesc="The usLastCharIndex is not valid"
    fwLinkID="10386"
    tableName="OS/2">
    <problem>The maximum Unicode index (character code) in this font, according to the cmap subtable for platform ID 3 and encoding ID 0 or 1. This value depends on which character sets the font supports. This field cannot represent supplementary character values (codepoints greater than 0xFFFF). Fonts that support supplementary characters should set the value in this field to 0xFFFF.</problem>
</item>

<item
    helpID="I2131"
    atom="OS_2_I_usLastCharIndex"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#lci"
    shortDesc="The usLastCharIndex is 0xFFFF and a (3.10) cmap is present"
    fwLinkID="10386"
    tableName="OS/2">
    <problem>The maximum Unicode index (character code) in this font, according to the cmap subtable for platform ID 3 and encoding ID 0 or 1. This value depends on which character sets the font supports. This field cannot represent supplementary character values (codepoints greater than 0xFFFF). Fonts that support supplementary characters should set the value in this field to 0xFFFF.</problem>
</item>

<item
    helpID="E2132"
    atom="OS_2_E_Version"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#ver"
    shortDesc="The version number is invalid"
    fwLinkID="10398"
    tableName="OS/2">
    <problem>The current version of the OS/2 table is Version 3. Versions zero (0, TrueType rev 1.5), one (1, TrueType rev 1.66), and two (2, OpenType rev 1.2) have been used previously.</problem>
</item>

<item
    helpID="E2133"
    atom="OS_2_E_WeightClass"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#wtc"
    shortDesc="The usWeightClass is not a valid value"
    fwLinkID="10400"
    tableName="OS/2">
    <problem>The usWeightClass field indicates the visual weight of the characters in the font. Values may range from 100 (Thin) to 900 (Black), in increments of 100. The usWeightClass is used by the system to obtain a font when an application requests a font with a specified weight class (through the CreateFont API).&lt;BR&gt;There are several places within the font file that the typeface may be characterized as 'Regular,' 

'Bold,' 'Italic,' 'Condensed,' etc. Font designers should encode this information consistently 

throughout the font. Font clients use the information to:&lt;BR&gt;
&lt;UL&gt;
&lt;LI&gt;organize related typefaces into families (i.e., Arial Narrow, Arial, Arial Bold, Arial 

Expanded...)&lt;/LI&gt;
&lt;LI&gt;use appropriate names when enumerating typefaces to the user
&lt;LI&gt;obtain a font from the system according to certain attributes (weight, style, width)&lt;/LI&gt;
&lt;/UL&gt;
The fields related to encoding this information exist in several different tables:
&lt;UL&gt;
&lt;LI&gt;In the name table, Name ID strings (family name, subfamily name, full-font name, preferred 

family grouping, and preferred subfamily grouping)&lt;/LI&gt;
&lt;LI&gt;In the OS/2 table, usWeightClass, usWidthClass, fsSelection, and PANOSE(tm)&lt;/LI&gt;
&lt;LI&gt;In the head table, macStyle bits&lt;/LI&gt;
&lt;/UL&gt;
Correct this data using a table editing tool.&lt;BR&gt;For examples of how to use these various fields, see these &lt;A TARGET=&quot;top&quot;  HREF=&quot;http://go.microsoft.com/fwlink?LinkID=10455&quot;&gt;name string examples&lt;/A&gt;.&lt;BR&gt;</problem>
</item>

<item
    helpID="E2134"
    atom="OS_2_E_WidthClass"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#wdc"
    shortDesc="The width class is not a valid value"
    fwLinkID="10399"
    tableName="OS/2">
    <problem>The usWidthClass field indicates the relative change from the normal aspect ratio for the glyphs in a font. Values range from 1 (Ultra-condensed or 50% of normal) to 9 (Ultra-expanded or 200% of normal).  The usWidthClass is used by the system to obtain a font when an application requests a font with a specified width class (through the CreateFont API).&lt;BR&gt;There are several places within the font file that the typeface may be characterized as 'Regular,' 

'Bold,' 'Italic,' 'Condensed,' etc. Font designers should encode this information consistently 

throughout the font. Font clients use the information to:&lt;BR&gt;
&lt;UL&gt;
&lt;LI&gt;organize related typefaces into families (i.e., Arial Narrow, Arial, Arial Bold, Arial 

Expanded...)&lt;/LI&gt;
&lt;LI&gt;use appropriate names when enumerating typefaces to the user
&lt;LI&gt;obtain a font from the system according to certain attributes (weight, style, width)&lt;/LI&gt;
&lt;/UL&gt;
The fields related to encoding this information exist in several different tables:
&lt;UL&gt;
&lt;LI&gt;In the name table, Name ID strings (family name, subfamily name, full-font name, preferred 

family grouping, and preferred subfamily grouping)&lt;/LI&gt;
&lt;LI&gt;In the OS/2 table, usWeightClass, usWidthClass, fsSelection, and PANOSE(tm)&lt;/LI&gt;
&lt;LI&gt;In the head table, macStyle bits&lt;/LI&gt;
&lt;/UL&gt;
Correct this data using a table editing tool.&lt;BR&gt;For examples of how to use these various fields, see these &lt;A TARGET=&quot;top&quot;  HREF=&quot;http://go.microsoft.com/fwlink?LinkID=10455&quot;&gt;name string examples&lt;/A&gt;.&lt;BR&gt;</problem>
</item>

<item
    helpID="E2135"
    atom="OS_2_E_xAvgCharWidth"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#acw"
    shortDesc="The xAvgCharWidth field does not equal the calculated value"
    fwLinkID="10378"
    tableName="OS/2">
    <problem>The xAvgCharWidth value for non-symbol fonts specifies the arithmetic average of the width of all the non-zero width glyphs in a font (change per spec version 1.4). For symbol fonts, the xAvgCharWidth should be calculated as the unweighted average of all mapped glyphs, including those with null contours.</problem>
</item>

<item
    helpID="E2139"
    atom="OS_2_E_Panose_FamilyTypeNotSymbol"
    linkTitle="PANOSE specification"
    specLink="http://www.panose.com/hardware/pan2.asp"
    shortDesc="Font is a symbol font, but PANOSE(tm) byte 1, FamilyType, is not set to Latin Symbol"
    fwLinkID="0"
    tableName="OS/2">
    <problem>PANOSE(tm) values are important for font clients that must substitute a font when a specified font is not available. PANOSE values should be carefully assigned to ensure adequate font mapping. PANOSE values are fully described in the reference noted below.</problem>
</item>

<item
    helpID="E2140"
    atom="OS_2_E_Panose_FamilyTypeSymbol"
    linkTitle="PANOSE specification"
    specLink="http://www.panose.com/hardware/pan2.asp"
    shortDesc="Font is a not a symbol font, but PANOSE(tm) byte 1, FamilyType, is set to Latin Symbol"
    fwLinkID="0"
    tableName="OS/2">
    <problem>PANOSE(tm) values are important for font clients that must substitute a font when a specified font is not available. PANOSE values should be carefully assigned to ensure adequate font mapping. PANOSE values are fully described in the reference noted below.</problem>
</item>

<item
    helpID="E2141"
    atom="OS_2_E_Panose_SymbolAspectRatio"
    linkTitle="PANOSE specification"
    specLink="http://www.panose.com/hardware/pan2.asp"
    shortDesc="PANOSE family kind is Latin Symbol, but byte 5, Aspect Ratio and Contrast, does not equal 1"
    fwLinkID="0"
    tableName="OS/2">
    <problem>PANOSE(tm) values are important for font clients that must substitute a font when a specified font is not available. PANOSE values should be carefully assigned to ensure adequate font mapping. PANOSE values are fully described in the reference noted below.</problem>
</item>

<item
    helpID="E2142"
    atom="OS_2_E_Panose_SymbolWeight"
    linkTitle="PANOSE specification"
    specLink="http://www.panose.com/hardware/pan2.asp"
    shortDesc="PANOSE family kind is Latin Symbol, but byte 3, Weight, does not equal 1"
    fwLinkID="0"
    tableName="OS/2">
    <problem>PANOSE(tm) values are important for font clients that must substitute a font when a specified font is not available. PANOSE values should be carefully assigned to ensure adequate font mapping. PANOSE values are fully described in the reference noted below.</problem>
</item>

<item
    helpID="E2143"
    atom="OS_2_E_fsSelection_macStyle_bold"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#fss"
    shortDesc="The fsSelection bold bit is inconsistent with the macStyle bold bit"
    fwLinkID="10384"
    tableName="OS/2">
    <problem>Use a table editing tool to correct either the fsSelection bold bit (bit 5) in the OS/2 table, or the macStyle bold bit (bit 0) in the head table.</problem>
</item>

<item
    helpID="E2144"
    atom="OS_2_E_fsSelection_macStyle_italic"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#fss"
    shortDesc="The fsSelection italic bit is inconsistent with the macStyle italic bit"
    fwLinkID="10384"
    tableName="OS/2">
    <problem>Use a table editing tool to correct either the fsSelection italic bit (bit 0) in the OS/2 table, or the macStyle italic bit (bit 1) in the head table.</problem>
</item>

<item
    helpID="E2145"
    atom="OS_2_E_sTypoAscender_notpositive"
    linkTitle="OS/2 table specification"
    specLink="WARNING: field missing"
    shortDesc="The sTypoAscender value is less than or equal to zero"
    fwLinkID="11802"
    tableName="OS/2">
    <problem>The sTypoAscender value is used to determine the optimum offset from the top of a text frame to the first baseline. The sTypoDescender value should be greater than zero, and the value of (sTypoAscender - sTypoDescender) is recommended to equal one em. To learn more about this value, see the &lt;A TARGET=&quot;top&quot; HREF=&quot;http://go.microsoft.com/fwlink?LinkID=10367&quot;&gt;Recommendations for OpenType Fonts.&lt;/A&gt;</problem>
</item>

<item
    helpID="E2146"
    atom="OS_2_E_sTypoDescender_positive"
    linkTitle="OS/2 table specification"
    specLink="WARNING: field missing"
    shortDesc="The sTypoDescender value is greater than zero"
    fwLinkID="11803"
    tableName="OS/2">
    <problem>The sTypoDescender value is used to determine the optimum offset from the last baseline to the bottom of the text frame. The sTypoDescender value should be negative, and the value of (sTypoAscender - sTypoDescender) is recommended to equal one em. To learn more about this value, see the &lt;A TARGET=&quot;top&quot; HREF=&quot;http://go.microsoft.com/fwlink?LinkID=10367&quot;&gt;Recommendations for OpenType Fonts.&lt;/A&gt;</problem>
</item>

<item
    helpID="E2147"
    atom="OS_2_E_fsTypeExclusiveBits"
    linkTitle="OS/2 table specification"
    specLink="WARNING: field missing"
    shortDesc="The fsType field has mutually exclusive bits set"
    fwLinkID="10385"
    tableName="OS/2">
    <problem>The following bits are mutually exclusive:&lt;BR&gt;0x0002, Restricted License embedding&lt;BR&gt;0x0004, Preview and Print embedding&lt;BR&gt;0x0008, Editable embedding</problem>
</item>

<item
    helpID="E2148"
    atom="OS_2_E_usMaxContext"
    linkTitle="OS/2 table specification"
    specLink="WARNING: field missing"
    shortDesc="The usMaxContext field doesn't match the calculated value"
    fwLinkID="13002"
    tableName="OS/2">
    <problem>This field should represent the maximum length of a target glyph context for any feature in the font. For example, if the font has a ligature feature in which the glyph sequence 'f f i' is substituted by the ligature 'ffi', then this field should be set to 3. For chaining contextual lookups, the length of the string (covered glyph) + (input sequence) + (lookahead sequence) should be considered.</problem>
</item>

<item
    helpID="E2200"
    atom="PCLT_E_Bottom6"
    linkTitle="PCLT table specification"
    specLink="http://www.microsoft.com/typography/otspec/pclt.htm"
    shortDesc="The SerifStyle bottom 6 bit value is invalid"
    fwLinkID="10364"
    tableName="PCLT">
    <problem>The SerifStyle bottom 6 bit values may equal the following. Correct this value using a table editing tool. &lt;TABLE WIDTH=460 BGCOLOR=&quot;#F0F0F0&quot;&gt;
&lt;TR&gt;&lt;/TD&gt;
&lt;TD CLASS=tab WIDTH=20% VALIGN=TOP&gt;0&lt;/TD&gt;
&lt;TD CLASS=tab WIDTH=80% VALIGN=TOP&gt;Sans Serif Square&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;1&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;Sans Serif Round&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;2&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;Serif Line&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;3&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;Serif Triangle&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;4&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;Serif Swath&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;5&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;Serif Block&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;6&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;Serif Bracket&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;7&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;Rounded Bracket&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;8&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;Flair Serif, Modified Sans&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;9&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;Script Nonconnecting&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;10&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;Script Joining&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;11&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;Script Calligraphic&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;12&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;Script Broken Letter&lt;/TD&gt;&lt;/TR&gt;
&lt;/TABLE&gt;</problem>
</item>

<item
    helpID="E2201"
    atom="PCLT_E_Pitch"
    linkTitle="PCLT table specification"
    specLink="http://www.microsoft.com/typography/otspec/pclt.htm"
    shortDesc="The Pitch field does not equal the width of the space character"
    fwLinkID="10364"
    tableName="PCLT">
    <problem>The Pitch value in the PCLT table should be the same as the space character in FUnits (as described by the unitsPerEm field of the 'head' table).</problem>
</item>

<item
    helpID="E2202"
    atom="PCLT_E_Reserved"
    linkTitle="PCLT table specification"
    specLink="http://www.microsoft.com/typography/otspec/pclt.htm"
    shortDesc="The Reserved field is not zero"
    fwLinkID="10364"
    tableName="PCLT">
    <problem>The last byte of the PCLT table is reserved for padding, and should be set to zero.</problem>
</item>

<item
    helpID="E2203"
    atom="PCLT_E_StrokeWeight"
    linkTitle="PCLT table specification"
    specLink="http://www.microsoft.com/typography/otspec/pclt.htm"
    shortDesc="The StrokeWeight value was not in the range of -7 to 7"
    fwLinkID="10364"
    tableName="PCLT">
    <problem>For the StrokeWeight field, only values in the range of -7 (Ultra Thin) to 7 (Ultra Black) are valid.</problem>
</item>

<item
    helpID="E2204"
    atom="PCLT_E_Style_Posture"
    linkTitle="PCLT table specification"
    specLink="http://www.microsoft.com/typography/otspec/pclt.htm"
    shortDesc="The Style Posture bits have a reserved value of 3"
    fwLinkID="10364"
    tableName="PCLT">
    <problem>Bits 0-1 of the Style field are used to encode Posture, with the values signifying: 0 - upright; 1 - italic/oblique; 2 - alternate italic. These bits should not be set to indicate a value of 3, as this value is reserved.</problem>
</item>

<item
    helpID="E2205"
    atom="PCLT_E_Style_Reserved"
    linkTitle="PCLT table specification"
    specLink="http://www.microsoft.com/typography/otspec/pclt.htm"
    shortDesc="The Style field has non zero bits in the most significant 6 bits"
    fwLinkID="10364"
    tableName="PCLT">
    <problem>The most significant 6 bits of the Style field are reserved and must indicate a value of zero.</problem>
</item>

<item
    helpID="E2206"
    atom="PCLT_E_Style_Structure"
    linkTitle="PCLT table specification"
    specLink="http://www.microsoft.com/typography/otspec/pclt.htm"
    shortDesc="The Style Structure bits are in the reserved range of 18 to 31"
    fwLinkID="10364"
    tableName="PCLT">
    <problem>Bits 5-9 of the Style field are used to encode Structure. Only values 0-17 may be encoded in these bits; values 18-31 are reserved.</problem>
</item>

<item
    helpID="E2207"
    atom="PCLT_E_Style_Width"
    linkTitle="PCLT table specification"
    specLink="http://www.microsoft.com/typography/otspec/pclt.htm"
    shortDesc="The Style Width bits have a reserved value of 5"
    fwLinkID="10364"
    tableName="PCLT">
    <problem>Bits 2-4 of the Style field are used to encode Width. With the exception of reserved value 5, these bits may be used to encode values 0-7.</problem>
</item>

<item
    helpID="E2208"
    atom="PCLT_E_TableLength"
    linkTitle="PCLT table specification"
    specLink="http://www.microsoft.com/typography/otspec/pclt.htm"
    shortDesc="The table length is not 54 bytes"
    fwLinkID="10364"
    tableName="PCLT">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E2209"
    atom="PCLT_E_Top2"
    linkTitle="PCLT table specification"
    specLink="http://www.microsoft.com/typography/otspec/pclt.htm"
    shortDesc="The SerifStyle top 2 bit value is invalid"
    fwLinkID="10364"
    tableName="PCLT">
    <problem>The most significant two bits of the serifStyle byte specify the serif/sans or contrast/monoline characterisitics of the typeface. The bits may have the following values:&lt;BR&gt;&lt;TABLE WIDTH=460 BGCOLOR=&quot;#F0F0F0&quot;&gt;
&lt;TR&gt;&lt;/TD&gt;
&lt;TD CLASS=tab WIDTH=20% VALIGN=TOP&gt;0&lt;/TD&gt;
&lt;TD CLASS=tab WIDTH=80% VALIGN=TOP&gt;reserved&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;1&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;Sans Serif/Monoline&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;2&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;Serif/Contrasting&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;3&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;reserved&lt;/TD&gt;&lt;/TR&gt;
&lt;/TABLE&gt;
&lt;P&gt;</problem>
</item>

<item
    helpID="E2210"
    atom="PCLT_E_Version"
    linkTitle="PCLT table specification"
    specLink="http://www.microsoft.com/typography/otspec/pclt.htm"
    shortDesc="The version is not 0x00010000"
    fwLinkID="10364"
    tableName="PCLT">
    <problem>Version 0x00010000 is currently the only defined version of the PCLT table.</problem>
</item>

<item
    helpID="E2211"
    atom="PCLT_E_WidthType"
    linkTitle="PCLT table specification"
    specLink="http://www.microsoft.com/typography/otspec/pclt.htm"
    shortDesc="The WidthType value was not in the range of -5 to 5"
    fwLinkID="10364"
    tableName="PCLT">
    <problem>For the WidthType field, only values in the range -5 (Ultra Compressed) to 5 (Extra Expanded) are valid.</problem>
</item>

<item
    helpID="E2300"
    atom="post_E_glyphNameIndex_range"
    linkTitle="post table specification"
    specLink="http://www.microsoft.com/typography/otspec/post.htm"
    shortDesc="An entry in the glyphNameIndex - 258 is greater than the number of names"
    fwLinkID="10365"
    tableName="post">
    <problem>The glyphNameIndex field should contain a value indicating the ordinal number of the glyph in the post string tables. For values in the range of 258-32767, the number of strings in the post table should equal (glyphNameIndex - 258). Regenerate this font.</problem>
</item>

<item
    helpID="E2301"
    atom="post_E_InvalidTableLen"
    linkTitle="post table specification"
    specLink="http://www.microsoft.com/typography/otspec/post.htm"
    shortDesc="The table length is invalid"
    fwLinkID="10365"
    tableName="post">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E2302"
    atom="post_E_isFixedPitchNonzero_hmtx"
    linkTitle="post table specification"
    specLink="http://www.microsoft.com/typography/otspec/post.htm"
    shortDesc="The isFixedPitch field is nonzero, but hmtx shows the font as proportional"
    fwLinkID="10365"
    tableName="post">
    <problem>Ensure that the designation of fixed-pitch within the font is consistent. Currently, the value for the isFixedPitch in the post table indicates that the font is monospaced, but there are multiple pairs of advance width/left side bearing values in the hmtx table (indicating the font is not fixed pitch). Use a table editing tool to correct value of the isFixedPitch field, or remove all but one pair of metric data from the hmtx table.</problem>
</item>

<item
    helpID="E2303"
    atom="post_E_isFixedPitchNonzero_OS_2"
    linkTitle="post table specification"
    specLink="http://www.microsoft.com/typography/otspec/post.htm"
    shortDesc="The isFixedPitch field != 0, but the OS/2 panose bProportion is not monospace"
    fwLinkID="10365"
    tableName="post">
    <problem>Ensure that the designation of fixed-pitch within the font is consistent. Currently, the value for the isFixedPitch in the post table indicates that the font is monospaced, but the PANOSE bProportion field in the OS/2 table indicates that the font is not monospaced. Use a table editing tool to correct values of the isFixedPitch field and the bProportion field so that they agree.</problem>
</item>

<item
    helpID="E2304"
    atom="post_E_isFixedPitchZero_hmtx"
    linkTitle="post table specification"
    specLink="http://www.microsoft.com/typography/otspec/post.htm"
    shortDesc="The isFixedPitch field is zero, but hmtx shows the font as fixed pitch"
    fwLinkID="10365"
    tableName="post">
    <problem>Ensure that the designation of fixed-pitch within the font is consistent. Currently, the value for the isFixedPitch in the post table indicates that the font is not monospaced, but there is only one pair of advance width/left side bearing values in the hmtx table (indicating the font is fixed pitch). Use a table editing tool to correct value of the isFixedPitch field, or fully populate the hmtx table with metric data.</problem>
</item>

<item
    helpID="E2305"
    atom="post_E_isFixedPitchZero_OS_2"
    linkTitle="post table specification"
    specLink="http://www.microsoft.com/typography/otspec/post.htm"
    shortDesc="The isFixedPitch field is zero, but the OS/2 panose bProportion is monospace"
    fwLinkID="10365"
    tableName="post">
    <problem>Ensure that the designation of fixed-pitch within the font is consistent. Currently, the value for the isFixedPitch in the post table indicates that the font is not monospaced, but the PANOSE bProportion field in the OS/2 table indicates that the font is monospaced. Use a table editing tool to correct values of the isFixedPitch field and the bProportion field so that they agree.</problem>
</item>

<item
    helpID="E2306"
    atom="post_E_italicAngleNonzero_caretSlopeRun"
    linkTitle="post table specification"
    specLink="http://www.microsoft.com/typography/otspec/post.htm"
    shortDesc="The italicAngle is nonzero, but the hhea.caretSlopeRun is zero"
    fwLinkID="10365"
    tableName="post">
    <problem>The current setting of the caretSlopeRun in the hhea table suggests that the font is upright, but the italicAngle value in the post table indicates an italic font. Ensure that italic designation is consistent within the font by making the italicAngle zero, or by setting the caretSlopeRun value in the hhea table to non-zero.</problem>
</item>

<item
    helpID="E2307"
    atom="post_E_italicAngleNonzero_hheaAngle"
    linkTitle="post table specification"
    specLink="http://www.microsoft.com/typography/otspec/post.htm"
    shortDesc="The italicAngle does not match the hhea.caretSlopeRise/hhea.caretSlopeRun angle"
    fwLinkID="10365"
    tableName="post">
    <problem>The angle of the caret should equal the italicAngle of the font so that the insertion point nests well between glyphs. There are cases where these values will not be exactly equal, due to rounding -- but they should be as close as possible. Correct the italicAngle or the caretSlopeRise/Run values to be consistent.</problem>
</item>

<item
    helpID="E2308"
    atom="post_E_italicAngleNonzero_macStyle"
    linkTitle="post table specification"
    specLink="http://www.microsoft.com/typography/otspec/post.htm"
    shortDesc="The italicAngle is nonzero, but the head.macStyle italic bit is not set"
    fwLinkID="10365"
    tableName="post">
    <problem>Ensure that italic designation is consistent within the font. One case where these designations may differ is in the encoding of a font that has a slope, such as a script face. Such a font will have the italicAngle set, but since it is not considered italic within its own family, the italic bit may not be set.&lt;BR&gt;&lt;BR&gt;Use a table editing tool to set the macStyle italic bit (bit 1), or enter zero for the italicAngle in the post table to indicate the font is upright.</problem>
</item>

<item
    helpID="E2309"
    atom="post_E_italicAngleZero_caretSlopeRun"
    linkTitle="post table specification"
    specLink="http://www.microsoft.com/typography/otspec/post.htm"
    shortDesc="The italicAngle is zero, but the hhea.caretSlopeRun is not zero"
    fwLinkID="10365"
    tableName="post">
    <problem>The current setting of the caretSlopeRun in the hhea table suggests that the font is italic, but the italicAngle value in the post table indicates an upright font. Ensure that italic designation is consistent within the font by making the italicAngle non-zero, or by setting the caretSlopeRun value in the hhea table to zero.</problem>
</item>

<item
    helpID="E2310"
    atom="post_E_italicAngleZero_macStyle"
    linkTitle="post table specification"
    specLink="http://www.microsoft.com/typography/otspec/post.htm"
    shortDesc="The italicAngle is zero, but the head.macStyle italic bit is set"
    fwLinkID="10365"
    tableName="post">
    <problem>Ensure that italic designation is consistent within the font. Use a table editing tool to clear the macStyle italic bit (bit 1), or enter a non-zero value for the italicAngle in the post table (negative for text that leans to the right).</problem>
</item>

<item
    helpID="E2311"
    atom="post_E_TableLenNot32"
    linkTitle="post table specification"
    specLink="http://www.microsoft.com/typography/otspec/post.htm"
    shortDesc="The table length is not 32 bytes long"
    fwLinkID="10365"
    tableName="post">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E2312"
    atom="post_E_v2_NameLengthInvalid"
    linkTitle="post table specification"
    specLink="http://www.microsoft.com/typography/otspec/post.htm"
    shortDesc="The post name extends past the end of the table"
    fwLinkID="10365"
    tableName="post">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E2313"
    atom="post_E_v2_NameOffsetInvalid"
    linkTitle="post table specification"
    specLink="http://www.microsoft.com/typography/otspec/post.htm"
    shortDesc="The offset to the post name is invalid"
    fwLinkID="10365"
    tableName="post">
    <problem>In version 2.0 of the post table, the offset to post names is derived from the glyphNameIndex. Although the index for this glyph may be valid, the offset points outside the post table (compared with the size of the post table as defined in the font file header). Recreate the post table.</problem>
</item>

<item
    helpID="E2314"
    atom="post_E_v2_numberOfGlyphs"
    linkTitle="post table specification"
    specLink="http://www.microsoft.com/typography/otspec/post.htm"
    shortDesc="The numberOfGlyphs field does not equal maxp.numGlyphs"
    fwLinkID="10365"
    tableName="post">
    <problem>The numberOfGlyphs field should be the same as the numGlyphs field in the maxp table.</problem>
</item>

<item
    helpID="E2315"
    atom="post_E_Version"
    linkTitle="post table specification"
    specLink="http://www.microsoft.com/typography/otspec/post.htm"
    shortDesc="The version number is invalid"
    fwLinkID="10365"
    tableName="post">
    <problem>The post table has four possible versions: version 1.0 (TrueType-based font file containing 258 glyphs in the standard Macintosh set); version 2.0 (TrueType-based font file, version 2.5 (deprecated as of OpenType Specification v1.3), and version 3.0, used by OpenType fonts with TrueType or CFF data.</problem>
</item>

<item
    helpID="E2500"
    atom="VDMX_E_CalcData"
    linkTitle="VDMX table specification"
    specLink="http://www.microsoft.com/typography/otspec/vdmx.htm"
    shortDesc="The VDMX data doesn't match the data calculated by the rasterizer"
    fwLinkID="10371"
    tableName="VDMX">
    <problem>The VDMX data does not match the value calculated by the current version of the rasterizer. This data may not match if glyphs have been updated but the VDMX table has not been recalculated (using a tool such as Microsoft's CacheTT). The problem may also occur if the VDMX table was generated using a previous version of the rasterizer, or another tool that performs the calculations differently. To correct the data, use the latest version of CacheTT to calculate the cached values using the current rasterizer. However, you may not want to change these values if there are concerns about the way text in legacy documents might reflow.</problem>
</item>

<item
    helpID="E2501"
    atom="VDMX_E_GroupsInTable"
    linkTitle="VDMX table specification"
    specLink="http://www.microsoft.com/typography/otspec/vdmx.htm"
    shortDesc="A VDMX group isn't within the table"
    fwLinkID="10371"
    tableName="VDMX">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E2502"
    atom="VDMX_E_InvalidOffset"
    linkTitle="VDMX table specification"
    specLink="http://www.microsoft.com/typography/otspec/vdmx.htm"
    shortDesc="An offset to a VDMX group is invalid"
    fwLinkID="10371"
    tableName="VDMX">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E2504"
    atom="VDMX_E_Version"
    linkTitle="VDMX table specification"
    specLink="http://www.microsoft.com/typography/otspec/vdmx.htm"
    shortDesc="The version number is not 0 or 1"
    fwLinkID="10371"
    tableName="VDMX">
    <problem>There are currently only two versions of the VDMX table defined: 0 and 1. Microsoft recommends using version 1 of the VDMX table.</problem>
</item>

<item
    helpID="E2505"
    atom="VDMX_E_yPelHeight_illegal"
    linkTitle="VDMX table specification"
    specLink="WARNING: field missing"
    shortDesc="The yPelHeight value is greater than 255"
    fwLinkID="10371"
    tableName="VDMX">
    <problem>YPel Height values in the VDMX table must be in the range of 0..255.</problem>
</item>

<item
    helpID="E2600"
    atom="vhea_E_metricDataFormat"
    linkTitle="vhea table specification"
    specLink="http://www.microsoft.com/typography/otspec/vhea.htm"
    shortDesc="The metricDataFormat field is not set to zero"
    fwLinkID="10372"
    tableName="vhea">
    <problem>Zero is the only allowed value for the metricDataFormat. Use a table editing tool to correct this value.</problem>
</item>

<item
    helpID="E2601"
    atom="vhea_E_ReservedFields"
    linkTitle="vhea table specification"
    specLink="http://www.microsoft.com/typography/otspec/vhea.htm"
    shortDesc="The reserved fields are not all set to zero"
    fwLinkID="10372"
    tableName="vhea">
    <problem>All reserved fields in the vhea table must be set to 0.</problem>
</item>

<item
    helpID="E2602"
    atom="vhea_E_version"
    linkTitle="vhea table specification"
    specLink="http://www.microsoft.com/typography/otspec/vhea.htm"
    shortDesc="The version is not valid"
    fwLinkID="10372"
    tableName="vhea">
    <problem>Two versions of the vhea table are currently defined:&lt;BR&gt;&lt;BR&gt;Version 1.0 (0x00010000) defines ascent as the distance from the centerline to the previous line's descent; descent as the distance from the centerline to the next line's ascent; and lineGap as reserved (0).&lt;BR&gt;&lt;BR&gt;Version 1.1 (0x00011000, note the representation of a non-zero fractional part in Fixed numbers) defines vertTypoAscender, vertTypoDescender, and vertTypoLineGap as functions of the ideographic em-box.</problem>
</item>

<item
    helpID="E2700"
    atom="vmtx_E_TableLength"
    linkTitle="vmtx table specification"
    specLink="http://www.microsoft.com/typography/otspec/vmtx.htm"
    shortDesc="The table length is incorrect"
    fwLinkID="10373"
    tableName="vmtx">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E2800"
    atom="VORG_E_CFF_Font"
    linkTitle="VORG table specification"
    specLink="http://www.microsoft.com/typography/otspec/vorg.htm"
    shortDesc="The font is not a CFF font, and so it should not contain a VORG table"
    fwLinkID="10374"
    tableName="VORG">
    <problem>The VORG table improves accuracy and efficiency for font clients of CFF OpenType fonts. For fonts that contain TrueType outline data, the VORG table will be ignored.</problem>
</item>

<item
    helpID="E2801"
    atom="VORG_E_Version"
    linkTitle="VORG table specification"
    specLink="http://www.microsoft.com/typography/otspec/vorg.htm"
    shortDesc="The major.minor version is not 1.0"
    fwLinkID="10374"
    tableName="VORG">
    <problem>The majorVersion value of the specified VORG format is 1. The minorVersion value of the specified VORG format is 0.</problem>
</item>

<item
    helpID="E4000"
    atom="GDEF_E_AttachListTable_AttachPointArray_PastEOT"
    linkTitle="GDEF table specification"
    specLink="http://www.microsoft.com/typography/otspec/gdef.htm"
    shortDesc="The AttachPoint array extends past the end of the GDEF table"
    fwLinkID="10347"
    tableName="GDEF">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E4001"
    atom="GDEF_E_AttachListTable_AttachPointOffset"
    linkTitle="GDEF table specification"
    specLink="http://www.microsoft.com/typography/otspec/gdef.htm"
    shortDesc="The AttachPoint offset points outside of the GDEF table"
    fwLinkID="10347"
    tableName="GDEF">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E4002"
    atom="GDEF_E_AttachListTable_CoverageOffset_0"
    linkTitle="GDEF table specification"
    specLink="http://www.microsoft.com/typography/otspec/gdef.htm"
    shortDesc="The Coverage offset is zero"
    fwLinkID="10347"
    tableName="GDEF">
    <problem>This value should specify the offset to the Coverage table listing all the glyphs that define attachment points in the GPOS table. The offset is calculated from the beginning of the AttachList table.</problem>
</item>

<item
    helpID="E4003"
    atom="GDEF_E_AttachListTable_CoverageOffset_invalid"
    linkTitle="GDEF table specification"
    specLink="http://www.microsoft.com/typography/otspec/gdef.htm"
    shortDesc="The Coverage offset points past the end of the GDEF table"
    fwLinkID="10347"
    tableName="GDEF">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E4004"
    atom="GDEF_E_CaretValueTable_Format"
    linkTitle="GDEF table specification"
    specLink="http://www.microsoft.com/typography/otspec/gdef.htm"
    shortDesc="The CaretValueFormat is invalid"
    fwLinkID="10347"
    tableName="GDEF">
    <problem>The CaretValueTable can have the following formats:&lt;BR&gt;&lt;BR&gt;Format 1 consists of a format identifier, followed by a single coordinate for the caret position.&lt;BR&gt;&lt;BR&gt;Format 2 specifies the caret coordinate in terms of a contour point index on a specific glyph.&lt;BR&gt;&lt;BR&gt;Format 3 also specifies the value in design units, but uses a Device table rather than a contour point to adjust the value.</problem>
</item>

<item
    helpID="E4006"
    atom="GDEF_E_LigCaretListTable_CoverageOffset_0"
    linkTitle="GDEF table specification"
    specLink="http://www.microsoft.com/typography/otspec/gdef.htm"
    shortDesc="The Coverage offset is zero"
    fwLinkID="10347"
    tableName="GDEF">
    <problem>This value should specify the offset to the Coverage table listing all the ligature glyphs in the font. The offset is calculated from the beginning of the LigCaretList table.</problem>
</item>

<item
    helpID="E4007"
    atom="GDEF_E_LigCaretListTable_CoverageOffset_invalid"
    linkTitle="GDEF table specification"
    specLink="http://www.microsoft.com/typography/otspec/gdef.htm"
    shortDesc="The Coverage offset points past the end of the GDEF table"
    fwLinkID="10347"
    tableName="GDEF">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E4008"
    atom="GDEF_E_LigCaretListTable_LigGlyphArray_PastEOT"
    linkTitle="GDEF table specification"
    specLink="http://www.microsoft.com/typography/otspec/gdef.htm"
    shortDesc="The LigGlyph array extends past the end of the GDEF table"
    fwLinkID="10347"
    tableName="GDEF">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E4009"
    atom="GDEF_E_LigCaretListTable_LigGlyphOffset"
    linkTitle="GDEF table specification"
    specLink="http://www.microsoft.com/typography/otspec/gdef.htm"
    shortDesc="The LigGlyph offset points outside of the GDEF table"
    fwLinkID="10347"
    tableName="GDEF">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E4010"
    atom="GDEF_E_LigGlyphTable_CaretValueArray_PastEOT"
    linkTitle="GDEF table specification"
    specLink="http://www.microsoft.com/typography/otspec/gdef.htm"
    shortDesc="The CaretValue array extends past the end of the GDEF table"
    fwLinkID="10347"
    tableName="GDEF">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E4011"
    atom="GDEF_E_LigGlyphTable_CaretValueOffset"
    linkTitle="GDEF table specification"
    specLink="http://www.microsoft.com/typography/otspec/gdef.htm"
    shortDesc="The CaretValue offset points outside of the GDEF table"
    fwLinkID="10347"
    tableName="GDEF">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E4012"
    atom="GDEF_E_Version"
    linkTitle="GDEF table specification"
    specLink="http://www.microsoft.com/typography/otspec/gdef.htm"
    shortDesc="The version number is not 0x00010000, 0x00010002 nor 0x00010003"
    fwLinkID="10347"
    tableName="GDEF">
    <problem>Versions 0x00010000, 0x00010002 and 0x00010003 are currently the only defined versions of the GDEF table.</problem>
</item>

<item
    helpID="E4013"
    atom="GDEF_E_MarkSetTableFormat"
    linkTitle="GDEF table specification"
    specLink="http://www.microsoft.com/typography/otspec/gdef.htm"
    shortDesc="The MarkSetTableFormat is not 1"
    fwLinkID="10347"
    tableName="GDEF">
    <problem>MarkSetTableFormat must be 1.</problem>
</item>

<item
    helpID="E4014"
    atom="GDEF_E_MarkGlyphSetsDefTable_PastEOT"
    linkTitle="GDEF table specification"
    specLink="http://www.microsoft.com/typography/otspec/gdef.htm"
    shortDesc="The MarkGlyphSetsDefTable extends past the end of the GDEF table"
    fwLinkID="10347"
    tableName="GDEF">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="I4000"
    atom="GDEF_I_MarkSetCount"
    linkTitle="GDEF table specification"
    specLink="http://www.microsoft.com/typography/otspec/gdef.htm"
    shortDesc="The MarkSetCount of the GDEF table"
    fwLinkID="10347"
    tableName="GDEF">
    <problem>Number of mark sets defined in the MarkGlyphSetsTable of the GDEF table</problem>
</item>

<item
    helpID="P4007"
    atom="GDEF_P_MarkGlyphSetsDefTable"
    linkTitle="GDEF table specification"
    specLink="http://www.microsoft.com/typography/otspec/gdef.htm"
    shortDesc="The MarkGlyphSetsDefTable of the GDEF table is okay"
    fwLinkID="10347"
    tableName="GDEF">
    <problem>The MarkGlyphSetsTable of the GDEF table is okay.</problem>
</item>

<item
    helpID="E4100"
    atom="GPOS_E_AnchorTable_format"
    linkTitle="GPOS table specification"
    specLink="http://www.microsoft.com/typography/otspec/gpos.htm"
    shortDesc="The AnchorFormat field is invalid"
    fwLinkID="10349"
    tableName="GPOS">
    <problem>The Anchor table has the following defined formats:&lt;BR&gt;&lt;BR&gt;Format 1 consists of a format identifier and a pair of design unit coordinates that specify the location of the anchor point.&lt;BR&gt;&lt;BR&gt;Format 2 specifies a format identifier, a pair of design unit coordinates for the anchor point, and an index to a glyph contour point that is on the outline of a glyph.&lt;BR&gt;&lt;BR&gt;Format 3 specifies a format identifier, locates an anchor point, and permits fine adjustments to the coordinate values via Device tables (rather than a contour point).</problem>
</item>

<item
    helpID="E4102"
    atom="GPOS_E_Array_pastEOT"
    linkTitle="GPOS table specification"
    specLink="http://www.microsoft.com/typography/otspec/gpos.htm"
    shortDesc="The array extends past the end of the GPOS table"
    fwLinkID="10349"
    tableName="GPOS">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E4103"
    atom="GPOS_E_ExtensionLookupType"
    linkTitle="GPOS table specification"
    specLink="http://www.microsoft.com/typography/otspec/gpos.htm"
    shortDesc="The extension lookup type is invalid"
    fwLinkID="10349"
    tableName="GPOS">
    <problem>The ExtensionLookupType field must be set to one of the defined lookup types, excluding lookup type 9 (1-8 are valid). All subtables in a LookupType 9 lookup must have the same ExtensionLookupType.&lt;BR&gt;&lt;BR&gt;Use an OpenType Layout editing tool to create properly structured tables, or regenerate the font if you believe it may have become corrupted</problem>
</item>

<item
    helpID="E4104"
    atom="GPOS_E_HeaderOffset"
    linkTitle="GPOS table specification"
    specLink="http://www.microsoft.com/typography/otspec/gpos.htm"
    shortDesc="A header offset doesn't point within the table"
    fwLinkID="10349"
    tableName="GPOS">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E4005"
    atom="GDEF_E_HeaderOffset"
    linkTitle="GDEF table specification"
    specLink="http://www.microsoft.com/typography/otspec/gdef.htm"
    shortDesc="A header offset doesn't point within the table"
    fwLinkID="10347"
    tableName="GDEF">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E4101"
    atom="GPOS_E_Array_order"
    linkTitle="GPOS table specification"
    specLink="http://www.microsoft.com/typography/otspec/gpos.htm"
    shortDesc="The array order is incorrect"
    fwLinkID="10349"
    tableName="GPOS">
    <problem>Use an OpenType Layout editing tool to create properly structured tables, or regenerate the font if you believe it may have become corrupted. Some of the GPOS arrays and their orderings are listed below:&lt;BR&gt;&lt;BR&gt;PairSetOffsets - ordered by Coverage index&lt;BR&gt;PairValueRecords - ordered by GlyphID of the second glyph&lt;BR&gt;Class1Records - ordered by Class1 value&lt;BR&gt;Class2Records - ordered by Class2 value&lt;BR&gt;BaseRecords - ordered by BaseCoverage index&lt;BR&gt;BaseAnchors - ordered by Class&lt;BR&gt;LigatureAttachOffsets - ordered by LigatureCoverage index&lt;BR&gt;ComponentRecords - ordered in writing direction&lt;BR&gt;LigatureAnchors - ordered by Class&lt;BR&gt;Mark2Records - ordered by Coverage&lt;BR&gt;PosRuleSets - ordered by Coverage&lt;BR&gt;PosRules - ordered by preference&lt;BR&gt;PosLookupRecords - ordered by design order&lt;BR&gt;PosClassSets - ordered by Class&lt;BR&gt;PosClassRules - ordered by preference</problem>
</item>

<item
    helpID="E4105"
    atom="GPOS_E_HeaderOffset_0"
    linkTitle="GPOS table specification"
    specLink="http://www.microsoft.com/typography/otspec/gpos.htm"
    shortDesc="A header offset has a value of 0"
    fwLinkID="10349"
    tableName="GPOS">
    <problem>The offsets to the ScriptList table, FeatureList table, and LookupList table should all be defined and should be calculated from the beginning of the GPOS table. Use a OTL editing tool to ensure that the GPOS table is constructed properly.</problem>
</item>

<item
    helpID="E4106"
    atom="GPOS_E_Offset_PastEOT"
    linkTitle="GPOS table specification"
    specLink="http://www.microsoft.com/typography/otspec/gpos.htm"
    shortDesc="An offset points past the end of the GPOS table"
    fwLinkID="10349"
    tableName="GPOS">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E4107"
    atom="GPOS_E_PosLookupRecord_SequenceIndex"
    linkTitle="GPOS table specification"
    specLink="http://www.microsoft.com/typography/otspec/gpos.htm"
    shortDesc="The PosLookupRecord SequenceIndex is greater than the Input sequence size"
    fwLinkID="10349"
    tableName="GPOS">
    <problem>This value should specify the index to the input glyph sequence, with the value for the first glyph equal to 0. Use an OpenType Layout editing tool to create properly structured tables, or regenerate the font if you believe it may have become corrupted.</problem>
</item>

<item
    helpID="E4108"
    atom="GPOS_E_SubtableFormat"
    linkTitle="GPOS table specification"
    specLink="http://www.microsoft.com/typography/otspec/gpos.htm"
    shortDesc="The subtable format value is invalid"
    fwLinkID="10349"
    tableName="GPOS">
    <problem>Use an OpenType Layout editing tool to create properly structured tables, or regenerate the font if you believe it may have become corrupted.</problem>
</item>

<item
    helpID="E4109"
    atom="GPOS_E_ValueArray_pastEOT"
    linkTitle="GPOS table specification"
    specLink="http://www.microsoft.com/typography/otspec/gpos.htm"
    shortDesc="The Value array extends past the end of the GPOS table"
    fwLinkID="10349"
    tableName="GPOS">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E4110"
    atom="GPOS_E_ValueFormatReservedBits"
    linkTitle="GPOS table specification"
    specLink="http://www.microsoft.com/typography/otspec/gpos.htm"
    shortDesc="The ValueFormat reserved bits are not all zero"
    fwLinkID="10349"
    tableName="GPOS">
    <problem>Bits 0xF000 of the ValueFormat bit field are reserved and should be set to 0.</problem>
</item>

<item
    helpID="E4111"
    atom="GPOS_E_Version"
    linkTitle="GPOS table specification"
    specLink="http://www.microsoft.com/typography/otspec/gpos.htm"
    shortDesc="The version number is not 0x00010000"
    fwLinkID="10349"
    tableName="GPOS">
    <problem>Format 0x00010000 is currently the only defined version of the GPOS table.</problem>
</item>

<item
    helpID="E4201"
    atom="GSUB_E_Array_pastEOT"
    linkTitle="GSUB table specification"
    specLink="http://www.microsoft.com/typography/otspec/gsub.htm"
    shortDesc="The array extends past the end of the GSUB table"
    fwLinkID="10350"
    tableName="GSUB">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E4202"
    atom="GSUB_E_ExtensionLookupType"
    linkTitle="GSUB table specification"
    specLink="http://www.microsoft.com/typography/otspec/gsub.htm"
    shortDesc="The extension lookup type is invalid"
    fwLinkID="10350"
    tableName="GSUB">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E4203"
    atom="GSUB_E_HeaderOffset"
    linkTitle="GSUB table specification"
    specLink="http://www.microsoft.com/typography/otspec/gsub.htm"
    shortDesc="A header offset doesn't point within the table"
    fwLinkID="10350"
    tableName="GSUB">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E4204"
    atom="GSUB_E_HeaderOffset_0"
    linkTitle="GSUB table specification"
    specLink="http://www.microsoft.com/typography/otspec/gsub.htm"
    shortDesc="A header offset has a value of 0"
    fwLinkID="10350"
    tableName="GSUB">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E4205"
    atom="GSUB_E_Offset_PastEOT"
    linkTitle="GSUB table specification"
    specLink="http://www.microsoft.com/typography/otspec/gsub.htm"
    shortDesc="An offset points past the end of the GSUB table"
    fwLinkID="10350"
    tableName="GSUB">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E4206"
    atom="GSUB_E_SubstLookupRecord_SequenceIndex"
    linkTitle="GSUB table specification"
    specLink="http://www.microsoft.com/typography/otspec/gsub.htm"
    shortDesc="The SubstLookupRecord SequenceIndex is greater than the Input sequence size"
    fwLinkID="10350"
    tableName="GSUB">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E4207"
    atom="GSUB_E_SubtableFormat"
    linkTitle="GSUB table specification"
    specLink="http://www.microsoft.com/typography/otspec/gsub.htm"
    shortDesc="The subtable format value is invalid"
    fwLinkID="10350"
    tableName="GSUB">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E4208"
    atom="GSUB_E_Version"
    linkTitle="GSUB table specification"
    specLink="http://www.microsoft.com/typography/otspec/gsub.htm"
    shortDesc="The version number is not 0x00010000"
    fwLinkID="10350"
    tableName="GSUB">
    <problem>Version 0x00010000 is currently the only defined version of the GSUB table.</problem>
</item>

<item
    helpID="P4310"
    atom="BASE_P_BaseValuesOffset"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The BaseValues offset in the BaseScript table is in a valid range"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="E4300"
    atom="BASE_E_AxisTable_BaseScriptListOffset"
    linkTitle="BASE table specification"
    specLink="http://www.microsoft.com/typography/otspec/base.htm"
    shortDesc="The Axis Table's BaseScriptListOffset is outside the BASE table"
    fwLinkID="10223"
    tableName="BASE">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E4301"
    atom="BASE_E_AxisTable_BaseScriptListOffset_null"
    linkTitle="BASE table specification"
    specLink="http://www.microsoft.com/typography/otspec/base.htm"
    shortDesc="The Axis Table's BaseScriptListOffset is null"
    fwLinkID="10223"
    tableName="BASE">
    <problem>This table may not be constructed properly, or the offset value has been set or changed incorrectly. The BaseScriptListOffset should indicate the offset to the BaseScriptList table from the beginning of the Axis table.</problem>
</item>

<item
    helpID="E4302"
    atom="BASE_E_AxisTable_BaseTagListOffset"
    linkTitle="BASE table specification"
    specLink="http://www.microsoft.com/typography/otspec/base.htm"
    shortDesc="The Axis Table's BaseTagListOffset is outside the BASE table"
    fwLinkID="10223"
    tableName="BASE">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E4303"
    atom="BASE_E_BaseCoordTable_format"
    linkTitle="BASE table specification"
    specLink="http://www.microsoft.com/typography/otspec/base.htm"
    shortDesc="The format of the BaseCoord table is not a valid value"
    fwLinkID="10223"
    tableName="BASE">
    <problem>Use a table editing tool to correct this value, or recreate the BASE table using valid formats for the BaseCoord tables. There are currently three formats for the BaseCoord table:&lt;BR&gt;&lt;BR&gt;Format 1 consists of a format identifier, followed by a single design unit coordinate that specifies the BaseCoord value. This format has the benefits of small size and simplicity, but the BaseCoord value cannot be hinted for fine adjustments at different sizes or device resolutions.&lt;BR&gt;&lt;BR&gt;Format 2 specifies the BaseCoord value in design units, but also supplies a glyph index and a contour point for reference. During font hinting, the contour point on the glyph outline may move.&lt;BR&gt;&lt;BR&gt;Format 3 specifies the BaseCoord value in design units, but it uses a Device table rather than a contour point to adjust the value.</problem>
</item>

<item
    helpID="E4304"
    atom="BASE_E_BaseLangSysRecord_offset"
    linkTitle="BASE table specification"
    specLink="http://www.microsoft.com/typography/otspec/base.htm"
    shortDesc="The BaseLangSysRecord's MinMax offset points outside the BASE table"
    fwLinkID="10223"
    tableName="BASE">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E4305"
    atom="BASE_E_BaseLangSysRecord_offset0"
    linkTitle="BASE table specification"
    specLink="http://www.microsoft.com/typography/otspec/base.htm"
    shortDesc="The BaseLangSysRecord's MinMax offset is zero"
    fwLinkID="10223"
    tableName="BASE">
    <problem>This table may not be constructed properly, or the offset value has been set or changed incorrectly. This value should indicate the offset, from the beginning of the BaseScript table, to the MinMax table for a BaseLangSysRecord.</problem>
</item>

<item
    helpID="E4306"
    atom="BASE_E_BaseLangSysRecord_order"
    linkTitle="BASE table specification"
    specLink="http://www.microsoft.com/typography/otspec/base.htm"
    shortDesc="The BaseScript Table's BaseLangSysRecord array isn't in alphabetical order"
    fwLinkID="10223"
    tableName="BASE">
    <problem>The array of BaseLangSysRecords should be ordered alphabetically, by BaseLangSysTag.</problem>
</item>

<item
    helpID="E4307"
    atom="BASE_E_BaseScriptList_Offset"
    linkTitle="BASE table specification"
    specLink="http://www.microsoft.com/typography/otspec/base.htm"
    shortDesc="A BaseScript offset is outside the BASE table"
    fwLinkID="10223"
    tableName="BASE">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E4308"
    atom="BASE_E_BaseScriptList_Order"
    linkTitle="BASE table specification"
    specLink="http://www.microsoft.com/typography/otspec/base.htm"
    shortDesc="The BaseScriptList table's BaseScriptRecords are not in alphabetical order"
    fwLinkID="10223"
    tableName="BASE">
    <problem>The array of BaseScriptRecords should be ordered alphabetically, by BaseScriptTag.</problem>
</item>

<item
    helpID="E4309"
    atom="BASE_E_BaseTagList_TagOrder"
    linkTitle="BASE table specification"
    specLink="http://www.microsoft.com/typography/otspec/base.htm"
    shortDesc="The tags in the BaseTagList table are not in alphabetical order"
    fwLinkID="10223"
    tableName="BASE">
    <problem>The Baseline tags in the BaseTagList table must be in alphabetical order.</problem>
</item>

<item
    helpID="E4310"
    atom="BASE_E_BaseTagList_TagValid"
    linkTitle="BASE table specification"
    specLink="http://www.microsoft.com/typography/otspec/base.htm"
    shortDesc="The BaseTagList table contains an invalid tag"
    fwLinkID="10223"
    tableName="BASE">
    <problem>All tag names consist of four characters. Names with less than four characters are allowed if followed by the necessary trailing spaces. All tag names defined within a font (including table names, feature tags, and language tags) must be composed of printing characters represented by ASCII values 32-126.&lt;BR&gt;&lt;BR&gt;The Baseline Tags section of the OpenType Tag Registry lists currently registered baseline tags. To learn more about registered tags, see &lt;A TARGET=&quot;top&quot;  HREF=&quot;http://go.microsoft.com/fwlink?LinkID=10370&quot;&gt;the OpenType Tag Registry&lt;/A&gt;</problem>
</item>

<item
    helpID="E4311"
    atom="BASE_E_BaseValuesOffset"
    linkTitle="BASE table specification"
    specLink="http://www.microsoft.com/typography/otspec/base.htm"
    shortDesc="The BaseValues offset in the BaseScript table points outside the BASE table"
    fwLinkID="10223"
    tableName="BASE">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E4312"
    atom="BASE_E_BaseValuesTable_BCO_0"
    linkTitle="BASE table specification"
    specLink="http://www.microsoft.com/typography/otspec/base.htm"
    shortDesc="A BaseCoord offset in the BaseValues table is zero"
    fwLinkID="10223"
    tableName="BASE">
    <problem>Offsets to each BaseCoord table (from the beginning of the BaseValues table) are stored within the BaseValues table. The order of the stored offsets corresponds to the order of the tags listed in the BaselineTag array of the BaseTagList. In other words, the first position in the BaseCoord array will define the offset to the BaseCoord table for the first baseline named in the BaselineTag array, the second position will define the offset to the BaseCoord table for the second baseline named in the BaselineTag array, and so on.</problem>
</item>

<item
    helpID="E4313"
    atom="BASE_E_BaseValuesTable_BCO_invalid"
    linkTitle="BASE table specification"
    specLink="http://www.microsoft.com/typography/otspec/base.htm"
    shortDesc="A BaseCoord offset in the BaseValues table points outside the BASE table"
    fwLinkID="10223"
    tableName="BASE">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E4314"
    atom="BASE_E_DefaultMinMaxOffset"
    linkTitle="BASE table specification"
    specLink="http://www.microsoft.com/typography/otspec/base.htm"
    shortDesc="The BaseScript table's DefaultMinMax offset points outside the BASE table"
    fwLinkID="10223"
    tableName="BASE">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E4315"
    atom="BASE_E_FeatMinMaxRecords_MaxCO_offset"
    linkTitle="BASE table specification"
    specLink="http://www.microsoft.com/typography/otspec/base.htm"
    shortDesc="The FeatMinMaxRecord MaxCoord offset points outside the BASE table"
    fwLinkID="10223"
    tableName="BASE">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E4316"
    atom="BASE_E_FeatMinMaxRecords_MinCO_offset"
    linkTitle="BASE table specification"
    specLink="http://www.microsoft.com/typography/otspec/base.htm"
    shortDesc="The FeatMinMaxRecord MinCoord offset points outside the BASE table"
    fwLinkID="10223"
    tableName="BASE">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E4317"
    atom="BASE_E_HorizAxisOffset_OutsideTable"
    linkTitle="BASE table specification"
    specLink="http://www.microsoft.com/typography/otspec/base.htm"
    shortDesc="The HorizAxisOffset value is outside of the BASE table"
    fwLinkID="10223"
    tableName="BASE">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E4318"
    atom="BASE_E_MinMaxTable_MaxCO"
    linkTitle="BASE table specification"
    specLink="http://www.microsoft.com/typography/otspec/base.htm"
    shortDesc="The MaxCoord offset of the MinMax table points outside the BASE table"
    fwLinkID="10223"
    tableName="BASE">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E4319"
    atom="BASE_E_MinMaxTable_MinCO"
    linkTitle="BASE table specification"
    specLink="http://www.microsoft.com/typography/otspec/base.htm"
    shortDesc="The MinCoord offset of the MinMax table points outside the BASE table"
    fwLinkID="10223"
    tableName="BASE">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E4320"
    atom="BASE_E_Version"
    linkTitle="BASE table specification"
    specLink="http://www.microsoft.com/typography/otspec/base.htm"
    shortDesc="The version number is not 0x00010000"
    fwLinkID="10223"
    tableName="BASE">
    <problem>Version 0x00010000 is currently the only defined version of the BASE table.</problem>
</item>

<item
    helpID="E4321"
    atom="BASE_E_VertAxisOffset_OutsideTable"
    linkTitle="BASE table specification"
    specLink="http://www.microsoft.com/typography/otspec/base.htm"
    shortDesc="The VertAxisOffset value is outside the BASE table"
    fwLinkID="10223"
    tableName="BASE">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E4400"
    atom="JSTF_E_Array_order"
    linkTitle="JSTF table specification"
    specLink="http://www.microsoft.com/typography/otspec/jstf.htm"
    shortDesc="The array order is incorrect"
    fwLinkID="10356"
    tableName="JSTF">
    <problem>The JstfScriptRecords must be stored alphabetically, by JstfScriptTag, within the array.</problem>
</item>

<item
    helpID="E4401"
    atom="JSTF_E_Array_pastEOT"
    linkTitle="JSTF table specification"
    specLink="http://www.microsoft.com/typography/otspec/jstf.htm"
    shortDesc="The array extends past the end of the JSTF table"
    fwLinkID="10356"
    tableName="JSTF">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E4402"
    atom="JSTF_E_Offset_PastEOT"
    linkTitle="JSTF table specification"
    specLink="http://www.microsoft.com/typography/otspec/jstf.htm"
    shortDesc="An offset points past the end of the JSTF table"
    fwLinkID="10356"
    tableName="JSTF">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E4403"
    atom="JSTF_E_tag"
    linkTitle="JSTF table specification"
    specLink="http://www.microsoft.com/typography/otspec/jstf.htm"
    shortDesc="The tag is invalid"
    fwLinkID="10356"
    tableName="JSTF">
    <problem>The JstfScriptTag field contains a 4-byte tag name that must correspond to the script tags used in the GSUB and the GPOS tables.</problem>
</item>

<item
    helpID="E4404"
    atom="JSTF_E_Version"
    linkTitle="JSTF table specification"
    specLink="http://www.microsoft.com/typography/otspec/jstf.htm"
    shortDesc="The version number is not 0x00010000"
    fwLinkID="10356"
    tableName="JSTF">
    <problem>Version 0x00010000 is the only version of the JSTF table currently defined. Correct this field using a table editing tool, or a tool such as VOLT.</problem>
</item>

<item
    helpID="E5000"
    atom="_OTL_ClassDefinitionTable_E_Format"
    linkTitle="OTL common table formats"
    specLink="http://www.microsoft.com/typography/otspec/chapter2.htm"
    shortDesc="The Format field is invalid"
    fwLinkID="10338"
    tableName="OTL Class Definition">
    <problem>The ClassDef table can have either of two formats:&lt;BR&gt;&lt;BR&gt;Format 1 assigns a range of consecutive glyph indices to different classes.&lt;BR&gt;&lt;BR&gt;Format 2 puts groups of consecutive glyph indices into the same class.</problem>
</item>

<item
    helpID="E5001"
    atom="_OTL_ClassDefinitionTable_E_GlyphArrayPastEOT"
    linkTitle="OTL common table formats"
    specLink="http://www.microsoft.com/typography/otspec/chapter2.htm"
    shortDesc="The GlyphArray extends past the end of the table"
    fwLinkID="10338"
    tableName="OTL Class Definition">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E5002"
    atom="_OTL_ClassDefinitionTable_E_RangeRecordArray_order"
    linkTitle="OTL common table formats"
    specLink="http://www.microsoft.com/typography/otspec/chapter2.htm"
    shortDesc="The RangeRecord array is not in sorted order"
    fwLinkID="10338"
    tableName="OTL Class Definition">
    <problem>Each RangeRecord consists of a start glyph index (Start), an end glyph index (End), and the Coverage Index associated with the range's Start glyph. Ranges must be in starting GlyphID order, and they must be distinct, with no overlapping.</problem>
</item>

<item
    helpID="E5003"
    atom="_OTL_ClassDefinitionTable_E_RangeRecordArrayPastEOT"
    linkTitle="OTL common table formats"
    specLink="http://www.microsoft.com/typography/otspec/chapter2.htm"
    shortDesc="The RangeRecord array extends past the end of the table"
    fwLinkID="10338"
    tableName="OTL Class Definition">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E5100"
    atom="_OTL_CoverageTable_E_Format"
    linkTitle="OTL common table formats"
    specLink="http://www.microsoft.com/typography/otspec/chapter2.htm"
    shortDesc="The Format field is invalid"
    fwLinkID="10338"
    tableName="OTL Coverage">
    <problem>There are two formats for Coverage tables:&lt;BR&gt;&lt;BR&gt;Coverage Format 1 consists of a count of covered glyphs (GlyphCount), followed by an array of glyph indices (GlyphArray). The glyph indices must be in numerical order for binary searching of the list. &lt;BR&gt;&lt;BR&gt;Coverage Format 2 consists of a count of glyph index ranges (RangeCount), followed by an array of records (RangeRecords). Each RangeRecord consists of a start glyph index (Start), an end glyph index (End), and the Coverage Index associated with the range's Start glyph. Ranges must be in GlyphID order, and they must be distinct, with no overlapping.</problem>
</item>

<item
    helpID="E5101"
    atom="_OTL_CoverageTable_E_GlyphArrayPastEOT"
    linkTitle="OTL common table formats"
    specLink="http://www.microsoft.com/typography/otspec/chapter2.htm"
    shortDesc="The GlyphArray extends past the end of the table"
    fwLinkID="10338"
    tableName="OTL Coverage">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E5102"
    atom="_OTL_CoverageTable_E_RangeRecordArrayPastEOT"
    linkTitle="OTL common table formats"
    specLink="http://www.microsoft.com/typography/otspec/chapter2.htm"
    shortDesc="The RangeRecord array extends past the end of the table"
    fwLinkID="10338"
    tableName="OTL Coverage">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E5200"
    atom="_OTL_DeviceTable_E_DeltaFormat"
    linkTitle="OTL common table formats"
    specLink="http://www.microsoft.com/typography/otspec/chapter2.htm"
    shortDesc="The device table's DeltaFormat value is invalid"
    fwLinkID="10338"
    tableName="OTL Device">
    <problem>The DeltaFormat value specifies the format of the DeltaValue array. The DeltaFormat may have one of the following values:&lt;BR&gt;&lt;BR&gt;&lt;TABLE BGCOLOR=&quot;#F0F0F0&quot; WIDTH=460 BORDER=0 CELLPADDING=3&gt;
&lt;TR&gt;
&lt;TD CLASS=tab WIDTH=20% BGCOLOR=&quot;#C0C0C0&quot;&gt;Type&lt;/TD&gt;
&lt;TD CLASS=tab WIDTH=30% BGCOLOR=&quot;#C0C0C0&quot;&gt;Name&lt;/TD&gt;
&lt;TD CLASS=tab WIDTH=50% BGCOLOR=&quot;#C0C0C0&quot;&gt;Description&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;	
&lt;TD CLASS=tab VALIGN=TOP&gt;1&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;2&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;Signed 2-bit value, 8 values per uint16&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;	
&lt;TD CLASS=tab VALIGN=TOP&gt;2&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;4&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;Signed 4-bit value, 4 values per uint16&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;	
&lt;TD CLASS=tab VALIGN=TOP&gt;3&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;8&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;Signed 8-bit value, 2 values per uint16&lt;/TD&gt;&lt;/TR&gt;
&lt;/TABLE&gt;</problem>
</item>

<item
    helpID="E5201"
    atom="_OTL_DeviceTable_E_DeltaValueArray_pastEOT"
    linkTitle="OTL common table formats"
    specLink="http://www.microsoft.com/typography/otspec/chapter2.htm"
    shortDesc="The device table's DeltaValue array extends past the end of the table"
    fwLinkID="10338"
    tableName="OTL Device">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E5202"
    atom="_OTL_DeviceTable_E_sizes"
    linkTitle="OTL common table formats"
    specLink="http://www.microsoft.com/typography/otspec/chapter2.htm"
    shortDesc="The device table StartSize is greater than the end size"
    fwLinkID="10338"
    tableName="OTL Device">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E5300"
    atom="_OTL_FeatureListTable_E_FeatureRecord_offset"
    linkTitle="OTL common table formats"
    specLink="http://www.microsoft.com/typography/otspec/chapter2.htm"
    shortDesc="The FeatureRecord Feature table offset points past the end of the table"
    fwLinkID="10338"
    tableName="OTL Feature List">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E5301"
    atom="_OTL_FeatureListTable_E_FeatureRecord_tag"
    linkTitle="details about OpenType files"
    specLink="http://www.microsoft.com/typography/otspec/otff.htm"
    shortDesc="The FeatureRecord tag is invalid"
    fwLinkID="10363"
    tableName="OTL Feature List">
    <problem>The FeatureTag contained in the FeatureRecord is invalid. All tag names consist of four characters. Names with less than four characters are allowed if followed by the necessary trailing spaces. All tag names defined within a font (including table names, feature tags, and language tags) must be composed of printing characters represented by ASCII values 32-126.</problem>
</item>

<item
    helpID="E5302"
    atom="_OTL_FeatureListTable_E_FeatureRecordArray_order"
    linkTitle="OTL common table formats"
    specLink="http://www.microsoft.com/typography/otspec/chapter2.htm"
    shortDesc="The FeatureRecord array is not in alphabetical order"
    fwLinkID="10338"
    tableName="OTL Feature List">
    <problem>The FeatureRecord array must be arranged alphabetically by FeatureTag names.</problem>
</item>

<item
    helpID="E5303"
    atom="_OTL_FeatureListTable_E_FeatureRecordArray_pastEOT"
    linkTitle="OTL common table formats"
    specLink="http://www.microsoft.com/typography/otspec/chapter2.htm"
    shortDesc="The FeatureRecord array extends past the end of the table"
    fwLinkID="10338"
    tableName="OTL Feature List">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E5400"
    atom="_OTL_FeatureTable_E_FeatureParams_nonnull"
    linkTitle="OTL common table formats"
    specLink="http://www.microsoft.com/typography/otspec/chapter2.htm"
    shortDesc="The FeatureParams field is not null"
    fwLinkID="10338"
    tableName="OTL Feature">
    <problem>The FeatureParams field in the Feature Table records the offset relative to the beginning of the Feature Table. If a Feature Parameters table is not needed, the FeatureParams field must be set to NULL.</problem>
</item>

<item
    helpID="E5401"
    atom="_OTL_FeatureTable_E_LookupListIndexArray_pastEOT"
    linkTitle="OTL common table formats"
    specLink="http://www.microsoft.com/typography/otspec/chapter2.htm"
    shortDesc="The LookupListIndexArray extends past the end of the table"
    fwLinkID="10338"
    tableName="OTL Feature">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E5500"
    atom="_OTL_LangSysTable_E_FeatureIndexArray_pastEOT"
    linkTitle="OTL common table formats"
    specLink="http://www.microsoft.com/typography/otspec/chapter2.htm"
    shortDesc="The FeatureIndex array extends past the end of the table"
    fwLinkID="10338"
    tableName="OTL LangSys">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E5501"
    atom="_OTL_LangSysTable_E_LookupOrder"
    linkTitle="OTL common table formats"
    specLink="http://www.microsoft.com/typography/otspec/chapter2.htm"
    shortDesc="The LookupOrder offset is not null"
    fwLinkID="10338"
    tableName="OTL LangSys">
    <problem>This field is reserved for future use and should be set to null.</problem>
</item>

<item
    helpID="E5600"
    atom="_OTL_LookupListTable_E_Lookup_offset"
    linkTitle="OTL common table formats"
    specLink="http://www.microsoft.com/typography/otspec/chapter2.htm"
    shortDesc="The Lookup table offset points past the end of the table"
    fwLinkID="10338"
    tableName="OTL Lookup List">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E5601"
    atom="_OTL_LookupListTable_E_LookupArray_pastEOT"
    linkTitle="OTL common table formats"
    specLink="http://www.microsoft.com/typography/otspec/chapter2.htm"
    shortDesc="The Lookup array extends past the end of the table"
    fwLinkID="10338"
    tableName="OTL Lookup List">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E5700"
    atom="_OTL_LookupTable_E_LookupFlag_reserved"
    linkTitle="OTL common table formats"
    specLink="http://www.microsoft.com/typography/otspec/chapter2.htm"
    shortDesc="The LookupFlag reserved bits are not all set to zero"
    fwLinkID="10338"
    tableName="OTL Lookup">
    <problem>LookupFlag bit 0x00E0 is reserved and should be set to zero.</problem>
</item>

<item
    helpID="E5701"
    atom="_OTL_LookupTable_E_LookupType"
    linkTitle="OTL common table formats"
    specLink="http://www.microsoft.com/typography/otspec/chapter2.htm"
    shortDesc="The LookupType value is invalid"
    fwLinkID="10338"
    tableName="OTL Lookup">
    <problem>OpenType Layout has seven types of GSUB lookups and nine types of GPOS lookups.&lt;BR&gt;&lt;BR&gt;&lt;P&gt;&lt;BR&gt;&lt;I&gt;LookupType Enumeration table for glyph substitution&lt;/I&gt;&lt;P&gt;

&lt;TABLE BGCOLOR=&quot;#F0F0F0&quot; WIDTH=460 BORDER=0 CELLPADDING=3&gt;
&lt;TR&gt;
&lt;TD CLASS=tab WIDTH=20% BGCOLOR=&quot;#COCOCO&quot;&gt;Value&lt;/TD&gt;
&lt;TD CLASS=tab WIDTH=30% BGCOLOR=&quot;#COCOCO&quot;&gt;Type&lt;/TD&gt;
&lt;TD CLASS=tab WIDTH=50% BGCOLOR=&quot;#COCOCO&quot;&gt;Description&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;&lt;TD CLASS=tab VALIGN=TOP&gt;1&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;Single&lt;/TD&gt;
&lt;TD CLASS=tab&gt;Replace one glyph with one glyph&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;&lt;TD CLASS=tab VALIGN=TOP&gt;2&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;Multiple&lt;/TD&gt;
&lt;TD CLASS=tab&gt;Replace one glyph with more than one glyph&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;&lt;TD CLASS=tab VALIGN=TOP&gt;3&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;Alternate&lt;/TD&gt;
&lt;TD CLASS=tab&gt;Replace one glyph with one of many glyphs&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;&lt;TD CLASS=tab VALIGN=TOP&gt;4&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;Ligature&lt;/TD&gt;
&lt;TD CLASS=tab&gt;Replace multiple glyphs with one glyph&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;&lt;TD CLASS=tab VALIGN=TOP&gt;5&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;Context&lt;/TD&gt;
&lt;TD CLASS=tab&gt;Replace one or more glyphs in context&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;&lt;TD CLASS=tab VALIGN=TOP&gt;6&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;Chaining Context&lt;/TD&gt;
&lt;TD CLASS=tab&gt;Replace one or more glyphs in chained context&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;&lt;TD CLASS=tab VALIGN=TOP&gt;7&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;Extension Substitution&lt;/TD&gt;
&lt;TD CLASS=tab&gt;Extension mechanism for other substitutions (i.e. this excludes the Extension type substitution itself)&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;&lt;TD class=&quot;tab&quot; vAlign=&quot;top&quot;&gt;8&lt;/TD&gt;
&lt;TD class=&quot;tab&quot; vAlign=&quot;top&quot;&gt;Reverse&amp;nbsp;chaining context single&lt;/TD&gt;
&lt;TD class=&quot;tab&quot;&gt;Applied in&amp;nbsp;reverse order, replace single glyph in chaining context&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;&lt;TD CLASS=tab VALIGN=TOP&gt;9+&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;Reserved&lt;/TD&gt;
&lt;TD CLASS=tab&gt;For future use&lt;/TD&gt;&lt;/TR&gt;
&lt;/TABLE&gt;
&lt;P&gt;&lt;BR&gt;&lt;I&gt;LookupType Enumeration table for glyph positioning&lt;/I&gt;
&lt;P&gt;
&lt;TABLE BGCOLOR=&quot;#F0F0F0&quot; WIDTH=460 BORDER=0 CELLPADDING=3&gt;
&lt;TR&gt;
&lt;TD CLASS=tab WIDTH=20% BGCOLOR=&quot;#COCOCO&quot;&gt;Value&lt;/TD&gt;
&lt;TD CLASS=tab WIDTH=30% BGCOLOR=&quot;#COCOCO&quot;&gt;Type&lt;/TD&gt;
&lt;TD CLASS=tab WIDTH=50% BGCOLOR=&quot;#COCOCO&quot;&gt;Description&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;&lt;TD CLASS=tab VALIGN=TOP&gt;1&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;Single adjustment&lt;/TD&gt;
&lt;TD CLASS=tab&gt;Adjust position of a single glyph&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;&lt;TD CLASS=tab VALIGN=TOP&gt;2&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;Pair adjustment&lt;/TD&gt;
&lt;TD CLASS=tab&gt;Adjust position of a pair of glyphs&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;&lt;TD CLASS=tab VALIGN=TOP&gt;3&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;Cursive attachment&lt;/TD&gt;
&lt;TD CLASS=tab&gt;Attach cursive glyphs&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;&lt;TD CLASS=tab VALIGN=TOP&gt;4&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;MarkToBase attachment&lt;/TD&gt;
&lt;TD CLASS=tab&gt;Attach a combining mark to a base glyph&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;&lt;TD CLASS=tab VALIGN=TOP&gt;5&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;MarkToLigature attachment&lt;/TD&gt;
&lt;TD CLASS=tab&gt;Attach a combining mark to a ligature&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;&lt;TD CLASS=tab VALIGN=TOP&gt;6&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;MarkToMark attachment&lt;/TD&gt;
&lt;TD CLASS=tab&gt;Attach a combining mark to another mark&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;&lt;TD CLASS=tab VALIGN=TOP&gt;7&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;Context positioning&lt;/TD&gt;
&lt;TD CLASS=tab&gt;Position one or more glyphs in context&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;&lt;TD CLASS=tab VALIGN=TOP&gt;8&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;Chained Context positioning&lt;/TD&gt;
&lt;TD CLASS=tab&gt;Position one or more glyphs in chained context&lt;/TD&gt;&lt;/TR&gt; 
&lt;TR&gt;&lt;TD CLASS=tab VALIGN=TOP&gt;9&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;Extension positioning&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;Extension mechanism for other positionings&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;&lt;TD CLASS=tab VALIGN=TOP&gt;10+&lt;/TD&gt;
&lt;TD CLASS=tab VALIGN=TOP&gt;Reserved&lt;/TD&gt;
&lt;TD CLASS=tab&gt;For future use&lt;/TD&gt;&lt;/TR&gt;
&lt;/TABLE&gt;&lt;BR&gt;&lt;BR&gt;To learn more about how LookupTypes are used in these tables, see &lt;A TARGET=&quot;top&quot; HREF=&quot;http://go.microsoft.com/fwlink?LinkID=10350&quot;&gt;the GSUB table specification&lt;/A&gt; and &lt;A TARGET=&quot;top&quot; HREF=&quot;http://go.microsoft.com/fwlink?LinkID=10349&quot;&gt;the GPOS table specification&lt;/A&gt;.</problem>
</item>

<item
    helpID="E5702"
    atom="_OTL_LookupTable_E_SubtableArray_offset"
    linkTitle="OTL common table formats"
    specLink="http://www.microsoft.com/typography/otspec/chapter2.htm"
    shortDesc="The Subtable array offset value points past the end of the table"
    fwLinkID="10338"
    tableName="OTL Lookup">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E5703"
    atom="_OTL_LookupTable_E_SubtableArray_pastEOT"
    linkTitle="OTL common table formats"
    specLink="http://www.microsoft.com/typography/otspec/chapter2.htm"
    shortDesc="The Subtable offset array extends past the end of the table"
    fwLinkID="10338"
    tableName="OTL Lookup">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E5800"
    atom="_OTL_ScriptListTable_E_ScriptRecord_offset"
    linkTitle="OTL common table formats"
    specLink="http://www.microsoft.com/typography/otspec/chapter2.htm"
    shortDesc="The ScriptRecord offset to ScriptTable points past the end of the table"
    fwLinkID="10338"
    tableName="OTL Script List">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E5801"
    atom="_OTL_ScriptListTable_E_ScriptRecord_tag"
    linkTitle="OTL common table formats"
    specLink="http://www.microsoft.com/typography/otspec/chapter2.htm"
    shortDesc="The ScriptRecord tag is invalid"
    fwLinkID="10338"
    tableName="OTL Script List">
    <problem>All tag names consist of four characters. Names with less than four characters are allowed if followed by the necessary trailing spaces. All tag names defined within a font (including table names, feature tags, and language tags) must be composed of printing characters represented by ASCII values 32-126.</problem>
</item>

<item
    helpID="E5802"
    atom="_OTL_ScriptListTable_E_ScriptRecordArray_order"
    linkTitle="OTL common table formats"
    specLink="http://www.microsoft.com/typography/otspec/chapter2.htm"
    shortDesc="The ScriptRecord array is not in alphabetical order"
    fwLinkID="10338"
    tableName="OTL Script List">
    <problem>The ScriptRecord array must be ordered alphabetically by Script tag. Use an OpenType Layout tool to create this table properly.</problem>
</item>

<item
    helpID="E5803"
    atom="_OTL_ScriptListTable_E_ScriptRecordArray_pastEOT"
    linkTitle="OTL common table formats"
    specLink="http://www.microsoft.com/typography/otspec/chapter2.htm"
    shortDesc="The ScriptRecord array extends past the end of the table"
    fwLinkID="10338"
    tableName="OTL Script List">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E5900"
    atom="_OTL_ScriptTable_E_DefaultLangSysOffset"
    linkTitle="OTL common table formats"
    specLink="http://www.microsoft.com/typography/otspec/chapter2.htm"
    shortDesc="The DefaultLangSys offset points past the end of the table"
    fwLinkID="10338"
    tableName="OTL Script">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E5901"
    atom="_OTL_ScriptTable_E_LangSysRecord_offset"
    linkTitle="OTL common table formats"
    specLink="http://www.microsoft.com/typography/otspec/chapter2.htm"
    shortDesc="The LangSysRecord's LangSys offset points past the end of the table"
    fwLinkID="10338"
    tableName="OTL Script">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E5902"
    atom="_OTL_ScriptTable_E_LangSysRecord_tag"
    linkTitle="OTL common table formats"
    specLink="http://www.microsoft.com/typography/otspec/chapter2.htm"
    shortDesc="The LangSysRecord tag is not valid"
    fwLinkID="10338"
    tableName="OTL Script">
    <problem>All tag names consist of four characters. Names with less than four characters are allowed if followed by the necessary trailing spaces. All tag names defined within a font (including table names, feature tags, and language tags) must be composed of printing characters represented by ASCII values 32-126.</problem>
</item>

<item
    helpID="E5903"
    atom="_OTL_ScriptTable_E_LangSysRecordArray_order"
    linkTitle="OTL common table formats"
    specLink="http://www.microsoft.com/typography/otspec/chapter2.htm"
    shortDesc="The LangSysRecord array is not in alphabetical order"
    fwLinkID="10338"
    tableName="OTL Script">
    <problem>The LangSysRecord array must be ordered alphabetically by Language tag. Use an OpenType Layout tool to create this table properly.</problem>
</item>

<item
    helpID="E5904"
    atom="_OTL_ScriptTable_E_LangSysRecordArray_pastEOT"
    linkTitle="OTL common table formats"
    specLink="http://www.microsoft.com/typography/otspec/chapter2.htm"
    shortDesc="The LangSysRecord array extends past the end of the table"
    fwLinkID="10338"
    tableName="OTL Script">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="E6000"
    atom="_rast_E_3_USED_FOR_PERIOD"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Reserved value of 3 used for period"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>For the instructions SROUND and S45ROUND, the period value of 3 is reserved and should not be used.</problem>
</item>

<item
    helpID="E6001"
    atom="_rast_E_BITS_10_AND_13_SET"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Bits 10 and 13 are set, they are mutually exclusive"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>The following pairs of bits are mutually exclusive: 10 and 13; 8 and 11; 9 and 12. Make sure mutually exclusive bits of the flags field are not set together.</problem>
</item>

<item
    helpID="E6002"
    atom="_rast_E_BITS_8_AND_11_SET"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Bits 8 and 11 are set, they are mutually exclusive"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>The following pairs of bits are mutually exclusive: 10 and 13; 8 and 11; 9 and 12. Make sure mutually exclusive bits of the flags field are not set together.</problem>
</item>

<item
    helpID="E6003"
    atom="_rast_E_BITS_9_AND_12_SET"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Bits 9 and 12 are set, they are mutually exclusive"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>The following pairs of bits are mutually exclusive: 10 and 13; 8 and 11; 9 and 12. Make sure mutually exclusive bits of the flags field are not set together.</problem>
</item>

<item
    helpID="E6004"
    atom="_rast_E_CONTOUR_OUT_OF_RANGE"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Contour out of range"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>Either the zero-based contour value exceeds the larger of the maxp table values of maxContours-1 and maxCompositeContours-1, or the zero-based contour value exceeds value for number of contours in outline - 1.</problem>
</item>

<item
    helpID="E6005"
    atom="_rast_E_CVT_OUT_OF_RANGE"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="CVT Out of range"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>Zero-based value for CVT index exceeds number of entries in CVT table - 1.</problem>
</item>

<item
    helpID="E6006"
    atom="_rast_E_DIVIDE_BY_ZERO"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Divide by zero"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>The DIV instruction attempted to divide by zero.</problem>
</item>

<item
    helpID="E6007"
    atom="_rast_E_EIF_WITHOUT_IF"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="EIF found without IF"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>An EIF was found that did not correspond with an IF.</problem>
</item>

<item
    helpID="E6008"
    atom="_rast_E_ELSE_WITHOUT_EIF"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="ELSE found without EIF"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>An ELSE was found that did not correspond with an EIF.</problem>
</item>

<item
    helpID="E6009"
    atom="_rast_E_ELSE_WITHOUT_IF"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="ELSE found without IF"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>An ELSE was found that did not correspond with an IF.</problem>
</item>

<item
    helpID="E6010"
    atom="_rast_E_ENDF_BEYOND_64K_OF_FDEF"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="ENDF beyond 64K of FDEF"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>A function length cannot exceed 64K in size. An ENDF was found more than 64K away from its corresponding FDEF.</problem>
</item>

<item
    helpID="E6011"
    atom="_rast_E_ENDF_BEYOND_64K_OF_IDEF"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="ENDF beyond 64K of IDEF"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>A user-defined instruction cannot exceed 64K in size. An ENDF was found more than 64K away from its corresponding IDEF.</problem>
</item>

<item
    helpID="E6012"
    atom="_rast_E_ENDF_EXECUTED"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="ENDF found without FDEF or IDEF"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>An ENDF was found without its corresponding FDEF or IDEF.</problem>
</item>

<item
    helpID="E6013"
    atom="_rast_E_EXCEEDS_INSTR_DEFS_IN_MAXP"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="IDEF exceeds max instruction defs in maxp"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>The number of instructions defined exceeds value for maxInstructionDefs in maxp.</problem>
</item>

<item
    helpID="E6014"
    atom="_rast_E_FDEF_FOUND_IN_FDEF"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="FDEF found within FDEF - ENDF pair"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>A function cannot be defined within another function or user-defined instruction.</problem>
</item>

<item
    helpID="E6015"
    atom="_rast_E_FDEF_FOUND_IN_IDEF"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="FDEF found within IDEF - ENDF pair"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>A function cannot be defined within another function or user-defined instruction.</problem>
</item>

<item
    helpID="E6016"
    atom="_rast_E_FDEF_OUT_OF_RANGE"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="FDEF out of range"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>Zero-based value for function number exceeds the maxp value for maxFunctionsDefs - 1.</problem>
</item>

<!-- HTL: E6017 is not used AFAIK, seems to be a mistake as it is almost identical to E6020.; not in 1.0.1028/1.0.1140/1.1 -->
<item
    helpID="E6017"
    atom="_rast_E_FDEF_SPACE_NOT_DEFINED"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Function definition space not defined"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>The called function was not properly defined. Make sure function was defined in either the font program or the pre-program.</problem>
</item>

<item
    helpID="E6018"
    atom="_rast_E_FDEF_WITHOUT_ENDF"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="FDEF found without ENDF"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>An FDEF was found that did not correspond with an ENDF.</problem>
</item>

<item
    helpID="E6019"
    atom="_rast_E_FUCOORDINATE_OUT_OF_RANGE"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Funit coordinate out of range must be -16384 .. 16383"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>Font Unit values must be in the range of -16384 to 16383.

&lt;p&gt;
FontVal 1.0 mis-implemented the check as F26.6 and thus for [-1048576, 1048512] instead.
</problem>
</item>

<item
    helpID="E6020"
    atom="_rast_E_FUNCTION_NOT_DEFINED"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Function not defined"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>The called function was not properly defined. Make sure function was defined in either the font program or the pre-program.</problem>
</item>

<item
    helpID="E6021"
    atom="_rast_E_IDEF_FOUND_IN_FDEF"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="IDEF found within FDEF - ENDF pair"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>A user-defined instruction cannot be defined within another user-defined instruction or function.</problem>
</item>

<item
    helpID="E6022"
    atom="_rast_E_IDEF_FOUND_IN_IDEF"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="IDEF found within IDEF - ENDF pair"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>A user-defined instruction cannot be defined within another user-defined instruction or function.</problem>
</item>

<item
    helpID="E6023"
    atom="_rast_E_IDEF_WITHOUT_ENDF"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="IDEF found without ENDF"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>An IDEF was found that did not correspond with an ENDF.</problem>
</item>

<item
    helpID="E6024"
    atom="_rast_E_IF_WITHOUT_EIF"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="IF found without corresponding EIF"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>An IF was found that did not correspond with an EIF.</problem>
</item>

<item
    helpID="E6025"
    atom="_rast_E_INST_OPCODE_TO_LARGE"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Instruction OpCode is to large. Must be between 0 and 255"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>The instruction OpCode you are trying to define is too large. The OpCode is 8-bits in size, and can only have a value of 0-255.</problem>
</item>

<item
    helpID="E6026"
    atom="_rast_E_INSTR_DEFD_BY_FS"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Instruction already defined by rasterizer"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>There is an attempt to create a user-defined instruction that is already defined by the rasterizer.</problem>
</item>

<item
    helpID="E6027"
    atom="_rast_E_INVALID_FLAG"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Invalid Instruction flag"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>For the instructions MDRP, MIRP, ROUND, and NROUND, the value 3 has been used as distance type for engine characteristic compensation. For these instructions, two bits of the instruction flags are designated for the distance type for engine characteristic compensation. Valid values are 0 for Gray, 1 for Black and 2 for White.</problem>
</item>

<item
    helpID="E6028"
    atom="_rast_E_INVALID_INSTRUCTION"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Invalid Instruction"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>Attempt to execute an instruction which is invalid and has not been defined.</problem>
</item>

<item
    helpID="E6029"
    atom="_rast_E_INVALID_MAXZONES_IN_MAXP"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Invalid maxZones in maxp table"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>The value for maxZones in maxp must be either 1 or 2: 1 if you do not use the twilight zone, and 2 if you do.</problem>
</item>

<item
    helpID="E6030"
    atom="_rast_E_INVALID_STACK_ACCESS"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Attempt to access stack element out of range"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>Make sure the value for the index will not access a stack element which is either above the top of the stack or below the bottom of the stack. Stack index must be greater than or equal to 1.</problem>
</item>

<item
    helpID="E6031"
    atom="_rast_E_INVALID_ZONE"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Invalid zone"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>Valid values for zone are: 0 or 1 if maxZones in maxp is 2; 1 if maxZones in maxp is 1.</problem>
</item>

<item
    helpID="E6032"
    atom="_rast_E_INVALID_ZONE_IN_IUP"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="ZP2 in IUP does not point to zone 1"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>IUP operates on points in the glyph zone pointed to by ZP2. This zone should always be zone 1. IUP cannot operate on the twilight zone.</problem>
</item>

<item
    helpID="E6033"
    atom="_rast_E_INVALID_ZONE_NO_TWI"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="No twilight zone defined. Invalid zone"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>There is an attempt to use the twilight zone when it does not exist because maxZones in maxp is 1. The value for maxZones should be set to 2 if the twilight zone is going to be used.</problem>
</item>

<item
    helpID="E6034"
    atom="_rast_E_JMP_BEFORE_BEGINNING"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Jump before beginning of program or function"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>There is an attempt to use one of the jump instructions to jump to an offset in the instruction stream which is before the beginning of the program or function.</problem>
</item>

<item
    helpID="E6035"
    atom="_rast_E_JMP_BEYOND_2MORE_THAN_END"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Jump beyond 2 bytes past end of function or program"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>There is an attempt to use one of the jump instructions to jump to an offset in the instruction stream which is more than 2 bytes beyond the end of the function or program.</problem>
</item>

<item
    helpID="E6036"
    atom="_rast_E_MATH_OVERFLOW"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Math overflow"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>The result of either ADD, SUB, MUL, or DIV is an overflow. The result cannot fit into an F26Dot6 value.</problem>
</item>

<item
    helpID="E6037"
    atom="_rast_E_NOT_CALLED_FROM_PREPROGRAM"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Not called from pre-program"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>Make sure you only make this call from the pre-program.&lt;BR&gt;&lt;BR&gt;FDEF and IDEF can only be called from the font program or pre-program. INSTCTRL[ ] can only be called from the pre-program.

&lt;p&gt;
&lt;A TARGET=&quot;top&quot; HREF=&quot;https://www.microsoft.com/typography/cleartype/truetypecleartype.aspx&quot;&gt;The ClearType whitepaper&lt;/A&gt;
states that INSTCTRL[ ] with selector 3 is used in glyph programs for ClearType. This was not taken account of in FontVal 1.0 .
</problem>
</item>

<item
    helpID="E6038"
    atom="_rast_E_OVERFLOW_INST_PTR"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Overflow Instruction Stream"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>One of the PUSH instructions has tried to push data which is beyond the end of the instruction stream.</problem>
</item>

<item
    helpID="E6039"
    atom="_rast_E_POINT_OUT_OF_RANGE"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Point out of range"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>Either the zero-based point value exceeds the larger of the maxp table values of maxPoints - 1 and maxCompositePoints - 1, or the zero-based point value exceeds value for the number of points in outline - 1, including phantom points.</problem>
</item>

<item
    helpID="E6040"
    atom="_rast_E_PREPROGAM_ZONE_NOT_TWI"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Zone referenced in pre-program is not the twilight zone"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>If you are operating in the pre-program, a zone referenced must be the twilight zone since the context does not include a particular glyph and there are no actual points.</problem>
</item>

<!-- HTL: E6041 not used AFAIK; not in 1.0.1028/1.0.1140/1.1 -->
<item
    helpID="E6041"
    atom="_rast_E_REFPOINT_USED_BUT_NOT_SET"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Reference point used but not set"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="E6042"
    atom="_rast_E_RESERVED_BIT_SET"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="At least one reserved bit is set"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>At least one reserved bit of the flags field is set. Make sure it is clear since it is reserved for future use.</problem>
</item>

<item
    helpID="E6043"
    atom="_rast_E_RP1_RP2_SAME_POS_ON_PROJ"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="RP1 and RP2 have the same position on the projection vector"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>For the IP instruction, it is illegal if RP1 and RP2 have the same position on the projection vector.</problem>
</item>

<item
    helpID="E6044"
    atom="_rast_E_SELECTOR_INVALID"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Selector invalid"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>The selector value is outside valid range.</problem>
</item>

<item
    helpID="E6045"
    atom="_rast_E_STACK_OVERFLOW"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Stack Overflow"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>There is an attempt to PUSH more data on the stack than space will accommodate. Adjust maxStackElements field in the maxp table.

&lt;p&gt;
Note that the FreeType backend of FontVal 2.0+ behaves differently after this error, compared to FontVal 1.0.
Instead of aborting, it continues processing the rest of the instruction stream. Users can therefore see further problems
beyond the point of this error. This is expected.
</problem>
</item>

<item
    helpID="E6046"
    atom="_rast_E_STACK_UNDERFLOW"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Stack Underflow"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>There is an attempt to POP a value from below the bottom of the stack. Make sure the data you are popping from the stack has been pushed onto the stack.

&lt;p&gt;
Note that the FreeType backend of FontVal 2.0+ behaves differently after this error, compared to FontVal 1.0.
Instead of aborting, it continues processing the rest of the instruction stream. Users can therefore see further problems
beyond the point of this error. This is expected.
</problem>
</item>

<item
    helpID="E6047"
    atom="_rast_E_STORAGE_OUT_OF_RANGE"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Storage index out of range"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>Zero-based storage index exceeds the maxp value for maxStorage - 1. Adjust maxp accordingly.

&lt;p&gt;
The FreeType backend of FontVal 2.0+ is known to be better at identifying this kind of error than FontVal 1.0.FontVal 1.0.
See https://bugzilla.redhat.com/show_bug.cgi?id=1648612 and https://bugzilla.redhat.com/show_bug.cgi?id=1646688 .
</problem>
</item>

<item
    helpID="E6048"
    atom="_rast_E_STORE_INDEX_NOT_WRITTEN_TO"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Storage location not written to"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>The storage location has not been written to. This means that the data in the storage location is not valid.</problem>
</item>

<item
    helpID="E6049"
    atom="_rast_E_TWILIGHT_ZONE_PT_NOT_SET"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Twilight zone point not set"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>A twilight zone point has not been set and is not valid. Make sure it is set with an instructions like MDAP, MIAP, MIRP, MSIRP, or SCFS before it is used.

&lt;p&gt;A few instructions use more than one reference points or contain a loop, and can therefore emit this error message more than
once at the same location, one per reference point. This is seen with IP and MSIRP in the wild.
</problem>
</item>

<item
    helpID="E6050"
    atom="_rast_E_VALUE_INVALID_0_OR_1"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Value invalid should be 0 or 1"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>If the selector for the INSTCTRL instruction is 1, then valid values for the value parameter are 0 or 1.</problem>
</item>

<item
    helpID="E6051"
    atom="_rast_E_VALUE_INVALID_0_OR_2"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Value invalid should be 0 or 2"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>If the selector for the INSTCTRL instruction is 2, then valid values for the value parameter are 0 or 2.</problem>
</item>

<item
    helpID="E6052"
    atom="_rast_E_VALUE_OUT_OF_RANGE"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Value out of range"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>The value is outside its value range.</problem>
</item>

<item
    helpID="E6053"
    atom="_rast_E_VALUE_TO_LARGE_FOR_INT16"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Value exceeds capacity of 2 byte number"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>The value is too big to fit into a 16-bit (2-byte) number.</problem>
</item>

<item
    helpID="E6054"
    atom="_rast_E_VALUE_TO_LARGE_FOR_INT8"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Value exceeds capacity of 1 byte number"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>The value is too big to fit into an 8-bit (1-byte) number.</problem>
</item>

<item
    helpID="E6055"
    atom="_rast_E_VALUE_TO_SMALL"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Value too small"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>The value is less than the smallest allowed value.</problem>
</item>

<item
    helpID="E6056"
    atom="_rast_E_VECTOR_XY_INVALID"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="X and Y components of vector are invalid. X^2 + Y^2 != 0x4000^2"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>Values to be put on the stack are based on normalized vector lengths and must be set such that (X^2 + Y^2) is 1. 0x4000 is the hex representation of 1 in 2.14 format.</problem>
</item>

<item
    helpID="E6057"
    atom="_rast_E_VECTOR_XY_ZERO"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="X and Y components of vector are 0"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>The X and Y components of a vector passed to SPVFS or SFVFS cannot be 0.</problem>
</item>

<item
    helpID="E6058"
    atom="_rast_E_ZONE_NOT_0_NOR_1"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Zone not 0 nor 1"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>The zone is set to something other than 0 or 1.</problem>
</item>

<item
    helpID="E6059"
    atom="_rast_E_rasterization"
    linkTitle="details about OpenType files"
    specLink="WARNING: field missing"
    shortDesc="Could not perform rasterization"
    fwLinkID="10363"
    tableName="Rasterization Test">
    <problem>Rasterization could not be performed because the head, maxp, or glyf table is missing.</problem>
</item>

<item
    helpID="E6070"
    atom="_rast_E_FT_EXECUTION_TOO_LONG"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Execution time too long and exceeds dynamic limit"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>Execution time too long and exceeds dynamic limit</problem>
</item>

<item
    helpID="E6071"
    atom="_rast_E_FT_EXECUTION_TOO_LONG_BACKWARD_JUMP"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Execution time too long and exceeds dynamic limit in backward jump"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>Execution time too long and exceeds dynamic limit in backward jump</problem>
</item>

<item
    helpID="E6072"
    atom="_rast_E_FT_DEF_IN_GLYF"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="FDEF or IDEF should be in fpgm and prep only, not in glyf"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>FDEF or IDEF should be in fpgm and prep only, not in glyf</problem>
</item>

<item
    helpID="I0001"
    atom="_GEN_I_Collection"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The file begins with a TTC header (file contains a collection of fonts)"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="I0002"
    atom="_GEN_I_OpeningFile"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Opening File"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="I0004"
    atom="_GEN_I_Single"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The file begins with an Offset Table (file contains a single font)"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="I0005"
    atom="_GEN_I_TotalValTime"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Total time validating file"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="I0040"
    atom="_Table_I_Non_OT_Table"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Not an OpenType table, contents not validated"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="I0041"
    atom="_Table_I_NotSelected"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Table not selected for validation"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="I0050"
    atom="_TEST_I_NotForCFF"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Cannot perform test since this is a CFF font"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="I0051"
    atom="_TEST_I_TableVersion"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Cannot perform test, table is wrong version!"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="I0052"
    atom="_TEST_I_RastTestNotSelected"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Rasterization not selected for validation"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="I0200"
    atom="CFF_I_NotValidated"
    linkTitle="CFF table specification"
    specLink="http://www.microsoft.com/typography/otspec/cff.htm"
    shortDesc="Validation for the CFF table is not completedly implemented"
    fwLinkID="0"
    tableName="CFF">
  <problem>Validation for the CFF table is not completedly implemented. Charset, Encoding, FDSelect for CID-keyed fonts, and
  detailed testing of CharStrings are not implemented</problem>
</item>

<item
    helpID="I0201"
    atom="CFF_I_Version"
    linkTitle="CFF table specification"
    specLink="http://www.microsoft.com/typography/otspec/cff.htm"
    shortDesc="The CFF major.minor version for this table"
    fwLinkID="0"
    tableName="CFF">
    <problem>The CFF major.minor version for this table</problem>
</item>

<item
    helpID="P0202"
    atom="CFF_P_Header"
    linkTitle="CFF table specification"
    specLink="http://www.microsoft.com/typography/otspec/cff.htm"
    shortDesc="The header for the CFF table is okay"
    fwLinkID="0"
    tableName="CFF">
    <problem>The header for the CFF table is okay.</problem>
</item>

<item
    helpID="E0202"
    atom="CFF_E_Header"
    linkTitle="CFF table specification"
    specLink="http://www.microsoft.com/typography/otspec/cff.htm"
    shortDesc="The header for the CFF table is wrong"
    fwLinkID="0"
    tableName="CFF">
    <problem>The header for the CFF table should have major 1, minor 0, header size 4 and offSize 0.</problem>
</item>

<item
    helpID="P0203"
    atom="CFF_P_MAININDEX_Enumeration"
    linkTitle="CFF table specification"
    specLink="http://www.microsoft.com/typography/otspec/cff.htm"
    shortDesc="Parse and Count items in the 4 main INDEX"
    fwLinkID="0"
    tableName="CFF">
    <problem>Parse and count items in the 4 main INDEX</problem>
</item>

<item
    helpID="E0203"
    atom="CFF_E_MAININDEX_Enumeration"
    linkTitle="CFF table specification"
    specLink="http://www.microsoft.com/typography/otspec/cff.htm"
    shortDesc="Failed to parse and count items in the 4 main INDEX"
    fwLinkID="0"
    tableName="CFF">
    <problem>Failed to parse and count items in the 4 main INDEX</problem>
</item>

<item
    helpID="P0204"
    atom="CFF_P_NameDICTSize"
    linkTitle="CFF table specification"
    specLink="http://www.microsoft.com/typography/otspec/cff.htm"
    shortDesc="Name and TopDICT have exactly 1 item each."
    fwLinkID="0"
    tableName="CFF">
    <problem>Name and TopDICT have exactly 1 item each.</problem>
</item>

<item
    helpID="E0204"
    atom="CFF_E_NameDICTSize"
    linkTitle="CFF table specification"
    specLink="http://www.microsoft.com/typography/otspec/cff.htm"
    shortDesc="Name and TopDICT should have exactly 1 item each."
    fwLinkID="0"
    tableName="CFF">
    <problem>Name and TopDICT should have exactly 1 item each.</problem>
</item>

<item
    helpID="W0205"
    atom="CFF_W_INDEXFirstOffset"
    linkTitle="CFF table specification"
    specLink="http://www.microsoft.com/typography/otspec/cff.htm"
    shortDesc="The first offset in an INDEX structure should be 1"
    fwLinkID="0"
    tableName="CFF">
    <problem>The first offset in an INDEX structure should be 1</problem>
</item>

<item
    helpID="E0206"
    atom="CFF_E_StructOverlap"
    linkTitle="CFF table specification"
    specLink="http://www.microsoft.com/typography/otspec/cff.htm"
    shortDesc="structure overlap detected"
    fwLinkID="0"
    tableName="CFF">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="P0207"
    atom="CFF_P_DICTUnwind"
    linkTitle="CFF table specification"
    specLink="http://www.microsoft.com/typography/otspec/cff.htm"
    shortDesc="Top/FD Dictionary Unwind Passed"
    fwLinkID="0"
    tableName="CFF">
    <problem></problem>
</item>

<item
    helpID="E0207"
    atom="CFF_E_DICTUnwind"
    linkTitle="CFF table specification"
    specLink="http://www.microsoft.com/typography/otspec/cff.htm"
    shortDesc="Top/FD Dictionary Unwind Error"
    fwLinkID="0"
    tableName="CFF">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="P0208"
    atom="CFF_P_PrivDICTUnwind"
    linkTitle="CFF table specification"
    specLink="http://www.microsoft.com/typography/otspec/cff.htm"
    shortDesc="Private Dictionary Unwind Passed"
    fwLinkID="0"
    tableName="CFF">
    <problem></problem>
</item>

<item
    helpID="E0208"
    atom="CFF_E_PrivDICTUnwind"
    linkTitle="CFF table specification"
    specLink="http://www.microsoft.com/typography/otspec/cff.htm"
    shortDesc="Private Dictionary Unwind Error"
    fwLinkID="0"
    tableName="CFF">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="P0209"
    atom="CFF_P_INDEXCount"
    linkTitle="CFF table specification"
    specLink="http://www.microsoft.com/typography/otspec/cff.htm"
    shortDesc="Number of items in an INDEX"
    fwLinkID="0"
    tableName="CFF">
    <problem></problem>
</item>

<item
    helpID="E0209"
    atom="CFF_E_INDEXCount"
    linkTitle="CFF table specification"
    specLink="http://www.microsoft.com/typography/otspec/cff.htm"
    shortDesc="Failed to extract INDEX"
    fwLinkID="0"
    tableName="CFF">
    <problem>This error indicates a structural problem with the font. Structural errors may be caused by: a font tool incorrectly generating the font file; a person altering the contents of a valid font file; or some other corruption to the font file. Regenerate the font, or contact the font vendor to obtain a valid version of the font.</problem>
</item>

<item
    helpID="P0210"
    atom="CFF_P_CharStringsCount"
    linkTitle="CFF table specification"
    specLink="http://www.microsoft.com/typography/otspec/cff.htm"
    shortDesc="Count of CharStrings is equal to numGlyphs in maxp"
    fwLinkID="0"
    tableName="CFF">
    <problem></problem>
</item>

<item
    helpID="E0210"
    atom="CFF_E_CharStringsCount"
    linkTitle="CFF table specification"
    specLink="http://www.microsoft.com/typography/otspec/cff.htm"
    shortDesc="Count of CharStrings is not equal to numGlyphs in maxp"
    fwLinkID="0"
    tableName="CFF">
    <problem>Count of CharStrings should be equal to numGlyphs in maxp.</problem>
</item>

<item
    helpID="I0211"
    atom="CFF_I_CIDROS"
    linkTitle="CFF table specification"
    specLink="http://www.microsoft.com/typography/otspec/cff.htm"
    shortDesc="Registry, Ordering, Supplement of the CID Font"
    fwLinkID="0"
    tableName="CFF">
    <problem>Registry, Ordering, Supplement of the CID Font</problem>
</item>

<item
    helpID="P0212"
    atom="CFF_P_Non_ASCII_String_or_Name"
    linkTitle="CFF table specification"
    specLink="http://www.microsoft.com/typography/otspec/cff.htm"
    shortDesc="Names and Strings are us-ascii"
    fwLinkID="0"
    tableName="CFF">
    <problem></problem>
</item>

<item
    helpID="E0212"
    atom="CFF_E_Non_ASCII_String_or_Name"
    linkTitle="CFF table specification"
    specLink="http://www.microsoft.com/typography/otspec/cff.htm"
    shortDesc="Names and Strings should be us-ascii"
    fwLinkID="0"
    tableName="CFF">
    <problem>Font names and text strings in the CFF table should be in us-ascii encoding. In particular, copyright signs, trademarks, notices and non-English names of authors should be encoded with the proper encoding in the top level 'name' table. Some font vendors had in the past occasionally and mistakenly put copyright signs in either Latin1 or UTF8 encoding in the CFF String table.</problem>
</item>

<item
    helpID="I0500"
    atom="DSIG_I_VerifySignature_Generic"
    linkTitle="DSIG table specification"
    specLink="http://www.microsoft.com/typography/otspec/dsig.htm"
    shortDesc="DSIG Information"
    fwLinkID="10341"
    tableName="DSIG">
    <problem>Catch-all Place Holder for Generic DSIG Information</problem>
</item>

<item
    helpID="I0900"
    atom="fpgm_I_NotValidated"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Validation for the fpgm table is not directly implemented, but rasterization testing will validate any executed hinting instructions"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="I1700"
    atom="loca_I_GlyfEntryEmpty"
    linkTitle="loca table specification"
    specLink="http://www.microsoft.com/typography/otspec/loca.htm"
    shortDesc="Loca references a zero-length entry in the glyf table"
    fwLinkID="10358"
    tableName="loca">
    <problem>This message may indicate that there are multiple zero-length glyphs located at the end of the glyf table. If so, remove the extra empty glyphs.</problem>
</item>

<item
    helpID="I2001"
    atom="name_I_Preferred_family_present"
    linkTitle="name table specification"
    specLink="https://www.microsoft.com/typography/otspec/name.htm"
    shortDesc="Found Typographic Family name (Name ID 16)"
    fwLinkID="0"
    tableName="name">
    <problem>Found Typographic Family name (Name ID 16)</problem>
</item>

<item
    helpID="I2002"
    atom="name_I_Preferred_family_not_present"
    linkTitle="name table specification"
    specLink="https://www.microsoft.com/typography/otspec/name.htm"
    shortDesc="No string for Typographic Family name (Name ID 16)"
    fwLinkID="0"
    tableName="name">
    <problem>No string for Typographic Family name (Name ID 16)</problem>
</item>

<item
    helpID="I2003"
    atom="name_I_Preferred_subfamily_present"
    linkTitle="name table specification"
    specLink="https://www.microsoft.com/typography/otspec/name.htm"
    shortDesc="Found Typographic Subfamily name (Name ID 17)"
    fwLinkID="0"
    tableName="name">
    <problem>Found Typographic Subfamily name (Name ID 17)</problem>
</item>

<item
    helpID="I2004"
    atom="name_I_Preferred_subfamily_not_present"
    linkTitle="name table specification"
    specLink="https://www.microsoft.com/typography/otspec/name.htm"
    shortDesc="No string for Typographic Subfamily name (Name ID 17)"
    fwLinkID="0"
    tableName="name">
    <problem>No string for Typographic Subfamily name (Name ID 17)</problem>
</item>

<item
    helpID="I2100"
    atom="OS_2_I_RangeBitNotSet"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#ur"
    shortDesc="Characters in a unicode range are present in the font, but not indicated in ulUnicodeRange fields"
    fwLinkID="10397"
    tableName="OS/2">
    <problem>Frequently, it is not necessary to cover the entire Unicode range for a font to be considered functional in that range. The font designer determines whether this font can be useful (or should be used) for the Unicode range noted.</problem>
</item>

<item
    helpID="I2300"
    atom="post_I_names_noAdobe"
    linkTitle="post table specification"
    specLink="http://www.microsoft.com/typography/otspec/post.htm"
    shortDesc="The post name isn't in uniXXXX or uXXXXX format and there is no Adobe Glyph List entry"
    fwLinkID="10365"
    tableName="post">
    <problem>PostScript character set glyph names should match those in the PostScript Reference Manual. Glyphs outside the PostScript character set may use a character string in the format of uniXXXX as their PostScript name. To learn more about PostScript names, see &lt;A TARGET=&quot;top&quot; HREF=&quot;http://go.microsoft.com/fwlink?LinkID=0&quot;&gt;Adobe Glyph List&lt;/A&gt;.</problem>
</item>

<item
    helpID="I2301"
    atom="post_I_names_nomatch"
    linkTitle="post table specification"
    specLink="http://www.microsoft.com/typography/otspec/post.htm"
    shortDesc="The post name does not match the name in the Adobe Glyph List"
    fwLinkID="10365"
    tableName="post">
    <problem>PostScript character set glyph names should match those in the PostScript Reference Manual. Glyphs outside the PostScript character set may use a character string in the format of uniXXXX as their PostScript name. To learn more about PostScript names, see &lt;A TARGET=&quot;top&quot; HREF=&quot;http://go.microsoft.com/fwlink?LinkID=0&quot;&gt;Adobe Glyph List&lt;/A&gt;.</problem>
</item>

<item
    helpID="I2302"
    atom="post_I_v2_glyphNameIndex_notv2"
    linkTitle="post table specification"
    specLink="http://www.microsoft.com/typography/otspec/post.htm"
    shortDesc="The glyphNameIndex array was not tested since version != 2"
    fwLinkID="10365"
    tableName="post">
    <problem>This field is only used in Version 2.0 of the post table (for TrueType fonts to be used on Windows). Since the post table has a different version, tests of these fields were not performed.</problem>
</item>

<item
    helpID="I2303"
    atom="post_I_v2_names_notv2"
    linkTitle="post table specification"
    specLink="http://www.microsoft.com/typography/otspec/post.htm"
    shortDesc="The post name was not tested since version != 2"
    fwLinkID="10365"
    tableName="post">
    <problem>This field is only used in Version 2.0 of the post table (for TrueType fonts to be used on Windows). Since the post table has a different version, tests of these fields were not performed.</problem>
</item>

<item
    helpID="I2304"
    atom="post_I_v2_numberOfGlyphs_notv2"
    linkTitle="post table specification"
    specLink="http://www.microsoft.com/typography/otspec/post.htm"
    shortDesc="The numberOfGlyphs field was not tested since version != 2"
    fwLinkID="10365"
    tableName="post">
    <problem>This field is only used in Version 2.0 of the post table (for TrueType fonts to be used on Windows). Since the post table has a different version, tests of these fields were not performed.</problem>
</item>

<item
    helpID="I2305"
    atom="post_I_names_uni_unexpected"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The post name has an unexpected value"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="I2400"
    atom="prep_I_NotValidated"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Validation for the prep table is not directly implemented, but rasterization testing will validate any executed hinting instructions"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="P0010"
    atom="_OFFSET_P_BinarySearchTables"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The searchRange, entrySelector, and rangeShift fields are all valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0011"
    atom="_OFFSET_P_numTables"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The numTables field is non-zero"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0020"
    atom="_FONT_P_MissingRequiredTable"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="All required tables are present"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0021"
    atom="_FONT_P_OptimalOrder"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Tables are in optimal order"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0022"
    atom="_FONT_P_UnnecessaryTable"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="No unnecessary tables are present"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0023"
    atom="_FONT_P_MissingRecommendedTable"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="All recommended tables are present"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0030"
    atom="_DE_P_TableAlignment"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The directory entry table offsets are all multiples of 4"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0031"
    atom="_DE_P_TagName"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The directory entry tag names are valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0032"
    atom="_DE_P_TagsAscending"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The directory entry tags are in ascending order"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0300"
    atom="cmap_P_AppleLogo"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Character code 240, the Apple logo, is mapped to missing glyph in cmap 1,0 (legal requirement for Microsoft fonts)"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0301"
    atom="cmap_P_AppleMSSupport"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The table contains both Apple and Microsoft subtables"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0302"
    atom="cmap_P_DuplicateSubtables"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="There are no duplicate subtables"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0303"
    atom="cmap_P_EuroGlyph_Mac"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Character code 219, the euro character, is mapped for cmap 1,0"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0304"
    atom="cmap_P_EuroGlyph_Uni"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Character code U+20AC, the euro character, is mapped for cmap 3,1"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0305"
    atom="cmap_P_InternalFormat"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The subtable internal format appears valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0306"
    atom="cmap_P_SubtableLength"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Each subtable length is within the table"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0307"
    atom="cmap_P_SubtableOffset"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Each subtable offset is within the table"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0308"
    atom="cmap_P_SubtableOverlap"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="No overlapping subtables were found"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0309"
    atom="cmap_P_SubtableSortOrder"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The subtables are in the correct order"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0310"
    atom="cmap_P_SubtableValidFormat"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Each subtable's format number is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0311"
    atom="cmap_P_UnicodePrivateUse"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="No characters are mapped in the Unicode Private Use area"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0312"
    atom="cmap_P_version"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The table version number is 0"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0313"
    atom="cmap_P_UnicodePrivateUse_lig"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="No characters are mapped in the Unicode Private Use area except the 'fl' and/or 'fi' ligatures"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0314"
    atom="cmap_P_NonMacSubtableLanguage"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="All non mac subtables have a language field of zero"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0400"
    atom="cvt_P_length_even"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The length of the cvt table is an even number of bytes"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0500"
    atom="DSIG_P_Formats"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="All signature blocks were in format 1"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0501"
    atom="DSIG_P_Reserved"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="All signature blocks' reserved values were 0"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0502"
    atom="DSIG_P_VerifySignature"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The digital signature of the file verified correctly"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0600"
    atom="EBDT_P_version"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The version is 0x00020000"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0601"
    atom="EBDT_P_TableDependency"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The EBLC table is present"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0602"
    atom="EBDT_P_GlyphImageData"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The glyph image data is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0700"
    atom="EBLC_P_bitDepth"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Each bitmapSizeTable's bitDepth field was valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0701"
    atom="EBLC_P_indexSubTableArrayOffset"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Each bitmapSizeTable's indexSubTableArrayOffset field is in a valid range"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0702"
    atom="EBLC_P_version"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The version is 0x00020000"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0703"
    atom="EBLC_P_TableDependency"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The EBDT table is also present"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0704"
    atom="EBLC_P_BitmapSizeTableIndexOrder"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Each bitmapSizeTable's indices are ordered okay"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0705"
    atom="EBLC_P_indexSubTables"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The index subtable is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0706"
    atom="EBLC_P_numSizes"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The number of sizes in the EBLC table fits table size."
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0800"
    atom="EBSC_P_TableLength"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The table length equals the calculated value"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0801"
    atom="EBSC_P_version"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The version is 0x00020000"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0802"
    atom="EBSC_P_TableDependency"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Required bitmap tables present (EBLC and EBDT)"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P0803"
    atom="EBSC_P_StrikeSize"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="All substitue bitmap stikes are present"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1000"
    atom="gasp_P_rangeGaspBehavior"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="All of the rangeGaspBehavior fields contain valid flags"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1001"
    atom="gasp_P_Sentinel"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The gaspRange array has a 0xFFFF sentinel"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1002"
    atom="gasp_P_SortOrder"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The gaspRange array is in sorted order"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1003"
    atom="gasp_P_Version"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The version number is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1004"
    atom="gasp_P_AdjRangeIdenticalFlags"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="No adjacent ranges have identical flags"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1200"
    atom="hdmx_P_DeviceRecordPadBytes_none"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="There are no DeviceRecord padding bytes"
    fwLinkID="0"
    tableName="hdmx">
    <problem/>
</item>

<item
    helpID="P1201"
    atom="hdmx_P_DeviceRecordPadBytes_zero"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The DeviceRecord padding bytes are 0"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1202"
    atom="hdmx_P_DuplicateDeviceRecords"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="There are no duplicate DeviceRecords"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1203"
    atom="hdmx_P_SizeofDeviceRecord"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The SizeofDeviceRecord matches the calculated value"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1204"
    atom="hdmx_P_SortedOrder"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The DeviceRecords are sorted in ascending order"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1205"
    atom="hdmx_P_Version"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The version number is 0"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1206"
    atom="hdmx_P_Widths"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The hdmx widths match the calculated widths"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1207"
    atom="hdmx_P_TableLength"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The table length is correct"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1208"
    atom="hdmx_P_NumDeviceRecords"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The number of device records is non-negative"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1300"
    atom="head_P_created_0"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The created time is not zero"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1301"
    atom="head_P_flags_bit14"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Reserved bit 14 of the flags field is clear"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1302"
    atom="head_P_flags_bit15"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Reserved bit 15 of the flags field is clear"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1303"
    atom="head_P_flags_bit4_0_hdmx"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Non-linear scaling flag (bit 4) is clear, and hdmx table is not present"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1304"
    atom="head_P_flags_bit4_0_LTSH"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Non-linear scaling flag (bit 4) is clear, and LTSH table is not present"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1305"
    atom="head_P_flags_bit4_1_hdmx"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Non-linear scaling flag (bit 4) is set, and hdmx table is present"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1306"
    atom="head_P_flags_bit4_1_LTSH"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Non-linear scaling flag (bit 4) is set, and LTSH table is present"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1307"
    atom="head_P_FontChecksum"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Font checksum is correct"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1308"
    atom="head_P_fontDirectionHint"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The fontDirectionHint is in the range -2..2"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1309"
    atom="head_P_glyphDataFormat"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The glyphDataFormat value is 0"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1310"
    atom="head_P_indexToLocFormat_ignore"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The indexToLocFormat value is ignored in a CFF font"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1311"
    atom="head_P_indexToLocFormat_match"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The indexToLocFormat value matches the loca table"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1312"
    atom="head_P_indexToLocFormat_range"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The indexToLocFormat value is 0 or 1"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1313"
    atom="head_P_lowestRecPPEM"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The lowestRecPPEM value is in a reasonable range"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1314"
    atom="head_P_macStyleBold_OS2"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The macStyle bold bit matches the OS/2 fsSelection bit"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1316"
    atom="head_P_macStyleBold_subfamily"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The macStyle bold bit matches the name table's font subfamily string"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1318"
    atom="head_P_macStyleItal_OS2"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The macStyle italic bit matches the OS/2 fsSelection bit"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1319"
    atom="head_P_macStyleItal_post"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The macStyle italic bit matches the post table italic angle"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1320"
    atom="head_P_macStyleItal_subfamily"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The macStyle italic bit matches the name table's font subfamily string"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1321"
    atom="head_P_MagicNumber"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The magic number is 0x5f0f3cf5"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1322"
    atom="head_P_modified_0"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The modified time is not zero"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1323"
    atom="head_P_TableLength"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Table length is 54 bytes"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1324"
    atom="head_P_TableVersion"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The table version number is 0x00010000"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1325"
    atom="head_P_unitsPerEm"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The unitsPerEm value is a power of two in the range 64..16384"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1326"
    atom="head_P_xMax_glyf"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The xMax value matches the maximum glyph xMax"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1327"
    atom="head_P_xMin_glyf"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The xMin value matches the minimum glyph xMin"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1328"
    atom="head_P_yMax_glyf"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The yMax value matches the maximum glyph yMax"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1329"
    atom="head_P_yMin_glyf"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The yMin value matches the minimum glyph yMin"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1330"
    atom="head_P_fontRevision"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="fontRevision is consistent with the font's version string"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1400"
    atom="hhea_P_advanceWidthMax"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The advanceWidthMax field equals the calculated value"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1401"
    atom="hhea_P_metricDataFormat"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The metricDataFormat field is set to zero"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1402"
    atom="hhea_P_minLeftSideBearing"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The minLeftSideBearing field equals the calculated value"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1403"
    atom="hhea_P_minRightSideBearing"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The minRightSideBearing field equals the calculated value"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1404"
    atom="hhea_P_numberOfHMetrics"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The numberOfHMetrics value is consistent with the length of the hmtx table"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1405"
    atom="hhea_P_reserved"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The reserved fields are all set to zero"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1406"
    atom="hhea_P_version"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The table version number is 0x00010000"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1407"
    atom="hhea_P_xMaxExtent"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The xMaxExtent field equals the calculated value"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1408"
    atom="hhea_P_caretSlopeAngle_italicAngle"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The caretSlope angle matches the post.italicAngle"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1409"
    atom="hhea_P_AscenderPositive"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The Ascender value is greater than zero"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1410"
    atom="hhea_P_Ascender_yMax"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Ascender is less than or equal to head.yMax"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1411"
    atom="hhea_P_DescenderNegative"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The Descender is less than zero"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1412"
    atom="hhea_P_Descender_yMin"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Descender is greater than or equal to head.yMin"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1413"
    atom="hhea_P_LineGapPositive"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="LineGap is greater than or equal to 0"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1414"
    atom="hhea_P_LineGap_minGap"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The LineGap is greater to or equal the minimum recommended value"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1415"
    atom="hhea_P_Ascender_usWinAscent"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Ascender is same value as OS/2.usWinAscent"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1416"
    atom="hhea_P_Descender_usWinDescent"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Descender value is the same as OS/2.usWinDescent"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1500"
    atom="hmtx_P_CheckMetrics"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The horizontal metrics are all within an allowable range of values"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1501"
    atom="hmtx_P_TableSize"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The size of the table matches the calculated size"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1600"
    atom="kern_P_Format0_SearchFields"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="All subtables' searchRange, entrySelector, and rangeShift fields are valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1601"
    atom="kern_P_NumSubTables"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The number of subtables is not 0"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1602"
    atom="kern_P_ReservedCoverageBits"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="All subtables had their reserved coverage bits set to 0"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1603"
    atom="kern_P_SubtableFormats"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The subtable formats were all 0 or 2"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1604"
    atom="kern_P_SubtableLengths"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="All subtable's lengths match the calculated lengths"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1605"
    atom="kern_P_TableVersion"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The table version was 0"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1606"
    atom="kern_P_Format0_GlyphIDs"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="All the glyph IDs in the format 0 subtable are in a valid range"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1607"
    atom="kern_P_Format0_Values"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="All the kerning values in the format 0 subtable are in a valid range"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1608"
    atom="kern_P_Format0_GlyphIdInCmap"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Every kern pair in the format 0 subtable has its glyph IDs mapped in the cmap table"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1700"
    atom="loca_P_Format"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Correct format of loca (0 or 1)"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1701"
    atom="loca_P_GlyfEntryEmpty"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Loca does not contain references to zero-length entries in glyf table"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1702"
    atom="loca_P_GlyfEntryLengthAlignment"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Loca references a glyf entry which length is not a multiple of 4"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1703"
    atom="loca_P_GlyfPartiallyUnreferenced"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="All glyphs in the glyf table are referenced by the loca table"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1704"
    atom="loca_P_NumEntries"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The number of entries is equal to (maxp.numGlyphs + 1)"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1705"
    atom="loca_P_OffsetsIncreasing"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The entries are sorted in ascending order"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1706"
    atom="loca_P_OffsetWithinGlyfRange"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="All entries point within range of the glyf table"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1800"
    atom="LTSH_P_numGlyphs"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The numGlyphs field equals maxp.numGlyphs"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1801"
    atom="LTSH_P_TableLength"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The calculated table length matches the actual table length"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1802"
    atom="LTSH_P_version"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The version number is 0"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1803"
    atom="LTSH_P_yPels"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="All LTSH yPel values match the calculated values"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1900"
    atom="maxp_P_Calculation"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The points, contours, and component values match the calculated values"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1901"
    atom="maxp_P_LENGTH_0_5"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Table version is 0x00005000 and the table is 6 bytes long"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1902"
    atom="maxp_P_LENGTH_1_0"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Table version is 1.0 and the table is 32 bytes long"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1903"
    atom="maxp_P_NumGlyphsMatchLoca"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The numGlyphs value equals the number of entries in the loca array plus one"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1904"
    atom="maxp_P_VERSION_0_5"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Table version is 0x00005000, CFF table is present, no glyf table is present"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P1905"
    atom="maxp_P_VERSION_1_0"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Table version is 1.0 and a glyf table is present and no CFF table is present"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2000"
    atom="name_P_BothPlatforms"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The table contains strings for both Mac and Microsoft platforms"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2001"
    atom="name_P_FormatSelector"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The format selector field is 0"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2002"
    atom="name_P_MSLanguageID"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="All Microsoft unicode strings had valid Language IDs"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2003"
    atom="name_P_NameRecordsSorted"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The NameRecords array is in sorted order"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2004"
    atom="name_P_PlatformSpecificEncoding"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="All strings had valid Platform Specific Encoding IDs"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2005"
    atom="name_P_Postscript"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The PostScript strings are correctly formatted"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2006"
    atom="name_P_ReservedNameID"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="No name records are using reserved Name IDs"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2007"
    atom="name_P_StringsWithinTable"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="No strings extended past the end of the table"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2008"
    atom="name_P_UnicodeLength"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The length of every unicode string is an even # of bytes"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2009"
    atom="name_P_VersionStringFormat"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The version string is in the correct format"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2010"
    atom="name_P_subfamily"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The subfamily string is consistent with the style of the font"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2011"
    atom="name_P_sample"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The sample string is composed of characters that are mapped in the font"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2012"
    atom="name_P_CopyrightConsistent"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="No inconsistencies were found for Copyright strings"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2013"
    atom="name_P_DescriptionConsistent"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="No inconsistencies were found for Description strings"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2014"
    atom="name_P_TrademarkConsistent"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="No inconsistencies were found for Trademark strings"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2015"
    atom="name_P_NoFormat14"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="No name record specified Unicode Variation Sequences cmap subtable"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2100"
    atom="OS_2_P_CharIndexes"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The usFirstCharIndex and usLastCharIndex fields are valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2101"
    atom="OS_2_P_CodePageRanges"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The CodePage Range fields' bits are all allowable values"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2102"
    atom="OS_2_P_fsSelection"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The fsSelection field appears to be valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2103"
    atom="OS_2_P_fsType"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The fsType field is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2104"
    atom="OS_2_P_Panose"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="All panose values are in a valid range"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2105"
    atom="OS_2_P_sCapHeight_nonzero"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The sCapHeight field is nonzero"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2106"
    atom="OS_2_P_sCapHeight_zero"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The sCapHeight field is zero, and U+0048 is not mapped to a glyf"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2107"
    atom="OS_2_P_sFamilyClass"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The sFamilyClass Class ID and Subclass ID values are in a valid range"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2108"
    atom="OS_2_P_Strikeout"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The yStrikeoutSize and yStrikeoutPosition appear valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2109"
    atom="OS_2_P_SuperscriptSubscript"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="All subscript and superscript values appear valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2110"
    atom="OS_2_P_sxHeight_nonzero"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The sxHeight field is nonzero"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2111"
    atom="OS_2_P_sxHeight_zero"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The sxHeight field is zero, and U+0078 is not mapped to a glyf"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2112"
    atom="OS_2_P_TableLength"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The table length matches the expected length for this version"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2113"
    atom="OS_2_P_UnicodeRanges"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The Unicode Range fields' bits are all allowable values"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2114"
    atom="OS_2_P_usBreakChar_mapped"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The usBreakChar is mapped to a glyf"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2115"
    atom="OS_2_P_usDefaultChar_nonzero"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The usDefaultChar field is nonzero, and the character is mapped to a glyf"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2116"
    atom="OS_2_P_usDefaultChar_zero"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The usDefaultChar field is zero"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2117"
    atom="OS_2_P_Version"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The version number is valid and is the current version number"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2118"
    atom="OS_2_P_WeightClass"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The usWeightClass is a valid value"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2119"
    atom="OS_2_P_WidthClass"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The width class is a valid value"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2120"
    atom="OS_2_P_xAvgCharWidth"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The xAvgCharWidth field equals the calculated value"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2122"
    atom="OS_2_P_WeightClass_PANOSE"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The usWeightClass is consistent with the PANOSE weight value"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2123"
    atom="OS_2_P_sTypoAscenderDescender"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The sTypoAscender and sTypoDescender fields are reasonable values"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2124"
    atom="OS_2_P_usMaxContext"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The usMaxContext field matches the calculated value"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2200"
    atom="PCLT_P_Pitch"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The Pitch field equals the width of the space character"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2201"
    atom="PCLT_P_Reserved"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The Reserved field is zero"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2202"
    atom="PCLT_P_SerifStyle"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The SerifStyle values are in a valid range"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2203"
    atom="PCLT_P_StrokeWeight"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The StrokeWeight value was in the range of -7 to 7"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2204"
    atom="PCLT_P_Style"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="All reserved bits in the Style field were set to zero"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2205"
    atom="PCLT_P_TableLength"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The table length is 54 bytes"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2206"
    atom="PCLT_P_Version"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The version is 0x00010000"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2207"
    atom="PCLT_P_WidthType"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The WidthType value was in the range of -5 to 5"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2300"
    atom="post_P_glyphNameIndex"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The glyphNameIndex array contains valid indexes"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2301"
    atom="post_P_isFixedPitch"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The isFixedPitch field is consistent with other table(s)"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2302"
    atom="post_P_italicAngle"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The italicAngle value is reasonable and consistent with other tables"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2303"
    atom="post_P_names"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The names in the post table are consistent with the Adobe Glyph List names"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2304"
    atom="post_P_TableLength"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The table length is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2305"
    atom="post_P_underlinePosition"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The underlinePosition value is not less than hhea.Descender"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2306"
    atom="post_P_underlineThickness"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The underlineThickness value is reasonable"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2307"
    atom="post_P_v2_numberOfGlyphs"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The numberOfGlyphs field equals maxp.numGlyphs"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2308"
    atom="post_P_Version"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The version number is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2500"
    atom="VDMX_P_CalcData"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The VDMX data matches the data calculated by the rasterizer"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2501"
    atom="VDMX_P_GroupsInTable"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="All of the VDMX groups are within the table"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2502"
    atom="VDMX_P_Offsets"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="All of the offsets to VDMX groups were in a valid range"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2503"
    atom="VDMX_P_Version"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The version number is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2600"
    atom="vhea_P_metricDataFormat"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The metricDataFormat field is set to zero"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2601"
    atom="vhea_P_ReservedFields"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The reserved fields are all set to zero"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2602"
    atom="vhea_P_version"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The version is number is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2700"
    atom="vmtx_P_TableLength"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The table length is correct"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2800"
    atom="VORG_P_CFF_Font"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The font is a CFF font"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P2801"
    atom="VORG_P_Version"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The major.minor version is 1.0"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4000"
    atom="GDEF_P_AttachListTable_AttachPointArray"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The offsets in the AttachPoint array are valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4001"
    atom="GDEF_P_AttachListTable_CoverageOffset"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The Coverage offset is nonzero and points within the GDEF table"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4002"
    atom="GDEF_P_HeaderOffsets"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="All header offsets point within the table"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4003"
    atom="GDEF_P_LigCaretListTable_CoverageOffset"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The Coverage offset is nonzero and points within the GDEF table"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4004"
    atom="GDEF_P_LigCaretListTable_LigGlyphArray"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The offsets in the LigGlyph array are valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4005"
    atom="GDEF_P_LigGlyphTable_CaretValueArray"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The offsets in the CaretValue array are valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4006"
    atom="GDEF_P_Version"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The version numbers 0x00010000, 0x00010002 or 0x00010003 are okay"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4100"
    atom="GPOS_P_AnchorTable"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The Anchor table is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4101"
    atom="GPOS_P_BaseArrayTable"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The BaseArray table is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4102"
    atom="GPOS_P_BaseRecord"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The BaseRecord is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4103"
    atom="GPOS_P_ChainContextPos"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The ChainContextPos subtable is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4104"
    atom="GPOS_P_ChainPosClassRule"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The ChainPosClassRule table is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4105"
    atom="GPOS_P_ChainPosClassSet"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The ChainPosClassSet table is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4106"
    atom="GPOS_P_ChainPosRule"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The ChainPosRule table is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4107"
    atom="GPOS_P_ChainPosRuleSet"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The ChainPosRuleSet table is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4108"
    atom="GPOS_P_Class1Record"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The Class1Record is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4109"
    atom="GPOS_P_Class2Record"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The Class2Record is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4110"
    atom="GPOS_P_ComponentRecord"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The ComponentRecord is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4111"
    atom="GPOS_P_ContextPos"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The ContextPos subtable is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4112"
    atom="GPOS_P_CursivePos"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The CursivePos subtable is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4113"
    atom="GPOS_P_EntryExit"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The EntryExit record is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4114"
    atom="GPOS_P_ExtensionPos"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The ExtensiontPos subtable is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4115"
    atom="GPOS_P_HeaderOffsets"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="All header offsets point within the table"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4116"
    atom="GPOS_P_LigatureArrayTable"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The LigatureArray table is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4117"
    atom="GPOS_P_LigatureAttachTable"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The LigatureAttach table is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4118"
    atom="GPOS_P_Mark2ArrayTable"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The Mark2Array table is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4119"
    atom="GPOS_P_Mark2Record"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The Mark2Record is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4120"
    atom="GPOS_P_MarkArrayTable"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The MarkArray table is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4121"
    atom="GPOS_P_MarkBasePos"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The MarkBasePos subtable is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4122"
    atom="GPOS_P_MarkLigPos"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The MarkLigPos subtable is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4123"
    atom="GPOS_P_MarkMarkPos"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The MarkMarkPos subtable is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4124"
    atom="GPOS_P_PairPos"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The PairPos subtable is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4125"
    atom="GPOS_P_PairSet"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The PairSet table is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4127"
    atom="GPOS_P_PosClassSet"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The PosClassSet table is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4128"
    atom="GPOS_P_PosRule"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The PosRule table is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4129"
    atom="GPOS_P_PosRuleSet"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The PosRuleSet table is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4130"
    atom="GPOS_P_SinglePos"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The SinglePos subtable is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4131"
    atom="GPOS_P_ValueRecord"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The ValueRecord subtable is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4132"
    atom="GPOS_P_Version"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The version number is 0x00010000"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4200"
    atom="GSUB_P_AlternateSubst"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The AlternateSubst subtable is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4201"
    atom="GSUB_P_ChainContextSubst"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The ChainContextSubst subtable is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4202"
    atom="GSUB_P_ContextSubst"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The ContextSubst subtable is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4203"
    atom="GSUB_P_ExtensionSubst"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The ExtensionSubst subtable is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4204"
    atom="GSUB_P_HeaderOffsets"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="All header offsets point within the table"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4205"
    atom="GSUB_P_LigatureSubst"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The LigatureSubst subtable is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4206"
    atom="GSUB_P_MultipleSubst"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The MultipleSubst subtable is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4207"
    atom="GSUB_P_SingleSubst"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The SingleSubst subtable is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4208"
    atom="GSUB_P_Version"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The version number is 0x00010000"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4209"
    atom="GSUB_P_ReverseChainContextSubst"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The ReverseChainSingleSubst subtable is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4300"
    atom="BASE_P_AxisTable_BaseScriptListOffset_valid"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The Axis Table's BaseScriptListOffset is within a valid range"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4301"
    atom="BASE_P_AxisTable_BaseTagListOffset_null"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The Axis Table's BaseTagListOffset is null"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4302"
    atom="BASE_P_AxisTable_BaseTagListOffset_valid"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The Axis Table's BaseTagListOffset is within a valid range"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4303"
    atom="BASE_P_BaseCoordTable_format"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The format of the BaseCoord table is a valid value"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4304"
    atom="BASE_P_BaseLangSysRecord_offsets"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The BaseLangSysRecord array's MinMax offsets were all within a valid range"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4305"
    atom="BASE_P_BaseLangSysRecord_order"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The BaseScript Table's BaseLangSysRecord array is in alphabetical order"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4306"
    atom="BASE_P_BaseScriptList_Offset"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="All BaseScript offsets are in a valid range"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4307"
    atom="BASE_P_BaseScriptList_Order"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The BaseScriptList table's BaseScriptRecords are in alphabetical order"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4308"
    atom="BASE_P_BaseTagList_TagOrder"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The tags in the BaseTagList table are in alphabetical order"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4309"
    atom="BASE_P_BaseTagList_TagValid"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="All the tags in the BaseTagList table were valid tags"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4311"
    atom="BASE_P_BaseValuesOffset_null"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The BaseValues offset in the BaseScript table is null"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4312"
    atom="BASE_P_BaseValuesTable_BCO"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The BaseCoord offsets in the BaseValues table are all within a valid range"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4313"
    atom="BASE_P_DefaultMinMaxOffset"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The DefaultMinMax offset in the BaseScript table is in a valid range"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4314"
    atom="BASE_P_DefaultMinMaxOffset_null"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The DefaultMinMax offset in the BaseScript table is null"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4315"
    atom="BASE_P_FeatMinMaxRecords_offsets"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The MinMax table's FeatMinMaxRecord array contains valid offsets"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4316"
    atom="BASE_P_HorizAxisOffset_null"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The HorizAxisOffset value is null"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4317"
    atom="BASE_P_HorizAxisOffset_valid"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The HorizAxisOffset value is within the BASE table"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4318"
    atom="BASE_P_MinMaxTable_MaxCO"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The MaxCoord offset of the MinMax table is within range"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4319"
    atom="BASE_P_MinMaxTable_MaxCO_0"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The MaxCoord offset of the MinMax table is zero"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4320"
    atom="BASE_P_MinMaxTable_MinCO"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The MinCoord offset of the MinMax table is within range"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4321"
    atom="BASE_P_MinMaxTable_MinCO_0"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The MinCoord offset of the MinMax table is zero"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4322"
    atom="BASE_P_Version"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The version number is 0x00010000"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4323"
    atom="BASE_P_VertAxisOffset_null"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The VertAxisOffset value is null"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4324"
    atom="BASE_P_VertAxisOffset_valid"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The VertAxisOffset value is within the BASE table"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P4400"
    atom="JSTF_P_Version"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The version number is 0x00010000"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P5000"
    atom="_OTL_ClassDefinitionTable_P_valid"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The Class Definition Table is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P5100"
    atom="_OTL_CoverageTable_P_valid"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The Coverage Table is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P5200"
    atom="_OTL_DeviceTable_P_valid"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The device table is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P5300"
    atom="_OTL_FeatureListTable_P_valid"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The FeatureList table is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P5400"
    atom="_OTL_FeatureTable_P_valid"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The Feature table is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P5500"
    atom="_OTL_LangSysTable_P_valid"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The LangSysTable is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P5600"
    atom="_OTL_LookupListTable_P_valid"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The LookupList table is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P5700"
    atom="_OTL_LookupTable_P_valid"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The Lookup table is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P5800"
    atom="_OTL_ScriptListTable_P_valid"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The ScriptList Table is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P5900"
    atom="_OTL_ScriptTable_P_valid"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The Script Table is valid"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="P6000"
    atom="_rast_P_rasterization"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="No problems were found during rasterization testing"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem/>
</item>

<item
    helpID="W0020"
    atom="_FONT_W_OptimalOrder"
    linkTitle="Recommendations for OpenType fonts"
    specLink="http://www.microsoft.com/typography/otspec/recom.htm"
    shortDesc="Tables are not in optimal order"
    fwLinkID="10367"
    tableName="Font">
    <problem>OpenType fonts with TrueType outlines are most efficiently utilized by Windows when the tables are ordered as follows (from first to last):&lt;BR&gt;head, hhea, maxp, OS/2, hmtx, LTSH, VDMX, hdmx, cmap, fpgm, prep, cvt, loca, glyf, kern, name, post, gasp, PCLT, DSIG&lt;BR&gt;&lt;BR&gt;The initial loading of an OpenType font containing CFF data will be more efficient if the following table ordering is used within the body of the font (from first to last):&lt;BR&gt;head, hhea, maxp, OS/2, name, cmap, post, CFF, other tables (as convenient)&lt;BR&gt;&lt;BR&gt;This efficiency results from the operating system being able to access commonly used information without having to move between 'pages' of data in memory. Therefore, the efficiency gained by Windows applies to implementations of the rasterizer on other operating systems that use a paging architecture.&lt;BR&gt;&lt;BR&gt;To reorder the tables of a font, use the FastFont tool (available from Microsoft). You will need to create a text file containing table tags in the order in which you want them, and then reference this text file as a parameter of the FastFont tool. (The default order in which tables are placed by FastFont is antiquated.) Tables not included in the list above should be placed at the end of the table before the font is signed (and a DSIG table is appended as the last table in the font). If two tables are dependent on each other (like vhea/vmtx) then they should be placed next to each other.</problem>
</item>

<item
    helpID="W0021"
    atom="_FONT_W_UnnecessaryTable"
    linkTitle="details about OpenType files"
    specLink="http://www.microsoft.com/typography/otspec/otff.htm"
    shortDesc="Table is unnecessary"
    fwLinkID="10363"
    tableName="Font">
    <problem>Depending on the typeface and coverage of a font, certain tables are not necessary to have in the font file. For example, in a purely Latin (WinAnsi) font, the vhea (vertical header) and vmtx (vertical metrics) tables are not necessary.</problem>
</item>

<item
    helpID="W0022"
    atom="_FONT_W_MissingRecommendedTable"
    linkTitle="details about OpenType files"
    specLink="http://www.microsoft.com/typography/otspec/otff.htm"
    shortDesc="Recommended table is missing"
    fwLinkID="10363"
    tableName="Font">
    <problem>Depending on the typeface and coverage of a font, certain tables are recommended for optimum quality. For example, the performance of a non-linear font is improved if the VDMX, LTSH, and hdmx tables are present (use the CacheTT tool to calculate these values and create these tables). Non-monospaced Latin fonts should have a kern table. A gasp table is necessary if a designer wants to influence the sizes at which grayscaling is used under Windows. A DSIG table containing a digital signature helps ensure the integrity of the font file. Etc.</problem>
</item>

<item
    helpID="W0023"
    atom="_FONT_W_FONTNAME_CHARS"
    linkTitle="details about OpenType files"
    specLink="http://www.microsoft.com/typography/otspec/otff.htm"
    shortDesc="Unusual characters in FontName"
    fwLinkID="10363"
    tableName="Font">
    <problem>Unusual characters detected in FontName. Please check that this is necessary.</problem>
</item>

<item
    helpID="W0024"
    atom="_FONT_W_FONTVERSION_CHARS"
    linkTitle="details about OpenType files"
    specLink="http://www.microsoft.com/typography/otspec/otff.htm"
    shortDesc="Unusual characters in FontVersion"
    fwLinkID="10363"
    tableName="Font">
    <problem>Unusual characters detected in FontVersion. Please check that this is necessary.</problem>
</item>

<item
    helpID="W0030"
    atom="_DE_W_TableAlignment"
    linkTitle="details about OpenType files"
    specLink="http://www.microsoft.com/typography/otspec/otff.htm"
    shortDesc="The directory entry table offset is not a multiple of 4"
    fwLinkID="10363"
    tableName="Table Directory">
    <problem>All tables should be aligned to begin at offsets which are multiples of four bytes. While this is not required by the TrueType rasterizer, it does prevent ambiguous checksum calculations and greatly speeds table access on some processors.&lt;BR&gt;
All tables should be recorded in the table directory with their actual length. To ensure that checksums are calculated correctly, it is suggested that tables begin on LONG word boundries. Any extra space after a table (and before the next LONG word boundary) should be padded with zeros.</problem>
</item>

<item
    helpID="W0031"
    atom="_DE_W_PadBytesNotZero"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Non-zero pad bytes were found for the table"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="W0050"
    atom="_TEST_W_ErrorInAnotherTable"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Cannot perform test due to an error in another table"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="W0051"
    atom="_TEST_W_OtherErrorsInTable"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Cannot perform test due to other errors in this table"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="W0300"
    atom="cmap_W_AppleLogo"
    linkTitle="cmap table specification"
    specLink="http://www.microsoft.com/typography/otspec/cmap.htm"
    shortDesc="Character code 240, the Apple logo, isn't mapped to missing glyph in cmap 1,0 (legal requirement for Microsoft fonts)"
    fwLinkID="10339"
    tableName="cmap">
    <problem>Microsoft fonts developed for use on Apple platforms (platform 1, encoding 0) must map the Apple logo (character code 240) to the missing glyph in the cmap table.</problem>
</item>

<item
    helpID="W0301"
    atom="cmap_W_AppleLogo_NoMap"
    linkTitle="cmap table specification"
    specLink="http://www.microsoft.com/typography/otspec/cmap.htm"
    shortDesc="Apple logo mapping test not performed, cmap 1,0 not present"
    fwLinkID="10339"
    tableName="cmap">
    <problem>Because there is not an Apple-platform subtable present in the font (platform 1, encoding id 0), the mapping test for the Apple logo was not performed.</problem>
</item>

<item
    helpID="W0302"
    atom="cmap_W_AppleMSSupport_A"
    linkTitle="cmap table specification"
    specLink="http://www.microsoft.com/typography/otspec/cmap.htm"
    shortDesc="The table does not contain any Apple subtables"
    fwLinkID="10339"
    tableName="cmap">
    <problem>For Microsoft fonts, at least two subtables are required within the cmap table: Format 4 (Windows) and Format 0 (Macintosh) subtables.&lt;BR&gt;&lt;BR&gt;Format 4 is a Windows subtable which uses platform id 3 and encoding id 1 if the font is a text face, and encoding id 0 if the font is a symbol font. This format supports two-byte glyph indices.&lt;BR&gt;&lt;BR&gt;Format 0 is a Macintosh subtable and uses platform id 1 and encoding id 0. This format supports single-byte glyph indices.</problem>
</item>

<item
    helpID="W0303"
    atom="cmap_W_AppleMSSupport_M"
    linkTitle="cmap table specification"
    specLink="http://www.microsoft.com/typography/otspec/cmap.htm"
    shortDesc="The table does not contain any Microsoft subtables"
    fwLinkID="10339"
    tableName="cmap">
    <problem>For Microsoft fonts, at least two subtables are required within the cmap table: Format 4 (Windows) and Format 0 (Macintosh) subtables.&lt;BR&gt;&lt;BR&gt;Format 4 is a Windows subtable which uses platform id 3 and encoding id 1 if the font is a text face, and encoding id 0 if the font is a symbol font. This format supports two-byte glyph indices.&lt;BR&gt;&lt;BR&gt;Format 0 is a Macintosh subtable and uses platform id 1 and encoding id 0. This format supports single-byte glyph indices.</problem>
</item>

<item
    helpID="W0304"
    atom="cmap_W_EuroGlyph_Mac"
    linkTitle="cmap table specification"
    specLink="http://www.microsoft.com/typography/otspec/cmap.htm"
    shortDesc="Character code 219, the euro character, is not mapped in cmap 1,0"
    fwLinkID="10339"
    tableName="cmap">
    <problem>The Euro glyph is required for all Microsoft fonts. The glyph should be mapped to Unicode U+20AC, and Macintosh character code 219.</problem>
</item>

<item
    helpID="W0305"
    atom="cmap_W_EuroGlyph_Uni"
    linkTitle="cmap table specification"
    specLink="http://www.microsoft.com/typography/otspec/cmap.htm"
    shortDesc="Character code U+20AC, the euro character, is not mapped in cmap 3,1"
    fwLinkID="10339"
    tableName="cmap">
    <problem>The Euro glyph is required for all Microsoft fonts. The glyph should be mapped to Unicode: U+20AC, and Macintosh character code: x00DB</problem>
</item>

<item
    helpID="W0306"
    atom="cmap_W_f12_EncID"
    linkTitle="cmap table specification"
    specLink="http://www.microsoft.com/typography/otspec/cmap.htm"
    shortDesc="The format is 12, but the (platform, encoding) id is not (3,10), (0,4) or (0,6)"
    fwLinkID="10339"
    tableName="cmap">
    <problem>Fonts providing Unicode encoded UCS-4 character support for Win2000 and later need to have a format 4 subtable using platform 3, encoding 1, as well as have a format 12 subtable using platform 3, encoding 10, or using platform 0 encoding 4 or 6.</problem>
</item>

<item
    helpID="W0307"
    atom="cmap_W_UnicodePrivateUse"
    linkTitle="cmap table specification"
    specLink="http://www.microsoft.com/typography/otspec/cmap.htm"
    shortDesc="Characters are mapped in the Unicode Private Use area"
    fwLinkID="10339"
    tableName="cmap">
    <problem>Characters are mapped to the Private Use Area. Microsoft recommends that use of the PUA is avoided. For Microsoft fonts, any alternate glyphs, OpenType glyphs, or unused glyphs should NOT be mapped in the Private Use Area. These glyphs should remain unmapped.&lt;BR&gt;&lt;BR&gt;For legacy reasons, the 'fi' and 'fl' ligatures are the only glyphs that should be mapped in this area, as follows:&lt;BR&gt;&lt;BR&gt;fi ligature&lt;BR&gt;Unicode: U+FB01 and U+F001&lt;BR&gt;&lt;BR&gt;fl ligature&lt;BR&gt;Unicode: U+FB02 and U+F002</problem>
</item>

<item
    helpID="W0344"
    atom="cmap_W_f14_NonPacked"
    linkTitle="cmap table specification"
    specLink="WARNING: field missing"
    shortDesc="Format 14 tables not packed"
    fwLinkID="10339"
    tableName="cmap">
    <problem>The region of non-default and default UVS tables following the Variation Selector records is not packed. This may indicated corrupted data</problem>
</item>

<item
    helpID="W0500"
    atom="DSIG_W_VerifySignature_Generic"
    linkTitle="DSIG table specification"
    specLink="http://www.microsoft.com/typography/otspec/dsig.htm"
    shortDesc="DSIG Warning"
    fwLinkID="10341"
    tableName="DSIG">
    <problem>Catch-all Place Holder for Generic DSIG Warnings</problem>
</item>

<item
    helpID="W1000"
    atom="gasp_W_AdjRangeIdenticalFlags"
    linkTitle="gasp table specification"
    specLink="http://www.microsoft.com/typography/otspec/gasp.htm"
    shortDesc="Two adjacent ranges have identical flags"
    fwLinkID="10346"
    tableName="gasp">
    <problem>Two adjacent size ranges specified in the gasp table are using the same settings for grid fitting and grayscale rendering. Check that the gasp flag settings are correct for both ranges, or whether it may be possible to combine the two ranges into a single range.</problem>
</item>

<item
    helpID="W1100"
    atom="glyf_W_CompositeReservedBit"
    linkTitle="glyf table specification"
    specLink="http://www.microsoft.com/typography/otspec/glyf.htm"
    shortDesc="Reserved bit is set to 1"
    fwLinkID="10348"
    tableName="glyf">
    <problem>A composite glyph description contained in the glyf table has bit 4 of the flag field incorrectly set to 1. This bit should be set to 0.</problem>
</item>

<item
    helpID="I1100"
    atom="glyf_I_IDENTICAL_GLYF_TABLES_IN_TTC"
    linkTitle="glyf table specification"
    specLink="http://www.microsoft.com/typography/otspec/glyf.htm"
    shortDesc="No need to check identical glyf or EBDT tables in TTC beyond the first member"
    fwLinkID="10348"
    tableName="glyf">
    <problem>No need to check identical glyf or EBDT tables in TTC beyond the first member</problem>
</item>

<item
    helpID="W1200"
    atom="hdmx_W_Need_Newer_FreeType"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The Freetype version is too old"
    fwLinkID="0"
    tableName="hdmx">
    <problem>To calculate HDMX, LTSH and VDMX correctly, the minimum version of Freetype required is 2.6.1.</problem>
</item>

<item
    helpID="W1300"
    atom="head_W_created_0"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="The created time is zero"
    fwLinkID="10352"
    tableName="head">
    <problem>The time the font was created should be a 64-bit integer that equals the number of seconds since midnight, January 1, 1904. Use a table editing tool to correct this value.</problem>
</item>

<item
    helpID="W1301"
    atom="head_W_created_unlikely"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="The created time is an unlikely value"
    fwLinkID="10352"
    tableName="head">
    <problem>The time the font was created should be a 64-bit integer that equals the number of seconds since midnight, January 1, 1904. Use a table editing tool to correct this value.</problem>
</item>

<item
    helpID="W1302"
    atom="head_W_flags_bit4_1_hdmx"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="Non-linear scaling flag (bit 4) is set, but hdmx table is not present"
    fwLinkID="10352"
    tableName="head">
    <problem>Bit 4 of the flags field in the head table is set, indicating that the advance widths might not scale linearly (that is, hints applied to the glyphs might alter the advance widths). Regenerate this font.</problem>
</item>

<item
    helpID="W1303"
    atom="head_W_flags_bit4_1_LTSH"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="Non-linear scaling flag (bit 4) is set, but LTSH table is not present"
    fwLinkID="10352"
    tableName="head">
    <problem>Bit 4 of the flags field in the head table is set, indicating that the advance widths might not scale linearly (that is, hints applied to the glyphs might alter the advance widths). Regenerate this font.</problem>
</item>

<item
    helpID="W1304"
    atom="head_W_lowestRecPPEM_large"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="The lowestRecPPEM value may be unreasonably large"
    fwLinkID="10352"
    tableName="head">
    <problem>This value should indicate the smallest size (in pixels) at which the font is readable. The lowestRecPPEM value should be an indicator of the level at which the font is hinted. Use a head table editor to correct this value.</problem>
</item>

<item
    helpID="W1305"
    atom="head_W_lowestRecPPEM_small"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="The lowestRecPPEM value may be unreasonably small"
    fwLinkID="10352"
    tableName="head">
    <problem>This value should indicate the smallest size (in pixels) at which the font is readable. The lowestRecPPEM value should be an indicator of the level at which the font is hinted. This value is not required when bitmaps exist in the font for use at small sizes. Use a head table editor to correct this value.</problem>
</item>

<item
    helpID="W1310"
    atom="head_W_modified_0"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="The modified time is zero"
    fwLinkID="10352"
    tableName="head">
    <problem>The time the font was modified should be a 64-bit integer that equals the number of seconds since midnight, January 1, 1904. Check to ensure that the tool you are using to edit the font is producing this value correctly.</problem>
</item>

<item
    helpID="W1311"
    atom="head_W_modified_unlikely"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="The modified time is an unlikely value"
    fwLinkID="10352"
    tableName="head">
    <problem>The time the font was modified should be a 64-bit integer that equals the number of seconds since midnight, January 1, 1904. Check to ensure that the tool you are using to edit the font is producing this value correctly.</problem>
</item>

<item
    helpID="W1312"
    atom="head_W_unitsPerEM_LT64"
    linkTitle="Apple TrueType Reference Manual"
    specLink="http://developer.apple.com/fonts/TTRefMan/RM06/Chap6head.html"
    shortDesc="The unitsPerEm is less than 64 which is in violation of the Apple spec"
    fwLinkID="0"
    tableName="head">
    <problem>The Apple specification for TrueType fonts specifies that the range of possible values for unitsPerEm is 64-16384, and should be a power of 2.</problem>
</item>

<item
    helpID="W1313"
    atom="head_W_unitsPerEm_Pow2"
    linkTitle="head table specification"
    specLink="http://www.microsoft.com/typography/otspec/head.htm"
    shortDesc="The unitsPerEm value is not a power of two"
    fwLinkID="10352"
    tableName="head">
    <problem>Microsoft and Apple recommend that the unitsPerEm value of the font is a power of 2. Such a value allows font clients to efficiently perform calculations involving division.&lt;BR&gt;&lt;BR&gt;Microsoft considers a value of 2048 unitsPerEm to be ideal because it is a power of 2, a high enough value for good precision in rendering, and a low enough value to be processed efficiently.&lt;BR&gt;&lt;BR&gt;To learn more about these recommendations, see the &lt;A TARGET=&quot;top&quot; HREF=&quot;http://go.microsoft.com/fwlink?LinkID=10456&quot;&gt;Hinting and Production Guidelines Specification&lt;/A&gt;.</problem>
</item>

<item
    helpID="W1314"
    atom="head_W_fontRevision"
    linkTitle="head table specification"
    specLink="WARNING: field missing"
    shortDesc="fontRevision is not consistent with the font's version string"
    fwLinkID="10352"
    tableName="head">
    <problem>The fontRevision value in the head table should be consistent with the version string in the name table. The 'major' numbers should match and the 'minor' numbers should match to the thousandths place (when rounded and zero-padded).</problem>
</item>

<item
    helpID="W1400"
    atom="hhea_W_hmtx_invalid"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The advanceWidthMax, minLeftSideBearing, minRightSideBearing, and xMaxExtent fields can not be validated"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="I1401"
    atom="hhea_I_Ascender_yMax"
    linkTitle="hhea table specification"
    specLink="http://www.microsoft.com/typography/otspec/hhea.htm"
    shortDesc="Ascender should be less than or equal to head.yMax"
    fwLinkID="10353"
    tableName="hhea">
    <problem>For the most consistent performance between platforms, the hhea.ascender value should be less than or equal to the head.yMax value.</problem>
</item>

<item
    helpID="I1402"
    atom="hhea_I_Descender_yMin"
    linkTitle="hhea table specification"
    specLink="http://www.microsoft.com/typography/otspec/hhea.htm"
    shortDesc="Descender should be greater than or equal to head.yMin"
    fwLinkID="10353"
    tableName="hhea">
    <problem>For the most consistent performance between platforms, the hhea.descender value should be greater than or equal to the head.yMin value.</problem>
</item>

<item
    helpID="W1403"
    atom="hhea_W_LineGapPositive"
    linkTitle="hhea table specification"
    specLink="WARNING: field missing"
    shortDesc="LineGap value is less than 0 (unlikely value)"
    fwLinkID="10353"
    tableName="hhea">
    <problem>For the most consistent performance between platforms, the linegap value should indicate the difference between (winascent + windescent, lineheight used by Windows) and (hhea.ascender + (-hhea.descender), lineheight used by Apple). This is not an 'interline gap' value.</problem>
</item>

<item
    helpID="W1404"
    atom="hhea_W_LineGap_minGap"
    linkTitle="hhea table specification"
    specLink="WARNING: field missing"
    shortDesc="The LineGap value is less than the recommended value"
    fwLinkID="10353"
    tableName="hhea">
    <problem>For the most consistent performance between platforms, the linegap value should indicate the difference between (winascent + windescent, lineheight used by Windows) and (hhea.ascender + (-hhea.descender), lineheight used by Apple). This is not an 'interline gap' value.</problem>
</item>

<item
    helpID="W1405"
    atom="hhea_W_Ascender_usWinAscent"
    linkTitle="hhea table specification"
    specLink="WARNING: field missing"
    shortDesc="Ascender is different than OS/2.usWinAscent. Different line heights on Windows and Apple"
    fwLinkID="10353"
    tableName="hhea">
    <problem>For the most consistent performance between platforms, the hhea.Ascender value (used by Apple) should be the same as the OS/2.usWinAscent value (used by Windows).</problem>
</item>

<item
    helpID="W1406"
    atom="hhea_W_Descender_usWinDescent"
    linkTitle="hhea table specification"
    specLink="WARNING: field missing"
    shortDesc="Descender is different than OS/2.usWinDescent. Different line heights on Windows and Apple"
    fwLinkID="10353"
    tableName="hhea">
    <problem>For the most consistent performance between platforms, the hhea.Descender value (used by Apple) should be the same as the OS/2.usWinDescent value (used by Windows).</problem>
</item>

<item
    helpID="W1500"
    atom="hmtx_W_CheckMetrics_lsb_gt_adv"
    linkTitle="hmtx table specification"
    specLink="http://www.microsoft.com/typography/otspec/hmtx.htm"
    shortDesc="The leftSideBearing is greater than the advance width (unlikely value)"
    fwLinkID="10354"
    tableName="hmtx">
    <problem>Most glyphs have an advance width that equals the following:&lt;BR&gt;&lt;BR&gt;aw = lsb + width of outline + rsb. [the width of the outline being max x coordinate of outline data - min x coordinate of outline data).&lt;BR&gt;&lt;BR&gt;However, there are cases where placement of a glyph does not cause the 'penpoint' to be advanced (as with some combining marks, or scripts that require diacritics that are separate from composite glyphs). In these cases, the leftSideBearing may be greater than the advance width.</problem>
</item>

<item
    helpID="W1600"
    atom="kern_W_Format0_SearchFields"
    linkTitle="kern table specification"
    specLink="http://www.microsoft.com/typography/otspec/kern.htm"
    shortDesc="The subtable's searchRange, entrySelector, and rangeShift fields cannot be validated"
    fwLinkID="10357"
    tableName="kern">
    <problem>The values of the fields noted cannot be calculated because the npairs field is set to 0. The npairs field should indicate the number of kerning pairs in the table. Recreate the kern table using a kern table editing tool.</problem>
</item>

<item
    helpID="W1701"
    atom="loca_W_GlyfEntryLengthAlignment"
    linkTitle="loca table specification"
    specLink="http://www.microsoft.com/typography/otspec/loca.htm"
    shortDesc="Loca references a glyf entry which length is not a multiple of 4"
    fwLinkID="10358"
    tableName="loca">
    <problem>The local offsets to glyph data should be long-aligned, i.e., multiples of 4. Offsets which are not long-aligned may degrade the performance of some processors. Ensure that the outline editing tool you are using is creating the glyf table properly.</problem>
</item>

<item
    helpID="W1702"
    atom="loca_W_GlyfPartiallyUnreferenced"
    linkTitle="loca table specification"
    specLink="http://www.microsoft.com/typography/otspec/loca.htm"
    shortDesc="Glyf table is partially unreferenced by loca table"
    fwLinkID="10358"
    tableName="loca">
    <problem>There is data in the glyf table that is not referenced via offsets in the loca table. Remove the extra glyph data, or recreate the loca table.</problem>
</item>

<item
    helpID="W1800"
    atom="LTSH_W_yPels_zero"
    linkTitle="LTSH table specification"
    specLink="http://www.microsoft.com/typography/otspec/LTSH.htm"
    shortDesc="The LTSH yPel value is zero"
    fwLinkID="10359"
    tableName="LTSH">
    <problem>The yPel value of the LTSH table records the ppem for each glyph at which the scaling becomes linear, despite instructions effecting the advance width. At and above the recorded threshold size, the glyph must remain linear in its scaling. The proper yPel value for glyphs that scale linearly at all sizes is '1' (at 1 ppem and above the glyph scales linearly). Use a tool such as CacheTT, available from Microsoft, to regenerate the LTSH table with correct values.</problem>
</item>

<item
    helpID="W1801"
    atom="LTSH_W_Need_Newer_FreeType"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The Freetype version is too old"
    fwLinkID="0"
    tableName="LTSH">
    <problem>To calculate HDMX, LTSH and VDMX correctly, the minimum version of Freetype required is 2.6.1.</problem>
</item>

<item
    helpID="W2000"
    atom="name_W_subfamily_style"
    linkTitle="name table specification"
    specLink="http://www.microsoft.com/typography/otspec/name.htm"
    shortDesc="The subfamily string is inconsistent with the style of the font"
    fwLinkID="10361"
    tableName="name">
    <problem>This warning is generated when there is an inconsistency between the contents of the subfamily string in the name table and the way the bold/italic bits are set in the fsSelection field of the OS/2 table. Only bold and italic styling is considered. For example, if the bold bit is set, the subfamily string should read 'Bold'. If the bold bit is not set, the subfamily string should read 'Regular'. To learn more about the fsSelection field in the OS/2 table, see &lt;A TARGET=&quot;top&quot; HREF=&quot;http://go.microsoft.com/fwlink?LinkID=10384&quot;&gt;the OS/2 table specification&lt;/ A&gt;.</problem>
</item>

<item
    helpID="W2001"
    atom="name_W_VersionMismatch_MS_MAC"
    linkTitle="name table specification"
    specLink="http://www.microsoft.com/typography/otspec/name.htm"
    shortDesc="The MS version string doesn't match the Mac version string"
    fwLinkID="10361"
    tableName="name">
    <problem>The version string in the name table should exist for both platforms and should have the same value.</problem>
</item>

<item
    helpID="W2002"
    atom="name_W_VersionMismatch_3_1_3_10"
    linkTitle="name table specification"
    specLink="http://www.microsoft.com/typography/otspec/name.htm"
    shortDesc="The 3,1 version string doesn't match the 3,10 version string"
    fwLinkID="0"
    tableName="name">
    <problem>The 3,1 version string doesn't match the 3,10 version string</problem>
</item>

<item
    helpID="W2003"
    atom="name_W_CopyrightInconsistent"
    linkTitle="name table specification"
    specLink="http://www.microsoft.com/typography/otspec/name.htm"
    shortDesc="The copyright strings are inconsistent"
    fwLinkID="0"
    tableName="name">
    <problem>The copyright strings are inconsistent</problem>
</item>

<item
    helpID="W2004"
    atom="name_W_DescriptionInconsistent"
    linkTitle="name table specification"
    specLink="http://www.microsoft.com/typography/otspec/name.htm"
    shortDesc="The description strings are inconsistent"
    fwLinkID="0"
    tableName="name">
    <problem>The description strings are inconsistent</problem>
</item>

<item
    helpID="W2005"
    atom="name_W_TrademarkInconsistent"
    linkTitle="name table specification"
    specLink="http://www.microsoft.com/typography/otspec/name.htm"
    shortDesc="The trademark strings are inconsistent"
    fwLinkID="0"
    tableName="name">
    <problem>The trademark strings are inconsistent</problem>
</item>

<item
    helpID="W2006"
    atom="name_W_ID_1to6_Required_For_Common_OSes"
    linkTitle="name table specification"
    specLink="http://www.microsoft.com/typography/otspec/name.htm"
    shortDesc="Name ID 1 to 6 are often needed to be installable."
    fwLinkID="0"
    tableName="name">
    <problem>Name ID 1 to 6 are often needed, to be installable to Windows and Mac OS X.
&lt;P&gt;See also &lt;A TARGET=&quot;top&quot; HREF=&quot;http://www.adobe.com/devnet/opentype/afdko/topic_tables_win.html&quot;&gt;OpenType tables used by Windows&lt;/A&gt; at Adobe Developer Connection.
  </problem>
</item>

<item
    helpID="W2100"
    atom="OS_2_W_CodePageRangeBitClear"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#cpr"
    shortDesc="A CodePage bit is clear in ulCodePageRange, but the font contains all of the printable characters from that codepage"
    fwLinkID="10381"
    tableName="OS/2">
    <problem>A codepage supported by this font is not represented in the codepage bit settings of the OS/2 table. Although the font may still be functional and valid, this warning may indicate an oversight on the part of the font designer, or a problem with the font development tool. Alternately, designers may choose not to claim codepage support if the additional characters are for special purposes and are not intended for general use at different sizes or at different resolutions.</problem>
</item>

<item
    helpID="W2101"
    atom="OS_2_W_CodePageRangeBitSet"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#cpr"
    shortDesc="A CodePage bit is set in ulCodePageRange, but the font is missing some of the printable characters from that codepage"
    fwLinkID="10381"
    tableName="OS/2">
    <problem>If a bit is set (1) indicating codepage coverage, then font clients will consider the font fully functional for that codepage. Although a font designer may choose to set a codepage bit if the font is 'substantially' functional for a codepage, this may cause problems to operating systems or applications expecting full codepage coverage. Font designers should select character sets that support fully functional code pages, if at all possible.</problem>
</item>

<item
    helpID="W2103"
    atom="OS_2_W_fsSelection_weight"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#fss"
    shortDesc="The fsSelection bold bit is set, but is inconsistent with the usWeightClass value"
    fwLinkID="10384"
    tableName="OS/2">
    <problem>This warning is generated when there is an inconsistency between the usWeightClass field in the OS/2 table and the way the bold bit is set in the fsSelection field of the OS/2 table. If an application is choosing fonts based on weight class values, this font may not be enumerated properly.&lt;BR&gt;&lt;BR&gt;If the bold bit is set, the Font Validator expects to find a usWeightClass value of at least 500 (400 being considered 'Regular').</problem>
</item>

<item
    helpID="W2104"
    atom="OS_2_W_hmtx_invalid"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#acw"
    shortDesc="The xAvgCharWidth field can not be validated"
    fwLinkID="10378"
    tableName="OS/2">
    <problem>This value cannot be validated because width data for glyphs is not available. This is either because the hmtx table, a required table, is corrupted or missing. Regenerate a new version of the font containing a valid hmtx table.</problem>
</item>

<item
    helpID="W2105"
    atom="OS_2_W_Panose_undefined"
    linkTitle="PANOSE specification"
    specLink="http://www.panose.com/hardware/pan2.asp"
    shortDesc="PANOSE(tm) is undefined. Font mapping may not work properly"
    fwLinkID="0"
    tableName="OS/2">
    <problem>PANOSE(tm) values are important for font clients that must substitute a font when a specified font is not available. PANOSE values should be carefully assigned to ensure adequate font mapping. PANOSE values are fully described in the reference noted below.</problem>
</item>

<item
    helpID="W2106"
    atom="OS_2_W_Version_old"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#ver"
    shortDesc="The version number is valid, but less than 5"
    fwLinkID="10398"
    tableName="OS/2">
    <problem>The version number of the OS/2 table identifies the content and layout of the table. The version number used currently is five (5). Versions zero (0, TrueType rev 1.5), one (1, TrueType rev 1.66), two (2, OpenType rev 1.2), three (3, OpenType rev 1.4) and four (4, OpenType rev 1.6) have been used previously. Incrementing the version number of the table will require that values stored in the table be changed to conform to the new version.</problem>
</item>

<item
    helpID="W2107"
    atom="OS_2_W_yStrikeoutPosition_unlikely"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#sp"
    shortDesc="yStrikeoutPosition has unlikely value"
    fwLinkID="10387"
    tableName="OS/2">
    <problem>This field should specify the position of the top of the strikeout stroke relative to the baseline in font design units. Positive values represent distances above the baseline, while negative values represent distances below the baseline (although this would be an unlikely location for strikeout positioning). A value of zero falls directly on the baseline, while a value of one falls one pel above the baseline. The value of the strikeout position should not interfere with the recognition of standard characters, and therefore not line up with crossbars in a font. For a Roman font with a 2048 em square, 460 is suggested.</problem>
</item>

<item
    helpID="W2108"
    atom="OS_2_W_yStrikeoutSize_unlikely"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#ss"
    shortDesc="yStrikeoutSize has unlikely value"
    fwLinkID="10388"
    tableName="OS/2">
    <problem>This field should specify the width of the strikeout stroke in font design units. This field should normally be the width of the em dash for the current font. If the size is one, the strikeout line will be the line represented by the strikeout position field. If the value is two, the strikeout line will be the line represented by the strikeout position and the line immediately above the strikeout position. For a roman font with a 2048 em square, 102 is suggested.</problem>
</item>

<item
    helpID="W2109"
    atom="OS_2_W_ySubscriptXSize_unlikely"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#subxs"
    shortDesc="ySubscriptXSize has unlikely value"
    fwLinkID="10390"
    tableName="OS/2">
    <problem>This value, measured in Funits, should represent the horizontal size for subscripts for this font, as recommended by the font designer. This value can be used by clients for simulating or substituting subscript glyphs if true subscript glyphs are not available in the font. Use a table editing tool to correct this value.</problem>
</item>

<item
    helpID="W2110"
    atom="OS_2_W_ySubscriptYOffset_LTZero"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#subyo"
    shortDesc="ySubscriptYOffset is less than zero which is an unlikely value"
    fwLinkID="10391"
    tableName="OS/2">
    <problem>This value, measured in Funits, should represent the horizontal offset for subscript characters for this font, as recommended by the font designer. The offset is measured from the character origin of the font to the character origin of the subscript character. For upright characters, this value is usually zero. Use a table editing tool to correct this value.</problem>
</item>

<item
    helpID="W2111"
    atom="OS_2_W_ySubscriptYSize_unlikely"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#subys"
    shortDesc="ySubscriptYSize has unlikely value"
    fwLinkID="10392"
    tableName="OS/2">
    <problem>This value, measured in Funits, should represent the vertical size for subscripts for this font, as recommended by the font designer. This value can be used by clients for simulating or substituting subscript glyphs if true subscript glyphs are not available in the font. Use a table editing tool to correct this value.</problem>
</item>

<item
    helpID="W2112"
    atom="OS_2_W_ySuperscriptXSize_unlikely"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#supxs"
    shortDesc="ySuperscriptXSize has unlikely value"
    fwLinkID="10394"
    tableName="OS/2">
    <problem>This value, measured in Funits, should represent the horizontal size for superscripts for this font, as recommended by the font designer. This value can be used by clients for simulating or substituting superscript glyphs if true superscript glyphs are not available in the font. Use a table editing tool to correct this value.</problem>
</item>

<item
    helpID="W2113"
    atom="OS_2_W_ySuperscriptYOffset_unlikely"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#supyo"
    shortDesc="ySuperscriptYOffset is less than zero which is an unlikely value"
    fwLinkID="10395"
    tableName="OS/2">
    <problem>This value, measured in Funits, should represent the vertical offset for superscript characters for this font, as recommended by the font designer. The offset is measured from the character baseline to the superscript character's baseline. Use a table editing tool to correct this value.</problem>
</item>

<item
    helpID="W2114"
    atom="OS_2_W_ySuperscriptYSize_unlikely"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#supys"
    shortDesc="ySuperscriptYSize has unlikely value"
    fwLinkID="10396"
    tableName="OS/2">
    <problem>This value, measured in Funits, should represent the vertical size for superscripts for this font, as recommended by the font designer. This value can be used by clients for simulating or substituting superscript glyphs if true superscript glyphs are not available in the font. Use a table editing tool to correct this value.</problem>
</item>

<item
    helpID="W2116"
    atom="OS_2_W_WeightClass_PANOSE"
    linkTitle="OS/2 table specification"
    specLink="http://www.microsoft.com/typography/otspec/os2.htm#wtc"
    shortDesc="The usWeightClass is inconsistent with the PANOSE weight value"
    fwLinkID="10400"
    tableName="OS/2">
    <problem>Use a table editing tool to correct the usWeightClass value and/or the PANOSE value so that they correspond.</problem>
</item>

<item
    helpID="W2117"
    atom="OS_2_W_sTypoAscenderDescender_difference"
    linkTitle="OS/2 table specification"
    specLink="WARNING: field missing"
    shortDesc="The value of sTypoAscender minus sTypoDescender is greater than unitsPerEm"
    fwLinkID="11802"
    tableName="OS/2">
    <problem>The sTypoAscender value is used to determine the optimum offset from the top of a text frame to the first baseline. The sTypoDescender value is used to determine the optimum offset from the last baseline to the bottom of the text frame. The sTypoDescender value should be greater than zero, and the value of (sTypoAscender - sTypoDescender) is recommended to equal one em. To learn more about this value, see the &lt;A TARGET=&quot;top&quot; HREF=&quot;http://go.microsoft.com/fwlink?LinkID=10367&quot;&gt;Recommendations for OpenType Fonts.&lt;/A&gt;</problem>
</item>

<item
    helpID="W2300"
    atom="post_W_italicAngle_unlikely"
    linkTitle="post table specification"
    specLink="http://www.microsoft.com/typography/otspec/post.htm"
    shortDesc="The italicAngle value is unlikely"
    fwLinkID="10365"
    tableName="post">
    <problem>The italic angle value is measured in degrees, counter-clockwise from the vertical. Zero is the value for upright text. Negative values are used for text that leans to the right (forward for left-to-right writing). This value should be in agreement with the caretSlopeRise and caretSlopeRun values in the hhea table.</problem>
</item>

<item
    helpID="W2301"
    atom="post_W_underlinePos_LT_descender"
    linkTitle="post table specification"
    specLink="http://www.microsoft.com/typography/otspec/post.htm"
    shortDesc="The underlinePosition value is less than hhea.Descender"
    fwLinkID="10365"
    tableName="post">
    <problem>The underlinePosition value in the post table is the suggested distance from the top of the underline to the baseline (negative values indicate below baseline). Typically, underlines are not positioned beyond the lowest descender in the font.</problem>
</item>

<item
    helpID="W2302"
    atom="post_W_underlineThickness"
    linkTitle="post table specification"
    specLink="http://www.microsoft.com/typography/otspec/post.htm"
    shortDesc="The underlineThickness value is unlikely"
    fwLinkID="10365"
    tableName="post">
    <problem>The thickness of the underline for the font, as specified in the post table, is either less than zero or is greater than 1/2 the unitsPerEm. Correct this value using a table editing tool.</problem>
</item>

<item
    helpID="W2303"
    atom="post_W_Version_2_5"
    linkTitle="post table specification"
    specLink="http://www.microsoft.com/typography/otspec/post.htm"
    shortDesc="The version number is 0x00025000, which is valid but deprecated"
    fwLinkID="10365"
    tableName="post">
    <problem>Version 2.5 of the post table was deprecated by Apple in February, 2000, with the release of version 1.3 of the OpenType specification.</problem>
</item>

<item
    helpID="W2304"
    atom="post_W_Version_3_Apple"
    linkTitle="post table specification"
    specLink="https://developer.apple.com/fonts/TrueType-Reference-Manual/RM06/Chap6post.html"
    shortDesc="Apple recommends against using post table format 3 under most circumstances"
    fwLinkID="10365"
    tableName="post">
    <problem>Apple recommends against using 'post' table format 3 under most circumstances, as it can create problems with some printer drivers and PDF documents. The savings in disk space usually does not justify the potential loss in functionality.</problem>
</item>

<item
    helpID="W2305"
    atom="post_W_Version_4_Apple"
    linkTitle="post table specification"
    specLink="https://developer.apple.com/fonts/TrueType-Reference-Manual/RM06/Chap6post.html"
    shortDesc="As a rule, format 4 post tables are no longer necessary and should be avoided."
    fwLinkID="10365"
    tableName="post">
    <problem>As a rule, format 4 post tables are no longer necessary and should be avoided.</problem>
</item>

<item
    helpID="W5021"
    atom="_OTL_DeviceTable_W_StartSize"
    linkTitle="OTL common table formats"
    specLink="http://www.microsoft.com/typography/otspec/chapter2.htm"
    shortDesc="The device table StartSize is unusually large"
    fwLinkID="10338"
    tableName="OTL Device">
    <problem>The device table defines single pixel adjustments for specified font sizes (in ppem). Since 16384 is the largest unitsPerEm value allowed for OpenType fonts, 16384 is the largest ppem size that can be specified as a starting or ending size in the device table. To learn more about allowable and recommended ppem values, see &lt;A TARGET=&quot;top&quot; HREF=&quot;go.microsoft.com/fwlink?LinkID=10352&quot;&gt;the head table specification&lt;/A&gt; and the &lt;A TARGET=&quot;top&quot; HREF=&quot;http://go.microsoft.com/fwlink?LinkID=10456&quot;&gt;Hinting and Production Guidelines Specification&lt;/A&gt;.</problem>
</item>

<item
    helpID="W5200"
    atom="_OTL_DeviceTable_W_EndSize"
    linkTitle="OTL common table formats"
    specLink="http://www.microsoft.com/typography/otspec/chapter2.htm"
    shortDesc="The device table EndSize is unusually large"
    fwLinkID="10338"
    tableName="OTL Device">
    <problem>The device table defines single pixel adjustments for specified font sizes (in ppem). Since 16384 is the largest unitsPerEm value allowed for OpenType fonts, 16384 is the largest ppem size that can be specified as a starting or ending size in the device table. To learn more about allowable and recommended ppem values, see &lt;A TARGET=&quot;top&quot; HREF=&quot;go.microsoft.com/fwlink?LinkID=10352&quot;&gt;the head table specification&lt;/A&gt; and the &lt;A TARGET=&quot;top&quot; HREF=&quot;http://go.microsoft.com/fwlink?LinkID=10456&quot;&gt;Hinting and Production Guidelines Specification&lt;/A&gt;.</problem>
</item>

<item
    helpID="W5300"
    atom="_OTL_FeatureListTable_W_FeatureRecord_tag"
    linkTitle="OTL feature registry"
    specLink="http://www.microsoft.com/typography/otspec/ttoreg.htm"
    shortDesc="The FeatureRecord tag is valid, but unregistered"
    fwLinkID="10370"
    tableName="OTL Feature List">
    <problem>Microsoft maintains a registry of supported feature and language tags. The registry establishes conventions for naming and using these tags. Registered tags have a specific meaning and convey precise information to developers and text-processing clients of OpenType Layout. Microsoft encourages font developers to use registered tags to assure compatibility and ease of use across fonts, applications, and operating systems.</problem>
</item>

<item
    helpID="W6000"
    atom="_rast_W_APPLE_ONLY_INSTR"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="GETVARIATION, GETDATA (Apple-specific) or IDEFs at opcode 0x91,0x92"
    fwLinkID="10368"
    tableName="Rasterization Test">
  <problem>This warning indicates that opcode 0x91 or 0x92 is detected.

&lt;P&gt;Apple uses opcode 0x91 and 0x92 for their Quick Draw GX-specific instructions GETVARIATION and GETDATA.
The GETVARIATION and GETDATA instructions are not valid under Windows. These instructions are only valid on Apple platforms. Please consult Apple documentation to find out for which versions of the Mac OS the instruction is valid.

&lt;P&gt;Microsoft removed support for GETVARIATION and GETDATA in its
bytecode engine. Instead, they allow IDEFs for opcode 0x91 and 0x92.

&lt;P&gt;The specification says that IDEFs work for undefined opcodes only.

&lt;P&gt;IDEFs for bytecodes 0x91 and 0x92 are not possible with the Apple bytecode engine since those instructions are undocumented but still in use for backwards compatibility.

&lt;P&gt;Microsoft ships two fonts, LaoUIb.ttf and LaoUI.ttf, which use IDEFs at opcode 0x91 and 0x92 (and therefore do not work correctly on Mac OS). Apple ships Skia.ttf which uses GETVARIATION (and therefore do not work correctly on MS Windows).

&lt;P&gt;To support multiple platforms, font designers are advised to avoid either usage of opcode 0x91 and 0x92 in new fonts.
  </problem>
</item>

<item
    helpID="W6001"
    atom="_rast_W_CALL_ZERO_LEN_FUNC"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="CALL to zero length function"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>A call to a zero length function should be avoided because it wastes an instruction (although it is legal).</problem>
</item>

<item
    helpID="W6002"
    atom="_rast_W_CALL_ZERO_LEN_UD_INSTR"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Call to zero length user defined instruction"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>A call to a zero length user-defined instruction should be avoided because it wastes an instruction (although it is legal).</problem>
</item>

<item
    helpID="W6003"
    atom="_rast_W_DEBUG_FOUND"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="DEBUG found which should not be found in production code"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>Remove all DEBUG statements before shipping this font.</problem>
</item>

<item
    helpID="W6004"
    atom="_rast_W_DELTAC_IN_GLYPH_PGM"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Repeated executions in glyph programs can have unexpected results"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>The DELTAC instruction changes the value of CVT entries. If this is executed in a glyph program, every time that glyph is hinted the CVT entry is changed. These changes will accumulate and cause a result that the hinter might not have expected.</problem>
</item>

<item
    helpID="W6005"
    atom="_rast_W_HI_PT_LESS_THAN_LOW_PT"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="High point is less than low point"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>If the value for the high point is less than the low point, the instruction will do nothing.</problem>
</item>

<item
    helpID="W6006"
    atom="_rast_W_JMP_OFFSET_ZERO"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Jump offset zero"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>The jump offset is zero which means that execution will jump back to this jump instruction.</problem>
</item>

<item
    helpID="W6007"
    atom="_rast_W_LOOP_NOT_1_AT_END_OF_PGM"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Loop variable not 1 at end of program. This means it was set but not used"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>At the end of the execution of the instructions for a glyph, the loop variable was not 1, which means that it was set and not used by any other instructions. In this case, a previous SLOOP instruction is wasted.

&lt;P&gt;Note that the Details part of the diagnostic message is essentially meaningless: it contains information about the last instruction executed. To rectify this issue, the font designer should examine the last SLOOP instruction, by searching backwards from the end.
</problem>
</item>

<item
    helpID="W6008"
    atom="_rast_W_LOOPCALL_COUNT_LESS_THAN_ONE"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Value for count is less than 1. Function will not be called"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>The 'value for count' is the number of times LOOPCALL will call the function. In the LOOPCALL instruction, if the value for count is less than 1, the function will not be called.</problem>
</item>

<item
    helpID="W6009"
    atom="_rast_W_MPS_ALWAYS_12_ON_WINDOWS"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Window 95 and Windows 3.1 always return 12"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>Windows 95 and Windows 3.1 will always return 12 in response to the MPS instruction. This is a side effect of the way the TrueType rasterizer was integrated into Windows.</problem>
</item>

<item
    helpID="W6010"
    atom="_rast_W_PF_VECTORS_AT_OR_NEAR_PERP"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Projection and freedom vectors at or near perpendicular"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>The current projection and freedom vectors are at or near perpendicular. This could cause points to move in an unexpected manner.</problem>
</item>

<item
    helpID="W6011"
    atom="_rast_W_PT_NOT_TOUCHED"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Point not touched"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>Untouching a point that is not touched. This is a waste of an instruction.</problem>
</item>

<item
    helpID="W6012"
    atom="_rast_W_SANGW_OBSELETE"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Function no longer needed because of dropped support of AA"
    fwLinkID="0"
    tableName="WARNING: field missing">
    <problem>ERROR: Required field missing</problem>
</item>

<item
    helpID="W6019"
    atom="_rast_W_Need_Newer_FreeType"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The Freetype version is too old"
    fwLinkID="0"
    tableName="Rasterization Test">
    <problem>Place holder - We most likely need to enhance Freetype and do a minimum version check.</problem>
</item>

<item
    helpID="W6020"
    atom="_rast_W_FT_VALUE_OUT_OF_RANGE_SLOOP"
    linkTitle="WARNING: field missing"
    specLink="https://developer.apple.com/fonts/TrueType-Reference-Manual/RM05/Chap5.html#SLOOP"
    shortDesc="Setting the loop variable to negative value"
    fwLinkID="0"
    tableName="Rasterization Test">
    <problem>Setting the loop variable to negative value.</problem>
</item>

<item
    helpID="W6029"
    atom="_rast_W_FT_VALUE_OUT_OF_RANGE_SLOOP_ZERO"
    linkTitle="WARNING: field missing"
    specLink="https://developer.apple.com/fonts/TrueType-Reference-Manual/RM05/Chap5.html#SLOOP"
    shortDesc="Setting the loop variable to zero is an error"
    fwLinkID="0"
    tableName="Rasterization Test">
    <problem>Setting the loop variable to zero is an error, according to Apple documentation.

&lt;ol&gt;
ttfautohint is known to generate such hinting instructions, and FreeType is known to tolerate it.
If the font is intended to be used only on systems where FreeType is the rendering engine, this warning can be safely ignored.</problem>
</item>

<item
    helpID="W6021"
    atom="_rast_W_FT_ZERO_LEN_FUNC"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Defining zero-length function"
    fwLinkID="0"
    tableName="Rasterization Test">
    <problem>Defining zero-length function</problem>
</item>

<item
    helpID="W6022"
    atom="_rast_W_FT_ZERO_LEN_UD_INSTR"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Defining zero-length user-defined instruction"
    fwLinkID="0"
    tableName="Rasterization Test">
    <problem>Defining zero-length user-defined instruction</problem>
</item>

<item
    helpID="W6023"
    atom="_rast_W_FT_InvalidOutline"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Invalid Outline"
    fwLinkID="0"
    tableName="Rasterization Test">
    <problem>FreeType throws &quot;Invalid Outline&quot; error on this glyph. Check and fix errors indicated by the glyf table test first, before re-test.</problem>
</item>

<item
    helpID="W6024"
    atom="_rast_W_FT_InvalidArgument"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Invalid Argument"
    fwLinkID="0"
    tableName="Rasterization Test">
    <problem>FreeType throws &quot;Invalid Argument&quot; error. Most likely there is an inconsistency in the number of glyphs declared in different tables. Fixes these other errors first, before re-test.</problem>
</item>

<item
    helpID="W6025"
    atom="_rast_W_FT_InvalidPixelSize"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Invalid PixelSize"
    fwLinkID="0"
    tableName="Rasterization Test">
    <problem>FreeType throws &quot;Invalid PixelSize&quot; error. This is likely a user error, trying to set an unsupported size for a fixed-size font.</problem>
</item>

<item
    helpID="W6026"
    atom="_rast_W_FT_InvalidSizeHandle"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="Invalid Size Handle"
    fwLinkID="0"
    tableName="Rasterization Test">
    <problem>FreeType throws &quot;Invalid Size Handle&quot; error. When this happens for a fixed-size font at specific glyphs, it is likely that those glyphs have invalid metrics.</problem>
</item>

<item
    helpID="W6027"
    atom="_rast_W_FT_MAXP_maxComponentDepth_TOO_LOW"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="maxComponentDepth in maxp is too low"
    fwLinkID="0"
    tableName="Rasterization Test">
    <problem>maxComponentDepth in maxp is too low. Consider increasing its value.</problem>
</item>

<item
    helpID="W6028"
    atom="_rast_W_FT_MAX_NUM_TWILIGHT_POINTS_CLAMP"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="number of twilight points unreasonably large"
    fwLinkID="0"
    tableName="Rasterization Test">
    <problem>Number of twilight points seems unreasonably large. Consider resetting to a more reasonable heuristic value.</problem>
</item>

<item
    helpID="W6030"
    atom="_rast_W_FT_ALIGNRP_AFTER_IUP"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="ALIGNRP after IUP in Subpixel-hinting mode"
    fwLinkID="0"
    tableName="Rasterization Test">
    <problem>ALIGNRP after IUP in Subpixel-hinting mode.</problem>
</item>

<item
    helpID="W1703"
    atom="loca_W_GlyfEntryEmpty"
    linkTitle="loca table specification"
    specLink="http://www.microsoft.com/typography/otspec/loca.htm"
    shortDesc="Loca references a zero-length entry in the glyf table"
    fwLinkID="10358"
    tableName="loca">
    <problem>This message may indicate that there are multiple zero-length glyphs located at the end of the glyf table. If so, remove the extra empty glyphs.</problem>
</item>

<item
    helpID="I1900"
    atom="maxp_I_Calculation_Method1"
    linkTitle="maxp table specification"
    specLink="http://www.microsoft.com/typography/otspec/maxp.htm"
    shortDesc="maxSizeOfInstructions via method #1"
    fwLinkID="10360"
    tableName="maxp">
    <problem>The maxSizeOfInstructions field may be calculated by two
methods, the first being preferred:
&lt;ol&gt;
&lt;li&gt;The maximum instruction size of any glyph, taking into account
only the instructions in the glyf table.
&lt;li&gt;The same as method #1, plus the size of the prep table plus the size of
the fpgm table.
&lt;/ol&gt;

&lt;P&gt;
This info message indicates that maxSizeOfInstructions computed via method #1.
</problem>
</item>

<item
    helpID="I1901"
    atom="maxp_I_Calculation_Method2"
    linkTitle="maxp table specification"
    specLink="http://www.microsoft.com/typography/otspec/maxp.htm"
    shortDesc="maxSizeOfInstructions via method #2"
    fwLinkID="10360"
    tableName="maxp">
    <problem>The maxSizeOfInstructions field may be calculated by two
methods, the first being preferred:
&lt;ol&gt;
&lt;li&gt;The maximum instruction size of any glyph, taking into account
only the instructions in the glyf table.
&lt;li&gt;The same as method #1, plus the size of the prep table plus the 
size of the fpgm table.
&lt;/ol&gt;

&lt;P&gt;
This info message indicates that maxSizeOfInstructions computed via method #2.
</problem>
</item>

<item
    helpID="W1900"
    atom="maxp_W_Calculation_Unclear"
    linkTitle="maxp table specification"
    specLink="http://www.microsoft.com/typography/otspec/maxp.htm"
    shortDesc="maxSizeOfInstructions computation not via either approved method"
    fwLinkID="10360"
    tableName="maxp">
    <problem>The maxSizeOfInstructions field may be calculated by two
methods, the first being preferred:
&lt;ol&gt;
&lt;li&gt;The maximum instruction size of any glyph, taking into account
only the instructions in the glyf table.
&lt;li&gt;The same as method #1, plus the size of the prep table plus the 
size of the fpgm table.
&lt;/ol&gt;

&lt;P&gt;
A font showing this warning has maxSizeOfInstructions that is larger than
the value calculated by method #1, but not equal to the value calculated by
method #2. (Note that a maxSizeOfInstructions value smaller than that 
calculated via method #1 is an error.) 

&lt;P&gt;

The fact that the maxSizeOfInstructions value does not match the value computed
by either method may indicate some other problem in the font.
</problem>
</item>

<item
    helpID="I6059"
    atom="_rast_I_rasterization"
    linkTitle="details about OpenType files"
    specLink="WARNING: Rasterization for fonts with PostScript outlines not implemented yet."
    shortDesc="Could not perform rasterization"
    fwLinkID="10363"
    tableName="Rasterization Test">
    <problem>Rasterization could not be performed because the font file has PostScript outlines.</problem>
</item>

<item
    helpID="I6070"
    atom="_rast_I_FT_Error_Supplymentary_Info"
    linkTitle="TrueType instruction set"
    specLink="http://www.microsoft.com/typography/otspec/ttinst.htm"
    shortDesc="Supplementary Information"
    fwLinkID="10368"
    tableName="Rasterization Test">
    <problem>Supplementary Information, just before impending Font Engine error.</problem>
</item>

<item
    helpID="W2500"
    atom="VDMX_W_CalcData"
    linkTitle="VDMX table specification"
    specLink="http://www.microsoft.com/typography/otspec/vdmx.htm"
    shortDesc="The VDMX data doesn't match the data calculated by the rasterizer"
    fwLinkID="10371"
    tableName="VDMX">
    <problem>The VDMX data does not match the value calculated by the current version of the rasterizer. This data may not match if glyphs have been updated but the VDMX table has not been recalculated (using a tool such as Microsoft's CacheTT). The problem may also occur if the VDMX table was generated using a previous version of the rasterizer, or another tool that performs the calculations differently. To correct the data, use the latest version of CacheTT to calculate the cached values using the current rasterizer. However, you may not want to change these values if there are concerns about the way text in legacy documents might reflow.</problem>
</item>

<item
    helpID="W2501"
    atom="VDMX_W_Need_Newer_FreeType"
    linkTitle="WARNING: field missing"
    specLink="WARNING: field missing"
    shortDesc="The Freetype version is too old"
    fwLinkID="0"
    tableName="VDMX">
    <problem>To calculate HDMX, LTSH and VDMX correctly, the minimum version of Freetype required is 2.6.1.</problem>
</item>

<!--
Pre-2015 assigned values:

00 _GEN,_OFFSET,_FONT,_DE,_Table,_TEST

02 CFF
03 cmap
04 cvt
05 DSIG
06 EBDT
07 EBLC
08 EBSC
09 fpgm
10 gasp
11 glyf
12 hdmx
13 head
14 hhea
15 hmtx
16 kern
17 loca
18 LTSH
19 maxp
20 name
21 OS/2
22 PCLT
23 post
24 prep
25 VDMX
26 vhea
27 vmtx
28 VORG

40 GDEF
41 GPOS
42 GSUB
43 BASE
44 JSTF

50 _OTL_ClassDefinitionTable
51 _OTL_CoverageTable
52 _OTL_DeviceTable
53 _OTL_FeatureListTable
54 _OTL_FeatureTable
55 _OTL_LangSysTable
56 _OTL_LookupListTable
57 _OTL_LookupTable
58 _OTL_ScriptListTable
59 _OTL_ScriptTable

60 rast
-->

<!--
2015:
reserve 30-35 for CBDT/CBLC/COLR/CPAL/MATH/SVG
-->

<!--
    As part of the re-organization,
    a few 1.1 codes were re-assigned:

    loca_W_GlyfEntryEmpty      : W7001 -> W1703
    maxp_I_Calculation_Method1 : I9001 -> I1900
    maxp_I_Calculation_Method2 : I9002 -> I1901
    maxp_W_Calculation_Unclear : W7002 -> W1900
-->

<item
    helpID="P3500"
    atom="SVG_P_version"
    linkTitle="SVG table specification"
    specLink="http://www.microsoft.com/typography/otspec/svg.htm"
    shortDesc="The version field is okay"
    fwLinkID="0"
    tableName="SVG">
    <problem></problem>
</item>

<item
    helpID="W3500"
    atom="SVG_W_version"
    linkTitle="SVG table specification"
    specLink="http://www.microsoft.com/typography/otspec/svg.htm"
    shortDesc="The version field is wrong"
    fwLinkID="0"
    tableName="SVG">
    <problem>Version should be zero.</problem>
</item>

<item
    helpID="P3501"
    atom="SVG_P_offsetToSVGDocIndex"
    linkTitle="SVG table specification"
    specLink="http://www.microsoft.com/typography/otspec/svg.htm"
    shortDesc="The offsetToSVGDocIndex field is okay"
    fwLinkID="0"
    tableName="SVG">
    <problem></problem>
</item>

<item
    helpID="W3501"
    atom="SVG_W_offsetToSVGDocIndex_NonContiguous"
    linkTitle="SVG table specification"
    specLink="http://www.microsoft.com/typography/otspec/svg.htm"
    shortDesc="The offsetToSVGDocIndex field is too large"
    fwLinkID="0"
    tableName="SVG">
    <problem>There is a gap between the end of the reserved field and the SVGDocIndex.</problem>
</item>

<item
    helpID="E3501"
    atom="SVG_E_offsetToSVGDocIndex_Overlapping"
    linkTitle="SVG table specification"
    specLink="http://www.microsoft.com/typography/otspec/svg.htm"
    shortDesc="The offsetToSVGDocIndex field is too small"
    fwLinkID="0"
    tableName="SVG">
    <problem>The offsetToSVGDocIndex should be non-zero and beyond the reserved field.</problem>
</item>

<item
    helpID="P3502"
    atom="SVG_P_reserved"
    linkTitle="SVG table specification"
    specLink="http://www.microsoft.com/typography/otspec/svg.htm"
    shortDesc="The reserved field is okay"
    fwLinkID="0"
    tableName="SVG">
    <problem></problem>
</item>

<item
    helpID="W3502"
    atom="SVG_W_reserved"
    linkTitle="SVG table specification"
    specLink="http://www.microsoft.com/typography/otspec/svg.htm"
    shortDesc="The reserved field is wrong"
    fwLinkID="0"
    tableName="SVG">
    <problem>reserved field should be zero.</problem>
</item>

<item
    helpID="P3503"
    atom="SVG_P_numEntries"
    linkTitle="SVG table specification"
    specLink="http://www.microsoft.com/typography/otspec/svg.htm"
    shortDesc="The numEntries field is okay"
    fwLinkID="0"
    tableName="SVG">
    <problem></problem>
</item>

<item
    helpID="W3503"
    atom="SVG_W_numEntries"
    linkTitle="SVG table specification"
    specLink="http://www.microsoft.com/typography/otspec/svg.htm"
    shortDesc="The numEntries field is wrong"
    fwLinkID="0"
    tableName="SVG">
    <problem>numEntries should not be zero.</problem>
</item>

<item
    helpID="P3504"
    atom="SVG_P_SVGDocIndex"
    linkTitle="SVG table specification"
    specLink="http://www.microsoft.com/typography/otspec/svg.htm"
    shortDesc="The SVGDocIndex field is okay"
    fwLinkID="0"
    tableName="SVG">
    <problem></problem>
</item>

<item
    helpID="W3504"
    atom="SVG_W_SVGDocIndex"
    linkTitle="SVG table specification"
    specLink="http://www.microsoft.com/typography/otspec/svg.htm"
    shortDesc="The SVGDocIndex field has some non-fatal errors"
    fwLinkID="0"
    tableName="SVG">
    <problem>Non-fatal errors are for example, unused gaps between index entries.</problem>
</item>

<item
    helpID="E3504"
    atom="SVG_E_SVGDocIndex"
    linkTitle="SVG table specification"
    specLink="http://www.microsoft.com/typography/otspec/svg.htm"
    shortDesc="The SVGDocIndex field has some fatal errors"
    fwLinkID="0"
    tableName="SVG">
    <problem>Fatal errors are, for example, overlapping entries, where further processing is impossible.</problem>
</item>

<item
    helpID="P3505"
    atom="SVG_P_TryLoadSVG"
    linkTitle="SVG table specification"
    specLink="http://www.microsoft.com/typography/otspec/svg.htm"
    shortDesc="Try loading SVG as XML is okay"
    fwLinkID="0"
    tableName="SVG">
    <problem></problem>
</item>

<item
    helpID="E3505"
    atom="SVG_E_TryLoadSVG"
    linkTitle="SVG table specification"
    specLink="http://www.microsoft.com/typography/otspec/svg.htm"
    shortDesc="Try loading SVG as XML failed"
    fwLinkID="0"
    tableName="SVG">
    <problem>Try loading SVG as XML failed. It is possible this is a bare deflate stream which is not recommended, or simply corrupted data.</problem>
</item>

</helpitems>