This exception corrupts the whole document import. Instead, we should provide Exception handling mechanism which allows the user to import the rest of the content.

The letters are disordered after the file is exported using PdfFormatProvider.

This happens only in cases when the Radio flag is not set and there are multiple widgets with different "ON" state names.

Available in R1 2018 SP2 version.

The Matrix property seems to be incorrectly interpreted during the import process.

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

Fix available in R2 2018 SP1 release version.

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.

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

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.

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

The appearance dictionary specifies how the annotation is presented visually on the page. If the appearance missing or is empty in PDF document NullReferenceException is thrown on import. 

By specification the explicit destinations define a required page property. However, some documents contain definition for destinations with null page value, which causes an ArgumentNullException on import.

This request is to ask that the development team review the code inside the Documents for refactoring to see if certain things can be reduced (like Generics).

 

When using the Telerik UI for Xamarin and referencing the UI.for.Xamarin NuGet package, the assembly reference for the Telerik.Documents.Fixed.dll is added to the project. This increases the amount of code that is compiled when the Linker is only set to SDK only, thus breaking AOT compilation with LLVM enabled.

 

A few addition insights:

 

- When the project cannot set the Linker to SDK and User Assemblies

- When individually referencing DLLs for only what the project uses is an insufficient solution

- When installing sub-packages like Telerik.UI.for.Xamarin.DataGrid is an insufficient solution.

 

 

Thank you.

By specification the last line of the file contains only the end-of-file marker, %%EOF. When importing document with missing EOF, InvalidOperationException: 'Stack empty', is thrown.

By specification, the document AcroForm contains fields with no parents. However, some documents may have child fields in the AcroForm. This leads to ArgumentException when importing the child and parent fields - 'An item with the same key has already been added.' since the child field is added twice.

By the PDF format specification, CIDToGIDMap is optional. The default value is Identity. However when exporting CID Font with missing CIDToGIDMap property the analyzing tool causes the following warning message:

"PDF/A requires that a Type 2 CIDFont has a stream mapping from CIDs to glyph indices or the name Identity as its value."

I would like to request an example of the RadPdfProcessing library utilizing a Line Chart similar to how the Bar Chart is drawn in this example. 

Additionally, it would be great if there was an example with multiple charts on one page.

Thank you!

By specification when a form field is merged with the dictionary of the widget annotation, a Kids parameter can be existent if there are more than one widget annotations for that field. Support for importing such a fields should be added. 

When there is a destination object in a RadFixedDocument and it doesn't have page set (it is null), an exception is thrown. However, this is supported by Adobe and it is not forbidden in the Pdf specification.

If ImageInline's size is set through its Size property and not through Height or Width, the given size is not respected on export.

I was working on some acroforms and wherever I needed a space I kept on getting a different letter (Ê). On debugging the problem seems to be in the TryGetCharCode function of OpenTypeFontSource

Version: 2019.3.917

Below is copy of function

public override bool TryGetCharCode(int unicode, out int charCode)
        {
            bool result = false;
            ushort glyphId;
            charCode = CMap.MISSING_GLYPH_ID;
            if (this.TryGetGlyphId(unicode, out glyphId))
            {
                ushort uCharCode = CMap.MISSING_GLYPH_ID;
                CMapTable table = this.CMap.GetCMapTable(3, 0);
                if (table != null)
                {
                    result = table.TryGetCharId(glyphId, out uCharCode);
                }

                table = this.CMap.GetCMapTable(1, 0);
                if (table != null)
                {
                    result = table.TryGetCharId(glyphId, out uCharCode);
                }

                charCode = uCharCode;

                return result;
            }

            return false;
        }

The font used has 2 cmap tables: one with platformid of 3 and encodingid of 1, the other with platformid 1 and encodingid 0. According to https://docs.microsoft.com/en-us/typography/opentype/spec/cmap platform id 3 and encoding 1 is correct for windows so not sure why the first call to getcmaptable looks for encodingid 0.

Second of all even if I change it to the following

CMapTable table = this.CMap.GetCMapTable(3, 1);

if there is a second cmap with platformid of 1 whatever the result of the call with regards to platformid 3, the result will be overridden

I can say that if I add some checks so that if the first call succeeds it doesn't attempt the 2nd I do get the expected behaviour in the pdf and get spaces

 

As a note the FontFamily property of the OpenTypeFontSource is "Arial"