Why Do Accents Collide With Nearby Letters in My Packaging Headline Even Though the Spelling Is Correct?

Confirm the characters before changing the font

Start with the approved name as plain text. Compare it with the editable headline and verify that accents have not been removed or replaced.

Unicode permits canonically equivalent representations of many accented characters. For example, an accented e may be represented by a precomposed character or by a base e followed by a combining acute accent. These can represent the same intended spelling under canonical normalization.

The existing accented-name guide owns that textual equivalence check. This article begins when the characters are correct but their visible marks overlap another glyph or line.

Do not delete the accent, insert spaces into the name or redraw a random mark before investigating the font. Such edits may conceal the problem while changing the authorized spelling or making future text editing unreliable.

Inspect font coverage and mark positioning

OpenType defines positioning features including mark for positioning marks relative to base glyphs and mkmk for positioning marks relative to other marks. The specification also defines character composition and decomposition behavior through ccmp.

These mechanisms are relevant when a font must position combining accents, especially in sequences with multiple marks. Their presence in the specification does not prove that a particular font implements every needed lookup correctly.

Compare the same text in the intended font and an authorized reference font known to support the relevant characters. If the collision appears only with one font, investigate its glyph coverage and shaping behavior. If it appears after import into a different application, inspect the receiving application's font substitution and shaping.

A missing glyph and a poorly positioned existing glyph are different diagnoses. Inspect the actual rendered font rather than relying only on the family name selected in the style panel.

Separate accent collisions from line-spacing collisions

Examine the collision at the intended text size. An accent touching a neighboring letter on the same line may involve horizontal glyph placement or spacing. An accent touching the line above may instead involve insufficient leading or a headline frame that is too tight.

Make controlled copies changing only one relevant factor: font, line spacing or the specific typographic treatment. Do not simultaneously change the font, tracking and frame width, because that obscures the cause.

Review whether a manual spacing adjustment merely hides a broken combining-mark relationship. If the accent is attached incorrectly to its own base character, moving the whole word may not be an appropriate repair.

Keep the approved text unchanged throughout these comparisons.

Hypothetical accented packaging headline

Hypothetical illustration—not an executed font test: a fictional package uses the headline 'Café Élan' in a tight two-line composition.

Specimen A uses the current font and line spacing. The proposed concern is that the accent on É approaches the line above. Specimen B increases only the leading. Specimen C keeps the original leading but compares an authorized font with different mark positioning.

If B resolves a vertical collision while the same-line marks remain well positioned, leading is the likely intervention. If only C changes a mark's attachment to its base glyph, font rendering deserves further investigation.

No actual font, PDF or package was tested. These branches describe what observations would mean, not results already obtained.

Preserve the correct name through delivery

Retain the authoritative text, normalization policy where relevant, font version and approved rendered specimen. Check the actual exported file for accent placement and cropping.

If fixed outlines are needed, compare them against the approved live text and preserve the editable name separately. Outlines can freeze an acceptable appearance but do not repair the original font or restore searchable text.

Inspect the smallest real application and any neighboring text lines. An enlarged proof may hide collisions that become apparent after scaling or substitution.

Do not attribute every collision to Unicode normalization. Canonically equivalent strings can still encounter application- or font-specific rendering problems; the evidence must identify the actual stage.

Record your own observations

The filled rows are illustrative examples. Use the blank row for your own files and observations.

Download the editable CSV worksheet

What the references establish

• Microsoft Typography — Developing OpenType Fonts for Standard Scripts: Documents character composition, mark-to-base positioning and mark-to-mark positioning features.
• OpenType Specification Overview: Establishes the font layout mechanisms used for advanced script and glyph positioning.
• Unicode Standard Annex #15 — Unicode Normalization Forms: Defines canonical equivalence and normalization for precomposed and combining-character sequences.