Received the invitations, thanks @james! will look around and start to get comfortable with them to try and test.
I agree that working on GlotPress may offer us a very streamlined solution completely tailored to our needs, but this requires basically:
- more people able to manage it and set it up in a way it is secure
We may have time, at least we may show people a roadmap for it and show that at our pace the thing is progressing, but for this to work we need devs. And even if we have devs and time, I think security first matters. (I think the current devs have a lot on their plates, so better think that if we need GlotPress we have to launch a campaign to increase the number of people willing to roll sleeves up, before even starting to discuss about setting it up and testing it)
Crowdin vs. POEditor, I’ll say what I think after testing them.
spent five minutes in crowdin since my hands were itching.
Nothing to say on the Translation workflow, revisors here are called Proofeditors.
The encoding issue about characters is present also in the present version of translatewordpress (both.com and .org) so I do not see it as an issue since we need the strings be approved by revisors before releasing and if they are flagged as approved the system won’t bother.
The workflow is very similar (much more than translatewordpress) to a CAT tool, this makes for easy contriubution even from people who are “just translators” willing to srtart collaboration with the open source world. (if you need proof of this, just visit matecat and see the imterface, it’s just one of the most used web based, stored in cloud CAT tools but there are many and the interface is very similar and every translator is familiar with this).
That said we need to understand how it handles the workflow and how it reacts when various people are editing various locales at the same time and in big numbers.
One thing we need testing on is when new string get added to the locale, and what happens when the locales get updated and pushed to the repo. Is the merge to the repo done automathically? this I would not like… I would prefer that at repo’s level and admin action takes place to definitely merge to the core and serve updated translations.
I tried to send some strings and on the translation screen it is not marking them as pending review, since I act in that role as a translator. Have to verify if Proofreaders can filter the “to be proofreaded” strings only to work on them.
Bonus points, connects to Jira and Zendesk.
I have couple ideas about using those in the very future but it’s another branch entirely.
Overall I think this is what we need, and if we think that third party is the way to go, for now Crowdin has my vote (untill I test POEditor).