10-Point QA Checklist for String Catalog Translations (2026)

A string catalog translator can accelerate your release cycle, but only if your QA catches the right risks.

Use this concise checklist before shipping translated builds.

Placeholder and format checks

Confirm that each translated value preserves placeholders and ordering.

Examples to verify manually:

• %@, %d, %f
• positional placeholders when required by locale
• escaped characters and line breaks

Plural and variation coverage

Review plural forms for languages that require multiple categories.

Look for:

• missing plural variants,
• unnatural singular/plural wording,
• broken variable insertion inside pluralized strings.

UI-context correctness

Without context, short strings are often ambiguous.

Check high-impact surfaces first:

• paywall CTA labels,
• destructive action confirmations,
• onboarding step headers,
• empty-state descriptions.

Terminology consistency

Decide your preferred product terms and enforce them.

For example, if one screen says "Project", avoid another screen using "Workspace" unless you explicitly want both.

Regression sweep

Before release, scan for:

• untranslated leftovers,
• suspiciously long strings,
• clipped text in compact UI.

If you use StringWise regularly, this checklist becomes part of your standard release template.

For feature details, visit the XCStrings Translator page and the XCStrings workflow guide.