Skip to content

Commit 6e7019a

Browse files
Merge pull request #578 from telerik/new-kb-validating-fonts-document-processing-9ec1f0c564dd4019abd164280fc1feea
Added new kb article validating-fonts-document-processing
2 parents 5045719 + 6f7cc32 commit 6e7019a

File tree

3 files changed

+66
-2
lines changed

3 files changed

+66
-2
lines changed
Lines changed: 63 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,63 @@
1+
---
2+
title: Validating Fonts when Using Telerik Document Processing
3+
description: Learn how to identify incomplete or corrupt TTF font files that cause content issues while exporting PDF files using Telerik Document Processing.
4+
type: how-to
5+
page_title: Identifying incomplete or corrupted font files causing content issues in exported PDF dcouments
6+
meta_title: Identifying incomplete or corrupted font files causing content issues in exported PDF documents
7+
slug: validating-fonts-pdf-document-processing
8+
tags: word, document, processing, ttf, font, validation, pdf, export, spread, fixed, flow, excel
9+
res_type: kb
10+
ticketid: 1690314
11+
---
12+
13+
## Environment
14+
15+
| Version | Product | Author |
16+
| ---- | ---- | ---- |
17+
| 2025.2.520| Telerik Document Processing |[Desislava Yordanova](https://www.telerik.com/blogs/author/desislava-yordanova)|
18+
19+
## Description
20+
21+
When exporting a document to PDF format using the Telerik [Document Processing Librararies]({%slug introduction%}), content issues may occur due to incomplete or corrupted font files. These issues can arise if the font file is incomplete, corrupted, or missing required font tables. This results in missing or improperly rendered text in the exported PDF.
22+
23+
This knowledge base article gives some tips and tricks how to validate fonts used in Telerik Document Processing and what tools can check for font file's integrity.
24+
25+
## Solution
26+
27+
To ensure a font file is complete and compatible with Telerik Document Processing, follow these steps:
28+
29+
* **Open the Font in a Font Viewer**
30+
31+
Double-click the TTF file to open it in the system font viewer. Inspect whether all expected characters display correctly and ensure no error messages appear.
32+
33+
* **Test the Font in Other Applications**
34+
35+
Install the font on your system and use it in applications like Word or Notepad. Verify that all characters render correctly.
36+
37+
* **Compare File Size and Metadata**
38+
39+
Compare the file size and properties of the font with an official or known-good version. Noticeable differences can indicate corruption or missing data.
40+
41+
* **Use Font Validation Tools**
42+
Validate the font file with tools like:
43+
- [FontForge](https://fontforge.org/)
44+
- [Microsoft Font Validator](https://github.com/Microsoft/Font-Validator)
45+
These tools check for missing tables, corrupt glyphs, and other font-related issues.
46+
47+
* **Check Required Styles**
48+
49+
Verify that all required styles (Regular, Bold, Italic, etc.) are available if your document uses them. Missing styles can cause fallback or rendering issues.
50+
51+
### Recommendations
52+
53+
- Validate fonts from third-party sources before integrating them.
54+
- Request official font packages or sources for reliable compatibility.
55+
- Replace problematic font files with known-good versions to resolve rendering issues.
56+
- You can utilize a [FontsProvider]({%slug pdfprocessing-implement-fontsprovider%}) implementation to identify all fonts and styles used in the document. Thus, you can log missing or problematic fonts during testing for early detection.
57+
58+
## See Also
59+
60+
- [FontForge](https://fontforge.org/)
61+
- [Microsoft Font Validator](https://github.com/Microsoft/Font-Validator)
62+
- [Fonts - Cross-Platform support]({%slug radpdfprocessing-cross-platform-fonts%})
63+
- [Standard Fonts in PdfProcessing]({%slug radpdfprocessing-concepts-fonts%})

libraries/radpdfprocessing/concepts/fonts.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -164,6 +164,6 @@ You can create fonts that are not explicitly registered. Creating a font that is
164164
* [FontsRepository](https://docs.telerik.com/devtools/document-processing/api/Telerik.Windows.Documents.Fixed.Model.Fonts.FontsRepository.html)
165165
* [TextFragment]({%slug radpdfprocessing-model-textfragment%})
166166
* [Preserving the Font in PDF Export from Excel]({%slug preserve-font-boldness-pdf-export-radspreadprocessing%})
167-
* [How to Prevent Text with Special Characters from Being Cut Off when converting HTML to PDF using RadWordsProcessing]({%slug prevent-text-cut-off-pdf-conversion-radwordsprocessing%})
167+
* [How to Prevent Text with Special Characters from Being Cut Off when converting HTML to PDF using RadWordsProcessing]({%slug prevent-text-cut-off-pdf-conversion-radwordsprocessing%})
168+
* [Validating Fonts when Using Telerik Document Processing]({%slug validating-fonts-pdf-document-processing%})
168169
* [Resolving Apostrophe Character Being Replaced with Copyright Symbol in Filled PDF AcroForm]({%slug apostrophe-character-replaced-copyright-symbol-acroform%})
169-

libraries/radpdfprocessing/cross-platform/fonts.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,4 +27,5 @@ You can find a detailed **FixedExtensibilityManager** and **FontsProvider** desc
2727
* [Inserting Special Symbols in PDF using RadPdfProcessing]({%slug inserting-special-symbols-pdf-radpdfprocessing%})
2828
* [How to Eliminate Formatting Issues when Exporting XLSX to PDF Format]({%slug exporting-xlsx-to-pdf-formatting-issues%})
2929
* [Resolving Missing Content in Exported PDF Files]({%slug missing-content-word-to-pdf-radwordsprocessing%})
30+
* [Validating Fonts when Using Telerik Document Processing]({%slug validating-fonts-pdf-document-processing%})
3031

0 commit comments

Comments
 (0)