I don't even understand it; I just can recognize a character and type it in. The only time I have to do so is in looking at poorly designed firmware sites and stuff like that, but I manage when the developers do not accomodate for me.
But that's not what the topic is. The topic is HOW developers should accomodate users. And I'm simply taking the stance that preventing user selectability is a lesser evil in specific cases than universal selectability, because the former can be mitigated with less scripting overhead than the latter.
A native Chinese high school graduate is generally expected to know around 3500 characters. A middle school student, 2500-3000.
For Kanji the numbers are around 2136 and 1200 and respectively.
If you know the language, then you don't need this.
But if you're claiming that you can type a random Hanzi or Kanji character you see in an interface without speaking the language, you are either missing something here or not arguing in good faith.
It's solvable through the handwriting input, although you do need to know the approximate order and direction of strokes or you will get nowhere. I know roughly zero Chinese characters and use this often-ish.
Most importantly, you also need to find and enable the handwriting IME on your OS; which is... not a reasonable thing to ask of someone who doesn't actually type that language on a daily basis.
But that's not what the topic is. The topic is HOW developers should accomodate users. And I'm simply taking the stance that preventing user selectability is a lesser evil in specific cases than universal selectability, because the former can be mitigated with less scripting overhead than the latter.