Something I was interested in looking into was the Microsoft Translator API. From its description,
> [...] that developers can easily integrate into their applications websites, tools, or any solution requiring multi-language support such as website localization, e-commerce, customer support, messaging applications, internal communication, and more.
I have not tried this program yet, but we could potentially use our Azure sponsorship money to consume this service and provide localization support for the website.
I'd be most curious to see how it'd handle syntax and code blocks.
Caffeinated Software Engineer
From: cncf-helm@... <cncf-helm@...> on behalf of Matt Farina via Lists.Cncf.Io <matt=mattfarina.com@...>
Sent: Monday, March 30, 2020 12:01 PM
To: cncf-helm@... <cncf-helm@...>
Cc: cncf-helm@... <cncf-helm@...>
Subject: [cncf-helm] localizing Helm docs [feedback requested]
The Helm website and docs are setup for localization / i18n. The flow of contributing translations is the same as contributing docs and code.
This has left me wondering... should Helm use some outside tooling to make the translation process easier? Is there something you're familiar with and would suggest? To seed the conversation, I was looking at https://gitlocalize.com/.
Do you have any tips or pointers? We want to make the process easier. Especially for non-devs.
- Matt Farina