Internasionalisasi (i18n)

Internationalization (i18n) is the process of designing and developing your components and applications so they can be easily adapted to different languages, regional differences, and technical requirements of a target country, region, or culture.

Think of it as preparing your product for the world! It's not just about translation, but about making sure your UI works everywhere.

A locale is a set of parameters that defines the user's language, country, and any special variant preferences that should be used to present information.

• en-US: English (United States)
• fr-CA: French (Canada)
• es-MX: Spanish (Mexico)

These codes help your system know how to format things correctly.

Instead of hardcoding text directly into your components, you use translation keys. These keys are like placeholders.

For example, instead of "Hello", you might use a key like "greeting.hello". Your application then looks up the actual translated text for that key based on the user's locale.

Here's a conceptual example of how translation keys work. The getTranslatedString function would fetch the correct text based on the locale from a translation file.

Dates and times are presented differently around the world. For example, "03/04/2023" means March 4th in the US but April 3rd in many other countries.

Your design system components should use locale-aware formatting utilities to display dates and times correctly for the user's region.

Number formats also vary. The decimal separator can be a dot (.) or a comma (,).

• US: 1,234.56
• Germany: 1.234,56

Currencies need their symbol and correct placement (e.g., $100.00 vs. 100,00 €).

Most languages read from Left-to-Right (LTR). However, languages like Arabic, Hebrew, and Farsi read from Right-to-Left (RTL).

For RTL languages, the entire layout of your components needs to be mirrored. This includes text alignment, icon placement, and the flow of elements.

Sometimes, images, icons, or even videos need to change based on the user's culture or region.

A picture that resonates well in one country might be confusing or even offensive in another. Your design system should support managing and delivering locale-specific assets.

A design system is key for good i18n because it provides:

• Centralized Translations: All strings managed in one place.
• Adaptable Components: Components designed to handle varying text lengths and RTL layouts.
• Consistent Formatting: Standardized date, time, and number formatting.

This ensures a consistent global experience.

We've explored Internationalization (i18n), understanding that it's more than just translation.

• We learned about locales and how they define regional preferences.
• We saw how to use translation keys for dynamic text.
• We discussed adapting dates, numbers, currencies, and layouts (RTL).
• And finally, how a design system provides a powerful foundation for building globally-ready components.

Keep these principles in mind for truly global products!