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.
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.