///
It is generally agreed that context is essential in translation studies. However, according to Baker (2006), “translation scholars have so far largely ignored the obvious centrality of the notion of context to their own discipline”. She suggests that instead of treating context as a constraint, “a set of restrictions on what we can or cannot achieve in translation and other communicative events,” it might be more productive to “recognize context as a resource”. Translators should carefully assemble the needed types of context for a given project and ask for additional resources. Human translators who understand source texts in their full context need not be afraid of machine translation. Rather, they should be happy that machine translation can take care of some tedious and boring work while they apply their minds to work that cannot be done properly by a computer. Those considering the use of machine translation should evaluate the types of context needed to produce an acceptable translation of the source texts in question. Computers are incapable of taking into account non-text. When texts are tightly restricted to a narrow domain and are highly uncreative, all the context that is needed may be present in the source text, monolingual dictionaries, and processed bitexts. When understanding of the source text and adherence to a variety of specifications is required, it is probably better to ask a human to produce the initial draft translation rather than post-edit a raw machine translation.
The word “rather” (.25) can be correctly translated as da mesma forma.