The issues you have found earlier (filed as CELLSNET-55009) have been fixed in this update. This message was posted using Bugs notification tool by johnson.shi
Sure, I also was curious that we had used one of the Aspose version, same in 2 different app versions. Yet we faced issue only in 1 whereas in another we dint face any issue at all despite having exactly same piece of code,
Maybe you are using two different Aspose versions in those applications. Please try Aspose.Cells for .NET 24.2. If you face any issue with Aspose.Cells for .NET 24.2, let us know with details and simulation code (with resource files), we will check it soon.
Sure, will let know. Thank you for your support.
The Aspose version had been same. Though none of the above issues were faced in the particular app version.
I may not be able to provide sample code for font size at the moment as having some priority tasks and may also handle the issue differently at the moment.
We had considered plain text in the particular version and thus not reproducible. Please ignore that.
Alright and good to know that you can cope with it by using plain text.
Alright, it’s good to know that you can handle it using plain text.
By the way, out of curiosity, we would love to address any issues in the APIs. So, once you find some time, kindly write sample code and provide it to us with all the details to reproduce the issue on our end. We will check and try to figure it out soon.
As I tested new DLL var issue was resolved. But rgba and font size still remains.
Can you please test below examples once again.
<font color=“rgba(0, 0, 0, 0)”>
span style=“font-size:0px;”>Test</span
Thanks.
Could you please share your sample (runnable) code and sample files (please zip the file(s) prior attaching) to reproduce the issue on our end, we will check your issue soon.
I am working on sample code and will provide you soon. Meanwhile can you confirm if upgrading Aspose.Cells only and no other DLL shall be enough. If you have any sample code, you can provide it too. It shall be helpful. Thanks.
Yes, we recommend using the latest version as we have included many enhancements regarding HTML parsing and rendering. If you still encounter any issues, please provide the necessary information and resource files as requested. We will address your issue soon.
While upgrading pdf I encountered these 2 errors.
Value of type ‘PageSettings’ cannot be converted to ‘PageSettings’.
Value of type ‘PrinterSettings’ cannot be converted to ‘PrinterSettings’.
Kindly please address it soon.
Do you think there are classes added since 23.6.0 which have similar names in System.Drawing.
PdfViewer.PrintDocumentWithSettings seems to be accepting PageSettings and PrintSettings only from Aspose.PDF.Printing and not System.Drawing.Priting any more. Had there been any such change. Can you please confirm.
I am afraid, I can help regarding Aspose.Cells here. I guess your queries/issues are related to Aspose.PDF API. Please post your queries/issues in dedicated forum where one of our fellow colleagues from Aspose.PDF team will assist you soon.
Thanks @amjad.sahi. I have asked it in PDF forum here. Meanwhile as I am going to update ti tomorrow, just wanted to confirm with you, if we upgrade only Aspose.Cells and not Aspose.Words and Aspose.PDF, do you think that should be fine?
I am not sure that just upgrading Aspose.Cells would resolve your issue, as I am not entirely certain about the nature of your problem. If you encounter any issues with Aspose.Cells, we would need your sample project with resource files to reproduce the issue on our end.
Yes upgrading Aspose.Cells resolves the issue. Just that if we dont upgrade Aspose.PDF it should not cause any problem and they both must be independent. While upgrading Aspose.PDF there is another issue.
@Bhumika.Shah
Thank you for your feedback. I’m glad that the cells issue you encountered has been resolved. If you have any questions, please feel free to contact us.
Yes, majority was resolved. Thank you. Though font size 0 or 1 remains. I am trying for sample code but facing some issue. When I will be able to, will surely send you sample code for it. Thanks.