Globalization: Internationalisation, Localisation, and Operations
Globalization in computing means designing, delivering, and supporting systems across countries and cultures. The exam tests the distinction between internationalisation and localisation, the technical standards that make multilingual systems possible, and the operational and legal issues of distributed work. Questions usually describe a product launch in a new market and ask what must change.
Core distinctions
- Internationalisation is designing a product so it can be adapted without engineering changes; localisation is the actual adaptation to a specific market.
- Translation converts text; transcreation reworks content so it lands culturally.
- Outsourcing moves work to a third party; offshoring moves it to another country; nearshoring keeps it in a nearby country or time zone.
Technical requirements
- Unicode, usually UTF-8, supports multilingual text; legacy single-byte encodings corrupt characters.
- Store dates and times in UTC in a standard format, then display in local time and format.
- Locale settings govern number, currency, date, address, and name formats; some scripts run right to left.
- Avoid embedding text in images and allow for text expansion in translation.
Legal and operational issues
- Data sovereignty and cross-border transfer rules may require local storage or contractual safeguards.
- Payment methods, tax rules, consumer rights, and accessibility law vary by market.
- The digital divide affects bandwidth, device capability, and connectivity assumptions.
- Follow-the-sun support and clear escalation paths help distributed teams.
Worked example
A scheduling app stores appointment times as text such as "03/04/2025 9:00 AM" in local format. Reasoning: the same string means 3 April in one market and 4 March in another, and sorting as text fails. The fix is to store timestamps in UTC in a standard machine format, attach the user's time zone, and format for display using locale settings. That design is internationalisation; the translated interface and local holiday handling are localisation.
Traps that cost marks
- Using internationalisation and localisation interchangeably.
- Assuming an English interface is sufficient for global users.
- Hard-coding currency symbols, date formats, or decimal separators.
- Confusing outsourcing with offshoring.
- Ignoring data residency rules when choosing where to host data.