You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Also, since your documentation recommends to use XLF, I think the script should generate the files in XLF too. Or change the documentation to mention that the default should be YAML/YML (I personally prefer YAML/YML). This would make everything consistent.
The text was updated successfully, but these errors were encountered:
@GaryPEGEOT in #27935 we made XLF the default format ... but here another bug has been reported too: the command generates a .yml file which Symfony doesn't load because it only loads .yaml
…EGEOT)
This PR was squashed before being merged into the 3.4 branch (closes#30498).
Discussion
----------
[translation] Update defaut format from yml to yaml
| Q | A
| ------------- | ---
| Branch? | 3.4
| Bug fix? | yes
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes <!-- please add some, will be required by reviewers -->
| Fixed tickets | #30443
| License | MIT
| Doc PR |
As stated in #30443 , command `php bin/console translation:update --dump-messages --force fr` will by default output the translation to yml format, which is not supported by Symfony
Commits
-------
ba42030 [translation] Update defaut format from yml to yaml
Hi guys,
very small bug but that took me 4 hours to find the fix. When generating the files using :
php bin/console translation:update --dump-messages --force fr
It generates the files with the extension "yml" by default.
According to : https://symfony.com/doc/current/translation.html#translation-resource-file-names-and-locations, the translation component only recognizes files with the extension "yaml".
I think this could be fixed quite easily.
Also, since your documentation recommends to use XLF, I think the script should generate the files in XLF too. Or change the documentation to mention that the default should be YAML/YML (I personally prefer YAML/YML). This would make everything consistent.
The text was updated successfully, but these errors were encountered: