Thanks for your inquiry. I tested the scenario and have managed to reproduce the same problem. For the sake of correction, I have logged this problem in our issue tracking system as WORDSNET-11360. 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.
Hi,
Is there any update on this issue. By when we can expect a fix for this… We need to deploy it immediately, as we had purchased product license as well
Thanks.
Thanks for your inquiry. Unfortunately, your issue is not resolved yet. We have asked the ETA of this issue from our development team and will update you as soon as any estimates are available. We apologize for your inconvenience.
Thanks for your inquiry. Unfortunately, your issue is not resolved yet. Our development team has completed the analysis of this issue and the root cause has been identified. However, the implementation of the fix of this issue has been postponed till a later date. We will inform you via this thread as soon as this issue is resolved. We apologize for your inconvenience.
Thanks for your inquiry. The problem occurs because when justify low/medium/high option is selected for Arabic text, a special kind of justification called kashida is performed. In contrast to white-space justification, kashida justification is accomplished by elongating characters at certain chosen points. The characters are elongated by appending a number of glyphs resembling “ـ”.
The kashida justification can’t be supported now because Aspose.Words has limited support for fonts. Specifically, the glyphs of the Arial font used for elongating have glyph ID (1127) but have no code point.
The glyph for the elongation is specified in JSTF table (at least in Arial and Times New Roman).
Support for such glyphs will be added once OpenType advanced typography is resolved as per WORDSNET-6633.
Secondly, since you reported this issue via Aspose.Words’ normal Forum, WORDSNET-11360 was logged with ‘Normal Priority’ in our issue tracking system and when an issue is reported via normal (free) support forum we make no promises about estimations on when a fix can/will be delivered.
PS: If this issue is important to you, and for the fast resolution of this issue, please have a look at enhanced support options - e.g. purchasing Priority Support will allow you to post your issues in our Priority Support forum and raise the priority of this issue directly with our development teams, if possible, we will then aim to get a resolution to your issue as soon as we can. Many Priority Support customers find that this leads to their issue being fixed in the next release of the software.
@savinda90 As I already mentioned in your original post, Kashida feature is not yet supported by Aspose.Words layout engine. Once this feature is implemented we will notify you in your original thread.
Cookie Notice
To provide you with the best experience, we use cookies for personalization, analytics, and ads. By using our site, you agree to our cookie policy.
Enables storage, such as cookies, related to analytics.
Sets consent for sending user data to Google for online advertising purposes.
Sets consent for personalized advertising.
Cookie Notice
To provide you with the best experience, we use cookies for personalization, analytics, and ads. By using our site, you agree to our cookie policy.
More info
Enables storage, such as cookies, related to analytics.
Enables storage, such as cookies, related to advertising.
Sets consent for sending user data to Google for online advertising purposes.
Sets consent for personalized advertising.
Cookie Notice
To provide you with the best experience, we use cookies for personalization, analytics, and ads. By using our site, you agree to our cookie policy.
More info
Enables storage, such as cookies, related to analytics.
Enables storage, such as cookies, related to advertising.
Sets consent for sending user data to Google for online advertising purposes.