# Jianlai tutorial 24: enter an offline Markdown link source and check its boundaries

Language: en
Canonical: [Jianlai tutorial 24: enter an offline Markdown link source and check its boundaries](<https://allluckly.cn/en/guides/jianlai-markdown-inline-link-offline-source-brackets/>)
中文：[中文 HTML](<https://allluckly.cn/guides/jianlai-markdown-inline-link-offline-source-brackets/>)
English: [English HTML](<https://allluckly.cn/en/guides/jianlai-markdown-inline-link-offline-source-brackets/>)
Published: 2026-11-17T00:00:00+08:00
Modified: 2026-11-17T15:44:18+08:00
Author: Bison

Type an offline Markdown link source with Jianlai and check the bracketed label, parenthesized destination and literal address separately. The sample uses a reserved invalid domain: send no request and do not click to test it. The deliverables are source text and a paper interpretation, not claimed successful rendering or an available link.

English translation of the [Chinese original](<https://allluckly.cn/guides/jianlai-markdown-inline-link-offline-source-brackets/>), translated on 2026-11-17. Original publication dates, attribution, code and version notes are retained.

Type an offline Markdown link source with Jianlai and check the bracketed label, parenthesized destination and literal address separately. The sample uses a reserved invalid domain: send no request and do not click to test it. The deliverables are source text and a paper interpretation, not claimed successful rendering or an available link.

## 1. Create a source-only practice area

Choose a private ordinary text draft that lets you inspect original characters, rather than a field showing only a rich-text link title. Create a local practice copy and define the task as saving one link expression accurately without visiting its destination. The reserved invalid domain is for this offline example, not a real website, author service or login endpoint. Do not click even if the host makes it tappable. Keep target source, manual interpretation and actual host display in separate columns. If a host only creates rich text with no source view, choose a private editor that preserves the characters. An attractive link card does not satisfy this source-entry task, and no new service registration is needed.

## 2. Enter the label and destination delimiters

After confirming Jianlai, use the actual English and symbol layouts to type the sole target below. Complete the square brackets and their title, then immediately enter the opening parenthesis, address and closing parenthesis. There is no space between the closing square bracket and opening parenthesis. Inside the label there is exactly one ASCII space between the English word and zero-seven. Zero-seven belongs to the title and is not a quantity to strip of zeros. The line contains no code fences, quotation marks or final punctuation. Commit any pending composition before checking characters. A similar-looking title in a preview is not a reason to skip the source. Symbol positions depend on the installed version; no dedicated Markdown mode, auto-bracket button or template shortcut is invented.

```
[Draft 07](https://example.invalid/notes)
```

## 3. Map what each bracket pair contains

Draw separate boxes for square brackets and parentheses: the first contains link text and the second the destination address. Under CommonMark’s inline-link description, this simple example has no optional title, nested label, escaped parenthesis or relative-URL resolution. Count one pair of each delimiter and check that the closing square bracket immediately precedes the opening parenthesis. Do not treat them as the same shape. Correct pairing is insufficient without correct boundaries: the final closing parenthesis follows the path and is not part of the destination itself. Put the manual explanation in a separate column, not after the source, where seemingly explanatory words would become additional input text.

## 4. Inspect the address without visiting it

Read the destination in segments: scheme, two slashes, hostname, slash before the path and path word. Check spelling and ASCII periods. Keep the invalid-domain suffix unchanged rather than substituting a real commercial site or private address. RFC 2606’s reserved suffix explains this sample choice; it is not a reason to perform a DNS lookup. Add no spaces and do not casually change path case. This is a text comparison only: open no browser and do not use clicking as a success test. A future real article would need a separate task to verify an authorized destination and published result. This offline outcome does not provide that verification.

## 5. Repair a broken delimiter connection

In a new copy, insert just one space between the closing square bracket and opening parenthesis, leaving the correct line untouched. The character ledger already identifies the difference from the target; no renderer is needed to test whether a particular dialect tolerates it. Under this task’s no-space contract, use host insertion-point or selection controls to remove only that space. Verify that the required space inside the label remains. This comparison trains the distinction between identical space characters in different positions. Deleting all spaces globally would damage the label and fail the repair. If the selection is uncertain, cancel and locate it again, and record that the removed space was at the delimiter junction rather than inside the title.

## 6. Separate paper meaning from host display

In the manual interpretation, state that the intended visible text is the English title with zero-seven and the intended destination is the complete parenthesized address. This is a reading under the cited grammar, not a parser execution report. A host may retain all characters, automatically recognize some as a link, or offer no Markdown support. Record only the display actually observed and do not present any one behavior as a Jianlai promise. This lesson performs neither preview parsing nor network testing; mark rendering and access as not run. A keyboard skin’s font does not turn source into a web page. When host display changes, investigate its text mode and automatic formatting before assuming the input method includes publishing features.

## 7. Diagnose delimiters, substitution and copy range

If the source differs, check the two delimiter pairs and junction space first, label zeroes and letters second, then each address segment. Fullwidth brackets or curly quotes are character substitutions, regardless of visual similarity. If copied text includes explanations, inspect whether the selection extended into the following paragraph instead of immediately retyping the address. When the host shows only a title, return to a source-visible view. If none exists, record that this host is unsuitable for this source check and retain the copy while choosing an ordinary editor. Change one factor per comparison and never probe the network by tapping the link. Source text, display state and actual access are distinct evidence categories; the last remains unperformed throughout this exercise.

## 8. Deliver the offline source and boundary card

Save one clean source line, a delimiter-boundary diagram and a check card listing one space inside the label, none at the junction, the full destination and unperformed rendering and access. After reopening the draft, you may copy and compare characters again; mark persistence as passed only if actually checked. Do not retain only a rich-text screenshot and lose the raw line. Annotate the actual host and input state so a later display difference is traceable. This outcome establishes accurate entry and interpretation of structured text. It does not make the invalid domain usable or prove compatibility across Markdown hosts. A real destination later requires new proofreading and publishing checks rather than claiming this unvisited example is a live link.

## Related guides and sources

[Offline address character check](<https://allluckly.cn/en/guides/jianlai-offline-email-url-ascii-copy-check/>); [Hard breaks and soft wrapping](<https://allluckly.cn/en/guides/jianlai-three-line-draft-hard-break-soft-wrap/>).

Checked on 17 November 2026: [Apple’s Finland lookup](<https://itunes.apple.com/lookup?id=6754281557&country=fi&entity=software&timestamp=20261117>) and [China lookup](<https://itunes.apple.com/lookup?id=6754281557&country=cn&entity=software&timestamp=20261117>) 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: [CommonMark inline links](<https://spec.commonmark.org/0.31.2/#links>); [RFC 2606 reserved domain names](<https://www.rfc-editor.org/rfc/rfc2606.html>); [Apple text editing guide](<https://support.apple.com/guide/iphone/select-edit-and-move-text-iph1a9cae52c/ios>).

