Use the maker’s name to distinguish unrelated resources
Jaime Rangel Castro’s Hot / Sweet Coffee listing includes Hot Coffee Personal Use and Sweet Coffee. Its author note distinguishes the partial resource from a full version with one swash and ten ornamental elements. A separate Fonthead Design catalog entry identifies Hot Coffee by Ethan Paul Dunham. These are distinct resources; do not assume that a name match means identical lettering, features or files.
Try the underscore shortcut only in the documented resource
Castro’s note instructs users of the partial version to place an underscore after a word to access its swash, with Coffee_ as the example. Keep a plain Coffee proof beside that result, then compare both at the intended label width. Inspect the swash’s reach beneath or beyond adjacent wording before deciding how closely the next line should sit. Do not transfer this key sequence to Dunham’s unrelated font or assume it invokes the same artwork elsewhere. Yellowtail is a separate script comparison, not either Hot Coffee family.
Keep ornaments separate from the practical product line
For an original package, set one decorative phrase above the product description and quantity. Add only the ornament that helps the arrangement, leaving the small factual line independently readable. Compare the result with and without decoration at final print size, checking whether the ornament seems to belong to the word or the surrounding frame. Lora provides an independent serif comparison for the support text. The homepage Unicode text-style options can decorate copyable captions, but they do not install either family or reproduce a file-specific underscore-to-swash mapping.
Your questions, answered.
Does typing an underscore create this swash in every font?
No. The shortcut is documented for Castro’s partial Hot / Sweet Coffee resource. It should not be assumed for unrelated families with similar names.
Are Hot Coffee and Sweet Coffee simply the same filename?
Castro’s listing supplies them as separate named resources. Compare the actual files and their forms rather than inferring equivalence from the shared product listing.
Sources & background
Sources supporting this page’s explanations. Practical examples are our editorial suggestions.