I noticed that your German translations are not really complete and ready. Some strings are translated (like HR = Puls, or Power = Leistung), but most aren’t and those which are translated, could be tweaked a little bit.
Many software developers - especially those with a community of devoted users - make their translation strings publicly available and allow users to translate them for them (Facebook being one example). I am a Product Manager in SaaS myself, and have always preferred relying on native speakers within the company - or customers if possible.
So, why not make your translation strings publicly available and let the community do the (better) job for you? Just highlighted some of the issues in red (the green ones are ok), but there is more non-translated text of course within the app of course:
Sounds like a great idea. I just found recently a review with legal translation services Reviews of the Best Legal Translation Services | IsAccurate and in the description it was written that many of them do software localization. I understand that this option could suit us? The German language is included in the list of main languages, I think there should not be a problem with this.
Smartling is SO MUCH BETTER than spreadsheets. Please get a demo and look into community translations. For example, you can assign one email address to be the reviewer, but then have a team of volunteer translators. If you have a language where you need to hire a translator (in my case it was Korean), you can set the flow that Smartling translates and reviews that language.
I had a situation where we had many inside people with opinions, but no time to translate. This way they could just review words or phrases.
The other fantastic thing about Smartling is you can share the database across product lines. I thought iOS and Android would have the same database, but we only had a 60% over lap. Okay nice we didn’t have to translate that 60% again but… yeah we wanted to look at the 40% that didn’t match with the design team!
What I loved about Smartling was the db was always there, ready for an API call. So even if two words were out for translation, it wasn’t like the entire spreadsheet was checkout out and blocking release.
You can character limit “log in” so your German doesn’t overflow… you can search the DB for a specific word like “standing” and see if the context is correct, etc.
No, I didn’t work for Smartling, it just made 6 product lines, 14 languages, and 4 white label product releases of the stack possible.
Not to worry! We have a third-party service building and reviewing all of our language features within TrainerRoad. Thanks for your patience while we get it built!
