hi,
I have a template file in pdf and when i use aspose.pdf to convert it into word so it convert sucessfully. the output file is
https://drive.google.com/file/d/0B27sK4AZpwaxcUV6MTRfUjdwMEU/view?usp=sharing
when i open it in word 2016 so it is as expected.
https://drive.google.com/file/d/0B27sK4AZpwaxcmQ2bVYwYWVEbkk/view?usp=sharing
but if i open in word 2013 so it is
https://drive.google.com/file/d/0B27sK4AZpwaxSHZFOFh2c3ZhVzQ/view?usp=sharing
but this is not expected result. i m using aspose.pdf version 17.8.0.0 and i have also tried with 17.9.0.0
sample template file in pdf is
https://drive.google.com/file/d/0B27sK4AZpwaxMnZaRDlXSnRPdmc/view?usp=sharing
my code is
Document pdfDocument = new Document(templateFilePath);
pdfDocument.Save(fileName + ".docx", Aspose.Pdf.SaveFormat.DocX);
@gurpreet.singh,
We have converted your source PDF to Word document and could not replicate the problem of misplaced text as visible in your snapshot inWord2013.png. These are the output Word documents created with and without applying license: OutputWordFiles.zip (17.1 KB).
Kindly open these Word files and let us know how that goes into your environment. If you are able to find the same problem as visible in the snapshot inWord2013.png, then please share details of the environment, including operating system name and edition, Microsoft Word application edition and version number, local language settings and some other handy information which could help us to replicate this problem in our environment.
@imran.rafique
yes i am still facing this issue the template you have sent me is opening in word 2013 exactly like inWord2013.png. Now sure what is the problem. aspose.word creates the document as expected. i am using windows 7 service pack 1, microsoft visual studio professional 2017 version 4.7.02053 and microsoft office 365 ProPlus version 15.0.4963.1002. The OutputWordFiles.zip files you sent me is also opened like inWord2013.png in my machine.
@gurpreet.singh,
Thank you for the confirmation. We are investigating your query as per the shared environment details. We will get back to you soon.
@gurpreet.singh,
We are still unable to replicate this error in our environment. It appears as an environmental specific problem, please open the output Word document on any other computer and see how that goes.