Problem 4
Here I want to mention problems face with text boxes.
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.
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.
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?
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
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.
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
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?
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.
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.
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)
We have tested the scenario in our environment and were able to replicate the issue. However, could you please provide the font file as well so that we can install it in our system and test again as it is necessary to install used fonts in the system where PDF file is being processed.
Furthermore, regarding PDFNET-46567, please provide MS Mincho font file that you have installed in your system so that we can further try to complete the opened investigation against this ticket.
I asked our customer if I can send you the font files. As the license is only for their company I would like to send the files per mail and not here. To which mail adress should I send the files? The customer asked me to emphasize that the files should only be used for the investigation (should be deleted after that) because the payed for them. Otherwise this will contradict the license.
Regarding PDFNET-46567, we don’t use the font MS Mincho. All information regarding this problem are in the comment from Jan 22 2020.
As per our understandings, these comments were in the response to PDFNET-46582 and PDFNET-46583 tickets. The issue related to MS Mincho font was PDFNET-46567 (initially reported by @jayjain). For the complete investigation of this issue, we need sample font file that is installed in user system.
Instead of sending the font file via email, you can please send it in a private message by clicking over username and pressing the Blue Message Button. We assure you that we use the files only for investigation purposes and erase them from our system once the investigation is done.