System.ArgumentException when setting a password to a document with form fields

The current implementation relies on valid cross-reference offsets in the PDF documents so that PDF objects are easily found and parsed. However, we may implement a mechanism for importing documents with invalid offsets for the objects inside the stream.

Handle the case where the catalog starts with value other than 0

Currently Type0Font class has CMap that can only be Identity-H.

According to the specification, the startfref keyword must be followed by the offset the xref table start on, defined on a new line. Some documents, however, have both entries defined on the same line, which leads to InvalidOperationException with message "Stack empty" while importing. Make sure this case is handled in PdfProcessing as well.

This API should provide a method for removing all fields and widgets in the document and draw the default widget appearance in place of the removed widgets.

WORKAROUND: Sample implementation for flattening form fields may be seen in the FlattenFormFields method from the attached demo project.

According to PDF specification, all fonts should be embedded except from 14 Standard PDF fonts. This guarantees that the PDF file is self-contained and will be rendered successfully on different devices and operation systems.

However, some clients prefer not to embed fonts in order to reduce file size. That is why we may provide such API.

An implementation of JPXDecoder should be created to allow the decompression of data encoded using the wavelet-based JPEG2000 standard.

Guidelines of how to provide a custom implementation of the JPXDecode filter can be found in the Customize Rendering section of the documentation and a sample implementation can be found in the SDK examples.

A remote go-to action is similar to an ordinary go-to action but jumps to a destination in another PDF file instead of the current file.

Currently, when registering *.otf font file with FontsRepository.RegisterFont method an exception is thrown during the font creation. 

WORKAROUND:  The font file may be converted to TTF format (*.ttf) which is successfully registered. This conversion may be achieved with FontForge by opening the font file and then choosing File -> Generate Fonts -> TrueType -> Generate. More information on FontForge program may be found here: https://fontforge.github.io/en-US/

More information is available in the Pdf Reference 1.7. Page 442 lists all predefined CMaps that should be imported and exported as PdfName objects. At this point, trying to import a document with such encoding, a NotSupportedException is thrown with message Encoding type is not supported.

In Adobe Acrobat, if you bring up the "Document Properties" dialog window and then click on the "Advanced" tab, there is a property under the "Print Dialog Presets" section called "Page Scaling". We should preserve the value on import/export and be able to set it in the code behind.

Currently, importing a document with non-embedded TrueType font will result in a font instance with an empty font source. Support should be added for providing custom font data of TrueType fonts during document import.

Add a PDF document validator to validate (before the import of the document) an existing PDF document.

They are exported with the /EmbeddedFiles switch. This would allow adding external files to the PDF document.

More information is available in the Pdf Reference 1.7. Page 442 lists all predefined CMaps that should be imported and exported as PdfName objects. At this point, trying to import a document with such encoding, a NotSupportedException is thrown with message Encoding type is not supported.

Currently adding an Image content element with ImageSource instantiated with a PNG file format leads to NotSupportedException: 'Can not export other than Jpeg and Jpeg2000 and ImageQuality different than High', when exporting the document.

Support for adding PNG images and exporting to PDF should be implemented for PdfProcessing for .NET Standard scenario.

Currently adding an Image content element with ImageSource instantiated with a GIF file format leads to NotSupportedException: 'Can not export other than Jpeg and Jpeg2000 and ImageQuality different than High', when exporting the document.

Currently adding an Image content element with ImageQuality different from High leads to NotSupportedException: 'Can not export other than Jpeg and Jpeg2000 and ImageQuality different than High', when exporting the document.

At this point, the justify alignment is not supported.