We’re converting a Word document with Optima LT Std font applied inside to images using .Viewer, it’s properly displayed in the Word application, but in image it’s a wrong font.
Same happening if converted online:
https://products.groupdocs.app/viewer/app/?lang=en&file=81441dfe-1efc-411b-b7f2-39ab043c1e86%2Felc_letterhead_generic_2025_20250609141355343_20250703040306944.docx
Attaching document here ^
When converting a Word document that uses the Optima LT Std font to images using GroupDocs.Viewer, you may encounter issues where the font is displayed incorrectly in the generated images. This can happen due to the absence of the specific font on the server or environment where the conversion is taking place, leading to font substitution with a default or available font.
To address this issue, consider the following steps:
Ensure Font Availability: Make sure that the Optima LT Std font is installed on the server or environment where the conversion is being performed. If the font is not available, GroupDocs.Viewer will substitute it with a different font, which can lead to layout discrepancies.
Use Font Settings: You can specify custom font settings in your code to ensure that the correct fonts are used during rendering. This can be done by setting up a font source that points to the directory containing the required fonts.
Check Rendering Options: Review the rendering options you are using in GroupDocs.Viewer. For example, enabling options like RenderTextAsImage can help maintain the appearance of the text as it appears in the original document.
Here is a sample code snippet that demonstrates how to set up font settings:
using GroupDocs.Viewer;
using GroupDocs.Viewer.Options;
var viewer = new Viewer("path/to/document.docx");
var viewOptions = HtmlViewOptions.ForEmbeddedResources();
viewOptions.FontsToExclude.Add("Optima LT Std"); // Exclude if necessary
viewer.View(viewOptions);
By ensuring that the required fonts are installed and properly configured, you should be able to achieve accurate rendering of your documents in the desired format.
For more detailed information, you can refer to the GroupDocs documentation on font management and troubleshooting rendering issues.
Sources:
[1]: Exclude fonts | Documentation - GroupDocs Documentation
[2]: Troubleshooting - GroupDocs Documentation
Hi Matt,
I additionally analyzed the provided document elc_letterhead_generic_2025_20250609141355343_20250703040306944.docx (145.3 KB) . It uses 2 fonts “Optima LT Std Regular” and “Times New Roman Bold” in its content. From what I can see the “Optima LT Std Regular” is not a standard font because it is not installed in my Windows 10 fonts folder by default and also is absent in the Cloud fonts cache. It also is not embedded into the DOCX file itself.
So on my machine, when I try to convert the attached document to HTML, the GroupDocs.Viewer performs a font substitution - “Optima LT Std Regular” is replaced onto the “Palatino Linotype” font, because this font is present on my local PC and it is considered to be the most closest to the original.
In order to render the document correctly, you need to find the original “Optima LT Std Regular”, put it to the machine, where the GroupDocs.Viewer is running, and specify it using the font source, as it is described in this article: Set custom fonts.
If I understood something wrong, please tell us a bit more: sample of source code, screenshot of how the document is and how it should be.
With best regards,
Denis Gvardionov