Laravel Internationalization

Agent Workflow (MANDATORY)

Before ANY implementation, launch in parallel:

1. fuse-ai-pilot:explore-codebase – Check existing translation patterns
2. fuse-ai-pilot:research-expert – Verify Laravel i18n best practices via Context7
3. mcp__context7__query-docs – Check Laravel localization documentation

After implementation, run fuse-ai-pilot:sniper for validation.

Overview

Critical Rules

1. Never concatenate strings – Use :placeholder replacements
2. Always handle zero in pluralization
3. Group by feature – auth.login.title, auth.login.button
4. Extract strings early – No hardcoded text in views
5. Validate locales – Use enum or whitelist

Decision Guide

Translation task?
├── Basic string → __('key')
├── With variables → __('key', ['name' => $value])
├── Pluralization → trans_choice('key', $count)
├── In Blade → @lang('key') or {{ __('key') }}
├── Locale detection → Middleware
├── Format date/money → LocalizationService
└── Package strings → trans('package::key')

Reference Guide

Concepts (WHY & Architecture)

Templates (Complete Code)

Quick Reference

// Basic translation
__('messages.welcome')

// With replacement
__('Hello :name', ['name' => 'John'])

// Pluralization
trans_choice('messages.items', $count)

// Runtime locale
App::setLocale('fr');
App::currentLocale();  // 'fr'

Best Practices

DO

• Use :placeholder for dynamic values
• Handle zero case in pluralization
• Group keys by feature module
• Use Locale enum for type safety
• Set Carbon locale in middleware

DON’T

• Concatenate translated strings
• Hardcode text in views
• Accept any locale without validation
• Create DB-based translations (use files)