Gregory's ServerMy possibly unpopular view on documentation translations is that they are more of a liability than an asset when you don't have someone whose literal job it is to ensure those translations are always up to date. If something changes and the information becomes out of date it's worse than if you (in the worst case) had to use Google Translate on the page. But it's so difficult to say no when someone's already put their time into translating so I don't know where I'm going with this
Eugen Rochko
No comments
[DATA EXPUNGED]
  
compbiobryan
@Gargron Datestamp/revision-code the translation? ("Translation of documentation as of build 12345") and make that very visible?
Jimi Viita-aho
@Gargron I have seen so many low quality and therefore unreadable translations. I once had a client project where I had to fix machine translation from English to Finnish, but I couldn’t do it. I couldn’t even guess the meaning of all sentenges, because of wrong synonyms and/or incorrect declensions. More common language pairs may be fine with machine translation, but I think blanks/outdated parts should just display English 🤔 |
