The font swaps mid-word the moment Vietnamese diacritics show up
Vietnamese stacks diacritics on top of vowels and uses the đ character. Not every font a designer picked for an English deck ships those glyphs. When a glyph is missing, nothing errors — the renderer silently falls back to whatever system font does have it, mid-string. The result reads as two different typefaces stitched into one headline, and it usually only shows up once real Vietnamese copy is typed into the template, which tends to be the day before launch.
Some fonts hold up under this: Be Vietnam Pro, Inter, Fraunces, Noto Sans and Manrope all render Vietnamese diacritics and đ cleanly across their common weights. Some common English-brand picks don't — Sora, Figtree and Bodoni Moda are missing part of the glyph set, so Vietnamese copy set in them will fall back mid-word without warning.
- Check every weight and style actually used, not just regular — a bold or italic cut can drop support even when regular has it
- Paste real Vietnamese copy with diacritics into the live template; lorem ipsum won't reveal a fallback
- If the brand font fails, pick a fallback from the working list above instead of letting the browser choose one
The English-only version reads over the head of the person who signs off
Vietnam ranks 64th, according to English First's global ranking of English proficiency, with an average score of 500 — the moderate band, roughly CEFR B1 to B2. That average skews young: it's pulled up by students currently in school, not by the business owners and store managers who are the actual audience for trade or B2B creative.
The practical effect is that copy which reads as clean, idiomatic English to the person who wrote it can read as dense or ambiguous to the reader on the other end. It shows up hardest in anything transactional — pricing, order terms, a WhatsApp or Zalo script — where a missed word changes what someone thinks they agreed to, not just how polished the brand sounds.
- Assume the reader sits below the national average, not at it, for anything aimed at owners over 40
- Have a native Vietnamese speaker check transactional copy — price, terms, delivery — even if the rest stays in English
- Keep the Vietnamese version's sentences short regardless of how the English original reads; don't translate sentence-for-sentence
Subtitles built for English line length spill out of the safe area
Vietnamese runs longer than English for the same sentence, and each line needs more vertical room because diacritics stack above and below the base letter. A subtitle template built against English line counts and line height will either overflow the safe area or force the type down to a size that's unreadable on a phone.
The fix is a template change, not a font-size fix at render time. Vietnamese subtitle blocks need a taller line height — 1.15 or more — and a shorter character count per line than the English original, which usually means re-breaking the lines rather than retyping the translation into the same boxes.
- Rebuild the subtitle template for Vietnamese with its own line-height and character limit — don't reuse the English box
- Preview on an actual phone screen, not a desktop timeline, before calling a cut final
- Expect line breaks to fall in different places than the English cut; word-for-word substitution rarely fits
Run all three checks before an asset ships, not after it's flagged
Each of these failures is invisible in the English source file. The font looks fine until Vietnamese text is actually typed into it. The copy looks fine until it's read by the actual buyer, not the marketing team. The subtitle looks fine on a desktop preview until it plays back on the phone most people will actually watch it on. That's why they all survive an internal review and ship broken.
If a team is already producing short-form video and creative at volume for more than one market, this belongs in the production pipeline as a standing check on every asset — not a one-time localization pass done once at the start of a project and never revisited.
- Font check happens at the template stage, before any Vietnamese copy is written
- Reading-level check happens on transactional copy specifically, not the whole deck
- Subtitle check happens on a phone screen, on the final cut, not a desktop preview

