Integrate Google or Bing translator for the timeline and everywhere else
I’ve got some great news for you: our auto translation functionality just went live to the cloud with version 20.X.X.
Users will have easy access to a translated version of timeline posts in their language once the functionality has been enabled via admin section. And it even gets better: we were able to implement the feature for comments as well so that international colleagues can from now on easily follow and participate in entire discussions happening on timelines within COYO.
We decided to release the feature with DeepL as the first translation provider so that all you need to do is get a DeepL Pro API package to let your users benefit from automatic translations.
In our knowledge base, you can find an article on the feature that hopefully covers your most important questions: https://knowledgebase.coyoapp.com/de/article/automatische-%C3%BCbersetzungen-in-coyo (english version coming soon).
Finally, I’d like to encourage y’all to check out our auto translation feature intensively and let us know (via opening new suggestions!) what might be good next steps to further improve it.
Thanks for the hint, Nik. Might indeed be a handy workaround for others as well.
Concerning the different approaches tackling multilinguality that will be in our product once we released the automatic translation functionality for timeline posts, I'd again like to stress our agile and iterative approach. Once, the automatic approach has proven to be accepted / successful, I can absolutely see it rolled out further into our product. At some point in time, the current manual translation approach for content creation might then be replaced by it. Let's see... ;-)
Thank you for getting back.
IMO the iterative approach that you are suggesting is absolute understandable. Though it will be a half baked solution as you would have timeline post that could be translated but comments cannot. Blog on the other hand is completely manually by enabling the German language. So I understand where you are coming from but from a customer journey point of view looks like one hack on top of the other rather than having an end to end approach.
To circumvent this we are using the chrome inbuilt translation feature which more or less uses the same Google Translate Integration for all of Coyo (timeline, comments, blogs, wiki, forums etc.) This workaround works like a charm and German speakers in the company stopped complaining that zLife isn't multilingual.
In the meanwhile you can also suggest this workaround for your other customers who might be constantly nagging as we did.
Nevertheless we would opt for this feature once it is complete otherwise it becomes too much of a mish mash for us.
for the first iteration, we're planning to stick to texts within timeline posts only. Comments will then be one of the most likely followups.
Would you say that the possibility to translate comments is crucial for your users?
@marco: Will it be applicable for the comments on a timeline post as well?
as we want to give you the freedom to choose the provider that suits your needs best (eg focus on data protection, amount of supported languages) and as there are customers already having agreements with one of those translation providers in place, we decided to leave this choice up to you. Consequently, you would have to bear the costs of the agreement with your chosen provider.
Can you Tell something about data protection? Or do "we" have to buy premium services like DeepLPro where the data are not stored and used?
@Sven: Any update when this feature would be rolled out?
Thanks for the quick reply and the feedback! We already did some tests with Azure and DeepL - we will have another look into Google as well.
This might be an interesting topic for next year, though. At the moment we are pretty packed with work but we are aware that this would be a great feature!
Stephanie Zobel commented
I think of a solution like the one that you see at this example -> https://www.outdooractive.com/en/mountain-hike/allgaeu/from-oberstdorf-to-the-gaisalphorn/6817248/
I think they worked with google translate api. It would be nice if one could select between different languages and not just english at the coyo adminisitration backend.
Google translate seems to me the most obvious solution to create good multilangiage content but I if you can think of other good tranlastion providers they might also be ok.
@Sven: Google Translate :D.
Hey Stephanie, do you already have a translation engine in place or any preference? Google, Bing, Azure, DeepL etc?
Stephanie Zobel commented
Our company needs this feature as well!!!!!
Lea Mankel commented
Henrik Siebel commented
Thias is definitely necessary for our company group and I honestly cannot understand why it´s not built into Coyo yet! Please integrate this automatic translation feature asap!
Noah Koch commented
That would be great!
Thanks Sven, that would be awesome.
We ware already thinking about that as well. I think that would be a great addition and that feature would totally make sense for the product. I'll keep that in mind and maybe we can squeeze it in at some point.
Katharina Köhler commented
@Coyo: an indication on whether you do think about that or not would be great