Add built-in localization for the UI control and its tooltips. Currently they can be localized by expanding the XAML of RadPdfViewerToolBar and adding the required resources to the code.
Add UI for adding comments and ability to save them. Comments are represented in the document model as text annotations (annotations with Subtype Text).
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.
At the moment the AnnotationsHandler, SelectionHandler and PanHandler cannot be removed or disabled. It would be convenient for this to be possible.
This is Unicode (UTF-16BE) encoding for the Adobe-GB1 character collection; contains mappings for all characters in the GB18030-2000 character set. Described on page 443 in Pdf Reference 1.7.
Layers represent groups of optional content which can be hidden or shown.
A similar scenario is not defined in the PDF specification but the widgets can be rendered as read-only fields despite the fields associated with them are missing.
At this point, the Print() method allowing the customers to silently print a document uses the PrintableAreaWidth and PrintableAreaHeight properties of the print dialog, which are read-only and cannot be changed through the API. Consider changing them with PrintTicket.PageMediaSize. We should also consider the scenario when the client needs to print a smaller PDF page on a bigger page size. For instance, A5 page to be printed on an A4 sheet without scaling the content.
RadPdfViewer can not find startxref keyword at the end of a document if the document contains many zero bytes at its end. NotSupportedException is thrown with "Startxref keyword cannot be found" message. Workaround: Trim the ending zero bytes before loading the document to the PdfViewer. This is currently noted in the WinForms KB article: http://www.telerik.com/support/kb/winforms/details/notsupportedexception-startxref-keyword-cannot-be-found-when-loading-pdf-file-in-radpdfviewer-for-winforms
Currently the minimal zoom out value is 0.8% which impacts the performance while scrolling large documents.
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 would allow switching the focus between form field controls by using the Tab key.
Expose a button in the UI that can be used instead of Ctrl+F. Such a button can be currently added by customizing the default toolbar. For more information, check the documentation that describes how to achieve that: https://docs.telerik.com/devtools/wpf/controls/radpdfviewer/default-ui#customizing-the-default-ui
Currently, RadPdfViewer uses default constant value for the font size in this scenario.
At the moment the theme of the RadPdfViewerToolBar can be set only by setting the theme of the entire application. The individual setting (using telerik:StyleManager.Theme="Windows8") should also be supported.
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.
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.
In Adobe and Foxit readers, the user can draw different shapes, which are later saved as images in the document.
When users do "copy" operation, add the content to the clipboard in RTF format. This would allow to paste the text along with its formatting in text editors like MS Word.