How to Work with the User's Locale
Warning: You are browsing the documentation for Symfony 4.x, which is no longer maintained.
Read the updated version of this page for Symfony 7.1 (the current stable version).
The locale of the current user is stored in the request and is accessible
via the Request
object:
1 2 3 4 5 6
use Symfony\Component\HttpFoundation\Request;
public function index(Request $request)
{
$locale = $request->getLocale();
}
To set the user's locale, you may want to create a custom event listener so that it's set before any other parts of the system (i.e. the translator) need it:
1 2 3 4 5 6 7
public function onKernelRequest(RequestEvent $event)
{
$request = $event->getRequest();
// some logic to determine the $locale
$request->setLocale($locale);
}
Note
The custom listener must be called before LocaleListener
, which
initializes the locale based on the current request. To do so, set your
listener priority to a higher value than LocaleListener
priority (which
you can obtain by running the debug:event kernel.request
command).
Read Making the Locale "Sticky" during a User's Session for more information on making the user's locale "sticky" to their session.
Note
Setting the locale using $request->setLocale()
in the controller is
too late to affect the translator. Either set the locale via a listener
(like above), the URL (see next) or call setLocale()
directly on the
translator
service.
See the How to Work with the User's Locale section below about setting the locale via routing.
The Locale and the URL
Since you can store the locale of the user in the session, it may be tempting
to use the same URL to display a resource in different languages based on
the user's locale. For example, http://www.example.com/contact
could show
content in English for one user and French for another user. Unfortunately,
this violates a fundamental rule of the Web: that a particular URL returns
the same resource regardless of the user. To further muddy the problem, which
version of the content would be indexed by search engines?
A better policy is to include the locale in the URL using the special _locale parameter:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
// src/Controller/ContactController.php
namespace App\Controller;
// ...
class ContactController extends AbstractController
{
/**
* @Route(
* "/{_locale}/contact",
* name="contact",
* requirements={
* "_locale": "en|fr|de",
* }
* )
*/
public function contact()
{
}
}
When using the special _locale
parameter in a route, the matched locale
is automatically set on the Request and can be retrieved via the
getLocale() method. In
other words, if a user visits the URI /fr/contact
, the locale fr
will
automatically be set as the locale for the current request.
You can now use the locale to create routes to other translated pages in your application.
Tip
Define the locale requirement as a container parameter to avoid hardcoding its value in all your routes.
Setting a Default Locale
What if the user's locale hasn't been determined? You can guarantee that a
locale is set on each user's request by defining a default_locale
for
the framework:
1 2 3
# config/packages/translation.yaml
framework:
default_locale: en