Adding multilingual support to a Laravel application

The core methods for Laravel applications to implement multilingual support include: setting language files, dynamic language switching, translation URL routing, and managing translation keys in Blade templates. First, organize the strings of each language in the corresponding folders (such as en, es, fr) in the /resources/lang directory, and define the translation content by returning the associative array; 2. Translate key values ​​through the \_\_() helper function call, and use App::setLocale() to combine session or routing parameters to realize language switching; 3. For translation URLs, paths can be defined for different languages ​​through prefixed routing groups, or route aliases in language files can be dynamically mapped; 4. Keep the translation keys concise in the Blade template and use Laravel's support for placeholders and plural forms to improve translation flexibility. Together, these steps create a clear structure and easy to maintain multilingual system.

Adding multilingual support to a Laravel application isn't too complicated, but it does require some planning and setup. The core idea is to make your app able to serve content in multiple languages ​​based on user preference or browser settings.

Laravel has built-in localization features that you can use right out of the box — no need for extra packages unless you want more advanced functionality.

Setting up language files

The first thing you'll want to do is organize your language strings. Laravel uses the lang directory for this. Each language gets its own folder (like en , es , fr ), and inside each folder, you create PHP files that return associated arrays of key-value pairs.

For example:

 /resources/lang/en/messages.php
/resources/lang/es/messages.php

Each file might look like this:

 // en/messages.php
Return [
    'welcome' => 'Welcome to our site!',
];

 // es/messages.php
Return [
    'welcome' => '¡ Bienvenido a nuestro sitio!',
];

You can then display these messages using the __() helper function in views or controllers:

 <h1>{{ __(&#39;messages.welcome&#39;) }}</h1>

This method keeps your strings organized and makes switching between languages ​​easier later.

Switching between languages ​​dynamically

To let users switch languages, you'll typically set a session variable or use a route parameter like /es/home . Laravel doesn't handle this automatically, so you'll need to write a bit of logic.

A common approach is to create a middleware that checks the URL prefix or a cookie/session value and sets the app locale accordingly.

Here's a basic example of how to do it via a controller or middleware:

 App::setLocale($locale); // $locale could be 'en', 'es', etc.

You can also add routes for switching the language:

 Route::get('/language/{locale}', function ($locale) {
    App::setLocale($locale);
    session(['locale' => $locale]);
    return redirect()->back();
});

And in your view, show links for available languages:

 @foreach(['en', 'es', 'fr'] as $lang)
    <a href="{{ url("/language/$lang") }}">{{ strtoupper($lang) }}</a>
@endforeach

Make sure to check the session or user preference early in the request lifecycle so the correct language loads before rendering views.

Translated URLs and routes

If you want your URLs to be translated (eg, /about becomes /sobre in Spanish), things get a little trickier. Laravel doesn't support translated route names directly, but you can define separate routes for each language.

One way to manage this is by using route groups with different prefixes:

 Route::prefix('en')->group(function () {
    Route::get('/about', [PageController::class, 'about']);
});

Route::prefix('es')->group(function () {
    Route::get('/sobre', [PageController::class, 'about']);
});

Alternatively, you can store translations of route slugs in language files and map them dynamically. But that requires more complex routing logic and possibly a database lookup if the slugs are dynamic (like blog posts).

Keep in mind: translated URLs improve SEO for each language version, but they take more maintenance.

Managing translation keys in Blade templates

When working with Blade templates, it's best to keep your translation keys short and describe. For example:

 {{ __('auth.login') }}

Avoid putting entire sentences directly in the template — it makes managing translations harder over time.

Also, if you're dealing with pluralization or placeholders, Laravel supports that too:

 __('messages.items', ['count' => $items->count()])

In your language file:

 // en/messages.php
'items' => '{0} No items found.|{1} One item found.|[2,*] :count items found.'

This helps when your app needs to display slightly different text depending on context or data.

Basically, setting up multilingual support in Laravel comes down to organizing your language files, handling locale changes, and deciding whether you need translated URLs. It's not overly complex, but it does require attention to structure and consistency.

The above is the detailed content of Adding multilingual support to a Laravel application. For more information, please follow other related articles on the PHP Chinese website!