Now-a-days the open source tooling is actually pretty good at what it does. For example, i18Next or next-translate are a great. These tools are great utilities for detecting the browser locale, and looking up translated strings in the correct language in your front end code. "All you have to do" is get your translations in json files in your source code.
Therein lies the rub. I don't know french, so I need a translator to fill in the french strings for my JSON file, but Github is not the right place for a translator to work. In past projects, I've uploaded these files to Google Sheets. When the app gets big enough though and there's multiple features with their own strings in development in parallel, keeping the source files in sync with the sheets that the translators use becomes a headache (in fairness it's usually more of a headache for the project managers, not for myself haha).
If you've worked on a multilingual application before, I'd love to learn about how the translation system worked on that project and what it was like working with it from your perspective. The following info in each post would help provide context for the discussion: - your role - project framework/language - number of developers on the project - what tools did you use to manage the translations (if they were paid tools, please mention the price if you know it) - if you used a tool to manage the translation files, was the tool provided by a translation agency or did you bring your own translation agency and just use the software?
I still have lose sometimes too much time syncing master with upstream. Perhaps you can make a small program that just force updates the local master and switch to it, so the translator can jump to a safe initial state whenever is necessary. Remember to put a nice icon in the executable. It's incredible how easier is for most people to just click a nice icon instead of conjuring some ancient scroll in the cli.
(You must handle all the necessary rebase and conflict resolution.)