In our support ticket 1663439 you mention this maybe included in Q1 2025.  Is that still the case?  Having this still unplanned is concerning.

 

 

Hello Dimitar,

Thank you for your time.

I see some fixes, but still having the key after space problem and some crashes, besides sometimes the text appears in a different position than the caret position.
I appreciate your time trying to get a workaround but you are far behind what we have now.
Can we have an alpha version of the final solution to test?

Best regards,

Martin

Hi Dimitar,
Thank you for your effort, but it didn't work.
I did a quick test and this is what I've found:
- When typing first letter, it adds a space before it, that remains there
- When composing, if you press space, next character you press is ignored. Eg "nihongo<space>ha" will miss the h after the space and will show あ instead of は
- It crashes trying to delete using Backspace
- When pressing Enter with some text, it goes to the beginning of the document with an unexpected location for the new line inserted.
- Editing partial composition doesn't work as expected (1-caret position is not accurate, 2-the underline format doesn't change to a solid line, 3-typing a new character will insert the new character in any place and it will repeat completed text) 

Beside that, we are using Net8, not Net Fwk

I haven't continued testing and I won't.
Luckily, we have a much better workaround now, after struggling debugging Telerik code. By the way, the only way to fix the next character to the space, is executing the Textbox OnTextInput method, which implies to execute your Caret OnTextInput code, so we had to change private variable currentImeLanguage using reflection to get the logic path we need executed in the moment we need.

So, if this is all you can provide after all this time, it seems we will need to wait for the release for the final solution.
I hope you stop with the idea of the Caret inheriting from Textbox and start to handle Composition events in a different way. There is a bug related with it, which is that the IME popup moves continuously and that is because the popup position is related to the control giving the inputs position, which is the Caret in your case, and as the Caret is moving all the time, the IME popup is also moving.
Another bug we have is that the Caret is hidden some times, that hopefully will be solved when you had changed the Caret class.
And the more critical bug we still have is the partial composition, which we don't think we could find a fix for it without changing InsertIMETextCommand class or any of the other internal classes that we have not access.

Regards,
Martin 

Hi,
I think you should change this documentation https://docs.telerik.com/devtools/wpf/controls/radrichtextbox/ime-support?_gl=1*15m3pp4*_gcl_au*MTk3MDc2NjMxOC4xNzIyOTY2NzA1*_ga*MTUyNzgxNjk3Ny4xNzE1MTc0MjA4*_ga_9JSNBCSF54*MTcyNTQ1Njc3NC40Mi4xLjE3MjU0NzY4MzcuNDMuMC4w until you have this task done.

You are admitting with this task that the sentence "RadRichTextBox provides built-in support for the most commonly used Microsoft IMEs like Chinese IME, Japanese IME, Korean IME and etc" is false. I'm not a lawyer, but I think it could potentially lead to legal complications saying your product support something that it does not.
And, it's also false the part that says "you can easily add support for the IME which is used in your application". We both know that having this working just overriding 3 methods is not easy, if it is even possible. You are admitting in your comments that "this one will require significant resources and rewriting most of the IME support". Your team has access to internal classes you are using for this purpose and they can not fix it, and you expect developers to implement this just overriding 3 methods?
You could say instead something like "Create your own caret and override those 3 methods to try to fix the IME." and then finalize with "May the force be with you"

Regards,
Martin

Hi,

Can we please priorities this issue. We have a related ticket depends on this. View Ticket | Your Account (telerik.com)

Thanks,

Gowrisankar N