-
Notifications
You must be signed in to change notification settings - Fork 41
Added new kb article validating-fonts-document-processing #578
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
dessyordanova
merged 5 commits into
master
from
new-kb-validating-fonts-document-processing-9ec1f0c564dd4019abd164280fc1feea
Jul 16, 2025
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
6a0b5e8
Added new kb article validating-fonts-document-processing
4df9ccc
new KB for fonts validation - general info
dessyordanova 2f59589
Merge branch 'master' into new-kb-validating-fonts-document-processin…
dessyordanova bdc7aae
addressed Yoan's feedback
dessyordanova 6f7cc32
Merge branch 'new-kb-validating-fonts-document-processing-9ec1f0c564d…
dessyordanova File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,63 @@ | ||
--- | ||
title: Validating Fonts when Using Telerik Document Processing | ||
description: Learn how to identify incomplete or corrupt TTF font files that cause content issues while exporting PDF files using Telerik Document Processing. | ||
type: how-to | ||
page_title: Identifying incomplete or corrupted font files causing content issues in exported PDF dcouments | ||
meta_title: Identifying incomplete or corrupted font files causing content issues in exported PDF documents | ||
slug: validating-fonts-pdf-document-processing | ||
tags: word, document, processing, ttf, font, validation, pdf, export, spread, fixed, flow, excel | ||
res_type: kb | ||
ticketid: 1690314 | ||
--- | ||
|
||
## Environment | ||
|
||
| Version | Product | Author | | ||
| ---- | ---- | ---- | | ||
| 2025.2.520| Telerik Document Processing |[Desislava Yordanova](https://www.telerik.com/blogs/author/desislava-yordanova)| | ||
|
||
## Description | ||
|
||
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. | ||
|
||
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. | ||
|
||
## Solution | ||
|
||
To ensure a font file is complete and compatible with Telerik Document Processing, follow these steps: | ||
|
||
* **Open the Font in a Font Viewer** | ||
|
||
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. | ||
|
||
* **Test the Font in Other Applications** | ||
|
||
Install the font on your system and use it in applications like Word or Notepad. Verify that all characters render correctly. | ||
|
||
* **Compare File Size and Metadata** | ||
|
||
Compare the file size and properties of the font with an official or known-good version. Noticeable differences can indicate corruption or missing data. | ||
|
||
* **Use Font Validation Tools** | ||
Validate the font file with tools like: | ||
- [FontForge](https://fontforge.org/) | ||
- [Microsoft Font Validator](https://github.com/Microsoft/Font-Validator) | ||
These tools check for missing tables, corrupt glyphs, and other font-related issues. | ||
|
||
* **Check Required Styles** | ||
|
||
Verify that all required styles (Regular, Bold, Italic, etc.) are available if your document uses them. Missing styles can cause fallback or rendering issues. | ||
|
||
### Recommendations | ||
|
||
- Validate fonts from third-party sources before integrating them. | ||
- Request official font packages or sources for reliable compatibility. | ||
- Replace problematic font files with known-good versions to resolve rendering issues. | ||
- 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. | ||
|
||
## See Also | ||
|
||
- [FontForge](https://fontforge.org/) | ||
- [Microsoft Font Validator](https://github.com/Microsoft/Font-Validator) | ||
- [Fonts - Cross-Platform support]({%slug radpdfprocessing-cross-platform-fonts%}) | ||
- [Standard Fonts in PdfProcessing]({%slug radpdfprocessing-concepts-fonts%}) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.