Introduce support for PolyLine Annotation

FixedDocumentSinglePagePresenter uses simple rendering mechanism using UIElements, which currently has some limitations:
- Layers are not supported, thus annotations and forms are not rendered (even read-only)
- UIElements could be affected (clipped) when UseLayoutRounding property set at parent level, when DPI is different that 96 DPI. 

Workaround: If content is clipped, ensure that UseLayoutRounding is set to false as presenter level:
<telerikUI:FixedDocumentSinglePagePresenter UseLayoutRounding="False" />

When a page is rotated its annotations are not positioned correctly. 

Currently, the Find() method searches from the beginning of the document to its end. Enable the customer to specify a particular range of pages the method should search through.

Before starting to decode big image, try to estimate the needed memory and check if such memory is available using the MemoryFailPoint class. The behavior in case of failure in printing scenarios should be considered carefully.
The user should be able to turn the behavior on and off.

The Ò symbol is not found in the encoding as is rendered as a ".notdef" glyph.

Available in LIB Version 2017.3.1127.

Enable the customers to directly save the document inside PdfViewer to a file or a stream.

Available in LIB Version 2017.3.1225.

Images decoded with CCITTFaxDecode filter affect the performance when showing the document.

The exception is thrown when the RadioButtonField options array contains nested arrays instead of string values.

Fix available in LIB Version 2018.1.312.

The file contains the following:
68.637 604.561 455.981 -107.996 re
72.237 604.561 l
S
Instead of the more usual
68.637 604.561 455.981 -107.996 re
S
72.237 604.561 l
S
Both are valid but the first seems to create a problem.

Fix available in LIB Version 2018.1.319.

RadPdfViewer's AcroForm property ViewersShouldRecalculateWidgetAppearances should be respected when being set to true. In this case, RadPdfViewer should recalculate all widget appearances and this would resolve the issue with empty form field widgets after opening such PDF document.

Currently, we use System.Windows.Controls.TextBox for editing both TextBox and CombTextBox field types. We should implement CombTextBox editor which would allow having spaces between characters during the editing process.

This is reproducible when the matched result resides on different page.

Workaround: You may subscribe to the RadFixedDocument.CaretPosition.PositionChanged event and implement the scroll logic. Subscribe to PdfViewer's DocumentChanged event first if the document is not loaded.
        private void CaretPosition_PositionChanged(object sender, EventArgs e)
        {
            Telerik.Windows.Documents.Fixed.Model.RadFixedPage currentPage = this.pdfViewer.Document.CaretPosition.Page;
            int pageIndex = this.pdfViewer.Document.Pages.IndexOf(currentPage);
            this.pdfViewer.GoToPage(pageIndex + 1);
        }

Usually, the entries are on neighboring rows. However, some producers introduce some extra blank rows between entries and this causes exception in RadPdfViewer implementation.

Fix available in R2 2018 SP1 release version.

When importing document containing a destination which points to invalid page reference, KeyNotFoundException is thrown.

When importing documents containing Interactive FormFields with an empty collection of Normal state appearances, a NullReferenceException is thrown, which leads to non-editable FormFields in PdfViewer.

Fix available in LIB Version 2018.2.730.

Instead, we should not visualize them and they should not be interactable with the mouse.

Fix available in LIB Version 2018.2.730.

At the moment the AnnotationsHandler, SelectionHandler and PanHandler cannot be removed or disabled. It would be convenient for this to be possible.

The rendering of images with size ~5000/6000 and BitsPerComponent=1 is time-consuming. The scenario is optimized in terms of memory but would be nice to increase the performance as well.

When a ToUnicode CMap is defined for Simple Font (TrueType or Type1 font) which maps font character codes to two or more Unicode character values, the extracted text should contain the whole set of characters defined in the mappings. The current implementation of RadPdfViewer takes the first character specified in the ToUnicode mapping which leads to missing characters.