Setup translation tools and procedures

[lindenthal]

The community needs an easy way to translate the artefacts:

Asciidoctor (or DocBook) currently does not support translation of content out of the box. There’s a proposal to integrate gettext (discussion), and suggestions are welcome.

Please see the docs for forther details.

[lindenthal]

Hi @ionut-ai,
is there already a plan for the toolchain? Did you consider to use a crowd translation platform such as Crowdin?
Best
Niels

cc @ffalt @iliask75 @nkouroun

[lindenthal]

I just got feedback from Crowdin. Other than stated on their website they seem to support the AsciiDoc format. So I gave it a try:

I think this is good news (at least for me).
cc @ffalt @ionut-ai @iliask75

[iliask75]

Good news indeed

On Thu, 14 Jan 2021 at 11:19, Niels Lindenthal ***@***.***> wrote: I just got feedback from Crowdin. Other than stated on their website they seem to support the AsciiDoc format. So I gave it a try: [image: image] <https://user-images.githubusercontent.com/1019287/104577797-315a9f00-565a-11eb-81e4-2766c7433482.png> I think this is good news (at least for me). cc @ffalt <https://github.com/ffalt> @ionut-ai <https://github.com/ionut-ai> @iliask75 <https://github.com/iliask75> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#5 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFCTKLS5LSPCDVV6MYXUF63SZ3ALXANCNFSM4WBKHGRQ> .

--

[ionut-ai]

It is great to be able to access a broader community to assist in improving the translations. We have already translation teams that worked on translating the guide. What we are working on now is to ensure that we publish all of them.
In regards to the tooling and procedure, as the teams self-organized, we didn't impose a common way of working up to this point. However we do have a draft procedure and will work to publish it as soon as possible.