According to PDF specification widget's parent field should always be terminal field and should have FieldType specified. However, there are documents which are generated without fulfulling this rule and we need to consider handling this scenario without any exceptions.

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;
        }
    }
}

When using an ImageSharp version bigger than 2.0 an exception is thrown: "MissingMethodException: 'Method not found: 'SixLabors.ImageSharp.Image SixLabors.ImageSharp.Image.Load(Byte[], SixLabors.ImageSharp.Formats.IImageFormat ByRef)'."

Workaround: Downgrade to a lower ImageSharp version or use a custom implementation of ImagePropertiesResolverBase/JpegImageConverter.

With the current implementation, the Standard Fonts preloaded in the FontsRepository cannot be replaced.

Currently, Standard fonts are exported always with StandardEncoding. This does not allow export of some special characters which do not fit in the first 255 glyph definitions in the font. Most of these characters are the ones with an accent such as "Eacute" glyph (É) which is with position number 303 in Times Roman font. The list of all standard fonts may be found in this documentation section:
https://docs.telerik.com/devtools/document-processing/libraries/radpdfprocessing/concepts/fonts#standard-fonts

When opened in Adobe Reader it says that the file "claims compliance". However, when verifying the compliance with some validation tools there seem to be some issues mainly related but not limited to fonts. 

Hi there,

I've been researching how to use Telerik PDFProcessing to Digitally Sign a PDF. But can't find any documentation on how to incorporate it into ASP.Net AJAX (VB).

When the indirect object contains more spaces between the object number and the generation number the object content is not successfully parsed.

Expected: one space

Actual: more than one space

Setting a filter on a mask results in an invalid file when exporting. 

Workaround: Set the filer like this:

PdfFormatProvider provider = new PdfFormatProvider();
provider.ExportSettings.ImageCompression = new ImageFilterTypes[] { ImageFilterTypes.FlateDecode };