Structured text and scientific notation
Jianlai TSV handoff: real tabs between three fields, not four spaces
A visually aligned three-column note is not necessarily TSV. Enter field text with Jianlai in a normal editor, then insert or transfer actual tabs through the host’s available controls. Deliver the literal text, per-line field checks and target-import observations. The keyboard does not parse tables, and alignment in a note does not prove that columns were imported.
On this page
A visually aligned three-column note is not necessarily TSV. Enter field text with Jianlai in a normal editor, then insert or transfer actual tabs through the host’s available controls. Deliver the literal text, per-line field checks and target-import observations. The keyboard does not parse tables, and alignment in a note does not prove that columns were imported.
Agree on three nonempty fields
Create a separate practice note with the headers item, count and note, followed by pencil and folder records. Use three nonempty fields per line; no field contains a tab or newline, and notes contain ordinary English words. Write the order and character contract first, without copying contacts. Choose an existing plain-text host and record whether Tab moves focus rather than inserting a character. If it cannot insert tabs, draft the fields separately and assemble them in an existing text tool. Do not invent a dedicated TSV key in Jianlai. Counts are decimal text and column order remains fixed.
Separate a visible notation from actual characters
The first sample is explanatory notation: TAB inside angle brackets is five visible characters, not a delimiter. The second code block contains actual tabs and can serve as your own reference copy. Enter headers and words with Jianlai, then use the host’s real controls for delimiters. Record copied reference text as copied rather than typed. Equal-looking gaps prove nothing because fonts, tab stops and window width affect appearance. Read all three saved lines again, excluding code fences, sample labels and unintended blank lines. After saving, make a notation-only check: replace TAB with GAP inside the explanatory angle brackets. This remains ordinary text and leaves the real TSV untouched. The exercise separates visible labels from control characters; a changed label does not prove removal of a delimiter. Changing the actual delimiter requires a separate file and fresh character and import-rule checks.
item<TAB>count<TAB>note
pencil<TAB>12<TAB>ready
folder<TAB>3<TAB>archived
item count note
pencil 12 ready
folder 3 archived
Count delimiters before columns
Under the simple TSV convention registered with IANA, each line is a record, tabs separate fields and every line has the same field count. Each example line needs two actual tabs and therefore three fields. The first line supplies names rather than a third item record. If the editor exposes invisible characters, inspect both tab marks. Otherwise, pass your copy to an existing tool that splits on tabs and record the resulting columns. Neither check can be replaced by measuring visible gaps: four spaces remain four spaces even when they align.
Edit only a count field with Jianlai
Return to a normal field with Jianlai active. Change folder’s count from 3 to 4 while preserving both tabs and archived. Position the cursor using the host’s controls and select only the digit 3. Cancel and reposition if the selection crosses a tab. Read folder, 4 and archived from left to right, then verify that the other two lines are unchanged. Soft wrapping depends on window width; do not remove delimiters to keep a row on one screen. Record any actual candidate replacement or host correction without manufacturing a fault.
Make a space-delimited counterexample
Save a counterexample from the corrected copy and replace only the tab between folder and 4 with four ordinary spaces. The display may look similar, but splitting on tabs now gives two fields; the first contains folder, spaces and 4. Record literal characters and field counts for both files separately from observed imports. This tests the delimiter contract, not whether every spreadsheet can recognize spaces. If a target guesses separators automatically, record that condition and repeat with an explicitly fixed tab rule.
Preserve text during target handoff
For an existing spreadsheet target, create a blank practice sheet and import or paste the valid copy using tabs. Check that headers occupy separate columns and pencil and folder occupy separate rows. Preserve the first column as text and inspect count display and values separately; no formula conversion is required. Do not import the surrounding instructions or paste into a production financial file. If the target cannot split fields, retain the text and field checks and mark handoff incomplete rather than passing it on visual alignment.
Troubleshoot characters, host and import rules
If everything lands in one cell, check actual tabs and the target’s delimiter setting. Extra rows suggest embedded newlines. A Tab action that moves to another control shows host navigation in that trial, not a lost Jianlai character. Repair full-width digits or replaced English words within the affected field and retain the failing copy. Change one condition at a time rather than the keyboard, importer and encoding together. Without an invisible-character view, state the evidence limit; a screenshot cannot establish the file’s tab count.
Reopen and deliver the three-line artifact
Close and reopen the saved copy, checking two tabs and three fields per line and folder’s count of 4. Deliver the valid text, space counterexample and import record with device, Jianlai version, host and delimiter-entry method. Close the exercise without deleting originals. Explain where field text was entered, how tabs entered the file and which step actually verified splitting. If transport rewrites whitespace, the receiving end must inspect literal characters again; an earlier pass does not guarantee every later transfer.
Related guides and sources
Mixed text and punctuation; CSV records.
Checked on 19 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: IANA TSV registration.