Understand the main font and supporting files
The creator’s Adora Bouton listing places it in the Luxury Fine Art Typography series. It documents uppercase beginning swashes, lowercase beginning and ending forms, and ligatures. The main font contains the full glyph repertoire; the later Swashes 1 and Swashes 2 files provide another access route for software with limited feature controls. They are not heavier or lighter weights. Allura is a separately identified comparison here; use the creator’s specimen to inspect Adora Bouton itself.
Proof a name in the main file first
Set “Madison” in the main font and keep a plain duplicate. In a glyph-aware application, inspect beginning options for M and ending options for n, applying one substitution at a time. Compare the entire name after each change, checking the sweep’s distance from the next word and the margin. Add “& Oliver” only after settling the first name. Keep the ampersand separate during proofing so a long flourish can be evaluated without repeatedly changing the complete name line.
Use the supplementary files selectively
PeachCreme’s documented example changes only Madison’s initial M and final n to Swashes 1, leaving the interior letters in the main font. Swashes 2 supplies beginning lowercase forms and other alternatives. Reproduce that selective formatting in a separate trial rather than setting an entire paragraph in a swash file. Label the trial with the exact font assigned to each changed character. Reopen the editable document and inspect it again, since a missing supporting file can disrupt only part of the word.
Test an invitation name line at its real size
Place the selected name treatment above a plain date and venue line. Print both the plain and decorated versions at the intended invitation size, with the same margins and text position. Check whether either flourish crowds the supporting information or makes the two names feel uneven. Test the longest real name in the suite before extending the design to place cards. Keep ordinary text and a glyph-selection note with the source document, and consult the chosen creator storefront’s current terms for the intended use.
Your questions, answered.
Do I need Swashes 1 and 2 when my application has a glyph panel?
The creator says the main font contains all glyphs. The supplementary files provide an alternative access method, particularly for software with limited feature controls.
Should every letter use a supplementary swash font?
Use it selectively. The creator’s Madison example keeps the interior letters in the main font and changes the initial and final letters to the supporting file.
Sources & background
Sources supporting this page’s explanations. Practical examples are our editorial suggestions.