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
Unlike the .NET Framework one, RadPdfProcessing’s .NET Standardversion does not offer a default mechanism to read fonts. The **FixedExtensibilityManager** class is exposed to help implement this functionality.
14
+
Unlike the .NET Framework and .NET (Target OS: *Windows*) version, the RadPdfProcessing's **.NET Standard** and **.NET (Target OS: *None*)**version does not offer a default mechanism for reading fonts. The **FixedExtensibilityManager** class is exposed to help implement this functionality.
14
15
15
16
## Setting and Exporting Fonts
16
17
17
-
PdfProcessing needs to have access to the font data so that it can read it and add it to the PDF file. That is why, to allow the library to create and use fonts, you will need to provide an implementation of the **FontsProviderBase** abstract class and set this implementation to the <u>FontsProvider</u> property of the **FixedExtensibilityManager**.
18
+
RadPdfProcessing needs access to the font data, so that it can read it and add it to the PDF file. That is why, to allow the library to create and use fonts, you will need to provide an implementation of the **FontsProviderBase** abstract class and set this implementation to the **<u>FontsProvider</u>** property of the **FixedExtensibilityManager**.
18
19
19
20
You can find a detailed **FixedExtensibilityManager** and **FontsProvider** descripiton and implementaion in the [How to implement a FontsProvider]({%slug pdfprocessing-implement-fontsprovider%}) article.
20
21
21
-
>important If the FontsProvider property is not set, a default font will be used when exporting the document.
22
+
>caution If the FontsProvider property is not set, a default font will be used when exporting the document in cross-platform applications.
23
+
24
+
>important When converting a document (e.g. DOCX, HTML, etc.) to PDF format in **.NET Standard** and **.NET (Target OS: *None*)** projects, fonts from the original document are not automatically maintained in the PDF unless you explicitly provide the font data. This is especially important when the original document uses non-standard or custom fonts. The PdfProcessing library requires access to the actual font files to embed them in the PDF. If font data is not provided, the PDF model will substitute the missing fonts with standard ones, resulting in a mismatch between the original document and the exported PDF file.
@@ -26,7 +27,7 @@ To export images different than Jpeg and Jpeg2000 or ImageQuality different than
26
27
|Assembly/ NuGet package|Description|
27
28
|----|----|
28
29
|**Telerik.Documents.ImageUtils**|This assembly is currently not available in UI for Xamarin.|
29
-
|**SkiaSharp.NativeAssets.*** (version 2.88.8)|May differ according to the used platform. For **Linux** use <b>SkiaSharp.NativeAssets.Linux.NoDependencies|
30
+
|**SkiaSharp.NativeAssets.*** (version {{site.skiasharpversion}})|May differ according to the used platform. For **Linux** use <b>SkiaSharp.NativeAssets.Linux.NoDependencies|
30
31
|**SkiaSharp.Views.Blazor** and **wasm-tools**|For Blazor Web Assembly.|
31
32
32
33
>important With the [R2 2023 changes](https://docs.telerik.com/devtools/document-processing/libraries/radpdfprocessing/changes-and-backward-compatibility/backward-compatibility#whats-different-in-2023-r2) SkiaSharp replaced ImageSharp as the required dependency.
@@ -118,3 +119,7 @@ The following example depends on the [Magick.NET](https://www.nuget.org/packages
118
119
119
120
>note A complete SDK example of a custom implementation JpegImageConverterBase is available on our [GitHub repository](https://github.com/telerik/document-processing-sdk/tree/master/PdfProcessing/CustomJpegImageConverter).
**Telerik Document Processing** comes with **.NET Core** & **.NET Standard** support. There is a set of binaries built against the .NET Core & .NET Standard which you can reference in an application.
14
+
The [Telerik Document Processing]({%slug introduction%}) libraries are compatible across different .NET implementations, including .NET Standard, {{site.dotnetversions}} (Target OS: *None*), and newer versions. There is a set of binaries built against the .NET Standard version which you can reference in an application.
15
15
16
-
>note The binaries compatible with .NET Standardare distributed with the packages targeting .NET Standard and .NET Core. You can obtain the assemblies through the **UI for ASP.NET Core**, **UI for Blazor**, **UI for Xamarin**, and **UI for WinUI** suites. There are **NuGet** packages as well that you can access if you have a license for one of the above mentioned suites.
16
+
>note The binaries compatible with .NET Standard, {{site.dotnetversions}} (Target OS: *None*) are distributed with the packages targeting .NET Standard. You can obtain the assemblies through the **UI for ASP.NET Core**, **UI for Blazor**, **UI for Xamarin**, and **UI for WinUI** suites. There are **NuGet** packages as well that you can access if you have a license for one of the above mentioned suites.
17
17
18
18
## Assembly References
19
19
20
-
In order to use the model of the **RadPdfProcessing** library in your cross-platform project, you need to add references to the following **.Net Standard** assemblies:
20
+
In order to use the model of the **RadPdfProcessing** library in your cross-platform project, you need to add references to the following **.Net Standard** assemblies/ NuGet packages:
21
21
22
22
***Telerik.Documents.Core.dll**
23
23
***Telerik.Documents.Fixed.dll**
24
24
*~~Telerik.Zip.dll~~*
25
25
26
-
>note *As of **Q2 2025** the Zip Library will no longer be used as an internal dependency in the rest of the Document Processing Libraries - PdfProcessing, WordsProcessing, SpreadProcessing, SpreadStreamProcessing. It will be replaced by the System.IO.Compression. We will continue to ship the Telerik Zip Library as a standalone library so clients can still use it separately.
26
+
>note As of [Q2 2025](https://www.telerik.com/support/whats-new/telerik-document-processing/release-history/progress-telerik-document-processing-2025-2-520-changelog) the Zip Library will no longer be used as an internal dependency in the rest of the Document Processing Libraries - PdfProcessing, WordsProcessing, SpreadProcessing, SpreadStreamProcessing. It will be replaced by the System.IO.Compression. We will continue to ship the Telerik Zip Library as a standalone library so clients can still use it separately.
27
27
28
28
To export images different than Jpeg and Jpeg2000 or ImageQuality different than High you will need to add references to the following **.Net Standard** assembly:
29
29
@@ -34,7 +34,7 @@ To export images different than Jpeg and Jpeg2000 or ImageQuality different than
34
34
35
35
## Fonts and Images
36
36
37
-
The .NET Framework version of PdfProcessing comes with out-of-the-box functionality to read fonts, convert images, and scale their quality. The .NET Standard specification, however, does not specify APIs to provide such functionalities built in the library.
37
+
The .NET Framework and .NET (Target OS: *Windows*) versions of PdfProcessing comes with out-of-the-box functionality to read fonts, convert images, and scale their quality. The .NET Standard specification, however, does not specify APIs to provide such functionalities built in the library.
38
38
In order to provide the necessary extensibility mechanisms for working with fonts and images, the .NET Standard version of **RadPdfProcessing** exposes the **FixedExtensibilityManager** class.
39
39
More information, including code samples on how to configure the **FixedExtensibilityManager** is available in the [**Fonts**]({%slug radpdfprocessing-cross-platform-fonts%}) and [**Images**]({%slug radpdfprocessing-cross-platform-images%}) articles respectively.
40
40
@@ -44,7 +44,9 @@ More information, including code samples on how to configure the **FixedExtensib
*[What Versions of Document Processing Libraries are Distributed with the Telerik Products](%slug distribute-telerik-document-processing-libraries-net-versions%)
Copy file name to clipboardExpand all lines: libraries/radpdfprocessing/features/handling-document-exceptions.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,6 +72,7 @@ As of **Q1 2025** the [PdfExportSettings]({%slug radpdfprocessing-formats-and-co
72
72
|__NotSupportedStreamTypeException__| Represents an exception for a stream type which is not supported. A stream is not supported if it does not support read or seek. This exception has a SupportSeek and SupportRead properties which specify whether the stream supports them.|
73
73
|__NotSupportedXObjectTypeException__| Represents an exception for a document with an XObject type which is not supported.|
74
74
|**DuplicatedJavaScriptNameException**|Represents an exception for JavaScript with a duplicated name.|
75
+
|**NotSupportedImageFormatException**|Represents an exception thrown when attempting to use an image format that is not supported by the library.|
75
76
|**InvalidAnnotationException**|Represents an exception for an annotation which is not valid. *(Introduced in Q1 2025)*|
76
77
|**NotSupportedAnnotationException**|Represents an exception for an annotation which is not supported.*(Introduced in Q1 2025)*|
77
78
|**InvalidImageDataException**|Represents an exception for importing an invalid image data.*(Introduced in Q1 2025)*|
<sub><i>May differ according to the used platform. For <b>Linux</b> (since <b>Q2 2025</b>) use <b>SkiaSharp.NativeAssets.Linux.NoDependencies</b> and execute the <a href="#linux-specific-steps">required commands.</a></i></sub>
0 commit comments