Using non-supported fonts

Document Management/Document Output Management supports all Google Noto fonts. If another font is desired, then it must be embedded into the template. The reason for this is because the document generation itself occurs in the cloud.

If the desired font is not available in the cloud, then it must be provided in the template (embedded). Otherwise, Document Management substitutes the font with one available to it from the Google Noto font library.

Example

A customer wants to use Document Output to create a PDF using the MICR font. The MICR font is not a Google Noto font. Therefore, it must be embedded into the template so it is available to Document Output during the document's creation.

For details about embedding fonts in Microsoft Word, see the Microsoft documentation and online help.