Korean Input Issue: Incomplete Character Display in pqGrid

[lhscj2466]

Hello,

I am a web developer from South Korea, and I have been using pqGrid for my projects. I find the flexibility of pqGrid to be very impressive. However, I am facing a critical issue with the input of Korean characters. The problem is that the first character of a Korean word is not displayed in its completed form when typing. This issue is causing significant problems for our service.

To give you an example of the problem:
'안' is displayed as 'ㅇㅏㄴ'

I have raised this issue before, but it seems that there was no solution available at that time. I am curious to know when this issue might be resolved. If there is a workaround or temporary solution for this problem, please let me know.

Thank you.

Please note that this message was written using a translation tool, as I am not proficient in English.

[paramvir]

The issue workaround is updated in this post: https://paramquery.com/forum/index.php?topic=4560.0

Please let me know whether it works for you.

[lhscj2466]

Hello,

The solution provided above is not a fundamental fix for the issue. Even if it is considered a temporary workaround, the problem with the initial input should be at least partially resolved. Based on my experience with projects in Korea (although not all projects), there is a high likelihood that pqgrid will be excluded from consideration due to the current issue. This means that the issue is quite significant. I sincerely hope for a resolution, and if you are willing to address the problem, I am curious to know when we can expect a solution.

- This message has been written using a translation tool, so please understand if there are any oddities in the context.

[paramvir]

ETA for the fix is May 2023

[lhscj2466]

Thank you for your response.
I appreciate the quick reply even more.
I look forward to the update in May and hope that the desired feature will be included in the update.

Thank you.

[lhscj2466]

Hello,
I'm currently in the process of checking the latest 9.0 update.
It was mentioned before that the issue with Korean input would be resolved in this update.
However, it appears that the problem has not been fixed upon inspection.
Can you provide any insights into the possible reasons for this?

[paramvir]

Apologies, but currently, there is no available solution for the issue at hand. Upon careful examination, it has been determined that incorporating support for the pressToEdit feature in Unicode languages would necessitate substantial modifications to the key navigation and editing code base.

In the meantime, you have the option to deactivate the pressToEdit feature by adjusting the value of editModel.pressToEdit to false. This will allow you to continue utilizing the system until support for this feature becomes accessible.

[paramvir]

Dear lhscj2466

This is supported / resolved in v9.0.1