Read the maker’s account of the joined-letter design
Anton Scholtz’s Coral account explains that users requested a cursive version of Leah. The development changed enough for him to release Coral under a separate name. He describes it as a somewhat more formal and regular design and emphasizes its letterspacing and kerning. That is a documented development story for this script, not evidence that the typeface is drawn from coral reefs or belongs to every product sharing the word.
Proof complete joins and accented names together
Set a short message with the actual recipient’s name, then compare it with a second line containing the longest words in the design. Inspect the transition between neighboring letters before adding tracking: a global spacing change can open every join when only one pair needed attention. Include accents and punctuation in the same proof so the name’s vertical extent is part of the layout decision. Yellowtail provides an independent connected-script comparison, not Coral’s original Leah resource.
Record the edition and keep the message editable
The publisher also lists Coral Pro-Black separately under the same designer. Record the full family and style name when sharing a project instead of requesting simply “Coral” and assuming all files are interchangeable. Compare the approved message at the actual output size before flattening it into artwork. Satisfy is another independent script specimen. The homepage lettering styles to copy into a message uses Unicode substitutions and does not carry Coral’s designed joins into a receiving application.
Your questions, answered.
How does the maker connect Coral with Leah?
Scholtz says Coral began with requests for a cursive Leah, then changed enough during development to receive a separate name.
Should I automatically increase letterspacing in a connected script?
No. Inspect complete words first. A global increase may break useful joins while failing to resolve the one pair that prompted the change.
Sources & background
Sources supporting this page’s explanations. Practical examples are our editorial suggestions.