Hi Team,
When we generate a word into PDF format then page numbers are showing incorrectly. Please check and let us know.
000-E146728-A6011-DescriptionUL-2024-06-13-ea1a8832-05fa-4093-b395-0c91db61d813.pdf (134.5 KB)
Thanks,
Suryasree
000-E146728-A6011-DescriptionUL-2024-06-13-ea1a8832-05fa-4093-b395-0c91db61d813.pdf (134 KB)
000-E146728-A6011-DescriptionUL.zip (192.1 KB)
Added word document and converted PDF document in a zip folder. Plesae verify.
000-E146728-A6011-DescriptionUL.zip (192 KB)
@Suryasree Could you please share what version of Aspose.Words you are using? I checked your document with Aspose.Words for .NET 24.6 and the page numbers are rendered correctly.
Here is an output:
output.pdf (142.0 KB)
HI Team,
We are using 24.3 version of Aspose. Can you please let me know whether it will work in this version.
Thanks,
Suryasree
@Suryasree This also works fine with 24.3 version. Here is the output produced by 24.3 version on my side: out_24.3.pdf (142.0 KB)
As I can see some fonts are missed in your PDF document. The problem on your side might occur because the fonts used in your input document are not available on the machine where document is converted. The fonts are required to build document layout. If Aspose.Words cannot find the font used in the document, the font is substituted. This might lead into fonts mismatch and document layout differences due to the different fonts metrics. You can implement IWarningCallback to get notifications when font substitution is performed.
Please see our documentation to learn where Aspose.Words looks for fonts:
https://docs.aspose.com/words/net/specifying-truetype-fonts-location/
Hi Team,
Please let us know what fonts we are missing in our machines.
Thanks,
Suryasree
@Suryasree You are in the better position to determine this. Just implement IWarningCallback on your side and check the warnings generated by Aspose.Words upon conversion document to PDF.