Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commitaee8f75

Browse files
committed
minor#17827 Fix translation refs (fabpot)
This PR was squashed before being merged into the 5.4 branch.Discussion----------Fix translation refs<!--If your pull request fixes a BUG, use the oldest maintained branch that containsthe bug (seehttps://symfony.com/releases for the list of maintained branches).If your pull request documents a NEW FEATURE, use the same Symfony branch wherethe feature was introduced (and `6.x` for features of unreleased versions).-->Commits-------35313fe Fix broken links04bd7c9 Fix markup817e4e7 Fix translation refs
2 parents428e130 +35313fe commitaee8f75

File tree

3 files changed

+10
-11
lines changed

3 files changed

+10
-11
lines changed

‎reference/dic_tags.rst‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -642,7 +642,7 @@ register it as a service, then tag it with ``kernel.fragment_renderer``.
642642
kernel.locale_aware
643643
-------------------
644644

645-
**Purpose**: To access and use the current:doc:`locale</translation/locale>`
645+
**Purpose**: To access and use the current:ref:`locale<translation-locale>`
646646

647647
Setting and retrieving the locale can be done via configuration or using
648648
container parameters, listeners, route parameters or the current request.

‎routing.rst‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2267,7 +2267,7 @@ Localized Routes (i18n)
22672267
-----------------------
22682268

22692269
If your application is translated into multiple languages, each route can define
2270-
a different URL per each:doc:`translation locale</translation/locale>`. This
2270+
a different URL per each:ref:`translation locale<translation-locale>`. This
22712271
avoids the need for duplicating routes, which also reduces the potential bugs:
22722272

22732273
..configuration-block::

‎translation.rst‎

Lines changed: 8 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ The translation process has several steps:
4242
#.:ref:`Create translation resources/files<translation-resources>`
4343
for each supported locale that translate each message in the application;
4444

45-
#. Determine,:doc:`set and manage the user's locale</translation/locale>`
45+
#. Determine,:ref:`set and manage the user's locale<translation-locale>`
4646
for the request and optionally
4747
:ref:`on the user's entire session<locale-sticky-session>`.
4848

@@ -410,9 +410,9 @@ You can also specify the message domain and pass some additional variables:
410410
411411
..caution::
412412

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.
416416

417417
Forcing the Translator Locale
418418
-----------------------------
@@ -568,9 +568,8 @@ if you're generating translations with specialized programs or teams.
568568
..note::
569569

570570
You can also store translations in a database; it can be handled by
571-
Doctrine through the `Translatable Extension`_ or the `Translatable
572-
Behavior`_ (PHP 5.4+). For more information, see the documentation for
573-
these libraries.
571+
Doctrine through the `Translatable Extension`_ or the `Translatable Behavior`_
572+
(PHP 5.4+). For more information, see the documentation for these libraries.
574573

575574
For any other storage, you need to provide a custom class implementing the
576575
:class:`Symfony\\Component\\Translation\\Loader\\LoaderInterface`
@@ -699,8 +698,8 @@ configure the ``providers`` option:
699698
..tip::
700699

701700
If you use Lokalise as a provider and a locale format following the `ISO
702-
639-1`_ (e.g. "en" or "fr"), you have to set the `Custom Language Name
703-
setting`_in Lokalise for each of your locales, in order to override the
701+
639-1`_ (e.g. "en" or "fr"), you have to set the `Custom Language Name setting`_
702+
in Lokalise for each of your locales, in order to override the
704703
default value (which follow the `ISO 639-1`_ succeeded by a sub-code in
705704
capital letters that specifies the national variety (e.g. "GB" or "US"
706705
according to `ISO 3166-1 alpha-2`_)).

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp