# Jianlai letter coverage: check all twenty-six letters with an original twelve-word sentence

Language: en
Canonical: [Jianlai letter coverage: check all twenty-six letters with an original twelve-word sentence](<https://allluckly.cn/en/guides/jianlai-english-pangram-letter-coverage-set-frequency-original-sentence/>)
中文：[中文 HTML](<https://allluckly.cn/guides/jianlai-english-pangram-letter-coverage-set-frequency-original-sentence/>)
English: [English HTML](<https://allluckly.cn/en/guides/jianlai-english-pangram-letter-coverage-set-frequency-original-sentence/>)
Published: 2026-11-18T00:00:00+08:00
Modified: 2026-11-18T10:30:57+08:00
Author: Bison

Enter an original English practice sentence and check words, spaces, the period and case-insensitive letter coverage separately. Seeing all twenty-six letters does not pass every key position, candidate or accuracy claim. Keep the occurrence set and exact source comparison as separate results.

English translation of the [Chinese original](<https://allluckly.cn/guides/jianlai-english-pangram-letter-coverage-set-frequency-original-sentence/>), translated on 2026-11-18. Original publication dates, attribution, code and version notes are retained.

Enter an original English practice sentence and check words, spaces, the period and case-insensitive letter coverage separately. Seeing all twenty-six letters does not pass every key position, candidate or accuracy claim. Keep the occurrence set and exact source comparison as separate results.

## 1. Preserve the original target and ordinary input baseline

Preserve the original sentence below as an external target, then establish English-letter input in a new ordinary Jianlai draft. Record version, host, language and initial case state. This is an original exercise, not a quoted work or an online message. Hold theme, font and width fixed and identify actual keys. An unclear layout is evidence to record, not a reason to paste the target and call it typing. Keep the source independent of errors. Use the device’s actual route without prescribing one layout for all devices. Preserve formal documents; this separate practice is not a speed test.

## 2. Enter twelve words before pursuing a coverage score

Enter words in source order, checking Quick, fox, Ben and the later short words before the final period. Quick and Ben begin with capitals; other letters follow the lowercase source. Host capitalization is not automatically correct. Pause between words if useful, but inspect committed text when candidates or replacement occur rather than count taps. Preserve the entered fragment and locate a mismatch before making a separate corrected draft. Repeated clearing for an all-green record loses provenance. Until entry is complete, coverage is partial and unseen letters cannot be prechecked.

```
Quick fox Ben jumps past a wizard by the gray velvet quay.
```

## 3. Check length and word count under the fixed separators

The source uses one ASCII space between adjacent words: twelve words require eleven spaces and end with one English period. There are forty-six letters, totaling fifty-eight characters. This explicitly counts the listed single-code-point characters, not glyphs in every language. No trailing space or newline belongs to the target, and wrapping adds no character. Length fifty-eight can still misspell a word; twelve words can still contain a substituted word. Both are structural checks only. Record actual extra spacing before correction rather than claim an initially correct draft. Keep expected and observed columns separate: these are recomputed source values, not your input report.

## 4. Build a case-insensitive occurrence set

For coverage only, treat committed A–Z as corresponding lowercase and mark whether each a–z appears at least once. Do not alter source case in the document. The target covers all twenty-six basic Latin letters: j in jumps, x in fox, z in wizard, and q in both Quick and quay. Repeated occurrences occupy one set member; forty-six letters do not alone prove twenty-six kinds. Find a supporting word manually without an in-app statistics button. If the target covers everything but the actual draft omits a letter, fill coverage from the actual draft rather than copy the source set as a pass.

```
a b c d e f g h i j k l m n o p q r s t u v w x y z
Coverage ignores case; exact source comparison preserves it.
```

## 5. Use a word-removal control to distinguish coverage and length

In a separate external paper copy, remove the word fox and retain single-space separation, yielding a fifty-four-character control. It loses f, o and x despite retaining forty-three letters. None of those three occurs in another word, so this control also loses three kinds, but removing any three occurrences does not generally remove three kinds. This illustrates sets versus frequency without deleting the original draft or claiming a second completed Jianlai entry. Removing one occurrence need not remove a repeated kind; q has another source. The control rejects “long enough means complete coverage.” Actual typing errors still need exact comparison; appending a missing letter does not restore the original sentence.

## 6. Separate coverage, exact equality and the input route

Even with a–z present, compare case, word order, eleven spaces and final period. Reordering words can preserve coverage while breaking equality. Whole-sentence pasting may produce exact text but proves only that paste, not entry of each letter through Jianlai. One typed coverage trial also does not test every physical key because layouts, combinations and candidates can produce identical characters. Record manual entry, actual candidates and separate system editing. Leave uncertain steps unknown. An external computer can inspect an obtained plain-text copy, with tool and copy route recorded separately rather than described as in-app functionality.

## 7. Locate the mismatched word before input-state diagnosis

For a missing letter, find its intended word in the source, then inspect omission, spelling change or uncommitted text. For wrong length, inspect spaces, period and real newlines. A case-only mismatch calls for Shift and host checks before font changes; attractive glyphs do not establish characters. Correct one point, preserve draft differences and rerun relevant checks. Appending an alphabet as a patch does not pass the target. Preserve words and actions for host replacements rather than define all candidate behavior from one round. If keyboard identity is uncertain, pause and re-establish ordinary Jianlai input before a new trial.

## 8. Deliver the draft, coverage table and stated scope

Retain target, actual initial and corrected drafts and the twenty-six-member coverage table, plus words, characters, spaces, period and unperformed checks. Pass reopening only after checking retained text; a preserved document does not prove all keyboard settings persisted. Restore input state and keep this as a draft rather than an online speed score. Answer separately exact equality, coverage and actual route. Without timed repeated trials, report neither speed nor accuracy rates. A new layout, device or host needs renewed checks, not extension of this small card into certification of every key, language and candidate.

## Related guides and sources

[Mixed English and case](<https://allluckly.cn/en/guides/jianlai-mixed-chinese-english-version-note/>); [Confusable glyphs and actual characters](<https://allluckly.cn/en/guides/jianlai-confusable-latin-digit-three-line-glyph-card/>).

Checked on 18 November 2026: [Apple’s Finland lookup](<https://itunes.apple.com/lookup?id=6754281557&country=fi&entity=software&timestamp=20261118>) and [China lookup](<https://itunes.apple.com/lookup?id=6754281557&country=cn&entity=software&timestamp=20261118>) 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: [Python official ASCII letter definitions](<https://docs.python.org/3/library/string.html#string.ascii_lowercase>); [Apple custom-keyboard documentation](<https://developer.apple.com/library/archive/documentation/General/Conceptual/ExtensibilityPG/CustomKeyboard.html>).

