UIElements Any text input CJK not works

4721276--446630--CJK support.gif

I have look at official example, but there’s some have problem.
CJK input not allowed in UIElements! (but IMGUI works)

4721285--446633--CJK support wait.gif
Oh, wait… some kind things works fine, why?!

I have a similar issue with ShaderGraph UI and reported as Case 1167339.

Hi @Creta_Park . I cannot seem to reproduce this issue on my machine, other than some window lag between the IMGUI and UIElements panels.

What versions of Unity have you noticed this problem in?

I’m using 2019.1.9f1.

May you should try in windows 10 CJK lanugage pack. (im using korean language pack (RS5, 1809))
In english keyboard, can change right alt to change keyboard language layout. (I have physical english keyboard)

4741997--449915--korean.gif


Source

Thanks for the detailed response! I think it may be because I am on Mac, so I cannot use your exact language pack, but I still cannot reproduce the bug.

Do you mind reporting this as a bug so we can look into it further?
You can do this by navigating to Help > Report a bug... in the Unity Editor. It automatically adds the Unity Project as a file to the issue-tracker, but it would be great if you could also attach all these GIFs too.

Thanks for your patience! :slight_smile: We will check it out.

MacOS and Windows have different ways of handling CJK inputs.

Just try this on Windows please, this is simple to reproduce it!

I tried this in Unity sample repo

Step to reproduce

  1. Install Windows 10 based on any CJK language pack on any computer or virtual machine
  2. Install Unity Hub and Unity 2019.x
  3. Download sample and open it in Hub
  4. right alt to change keyboard layout, and try write CJK characters with keyboard
1 Like

Okay, I was able to reproduce it on my coworker’s Windows machine!
Thanks for the easy steps to reproduce. You’re right, this looks like a Windows-specific problem with using the alt-key to switch keyboards.

I will report the bug for you.

1 Like

Bump this cause still not fixed in 2019.3.0f3, What’s going on this problem status now?

This issue is fixed in 2020^