LocQA — Localization Overflow & Coverage Scanner


Includes a demo menu in six languages with one deliberate bug for each kind of ... WORKS WITH ... Any build target. ... Reads your prefabs, scenes and string files and never modifies them.


by YudiGamesStudio


Price History +

Find text that won't fit, glyphs your fonts lack, and broken translations in every language, in the editor or in CI.

FEATURES
• Nine checks: LOC001 overflow, LOC002 missing translation, LOC003 missing glyphs, LOC004 placeholder mismatch, LOC005 hard-coded text, LOC006 pseudo-localization reserve, LOC007 truncated text, LOC008 unknown key, LOC009 text that can't be measured
• Measures TextMesh Pro (its own layout engine) and legacy uGUI Text (Unity's TextGenerator) at the profile's reference resolution, in throw-away copies of prefabs and scenes
• String sources: CSV and TSV (column-mapping wizard), flat JSON per language, Unity Localization string tables
• Key bindings: the LocQAKey component, Unity Localization's LocalizeStringEvent, or a GameObject naming convention
• Command line: -executeMethod YudiGamesStudio.LocQA.Editor.LocQACommandLine.Run; exit codes 0 (pass), 1 (findings), 2 (scan couldn't run)
• Reports: HTML, JSON (with a JSON schema), CSV and JUnit XML
• Incremental cache in Library/, invalidated when an asset, its dependencies, your strings or the profile change
• Extension API: ILocCheck for custom checks, ILocQAExtension for other string sources
• Editor-only assemblies, plus one runtime component (LocQAKey) that stores a key and does nothing at runtime

SUPPORTED OS
• Unity Editor on Windows (tested). macOS and Linux Editors are not tested.

DOCUMENTATION
• https://yudigamesstudio.github.io/locqa/LocQA-Manual.pdf

Translated text breaks UI in ways you usually only see on a tester's phone, in a language you don't read. LocQA measures every localized string against the actual text component it will appear in, with your fonts, font sizes and layout settings. It then shows you exactly which strings won't fit, which characters your fonts can't draw, and which translations are empty or broken.

KEY FEATURES
• Overflow detection per language, measured with TextMesh Pro's own layout engine
• Missing-glyph detection, to catch empty boxes before a language ships
• Empty translations and mismatched placeholders ({0}, {name}, rich-text tags)
• Hard-coded text in scenes and prefabs that was never localized
• Pseudo-localization check: lengthens your source text to find overflow before translations exist
• One click jumps to the failing object, with a preview of the overflowing text
• Reads strings from Unity Localization string tables, JSON files, or CSV/TSV (with a column-mapping wizard)
• Command-line mode for CI, with exit codes and HTML, JSON, CSV and JUnit reports
• Incremental scans: 500,000 strings and 10,000 text components across 2,000 prefabs scan in under a minute, and an unchanged project re-scans in seconds (measured on a laptop with an i7-11370H and 16 GB RAM)
• Extend it with your own checks and string sources through a small C# interface

Using another localization system? If it can export to CSV, TSV or JSON, point LocQA at the exported file.

Includes a demo menu in six languages with one deliberate bug for each kind of problem LocQA finds.

WORKS WITH
• Unity 2022.3 LTS and Unity 6
• Built-in Render Pipeline, URP and HDRP
• TextMesh Pro and legacy uGUI Text
• Unity Localization (optional: used only if your project already has it; LocQA never installs packages)
• Any build target. LocQA is editor-only and adds nothing to your builds except an optional marker component that has no runtime behavior. Tested in the Unity Editor on Windows.

REQUIREMENTS
• TextMesh Pro (com.unity.textmeshpro on 2022.3; built into com.unity.ugui on Unity 6)
• For the demo, import TMP Essential Resources

DATA HANDLING
• Runs entirely in the editor. No network calls, no analytics.
• Reads your prefabs, scenes and string files and never modifies them. Writes only its own settings, its cache and the reports you export.

KNOWN LIMITATIONS
• UI Toolkit text isn't scanned yet.
• Text is measured at the profile's reference resolution. Create one profile for each resolution you care about.
• Text that your scripts set at runtime is checked only when its component is bound to a localization key.
• Text inside layout groups where sibling sizes depend on each other is measured approximately.
• Missing glyphs can't be checked for font assets that fall back to operating-system fonts.
• LocQA doesn't add shaping for Arabic or similar scripts; it measures text exactly as TextMesh Pro renders it.

DOCUMENTATION & SUPPORT
• Offline manual included (Documentation/Manual.pdf)
• Online: https://yudigamesstudio.github.io/locqa/
• Support: yudigamesstudio@gmail.com, replies within 48 hours

THIRD-PARTY NOTICES
• This package contains no third-party components.