Convert PDF to PPT in C# using Aspose.PDF for .NET - Problems in output files

PROBLEM 1

The Bullets are not working properly [highlighted in yellow]. When the user hits “enter” after any bullet point – a new bullet point is not added. Instead, we see the start of another paragraph. This is the same case for all the bullets in the entire PPT and it becomes extremely troublesome for our clients to edit the final output.

image(1).png (160.5 KB)
Problem_1_attachments.zip (258.6 KB)
image(2).png (143.6 KB)

Expectation

We expect that all the bullet points work as intended. If a user hits “enter” after any bullet point then he should see a new bullet point perfectly aligned below the previous bullet point.

PROBLEM 2

When we try to hit “enter” in the highlighted area [right column] then a new line disturbs the entire column.

image.png (161.1 KB)
image.png (162.3 KB)
image.png (87.0 KB)
image.png (111.3 KB)
Problem2Attachments.zip (256.5 KB)

Expectation

If a user wants to enter a line in Right column then he should be able to do it with ease. He should not be taken to left column instead or he should not be taken to many lines down instead.

Problem 3

When we try to enter new text in the table. The entire structure of the table gets disturbed. This is the same case for all the tables in the entire PPT.

image.png (151.5 KB)
image.png (125.5 KB)
image.png (199.1 KB)
Problem3.zip (260.4 KB)

Expectation

We expect that tables in the resultant “output PPT” work exactly as they work in any other PPT. We should be able to edit data in the tables without any hassle.

Problem 4

Here I want to mention problems face with text boxes.

  1. The text box size is too large and overlaps with other text boxes. This ultimately leads to overlapping of texts while editing.
  2. This one is extremely tiresome, please try inserting a new text box in the PPT provided and you’ll see what I am talking about.

image.png (31.2 KB)
Problem4.zip (255.9 KB)

Expectation

We expect that the resultant PPT behaves like a normal PPT.

We do appreciate your effort, “ Aspose Support Team”. The 4 issues mentioned above are serious to us and to our clients. As you could also examine that there are structural as well as functional issues in the output presentation file. Structural issues would mean that the output PPT does not look according to the input PDF. Functional issues would mean that the output PPT does not behave like any other presentation file. We’re sure that you could understand how much tiresome it becomes for the end users to accept such an output, hence we request you to please fix these issues. The Output PPT should look alike the input PDF and users should be able to update it with ease.

> We have tried our best to avoid the duplicate documentation of the same issue. Please feel free to identify any new issues other than the mentioned and try to resolve them too. Once the problems are fixed please notify us about the new release.

> We hope you would give a solution to us on a priority basis as we have production line waiting due to these issues. Please feel free to reach out to us for any more information.

@jayjain

Thank you for sharing all the details.

Please always create separate topics for separate issues, this helps us and you as well to track and report things efficiently. We have been able to notice mentioned issues and have logged below tickets in our issue management system for further investigations and resolution.

  • Problem 1: PDFNET-46581
  • Problem 2: PDFNET-46582
  • Problem 3: PDFNET-46583
  • Problem 4: PDFNET-46584

Moreover, please note that the issues have been logged under free support model and will be resolved under first come first serve policy which can take some months.

However, we also offer paid support model where issues are resolved on urgent basis and have priority over the issues logged under free support model. You may check our Paid Support options for your reference.

Which is the current status of PDFNET-46567 ticket?

@stefan.net.test

We are afraid PDFNET-46567 is still pending for investigations owing to previously logged and critical tickets. We have recorded your concerns and will let you know once any update will be available in this regard.

Our Customers need at least to know when you will start to fix this ticket.

Will it be within a 2 weeks? 3 months? Where is it on you schedule?

Best regards,
Stefan

@stefan.net.test

We apologize for the inconvenience faced.

We have recorded your concerns and will definitely take care of them during issue investigation. We have escalated the issue priority to next level and will surely let you know as soon as we have some news on their resolution ETA. Please spare us some time.

Please tell us on Feb, 1st what the current schedule on the issue is.

Our customer is currently thinking about leaving the contract and moving to a different solution.

Therefor we would need to dismiss Aspose as well.

@stefan.net.test

We would like to share with you that all of your issues are being investigated. However, regarding PDFNET-46582 and PDFNET-46583, would you kindly explain what behavior do you expect? It is not a real table. It is just a text box. The API CANNOT recognize logical structure of a slide. And such feature is not planned to be implemented in the nearest future. The primary goal was to preserve the appearance, not to prepare easily editable documents.

Dear Ali,

we convert DOCX=>PDF=>PPTX

What actually happens:
grafik.png (48.8 KB)

is a change to a more bold font “DGIUUI+Arial-BoldMT” coming from “Arial” bold.

We would expect the pptx font to keep the word font Arial bold during the conversion:
grafik.png (38.3 KB)

I attached the 3 files which we generate during the conversion: DOCX=>PDF=>PPTX in the zip file.

docxpdfpptx.zip (297.7 KB)

When do you think you can fix this?

Cheers,
Stefan

@stefan.net.test

Thanks for providing the details.

We have logged these details along with earlier logged issues and will share our feedback with you soon. Please spare us little time.

Is there no current update?

@stefan.net.test

We would like to share with you that the issue (logged as PDFNET-46584) has been resolved and its fix will be available in Aspose.PDF for .NET 20.2 version which will be releasing in coming week. We will surely notify you as soon as the fix-in version is published.

Regarding the remaining ticket, we regret to share that they are not yet resolved as they need more time to get investigated and resolved. We will inform you as soon as we have some additional updates regarding their fix. Please spare us some time.

We are sorry for the inconvenience.

1 Like

The issues you have found earlier (filed as PDFNET-46584) have been fixed in Aspose.PDF for .NET 20.2.

We experience a similar problem again. A customer uses the font Equip. The font is installed on our server but when converting (Word -> PDF -> PPTX) the text is not displayed.
Is this font not supported by you?
Using this font is quite important for the customer.

@stefan.net.test

There are certain fonts that require a license in order to use them. However, we need to check about this particular font that you referred. Would you kindly share your sample source PDF file with us. We will test the scenario in our environment and address it accordingly.

The font is correctly used in the word file, but not in PDF or PPT.
It seems that the font can be used in different spellings.
I attached two zip files. Files_v1 is the one where the spelling is used and nothing is displayed in PPT. Files_v2 is a different spelling where the text is displayed but the font is still wrong.
Files_v1.zip (26.4 KB)
Files_v2.zip (63.2 KB)