In order to assist your layout, custom font selection, and other metric intensive operations, starting in Windows 8, DirectWrite has a number of new APIs to express all the info about fonts that you might require to develop rich text apps.
PANOSE is a visual classification system for identifying typefaces. The PANOSE classification contains info on the family, serif style, weight, proportion, contrast, stroke, arm style, X-height, etc. This info describes the visual style of the font. This info is important because fonts with similar PANOSE values look similar. This is very useful in situations where a font isn’t available and the app needs to fall back to a font that’s available. Comparing PANOSE values for fonts allows you to choose a font that’s similar visually to the original font.
In order to access the PANOSE info for a font, use the GetPanose method on the IDWriteFont1 and IDWriteFontFace1 interfaces. This method returns a DWRITE_PANOSE enumeration that contains all of the PANOSE info for that font.
Starting in Windows 8, the DirectWrite API also supports a number of new metrics in order to express useful info about the fonts to your app. These new metrics include this info.
- Left, Right, Top, and Bottom glyph bounding box metrics.
- X and Y positioning for superscript and subscript elements.
- X and Y scaling info for superscript and subscript elements.
- Whether or not the font has typographic metrics.
To create text editing apps you need access to info about how to draw the caret that navigates through the text. Starting in Windows 8, DirectWrite provides the GetCaretMetrics method on the IDWriteFontFace1 and IDWriteFont1 interfaces for this scenario. GetCaretMetrics returns a DWRITE_CARET_METRICS enumeration which contains info about the slope and offset for the caret along the baseline.
This info is specifically helpful if you want to be able to have their caret slope appropriately with italic text.
Apps that allow your users to write computer code often use monospaced fonts in place of more traditional fonts. So you can have more control over font selection in apps related to development, DirectWrite expresses whether or not a font is monospaced through the API. The IsMonospacedFont method on the IDWriteFontFace1 interface returns a Boolean that indicates whether or not the font is monospaced.
Rich text apps like PDF readers need to be able to match fonts in their content to fonts on the system, need access to the full names of fonts in multiple formats. So you can better match fonts, DirectWrite contains an enumeration that expresses full naming info about a font in many formats.
you use the DWRITE_INFORMATIONAL_STRING_ID enumeration to get the full name, PostScript name, and PostScript CID name of any font on the system. This info is valuable when you need to match fonts in your app to appropriate fonts on the local system.
The GetGlyphAdvances method on the IDWriteFontFace1 and IDWriteFont1 interfaces takes in the glyph count and indices that you need advances info about and then returns the advances for the glyphs in question.
Apps that want to handle their own font selection need access to the Unicode ranges that are supported by the font. This way, if a Unicode codepoint isn’t supported by the font, the app can choose an appropriate font that contains that glyph. Without this info, the app may use a font that doesn’t contain all the glyphs that are necessary to display the info present.
The GetUnicodeRanges method on the the IDWriteFontFace1 and IDWriteFont1 interfaces takes in the maximum number of ranges passed in from the client, and returns the actual ranges supported by the font.
Use the GetEudcFontCollection method on the IDWriteFactory1 interface access the EUDC font collection. This method works in the same way as GetSystemFontCollection, but instead returns a pointer to an EUDC font collection.