Setting the ComplianceLevel to PdfA3B and the TaggingStrategy to UseExisting when exporting a PDF document leads to the following Error reported by VeraPdf:

Specification: ISO 19005-3:2012, Clause: 6.2.11.5, Test number: 1
For every font embedded in a conforming file and used for rendering, the glyph width information in the font dictionary and in the embedded font program shall be consistent.
Glyph width 274.4140625 in the embedded font program is not consistent with the Widths entry of the font dictionary (value 272)

Introduce support for TimeStampServer when using the PdfStreamSigner.

Stacktrace: 

This exception was originally thrown at this call stack:
    System.ThrowHelper.ThrowArgumentOutOfRange_IndexMustBeLessException()
    System.Collections.Generic.List<T>.this[int].get(int)
    Telerik.Windows.Documents.Core.PostScript.Data.PostScriptArray.GetElementAs<T>(int)
    Telerik.Windows.Documents.Core.Fonts.Type1.Type1Format.Dictionaries.Type1PostScriptObject.GetGlyphName(ushort)
    Telerik.Windows.Documents.Core.Fonts.Type1.Type1Format.Type1FontSource.GetGlyphName(ushort)
    Telerik.Windows.Documents.Core.Fonts.Type1.Type1Format.Type1FontSource.GetAdvancedWidthOverride(int)
    Telerik.Windows.Documents.Core.Fonts.FontSource.GetAdvancedWidth(int)
    Telerik.Windows.Documents.Fixed.Model.Fonts.StandardFont.GetActualWidth(Telerik.Windows.Documents.Fixed.Model.Data.CharCode)
    Telerik.Windows.Documents.Fixed.Model.Fonts.SimpleFont.GetWidthOverride(Telerik.Windows.Documents.Fixed.Model.Data.CharCode)
    Telerik.Windows.Documents.Fixed.Model.Fonts.FontBase.GetWidth(Telerik.Windows.Documents.Fixed.Model.Data.CharCode)

With the current implementation, the compression setting is omitted:

• streamWriter.Settings.StreamCompression

The issue is that the document contains incorrect data that the CrossReferenceStream.LoadReferences method cannot parse.

From R1 2017 all annotations (including sound and video) are supported for import-export scenarios by using PdfStreamWriter class. 

These feedback item will be opened as we may add API for generating and inserting new sound annotations from scratch in the file.

When a source RadFixedDocument is merged to a target RadFixedDocument, the content of the source document is cleared.

WinAnsiEncoding it is imported as StandardEncoding since WinAnsiEncoding is still not implemented in RadPdfProcessing. 

 This is content stream operator that is used to close, fill and then stroke a PDF path geometry.

Available in R3 2018 SP1 release.

When images are added to the document with non-default quality (PdfExportSettings.ImageQuality different that ImageQuality.High) , they are re-encoded, which uses a lot of memory and may cause OutOfMemoryException for large images.
Workaround (works when inserting big JPEG images): In this case ImageQuality.High may be used and RadPdfProcessing will decode only the image headers to insert the image into the PDF file. As image pixels are not decoded with ImageQuality.High, there will be no OutOfMemoryException.

This would allow creating documents with preferences such us HideToolbar, HideMenubar, FitWindow, PrintScaling and all other viewer preferences specified in PDF format specification.

OutOfMemoryException is thrown when generating PDF with many pages each of which contains images, as all of the document model data is in-memory.

The issue is fixed with the new PdfStreamWriter API. As an example, you may see the attached demo to the following feedback item:
https://feedback.telerik.com/Project/184/Feedback/Details/213503-pdfprocessing-optimize-pdfstreamwriter-cache-in-order-to-reduce-memory-when-writ

Available in LIB version: 2017.1.320

This is happening when the pages in the document has content arrays similar to the following:

[34 0 R 243 0 R] [34 0 R 245 0 R] [34 0 R 247 0 R] ....

As you may notice the content stream 34 0 R is reused and the issue is caused by incorrect caching of content stream indirect objects by their reference.

The current implementation of IDisposable implements a simple Dispose method which releases the inner stream resource. However, if the PdfStreamWriter instance is not disposed explicitly by calling Dispose() or by surrounding it in "using" clause, then the inner Stream resource is not Disposed as well. The same applies for PdfFileSource class.

We should implement the IDisposable pattern in a way that the GC disposes the inner stream if needed when collecting the PdfStreamWriter/PdfFileSource class instances.

Currently, only images without transparency may be created with this class.

Available in LIB version 2017.1.410.

This is causing issues when exporting the document to PDF from WordsProcessing - the pdf library tries to create the font, but cannot find it due to a different casing. When importing HTML document, the font-family property is read with small letters. Later, when converting the string containing the value, it is changed to title case. 

This issue will be reproducible with each font containing a name with a letter with casing different than the one of the other letters (exc. first capital letter), for example: Microsoft JhengHei

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.