Identifiers, display and revision

Jianlai tutorial 27: map keyboard-background visibility with an original nine-cell image

Prepare your own nine-cell background image for Jianlai and record what remains visible in preview, actual input and another available screen state. The outcome is a nine-region table tied to source locations and observation conditions. No crop control is assumed, and obscured or absent regions are not automatically interpreted as deleted image content.

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

Prepare your own nine-cell background image for Jianlai and record what remains visible in preview, actual input and another available screen state. The outcome is a nine-region table tied to source locations and observation conditions. No crop control is assumed, and obscured or absent regions are not automatically interpreted as deleted image content.

1. Prepare a position-referenced image externally

Using an image tool you already know, make an owned nine-hundred-by-nine-hundred-pixel practice image outside Jianlai. Divide it into three rows and three columns, each cell three hundred pixels square. Label the nine regions according to the position card below, from top to bottom and left to right. Give neighboring cells different lightness and clear boundaries. Use no private photograph or screenshot containing someone else’s data. Create labels and grid lines externally, not as a claimed Jianlai drawing feature. Save an untouched source and a working copy, checking for nine unique labels with none missing. These dimensions define the source image only, not the keyboard’s displayed pixel size or each cell’s visible area.

A1 A2 A3
B1 B2 B3
C1 C2 C3

2. Prepare nine observation rows

Make nine external paper or note rows, one per region, with columns for preview, actual input and another state. Allow four descriptions: complete label visible, part of region visible, foreground-obscured, or not yet located. Not located does not establish cropping. Background scaling, foreground keys and preview dimensions can all affect recognition, so an unknown result is legitimate. Also record source size, device, host, orientation and chosen theme, rather than nine ticks alone. Leave results blank before operating; theoretical grid positions are not observed layouts. The table traces the same source through actual states, rather than rating theme beauty or asserting consistency across devices.

3. Choose the copy through a real background control

Jianlai’s public information and official screenshots support custom background images, but editable options depend on the installed interface. Enter a genuinely editable theme or background area and select the working copy only through an identifiable image-selection flow. If no such control is found, record the version and stopping point instead of inventing a button name. If a preview exists, inspect which region labels are recognizable and fill the rows. Without a preview, mark that column unavailable. If additional display adjustments appear, record current values before changing anything; keep defaults for this round. Assume no crop, alignment or aspect-lock control. Preserve the source image: a display selection does not prove that the original image was rewritten.

4. Inspect the actual keyboard in an ordinary body

Complete the installed version’s real save or apply flow, return to your private ordinary text host and summon Jianlai again. Enter and commit the fixed phrase below. It contains one ASCII space; its digits identify this lesson’s sample, not image coordinates. Inspect the actual keyboard while holding theme, font and layout state constant, and record recognizable regions in the nine-row table. The phrase in the document proves committed text only, not visibility of all nine background cells. A candidate area or keycap obscuring a region does not make it disappear from the source image. If the keyboard still shows the previous background, first verify extension identity, actual theme application and whether the input area needs reopening. Do not change to another image and destroy the comparison.

检图 27

5. Choose a genuinely available second state

Without changing the source or theme, choose another orientation or editable-space state actually supported by the device and host. If orientation is locked or the host cannot change, do not guarantee landscape; mark that state unavailable and retain the complete first-state table. If a change is possible, record the specific before and after states and inspect the same nine labels again. Do not assume the image is cropped by width or pinned to a particular edge. Keep the sample phrase in the document and use no real outgoing message. If the keyboard layout also changes, list that condition separately rather than attributing every visible difference to image scaling. Conclusions apply only to the actually reproducible combination.

6. Compare cell evidence instead of guessing a scaling algorithm

From the table, choose a label fully recognizable in both states, a partly visible region and an unknown region. If a category did not occur, record its absence rather than inventing an observation. Use adjacency in the source image to confirm positions, avoiding confusion between a partly exposed color patch and another cell. Write only supported descriptions, such as a complete label with its lower edge obscured; one missing label cannot establish an exact crop percentage. This exercise measures no mapping between source pixels and screen pixels, so a three-hundred-pixel cell is not an actual key width. Keeping uncertainty makes a same-condition recheck more useful than inferring an internal rendering algorithm from one screenshot.

7. Diagnose the wrong image, old theme and poor legibility

If none of the nine labels matches, first check that the working copy rather than another image was selected and that the applied theme is the same. Do not begin by repeatedly cropping the source. If keycaps or candidate text simply cover labels, record occlusion rather than import failure. If the background severely interferes with input text, return to a known-readable theme for the body check and retain the test table for later adjustment. Usability matters more than exposing every cell. Change only one actually available parameter per trial and add a new condition column rather than overwriting the original observations. Without evidence, do not diagnose compression, failed remote synchronization or private caching, or require extra permissions to fix an unknown display effect.

8. Deliver the map and a recoverable theme record

Deliver the source image, working copy, nine-row table and committed sample text, labeling previews, orientations or states that were not actually tried. Save an identifiable theme name or external annotation with device conditions so the earlier readable configuration can be restored. If the interface offers no editable name, name the trial externally rather than inventing an in-app favorites feature. You may reopen the input area and recheck the same state; record consistency only if observed, otherwise leave it blank. The result explains which source regions are visible, obscured or unknown in the current keyboard, not that every background fully adapts. A new image, device or theme requires a new observation column instead of reusing this conclusion.

First background application and readability; Actual iPad input-space map.

Checked on 17 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: Apple text editing guide.