We should implement the logic for getting character codes from Unicode when using CFFFontSource.

Workaround: The font may be changed by creating a similar font with FontsRepository.TryCreateFont(...) method.
Telerik.Windows.Documents.Fixed.Model.Fonts.FontsRepository.RegisterFont(new Telerik.Documents.Core.Fonts.FontFamily("Arial"), Telerik.Documents.Core.Fonts.FontStyles.Normal, Telerik.Documents.Core.Fonts.FontWeights.Normal, fontData); // fontData is a byte[] keeping the font definition

FontBase font;
bool hasCreatedFont = FontsRepository.TryCreateFont(new FontFamily("Arial"), out font);
 
foreach (TextField field in document.AcroForm.FormFields.OfType<TextField>())
{
    if (hasCreatedFont)
    {
        foreach (var widget in field.Widgets)
        {
            widget.TextProperties.Font = font;
        }
 
        field.TextProperties.Font = font;
    }
}

For instance, we may implement WritePageAsync method in addition to the existing WritePage method. This is a similar scenario as in System.IO.StreamWriter class which has WriteLine and WriteLineAsync methods.

The exception is reproduced only with specific custom fonts and is thrown by the ComputeSubset() method of the GlyphTypeface class with the following message: "file does not conform to the expected file format specification". However, we can handle the exception and export the font data using the base class.

Fix available in LIB Version 2018.2.828.

The exception is thrown by System.Linq.Enumerable.Max method during the CidSet calculations.

Fix available in LIB Version 2018.2.730.

ArgumentException is thrown while importing a choice field whose value is an empty string. Instead, the empty string should be imported.
 

Usually, the entries are on neighboring rows. However, some producers introduce some extra blank rows between entries and this causes exception in RadPdfProcessing implementation.

Fix available in LIB Version 2018.2.625.

Currently, a default constant value is used for the font size in this scenario.

Importing document containing content with DeviceN color space causes System.InvalidCastException when the color components contain integer values

Fix available in R2 2018 SP1 release version.

The only applied graphics properties are the fill color, the stroke color and the rendering mode (which specifies whether the glyph is filled or/and stroked). Instead, Block and FixedContentEditor classes should apply all other graphics state properties (StrokeThickness, MiterLimit, StrokeDashOffset, StrokeDashArray, StrokeLineJoin, StrokeLineCap).

WORKAROUND: These properties may be applied after the text content is added. For instance, if you require changing the StrokeThickness of the text fragments which are stroked and not filled then you may use code similar to the one below:

foreach (RadFixedPage pages in document.Pages)
{
    foreach (TextFragment textContent in pages.Content.Where(c => c is TextFragment))
    {
        if (textContent.RenderingMode == RenderingMode.Stroke)
        {
            textContent.StrokeThickness = 0.3;
        }
    }
}

This operator modifies the current clipping path by intersecting it with the current path, using the even-odd rule to determine which regions lie inside the clipping path.

Available in R3 2018 SP1 release.

Although Lab color space is currently unsupported, the provider should not throw exceptions that break the whole file import.

The  FunctionType property is required according to PDF specification and we should always export it.

Fix available in R2 2018 SP1 release version.

This allows specifying a soft mask in the external graphics state.

Currently, there is internal API which is used by RadWordsProcessing PDF export functionality. We should consider making appropriate public API which would expose tab stops editing functionality.

Provide a way to change the Name of a FormField from the RadDocument.AcroForm.FormFields collection.

As a workaround, you could create a new instance of a FormField with the desired name, add the new field in the document and remove the old one. You can use the following approach:
   1) Create a new instance of FormField (with the desired name, passed in the constructor), which will play the role of a copy of a specific FormField
   2) Copy all properties from the original field (they all vary, depending on the concrete type of the FormField, for example CheckBoxField, etc.)
   3) Create a new widget for the new field, and copy all properties from the original field's widget into the new one.
   4) Remove the original field from the RadDocument.AcroForm.FormFields collection and add the new field.
   5) Remove the original widget from the corresponding page's annotation and add the new one.

Attached is a project demonstrating this approach for a CheckBoxField.

Currently, NotSupportedException is thrown when trying to import a document that uses Type 3 fonts.
Update: With Release R1 2021 the import of Type 3 fonts is already developed but the export is still not supported.

The hierarchical document structure is a means to describe the PDF document structure, which is currently not supported. See 10.6.1 Structure Hierarchy on 856 page of the PDF specification for details.
This document structure is an alternative to the standard PDF structure and most non-Adobe software does not support it.

The document might have been created with Adobe software like Adobe LiveCycle Designer. Very often the document contains some fallback text in the standard PDF structure like:
"Please wait... If this message is not eventually replaced by the proper contents of the document, your PDF viewer may not be able to display this type of document."
"The document you are trying to load requires Adobe Reader 8 or higher. You may not have the Adobe Reader installed or your viewing environment may not be properly configured to use Adobe Reader. For information on how to install Adobe Reader and configure your viewing environment please see  http://www.adobe.com/go/pdf_forms_configure."
"For the best experience, open this PDF portfolio in Acrobat X, Reader X, or later."

RadPdfProcessing currently supports interactive forms whose data is defined directly in the document. Add support for interactive forms based on the Adobe XML Forms Architecture (XFA). The entry is defined inside the interactive forms dictionary and refers to an XML stream containing the information of the form. More information is available on page 722 from Pdf Reference, version 1.7.
Updates:
November 2024
From PDF 2.0 (ISO 32000-2) the XFA forms are depreciated. For this reason, we are changing our plans and declining this item, but we will provide import-export support to avoid losing existing XFA content. Please, subscribe to the following public item: PdfProcessing: Add support for XFA fields import-export.

In this case, we should use a default alpha source value which is the opacity source.

Currently, when registering *.otf font file with FontsRepository.RegisterFont method an exception is thrown during the font creation. 

WORKAROUND:  The font file may be converted to TTF format (*.ttf) which is successfully registered. This conversion may be achieved with FontForge by opening the font file and then choosing File -> Generate Fonts -> TrueType -> Generate. More information on FontForge program may be found here: https://fontforge.github.io/en-US/