Friday, October 24, 2008

Editors

A good editor is an essential part of a translation team, but working with a bad one may be a nightmare.
  • A good editor must be a good translator, but sometimes a good translator is not a good editor: a good translator who has too high an opinion of himself and who is convinced that the definition of error is "something translated different from what what I would do" is unlikely to make a good editor.
  • A good editor must know when to change things that are not real errors. This may be necessary to achieve an appropriate register, to standardize style and terminology in team projects, to follow the style guide provided by the customer, etc.
  • A good editor must also know when, instead, it is better to leave things alone (for example, when the translation is done in a style different than one would use, but which is still appropriate).
  • A good editor needs to know how to indicate when a translation is wrong, how to indicate the type of error, and when instead to indicate that the changes made are preferential.
When I work as an editor I tend to make many changes in the translations I receive. But I also take care to say to the customer when the corrections are because of real errors (serious or otherwise) and when I am suggesting stylistic changes. For example:

"You'll see that I have made a lot of changes, but the translation was not, in fact, incorrect: these are almost all preferential changes made to give more of a "marketing" flavor to an otherwise correct translation."

Tuesday, October 14, 2008

"The sorrow with any translation"

A couple of interesting quotes from a recent, excellent article (from "The Australian") on new translations of Virgil:

"The sorrow with any translation is that you're never really quite there, [but] you may be someplace almost as good."
[Stanley Lombardo, professor of classics at the University of Kansas]

A translator must strive to see the work in its own terms, [Ruden] believes, while knowing that such a goal will always be just out of reach. "But it's something that you keep pushing and pushing and pushing, until you pass out from exhaustion."
[Sarah Ruden, poet and classicist]

The entire article is very much worth reading, and a welcome change of pace from the humdrum translations we might be working on.

Wednesday, October 01, 2008

Writing in a foreign language

As translators, we are not supposed to work into our second language, only from it. However, we have to write in a foreign language when we live and work in a foreign country: We need to be able to write it well to correspond with our customers and colleagues, to give classes and presentations, to write resumes and applications. If we want to communicate more broadly, we may decide that a more widespread language (like English) opens to us a wider stage.

We should strive to write our second language as well as possible, with elegance and precision, style, restraint, and power. We may even find that writing in a foreign language is easier than translating into it: when we translate, we are bound to the path chosen for us by the original author; when we write, we are making our own way.

I came to love English, to appreciate its difficulties and beauty, its subtleties, its style. Over time I learned to think in English, now I often dream in it. Do I write like a native? I don't think so: we are often blind to our faults. But I'm attuned to the way good English is written: for certain things, it is a more flexible tool than Italian.

In English a good standard is saying things in a simple manner, trying to be concise, to use the active voice. Far too often, in Italian we find instead convoluted sentences, needlessly complex syntax, the use of language not to communicate but as a way to show off. Hence, so much legal and bureaucratic verbiage, and also the misplaced love for half-learned, and one-fourth-understood foreign (especially English) words when Italian ones would do.

Thursday, September 25, 2008

The seductive power of words

Words are the embryos of ideas, the seed of thought, the framework of reasoning, but their contents goes beyond the simple official definition found in dictionaries. There, words appear exact, precisely and scientifically measured... And in these cold, orderly lists you cannot find the inner expanse of each word, but only the doorway to them.



From "La seducción de las palabras", by Alex Grijelmo, Santillana Ediciones Generales, 2000, as published by Punto de Lectura, 2007 (the translation o the passage is my own).

Thursday, September 11, 2008

The right word

“The difference between the right word and the almost right word is the difference between lightning and a lightning bug”

Mark Twain

Monday, September 08, 2008

New widget for this blog

In the right-hand bar I've added three Technorati charts, to track the relative frequency in blogs of the strings "translation", "translation quality" and "Trados" over a period of thirty days.

By clicking on the charts, you go to a Technorati page with links to the actual posts.

Thursday, August 28, 2008

Yet again: Trados fuzzy match woes (Expanded)

Continuing from my post of August 25, some further evidence of just how badly designed the fuzzy matching algorithms are in Trados:

So, according to Trados, "INSTALLING DISPLAY" is a 67% match for "Installing Display", while "Ownership of the Services and Marks." is a 65% match for "Description of the Service and Definitions."


A smarter matching algorithm would give more importance to meaningful words ("Description", "Service", "Definitions") than to grammatical ones ("of" "the" "and"), and would treat a difference between upper and lower case as much less significant than the chance similarity of two sentence structures.

By the way if "Installing Display" is changed to "Installing the Display", it does not come up as a fuzzy match at all (unless the fuzzy threshold is set extremely low), since it becomes a mere 40% match:


The worse thing is that all these problems have been known for years, but Trados (and now SDL/Trados) programmers have done nothing to improve the situation.

Wednesday, August 27, 2008

Trados: which bugs have been fixed?

I've just received a rather pushy call from an SDL/Trados representative. He wanted to know if I was considering upgrading from Trados 2007 to the newest version. When told that I was actually consider whether to change to a competitor's product, he asked why.

The reason I gave him was defects in the program, and old bugs never fixed.

I wonder however, if any of the more persistent bugs have been fixed with the latest releases - as far as I know, they haven't, but I would be happy to learn otherwise.

In particular, I'm thinking of such longstanding defects as the poor quality of low-fuzzy matches (see the previous post), the fact that formats are often mangled in MS Word documents, the irregular behavior of Workbench when translating MS Word tables with multiple columns (when Set Close/Next Open Get skips entire rows), the absence of shortcuts to open directly the previous segment, or the feebleness of the search functions within Tag Editor.

As far as I know, all development efforts were focused on supporting Vista/Office 2007, on corporate features, and on fixing some really disastrous new bugs (if any were introduced or discovered recently).

No real improvements to longstanding bugs, defects and annoyances as mentioned above. Does anybody know if this is still true, or which defects (if any) have been fixed after, say, version 7.1 and which improvements have been implemented?

Monday, August 25, 2008

Yet again: Trados fuzzy match woes

I sometime wonder whether SDL Trados programmers even understand the concept of fuzzy matching, or, if they do, whether they care or have pride in their job - only incompetent programmers would create or use a fuzzy matching algorithm that leads to ludicrous results such as these:


That's right: according to Trados, the segment "Ownership of the Services and Marks." is a 65% match for "Description of the Service and Definitions."

After all, "of the" and "and" are exactly the same in both sentences.

Wednesday, August 20, 2008

Translator v. linguist

One thing that riles me is the habit many translation companies have of calling us "linguists". According to my dictionaries, a linguist is either a specialist in linguistics or a person who knows more than one language.

Neither meaning directly applies: not all translators are specialists in linguistics, and most specialists in linguistics are certainly not translators. And though all translators do know more than one language, not all people who know more than one language have what it takes to be translators.