How to Find Missing or Unused Translation Messages
Warning: You are browsing the documentation for Symfony 2.x, which is no longer maintained.
Read the updated version of this page for Symfony 7.1 (the current stable version).
When maintaining an application or bundle, you may add or remove translation
messages and forget to update the message catalogues. The debug:translation
command helps you to find these missing or unused translation messages.
Thanks to the messages extractors, the command will detect the translation tag or filter usages in Twig templates:
1 2 3 4 5 6 7
{% trans %}Symfony is great{% endtrans %}
{{ 'Symfony is great'|trans }}
{{ 'Symfony is great'|transchoice(1) }}
{% transchoice 1 %}Symfony is great{% endtranschoice %}
It will also detect the following translator usages in PHP templates:
1 2 3
$view['translator']->trans("Symfony is great");
$view['translator']->transChoice('Symfony is great', 1);
Caution
The extractors are not able to inspect the messages translated outside templates which means that translator usages in form labels or inside your controllers won't be detected. Dynamic translations involving variables or expressions are not detected in templates, which means this example won't be analyzed:
1 2
{% set message = 'Symfony is great' %}
{{ message|trans }}
Suppose your application's default_locale is fr
and you have configured
en
as the fallback locale (see Translations and
Translations for how to configure these). And suppose
you've already setup some translations for the fr
locale inside an AcmeDemoBundle:
1 2 3 4 5 6 7 8 9 10 11 12
<!-- src/Acme/AcmeDemoBundle/Resources/translations/messages.fr.xliff -->
<?xml version="1.0"?>
<xliff version="1.2" xmlns="urn:oasis:names:tc:xliff:document:1.2">
<file source-language="en" datatype="plaintext" original="file.ext">
<body>
<trans-unit id="1">
<source>Symfony is great</source>
<target>J'aime Symfony</target>
</trans-unit>
</body>
</file>
</xliff>
and for the en
locale:
1 2 3 4 5 6 7 8 9 10 11 12
<!-- src/Acme/AcmeDemoBundle/Resources/translations/messages.en.xliff -->
<?xml version="1.0"?>
<xliff version="1.2" xmlns="urn:oasis:names:tc:xliff:document:1.2">
<file source-language="en" datatype="plaintext" original="file.ext">
<body>
<trans-unit id="1">
<source>Symfony is great</source>
<target>Symfony is great</target>
</trans-unit>
</body>
</file>
</xliff>
To inspect all messages in the fr
locale for the AcmeDemoBundle, run:
1 2 3 4 5 6 7
$ php app/console debug:translation fr AcmeDemoBundle
--------- ------------------ ---------------------- -------------------------------
State Id Message Preview (fr) Fallback Message Preview (en)
--------- ------------------ ---------------------- -------------------------------
unused Symfony is great J'aime Symfony Symfony is great
--------- ------------------ ---------------------- -------------------------------
It shows you a table with the result when translating the message in the fr
locale and the result when the fallback locale en
would be used. On top
of that, it will also show you when the translation is the same as the fallback
translation (this could indicate that the message was not correctly translated).
Furthermore, it indicates that the message Symfony is great
is unused
because it is translated, but you haven't used it anywhere yet.
Now, if you translate the message in one of your templates, you will get this output:
1 2 3 4 5 6 7
$ php app/console debug:translation fr AcmeDemoBundle
--------- ------------------ ---------------------- -------------------------------
State Id Message Preview (fr) Fallback Message Preview (en)
--------- ------------------ ---------------------- -------------------------------
Symfony is great J'aime Symfony Symfony is great
--------- ------------------ ---------------------- -------------------------------
The state is empty which means the message is translated in the fr
locale
and used in one or more templates.
If you delete the message Symfony is great
from your translation file
for the fr
locale and run the command, you will get:
1 2 3 4 5 6 7
$ php app/console debug:translation fr AcmeDemoBundle
--------- ------------------ ---------------------- -------------------------------
State Id Message Preview (fr) Fallback Message Preview (en)
--------- ------------------ ---------------------- -------------------------------
missing Symfony is great Symfony is great Symfony is great
--------- ------------------ ---------------------- -------------------------------
The state indicates the message is missing because it is not translated in
the fr
locale but it is still used in the template. Moreover, the message
in the fr
locale equals to the message in the en
locale. This is a
special case because the untranslated message id equals its translation in
the en
locale.
If you copy the content of the translation file in the en
locale, to the
translation file in the fr
locale and run the command, you will get:
1 2 3 4 5 6 7
$ php app/console debug:translation fr AcmeDemoBundle
---------- ------------------ ---------------------- -------------------------------
State Id Message Preview (fr) Fallback Message Preview (en)
---------- ------------------ ---------------------- -------------------------------
fallback Symfony is great Symfony is great Symfony is great
---------- ------------------ ---------------------- -------------------------------
You can see that the translations of the message are identical in the fr
and en
locales which means this message was probably copied from French
to English and maybe you forgot to translate it.
By default all domains are inspected, but it is possible to specify a single domain:
1
$ php app/console debug:translation en AcmeDemoBundle --domain=messages
When bundles have a lot of messages, it is useful to display only the unused
or only the missing messages, by using the --only-unused
or --only-missing
switches:
1 2
$ php app/console debug:translation en AcmeDemoBundle --only-unused
$ php app/console debug:translation en AcmeDemoBundle --only-missing