Understanding How Input Methods Encode Characters and Code Pages

(1) When you type on a keyboard, the computer receives an ASCII code sequence.

(2) The input method converts the ASCII sequence into its own defined code, which is then used to display characters.

(3) The characters you see in windows such as Notepad, WordPad, or a DOS console are rendered only when the code produced by the input method matches the code page (character set) of the font; otherwise they appear as garbled text.

The code page (e.g., cp936 for GBK, cp950 for BIG5, cp20936 for GB2312) determines how byte values map to glyphs. In a DOS console, the chcp command without parameters shows the current code page, while adding a parameter changes it (e.g., chcp 936 or chcp 437 ).

(4) When saving text from editors like Notepad, the file can be stored in Unicode formats. Little‑endian Unicode (UTF‑16LE) and big‑endian Unicode (UTF‑16BE) or UTF‑8 may be used, and a byte‑order‑mark (BOM) is often added at the file header to indicate the encoding.

Therefore, the encoding of characters typed directly via an input method depends on the specific input method, the active code page, and the file’s saved encoding; it cannot be generalized without analyzing the particular context.