# Jianlai YAML source: preserve nesting with two spaces and a literal hash with quotes

Language: en
Canonical: [Jianlai YAML source: preserve nesting with two spaces and a literal hash with quotes](<https://allluckly.cn/en/guides/jianlai-yaml-two-space-nested-mapping-quoted-hash/>)
中文：[中文 HTML](<https://allluckly.cn/guides/jianlai-yaml-two-space-nested-mapping-quoted-hash/>)
English: [English HTML](<https://allluckly.cn/en/guides/jianlai-yaml-two-space-nested-mapping-quoted-hash/>)
Published: 2026-11-19T00:00:00+08:00
Modified: 2026-11-19T10:24:33+08:00
Author: Bison

Type a four-line YAML card in an ordinary text field, checking nesting, ASCII colons and quoted text. Deliver the source, a dedented control and external parsing evidence. Jianlai enters text, the host edits it and a separate tool interprets YAML; visual alignment does not activate a configuration.

English translation of the [Chinese original](<https://allluckly.cn/guides/jianlai-yaml-two-space-nested-mapping-quoted-hash/>), translated on 2026-11-19. Original publication dates, attribution, code and version notes are retained.

Type a four-line YAML card in an ordinary text field, checking nesting, ASCII colons and quoted text. Deliver the source, a dedented control and external parsing evidence. Jianlai enters text, the host edits it and a separate tool interprets YAML; visual alignment does not activate a configuration.

## Separate the plain-text exercise from live configuration

Create an owned practice draft, identify Jianlai and record the host/input state. The target describes a fictional lesson, without credentials or a real service, and belongs in no production settings. Root key lesson contains title, note and copies. The title is Harbor #2, the note is text on and the count is numeric 3. Preserve this structural contract externally rather than rewrite it to match errors. Use a host retaining real newlines and ordinary spaces. If rich formatting hides source characters, use an existing plain-text tool instead of assuming a dedicated YAML editor in Jianlai.

## Enter four literal lines with two-space indentation

Enter lesson and an ASCII colon, then a real newline. Each following line begins with two ordinary spaces, then key, colon, one space and value. Check committed text after each line. The sample is the complete target; copies remains nested, without bullets or extra blank lines. Two spaces are this exercise’s contract, not YAML’s only permitted width; keep siblings consistent. Full-width spaces, tabs and visual indentation do not replace character inspection. Record host-generated indentation rather than call automatically inserted spaces individually typed.

```
lesson:
  title: "Harbor #2"
  note: "on"
  copies: 3
```

## Distinguish indentation characters from a Tab action

YAML block structure depends on indentation, and the specification excludes tabs from indentation for portability. A host’s Tab action may insert spaces, insert a tab or move focus; record the actual result. Check that each child key begins with the two U+0020 spaces required here. Without an invisible-character display, inspect your copy with an existing text tool and state limits. This does not ban tabs everywhere in YAML; inline separation differs from indentation. TSV’s need for real tabs does not transfer to these leading positions. Different targets have different character contracts.

## Keep quoted hashes distinct from comments

ASCII double quotes enclose Harbor #2, making the space and hash part of the title. In an external control remove only those title quotes: title: Harbor #2. The space-separated hash then begins a comment, leaving Harbor as the value and failing the target. Keep that control separate instead of repeatedly deleting quotes in the real draft. Quote on explicitly as a string as well. YAML versions and resolution modes can treat unquoted words differently; do not remove its quotes and predict the same Boolean result for every tool.

## Inspect nesting and value types after external parsing

If an existing trusted YAML tool is available, parse only an offline practice copy and record version/schema. Expect lesson as the sole root key, with three children: full title Harbor #2, string on and numeric 3. Inspect position and type as well as values; no error message alone is insufficient. No real service configuration is loaded and no course is created automatically. Without a parser, deliver character/structure checks and mark machine interpretation unperformed. Site validation does not certify device-entered text under every YAML 1.2 implementation or mode. As a separate paper check, add a duplicate title key: two same-named keys are not two independent titles in this mapping. A tool’s silence does not establish conformity; retain the duplicate source and record specification and mode rather than substitute a final displayed value.

## Dedent only the last line as a structural control

Save a control and remove only the two leading spaces from the final copies line. copies becomes a root key, leaving title and note under lesson. Successful parsing still fails the three-child contract. Placing copies last deliberately avoids subsequent child lines introducing another syntax problem during this one change. Record exact equality, parse success and resulting structure separately. Numeric 3 alone does not prove correct nesting. Restore only those two spaces before rechecking lines and quotes, without changing keys, types or values together.

```
lesson:
  title: "Harbor #2"
  note: "on"
copies: 3
```

## Troubleshoot indentation, colons and quote boundaries

Check tabs in indentation, full-width colons, paired quotes and host smart-quote replacement before investigating a parser error. For a successful parse with wrong data, inspect nesting and the full title instead of reinstalling the keyboard. Soft wrapping adds no source line; do not delete correct spaces for a four-row display. If saving reformats keys/indentation, retain before/after versions and distinguish semantic equivalence from exact text. A beautified screenshot cannot replace this literal target. Repair one condition and invent no Jianlai syntax checker, repairer or deployment feature.

## Reopen and deliver text, structure and interpretation

After reopening your draft, check four lines, three two-space prefixes, complete quotes and copies still inside lesson. Leave persistence unpassed if reopening was not performed. Deliver the source, unquoted control, dedented control and actual parsing evidence, identifying keyboard entry, host editing and external interpretation. Restore ordinary settings and keep practice out of production apps. Test exact text and intended structure separately. Lists, deeper nesting or other scalar forms need new checks; four lines do not establish all YAML syntax or host compatibility.

## Related guides and sources

[Real tabs and fields](<https://allluckly.cn/en/guides/jianlai-tsv-real-tabs-three-column-handoff/>); [JSON strings and numbers](<https://allluckly.cn/en/guides/jianlai-json-object-string-number-source-contract/>).

Checked on 19 November 2026: [Apple’s Finland lookup](<https://itunes.apple.com/lookup?id=6754281557&country=fi&entity=software&timestamp=20261119>) and [China lookup](<https://itunes.apple.com/lookup?id=6754281557&country=cn&entity=software&timestamp=20261119>) both list Jianlai 1.0.5, requiring iOS / iPadOS 16.0 or later. The [official store](<https://apps.apple.com/fi/app/id6754281557>) 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: [YAML 1.2.2 indentation and scalar specification](<https://yaml.org/spec/1.2.2/>).

