Q4 2025 (#652)

* ZugferdConformanceLevel

* polishing zugferd

* RadFixedPage and RadFixedDocument articles review

* Updated TextFormatProvider with timeout mechanism.

* Documented AnnotationBorderStyle.

* Stylisic changes.

* Documented ExpandableMemoryStream.

* ExpandableMemoryStream config.

* zugferd code snippet added to the docs solution

* Auto fit text in a stamp annotation KB.

* Update document-themes.md

* KB: Runtime Diagnostics - Showcase (85553)

* Replace Assemblies with NuGet Packages - Getting Started + Introduciton sections.

* Replace Assemblies information with NuGets.

* Update Skia version and HarfBuzz

* Documented JsonFormatProvider.

* Add support for encrypting documents with an AES-128 algorithm

* PdfProcessing: Document API for signing a document using a TimeStamp server

* Replaced the digital signature image

* RadFixedPage: Update the article and specify the Size unit

* NuGet Keys vs API keys

* Fixed ExpandableMemoryStream introduction.

* Resolved incorrect table formatting.

* Added missing bolding.

---------

Co-authored-by: Desislava Yordanova <[email protected]>

Author: YoanKar

_config.yml

@@ -187,6 +187,15 @@ navigation:
     libraries/radspreadprocessing/formats-and-conversion/data-table:
         title: DataTable
         position: 6
+    libraries/radspreadprocessing/formats-and-conversion/json:
+        title: Json
+        position: 7
+    libraries/radspreadprocessing/formats-and-conversion/json/jsonformatprovider:
+        title: JsonFormatProvider
+        position: 1
+    libraries/radspreadprocessing/formats-and-conversion/json/jsonexportsettings:
+        title: JsonExportSettings
+        position: 2
 
     libraries/radspreadprocessing/features/charts:
         title: Charts
@@ -387,7 +396,8 @@ defaults:
 mindotnetversion: "8"
 maxdotnetversion: "9"
 dotnetversions: ".NET 8 and .NET 9"
-skiasharpversion: "3.116.1"
+skiasharpversion: "3.119.1"
+harfbuzzsharp: "8.3.1.2"
 
 # Feedback Form Product Code
 productCode: TDP

distribution-and-licensing/license-key/images/download-license-key.png

@@ -11,7 +11,7 @@ position: 3
 
 The free trial license of Telerik Document Processing is fully functional and will work for an unlimited time.
 
-The only difference between the developer and trial versions of the assemblies is that trial assemblies add a copyright message to the produced documents.
+The only difference between the developer and trial versions of the packages is that trial packages add a copyright message to the produced documents.
 
 In PDF and flow formats, this is a message at the top of the document, whereas for XLSX documents the message is added to a separate sheet.
 

distribution-and-licensing/trial-license-limitations.md

@@ -45,7 +45,7 @@ This approach allows you to setup a local NuGet package source, so you can insta
 >
 >* A version for __.Net Standard 2.0__
 >
->Both versions are available as NuGet packages but with different names. The assemblies for __.NET Standard__ do __not__ contain the word __Windows__ in their name.
+>Both versions are available as NuGet packages but with different names. The packages for __.NET Standard__ do __not__ contain the word __Windows__ in their name.
 
 ## Download from the NuGet server
 

getting-started/Installation/install-nuget-packages.md

@@ -14,9 +14,9 @@ position: 5
 
 Telerik Document Processing is part of several Telerik bundles and is installed following the steps for installing the suite with which you've obtained the product.
 
->Starting from Q1 2016, the Document Processing assemblies have an assembly version which may differ from the assembly version of the other assemblies in the particular suite. 
+>Starting from Q1 2016, the Document Processing packages have a package version which may differ from the package version of the other packages in the particular suite. 
 >
->Starting from R3 2016, only assemblies with a version number ending with .40 suffix are distributed. The libraries don't contain code specific for .NET Framework 4.5, thus an additional version is not needed.
+>Starting from R3 2016, only packages with a version number ending with .40 suffix are distributed. The libraries don't contain code specific for .NET Framework 4.5, thus an additional version is not needed.
 >
 >The changes are synced between the controls that have a dependency on Telerik Document Processing and while the referenced files are from the same release, they should work as expected regardless of the version distinction. 
 
@@ -30,13 +30,13 @@ The libraries can be used through the available NuGet packages.
 
 [Installing Telerik UI for ASP.NET AJAX](http://docs.telerik.com/devtools/aspnet-ajax/installation/which-file-do-i-need-to-install)
 
-When the installation completes, the Telerik Document Processing assemblies will be available in the *AdditionalLibraries* sub-folder.
+When the installation completes, the Telerik Document Processing packages will be available in the *AdditionalLibraries* sub-folder.
 
 ## UI for ASP.NET MVC
 
 [Installing Telerik UI for ASP.NET MVC](https://docs.telerik.com/aspnet-mvc/getting-started/installation/overview)
 
-When the installation completes, the Telerik Document Processing assemblies will be available in the *spreadsheet* sub-folder.
+When the installation completes, the Telerik Document Processing packages will be available in the *spreadsheet* sub-folder.
 
 ## UI for Blazor
 

getting-started/Installation/installing-on-your-computer.md

@@ -3,7 +3,7 @@ title: Available NuGet Packages
 page_title: Available NuGet Packages
 description: Learn how you can use the Telerik Document Processing libraries through NuGet.
 slug: available-nuget-packages
-tags: nuget, document, processing, assembly
+tags: nuget, document, processing, assembly, package
 published: True
 position: 6
 ---
@@ -27,7 +27,7 @@ If your workflow relies on NuGet for package management, you can take advantage
 >
 >* A version for __.Net Standard 2.0__
 >
->Both versions are available as NuGet packages but with different names. The assemblies for __.NET Standard__ do __not__ contain the word __Windows__ in their name.
+>Both versions are available as NuGet packages but with different names. The packages for __.NET Standard__ do __not__ contain the word __Windows__ in their name.
 
 >caption Package lists to use with .NET Standard (left) and .NET Framework (right)
 
@@ -43,8 +43,8 @@ The following list represents the available NuGet packages for the Document Proc
 
 * __Telerik.Windows.Documents.Core:__ The main NuGet package for the Telerik Document Processing libraries. Required when you plan to use the library.
 * __Telerik.Windows.Documents.Fixed:__ The package is required when processing `PDF` documents.
-* __Telerik.Windows.Documents.Fixed.FormatProviders.Ocr:__ This assembly is needed for the [Optical Character Recognition (OCR)]({%slug radpdfprocessing-formats-and-conversion-ocr-ocrformatprovider%}) functionality.
-* __Telerik.Windows.Documents.Tesseract.Ocr:__ This assembly is needed for the [Optical Character Recognition (OCR)]({%slug radpdfprocessing-formats-and-conversion-ocr-ocrformatprovider%}) functionality.
+* __Telerik.Windows.Documents.Fixed.FormatProviders.Ocr:__ This package is needed for the [Optical Character Recognition (OCR)]({%slug radpdfprocessing-formats-and-conversion-ocr-ocrformatprovider%}) functionality.
+* __Telerik.Windows.Documents.Tesseract.Ocr:__ This package is needed for the [Optical Character Recognition (OCR)]({%slug radpdfprocessing-formats-and-conversion-ocr-ocrformatprovider%}) functionality.
 * __Telerik.Windows.Documents.CMapUtils:__ Provides a default implementation for getting the data of a predefined CMap table by a given name.
 * __Telerik.Windows.Documents.Flow:__ The package is part of the WordsProcessing library. Required for processing `HTML`, `DOCX`, `RTF`, and `TXT` documents.
 * __Telerik.Windows.Documents.DrawingML:__ Part of the WordsProcessing library. It is needed for working with shapes inside the documents. 
@@ -63,8 +63,8 @@ The following list represents the available NuGet packages for the Document Proc
 
 * __Telerik.Documents.Core:__ The main NuGet package from the Telerik Document Processing libraries. Required when you plan to use the library.
 * __Telerik.Documents.Fixed:__ The package is required when processing `PDF` documents.
-* __Telerik.Documents.Fixed.FormatProviders.Ocr:__ This assembly is needed for the [Optical Character Recognition (OCR)]({%slug radpdfprocessing-formats-and-conversion-ocr-ocrformatprovider%}) functionality.
-* __Telerik.Documents.Tesseract.Ocr:__ This assembly is needed for the [Optical Character Recognition (OCR)]({%slug radpdfprocessing-formats-and-conversion-ocr-ocrformatprovider%}) functionality.
+* __Telerik.Documents.Fixed.FormatProviders.Ocr:__ This package is needed for the [Optical Character Recognition (OCR)]({%slug radpdfprocessing-formats-and-conversion-ocr-ocrformatprovider%}) functionality.
+* __Telerik.Documents.Tesseract.Ocr:__ This package is needed for the [Optical Character Recognition (OCR)]({%slug radpdfprocessing-formats-and-conversion-ocr-ocrformatprovider%}) functionality.
 * __Telerik.Documents.ImageUtils:__ This package is required when exporting to `PDF` format a document containing images different than Jpeg and Jpeg2000 or ImageQuality different than High. For more information check the [PdfProcessing`s Cross-Platform Support]({%slug radpdfprocessing-cross-platform%}) article.
 * __Telerik.Documents.CMapUtils:__ Provides a default implementation for getting the data of a predefined CMap table by a given name.
 * __Telerik.Documents.Flow:__ The package is part of the Words Processing Library. Required for processing `HTML`, `DOCX`, `RTF`, and `TXT` documents.

getting-started/Installation/nuget-packages.md

@@ -24,7 +24,7 @@ Depending on the scenario, you could take advantage of the different functionali
 
 ## Create a PDF Document From Scratch
 
-**RadPdfProcessing** is intended to work with fixed documents and provides a convenient API to create, modify and export PDF documents. To use its import and export functionalities, you will need to add a reference to the **Telerik.Windows.Documents.Fixed** assembly. 
+**RadPdfProcessing** is intended to work with fixed documents and provides a convenient API to create, modify and export PDF documents. To use its import and export functionalities, you will need to add a reference to the **Telerik.Windows.Documents.Fixed** package. 
 
 You can import and export a document through the respective methods of the **PdfFormatProvider** class.
 
@@ -34,7 +34,7 @@ You can import and export a document through the respective methods of the **Pdf
 
 In scenarios where you need to convert a document from another file format to PDF, you could take advantage of the capabilities of **RadWordsProcessing**. This library allows you to import documents from the most common rich text formats (Docx, HTML, RTF) as well as plain text and export them to PDF. All the supported document formats and the corresponding format providers are listed in the [Formats and Conversion section]({%slug radwordsprocessing-formats-and-conversion%}). 
 
-In order to use the **PdfFormatProvider** of **RadWordsProcessing**, you should add a reference to  the **Telerik.Windows.Documents.Flow.FormatProviders.Pdf** assembly.
+In order to use the **PdfFormatProvider** of **RadWordsProcessing**, you should add a reference to  the **Telerik.Windows.Documents.Flow.FormatProviders.Pdf** package.
 
 >The **PdfFormatProvider** class of RadWordsProcessing resides in the **Telerik.Windows.Documents.Flow.FormatProviders.Pdf namespace**. For more information on how to work with this provider, please read [this topic]({%slug radwordsprocessing-formats-and-conversion-pdf-pdfformatprovider%}).
 
@@ -63,7 +63,7 @@ In order to use the **PdfFormatProvider** of **RadWordsProcessing**, you should
 
 While the so far discussed libraries allow working with text documents, with RadSpreadProcessing you can create, import and export tabular data. This library supports the most common file formats for storing spreadsheet documents - Xlsx, CSV. All format providers are listed and described in the corresponding [Formats and Conversion section]({%slug radspreadprocessing-formats-and-conversion-pdf-pdfformatprovider%}). 
 
-In order to enable the export to PDF in RadSpreadProcessing, you will need to add a reference to the **Telerik.Windows.Documents.Spreadsheet.FormatProviders.Pdf** assembly.
+In order to enable the export to PDF in RadSpreadProcessing, you will need to add a reference to the **Telerik.Windows.Documents.Spreadsheet.FormatProviders.Pdf** package.
 
 >The **PdfFormatProvider** class of RadSpreadProcessing resides in the **Telerik.Windows.Documents.Spreadsheet.FormatProviders.Pdf namespace**. For more information on how to work with this provider, please read [this topic]({%slug radspreadprocessing-formats-and-conversion-pdf-pdfformatprovider%}).
 

getting-started/Installation/pdf-export.md

@@ -17,11 +17,11 @@ The Telerik Document Processing libraries that we use in this guide are UI-indep
 
 >important Please install **<PackageReference Include="Telerik.Licensing" Version="1.*" />**.
 
-Since we distribute Telerik Document Processing libraries as an addition to several Telerik UI component bundles, chances are that the libraries are already installed on your system. In this case, all you need is to locate them. The table below provides links to the installation instructions for each of the Telerik UI component suites that give you access to the Telerik Document Processing libraries. If the standard installation of your Telerik UI component suite includes the Document Processing assemblies, the table also shows their default location.
+Since we distribute Telerik Document Processing libraries as an addition to several Telerik UI component bundles, chances are that the libraries are already installed on your system. In this case, all you need is to locate them. The table below provides links to the installation instructions for each of the Telerik UI component suites that give you access to the Telerik Document Processing libraries. If the standard installation of your Telerik UI component suite includes the Document Processing packages, the table also shows their default location.
 
->tipRegardless of the Telerik UI components suite that you use, you can always get the Document Processing assemblies as NuGet packages from the [Telerik NuGet server]({%slug installation-nuget-packages%}).
+>tipRegardless of the Telerik UI components suite that you use, you can always get the Document Processing packages as NuGet packages from the [Telerik NuGet server]({%slug installation-nuget-packages%}).
 
-| UI Components suite | Installation instructions | Default location of the Document Processing assemblies |
+| UI Components suite | Installation instructions | Default location of the Document Processing packages |
 |--------------------|---------------------------|------------------------------------------------|
 | UI for ASP.NET AJAX | [Installing Telerik UI for ASP.NET AJAX](http://docs.telerik.com/devtools/aspnet-ajax/installation/which-file-do-i-need-to-install) | <ul><li>`C:\Program Files (x86)\Progress\Telerik UI for ASP.NET AJAX [version]\AdditionalLibraries\Bin40`</li><li>`C:\Program Files (x86)\Progress\Telerik UI for ASP.NET AJAX [version]\AdditionalLibraries\Bin45`</li></ul> |
 | UI for ASP.NET MVC | [Installing Telerik UI for ASP.NET MVC](http://docs.telerik.com/kendo-ui/aspnet-mvc/introduction#installation) |  <ul><li>`C:\Program Files (x86)\Progress\Telerik UI for ASP.NET MVC [version]\dpl\net40`</li><li>`C:\Program Files (x86)\Progress\Telerik UI for ASP.NET MVC [version]\dpl\netstandard`</li></ul> |
@@ -46,29 +46,29 @@ As we are going to create a UI-Independent example, we will use a console projec
 
 ## Step 3: Add a Telerik Document Processing Library to a Project
 
-This sample application will use [RadWordsProcessing]({%slug radwordsprocessing-overview%}). In this step, we must add the required assemblies.
+This sample application will use [RadWordsProcessing]({%slug radwordsprocessing-overview%}). In this step, we must add the required packages.
 
-1. Reference the assemblies that provide the __RadWordsProcessing__ functionality:
+1. Reference the packages that provide the __RadWordsProcessing__ functionality:
 
 	For .NET Framework project:
-	  * __Telerik.Windows.Documents.Core.dll__
-	  * __Telerik.Windows.Documents.Flow.dll__
+	  * __Telerik.Windows.Documents.Core__
+	  * __Telerik.Windows.Documents.Flow__
 
 	For .NET Standard ({{site.dotnetversions}}) project:
-	  * __Telerik.Documents.Core.dll__
-	  * __Telerik.Documents.Flow.dll__
+	  * __Telerik.Documents.Core__
+	  * __Telerik.Documents.Flow__
 
 	>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.
 
-1. Reference the assembly that allows you to export the content as a PDF file:
+1. Reference the package that allows you to export the content as a PDF file:
 
 	For .NET Framework project:
-	  * __Telerik.Windows.Documents.Flow.FormatProviders.Pdf.dll__
+	  * __Telerik.Windows.Documents.Flow.FormatProviders.Pdf__
 
 	For .NET Standard ({{site.dotnetversions}}) project:
-	  * __Telerik.Documents.Flow.FormatProviders.Pdf.dll__
+	  * __Telerik.Documents.Flow.FormatProviders.Pdf__
 
-> The Document Processing assemblies for {{site.dotnetversions}} don't contain "Windows" in their names.
+> The Document Processing packages for {{site.dotnetversions}} don't contain "Windows" in their names.
 
 ## Step 4: Create a Document