Connect the family to the designer’s script research
In a first-person interview, Hornus describes designing the Latin/Ethiopic Kefa at Reading and its later inclusion in macOS. He connects his Ethiopic work with manuscript research. The current Black Foundry account describes Kefa III’s slab-serif origins, large x-height and relatively narrow proportions. These are specific design references, not a claim that all editions share identical outlines or coverage. Lora is an independent text comparison here; the original foundry specimen shows Kefa III itself.
Compare dense text with a title on one proof sheet
Set a short original archive note in two columns with an “Archive Notes” heading above it. Keep column width and leading fixed while comparing the actual Kefa edition with a separately labeled reading face. Inspect line endings, paragraph density and the relationship between the headline and body rather than choosing solely from a large alphabet sample. Make a second proof at a slightly different size, changing only that variable. A compact appearance should not be mistaken for evidence that a paragraph is automatically comfortable to read.
Test weights without confusing the retail and system editions
The current Kefa III offering lists Light, Regular, Bold and Extra Bold with italics, plus variable resources. Compare Regular body text with a Bold subheading first. If using a variable file, save the selected weight value with the layout and compare it against a named static style. Confirm the actual resource installed on the working computer before sending the editable file elsewhere. A system menu entry named Kefa is not sufficient evidence that the recipient has the same Kefa III files or feature repertoire.
Proof the actual accented text and required script
Black[Foundry] documents expanded Vietnamese support, currencies, fractions, arrows and case-sensitive punctuation for Kefa III. Build a short character proof from the exact names, amounts and punctuation in your document. For an Ethiopic project, use correctly encoded wording reviewed by a knowledgeable reader and check the actual edition’s glyph repertoire; historical project scope does not guarantee every current package supplies every needed character. Export a proof and inspect it beside the editable source. Keep the edition name, weight settings and publisher terms with the project record.
Your questions, answered.
Is Kefa III automatically the same file as an older system Kefa?
No. The foundry identifies III as a later version. Compare the exact installed edition, outlines and repertoire instead of relying on the shorter menu name.
Does the design’s Ethiopic history guarantee every required language character?
No. Check the actual edition and the exact wording. Script history, language coverage and the contents of a particular font package are separate questions.
Sources & background
Sources supporting this page’s explanations. Practical examples are our editorial suggestions.