Localisation testing: before release

Localisation is more than words: date formats, currency, faces in images, legal requirements. Without them the text reads foreign.

Task: Display issues appear after every multilingual release.

[Before you start, do three things]
1. Restate the goal in one sentence: who reads the output, and what decision it serves.
2. If I have not given you the following, ask me. Do not assume:
   - languages and platforms
   - test resources
   - known issues
   - release flow
3. Say how you plan to do it (at most 5 steps) and wait for my go-ahead.

[Go through each of these]
- five categories: overflow, truncation, encoding, sorting, formats
- test the longest path per language
- real devices, not emulators
- a ten-item pre-release checklist

[Process]
1. List every localisable element: text, formats, images, law
2. One rule set per market
3. Check for hard-coded strings
4. Design a verification
5. Say what should stay untranslated

[Output]
Element list, market rules, gap check, verification.

[Do not]
- Never translate only the UI strings
- Do not ignore plurals and gender
- One format never fits all markets
- Never force-translate a brand name