New in Symfony 2.8: Translator improvements

XLIFF is the format recommended by Symfony to create the translation files
used to internationalize your web sites and applications. Before Symfony 2.8, the
only XLIFF version supported by Symfony was 1.2, a standard which was published
back on February 2008.

Starting from Symfony 2.8, we also support XLIFF 2.0, the most recent version
of the standard and which was published on August 2014. Given the complexity of
the XLIFF standard, we only support a subset a features which allow to parse and
dump XLIFF 2.0 files.

When dumping a translation catalogue, use the new xliff_version option to set
the XLIFF version to 2.0. Otherwise, it will be dumped as XLIFF 1.2:

In Symfony 2.7 and previous versions, when you wanted to transform a translation
catalogue into some format (for example Yaml), you needed to dump the contents
into a file and read them back from that file.

In Symfony 2.8, FileDumper class includes a formatCatalogue() method
which transforms the catalogue contents into the given format and returns the
result:

In Symfony applications, translation files names and locations follow a strict
convention. If you need to load files from other locations, you may need to
create a compiler pass to inject your files into the translator service paths.

In Symfony 2.8, the translator service defines a new option called paths
which allows to define an array of paths were the component will look for
translation files: