What is included in the proper localization and translation workflow?

• A. Internationalization preparation, translation, cultural and linguistic review, QA testing, and UI/regression checks before release.
• B. Translate content in a single language only.
• C. Skip cultural and linguistic review to save time.
• D. Use machine translation exclusively, ignoring localization standards.

Answer: (A)

Localization and translation require a full workflow that prepares content for multiple markets, not just converting words. The best option includes internationalization preparation, translation, cultural and linguistic review, QA testing, and UI/regression checks before release. Internationalization lays the groundwork so strings, UI, and code can adapt to different languages and locales. Translation produces the actual target-language content. Cultural and linguistic review checks for tone, idioms, date formats, and cultural appropriateness to ensure the product feels natural to users. QA testing verifies linguistic accuracy along with functional behavior, while UI/regression checks confirm that the translated UI fits in screens and that features haven’t broken due to text expansion or other changes. Together, these steps ensure both accuracy and usability across locales.

Translating into just one language misses localization; skipping cultural and linguistic review risks miscommunication or cultural missteps; relying solely on machine translation ignores localization standards and quality controls.