Rendering problem of Thai characters in PDF

Aspose.Words Product Family
5

Hi @awais.hafeez,
Thank you for your kind support.

Your software product makes me impressed and I would like to use it in my project.
However, I don’t have much time but I believe that you will solve this problem.

I hope to hear a good news from you soon.
Keep me informed of any updates. :slightly_smiling_face:

6

@brunetta,

Sure, we will keep you posted on any further updates and let you know via this thread as soon as the linked issue is resolved.

7

2 posts were split to a new topic: Thai characters rendering in PDF - Aspose.Words

8

Hi @awais.hafeez ,
2 months ago, Would like to know if you have any update on our topic?
I look forward to hearing from you.

Thank you & Best regards.

9

@brunetta,

Unfortunately, your issue is not resolved yet. We have completed the initial analysis of this issue but I am afraid, because of complexity, the implementation of this issue has been postponed. There is no ETA available at the moment. We will inform you via this thread as soon as this issue will be resolved in future. We apologize for your inconvenience.

10

Thanks for letting me know and I will wait to hear from you.

11

@brunetta,

Regarding WORDSNET-18424, there are following three problems:

  • Incorrect positioning of Thai glyphs
  • Incorrect line wrapping for Thai
  • Thai distributed paragraph alignment.

The first issue can be solved by installing the Aspose.Words.Shaping.HarfBuzz package and then enabling it as explained in this article: Enable OpenType Features in C#|Aspose.Words for .NET.

We are working on the other two issues and will keep you posted on further updates.

12

Hi @awais.hafeez and Team,

Great! Thank you so much for working hard.
Your solution is very important to our project.
We believe that ASPOSE team can fix all.

I’m looking forward to your reply with good news for issues 2-3.

Have a nice day :slight_smile:

13

@brunetta,

Sure, we will inform you via this thread as soon as the linked issue is resolved.

14

Hello @awais.hafeez,

Hope you are doing well. :slight_smile:

Do you have any progress on 2 pending items?

Thank you and Best regards.

15

@brunetta,

Unfortunately, your issue is not resolved yet and there is no further news about this issue i.e. the implementation of the fix of this issue (WORDSNET-18424) has still been postponed. We will keep you posted on any further updates and let you know when this issue will be resolved in future. We apologize for your inconvenience.

16

@awais.hafeez
Thank you for letting me know.
I’ll wait to hear from you.

17

A post was split to a new topic: Scanner SDK for Web Applications

18

Hi @awais.hafeez,

Could you give me a status on your progress?

19

@brunetta,

Your issue WORDSNET-18424 depends on the resolution of internal complex issues WORDSNET-15081 (rough ETA of this issue is first quarter of 2020) and WORDSNET-17085. Therefore, WORDSNET-18424 is postponed until at least these two issue are resolved. Unfortunately, there is no ETA available at the moment. We will inform you via this thread as soon as the linked issue is resolved. We apologize for your inconvenience.

20

Thank you for your information and prompt response.
We believe in your talent.
We look forward to hearing from you.

21

Hello @awais.hafeez and team,

Hope all is well with you.

Could you give us a status on your progress?
We are waiting to hear from you.

Stay safe!

Thank you and best regards.

22

@brunetta,

I am afraid, your issue is not resolved yet and there is no further news about this issue i.e. the implementation of the fix of this issue (WORDSNET-18424) has still been postponed. We will inform you via this thread as soon as this issue will be resolved in future. We apologize for your inconvenience.

23

We are facing the same issue, is this fixed yet?

24

@dileepawijay Unfortunately, there are no news regarding the issue yet. It is still postponed and is not yet scheduled for development. Please accept our apologies for your inconvenience.