You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: user_guide_src/source/outgoing/localization.rst
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,9 +24,6 @@ supported language (locale)::
24
24
fr/
25
25
App.php
26
26
27
-
.. important:: Locale detection only works for web-based requests that use the IncomingRequest class.
28
-
Command-line requests will not have these features.
29
-
30
27
Configuring the Locale
31
28
======================
32
29
@@ -52,10 +49,13 @@ directory existed at the **app/Language/en-US** directory then that would be use
52
49
Locale Detection
53
50
================
54
51
55
-
There are two methods supported to detect the correct locale during the request. The first is a "set and forget"
56
-
method that will automatically perform :doc:`content negotiation </incoming/content_negotiation>` for you to
57
-
determine the correct locale to use. The second method allows you to specify a segment in your routes that
58
-
will be used to set the locale.
52
+
.. important:: Locale detection only works for web-based requests that use the IncomingRequest class.
53
+
Command-line requests will not have these features.
54
+
55
+
There are two methods supported to detect the correct locale during the request.
56
+
57
+
1. `Content Negotiation`_: The first is a "set and forget" method that will automatically perform :doc:`content negotiation </incoming/content_negotiation>` for you to determine the correct locale to use.
58
+
2. `In Routes`_: The second method allows you to specify a segment in your routes that will be used to set the locale.
59
59
60
60
Should you ever need to set the locale directly, see `Setting the Current Locale`_.
0 commit comments