10:19 Feb 6, 2001 |
German to English translations [PRO] Tech/Engineering | |||||||
---|---|---|---|---|---|---|---|
|
| ||||||
| Selected response from: Tom Funke Local time: 23:28 | ||||||
Grading comment
|
Summary of answers provided | ||||
---|---|---|---|---|
na | works/almost works method |
| ||
na | addendum |
| ||
na | get / get fast |
| ||
na | Trial-and-error method |
|
works/almost works method Explanation: I don't have much to back this up, but in AltaVista (English) _feasable/almost feasable_ registered no hits, while _works/almost works_ registered one hit, in which testing is done with three outcomes: works; almost; broken HTH Tom AltaVista |
| |
Login to enter a peer comment (or grade) |
addendum Explanation: Below is the URL I should have referenced Reference: http://mail-index.netbsd.org/port-i386/1996/05/26/0026.html |
| |
Login to enter a peer comment (or grade) |
get / get fast Explanation: Again I think a spelling mistake. I microrporcessors you have so-called "get cycles" in which information is for instance recovered from RAM or a cache, or a procedure is called up. In German it is frequently (if old-style) called a "Holanweisung". Schleber, Computer Englisch |
| |
Login to enter a peer comment (or grade) |
Trial-and-error method Explanation: Geht/GehtFast isn't a technical term. Literally it means "It works, it almost works" meaning that they had to try a lot of things until they finally could make it run. To translate adequately I would use "trial-and-error method" - |
| |
Login to enter a peer comment (or grade) |
Login or register (free and only takes a few minutes) to participate in this question.
You will also have access to many other tools and opportunities designed for those who have language-related jobs (or are passionate about them). Participation is free and the site has a strict confidentiality policy.