← ClaudeAtlas

unity-localizationlisted

Localize a Unity game: string tables, language switch, CJK fonts and tofu, TMP fallbacks, long text.
tipoLi5890/unity-dev-skills · ★ 2 · AI & Automation · score 75
Install: claude install-skill tipoLi5890/unity-dev-skills
# unity-localization — the asset pipeline, and the CJK part that bites > **Adding a language is easy; adding a script is not.** Latin locales mostly work by > substitution. The moment a CJK locale ships, font assets, atlas modes, Addressables and > layout all have to be right *together* — and the failure mode is a screen of empty boxes that > looks like a rendering bug rather than a missing asset. > > The failures that survive review are the quiet ones: text that renders in the **wrong region's > glyph shapes**, a **raw key** that reads as deliberate English, a button that fits Chinese and > splits in Japanese. None of them tofu. None of them fail an assertion. ## Symptom → where to look | Symptom | Go to | |---|---| | Adding languages, translating UI, from nothing | §1, then `reference/string-tables.md` | | Boxes / tofu instead of Chinese, Japanese or Korean | §2, then `reference/font-pipeline.md` §4 | | Text renders fine, but one locale shows the wrong regional glyph shapes | §1 | | Deciding how CJK fonts should be wired at all | §1 | | Building font assets from a script; a NullReferenceException with no message | `reference/font-pipeline.md` §1 | | The font worked, then went blank after a reimport | §3 | | `Failed to load sub-asset` at runtime | §3 Addressables | | Font assets modified in `git status` after every Editor or test run | §3, then `reference/font-pipeline.md` §5 | | A raw key on screen; a key that exists in one table only | §5, then `reference/string-tables.