Thanks for your inquiry. We tested the scenario and have managed to reproduce the same problem on our end. For the sake of correction, we have logged this problem in our issue tracking system. The ID of this issue is WORDSNET-17053. We will further look into the details of this problem and will keep you updated on the status of correction. We apologize for your inconvenience.
Thanks for your inquiry. Please ZIP and upload your new 1) input Word document, 2) Aspose.Words generated PDF file showing the undesired behavior and 3) Font files here for testing. We will investigate the issue on our end and provide you more information.
Thanks for the additional information. We tested the scenario and have managed to reproduce the same problem on our end. For the sake of correction, we have logged this problem in our issue tracking system. The ID of this issue is WORDSNET-17061. We will further look into the details of this problem and will keep you updated on the status of correction. We apologize for your inconvenience.
this is very critical for us. Our client requires this to be sorted.
We bought Aspose product after having purchased another PDF convertor which gave us too many issue in conversion especially around Arabic Characters. Now we are facing issues with Aspose.
Please treat this with some urgency. When can we expect an out come on this please? We need an update COB today latest - otherwise we will have to seek an alternate product
We are currently doing analysis of this issue to determine the root cause. It seems that some glyphs for “Arabic Presentation Forms-B” Unicode codepoints are missing in the “Cairo” font you attached but MS Word uses glyphs for chars from “Arabic” range. Aspose.Words on the other hand performs font fallback for these characters. Maybe advanced typography support in Aspose.Words will help in this case. We are investigating the issue further on our end and will inform you via this thread as soon as this issue is resolved or any estimates are available. We apologize for your inconvenience.
I am afraid, we have to postpone the implementation of this issue due to complexity.
Rendering Arabic with the Cairo font requires support of advanced typography features such as shaping. Aspose.Words currently does not support these features yet. The ETA for the advanced typography features support is Q4 2018 - Q1 2019.
The only workaround is to switch from Cairo to some font that has glyphs for the characters in Arabic Presentation Form-A and Arabic Presentation Form-B Unicode ranges. Arial is an example of such font.