Free Support Forum - aspose.com

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

#1

FONT COMPROMISED

Hello Team,
I am trying to convert MS WORD to PPT using Aspose. The way that I am going through is
WORD -> PDF -> PPT.
For this purpose, I am using the code given by you and the latest Aspose Dlls.

Let me take an example of 1 font MS Mincho. The font in the word document is MS Mincho and the font is PDF is also MS Mincho. But the font in PPT is (ABCDE+MS-Mincho), This ABCDE is a random 5 letter word and it is not exactly MS Mincho.

If you try to any text or number inside the PPT, then you’ll see weird lines coming on the PPT. However, if you manually change the font from (ABCDE+MS-Mincho) to MS Mincho, then you’ll see the numbers or letters entered.

This problem makes editing the document extremely laborious. I request you to please fix this issue soon. It’s not just observed for MS Mincho but also for other fonts like Arial Bold etc.

DOCUMENTS ATTACHED IN THE NEXT QUERY JUST BELOW THIS ONE.

#2

I am attaching some documents and some images for your reference.

see the font in word
image(1).jpg (313.3 KB)

see how the font comes in PDF. It is correct and acceptable.
image(2).jpg (421.3 KB)

See how font appears in PPT
image(3).png (384.9 KB)

See what happens when we enter any text / numbers in the PPT.
image(4).png (385.3 KB)

See what happens when we convert it to MS Mincho. {just FYI we do have MS Mincho installed in our machines and you’ll also notice the same issue in Arial(as explained below). Well, Arial is installed in almost every computing device of the universe :slight_smile:
image(5).png (359.6 KB)

We expect, that all fonts must be conserved. Verdana, Calibri, and others are conserved but not MS Mincho, and many more. You can discover the rest.

See how the font is shown in PDF.
image(6).png (294.2 KB)

See how does it show in PPT & see what happens when you enter something.
image(7).png (267.0 KB)

See how it changes when the font is cahnged manually.
image(8).png (302.1 KB)

Documents Attached:

Test Documents.zip (2.6 MB)

#3

@jayjain

Thank you for contacting support.

We have worked with the data shared by you and have been able to reproduce the issue in our environment. A ticket with ID PDFNET-46567 has been logged in our issue management system for further investigation and resolution. The ticket ID has been linked with this thread so that you will receive notification as soon as the ticket is resolved.

We are sorry for the inconvenience.

#4

That’s ok team, no product is perfect. I am glad that you noticed it and are also working on it to resolve the issue. Thanks & please let me know when the fix comes. :grinning:

#5

Hello team, I am using the following code for ppt text box optimization:-

string fnameppt = wordReportName + ".pptx";

using (MemoryStream pdfStream = new MemoryStream(inStream.ToArray()))

{

Aspose.Pdf.Document pdfDoc = new Aspose.Pdf.Document(pdfStream);

using (MemoryStream pptStream = new MemoryStream())

{

//pdfDoc.Save(pptStream, Aspose.Pdf.SaveFormat.Pptx);

pdfDoc.Save(pptStream, new PptxSaveOptions() { OptimizeTextBoxes = true });

//the yellow highlighted code is given by Aspose Dev team to us for resolving multiple text box issue

File.WriteAllBytes(fnameppt, pptStream.ToArray());

}

}

But the PPT generated has many issues.

There are a few more problems that we have discovered, I’ll be listing them 1 by 1 below. You might need to open a couple of new tickets.

#6

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.

#7

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.

#8

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.

#9

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.

#10

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.

#11

@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.

#12

Which is the current status of PDFNET-46567 ticket?

#13

@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.

#14

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

#15

@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.

#16

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.

#17

@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.

#18

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

#19

@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.

#20

Is there no current update?