Precise text entry

Transcribe example email and URL text in Jianlai without sending it

Use reserved-domain examples for an offline address card, checking ASCII delimiters, case and spaces.

English translation of the Chinese original, translated on . Original publication dates, attribution, code and version notes are retained.

Use reserved-domain examples for an offline address card, checking ASCII delimiters, case and spaces.

1. Build targets with explicitly invalid example domains

Use email target [email protected] and URL target https://example.invalid/a-b?x=1 in an ordinary note only, without sending, submitting or visiting. RFC 2606 reserves .invalid for clearly invalid domain names; this separates practice from real contact details rather than supplying a working service. Preserve reference and result separately, with one target per line. Do not use real customer addresses or pass visually similar replacement symbols as the specified character sequence.

2. Fix Jianlai and an ordinary English entry area

Confirm Jianlai and an available English state in an ordinary editable note, not a browser search or recipient field that also changes keyboard behaviour. Retain theme/layout and establish saving first. This is entry practice, not a promise of address completion, URL repair or clipboard history. Record host auto-link styling without tapping it. Blue text or underlining neither proves exact characters nor network validation; inspect the document sequence.

3. Enter and inspect the email in three parts

Enter the email as local name, delimiter and domain, then inspect the complete sequence. Use actual digits/symbol controls rather than universal key positions. Preserve lowercase letters, ASCII dot and no ordinary/full-width internal spaces. If a symbol is unavailable, retain incompleteness and inspect the current page instead of inventing a shortcut menu. Any candidate or automatic substitution requires checking committed text; apparent correctness during entry does not replace result inspection.

4. Group the URL into scheme, domain, path and query

Inspect URL scheme, domain, path and query as groups. Retain both slashes after the colon, the path’s short hyphen rather than a dash, and the intended question/equal signs. The final one is a digit, not letter l; no trailing space or period is specified. Grouping is an external check, not an assumed URL parser. Use cursor inspection and reading rather than treat screen wrapping as a second URL or a committed newline.

5. Distinguish similar appearance from character identity

Compare targets and results at dots, slashes, hyphen, question and equal signs. Similar full-width punctuation does not satisfy this ASCII target. If theme typography changes appearance, inspect character identity rather than guess encoding. No code-point inspector is assumed, and visual width is not precise detection. Keep uncertain locations pending or use an existing separate plain-text check, without attributing full syntax/reachability validation to Jianlai.

6. Correct one actual difference and recheck neighbours

Record an actual difference, position the host cursor and change that location only. Re-read neighbouring groups for deleted letters or added spaces rather than erase/retype the whole address and lose the comparison. If already exact, record no correction. Host selection/magnification is not a Jianlai-exclusive tool. No network operation occurred, so do not report delivered email or a reachable URL.

7. Diagnose character errors separately from link styling

For letters, inspect language/commitment; for symbols, inspect page and width; for changes after reopening, inspect host storage/presentation. Missing link styling is not input failure, and present styling is not exactness. Change one condition without resetting keyboards or granting extra access to repair a question mark. Real reachability testing belongs to a separate authorised task. This invalid example is not a live network fault or a reason to send probe messages.

8. Reopen and deliver the offline card

Save, leave and reopen both targets, checking complete sequences, line boundaries and extra spaces. Retain corrections/uncertainty. State offline transcription only, without general address validation, domain existence or delivery testing. Preserve reference and result separately; any real address needs a new check. This sample does not certify every symbol page/host. The deliverable is a comparable example card, with unperformed sending, visiting and automatic completion excluded from the results.

Mixed-language version note, Punctuation contracts.

Checked on November 16, 2026: Apple’s Finland lookup, cross-checked against China, lists Jianlai 1.0.5, requiring iOS / iPadOS 16.0 or later. Official store information and screenshots establish the input-language, layout and appearance scope; identify installed controls. Tasks use original nonsensitive samples. Storage and text selection depend on the host editor, without assuming unpublished keyboard tools. Keep expectations separate from observations; no completed physical-device or universal input-environment test is claimed.

RFC 2606: reserved top-level domains and invalid examples.

Official Apple screenshot: personal keyboard and visible keys.