How do I handle internationalization for custom error pages in Laravel 11

1. Set up language directories: Create language-specific directories inside the `resources/views/errors` directory. For example, create `en` for English and `es` for Spanish:

bash
mkdir -p resources/views/errors/{en,es}

2. Move error page templates: Move your existing error page templates (e.g., `404.blade.php`, `500.blade.php`) into the `en` directory:

bash
mv resources/views/errors/*.blade.php resources/views/errors/en/

3. Create translations: Create translated versions of the error page templates in the respective language directories. For example, create `404.blade.php` and `500.blade.php` in the `es` directory with the Spanish translations.

4. Use the `__` helper: In your error page templates, use the `__` helper function to display the localized error messages:

html
<p>{{ __('errors.404') }}</p>

5. Define translation strings: Create language-specific translation files in the `resources/lang` directory. For example, create `en/errors.php` and `es/errors.php` with the following content:

php
// resources/lang/en/errors.php
return [
    '404' => 'Oops! Page not found.',
    '500' => 'Oops! Something went wrong.',
];

php
// resources/lang/es/errors.php
return [
    '404' => 'Oops! Página no encontrada.',
    '500' => 'Oops! Algo salió mal.',
];

6. Set the app locale: In your application's entry point (e.g., `public/index.php`), set the app locale based on the user's preference or a default value:

php
app()->setLocale('en');

By following these steps, your custom error pages will be localized based on the user's preferred language or the default locale set in your application.

Remember to clear the config cache after making changes to the translation files:

bash
php artisan config:clear

This ensures that the updated translations are loaded correctly.