However, there are situations when the exact font cannot be found and Aspose.Words must substitute it for a similar font instead. Aspose.Words selects the font according to the following process: When Aspose.Words renders a document, it attempts to select the fonts that are specified in the document. The custom FontSettings have higher priority than the default instance.Ī text in a document can be formatted with various fonts, such as Arial, Times New Roman, Verdana, and others.

In this case, you can just amend the default instance as follows: If you are sure that all processing documents require the same font settings, then it is recommended to set up and utilize the default FontSettings instance. Suppose that you need to use the same font sources for all your documents. This instance is also automatically shared among documents, and can be extracted as follows: In the case when FontSettings is not defined explicitly, Aspose.Words uses the default FontSettings instance. For example, you can share an instance of the FontSettings class between different documents, which allows you to speed up the loading of the documents. However, each instance of FontSettings has its own cache, which could reduce the processing time of subsequent documents.

Since the procedure described above is time-consuming, it may negatively affect application performance at its first launch.

After all the fonts are retrieved, Aspose.Words uses these details to find the required font data or a suitable replacement for the requested font. When Aspose.Words encounters a font in the document for the first time, it attempts to obtain basic font information, such as the font full name, family name, version, style, from the font files located in each font source.

Parsing the resolved fonts for embedding and subsetting.

Parsing the resolved fonts to get available glyphs and metrics (horizontal and vertical).

Obtaining info for font, resolving from all available fonts.

Font Manipulation and Performance IssuesĪll available font manipulation mechanisms are contained in the FontSettings class. This class is responsible for fetching fonts within defined font sources as well as for the Font Substitution process, as described below. This enables certain tasks, most commonly the task of calculating text size during layout construction and embedding/subsetting to fixed-page formats. A number of other less popular tasks, such as font resolving and substitution while loading HTML or embedding/subsetting to some flow formats, are likewise enabled. Aspose.Words resolves the font in the document to a physical font at some stage of processing. Note that the font in the document represents an entity, such as family name, style, size, color, that is different from the TrueType font (physical font) entity.

There must be sufficient TrueType fonts available to Aspose.Words, preferably with the same font family names as the ones used in the document.

Aspose.Words should be able to find and access TrueType font files on the system.

To ensure Aspose.Words accurately measures the characters and successfully embeds relevant fonts, the following conditions must be met: This ensures that the document will appear the same to any viewer. Moreover, the XPS specification requires fonts to always be embedded in the document.

Differences in Processing of Font Formats in Aspose.Words and Microsoft WordĪspose.Words requires TrueType fonts for a variety of tasks, including rendering documents to fixed-page formats, for example, PDF or XPS. When Aspose.Words renders a document, it needs to perform embedding and subset embedding of TrueType fonts into the resulting document, which is a normal practice during a document generation, including popular PDF or XPS formats.

Predefined Font FallBack Settings for Google Noto Fonts.

How to Recognize That the Font Was Replaced.

Font Manipulation and Performance Issues.

Find free font substitutions