sonata-project / dev-kit

Development kit of the Sonata-Project
https://master-7rqtwti-ptm4dx6rjpjko.eu-5.platformsh.site/
42 stars 42 forks source link

Translation Platform #1614

Open jordisala1991 opened 3 years ago

jordisala1991 commented 3 years ago

Continues : #98 Seems like we already talked a bit about it

Current status:

Desired situation:

How do we do it? We integrate a third party platform, in this case my proposal is https://weblate.org/en/ We have access to a platform that is open source, and have plans for open source projects. With a nice interface that not only allows translators to do the work with more information but it also catches some mistakes or missing keys, or changed source translations, etc...

Roadmap

VincentLanglet commented 3 years ago
  • [ ] Modify editorconfig and linter for xml on all projects

https://github.com/sonata-project/dev-kit/pull/1615

VincentLanglet commented 3 years ago

Will also need to modify all the origin="AdminFooBundle.en.xliff"

VincentLanglet commented 3 years ago

I fixed xliff files in

@jordisala1991 did in

TODO:

jordisala1991 commented 3 years ago

This is the full list. Before anything, we should remove the placeholders translations and leave only the good ones for each project. I leave the list here to keep updating it.

Once that step is done, we should check for the SonataAdmin, to see if they can be removed, and then do a list with all the context that need to have each project. For example, there are project with normal translations and validations (that will require dou

Also would be nice to have the dev-kit pr to get the cs-fix-xliff @VincentLanglet

Removed placeholders translations

Check for all contexts

Configure Weblate

jordisala1991 commented 3 years ago

First example on how to do a PR to remove placeholders: https://github.com/sonata-project/SonataMediaBundle/pull/2088

We need to do all bundles, a little of work if anyone wants to help @sonata-project/contributors