One-handed layout and font evidence
Jianlai font import: trace an authorized source file through selection and restoration
Pass a font working file with a clear source and license through the installed import control, then check selection and actual keyboard display. Deliver provenance, import response and applied observations. Downloading is not application, and no universal format, variable-axis or host-document font support is promised.
On this page
Pass a font working file with a clear source and license through the installed import control, then check selection and actual keyboard display. Deliver provenance, import response and applied observations. Downloading is not application, and no universal format, variable-axis or host-document font support is promised.
1. Retain the author source, license and filename
Choose a font whose author permits the intended personal-device use, not a file from an unexplained archive. One verifiable example is the official Google Fonts Noto Sans directory, currently listing the filename below and an OFL license. Another font requires its own license check; one example does not make every font free. Retain original download, source link and license externally and make a working copy. This task reads and imports an unmodified font, not a tutorial redistribution package or arbitrary redistribution authorization. Brackets and comma belong to the filename. Removing its extension or renaming an HTML page does not create font software.
NotoSans[wdth,wght].ttf
OFL.txt
2. Verify file identity and the existing font baseline
Externally confirm the working file is font data rather than a preview image, retaining actual size, readable font information and an optional whole-file hash from an existing tool. Filename and internal family name may differ; a displayed family name does not establish silent replacement. Record Jianlai’s current font, theme, sizes and usable ordinary-note baseline without deleting themes or drafts. A variable font does not promise every axis control. The official image establishes an import entry, not an exhaustive compatibility list. Stop if format is unverified rather than rename an extension to manufacture support, and distinguish the latest public version from the installed version.
3. Select the working copy through the real import control
Find the actual font area and Import font file control in the installed keyboard settings, identify it and use the real system or provider picker. Select only the verified working copy and record path and response. Without the control, record version and stopping point rather than tap screenshot coordinates. A public image grounds scope, not an identical provider on every device. If selection is disallowed or import fails, retain the file and message. Do not equate failure with a void license, install unknown profiles or grant unrelated permissions to force success. Selection, import response and availability in the font list remain separate checks.
4. Check selectability before importing again
After a confirmed response, inspect the actual input-method font list for an item corresponding to the external font information, then select through the real flow. A family-only label should be recorded with provenance, not required to repeat a long filename. If absent, inspect feedback and page identity rather than import ten times hoping for refresh. Existing or same-named families complicate identification, so row count alone is insufficient. Record actual behavior without assuming replacement or deduplication rules. After applying selection, return to the ordinary note and summon Jianlai again, distinguishing a name in preview from the extension’s actual state.
5. Check keyboard and document with one fixed sample
Use the fixed card below in the same host, holding theme and sizes constant, and inspect keycaps, actual candidates and committed text separately. The official image applies font settings to keys, candidates and the encoding area, with missing-character fallback. It does not promise a matching rich-text font in every host document. Record unchanged glyphs as scope or coverage evidence rather than immediate import failure, and do not identify the rendering family from resemblance alone. Chinese, Latin and digits provide observation targets, but absent candidate types are not applicable. Document checking concerns correct commitment, not a claim that attractive outlines improve speed or accuracy.
雨 A32 09
6. Identify the scope of restoring the default font
After retaining import and display results, use an actual Restore default font control if desired, identifying it as font-scoped rather than an app-wide reset. Restoration does not promise deleting the font file, clearing themes or undoing an external download. Return to the same note and inspect keys/candidates and readable original text. Today’s default may differ from the previous custom family, so label default fallback separately from restoring an original value. An unperformed step stays blank; one tap does not restore all settings. Keep the working file, license and draft as provenance for this import.
7. Diagnose file, selection and coverage separately
For failure before selection, inspect actual type and provider. For feedback without a selectable item, inspect list and family identity. If only Chinese or a few characters appear unchanged, investigate coverage first. Changing file, size and theme together cannot isolate a cause, and unexposed axes or unsupported formats are not invented faults. If the former family cannot be restored, use a confirmed default as a labelled substitute rather than uninstalling and clearing data. A problem description needs public source, actual version, filename and a nonprivate card, not a copied personal font library. Unperformed file or device checks stay unverified; tool reports and app responses are separate.
8. Deliver provenance, import and display evidence
Retain source link, license, original/working-file identities, import response, actual choice, fixed card and restoration state. Reopen ordinary input and check current font only before passing. A download alone passes neither import nor application. Findings concern this file and environment, not every TTF, OTF, variable font or CJK character. A new font version or device requires renewed license, format and minimal-sample checks; a current public image cannot supply results for an older installation. The outcome is a traceable single-file import, not system font installation, font redistribution or all-host typography certification.
Related guides and sources
Font and size basics; Glyph and character identity.
Checked on 18 November 2026: Apple’s Finland lookup and China lookup both list Jianlai 1.0.5, requiring iOS / iPadOS 16.0 or later. The official store 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: Official Apple keyboard-settings image at full reading size; Noto Sans in the official Google Fonts repository; SIL Open Font License official text.