States, languages and diagnostics
Jianlai Japanese practice card: check two Hiragana phrases and two Japanese full stops
Use the original あさ。あおいそら。 as a nine-character practice card. Establish an actually available Japanese input route, then check kana, Japanese full stops and committed text separately. A public language switch does not promise a particular Japanese layout, romaji conversion or candidate feature; follow the actual available path.
On this page
Use the original あさ。あおいそら。 as a nine-character practice card. Establish an actually available Japanese input route, then check kana, Japanese full stops and committed text separately. A public language switch does not promise a particular Japanese layout, romaji conversion or candidate feature; follow the actual available path.
1. Establish Japanese input rather than interface language alone
Summon Jianlai in an ordinary note and record version, host and visible language. Establish an actual Japanese input route in the installed version. The official multilingual image shows 日本語 and grounds starting at that entry, but does not show every Japanese key or conversion step. Japanese menu text alone is not Japanese input. If the route is absent, retain interface/version evidence and leave entry pending. Pasting the whole sentence is not a key-input trial, nor is system Japanese output a Jianlai pass. Preserve existing drafts and use a new line, holding theme and font fixed.
2. Split the original practice into nine characters
The card concatenates あさ。 and あおいそら。 without a space or newline. The first has two Hiragana plus a full stop; the second has five plus a full stop: seven kana, two stops and nine characters. These are the explicitly listed single-code-point characters, not a definition of length for all Japanese text. Two あ occur at distinct positions and both count. Number positions one through nine externally and preserve the source. Screen wrapping is not another newline. Avoiding combining voiced marks and Kanji conversion creates a small checkable target; it neither rejects those capabilities nor claims to test them.
3. Enter the first phrase and confirm commitment
Use the actual Japanese route to enter あさ。 and compare every character with the card. Direct kana or another genuinely available key/candidate path may be used, but record only the observed process rather than invent universal romaji rules. If candidates appear, confirm the target remains in committed text; seeing あさ in composition is not commitment. Use an actual reachable punctuation entry. If the Japanese stop is unavailable, retain the two kana and stopping point instead of substituting an English period and marking equality. Preserve this first phrase; the next does not automatically pass missing earlier characters.
4. Continue with the second phrase without an extra separator
Keep the same input state and continue with あおいそら。, confirming the second occurrence of あ. The source has neither half-width nor full-width spacing between phrases, so do not add an English-style post-period space. Preserve and locate any space introduced by the host or input state. Distinguish width-induced wrapping from a real newline instead of interpreting two visible rows as two source records. Wrapping is acceptable while character order must match the target below. Mark any switch to another keyboard explicitly; a mixed route is not independent completion with Jianlai.
あさ。あおいそら。
5. Distinguish Japanese full stops from English periods
Positions three and nine are 。, U+3002, while English . is U+002E. Similar appearance or placement does not make them the same character. Official Unicode charts establish identity, not what this device actually selected. An existing plain-text inspection method may assist. If appearance alone is inconclusive, leave the code-point check pending rather than invent an in-app inspector. Replacing stops with periods cannot pass exact equality, even when length remains nine. A separately labelled external comparison is possible, but the target stays fixed and correct commitment remains distinct from font rendering.
positions 3 and 9: 。 U+3002
English period control: . U+002E
6. Find mismatches with nine positions, not length alone
Compare the sequence あ,さ,。,あ,お,い,そ,ら,。 position by position, especially the repeated あ at four and the final stop. Length nine is preliminary: swapping い and そ or replacing both stops with periods can preserve length while failing equality. An existing computer text tool can inspect an obtained plain-text copy, with external checking and possible copy processing recorded separately. It is not a phone keyboard self-test. Without a reliable copy, retain character observations and limitations rather than fill execution results. Keep the initial entry separate from a corrected draft so the final version does not conceal the original mismatch.
7. Diagnose language, commitment and character identity
For no Japanese route, inspect input language and keyboard identity. For candidates without document text, inspect commitment. For nine characters failing equality, inspect order and punctuation. Changing system region, interface language and font together cannot isolate a cause, and an absent candidate does not establish universal Japanese failure. Check font versus character for an altered glyph, and record an absent key rather than borrow another keyboard’s layout. Correct one position per revision, preserving drafts and recoverable language configuration. Incomplete work should identify confirmed portions and stopping point rather than mix another input method into nine passed boxes.
8. Restore the original language and deliver both phrases
After retaining original entry, per-position results, actual route and pending checks, restore the recorded daily input language and confirm ordinary Jianlai input. Pass restoration only if performed; do not invent restoration of an unchanged interface language. Explain the evidence for two phrases, seven kana and two stops, including external inspection or another keyboard’s involvement. This checks the small card and input route, not translation, every kana, Kanji conversion, prediction or all hosts. A new scheme, font or voiced-mark word needs its own target and character agreement rather than reuse this nine-position ledger as universal proof.
Related guides and sources
Interface and input languages; Glyph and character identity.
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 language-interface image; Unicode Hiragana character chart; Unicode CJK punctuation chart.