When Youdao Translate already returns text but the UI shows mojibake, tofu boxes, blank slots, rare-character boxes, or paste-out “????”, check system glyph coverage, whether the app or destination editor’s font covers that script, whether the source or export was re-encoded incorrectly, and whether any visible language/resource download in Settings is incomplete. Stuck progress, empty result panes, or photo OCR that never finds characters are “won’t translate” cases — use the document/photo failure posts, not a font wipe. Treat the download page and client UI as source of truth; do not invent official font-pack names or unpublished language-pack URLs.
Someone exported a finished PDF that looked fine in-app, then pasted into an old office build and got a wall of “????” — the destination font/encoding was the culprit. Another Android phone with only a minimal Chinese font set drew every minority-language result as boxes until a tablet with full script fonts rendered the same string cleanly. A third case had an offline pack half-downloaded, so only a subset of glyphs appeared — it felt like “missing characters,” but the resource simply wasn’t ready.
This page covers “there is a result, the display is broken.” It is not a retry guide for failed document jobs. Timeouts, blank exports, and smashed layouts belong on the document articles.
Split “bad display with a result” from “won’t translate”
Queries like “Youdao garbled,” “tofu box,” and “translation question marks” often collide with document timeouts and photo fails. Bad display: the main UI, dictionary pane, or export preview already shows a string — unreadable, missing strokes, or deformed after copy. Won’t translate: endless spinner, error, empty pane, task fails on retry.
Before changing settings, note whether the bad glyphs appear inside Youdao or only after copy/export; whether it’s whole-string mojibake or only rare characters / one language / one paragraph; and whether the timeline ties to an update or a just-finished resource download. Those three decide font work versus a different article.
Skim the FAQ for install/account notes. Don’t fold missing fonts, bad encoding, and whole-app crashes into one Clear all data.
Mojibake, tofu boxes, missing glyphs, paste “????”
Mojibake: Latin and CJK scrambled, or a wrong code page applied to the source before Youdao ever saw it — common when a webpage, legacy TXT, or mail body was already broken. Translating again “faithfully” reprints the damage. Confirm the source sentence is readable in a plain-text editor first.
Tofu boxes: each cell exists but the glyph is an empty rectangle. Almost always the active font has no outline for that code point: OS script fonts never enabled, desktop forced a Latin-only monospace, or the destination app draws CJK with a Western face. Switch to system UI defaults, preview in Notes/browser; if boxes vanish, the engine was fine.
Missing glyphs: holes in a line as if characters were eaten. Can be failed font fallback, zoom/line-height clipping, or a display resource still loading. Reset UI zoom to 100%, flip light/dark once, and rule out pure clipping.
Paste-out mojibake: clean in-app, “????” in chat or old Word. Test in order: Youdao → system Notes → target app. Only the last hop breaks → fix that app’s font or UTF-8 save. All three break → return to Youdao’s result pane and OS fonts.
OS fonts and language support: rare glyphs, scripts, locales
If a writing system was never enabled, fallback fonts won’t cover it and the result pane draws boxes for strings the engine already returned. Under Language & region or font management, enable the target script (menu names vary), let the OS fetch script fonts when offered, cold-start Youdao, and reopen the same result.
Rare characters, legacy forms, and dialect glyphs fail more on slim ROMs or managed devices. Open the same string on a second device with fuller fonts: boxes on one machine only → fix that OS, don’t reinstall Youdao first.
On desktop, a “documents” theme font that is Latin-only can poison embedded WebView fallbacks. Restore system UI fonts and retest. If you’re unsure which install you’re running, confirm the platform entry on the download page — avoid a portable folder and an installed build fighting display settings.
In-app display: zoom, themes, result-pane rendering
Extreme font scaling, accessibility huge text, or OEM “display size” tweaks sometimes clip strokes so it looks like missing characters. Restore default display size, quit third-party font skin apps, and retranslate a short control sentence.
Dark mode or high-contrast themes occasionally stack with a given client build: the same sentence is fine in light theme and hollow in dark. Lock light theme to reproduce, note the build number, and decide whether an update regression is involved.
If only dictionary-detail or only compact-result view breaks, that view’s font fallback differs — the whole lexicon isn’t necessarily corrupt. Product shape: Translate vs Dictionary. This page only asks whether visible glyphs are intact. Audio fine but glyphs broken is unrelated to TTS; you can still skim pronunciation / TTS in parallel.
Encoding: paste sources, exports, and second-hop damage
If the source was already mis-decoded before it entered Youdao (GBK opened as UTF-8, etc.), the UI shows “stable garbage” and translation can only operate on that garbage. Re-save the source with the correct encoding, or paste only a Unicode sentence you can read — tapping Translate again won’t heal encoding.
Export looks fine in Youdao but breaks in another app: try that app’s open/encoding controls with UTF-8. Table/PDF layout loss belongs on document translate failed and the document translation guide — those cover job failure and layout; this page covers whether characters are readable.
Longer copy chains mean more chances for a middle hop to re-encode. Prefer Youdao → one paste into the final target, or save UTF-8 plain text first. Dead clipboard hotkeys or stale popups are a different trail (clipboard failure), not “glyphs visible but wrong shape.”
Visible language / resource downloads: “fake” missing glyphs
Some builds expose language packs, offline packs, or display-related downloads under Settings. Half-finished, failed, or “re-download after update” states can leave the result pane rendering only a base set — rare glyphs and some scripts become boxes first. Open whatever download / language / offline entries you can actually see and confirm nothing is paused or failed.
Trust the menus on your client. This site does not invent official font-pack names, does not publish language-pack deep links that never appear in the UI, and does not claim a given resource includes a specific typeface. If Settings has no such item, return to OS fonts and encoding instead of hunting third-party “official” packs.
An offline text pack that can look up words does not guarantee every script’s glyphs are ready. Boundaries: offline translation guide and offline dictionary download; stuck downloads → offline pack download failed. Packs healthy but still boxed → OS fonts before reinstalling packs in a loop.
After updates — and when to leave this page
Interrupted major upgrades or mixed old/new resource folders can scramble font fallback in the result pane. When the timeline is “just updated,” run update failed first: confirm version, back up unsynced content before a clean reinstall, then retest the same sentence. Don’t start with Clear all data.
Empty pane, failed job, photo OCR finds no characters → document/photo failure posts, not here. Multi-file batches stuck in queue → batch translate queue. Softsub mojibake plus timeline drift → subtitle translate failed. Opening a result flash-quits → crash / won’t open.
Useful habits: confirm the source is readable in Notes before blaming Youdao; when you see boxes, compare on another device/OS font set; when paste breaks, test the chain hop by hop; after major upgrades, glance at visible download entries. More platform notes: FAQ and Guides.