Any update on this issue now?
Ankur
Any update on this issue now?
Ankur
We regret to share with you that these issues have been postponed due to advanced typography feature. We will inform you via this forum thread once these issues are resolved.
We apologize for your inconvenience.
Unfortunately, there is no update available on these issues at the moment. We apologize for your inconvenience.
The issues you have found earlier (filed as WORDSNET-17888) have been fixed in this Aspose.Words for .NET 21.1 update and this Aspose.Words for Java 21.1 update.
The issues you have found earlier (filed as WORDSNET-17887) have been fixed in this Aspose.Words for .NET 21.1 update and this Aspose.Words for Java 21.1 update.
Hi @tahir.manzoor,
I can see Arial font again in the output instead of calibri fonts. This issue is not resolved yet.
@sumeetm
Please refer to the following article. You need to enable open type feature as shown below to get the desired output.
Enable OpenType Features
Document doc = new Document("test.docx");
doc.LayoutOptions.TextShaperFactory = HarfBuzzTextShaperFactory.Instance;
doc.Save("out.pdf");
Hi @tahir.manzoor,
I still see some issues on the produced output:
These issues are similar to ones mentioned here: ECDCTS-6615: Arabic font is incorrect in PDF rendition - #27
@sumeetm
We have tested the scenario and noticed that the Arabic text is shifted up in output PDF. Please check the attached image. issue detail.png (47.5 KB) We have logged this issue as WORDSNET-21743. You will be notified via this forum thread once this issue is resolved. We apologize for your inconvenience.
We have not found this issue at our end. Please check the attached PDF. 21.1.pdf (67.9 KB)
Hi @tahir.manzoor,
With the latest Aspose.Words and Aspose.Words.Shaping.Harfbuzz.jar I found that the issue is resolved. Actually I was using Very Old Aspose.Words.Shaping.Harfbuzz.jar, hence those issues were encountered.
Thanks,
avinash.
Thanks for your feedback. Please feel free to ask if you have any question about Aspose.Words, we will be happy to help you.
The issues you have found earlier (filed as WORDSNET-21743) have been fixed in this Aspose.Words for .NET 21.3 update and this Aspose.Words for Java 21.3 update.