Locales

Contains translation JSON files for internationalization (i18n) using next-intl.

Translation Files

Contains translation JSON files for internationalization (i18n) using next-intl.

Purpose

Stores all user-facing text in JSON format, organized by locale, enabling translation and localization.

Available Locales

The application currently supports the following locales:

en.json - English (United States) - Default locale
en-GB.json - English (United Kingdom)
es.json - Spanish (Spain)
es-US.json - Spanish (United States)
fr.json - French
zh-CN.json - Chinese (Simplified)
zh-TW.json - Chinese (Traditional, Taiwan - Mandarin)
zh-HK.json - Chinese (Traditional, Hong Kong - Cantonese)
pt.json - Portuguese
hi.json - Hindi

Translation Source

Important: All translations except English (United States) are AI-translated and have not been professionally reviewed. While efforts have been made to ensure accuracy and cultural appropriateness, these translations should be reviewed by native speakers before production use, especially for:

Legal or regulatory content
Cultural nuances and idioms
Regional terminology variations
Accessibility labels and instructions

If you identify translation issues, please submit a pull request with corrections or open an issue with suggested improvements.

Structure

Translation files follow BCP 47 language tags and use the naming pattern {locale}.json

Translation Organization

Translations are nested by feature area:

common - Shared translations (buttons, loading states, errors)
navigation - Navigation labels and links
home - Homepage content
lookup - Single address lookup interface
bulk - Bulk processing interface
systemStatus - System status page
apiTesting - API testing interface

Usage

Translations are loaded dynamically by src/i18n/request.ts and accessed via next-intl hooks in components:

useTranslations() in Client Components
getTranslations() in Server Components