Precise text entry
Distinguish committed line breaks from screen wrapping in a Jianlai draft
Enter three ordinary text items and verify their original line boundaries after display changes, without assuming a task-management feature.
On this page
Enter three ordinary text items and verify their original line boundaries after display changes, without assuming a task-management feature.
1. Fix three targets and their order
Use ordered targets 买纸, 整理资料 and 备份笔记, one per line. These are practice text, not completed purchases, organisation or backup. Preserve reference/order separately from input. Three written actions are not three completed tasks, and no list needs sending. Choose an ordinary note rather than a real chat where return might send. Preserve existing documents; one small saveable area is sufficient without deleting older material.
2. Identify the ordinary editor and actual return control
Confirm Jianlai and identify the actual return-related control. An official screenshot shows a return key, but hosts can handle return differently; a label does not guarantee a paragraph insertion. Check in a nonsensitive draft and move to an ordinary note if the location submits or leaves input. No hidden shortcut or automatic conversion into checkboxes, reminders or cloud tasks is assumed. Separate text entry from host features.
3. Commit the first item before moving to line two
Enter and commit the first item, then use the actual return flow. During composition, return may first confirm a candidate, so one action must not automatically count as both confirmation and a line break. Establish the insertion point on the next line before item two. Blank display space alone is insufficient. Check document text even for a short phrase, recording the item and line transition separately instead of treating tap count as positional evidence.
4. Enter items two and three by their boundaries
Commit item two, insert its break and enter item three, checking order. Do not push text visually downward with spaces: wrapping and a committed break differ. Extra blank rows are not required for the three-item target. If the host adds bullets/list styling, attribute that presentation to the host while inspecting text/boundaries rather than inventing Jianlai task management. Save the initial round before changing size/orientation and obscuring its original structure.
5. Observe wrapping with a longer explanation
Use a separate longer self-written explanation to observe whether available width wraps it into several display lines. Keep it separate from the three-item original rather than add display rows to the task count. No fixed wrap count is promised across fonts, hosts or windows. Wrapping changes presentation without necessarily inserting a committed break. Use existing host cursor/selection tools where available; no keyboard control for invisible characters is assumed.
6. Recheck the items after a display-only change
If available, change only host display width or text size and recheck the three original boundaries without editing content. Keyboard label size and document display size differ; use actual controls without assuming one changes the other. A longer explanation may wrap differently while item count stays fixed. Record the condition or leave it pending if unavailable. Another device’s screenshot or shortened wording is not this display-only comparison.
7. Diagnose composition, line breaks and storage separately
For two items on one line, inspect whether a break was committed. If only candidates disappear, inspect composition confirmation. For changed text after reopening, inspect host storage/version. These are not all broken return, and repeated presses can add unwanted blank rows. Correct one boundary and check adjacent words. Wrapping may vary with width; committed breaks belong to the target. Keep unverified invisible characters unknown instead of certifying structure from neat appearance alone.
8. Reopen and deliver text rather than completed tasks
Restore everyday display, save, leave and reopen, checking content, order and committed boundaries. Deliver input/return observations, longer-text control and display change rather than merely three visible rows. Written backup/task labels do not mean those actions happened, and no reminder synchronisation is established. Recheck return behaviour after host, version or scheme changes. The deliverable is an ordinary structured draft with pending conditions, not device-wide or real-workflow certification.
Related guides and sources
Mixed-language note, One-location revision.
Checked on November 16, 2026: Apple’s Finland lookup, cross-checked against China, lists Jianlai 1.0.5, requiring iOS / iPadOS 16.0 or later. Official store information and screenshots establish the input-language, layout and appearance scope; identify installed controls. Tasks use original nonsensitive samples. Storage and text selection depend on the host editor, without assuming unpublished keyboard tools. Keep expectations separate from observations; no completed physical-device or universal input-environment test is claimed.
Official Apple screenshot: personal keyboard and visible keys.