Separate language from presentation
Internationalization (i18n) prepares an application to support different languages and regional conventions. Localization (l10n) supplies the language and formatting for a specific locale. Avoid hardcoding user-facing strings throughout controllers and templates.
Use translation catalogs
Store messages in structured catalogs keyed by stable identifiers. A translation function can retrieve a message and interpolate named parameters. Keep placeholders consistent across languages and allow translators to reorder them.
Handle plural forms
Plural rules differ by language. Do not assume every language uses singular and plural only. Use a translation format or library that supports locale-aware plural rules and contextual messages.
Store canonical data
Store timestamps in UTC and convert them for display in the user's selected time zone. Store numeric values in canonical database types, not preformatted strings. Format dates, numbers and currencies at the presentation boundary using locale-aware APIs such as PHP's Intl extension when available.
URLs and content strategy
Choose whether language appears in the URL, domain or user preference. Make canonical and alternate-language metadata consistent. Do not automatically translate slugs in a way that changes URLs unexpectedly; maintain explicit mappings and redirects when URLs change.
Checklist
- Keep translation keys out of business logic.
- Use a catalog format with plural support.
- Preserve placeholders across translations.
- Store dates in UTC and localize display.
- Format numbers and currencies at the presentation boundary.
- Define language fallback and URL strategy.
- Verify required PHP extensions such as
intl.