Match the source key set
Flatten both locale files and compare their full key paths. Block the release for missing keys or blank target values; flag extra target keys for review.
No missing keys · No empty valuesGEORGIAN LOCALIZATION QA CHECKLIST
Nine checks before your Georgian release.
A practical gate for product teams shipping a ka-GE locale. Start with deterministic JSON defects, then verify the rendered interface and native-language quality.
The free checker runs locally in your browser. No locale files are uploaded.
9release checks
4machine-checkable risk groups
1required native review
Preserve every variable
Compare placeholders as tokens, not as visible text. ICU, Mustache, printf, ${variable}, and framework-specific variables must survive with the same names and counts.
Exact placeholder parityDetect wrong-script leakage
Search human-facing Georgian strings for accidental Cyrillic characters and replacement symbols. Georgian and Cyrillic are different scripts; visual similarity can hide a bad paste.
No Cyrillic · No � charactersReview unchanged English
An identical source and target value may be a brand or technical term, but it may also be an untranslated string. Review each unchanged value deliberately.
Every unchanged value explainedExercise plural and formatted values
Render zero, one, two, and larger counts through the production i18n library. Also test dates, numbers, currencies, and list formatting with the actual Georgian locale configuration.
Production formatter paths testedProtect markup and links
Verify that HTML fragments, Markdown, deep links, product URLs, and escaped characters remain valid. Do not translate protocol, route, or identifier fragments.
Links resolve · Markup rendersTest narrow and dense UI
Check buttons, tabs, tables, errors, notifications, and mobile layouts with real Georgian copy. Expansion warnings identify where a focused visual pass is most valuable.
No clipping or hidden actionsVerify font and input support
Confirm the production font contains Georgian glyphs, fallback does not shift layout, text selection works, and search or form inputs accept Georgian text correctly.
No tofu · No fallback jumpFinish with native in-context review
Automated checks catch mechanical defects; they do not certify tone, terminology, or meaning. Review the final build with a Georgian speaker using the product in context.
Your native reviewer signs off (not included in ZERO audit)WORKED JSON FIX
A matching key can still lose its variable.
See a broken English/Georgian pair, the expected placeholder finding, and the corrected JSON.
COPYABLE RELEASE GATE
Make “ready” explicit.
Use this as the minimum definition of done in the release ticket.
[ ] Source and ka-GE keys match [ ] Variables and markup are intact [ ] No Cyrillic or encoding leakage [ ] Plurals and formats render correctly [ ] Mobile and dense UI remain usable [ ] Your native reviewer approved the build (not included in ZERO audit)
FROM CHECKLIST TO EVIDENCE
Run the mechanical checks now.
Paste source and Georgian JSON into the local-first preflight. For a prioritized review of up to 1,000 strings, the pilot audit is $29 and includes one re-check. Delivery timing is confirmed after scope review.