Identifiers, display and revision
Jianlai tutorial 26: preserve leading zeros and distinguish identifiers from quantities
Enter an original three-line ledger for an identifier, quantity and lot, preserving each leading zero with Jianlai and separating character contracts from external numeric conversion. Deliver copyable source, a field-role ledger and one precise repair. Numerically similar appearances do not establish identical identifiers.
On this page
Enter an original three-line ledger for an identifier, quantity and lot, preserving each leading zero with Jianlai and separating character contracts from external numeric conversion. Deliver copyable source, a field-role ledger and one precise repair. Numerically similar appearances do not establish identical identifiers.
1. Give identifiers and quantities different roles
On paper, define the first line as a fixed-width three-character identifier, the second as a quantity and the third as fixed-width three-character lot text. These labels are local exercise data, not real stock or personal information. Compare identifiers and lots exactly as text: a leading zero belongs to their identity and must not be dropped merely because it adds no numeric magnitude. The agreed quantity is seven, but the source is still ordinary text; a future receiver decides whether to convert it to a number. Make columns for field name, target characters and purpose, and state that these are not three quantities to add. An automatic loss of zeros can then be traced to a misinterpreted field rather than treating every digit-containing text as calculator input.
2. Enter labels and values as three exact lines
Confirm Jianlai is showing in your ordinary private draft, then enter the three lines below. Labels use uppercase Latin letters, each followed by one ASCII colon and one ASCII space. Two hard newlines separate the fields, with no blank lines or code fences. The first value is zero-zero-seven, the second just seven and the third zero-seven-zero. Notice that the third line ends in zero too; do not inspect only prefixes. Switch letters, digits and punctuation with the actual layouts, without assuming an inventory form or special identifier mode. Commit composition and inspect the body values rather than keycap digits as proof of entry. If the host reformats text, preserve a literal copy before investigating the change so the sole reference is not overwritten.
ID: 007
QTY: 7
LOT: 070
3. Check widths and character order separately
The first value has three characters, with two zeros before seven. The quantity has one character. The lot has three, with zeros before and after seven. Label characters and the space after the colon do not count toward value width, but remain required source characters. Check for three lines, then copy values into paper boxes of three, one and three positions. Verify order as well as the set of characters. If zero resembles a Latin letter, inspect the actual input layout and copied source rather than guessing from a font. A screenshot can mark positions but cannot replace copyable source. Do not globally delete zeros for visual simplicity: that would directly change the identifier contract.
4. Verify text equality rather than numeric equality
In the role ledger, state that the first value is not the same identifier as a lone seven: its length and prefix differ. If the lot becomes seventy without its leading zero, a numeric interpretation might be equal, but the agreed three-character representation is lost and the task fails. This does not mean every identifier must have three positions; these two fields were explicitly defined that way for this exercise. Real systems require their own rules. A quantity can be interpreted as a quantity without forcing identifiers into sums or automatic padding. A later format such as JSON needs explicit receiver-agreed string or numeric types; standard JSON number grammar does not allow multi-digit leading-zero numbers. The keyboard does not decide business-field types.
5. Repair just one zero-stripped copy
After saving the correct three lines, create a copy in which only the first value is mistakenly a lone seven. Keep the other values and labels unchanged. Diagnose two missing prefix zeros in the identifier, not a quantity that is two items short. Use the host insertion point at the start of that value and enter two zeros with Jianlai. Verify that the first value has three characters again, the quantity still one and the lot still zero-seven-zero, then compare the entire copy with the reference line by line. If the whole line is selected unintentionally, cancel before typing. The test checks local repair and unchanged neighbors, not merely several zeros appearing on screen. It does not establish automatic identifier recognition by Jianlai.
6. Check receiver fidelity before any handoff
For a handoff into another private ordinary editor, preserve the source first and copy only the three body lines. Check leading zeros, labels and newlines. If the receiver is a type-inferring spreadsheet or form, investigate its text-field controls using a nonprivate copy. Stop that route if no reliable preservation method is available rather than testing real identifiers. If zeros disappear, compare before and after paste to distinguish receiver conversion from an entry omission. Mark handoff untested if not performed. This lesson offers no Jianlai spreadsheet export, field lock or automatic zero-loss protection, nor a guarantee of formatting across applications. Source and receiver results require separate evidence.
7. Diagnose zero loss, glyphs and wrapping
First distinguish actual character loss, located by value width and source comparison. Second, characters may remain but look like letters; inspect their origin rather than treating poor legibility as changed data. Third, a narrow window can visually wrap text without changing the three source lines. If zeros disappear only after reopening, examine host saving or conversion rather than blaming the input method solely because Jianlai was active. Change one condition at a time and keep the known-correct copy. In particular, do not change layout, font and receiving tool together. Record field, position and whether the difference arose during entry or after handoff. A vague “number error” is insufficient to reproduce this specific discrepancy.
8. Save roles and repair evidence
Deliver the three clean source lines, a field-role ledger and a repair note, stating this exercise’s two fixed-width three-character identifiers and one-character quantity. Close and reopen the practice host, then copy and compare original characters. Mark persistence as passed only if retained; an unused receiver stays untested. Keep theme or font observations separate from values, and do not substitute screen column width for character width. For a real identifier system, establish its allowed characters, length and receiving format before choosing entry and checking procedures. The lesson supplies a method for preserving an agreed representation and locating zero loss. It does not issue identifiers, fill numbering gaps or prove actual inventory quantities.
Related guides and sources
Numbers, signs and units; Local revision and neighbour 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: RFC 8259 number and string grammar; Apple text editing guide.