Contributed by Mathieu Santostefano in #38475.
The process of translating Symfony applications requires extracting all translatable contents from templates and code. This task is boring and error-prone; that’s why Symfony provides a translation:update command to extract contents and update catalogs automatically. This works great, unless your application uses external translation services with their own local or SaaS-based translation tools. Then you need to send them the translation catalogs from time to time to translate the new contents and then merge the returned catalog back into your application. In Symfony 5.3 we’ve improved this workflow thanks to the integration of external translation providers. You can now upload/download translations to services like Crowdin, Loco, Lokalise and PoEditor and merge the new translations automatically into your application. Let’s imagine that you hire a translation company that uses Crowdin to share their work with you. First, configure the access to this provider: 1 2 3 4 5 6 7 8# config/packages/translation.yaml framework: translator: providers: crowdin: dsn: 'crowdin://PROJECT_ID:API_TOKEN@ORGANIZATION_DOMAIN.default' domains: ['messages'] locales: ['en', 'ja']
Now you can upload the current application translations with this command: 1 2 3 4 5 6 7 8# upload all translations for all locales $ php bin/console translation:push crowdin --force
or upload translations only for some locale(s)
$ php bin/console translation:push crowdin --locales ja
or just upload the translations of a particular domain
$ php bin/console translation:push crowdin --domain admin
Similarly, you can download the translations from the external service and let Symfony merge them automatically with the existing translations: 1 2 3 4 5 6# download all translations for all locales $ php bin/console translation:pull crowdin --force
download all translations for 'ja' locale and add the new
translations into the existing file
$ php bin/console translation:pull crowdin --locales ja
Both commands define more flags and options. Run them with the --help option to learn about those options.
Sponsor the Symfony project.
http://feedproxy.google.com/~r/symfony/blog/~3/t9dIHT2SYpw/new-in-symfony-5-3-translation-providers
Zaloguj się, aby dodać komentarz
Inne posty w tej grupie

This week, Symfony released the stable version of Symfony 7.3, which includes lots of amazing new features. We also published the maintenance versions 6.4.22 and 7.2.7.
Symfony development highlights

This is the second part of the blog post showcasing the main DX (developer experience) features introduced in Symfony 7.3. Read the first part of this blog post.
Verify URI Signatures… https://symfon

Symfony 6.4.22 has just been released. Read the Symfony upgrade guide to learn more about upgrading Symfony and use the SymfonyInsight upgrade reports to detect the code you will need to change in you

Symfony 7.2.7 has just been released. Read the Symfony upgrade guide to learn more about upgrading Symfony and use the SymfonyInsight upgrade reports to detect the code you will need to change in your

Symfony 7.3.0 has just been released. Check the New in Symfony 7.3 posts on this blog to learn about the main features of this new stable release; or check the first beta release announcement to get t

Symfony 7.3.0 has been released. As for any other Symfony release, our backward compatibility promise applies and this means that you should be able to upgrade easily to 7.3 without changing anything

Symfony 7.3 includes many small improvements aimed at making developers' lives easier and more productive. This blog post highlights some of the most useful DX (Developer Experience) features added in