MISSING I18N PLACEHOLDER

The key exists.
The UI still breaks.

A translated value can keep the right JSON key while silently dropping a runtime token. Compare placeholder sets for every matching key—not only the key lists.

01

MINIMAL REPRODUCTION

See the missing token.

English source

{
  "greeting": "Hello {name}",
  "save": "Save"
}

Broken Georgian target

{
  "greeting": "გამარჯობა",
  "save": "შენახვა"
}
Expected findingPLACEHOLDER_MISSING · greeting · {name}

The source value requires {name}; the target value contains no matching token.

02

CORRECTED TARGET

Restore the exact token.

{
  "greeting": "გამარჯობა, {name}",
  "save": "შენახვა"
}
  1. Extract placeholders from the source and target value for the same key.
  2. Compare token names and counts. Treat {name} and {Name} as different.
  3. Restore the source token unchanged, then render the real UI state with a test name.
  4. Re-run the check before merging the locale file.

WHAT THIS CHECK CANNOT TELL YOU

Structural safety is not translation quality.

Placeholder parity does not verify Georgian grammar, tone, terminology, cultural fit, or whether the sentence reads naturally in context. Review the rendered product with a Georgian-language reviewer.

RUN THE SAME CHECK

Test your pair locally.

Paste the two JSON objects into the free browser-only checker. Locale files stay in your browser.

Open the free JSON checker
See the sample $29 audit report

The sample shows how placeholder defects are prioritized with evidence and a repair action.

Request scope confirmation

Email only your locale pair, approximate key count, preferred deadline, and a public, non-confidential scope summary. Do not attach JSON files, credentials, customer data, or confidential information to the first message.

ZERO replies with a scope decision, agreed delivery timing, and a Scope confirmation reference. Confirmed customers receive payment instructions when checkout is available. Do not send JSON until ZERO accepts the scope. Clicking the button is not an order.