I started to document the translation process of Neos and Flow. When I was about to describe the fact that the translations are distributed across multiple projects (one per project) I had an idea…
So I created a Crowdin configuration file and uploaded “all” Neos packages’ translations into one project. This works fine and has the following advantages:
all translations are in one project
duplicate strings can thus be consistently translated
unified translation memory
unified glossary is possible
progress overview is easier
When switching to this approach, all existing translations are of course preserved.
Anything you might want to know or comment on? Something I have missed?
No, I propose to have one Neos and one Flow project instead of one for Neos (bundling Neos, Kickstarter, Media, Setup, …) and one for Flow (bundling Flow, Fluid, …). So probably even better. But we could of course have those Flow and Neos “bundles” together in one project even.
I can’t judge at the moment which impact it would have technically, but from a translator’s / community member’s point of view, it would help to have just one project (shared translation memory and such).