WARNING: You are browsing the documentation for Symfony 4.0 which is not maintained anymore. Consider upgrading your projects to Symfony 4.2.

You are browsing the Symfony 4 documentation, which changes significantly from Symfony 3.x. If your app doesn't use Symfony 4 yet, browse the Symfony 3.4 documentation.

How to Find Errors in Translation Files

4.0 version

Maintained

3.4 4.2 current 4.3 master

Unmaintained

2.7 2.8 3.2 3.3 4.1

How to Find Errors in Translation Files¶

Symfony processes all the application translation files as part of the process that compiles the application code before executing it. If there's an error in any translation file, you'll see an error message explaining the problem.

If you prefer, you can also validate the contents of any YAML and XLIFF translation file using the lint:yaml and lint:xliff commands:

# lint a single file
$ ./bin/console lint:yaml translations/messages.en.yaml
$ ./bin/console lint:xliff translations/messages.en.xlf

# lint a whole directory
$ ./bin/console lint:yaml translations
$ ./bin/console lint:xliff translations

The linter results can be exported to JSON using the --format option:

$ ./bin/console lint:yaml translations/ --format=json
$ ./bin/console lint:xliff translations/ --format=json

This work, including the code samples, is licensed under a Creative Commons BY-SA 3.0 license.