Structured drafts
Jianlai tutorial 25: type a two-state task-list source and check its spaces
Type an original two-line GFM task-list source with Jianlai, marking unchecked and checked character states while preserving hard line breaks, ASCII punctuation and required spaces. Deliver a copyable draft and grammar check card. A textual marker is not proof of completed work, and Jianlai is not claimed to manage reminders, lists or Markdown rendering.
On this page
Type an original two-line GFM task-list source with Jianlai, marking unchecked and checked character states while preserving hard line breaks, ASCII punctuation and required spaces. Deliver a copyable draft and grammar check card. A textual marker is not proof of completed work, and Jianlai is not claimed to manage reminders, lists or Markdown rendering.
1. Separate source practice from real work
Create a private ordinary text copy and define the task as entering two marker states without performing their named actions. The first English item says to read a draft and the second to save a copy, but both are original sample text. Their checked states are stipulated test data, not evidence that reading or saving happened. Do not substitute a working checklist and risk altering real completion states. Keep three columns for source, paper meaning under the rule and actual host display; the latter two are not interchangeable. Choose an editor exposing original characters. If it offers only tappable checkboxes with hidden source, switch to an ordinary text area instead of treating a convenient interface as proof of literal entry.
2. Enter each line with a hard break
After confirming Jianlai is active, use its actual layout to enter the first ASCII hyphen, space, bracket marker and English text. Insert one real newline in the host’s ordinary body and enter the second line. The second marker contains lowercase Latin x, not a multiplication sign, tick graphic or Chinese character. Article fences are not part of the target, and there is no extra blank line between items. Commit pending composition before using the host’s actual newline behavior. If Return in the current field sends content or submits a form, stop and choose a safe ordinary editor. This lesson does not assume identical Return labels across layouts or treat a keycap label as a guarantee of every host’s behavior.
- [ ] Read draft
- [x] Save copy
3. Number the spaces on each line
The first line contains four ASCII spaces: after the hyphen, inside the first bracket pair, after its closing bracket and between the English words. The second has three: after the hyphen, after the closing bracket and between words. Its brackets contain lowercase x, so there is no internal space. Number these positions only on paper, never in the source. This difference is central: collapsing or deleting all spaces in the first line would damage both the marker and word separation. Check that neither line has accidental indentation or a final period. Visually aligned columns do not prove space identity or position. Return to copyable characters for a position-by-position comparison.
4. Read states under the GFM convention
Under the GFM task-list extension, a bracket marker at the beginning of a list item’s text, followed by whitespace, can express task state: the blank marker is unchecked and the letter marker checked. This task fixes lowercase x. Although the rule also permits uppercase X, uppercase would not exactly match the sole target. Check the hyphen forming the list item, the marker at the beginning of its text and the space after the marker; seeing brackets alone does not establish all required context. Write “sample state” in the interpretation, not “reading completed” or “backup completed.” Text can correctly express a stipulated state without causing a real action. Keep that distinction separate from actual execution records.
5. Repair a missing space after a marker
Keep the correct draft and copy it. Delete only the first line’s space after the closing bracket, preserving its other three spaces and the entire second line. Locate the difference with the position ledger, then insert one ASCII space there through the host insertion point. Do not add another space inside the brackets merely to restore the total count. Verify that the repaired line has four spaces in their correct positions: total and placement must both pass. No checkbox tap or renderer execution is needed. If the host converts the list into its own format, investigate source view or restoration. If source cannot be retained, choose another practice area rather than repeatedly deleting unseen characters by guesswork.
6. Check source lines rather than visual bands
Narrow and widen the editing area to observe English text wrapping. The source should still contain two original task lines separated by one hard newline; item count must not change with screen width. If the second item joins the first after copying into another ordinary text area, check the real newline and whether the selection covered both complete lines. If a third item appears, inspect copied explanations or a trailing return treated as content. This builds on basic line-break checks with a more specific criterion: each marker and its own English text belong on the same source line. Leaving brackets on one hard line and adding the text after another hard return fails the target. Record original line boundaries separately from visible wrapping.
7. Assign rendering and input to their owners
Some hosts display GFM checkboxes, some show plain text and others use their own checklist syntax. Record those as host display behavior, not evidence that Jianlai implements a task system. Parsing is not required here; mark rendering as untested when not performed. Any separate tool check must retain its actual result rather than copying a paper-rule explanation into a passed-execution field. If spaces disappear or markers become graphics, compare committed source with saved-and-reopened text to locate the change at input, automatic formatting or persistence. Themes, fonts and keycap appearance affect what is seen, but cannot replace source-character checks or provide reminders, deadlines or background execution.
8. Save source and a state interpretation
Deliver the two clean source lines, a space-position ledger and the two sample-state interpretations, explicitly noting that the text proves neither actual reading nor actual saving. Check marker states first, English text second and the single hard newline last. Keep the sequence in an annotation for reproduction. Mark persistence as passed only if the source actually survives closing and reopening the host; a screenshot alone is insufficient. Real task management later requires creating and checking items in the relevant application. Lowercase x entered in this exercise is not an execution log. The outcome is accurate entry of state-bearing text with Jianlai and a method for finding missing spaces, wrong line boundaries and display conversions.
Related guides and sources
Hard breaks and soft wrapping; Actual space insertion check.
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: GFM task-list extension; Apple text editing guide.