After an initial testing, I am able to reproduce the issue you mentioned by simply converting your template XLSX file to PPTX via Aspose.Cells. I found issue(s) with some borders and formatting in Excel spreadsheet to PPTX rendering.
string excelFilePath = "g:\\test2\\GridToSlideTest.xlsx";
Workbook asposeWorkbook;
LoadOptions options = new LoadOptions();
asposeWorkbook = new Workbook(excelFilePath, options);
asposeWorkbook.Save("g:\\test2\\out1.pptx", SaveFormat.Pptx);
We require thorough evaluation of your issue. We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): CELLSNET-54742
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
FYI, regarding the row height, I did some playing with it an found that the minimum height is determined by the row’s font size. The row height can be made smaller by choosing a smaller font. That’s a good workaround to be aware of.
We found that all the fonts in the cells of the row must be changed so that the row height can become small. However, if we change the font of the cells to adjust the row height, the font settings will be lost. Is it fine for you?
Yes. I think if the row contains visible text at all then the row size should be set as it currently is being done by Aspose Cells. If the worksheet has a row with a height that is set too short for the font then that’s an issue that should be adjusted in the worksheet.
In other words, I would only change the font size in Aspose Cells to reduce the row height in the case where the row has no visible content.
If you want to auto fit row height if row contains data, please auto fit row height now.
But this feature will also reduce row height if it’s too large. We will check whether we only auto fit row height for the rows which can not show all data.
The issues you have found earlier (filed as CELLSNET-54742) have been fixed in this update. This message was posted using Bugs notification tool by johnson.shi
You’re welcome. Please take your time to try the new version. Hopefully, with the suggested code segments and other instructions, the new version will work for your needs.