Template PDF documents created for example with Foxit PDF Editor, or with documents created programmatically with Aspose.

If the documents are opened with other PDF viewers such as Foxit or Adobe, there are no problems, which is not the case with the Telerik viewer.

I am currently using Telerik UI for WinForms 2024 Q4 24.4.1113.0

For example, if you choose to print second page like this: 

It prints only the first page of the document, instead of the second page.

Currently, RadPdfViewer offers the DataError event which is purposed to handle errors during the import process. However, if there are problematic pages that are rendered in the viewer at a later moment after the document is already imported, the viewer doesn't offer a suitable way for handling such problematic moments even though the PdfProcessing library throws one of its exceptions. 

The exact client's case is loading a PDF document which contains images requiring JPX Decoder which is currently not supported. Even though the PdfProcessing library throws internally the following error, the RadPdfViewer control doesn't throw the DataError event with the respective error:

Telerik.Windows.Documents.Fixed.Exceptions.NotSupportedFilterException: 'JPXDecode is not supported.'

The following assemblies are missing in the 2024_4_1127_Dev_Preview zip folder:
- Telerik.Windows.Documents.Flow.FormatProviders.Doc
- Telerik.Windows.Documents.Flow.FormatProviders.Pdf
- Telerik.Documents.SpreadsheetStreaming.dll

Open the Demo app and load the PDF document with such annotation. The following error occurs:

The problem I'm trying to solve is that users do not know that the original document may not be what they are seeing in the viewer when there are layers.    

A property that indicates that a document has layers would allow the system to refuse to open the document.

The attached file lorem-ipsum.pdf is rendered incorrectly in PdfViewer. I suspect it has something to do with kerning, because monospace font is not affected. Adobe Acrobat, Foxit PDF Reader, and Chrome render the file correctly.

The file was created with Pandoc, open source software, converting a markdown file (.md) to .pdf.

When RadPdfViewer is in text selection mode and the user is trying to select a word by double-clicking on it, the last letter of the word is not selected when the word is followed by some symbols like '.', ':', '(', '...'

Also, the CaretPosition is not correct.

Steps to reproduce:

1. Load a PDF document with 0 pages

2. Enter some text in the search textbox and click the next/prev buttons

Expected: the search textbox should be either disabled or should ignore any search operation

Actual: an error occurs

Workaround:

    Private Sub pdf_Viewer_DocumentLoaded(sender As Object, e As EventArgs)
        If pdf_Viewer.Document.Pages.Count = 0 Then
            pdf_Toolbar.SearchTextBox.Enabled = False
            pdf_Toolbar.NextButton.Enabled = False
            pdf_Toolbar.PreviousButton.Enabled = False
        Else
            pdf_Toolbar.SearchTextBox.Enabled = True
            pdf_Toolbar.NextButton.Enabled = True
            pdf_Toolbar.PreviousButton.Enabled = True
        End If
    End Sub

Use the attached pdf document and launch the PdfPrintPreviewDialog. As it is demonstrated in the gif file, the preview dialog moves the pages slower than the pdf viewer itself.

Expected behavior: the performance for navigating the pages should be at least identical.

This is the result with R3 2022:

This is the result with R2 2023 SP1: