States, languages and diagnostics

Jianlai Shift state: separate a single change, the lock setting and double-tap retention

Use a short letter card in one ordinary text field to compare the original setting, a single Shift action after changing state locking, and a separate double-tap trial. Reconcile actual keycaps with committed characters instead of treating one setting, sentence capitalization and retained capitals as one rule.

English translation of the Chinese original, translated on . Original publication dates, attribution, code and version notes are retained.

Use a short letter card in one ordinary text field to compare the original setting, a single Shift action after changing state locking, and a separate double-tap trial. Reconcile actual keycaps with committed characters instead of treating one setting, sentence capitalization and retained capitals as one rule.

1. Establish a fixed ordinary English input environment

Summon Jianlai in a new private note and establish an actually available English-letter input state. Record app version, host and language. Inspect the original Shift-state-lock setting before changing it: the official image shows the option, but its switch position is not your saved value. Hold theme, font, width and orientation fixed so appearance changes do not conceal keycap state. Use neither secure nor phone-pad fields, which may substitute the system keyboard, and verify Jianlai even in an ordinary field. If English-letter input cannot be established, finish the language-switching basics first and leave this trial pending rather than substitute another keyboard’s result.

2. Enter a baseline without requiring lowercase

At a new line, record visible keycaps or the Shift indicator, then tap the three recognizable positions a, b and c in order, copying the case of each committed character. Lowercase here identifies positions, not predetermined output. Sentence-start capitalization may be another condition and belongs in the environment record. Preserve the baseline instead of deleting and retrying until it looks ideal. If candidates or word replacement intervene, note the step and establish the actual letter state; the final word is not automatically identical to three raw taps. A second baseline needs its own initial state, not one final screenshot used to explain both.

3. Read the setting before one controlled change

The official image says that with the option off, Shift follows the current input state, while double-tapping Shift keeps it locked. This does not mean every route to sustained capitals is impossible when off, nor does it enumerate every host’s sentence-start policy. Record the original value, change only this setting and return to the same note, resummoning the keyboard and checking retention. Hold theme and host fixed. If the installed option is absent, retain version and stopping point. Establish a distinguishable new trial line rather than continue an old sentence with different context. Observe the settings switch and the extension’s keycaps separately; the switch screenshot does not establish output.

4. Map one Shift action to three successive letters

On a new trial line, record the initial state, tap the actual Shift control once, then tap positions a, b and c, inspecting keycaps and committed characters after each. The first character may capitalize and return, or another actual state may persist; no undocumented per-key sequence becomes a mandatory answer. Record action order and avoid calling an accidental double tap one action. An uncertain count invalidates that round and needs a separate replacement, without overwriting evidence. Use the manual ledger below; no in-app key logger or export is required. Stop and retain the line and setting before another condition so a retained state does not leak into the next trial.

manual columns: initial state | setting | Shift action | keycaps | committed a/b/c
Run single-tap and double-tap conditions separately.

5. Run double tapping as its own condition

Preserve the single-action result, establish an identifiable new initial state through actual controls, then deliberately double-tap Shift and enter the same positions. Retained locking is described in the public image, but actual triggering still needs keycap and output evidence. Two taps far apart cannot simply be labelled a recognized double tap. Sustained capitals support this round only; untested punctuation, newlines or reopening remain unfilled. For failure to retain, first inspect taps, language and keyboard identity rather than immediately reject the description. Keep original-value, single-tap and double-tap records separate: final ABC alone does not identify its cause.

6. Keep sentence context in a separate control column

A new line and sentence interior may begin with different case under one setting. Record context before comparing Shift actions. An additional interior trial is a changed context, not a replacement for earlier new-line evidence. A similarly named capitalization option in system settings does not prove synchronization with this app’s switch; Apple’s custom-keyboard documentation distinguishes their access. Record host rewriting of committed text separately. Keycap appearance alone cannot establish that the host preserved characters. Retain before/after states and mark limitations when word replacement cannot be isolated rather than define a universal English-layout case rule.

7. Diagnose actions, state and committed text separately

For unexpected output, verify Jianlai and an actual English state, then initial state, single versus double taps, saved setting and finally host rewriting. Clearing dictionaries, changing themes and system keyboard settings together cannot isolate a cause; no library clearing or reinstallation is needed. A changed icon without changed text calls for separate evidence, not a guessed lost internal event. A change after reopening introduces another condition. Stop any branch whose control cannot be identified and preserve a confirmed baseline. Record actions and actual characters rather than use an origin-free long typing stream to allege universal failure.

8. Restore the original value and deliver the state ledger

Restore the recorded Shift-lock value, return to ordinary input and clear any retained trial lock through identifiable controls if needed. Restoring a setting and establishing current case are separate checks; pass each only if performed. Deliver context, actions, keycaps and text for the original-value, single-tap and double-tap rounds, plus unknown branches. The illustrative ledger does not perform those actions. Keep the exercise as a private draft. Findings apply to this version, language and host. A changed device or setting requires a new initial-state check rather than expanding one public sentence into verified behavior for all capitalization and hosts.

Mixed-text case basics; Host input boundaries.

Checked on 18 November 2026: Apple’s Finland lookup and China lookup both list Jianlai 1.0.5, requiring iOS / iPadOS 16.0 or later. The official store describes themes, backgrounds, fonts and multilingual input. Use controls actually present in the installed version; system editing and host processing are distinguished separately. These are repeatable instructions and paper expectations, not claims of completed device input, host compatibility or format-parser tests.

Method references: Official Apple keyboard-settings image; Apple custom-keyboard documentation.