Fixed
Apple ID sign-in failed on non-English Windows
Signing in died with 'latin-1' codec can't encode characters in position 0-5 after the password check had already succeeded (#3). The trusted-device 2FA step puts anisette fields on the HTTP request; on a Chinese Windows install the timezone display name is 中国标准时间, and HTTP headers must be latin-1. Timezone and locale are now rewritten to ASCII Apple-style values before they leave the engine.
If you hit this on 1.1.2 or earlier, update to 1.1.3 and sign in again — no cache wipe needed.
Verified: reproduced the exact encode error, fixed it, regression-tested, and confirmed in the installed 1.1.3 engine. The installer is unsigned, so SmartScreen will warn — the SHA-256 is in SHA256SUMS.txt.