How would you handle internationalization with address component order differences?

• A. Store canonical components with locale-sensitive formatting rules and format addresses per country on display using localization data.
• B. Store final formatted strings for all locales.
• C. Ignore locale differences and use a single format.
• D. Store only postal codes and assemble address at runtime.

Answer: (A)

International address formatting relies on keeping the address data separate from how it is shown. By storing canonical components—street, locality, city, state/region, postal code, country—you have a consistent data model that works across locales. When displaying, you apply locale-aware templates that dictate the exact order, line breaks, and punctuation for that country. Localization data (like CLDR) provides these formatting rules so you can format addresses correctly for many locales without hardcoding each variant. This approach is scalable and maintainable, and it respects differences in how addresses are written around the world, including multi-line versus single-line formats and script variations. In contrast, storing final formatted strings for all locales forces you to maintain separate versions for every locale, which is hard to update and prone to drift. Ignoring locale differences and using one fixed format would produce awkward or incorrect displays in many regions. Storing only postal codes leaves out essential components needed to identify and validate an address.