Merge branch '4.3' into 4.4

* 4.3: Promote usage of a single translation domain Move sidebar into a real section Removed Translation component documentation

Author: wouterj

_build/redirection_map

@@ -474,3 +474,5 @@
 /best_practices/web-assets /best_practices
 /best_practices/tests /best_practices
 /components/debug https://github.com/symfony/debug
+/components/translation https://github.com/symfony/translation
+/components/translation/usage /translation

bundles/override.rst

@@ -172,7 +172,7 @@ instead of the original ones.
 Translations
 ------------
 
-Translations are not related to bundles, but to :ref:`translation domains <using-message-domains>`.
+Translations are not related to bundles, but to translation domains.
 For this reason, you can override any bundle translation file from the main
 ``translations/`` directory, as long as the new file uses the same domain.
 

components/form.rst

@@ -55,7 +55,7 @@ support for very important features:
 The Symfony Form component relies on other libraries to solve these problems.
 Most of the time you will use Twig and the Symfony
 :doc:`HttpFoundation </components/http_foundation>`,
-:doc:`Translation </components/translation>` and :doc:`Validator </components/validator>`
+:doc:`Translation </translation>` and :doc:`Validator </components/validator>`
 components, but you can replace any of these with a different library of your choice.
 
 The following sections explain how to plug these libraries into the form