Cover of the book Symfony 5: The Fast Track

Symfony 5: The Fast Track is the best book to learn modern Symfony development, from zero to production. +300 pages showcasing Symfony with Docker, APIs, queues & async tasks, Webpack, SPAs, etc.

  1. Home
  2. Documentation
  3. Translation
  4. How to Find Errors in Translation Files
WARNING: You are browsing the documentation for Symfony 3.4 which is not maintained anymore. Consider upgrading your projects to Symfony 5.2.

How to Find Errors in Translation Files

3.4 version
Maintained
4.4 5.1 5.2 current 5.3 dev
Unmaintained
2.7 2.8 3.2 3.3 3.4 4.0 4.1 4.2 4.3 5.0

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:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
# lint a single file
$ php bin/console lint:yaml app/Resources/translations/messages.en.yml
$ php bin/console lint:xliff app/Resources/translations/messages.en.xlf

# lint a whole directory
$ php bin/console lint:yaml app/Resources/translations
$ php bin/console lint:xliff app/Resources/translations

# lint a specific bundle
$ php bin/console lint:yaml @AppBundle
$ php bin/console lint:xliff @AppBundle

New in version 3.3: The lint:xliff command was introduced in Symfony 3.3.

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

1
2
3
# lint a single file
$ php bin/console lint:yaml app/Resources/translations --format=json
$ php bin/console lint:xliff app/Resources/translations --format=json

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