That's what I think. I guess that contributors on these sites just pull in
raw MT-generated translations and post them as is,
or do these sites really have human Spanish/Indonesian translators that do actual proofreading? I bet they have none.
Take an example of desdelinux case. The original article (in Spanish) reads:
```
Bueno, como es de esperarse en Gentoo, existen muchas opciones de kernel, les dejo aquí una pequeña lista para que vean mejor a lo que me refiero:
gentoo-sources: Kernel 4.12 con parches especiales para Gentoo Linux.
git-sources: Kernel directamente descargado desde el repositorio Git de Linus.
vanilla-sources: Kernel completo sin ningún tipo de parche.
```
which is translated on the site as:
```
Seperti yang diharapkan di Gentoo, ada banyak opsi kernel, saya tinggalkan daftar kecil di sini agar Anda dapat memahami dengan lebih baik apa yang saya maksud:
sumber gentoo: Kernel 4.12 dengan patch khusus untuk Gentoo Linux.
git-sumber: Kernel langsung diunduh dari gudang Linus Git.
vanilla-sumbersource: Kernel penuh tanpa patch apapun.
```
Notice that linux sources package names (gentoo-sources, git-sources, and vanilla-sources) are translated despite being proper names, which should
not be in this case.
Whereas Google Translate renders the translated passage as:
```
Seperti yang diharapkan di Gentoo, ada banyak opsi kernel, berikut adalah daftar kecilnya sehingga Anda dapat lebih memahami maksud saya:
gentoo-sources: Kernel 4.12 dengan patch khusus untuk Gentoo Linux.
git-sources: Kernel diunduh langsung dari repositori Git Linus.
vanilla-sources: Kernel lengkap tanpa patch apa pun.
```
For more natural and flowing translation, I'd like to write it instead as:
```
Seperti yang diharapkan, ada banyak pilihan kode sumber kernel di Gentoo.
Beberapa diantaranya:
gentoo-sources: Kernel versi 4.12 dengan tambalan spesifik untuk Gentoo.
git-sources: Kernel dengan potret langsung dari repositori Linus.
vanilla-sources: Rilis kernel asli tanpa tambalan apapun.
```
These intricacies above reminds me of biblical translation context. Translation
can be done in either formal equivalence (word-by-word like NASB and ESV) or dynamic equivalence (thought-by-thought as in NIV and NLT). The former seeks to
stay close to original language's wording, but may produce stiff target language
text. The latter tries to convey meaning of original language in more readable
target language text by making use of context interpretation, which if it is
done poorly, can divert actual meaning from the original.
Take an example of desdelinux case. The original article (in Spanish) reads:
``` Bueno, como es de esperarse en Gentoo, existen muchas opciones de kernel, les dejo aquí una pequeña lista para que vean mejor a lo que me refiero:
```which is translated on the site as:
``` Seperti yang diharapkan di Gentoo, ada banyak opsi kernel, saya tinggalkan daftar kecil di sini agar Anda dapat memahami dengan lebih baik apa yang saya maksud:
```Notice that linux sources package names (gentoo-sources, git-sources, and vanilla-sources) are translated despite being proper names, which should not be in this case.
Whereas Google Translate renders the translated passage as:
``` Seperti yang diharapkan di Gentoo, ada banyak opsi kernel, berikut adalah daftar kecilnya sehingga Anda dapat lebih memahami maksud saya:
```For more natural and flowing translation, I'd like to write it instead as:
``` Seperti yang diharapkan, ada banyak pilihan kode sumber kernel di Gentoo. Beberapa diantaranya:
```These intricacies above reminds me of biblical translation context. Translation can be done in either formal equivalence (word-by-word like NASB and ESV) or dynamic equivalence (thought-by-thought as in NIV and NLT). The former seeks to stay close to original language's wording, but may produce stiff target language text. The latter tries to convey meaning of original language in more readable target language text by making use of context interpretation, which if it is done poorly, can divert actual meaning from the original.
Thanks for the reply.