When the URI source applied to the image cannot be parsed as a Path object to obtain its extension, an ArgumentException is thrown.

The exception is thrown while importing an image that has any value for height property applied through a style.

At this point the PdfFormatProvider does not support floating images and these elements are skipped when exporting to PDF.

The feature is trivial for floating images with "Behind Text"/"In Front of Text" settings, but otherwise floating images are affecting the text layout in complex ways.

Importing XLS document containing defined name with spaces in the sheet name causes exception

Based on how Excel works, VLookup doesn't need to be sorted, if the 4th parameter is FALSE.  The 4th Parameter determines whether an approximate search is used or an exact match is used.  by default true is used and an approximate search requires a sorted range.  However, if set to FALSE,  then the range doesn't need to be sorted.  the value is checked against the entire column of cells and can be unsorted. 

We process spreadsheets that use VLOOKUP with 4th parameter set to FALSE and unsorted data in range.  These work in Excel, but not in Telerik Spreadsheet processing.

thanks, 

The exception is thrown when the endObj keyword is present without preceding obj to define the start and the reference of the current object. 

The auto row height is not working when the row is merged. This is only valid if the merged cell range contains a single row.

By specification, the last line of the file contains only the end-of-file marker, %%EOF. If the file contains many trailing bytes at its end, a NotSupportedException: 'StartXRef keyword cannot be found.', is thrown.

Workaround: Trim any content after the end-of-file marker (see FixInvalidEndOfFile). 

Add support for shapes, and especially for shapes with textual content. 
In OOXML, shapes are represented by the wps:wsp element, and shapes with textual content by <wps:txbx>, <w:txbxContent>.
Such shape can be added to a Word document using the Insert -> Text -> Text Box -> Draw Text Box, or through a shape's context menu -> Add Text.

Do not confuse these shapes with Text/Rich Text content controls (see https://feedback.telerik.com/Project/184/Feedback/Details/190057 )

Add support for documents containing RTL (right-to-left) text.

Implement importing and exporting the javascript actions associated with push button fields so that they can be executed when the exported document is opened with Adobe Acrobat. Javascript actions are also used by text fields for text validation (for instance for date input).

When importing a document with a style set in a parent <div> element its children`s (heading (<h1>-<h6>) and <div>) content doesn't inherit it.

Steps to reproduce:

1. Import the following HTML string:

   <div style="background-color: green;">
   	<h1>Test heading</h1>
   	<div>Test div</div>
   </div>

2. Export it as PDF (or any other supported format)

Actual vs Expected:
 

Even without flattening the form the Barcode font gets lost.

Noticed that manually setting the font using the font name with spaces seems to work.

Other custom fonts on our form appear to work, however the Free 3 of 9 does not.

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.

Currently, NotSupportedEncryptionException is thrown.

This would allow to encrypt documents only with Owner Password and not showing password dialog when disabling some PDF features permissions. The customer should be able to disable printing, text and graphic selection and extraction, page rotations and others. The full specification of all permission bits may be seen in Table 3.20 on page 124 in PdfReference 1.7. On page 120 in PdfReference 1.7 are described the User and Owner passwords.

Image size is not respected when importing HTML

Add support for the PAdES-BES signature standard

When merging documents containing the same embedded font every time a document is merged the same font is repeatedly embedded in the merged document. This leads to very large files.

A possible workaround before this feature is developed could be to use the PdfProcessing model to import and merge the documents. After the documents are merged to iterate the document`s content in order to cache the fonts using their name and if there are duplicated names to set the already cached one (check the attached project). 

As a side note, the suggested workaround doesn't cover all possible cases (e.g. if there are fonts with a common name but different font sets (modified fonts or font subsets) this may lead to missing/different characters in the produced document). So in order to use this workaround, you will need to ensure the font names are unique for every different font.

For example when some PDF file has uncompressed contents we may import it and apply better compression to the stream objects. Ensure that all the content inside the document is compressed.