Translations workflow

[kimberscott]

We now offer translation capabilities via ember-intl for hard-coded text on frames (as of #221). Researchers interested in testing in a new language can follow the directions here to create a translation file. However, we need a way to maintain those files when changes are made to the underlying text to translate, e.g. when we update the troubleshooting instructions on the exp-video-config page or add a new button.

Because volunteers may complete a translation once but then not be available on an ongoing basis, we cannot assume we can simply send out requests for translations ahead of a release. We may need to e.g. create a placeholder entry along with a log of what changes need to be addressed per language, and translators can then address and remove items.

This will require scoping - the completion of this issue will entail designing/selecting a process for flagging changes in the en-us.yaml file and letting translators know what needs to be changed in other language files.

The current very makeshift workflow

If we make changes to the translation strings (changing text, adding an additional string, etc.) we make a first pass at translation using e.g. Google Translate, then check with the translators for edits:
Dutch - Isabella Saccardi i.saccardi@fsw.leidenuniv.nl
Italian - Francesca Bianco, on Slack

ManyBabies-AtHome

The ManyBabies-AtHome group is beginning to translate en-us.yaml into a variety of languages, and should be consulted on the workflow.