Garbled Chinese text in an SSH terminal does not point to one universal app bug. The remote program may emit bytes in a legacy encoding, the shell may use a non-UTF-8 locale, or the selected font may lack the necessary glyphs. Diagnose the stage before changing clients.
Check the server first
- Run
localeand inspectLANGandLC_CTYPE. A UTF-8 locale, such asen_US.UTF-8orzh_CN.UTF-8, helps programs produce UTF-8 output. - Test known UTF-8 text with
printf '%s ' '中文测试'. If this displays correctly but one log or file does not, inspect that file’s original encoding rather than changing every terminal setting. - Check whether the issue appears in one program only. A program can override the shell locale or output raw bytes from an older data source. A missing-glyph box points to the terminal font, not necessarily to byte encoding.
NeoServer’s terminal can display UTF-8 text and offers an alternative client to test. If the same remote bytes remain garbled in multiple clients, fix the server or source file. If only one client fails, compare its font and encoding settings. Avoid claiming that changing to NeoServer repairs a file stored in the wrong encoding.
If the keyboard cannot compose Chinese characters at all, that is a separate input-method issue; see the CJK keyboard guide.
Ready to try it?
NeoServer · SSH, Mosh, Docker & SFTP client for iPhone, iPad and Mac
Free on the App Store