Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
zemaitis342214dWhat cms solution do you use for wiki?
heyheni2180814dmaybe a solution for your language problem is continuous localization. Where the copy text is stored in git and a ci instance translates either by human translators or machine translation your copy into the specified languages and serves them via i18n on the website.
Continuous Localization | Serge
And use www.deepl.com as translation service. (Better than google translate, pro version has an api)
Lensflare155914d@heyheni that documentation will be technical and will have domain specific terms and info.
Machine translation will suck as always.
Human translation will be just confusing and not helpful because the translators don't have the domain knowledge and context.
Just look at the 'translated' docs from Google and MS.
So I think the only way to go is for the original authors to write the stuff in the target language themselves.
NEMESISprj17513d@heyheni that will not really work in our case. As @LensFlare said: it's also too technical and a big part of the documentation is written partially English, partially native. So translating written texts non-stop is simply "mopping with an open watercrane".
All is fixed if people just write in the agreed-upon format, no need for automation there :)
chadd1723I put a lot of work into trying to explain to you muggles what I do all day in a way you can understand (it's ...
CodesNotHot8Here is a beautiful picture of everyone who cares about your opinion on which language is better.
Zyberg6Trying to learn X on wiki. Immediatelly learn that you suck at everything and need to research more about Y, Z...