Internationalization (i18n): Multi-Language Angular Apps
Prepare Angular for multiple languages, including translation strategy and common pitfalls.
Professional products often need multiple languages. Planning i18n early saves a lot of time. ## What i18n includes - translated text (labels, buttons, errors) - date/time formats by locale - number and currency formatting - right-to-left support (Arabic, Urdu) ## Two common approaches ### Approach A: Angular built-in i18n Pros: - strong integration - compile-time translations Cons: - build per locale (more DevOps work) ### Approach B: Runtime translation libraries Pros: - switch language without rebuilding - easier for multi-tenant apps Cons: - you must manage translation files and loading ## Important best practice Never hardcode text in many places. Centralize translation keys. ## Example (concept) Instead of: `"Save"` use a key like: `APP.SAVE` That makes translation consistent and scalable. > Next: In your next set, we can cover advanced topics like micro-frontends, module federation, PWA offline caching, and advanced DI patterns.