Why automation tools cannot type Chinese, and what OculiX does instead
An OculiX user filed a bug. Typing two Chinese characters into an input field silently produced garbage. The fix took fifteen lines of Java, but the explanation reaches back to how AWT was designed thirty years ago around the assumption that one character equals one keystroke. Here is what happens when that assumption meets the rest of the world.