With the current implementation, the Standard Fonts preloaded in the FontsRepository cannot be replaced.

Currently, Standard fonts are exported always with StandardEncoding. This does not allow export of some special characters which do not fit in the first 255 glyph definitions in the font. Most of these characters are the ones with an accent such as "Eacute" glyph (É) which is with position number 303 in Times Roman font. The list of all standard fonts may be found in this documentation section:
https://docs.telerik.com/devtools/document-processing/libraries/radpdfprocessing/concepts/fonts#standard-fonts

When opened in Adobe Reader it says that the file "claims compliance". However, when verifying the compliance with some validation tools there seem to be some issues mainly related but not limited to fonts. 

Hi there,

I've been researching how to use Telerik PDFProcessing to Digitally Sign a PDF. But can't find any documentation on how to incorporate it into ASP.Net AJAX (VB).

When the indirect object contains more spaces between the object number and the generation number the object content is not successfully parsed.

Expected: one space

Actual: more than one space

Setting a filter on a mask results in an invalid file when exporting. 

Workaround: Set the filer like this:

PdfFormatProvider provider = new PdfFormatProvider();
provider.ExportSettings.ImageCompression = new ImageFilterTypes[] { ImageFilterTypes.FlateDecode };

When a document containing a SignatureField is exported with the IsEncrypted property set to true, a not set UserPassword is required to open it, which makes it impossible to be opened.

Workaround: Exporting with AES256 encryption does not have this problem:

provider.ExportSettings = new PdfExportSettings
{
	IsEncrypted = true,
	EncryptionType = EncryptionType.AES256
};