You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -30,7 +30,7 @@ This KB article also answers the following questions:
30
30
## Solution
31
31
To resolve the issue with text cut off and ensure all characters, including special ones, are correctly displayed, implement a custom `FontsProvider`. This provider will supply the necessary font data to the PdfProcessing library, enabling it to correctly render all characters.
32
32
33
-
1. Implement a custom [FontsProvider]({%slug pdfprocessing-implement-fontsprovider%}) by extending `FontsProviderBase` and override the `GetFontData` method. This method should return the font data for the required fonts, including those with special characters.
33
+
1\. Implement a custom [FontsProvider]({%slug pdfprocessing-implement-fontsprovider%}) by extending `FontsProviderBase` and override the `GetFontData` method. This method should return the font data for the required fonts, including those with special characters.
34
34
35
35
The following example shows how to handle *Tahoma, Arial and Segoe UI* fonts. When using other fonts, the custom implementation should be modified and further extended with the respective fonts.
36
36
@@ -81,12 +81,12 @@ The following example shows how to handle *Tahoma, Arial and Segoe UI* fonts. Wh
81
81
}
82
82
```
83
83
84
-
2. Before converting your HTML document to PDF, set the custom `FontsProvider` to the `FontsProvider` property of the `FixedExtensibilityManager`.
84
+
2\. Before converting your HTML document to PDF, set the custom `FontsProvider` to the `FontsProvider` property of the `FixedExtensibilityManager`.
Following these steps will ensure access to the necessary font data, preventing text from being cut off and ensuring all characters, including those with special characters, are properly rendered in the PDF document.
0 commit comments