InvalidCastException is thrown when importing a document that contains structure elements (StructElem) with StructureType (/S) defined with an incorrect integer type (PdfInt) instead of the expected PdfName type.

When signing a PDF document with an image using the PdfStreamSigner, the signature is broken. This is the used approach for signing the document: https://www.telerik.com/document-processing-libraries/documentation/libraries/radpdfprocessing/features/digital-signature/pdfstreamsigner

However, instead of using the DrawText method, the DrawImage method is used.

 

NotImplementedException is thrown for GetCapHeight method of CFFFontSource.

System.NotImplementedException: The method or operation is not implemented.
   at Telerik.Windows.Documents.Core.Fonts.Type1.CFFFormat.CFFFontSource.GetCapHeight()
   at Telerik.Windows.Documents.Core.Fonts.FontSource.get_CapHeight()
   at Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.Fonts.FontDescriptor.CopyRequiredButType3FontPropertiesFrom(FontBase font)
   at Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.Fonts.FontDescriptor.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.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.ExceptionHandling.ExecutionHandler.TryHandleExecution[E](Action operation)
   at Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.PdfFormatProvider.ExportOverride(RadFixedDocument document, Stream output, CancellationToken cancellationToken)
   at Telerik.Windows.Documents.Common.FormatProviders.FormatProviderBase`1.Export(T document, Stream output, Nullable`1 timeout)

Error 141 TYPECHECK on Lexmark printer when printing DPL-generated PDF file.

Embedding files in a specific order within a PDF can cause an issue when accessing the embedded files in Adobe Acrobat.

When inspecting the main PDF in Adobe Acrobat and attempting to open a specific embedded file, the following dialog is displayed:

Workaround

Embedding the files in a different order may prevent the issue from occurring and can serve as a temporary workaround.

When a row has two cells and the content of the first one is large, the width of the second cell results in too small value while measuring and its content remains invisible.

Workaround: Set PreferredWidth to the second cell.

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. 

If the MatrixPosition has Matrix (1, 0, 0, 1, 20, 10) the Table should be positioned with top-left coordinate (20, 10). Instead, it is wrongly positioned at (40, 20).