Request for Guidance on Missing Fonts in Linux-Based Document Generation Environment

Welcome to Microsoft Q&A!

Thank you for reaching out with this question.

I understand how important font consistency is for platforms that generate PDFs from customer-provided Word templates, especially when running on Linux infrastructure. Missing fonts can directly impact pagination, text wrapping, table layouts, and overall document fidelity. Establishing a compliant and supportable font strategy is therefore an important part of ensuring consistent document generation results.

Based on Microsoft typography documentation, Calibri, Arial, Times New Roman, and Arial Unicode MS are distributed as part of Microsoft products such as Windows and Microsoft Office rather than as standalone Linux font packages. Microsoft does not currently provide an official Linux-compatible package containing these fonts.

1. Font Availability on Linux

From a technical perspective, Linux applications can use these fonts if the font files are available on the system. However, Microsoft does not currently provide an official or supported Linux distribution package for these fonts and the Microsoft typography documentation does not identify Linux as a supported distribution platform for their deployment. Specifically:

• Calibri is included with Windows and Microsoft Office products and is available only through Microsoft products and services where applicable. Reference: Calibri font family - Typography | Microsoft Learn
• Arial is included in Windows font distributions and is not offered by Microsoft as a Linux package.
• Times New Roman is included in Windows font distributions and is not offered by Microsoft as a Linux package. Reference: Font List Windows 11 - Typography | Microsoft Learn
• Arial Unicode MS was historically included with Microsoft Office, but Microsoft states that it is no longer serviced and is no longer installed by current Office versions. Customers with ongoing dependencies are directed to Monotype for updated versions. Reference: Arial Unicode MS font family - Microsoft Learn

2. Licensing Considerations

Licensing is typically the most important consideration for Linux-based document rendering solutions.

Customers requiring rights for server installation, redistribution, enterprise deployment, or similar scenarios should obtain the appropriate licensing rights through Microsoft's font licensing channels.

Key considerations include:

• Microsoft 365, Office, Windows, or Windows Server licenses should not be assumed to automatically grant rights to copy font files from those products onto Linux servers.
• Microsoft does not publish public pricing guidance for server-side font licensing.
• Licensing terms, redistribution rights, deployment restrictions, and procurement options depend on the specific deployment scenario and should be verified through Microsoft's font licensing program or the applicable font vendor.
• For Arial Unicode MS, please notes that updated versions are available through Monotype.

3. Recommended Alternatives

Microsoft does not publish an official Linux font substitution matrix for DOCX-to-PDF rendering. However, commonly adopted alternatives include:

• Calibri -> Carlito
• Arial -> Liberation Sans
• Times New Roman -> Liberation Serif
• Arial Unicode MS -> Noto Sans or Noto Serif CJK (depending on language requirements)

These alternatives are widely used because they provide similar metrics and compatibility characteristics, which can help reduce layout differences during document rendering. However, they are not identical replacements, and exact rendering parity should not be expected.

4. Expected Impact of Font Substitution

When substitute fonts are used instead of the original Microsoft fonts, the following differences may occur:

• Changes in line wrapping and text reflow
• Pagination and page-break differences
• Header and footer positioning changes
• Table width, row height, or cell alignment differences
• Character spacing variations
• Differences in PDF output compared to Microsoft Word

The actual impact depends on how closely the document layout relies on the original font metrics. Complex templates with precise formatting or multilingual content are typically more sensitive to font substitutions.

5. Best Practices for Linux-Based DOCX-to-PDF Rendering

To achieve rendering results that are as close as possible to Microsoft Word, I recommend the following:

• Use the original fonts whenever licensing permits, as this provides the highest level of document fidelity.
• Install all required fonts prior to rendering rather than relying on runtime font substitution or fallback mechanisms.
• Maintain consistent font inventories across development, testing, and production environments to ensure predictable results.
• Use metric-compatible alternatives such as Carlito, Liberation Sans, and Liberation Serif when the original fonts cannot be legally deployed.
• Validate representative customer templates by comparing page counts, line wrapping, table layouts, header/footer positioning, and PDF output.
• Consider modern Unicode font families instead of Arial Unicode MS for multilingual workloads. Microsoft notes that Arial Unicode MS is no longer serviced, and modern applications typically rely on font fallback mechanisms and broader Unicode font families for language coverage.

For additional information, please visit: Font redistribution FAQ - Typography | Microsoft Learn

I hope this information helps clarify the available options and considerations for your Linux-based document generation platform.

If you found this answer helpful, please consider clicking Accept Answer.

Thank you for using Microsoft Q&A!