Skip to content

Audit strings before handoff and after translation

Paste a JSON or Java .properties catalog. All checks run locally in your browser.

Lints a source file for strings that are hard or impossible to translate.

Strings file

Audit findings

Paste, open, or drop a .json or .properties file to run 11 checks:

  • String concatenation in value Values like 'You have ' + count + ' items' reach the translator as fragments that cannot be reordered. Use one string with placeholders.
  • Embedded HTML Markup in a value exposes tags and attributes to translation, where they get broken or translated. Keep markup outside the string, or use the i18n library's rich-text syntax.
  • Unbalanced ICU braces ICU MessageFormat delimits arguments with braces. An unbalanced brace breaks the message at runtime.
  • Printf-style placeholder Printf placeholders (%s, %d, %@) carry no name, so the translator cannot see what they hold, and unnumbered ones cannot be reordered. Prefer named ICU placeholders.
  • Plural form in the key name Plural forms split across keys. The legacy _plural suffix holds only two forms. CLDR suffixes (_one, _few, _many, _other, as in i18next) work only when every target locale gets every category it needs.
  • Empty / whitespace-only value An empty value renders as blank UI. Usually a missed paste.
  • Leading or trailing whitespace Usually a paste artifact. Some renderers trim it and some do not.
  • Double space inside value Usually a typo. HTML collapses it; plain-text and Markdown contexts do not.
  • Ambiguous short string Values of 12 characters or fewer ('Open', 'Save', 'Home') need a context note. One English word can need a different translation as a verb, a noun, or a label, or for grammatical gender.
  • Identifier or code as value Values that look like code (camelCase, snake_case, CONSTANTS) are usually not UI text and do not belong in the catalog.
  • Long value Values over 200 characters often hold more than one message. Give each message its own key; split at paragraph breaks, never mid-sentence.

Scope

  • Validates catalog structure, keys, placeholders, ICU plural forms, balanced braces, and leading or trailing whitespace. For linguistic quality evaluation, see LQA scoring.
  • Queries Intl.PluralRules in your browser to determine the required plural categories for the selected target locale.

Related: Pseudolocalization chapter · Budget estimator (prices the round before handoff)