This exception seems to be related to AES algorithm PaddingMode property.
The NotImplementedException is thrown while getting the color from unsupported color space (for example ICC). This exception occurs during the import of shading patterns with gradient stops using this color space or during the import of tiling pattern with underlying color space. Available in R2 2018 Official Release Version.
The Matrix property seems to be incorrectly interpreted during the import process.
For some documents, the clippings and colors of the geometries are modified on an import-export scenario.
The letters are disordered after the file is exported using PdfFormatProvider.
A NullReferenceException is thrown when trying to clone the Signature property of the field. Available in LIB Version 2018.1.312.
Although this is not a valid postscript scenario we should not throw exceptions and we should instead skip the invalid dictionary end characters. Fix available in LIB Version 2018.1.312.
These images are defined directly in the PDF page content stream with BI and EI operators. Currently InvalidCastException is thrown when document with such images is imported. Available in R1 2018 SP2 release version.
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.
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.
According to PDF specification, the resources used for the dynamic appearance of fields are defined globally in AcroForm "DR" PDF property. However, there are some invalid documents which define these resources locally in the field node which causes exception in PdfProcessing implementation. As there are several such documents we may consider handling such scenario instead of throwing the exception. Available in R3 2017 SP1 Official Release.
According to PDF specification, the field value should be specified in the "V" entry of the corresponding PDF dictionary. However, some PDF producers are skipping this entry and are setting only the Widgets appearance states. As most viewers manage to show the radio button and checkbox as selected, we should handle this scenario and import the field values based on the related widgets when this value is not explicitly set with the field's V entry.
InvalidOperationException is thrown when exporting font that is available but not used. The stack trace is as follows: at System.Linq.Enumerable.Max(IEnumerable`1 source) at Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.Fonts.Cid.CidSet.CopyPropertiesFrom(IPdfExportContext context, FontBase font) at Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.Fonts.CidFontDescriptor.CalculateCidSet(IPdfExportContext context, CidFontBase font) at Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.Fonts.CidFontDescriptor.<>c__DisplayClass34.<CopyPropertiesFrom>b__30() at Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Utilities.PdfObjectsExtensions.ToPrimitive[P,T](PdfProperty`1 pdfProperty, Func`2 convertToPrimitive, Func`1 getDefaultValue) at Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.Fonts.CidFontDescriptor.CopyPropertiesFrom(IPdfExportContext context, FontBase font) at Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.Fonts.CidFontObject.CopyPropertiesFromOverride(IPdfExportContext context, FontBase font) at Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.Fonts.CidFontObject.CopyPropertiesFrom(IPdfExportContext context, FontBase font) at Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.Fonts.Type0FontObject.CopyPropertiesFromOverride(IPdfExportContext context, FontBase font) at Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Export.PdfExporter.WriteFontsFromContext(PdfWriter writer, IPdfExportContext context) at Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Export.PdfExporter.Export(IRadFixedDocumentExportContext context, Stream output) at Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.PdfFormatProvider.ExportOverride(RadFixedDocument document, Stream output) at Telerik.Windows.Documents.Common.FormatProviders.FormatProviderBase`1.Export(T document, Stream output)
If a PDF with a TextBoxField is created with a corresponding Widget, the text is actually long enough to be broken in more than one line and AllowScroll is set to true, upon opening the file in Adobe, the text is not visible. The field actually does have an appearance which can be seen upon inspection of the document but for some reason it is not visualized. Another issue seems to be a different manifestation of the same problem: When the text is long and AllowScroll is false, the text will be visible, but will be misplaced. The issue is caused by the length of the text because the same field with a shorter text that can fit in the widget's rectangle will be displayed correctly.
The field name should be preserved on an import-export scenario. However, in some cases when the field name contains non-ASCII characters then the field name is exported with different value compared to the imported one. Fix available in LIB Version 2017.3.1009.
When trying to create documents simultaneously from different threads (in concurrent scenario), different exceptions are thrown: - NullReferenceException in Telerik.Windows.Documents.Core.Fonts.OpenType.OpenTypeFontSource.ReadTableData[T](UInt32 tag, ReadTableFormatDelegate`1 readTableDelegate) method, - OverflowException in Telerik.Windows.Documents.Core.Fonts.OpenType.Tables.CMapFormat4Table.Read(OpenTypeFontReader reader) method. Available in LIB version: 2017.2.814
System.Uri constructor throws UriFormatException when the text is some http address. Available in LIB Version 2017.2.814.
The current implementation expects the widths to be integer values and InvalidCastException is thrown when a real number is parsed. Workaround: If the scenario allows, the PdfStreamWriter may be used instead of PdfFormatProvider. More information may be found in the following documentation article: http://docs.telerik.com/devtools/document-processing/libraries/radpdfprocessing/formats-and-conversion/pdf/pdfstreamwriter/overview Available in LIB Version 2017.2.731.
This is because PdfProcessing does not export Annotation Flags and this way all annotations has Print flag set to false. Available in Release Version R2 2017 SP1.
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.