Timeline for We need to help non-English-speakers somehow
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 22, 2018 at 11:31 | history | edited | This_is_NOT_a_forum | CC BY-SA 4.0 |
(While we are at it.)
|
| Jul 23, 2009 at 18:25 | comment | added | Jim C | I realize that machine translations are far from perfect, but they are getting better all the time. Also most "technical" words tend to already be in English, at least as far a programming goes. As for mark up, that is definitely a issue, but I think there could be some workaround. Simply write your test, translate, then add the ML. | |
| Jul 23, 2009 at 16:25 | comment | added | John Saunders | I'm suggesting we put the "best-try English" first, followed by the foreign language. We'd use the (possibly translated) foreign language as a way to edit the English. OTOH, I was just playing with Google Translate, and it has problems with Markdown. | |
| Jul 22, 2009 at 16:41 | comment | added | Raymond Martineau | Google Translate does most of the translation work, but as you mentioned, it's not always accurate. As such, relying on the tool may cause translation errors, and it's more severe when you rely on a technical site such as Stack Overflow. A satirical website that shows the exact problem by translating an English phrase to the various different languages before returning to English, and it tends to show translation errors arrive rather quickly. | |
| Jul 22, 2009 at 16:20 | history | answered | Jim C | CC BY-SA 2.5 |