Reading Type1 font glyph data when there is a table with differences tries to get the glyph by name but it is not found. 

Exported protected document containing SignatureField can not be opened even if the correct password is used. The same behavior is reproduced with empty document (without pages).

Embedding a TrueType font collection using the FontsRepository.RegisterFont method leads to glyphs with empty outlines collection. The missing outlines are caused due to an empty glyf and loca tables of the TrueType font file.

When merging documents using the RadFixedDocument`s Merge() method the fonts are not successfully merged which leads to missing characters in the produced document.

Workaround: replace the font with a full font (not a subset) before exporting to a PDF file:

byte[] data = File.ReadAllBytes("verdana.ttf");
FontFamily verdanaRegularFontFamily = new FontFamily("Verdana");
FontsRepository.RegisterFont(verdanaRegularFontFamily, FontStyles.Normal, FontWeights.Normal, data);
FontsRepository.TryCreateFont(verdanaRegularFontFamily, out FontBase verdanaRegularFont);

foreach (RadFixedPage page in mergedDocument.Pages)
{
	foreach (TextFragment textFragment in page.Content.Where(c => c is TextFragment).Cast<TextFragment>())
	{
		textFragment.Font = verdanaRegularFont;
	}
}

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)

Exception when merging file that contains notdef characters with PdfStreamWriter

Add support for XRechnung compliance.

Add support for Encryption Algorithm 7.

Here is a sample structure of the signature: 

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

NullReferenceException is thrown when exporting pages containing images with missing optional ColorSpace.

When signing more than one signature field, the previous signatures are invalidated.

NullReferenceException is thrown then exporting a document with a Type 3 font with missing/invalid Unicode mapping.

PdfStreamWriter stream-copy page splitting performance is much slower than expected in some cases. When working with larger PDF files, the processing time can increase a lot and cause noticeable delays.

XMP metadata is unescaped during import/export.

When inserting a specific Jpeg image with an ICC profile there is a problem when opening the file in Adobe: 



On the other hand, the PDF is successfully opened by browsers and most PDF viewers.

Duplicated page content due to an incorrect caching mechanism.

This will allow the import of Tensor-product patch mesh gradients. Currently, importing documents that contain ShadingType 7 results in NotSupportedShadingTypeException.

When the document contains hidden PDF layers they are imported as visible which leads to additional content in the exported document.

This type of shading is not supported in the current version and a NotSupportedException is thrown when importing documents containing it.

The exception can be suppressed using the Exception Handling mechanism of PdfProcessing.