Separate Jianlai’s app language from its keyboard input languages

Use the actual Chinese, English and Japanese entries to distinguish interface labels from document input.

1. Record two different language states

Record the language of the Jianlai app’s interface and the active keyboard’s input language in an ordinary note. They may match or differ; Chinese settings labels do not prove Chinese-only input. Preserve system language, existing keyboards and notes: the whole device need not change language. Prepare three identifiable practice lines with content you can verify, without private messages or real accounts. Complete keyboard enablement first if needed instead of combining installation and multilingual checks into one task.

2. Identify the two groups of controls

An official screenshot separates app-interface language from keyboard-input languages under language/input settings, showing Chinese, English and Japanese choices. Inspect both groups in the installed version and record selections separately. A checkmark in one group does not enable the other. A follow-system interface option does not promise automatic text-language detection. Follow current names, order and availability. Do not add unrelated system keyboard languages to Jianlai’s claimed support; this task concerns the published scope of this app.

3. Change only the app-interface language first

Keep keyboard input languages fixed and choose a recognisable available app-interface language. Return through the actual flow and inspect changed titles or settings labels. Then inspect the keyboard’s input language in the note without assuming both changed together. Follow any visible redisplay instruction; do not invent app deletion as a requirement. Record old/new interface names and a recovery path. If unfamiliar with the target language, make a small controlled comparison instead of toggling controls you cannot identify.

4. Enable input languages separately

Save the interface-language result, then enable the required Chinese, English and Japanese input choices through actual switches, retaining prior states for restoration. Enabling makes a choice available; active typing still requires identifying the installed language switcher. Distinguish changing the whole keyboard extension from changing language inside Jianlai. Do not prescribe one globe-key action across layouts. If an item is absent, record the actual scope rather than use another keyboard and attribute that language’s result to Jianlai.

5. Check one real passage per input language

Use three lines in the same ordinary note: a familiar Chinese phrase, simple self-written English and Japanese you can verify. Confirm Jianlai and the target language before entering through the actual layout and committing candidates, then inspect final text. If you cannot verify Japanese, record the entry and leave input pending; copying a sample is not keyboard input. Published language support does not promise every conversion scheme, dictionary or automatic translation. Check only the path you actually use.

6. Distinguish composition from translation

Candidate words and confirmation can differ by language; record composition and document text separately. A changed candidate representation does not establish whole-article translation, and an English app interface does not mean Chinese input was removed. Keep theme and font fixed, recording unclear glyphs as appearance issues. Any desired translation is a separate task in an appropriate independently verified tool, not a capability established here. Input-language support, interface localisation and semantic translation are three different results.

7. Diagnose interface, enabled choices and active input

If only app labels change, inspect whether you changed interface language or an input switch. For unchanged input, check extension identity and internal language selection. For changed candidates without document text, inspect composition and focus. Change one condition instead of resetting system language and deleting every keyboard. Retain original labels, target language, control feedback and nonsensitive examples. If a special host field excludes third-party keyboards, compare an ordinary note; bypassing boundaries with permissions is not a language-test pass.

8. Restore a familiar interface and save the comparison

Restore your familiar interface language and desired input choices, redisplay Jianlai and confirm the active state while retaining all three lines. Deliver interface and input rounds separately, distinguishing actual typing, enabled-only choices and pending items. Explain how one app can use one interface language and another for document input instead of merely listing names or flags. Recheck needed paths after version, layout or host changes. Three lines do not certify every vocabulary, conversion scheme or automatic translation on physical devices.

Related tutorials and sources

Switching across apps, Chinese layouts.

Checked on November 15, 2026 against Apple public lookup and the official App Store information and screenshots it lists: version 1.0.5, requiring iOS / iPadOS 16.0 or later, with identity and version cross-checked against China lookup. Tasks use published capabilities; identify actual controls in your installed version. External records are acceptable. Keep expectations separate from observations; no physical-device or universal input-environment test is claimed.

Official Apple screenshot: language and input.