Getting stuff off my chest...

Increasingly, agencies run new documents past their databases of document "segments" (typically, sentences) that have been translated before. Heck, I do this all the time myself, with databases of segments I've translated previously, as that is the entire point of the "translation memory" concept.

The problem arises when they embed found segments in documents sent out for translation and insist on paying a reduced rate for "editing" said translations.

Traditionally, editing a translation pays less than writing the translation to begin with. And that's because of the unspoken assumption that the translation has been competently written.

What is a competent translation?

Well, back when I worked in-house in Houston, and had a voice in defining "competence" in this context, we decided that a translation containing more than one major error per 250 words was poor, and one with more than two major errors per 250 words was unacceptably poor.

If one assumes that an "average" sentence consists of 25 words (an assumption that might be called "conservative," in the engineering sense), that works out to one major error per 10 sentences for a poor translation, and one major error per 5 sentences for an unacceptably poor translation.

So if you consider that a "pretranslated" segment that is less than an 100% match to the corresponding bit of source text is guaranteed to have a major error in it (after all, it's not a 100% match!), and that typically, less than 1 in 5 pretranslated segments are a 100% match, the end result is like editing an utterly and completely incompetent translation, for which one is offered a rate typically offered for editing a competent translation.

So in my current assignment, I'm not only finding the less-than-100% matches requiring attention, but the 100% matches as well. To wit:

{0>
Такая укрупненная частица (флок) осаждается более быстро.
<}100{>
Sedimentation of a large particle, or floc, is faster.
<0}
My version:
Such an enlarged particle (floc) settles more quickly.

{0>
Это происходит за счет совокупного действия нескольких процессов.
<}100{>
The effect can be explained by the following processes.
<0}
My version:
This is due to the combined action of several processes.

{0>
Параметризация турбулентности основана на сформулированном в (Озмидов, 1986) подходе.
<}100{>
The turbulent parameterization is based on the Ozmidov’s approach (1986).
<0}
My version:
Parameterization of turbulence is based on the approach formulated by Ozmidov (1986).

{0>
Турбулентность может быть представлена на основе вложенных вихревых структур разного масштаба, определяемого океаническими процессами.
<}100{>
The turbulence may be presented as the enclosed eddies of a different scale depending on oceanic processes.
<0}
My version:
Turbulence may be depicted on the basis of embedded vortex structures of various scale, determined by oceanic processes.

In addition to being annoying as hell, this kind of stuff slows me down significantly (I had, in fact, expected higher quality and factored it into my turnaround estimate).

Ah, well, there's nothing to be done about it now. I shall have to be more careful in the future, though, about accepting work from this client.

Cheers...

P.S. I repeat myself, I know, but it's therapeutic, okay?

A 5K sort of day...

I've whittled the item due Thursday down to below 4,000 words (some of those are "edits," but then again, some of those "edits" are "retranslations," too), which is good enough for the day.

I've given the end client a heads up to the effect that, between the lousy weather over the weekend and the really substandard pretranslated segments I keep running into, I might likely be a few hours late with the assignment. However, that's little comfort, as I have about 30,000 words piled high on the plate.

Today laid 2600 words of the Thursday job down on phosphor and finished an urgent job for my best Houston client, for a total of just about 5000 target words. I might do some more work tonight, or I might not.

In fact, what I ought to do is go upstairs and continue the cleanup I started earlier, as our friend Mike is coming down from Parker for another load of stuff that he and Karen put into storage before moving up north. While I am not prepared to field-day the place, on the other hand it wouldn't do to have shredded wrappers and such lying around either. (Thank you, Shiloh!)

This week's LJ Idol theme is "cracking up," and I have at least two stories I can tell. One concerns a bit of hysteria I staged back shortly after I got married, for a lofty purpose; the other has to do with a chess game that I should have lost, but won. The first would be fairly easy to write, but making it interesting might not be so easy. The second seems like that much more of a challenge, but may not work in the end. Free time will be short this week, given my plate. I think I'll sleep on it.

In the immediate time frame, however, I think I'll go upstairs and pick up a bit.

Cheers...