@@ -42,7 +42,7 @@ The translation process has several steps:
42
42
#. :ref: `Create translation resources/files <translation-resources >`
43
43
for each supported locale that translate each message in the application;
44
44
45
- #. Determine, :doc : `set and manage the user's locale </ translation/ locale >`
45
+ #. Determine, :ref : `set and manage the user's locale <translation- locale >`
46
46
for the request and optionally
47
47
:ref: `on the user's entire session <locale-sticky-session >`.
48
48
@@ -410,9 +410,9 @@ You can also specify the message domain and pass some additional variables:
410
410
411
411
.. caution ::
412
412
413
- Using the translation tag has the same effect as the filter, but with one
414
- major difference: automatic output escaping is **not ** applied to translations
415
- using a tag.
413
+ Using the translation tag has the same effect as the filter, but with one
414
+ major difference: automatic output escaping is **not ** applied to translations
415
+ using a tag.
416
416
417
417
Forcing the Translator Locale
418
418
-----------------------------
@@ -569,9 +569,8 @@ if you're generating translations with specialized programs or teams.
569
569
.. note ::
570
570
571
571
You can also store translations in a database; it can be handled by
572
- Doctrine through the `Translatable Extension `_ or the `Translatable
573
- Behavior `_ (PHP 5.4+). For more information, see the documentation for
574
- these libraries.
572
+ Doctrine through the `Translatable Extension `_ or the `Translatable Behavior `_
573
+ (PHP 5.4+). For more information, see the documentation for these libraries.
575
574
576
575
For any other storage, you need to provide a custom class implementing the
577
576
:class: `Symfony\\ Component\\ Translation\\ Loader\\ LoaderInterface `
@@ -696,8 +695,8 @@ configure the ``providers`` option:
696
695
.. tip ::
697
696
698
697
If you use Lokalise as a provider and a locale format following the `ISO
699
- 639-1 `_ (e.g. "en" or "fr"), you have to set the `Custom Language Name
700
- setting `_ in Lokalise for each of your locales, in order to override the
698
+ 639-1 `_ (e.g. "en" or "fr"), you have to set the `Custom Language Name setting `_
699
+ in Lokalise for each of your locales, in order to override the
701
700
default value (which follow the `ISO 639-1 `_ succeeded by a sub-code in
702
701
capital letters that specifies the national variety (e.g. "GB" or "US"
703
702
according to `ISO 3166-1 alpha-2 `_)).
0 commit comments