We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Pdf.Validate in 21.11.0 is different to 21.1.0

Hi,
We are planning to upgrade libraries and started testing 21.11.0. Currently we are running 21.1.0
We use the method Aspose.Pdf.Validate(System.IO.Stream, Aspose.Pdf.PdfFormat).
The issues are:

  1. New version for some tested files returns invalid XML with missing end tags. When using method Aspose.Pdf.Validate(string, Aspose.Pdf.PdfFormat), the output file contains valid XML.
  2. This is worse case, as the result in new libraty returns different results:
    Older version:
    Acroform is enabled
    Width information for glyphs is inconsistent in embedded font ‘GHKNMH+DejaVuSans’
    New version:
    Can not convert signed file

Although results of Validate methods are the same in both versions, the reasons are not. That is causing problems as we analyze the results in our business logic.
Is there anything you are planning to change? Is this on purpose? Are there some settings that we can set to get results as before?

Attaching test project with tested pdf sample file
Aspose.zip (84.8 KB)

@Kyso

We have managed to reproduce the same issue at our side. For the sake of correction, we have logged this problem in our issue tracking system as PDFNET-51065. You will be notified via this forum thread once this issue is resolved.

We apologize for your inconvenience.