# Check Jianlai fonts and sizes across key labels, candidates and document text Language: en Canonical: [Check Jianlai fonts and sizes across key labels, candidates and document text]() 中文：[中文 HTML]() English: [English HTML]() Published: 2026-11-15T00:00:00+08:00 Modified: 2026-11-15T09:50:10+08:00 Author: Bison Hold the theme fixed and use one passage to identify where font and size changes actually apply. English translation of the [Chinese original](), translated on 2026-11-15. Original publication dates, attribution, code and version notes are retained. Hold the theme fixed and use one passage to identify where font and size changes actually apply. ## 1. Fix the theme and input sample Choose a working Jianlai theme and record original font, size and Chinese layout. Prepare an ordinary note with common characters, digits, punctuation and a longer candidate. Preserve theme and document, and establish basic insertion before changing appearance. An existing failure to commit candidates needs input diagnosis, not larger text. This is a display comparison: a more pleasing appearance does not establish faster typing, more accurate vocabulary or an accessibility certification. ## 2. Identify the actual scope of font controls The public description includes font customisation, and an official iPad screenshot shows font, size and key adjustments. Inspect the installed controls and identify whether each affects labels, candidates or another area. Do not assume all size switches have the same scope. Phone and tablet organisation may differ, so fixed screenshot coordinates are unsuitable instructions. Record original values and units. If only preset choices exist, compare them rather than invent arbitrary numeric entry or a font-file import method. ## 3. Change one available font first Keep size and theme fixed and choose one actually available font. Apply it, redisplay Jianlai in the ordinary note and inspect Chinese, Latin letters, digits and punctuation, especially easily confused characters. One attractive preview line is insufficient. Characters retaining a familiar appearance may involve font coverage or the control’s scope; record the display before declaring damage. Unavailable fonts remain unavailable. No unknown installation package or system-font reconfiguration is required for this exercise. ## 4. Compare size in a separate round Save the font comparison, then change only one clearly labelled size option, keeping font, theme, language and text fixed. Choose two adjacent real values instead of beginning at an extreme and generalising from clipped labels. Redisplay the keyboard, read labels, enter the same passage and inspect candidates. Record enlarged, unchanged and crowded areas separately. Visible text size and touch-target area are different; without measurement, do not claim proportional changes in keyboard area or error rate. ## 5. Inspect labels and candidates separately Readable main labels do not establish suitable candidate text. Enter an ordinary phrase requiring selection and inspect full text, selected state and spacing, then check crowded punctuation on the digits/symbols page. For a clipped candidate, record length and size before changing vocabulary or language. Compare short and long candidates within the same passage, noting any clipped line rather than generalising from one complete label to every length. Inspect only existing areas; do not invent pagination or custom candidate-row counts. An external checklist is sufficient. Jianlai need not generate a font-coverage report or accessibility score for this comparison. ## 6. Explain document styling through the host After committing a candidate, inspect the note’s font and size separately from keyboard labels. Keyboard-theme customisation does not promise insertion of identically styled rich text into every host. Unchanged document appearance therefore does not prove that the keyboard setting failed. Host-editor styling, system display and keyboard appearance are distinct layers. Any desired document styling belongs in a separate host-app action with its own record, not automatic work attributed to Jianlai. This task checks the display changes actually observed in the keyboard. ## 7. Diagnose scope and character coverage If preview changes but the active keyboard does not, check extension identity and application. For only some unchanged characters, record character type and font. For crowding after a size change, restore the prior value as a control. Do not change background, font and layout together and claim one cause, or clear theme collections. Retain device class, version, control label and a short nonsensitive sample. Unknown coverage mechanisms remain unknown; one character does not establish incompatibility of a whole font or every device. ## 8. Restore a readable everyday configuration Restore original values or the deliberately chosen configuration, reopen the note and enter a short passage. Check labels, candidates and document text as separate layers. Deliver the font and size rounds with their conditions and actual results, including unchanged areas and unchecked characters. Acceptance specifies what changed and how to restore it. Recheck key characters after theme, layout or device changes. One passage does not certify all fonts, sizes and rich-text hosts on physical devices. ## Related tutorials and sources [Built-in themes](), [Individual space-bar styling](). Checked on November 15, 2026 against [Apple public lookup]() and the [official App Store information and screenshots]() it lists: version 1.0.5, requiring iOS / iPadOS 16.0 or later, with identity and version cross-checked against China lookup. Tasks use published capabilities; identify actual controls in your installed version. External records are acceptable. Keep expectations separate from observations; no physical-device or universal input-environment test is claimed. [Official Apple screenshot: font and size (iPad)]().