Why placeholders break applications
An application may inject currency names, counts or customer details at runtime. If a translation changes the variable name, that substitution can fail. A translation can be linguistically correct and technically unusable.
Check before publishing
LangKit compares source and target placeholders and reports malformed or missing tokens. The checker runs without spending translation credits. Severe placeholder mismatches block approval.
Keep the source exact
For example, {CURRENCY_NAME} must remain {CURRENCY_NAME}, not {CURRENCY_NAM}. Translate the surrounding sentence but keep code-level identifiers unchanged. Complex ICU expressions still need dedicated format-aware review.
Common questions
Is the checker free?
Yes, the built-in static placeholder checks do not call a paid provider.
Does it understand all ICU MessageFormat rules?
No. Advanced ICU and plural-category validation remain separate concerns.
Before relying on this in production
Confirm support for your resource syntax and test exported translations in your application. Documentation describes supported workflows, not a guarantee of lossless conversion for every specialized format.