TechnicalCollectible prompt

Internationalization (i18n) readiness review

Find what will break when your app launches in new languages and regions.

ClaudeClaude CodeCursor

Curated by Nvoka

Nvoka wordmark logo
Nvoka wordmark logoTechnical

Internationalization (i18n) readiness review

Act as an internationalization engineer. Review this {{tech_stack}} code for readiness to launch in {{target_locales}}: {{code_to_review}} Check for hard-coded strings, sentences built by joining strings, plural handling, date, time, number, and currency formatting, how time zones are stored and displayed, text expansion in longer languages, right-to-left layouts, font and character support, sorting and search for non-Latin scripts, name, address, and phone formats, images with embedded text, and locale detection with fallbacks. Return a table with columns: issue, where it appears, locales affected, fix, and effort (small, medium, or large). Then give a phased plan: what to fix before extracting strings, what translators will need (context, screenshots, a glossary), and how to test with pseudo-localization. Ask about anything the code doesn't show, such as how dates are stored in the database.
Technicalnvoka.com/library/nvoka-i18n-readiness-reviewScan to open
Technical

Internationalization (i18n) readiness review

Find what will break when your app launches in new languages and regions.

Nvoka logo

Curated by Nvoka

ClaudeClaude CodeCursorChatGPT
Add to my library

Make it yours

Fill in the blanks and change any word. Only your copy changes, never the card.

Fill in the blanks

0 of 3 filled

Your prompt

Act as an internationalization engineer. Review this {{tech_stack}} code for readiness to launch in {{target_locales}}: {{code_to_review}} Check for hard-coded strings, sentences built by joining strings, plural handling, date, time, number, and currency formatting, how time zones are stored and displayed, text expansion in longer languages, right-to-left layouts, font and character support, sorting and search for non-Latin scripts, name, address, and phone formats, images with embedded text, and locale detection with fallbacks. Return a table with columns: issue, where it appears, locales affected, fix, and effort (small, medium, or large). Then give a phased plan: what to fix before extracting strings, what translators will need (context, screenshots, a glossary), and how to test with pseudo-localization. Ask about anything the code doesn't show, such as how dates are stored in the database.
See all