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

Free Support Forum - aspose.com

Wrong page numbers

Hi,

We are converting Word docs to PDF using Aspose.Words for .Net version 18.9.0 and the following code:

        var doc = new Document(input);
        doc.UpdateFields();
        doc.UpdatePageLayout();
        doc.AcceptAllRevisions();

        var saveFormat = new PdfSaveOptions
        {
            OptimizeOutput = true,
            ImageCompression = PdfImageCompression.Jpeg,
            PreserveFormFields = true,
            UpdateFields = true,
            SaveFormat = SaveFormat.Pdf
        };
        
        doc.Save(output, saveFormat);

Both input and output are of type Stream.

Please take a look at the page numbers in the header of the Word document input file input.zip (125.8 KB)

The page numbers in the generated PDF are wrong. See output.pdf (217.4 KB)

Is this an issue that you are aware of?

Thank you!

@gwert,

We tested the scenario and managed to reproduce the same problem on our end. For the sake of correction, we have logged this problem in our issue tracking system. The ID of this issue is WORDSNET-17999. We will further look into the details of this problem and will keep you updated on the status of correction. We apologize for your inconvenience.

Hi,

Thank you for looking into this.

Since this is a critical issue for this, is there any kind of workaround (a different approach to conversion or some changes we can do to the input file) so that we can get pass this issue for the moment?

Thank you!

@gwert,

We have logged your concerns in our issue tracking system and will keep you posted on any further updates.

A post was split to a new topic: Wrong page numbers returned by Aspose.Words

@gwert,

We have good news for you i.e. WORDSNET-17999 has now been resolved and the fix of this issue will be included in the 19.2 (next version) of Aspose.Words. We will inform you via this thread as soon as the next version containing the fix of your issue will be released at the start of next month.

The issues you have found earlier (filed as WORDSNET-16496) have been fixed in this update