Merge branch 'new-kb-validating-fonts-document-processing-9ec1f0c564dd4019abd164280fc1feea' of https://github.com/telerik/document-processing-docs into new-kb-validating-fonts-document-processing-9ec1f0c564dd4019abd164280fc1feea

Author: dessyordanova

distribution-and-licensing/license-key/activation-errors-and-warnings.md

@@ -32,7 +32,7 @@ When using the product in a project with an expired or missing license, the _Tel
 |----|----|----|
 |`No Telerik or Kendo UI product references detected in project`|TKL001|<ul><li>If you use Telerik products and see this message, update the Telerik.Licensing package to version 1.4.9 or later.</li><li>If you do not use Telerik products, remove the Telerik.Licensing NuGet reference from your project.</li></ul>|
 |`No Telerik and Kendo UI License file found`|TKL002|[Install a license key]({%slug setting-up-license-key%}) to activate the UI components and remove the error message.|
-|`Corrupted Telerik and Kendo UI License Key content`|TKL003|[Download a new license key]({%slug setting-up-license-key%}#downloading-the-license-key) and install it to activate the UI components and remove the error message.|
+|`Corrupted Telerik and Kendo UI License Key content in: [file path or environment variable name]`|TKL003|<ul><li>If you use a `telerik-license.txt` file to activate the components, [download a new license key file]({%slug setting-up-license-key%}) and place it in your home directory. Make sure to use a license key and not a script key.</li><li>If you use the `TELERIK_LICENSE` environment variable to store your license key, [download a new license key]({%slug setting-up-license-key%}), update the content of the environment variable, and make sure it contains the entire key.</li></ul>|
 |`Unable to locate licenses for all products`|TKL004|Your license is not valid for all Telerik and Kendo products added to your project. If you have already purchased the required license, then update your license key]({%slug setting-up-license-key%}).|
 |`"Telerik Document Processing Libraries" product is not listed in your current license file.`|TKL101|Review the purchase options for the listed products. Alternatively, remove the references to the listed packages from _package.json._|
 |`Your current license has expired.`|TKL102|You are using a product version released outside the validity period of your perpetual license. To remove the error message, do either of the following: <br> - Renew your subscription and [download a new license key]({%slug setting-up-license-key%}#downloading-the-license-key). <br> - Downgrade to a product version included in your perpetual license as indicated in the message.|

distribution-and-licensing/license-key/adding-license-key-ci-cd-services.md

@@ -127,4 +127,5 @@ public class Function
 * [Unable to find package Telerik.Licensing]({%slug dpl-package-update-failure-license%})
 * [Handling License Key File Name and Environment Variable Name Changes in the 2025 Q1 Release]({%slug handling-license-file-name-changes%})
 * [Telerik.Licensing NuGet package is not available on the Telerik NuGet feed]({%slug dpl-telerik-licensing-nuget-feed%})
+* [Telerik License Approaches](https://github.com/LanceMcCarthy/DevOpsExamples?tab=readme-ov-file#telerik-license-approaches)
 

distribution-and-licensing/license-key/setting-up-license-key.md

@@ -38,6 +38,9 @@ To activating the Document Processing Libraries:
 ```xml
 <PackageReference Include="Telerik.Licensing" Version="1.*" />
 ```
+
+>important The **Telerik.Licensing** verifies the DevSeat association at the time your classlib is built, and also provisions at runtime licenses in the Root app. When you have a setup such as **"Root app -> classlib -> Telerik UI"**, the Telerik UI will execute and verify the licensing for the classlib, but will not be applied transitively in the Root app. That's why you **need to add the Telerik.Licensing NuGet package reference to Root app manually**.
+
 When you build the project, the _Telerik.Licensing_ NuGet package automatically locates the license file and uses it to activate the product.
 
 >important If your project doesn’t use NuGet packages, see [Adding a License Key to Projects without NuGet References](#adding-a-license-key-to-projects-without-nuget-references).
@@ -70,4 +73,6 @@ Whenever you purchase a new license or renew an existing one, always [download a
 * [Handling License Key File Name and Environment Variable Name Changes in the 2025 Q1 Release]({%slug handling-license-file-name-changes%})
 * [Telerik.Licensing NuGet package is not available on the Telerik NuGet feed]({%slug dpl-telerik-licensing-nuget-feed%})
 * [Diagnostic Options for Telerik Licensing]({%slug telerik-trial-version-message-diagnostic-options%})
+* [Resolving License Validation Issues in Telerik Document Processing Libraries]({%slug license-not-recognized-telerik-document-processing-libraries%})
+* [Telerik License Approaches](https://github.com/LanceMcCarthy/DevOpsExamples?tab=readme-ov-file#telerik-license-approaches)
 

distribution-and-licensing/redistributing-telerik-document-processing.md

@@ -24,6 +24,8 @@ Telerik Document Processing is part of several Telerik bundles and is licensed u
 | UI for .NET MAUI ||
 | UI for Xamarin ||
 
+>important Protecting the Telerik dlls is required only with versions prior to **2025 Q2 (2025.2.520)**. With the introduction of our new [licensing mechanism](https://www.telerik.com/blogs/license-key-files-telerik-kendo-ui-products-2025-update), Telerik UI suites have simplified deployment requirements. __Starting with 2025 Q2, users are no longer required to protect the Telerik assemblies__. Instead, the respective Telerik product now requires [installing a license key]({%slug setting-up-license-key%}). Applications without a valid license will continue to function normally, but will contain a watermark.
+
 ## Using the Telerik Document Processing Libraries in Your Solutions
 
 In order to include the Telerik Document Processing libraries in your application, you should build the source code as described below. The source code of the Document Processing libraries is distributed together with the above-listed products' source code and is available for download from the client's account. 

getting-started/download-product-files.md

@@ -47,4 +47,5 @@ Since the **Telerik Document Processing** is a part of several [Telerik bundles]
 ## See Also
 
 * [What Versions of Document Processing Libraries are Distributed with the Telerik Products]({%slug distribute-telerik-document-processing-libraries-net-versions%})
-* [Latest Internal Build (Preview Version)]({%slug obtain-use-latest-internal-build-version%})
+* [Latest Internal Build (Preview Version)]({%slug obtain-use-latest-internal-build-version%})
+* [Release History]({%slug dpl-release-history%})

introduction.md

@@ -55,6 +55,7 @@ Telerik Document Processing features the following libraries:
 |**Any document. Any Business.**|The Telerik Document Processing is suitable for various business cases and scenarios, where document creation or manipulation is required|
 |**Support for Variety of File Formats**|The Telerik Document Processing includes 5 libraries for manipulating [Office Open XML](https://en.wikipedia.org/wiki/Office_Open_XML) file formats and PDF documents in your application.|
 |**Timeout Mechanism**|[Timeout Mechanism]({%slug timeout-mechanism-in-dpl%}) for importing and exporting documents. The **Import** and **Export** methods of all FormatProviders have a mandatory *TimeSpan?* timeout parameter after which the operation will be cancelled.|
+|**GenAI-powered Document Insights**|Enables you to easily extract insights from PDF documents using Large Language Models (LLMs). This functionality enables you to summarize document content and ask questions about it, with the AI providing relevant answers based on the document's content. [Read More]({%slug radpdfprocessing-features-gen-ai-powered-document-insights-overview%})|
 
 For more details about the benefits of using Telerik Document Processing, see the [Telerik Document Processing product overview page](https://www.telerik.com/document-processing-libraries).
 

knowledge-base/apostrophe-character-replaced-copyright-symbol-acroform.md

@@ -0,0 +1,72 @@
+---
+title: Resolving Apostrophe Character Being Replaced with Copyright Symbol in Filled PDF AcroForm
+description: Learn how to address the issue where an apostrophe character is replaced by a copyright symbol in a filled PDF AcroForm using RadPdfProcessing for Document Processing.
+type: how-to
+page_title: Fixing Apostrophe Display Issue in PDF AcroForm Fields
+meta_title: Fixing Apostrophe Display Issue in PDF AcroForm Fields
+slug: apostrophe-character-replaced-copyright-symbol-acroform
+tags: processing, document, pdf, acroform, font, encoding, text, field, xfa
+res_type: kb
+ticketid: 1692742
+---
+
+<style>
+img[alt$="><"] {
+  border: 1px solid lightgrey;
+}
+
+</style>
+
+## Environment
+
+| Version | Product | Author | 
+| ---- | ---- | ---- | 
+| 2025.2.520| RadPdfProcessing |[Desislava Yordanova](https://www.telerik.com/blogs/author/desislava-yordanova)| 
+
+## Description
+
+Learn how to address the issue where a special symbol (e.g. apostrophe character) is replaced by a copyright (or other) symbol in a filled PDF AcroForm using RadPdfProcessing. When the form is opened for editing in a viewer (like Adobe Acrobat), the character appears correctly as an apostrophe in the editor itself. 
+
+![apostrophe-character-replaced-copyright-symbol-acroform ><](images/apostrophe-character-replaced-copyright-symbol-acroform.gif)  
+
+>note This might be reproduced with other symbols as well, not only with the apostrophe character. Usually, such behavior may occur with XFA forms. However, from PDF 2.0 (ISO 32000-2) the XFA forms are depreciated.
+
+## Solution
+
+This issue is likely caused by the font encoding used in the [AcroForm]({%slug radpdfprocessing-model-interactive-forms-acroform%}) fields. If the font does not properly support the character encoding for the apostrophe or is not embedded or referenced correctly, such substitution may occur.
+
+To resolve this issue, set the font of the AcroForm fields to one of the [14 standard PDF fonts]({%slug radpdfprocessing-concepts-fonts%}), such as Helvetica, Times, or Courier. These fonts have broad character support and do not require embedding.
+
+### Steps:
+
+1. Iterate through all form fields in `RadFixedDocument.AcroForm.FormFields`.
+2. Check if the field type is [TextBox]({%slug radpdfprocessing-model-interactive-forms-form-fields-textboxfield%}) or [CombTextBox]({%slug radpdfprocessing-model-interactive-forms-form-fields-combtextboxfield%}).
+3. Set the widget font and text properties font to `FontsRepository.HelveticaBold`.
+
+### Code Implementation
+
+Use the following code snippet to update the font for all text fields in the PDF document:
+
+```csharp
+foreach (FormField field in document.AcroForm.FormFields)
+{
+    if (field.FieldType == FormFieldType.TextBox || field.FieldType == FormFieldType.CombTextBox)
+    {
+        TextField textBox = (TextField)field;
+        
+        // Set the font for the text field widgets
+        textBox.Widgets.First().TextProperties.Font = FontsRepository.HelveticaBold;
+        
+        // Set the font for the text field text properties
+        textBox.TextProperties.Font = FontsRepository.HelveticaBold;
+    }
+}
+```
+After applying the code, the apostrophe character will render correctly in the filled PDF.
+
+## See Also
+- [Fonts in RadPdfProcessing](https://docs.telerik.com/devtools/document-processing/libraries/radpdfprocessing/concepts/fonts)
+- [RadPdfProcessing Overview](https://docs.telerik.com/devtools/document-processing/libraries/radpdfprocessing/overview)
+- [Working with AcroForm Fields](https://docs.telerik.com/devtools/document-processing/libraries/radpdfprocessing/features/interactive-forms)
+
+---

knowledge-base/images/apostrophe-character-replaced-copyright-symbol-acroform.gif

@@ -0,0 +1,56 @@
+---
+title: Resolving License Validation Issues in Telerik Document Processing Libraries
+description: Troubleshooting the issue where the license is not recognized during runtime in Telerik Document Processing Libraries.
+type: troubleshooting
+page_title: License Not Recognized in Telerik Document Processing Libraries
+meta_title: License Not Recognized in Telerik Document Processing Libraries
+slug: license-not-recognized-telerik-document-processing-libraries
+tags: telerik, document, processing, license, validation, runtime, issues, licensing, diagnostics
+res_type: kb
+ticketid: 1690929
+---
+
+## Environment
+
+| Version | Product | Author | 
+| ---- | ---- | ---- | 
+| 2025.2.520| RadPdfProcessing |[Desislava Yordanova](https://www.telerik.com/blogs/author/desislava-yordanova)| 
+
+## Description
+
+This article aims to address potential licensing issues while generating Excel (or PDF, DOCX, etc.) files with Telerik Document Processing Libraries during **runtime** testing. The generated file contains a "License" sheet (or a watermark) with a trial message, despite the **Build Output** window indicating a valid license. The issue arises in a multi-project (e.g. Blazor WASM) application setup, where dependencies are shared across projects.
+
+## Cause
+
+This issue generally occurs due to incomplete license validation during runtime in complex setups, particularly when using shared libraries or plugin architectures. *Even if the license is validated during build time, runtime environments may fail to recognize it due to transitive dependency limitations.*
+
+## Solution
+
+The **Telerik.Licensing** verifies the DevSeat association at the time your classlib is built, and also provisions at runtime licenses in the Root app. When you have a setup such as **"Root app -> classlib -> Telerik UI"**, the Telerik UI will execute and verify the licensing for the classlib, but will not be applied transitively in the Root app. That's why you **need to add the Telerik.Licensing NuGet package reference to Root app manually**.
+
+To ensure proper license validation and eliminate trial messages, follow the steps below:
+
+* **Direct Package References**: Add references to the **Telerik.Licensing** package directly in the Root project. This resolves transitive dependency limitations.
+
+* **Explicit License Registration**: Add a call to `TelerikLicensing.Register()` early in your application lifecycle. For Blazor WASM applications, include this call in the `Program.cs` file. This approach validates the license explicitly.
+
+* **Verify Assemblies**: Ensure **no trial** versions of Telerik assemblies are referenced in any project. Replace [trial assemblies]({%slug upgrade-trial-to-licensed-version%}) with licensed ones, if such even exist.
+
+* **Enable Diagnostics**: Add the following property to your `.csproj` file to enable detailed licensing diagnostics during build and runtime:
+   ```xml
+   <PropertyGroup>
+       <TelerikLicensingVerbosity>diagnostic</TelerikLicensingVerbosity>
+   </PropertyGroup>
+   ```
+   Review the diagnostic output for clues about license validation issues.
+
+* **Avoid Environment Variables**: Use only the `telerik-license.txt` file for license delivery instead of environment variables, which can cause issues due to length limitations.
+
+By following these steps, runtime validation issues should resolve, and the trial message will no longer appear in generated documents.
+
+## See Also
+
+- [Telerik Document Processing Licensing Overview]({%slug introduction%})
+- [Setting Up Your Telerik Document Processing Libraries License Key]({%slug setting-up-license-key%})
+- [Using TelerikLicensing.Register Method]({%slug adding-license-key-ci-cd-services%}#using-teleriklicensingregister-method-on-aws-lambdas)
+- [Diagnostic Options for Telerik Licensing]({%slug telerik-trial-version-message-diagnostic-options%})

knowledge-base/license-not-recognized-telerik-document-processing-libraries.md

@@ -22,7 +22,7 @@ The __Clipping__ element exposes a single property.
 * __Clip__: Property of type __GeometryBase__ representing the [Geometry]({%slug radpdfprocessing-concepts-geometry%}) that is used to clip the content element.
 
 
-__Example 1__ demonstrates how you can create a Clipping element and assign a __RectangeGeometry__ to its Clip property.
+__Example 1__ demonstrates how you can create a Clipping element and assign a __RectangleGeometry__ to its Clip property.
 
 
 #### __[C#] Example 1: Create clipping__