I am working developing report builder tool so we want to use third party tool to export our html page to pdf,word,ppt and excel so we use trial version of aspose .net component and it meets most of our requirements but our tool must support Arabic language so we found some css styles does not work as the following example:
@charset "UTF-8";
.arabicAlpha > li:nth-child(8n+1)::before {
content: "أ .";
margin-left: 0;
}
.arabicAlpha > li:nth-child(8n+2)::before {
content: "ب .";
margin-left: 0;
}
.arabicAlpha > li:nth-child(8n+3)::before {
content: "ج .";
margin-left: 0;
}
.arabicAlpha > li:nth-child(8n+4)::before {
content: "د .";
margin-left: 0;
}
.arabicAlpha > li:nth-child(8n+5)::before {
content: "ه .";
margin-left: 0;
}
.arabicAlpha > li:nth-child(8n+6)::before {
content: "و .";
margin-left: 0;
}
.arabicAlpha > li:nth-child(8n+7)::before {
content: "ز .";
margin-left: 0;
}
.arabicAlpha > li:nth-child(8n+8)::before {
content: "ح .";
margin-left: 0;
}
ol.noStyle { list-style-type: none; }
ol.lowerAlpha { list-style-type: lower-alpha; }
اختبار
اختبار
اختبار
اختبار
we expect that when we export it to pdf it display:
Thanks for your inquriy. We have tested the HTML to PDF conversion using Aspose.Pdf for .NET and noticed it is not rendering text correctly, so we have logged a ticket PDFNEWNET-40088 in our issue tracking system for further investigation and resolution. We will keep you updated about the issue resolution.
Furthermore we are testing your other requirements and will update you our findings soon.
As we just have notice this problem, so unless the product team has analyzed these problems in details and have figured out the actual reasons behind them, we might not be able to share the possible timelines by which it will be resolved. However the team will start analyzing it and as soon as we have some definite updates regarding its resolution, we will let yo know.
PS, meanwhile I have also intimated the product team to see if they can consider accommodating this problem in their schedule.
As we recently have been able to notice this issue, so its still pending for review. However as soon as we have some definite updates regarding its resolution, we will let you know.