Why do only a few characters in my multilingual brand name look different?

Identify which character changes

Compare the approved spelling with the rendered word at a readable size. Record accents, script, punctuation and numerals exactly. A missing glyph, a wrong character and a different shaping behavior are different problems. Do not replace an accented character with an unaccented one simply to make an unsuitable font look consistent.

MDN explains that font selection occurs per character when a font lacks the needed glyph. Consequently, the first font appearing in a CSS family list does not prove that it drew every letter. Ask your developer or designer to inspect the actual rendered fonts and the supported character set.

Separate the text from its appearance. In a fictional approved name “Míra 星织,” first compare the actual copied text with the approved characters. If it becomes “Mira 星织” or replacement symbols, investigate the text source or encoding round trip before changing fonts. If the copied spelling is correct but í or the Chinese portion has a different weight, inspect the fonts actually used for those rendered characters. A CSS declaration naming one family describes the request, not proof that it drew them all.

Build a script-specific specimen

Use examples from your actual authorized brand, not a generic Latin alphabet that happens to render correctly. For scripts requiring shaping, include the complete name rather than isolated letters alone.

Resolve the typography boundary

For a fictional bilingual studio, preserve the intended Latin and Chinese names as two approved components if one family cannot serve both appropriately. Match their hierarchy deliberately instead of accepting accidental fallback. Confirm spacing, visual weight and reading order with a reader of the language. Keep a fixed approved wordmark asset separate from normal editable page text when their production needs differ.

Record a small comparison for that full fictional name: approved text, requested family/style/weight, font-file version, actual rendered family or families, browser/OS and the visible mismatch. Keep the initial and fully loaded states separate. A downloaded Latin subset can still omit required Chinese characters; a matching family name alone does not establish coverage. If a deliberate two-family design is chosen, approve both components and the complete reading order rather than hiding an accidental substitution.

MDN describes fallback per character and the influence of available styles. That supports the diagnostic possibility, not a finding that a particular named font is defective. This article has not installed or tested any font or browser specimen. Keep the approved spelling and character handoff with the checked output so a later export cannot silently remove the accent.

Test the final environment

Inspect the live header after fonts load and the fallback state when they do not. Check the delivered export as well; a correct design editor does not guarantee the browser or supplier received the same typography. CartVisual does not certify glyph coverage or deploy your web fonts. Record the exact text, font versions, supported scripts and reviewed outputs with the brand handoff.